# Dynamics GP Work, Open and History Table Map > Source: https://netray.co/tools/dynamics-gp-open-work-history-table-map > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A searchable list of Dynamics GP tables grouped by lifecycle: master, work, open and history, so you know where a transaction lives at each stage. ## Category microsoft-dynamics ## Erp Microsoft Dynamics GP ## Audience - GP developer - Report writer - Migration consultant ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Table **Key:** table **Type:** text #### Module **Key:** module **Type:** text #### Lifecycle stage **Key:** stage **Type:** text #### What it holds **Key:** contents **Type:** text **Rows:** **Table:** GL00100 **Module:** GL **Stage:** Master **Contents:** Account master (ACTINDX, ACTDESCR, account type) **Table:** GL00105 **Module:** GL **Stage:** Master **Contents:** Account index master (ACTINDX to account number string ACTNUMST) **Table:** GL10000 **Module:** GL **Stage:** Work **Contents:** Unposted GL transaction header (batch entry) **Table:** GL10001 **Module:** GL **Stage:** Work **Contents:** Unposted GL transaction lines **Table:** GL10110 **Module:** GL **Stage:** Summary **Contents:** Account period summary for the current open year **Table:** GL10111 **Module:** GL **Stage:** Summary **Contents:** Account period summary for historical years **Table:** GL20000 **Module:** GL **Stage:** Open **Contents:** Posted GL transactions for the open year **Table:** GL30000 **Module:** GL **Stage:** History **Contents:** Posted GL transactions for closed years **Table:** GL40000 **Module:** GL **Stage:** Setup **Contents:** General Ledger setup **Table:** RM00101 **Module:** RM **Stage:** Master **Contents:** Customer master **Table:** RM00102 **Module:** RM **Stage:** Master **Contents:** Customer address master **Table:** RM10301 **Module:** RM **Stage:** Work **Contents:** Sales work and open transactions entered in Receivables **Table:** RM20101 **Module:** RM **Stage:** Open **Contents:** Receivables open transactions (invoices, credits, payments with balance) **Table:** RM20201 **Module:** RM **Stage:** Open **Contents:** Receivables apply open (applications between documents) **Table:** RM30101 **Module:** RM **Stage:** History **Contents:** Receivables history transactions after removal **Table:** RM30201 **Module:** RM **Stage:** History **Contents:** Receivables apply history **Table:** PM00200 **Module:** PM **Stage:** Master **Contents:** Vendor master **Table:** PM00300 **Module:** PM **Stage:** Master **Contents:** Vendor address master **Table:** PM10000 **Module:** PM **Stage:** Work **Contents:** Payables transaction work **Table:** PM20000 **Module:** PM **Stage:** Open **Contents:** Payables open transactions **Table:** PM30200 **Module:** PM **Stage:** History **Contents:** Payables paid transaction history **Table:** PM30300 **Module:** PM **Stage:** History **Contents:** Payables apply to history **Table:** SOP10100 **Module:** SOP **Stage:** Work **Contents:** Sales transaction header, not yet moved to history **Table:** SOP10200 **Module:** SOP **Stage:** Work **Contents:** Sales transaction line items, not yet moved to history **Table:** SOP30200 **Module:** SOP **Stage:** History **Contents:** Sales transaction header history **Table:** SOP30300 **Module:** SOP **Stage:** History **Contents:** Sales transaction line amounts history **Table:** POP10100 **Module:** POP **Stage:** Work **Contents:** Purchase order header, open **Table:** POP10110 **Module:** POP **Stage:** Work **Contents:** Purchase order line items, open **Table:** POP30100 **Module:** POP **Stage:** History **Contents:** Purchase order header history **Table:** POP30110 **Module:** POP **Stage:** History **Contents:** Purchase order line history **Table:** POP10300 **Module:** POP **Stage:** Work **Contents:** Purchasing receipt header, unposted **Table:** POP10310 **Module:** POP **Stage:** Work **Contents:** Purchasing receipt lines, unposted **Table:** POP30300 **Module:** POP **Stage:** History **Contents:** Purchasing receipt header history **Table:** POP30310 **Module:** POP **Stage:** History **Contents:** Purchasing receipt line history **Table:** IV00101 **Module:** IV **Stage:** Master **Contents:** Item master **Table:** IV00102 **Module:** IV **Stage:** Master **Contents:** Item quantity master, by item and site (RCRDTYPE 2 is site level) **Table:** IV00103 **Module:** IV **Stage:** Master **Contents:** Item vendor master **Table:** IV10000 **Module:** IV **Stage:** Work **Contents:** Inventory transaction work header **Table:** IV10200 **Module:** IV **Stage:** Open **Contents:** Stock purchase receipts (cost layers) **Table:** IV30200 **Module:** IV **Stage:** History **Contents:** Inventory transaction history header **Table:** IV30300 **Module:** IV **Stage:** History **Contents:** Inventory transaction amounts history **Table:** SY01400 **Module:** SY **Stage:** System **Contents:** User master (DYNAMICS database) **Table:** SY01500 **Module:** SY **Stage:** System **Contents:** Company master (DYNAMICS database) **Table:** SY40100 **Module:** SY **Stage:** Setup **Contents:** Fiscal periods setup, period dates by year **Notes:** Table names are consistent across GP 2013 through 2018 and later, but ISV products and some versions add columns. Confirm against your own database before writing production queries. Company tables live in each company database; SY01400 and SY01500 live in DYNAMICS. ## Content **Intro:** Dynamics GP stores the same business document in different tables depending on where it is in its life. This map shows which table to query for master data, unposted work, open items and history, so reports and migration extracts stop missing records. **Sections:** #### How to use the table map **Body:** Search by table number, module prefix or keyword such as 'history' or 'receipt'. The lifecycle column tells you where a document sits. A posted receivables invoice lives in RM20101 while it has a balance and moves to RM30101 only after the Remove Receivables Transactions utility runs. If you query only one table you will either miss paid items or double count them. **Bullets:** - Filter by module prefix (GL, RM, PM, SOP, POP, IV) to see one subledger - Use the Work and Open rows to find unposted data before a cutover - Export to Excel and share it as a data dictionary for the migration team #### The numbering convention behind the names **Body:** GP table numbers follow a pattern: 00xxx are masters and setup, 10xxx are work or open-entry tables, 20xxx are open posted records, and 30xxx are history. That pattern is not a strict contract, since GL10110 is a summary and IV10200 holds cost layers, but it is a reliable first guess when you meet an unfamiliar table. The prefix before the digits is the module: RM receivables, PM payables, SOP sales order processing, POP purchase order processing, IV inventory, GL general ledger. #### Worked example: where is invoice INV-1041? **Body:** A sales invoice touches several tables. Before posting it sits in SOP10100 and SOP10200. After posting it is in SOP10100 until the Sales history utility moves it to SOP30200. Its receivable lives in RM20101 until paid and removed, then RM30101. The GL impact is in GL20000 for the open year or GL30000 for a closed year. Joining across all of these with UNION is how you build a complete document trace. #### Common mistakes **Body:** The most frequent error is reading balances from the wrong lifecycle stage. Customer balances should come from RM20101 CURTRXAM, not from summing history. Another is joining GL transactions to accounts by account string instead of ACTINDX through GL00105. Finally, remember that ISV add-ons write their own tables, so this map covers standard GP only. **Bullets:** - Do not assume a posted document has left the work table - Void documents still exist, check VOIDSTTS or the module's void flag - Test on a copy of the company database, never on production **Cta:** If your GP data needs to be extracted, reconciled and loaded into a successor ERP, we can help build read-only extraction queries and reconciliation reports against your own database. **Faq:** #### Does this list every Dynamics GP table? **Answer:** No. A full GP company database has well over a thousand tables. This map covers the core financial, receivables, payables, sales, purchasing and inventory tables most reports and migrations touch. Use the Table and Field reference in GP Support Debugging Tool or the SDK documentation for the rest. #### Why are posted documents still in work tables? **Answer:** GP keeps posted sales and purchasing documents in the 10xxx tables until you run history utilities such as Sales Transaction history transfer. Posted does not mean moved. Check the document status columns rather than assuming the table tells you. #### Which database holds SY01500? **Answer:** SY01500 is in the system database, named DYNAMICS by default. It lists every company and its database name (INTERID). Queries that loop across companies usually start by reading SY01500, then switch databases. #### Can I write directly to these tables? **Answer:** It is strongly discouraged. Direct inserts bypass GP business logic, numbering and posting. Use eConnect, Web Services or integration tools for writes, and treat SQL as read-only for reporting and extracts. ## Search terms dynamics gp table list, gp open vs history tables, gp work tables, dynamics gp database tables, RM20101 RM30101, PM20000 PM30200, SOP30200 history, dynamics gp sql reference --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json