# QAD Core Tables Reference (pt_mstr, so_mstr, ld_det and more) > Source: https://netray.co/tools/qad-core-tables-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A searchable lookup of the QAD EE tables you query most, what each holds and how they are keyed. ## Category other-erp ## Erp QAD ## Audience - QAD developer - Report writer - Data migration lead ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Table **Key:** table **Type:** text #### Area **Key:** area **Type:** text #### What it holds **Key:** meaning **Type:** text #### Typical key **Key:** key **Type:** text **Rows:** **Table:** pt_mstr **Area:** Item **Meaning:** Item master: description, unit of measure, product line, status **Key:** pt_domain, pt_part **Table:** ptp_det **Area:** Item **Meaning:** Item-site planning data: lead times, order policy, safety stock **Key:** ptp_domain, ptp_site, ptp_part **Table:** in_mstr **Area:** Inventory **Meaning:** Inventory master per item and site: on hand, allocated, on order **Key:** in_domain, in_part, in_site **Table:** ld_det **Area:** Inventory **Meaning:** Location detail: quantity on hand by site, location, lot and reference **Key:** ld_domain, ld_site, ld_loc, ld_part, ld_lot, ld_ref **Table:** tr_hist **Area:** Inventory **Meaning:** Inventory transaction history **Key:** tr_domain, tr_trnbr **Table:** lad_det **Area:** Inventory **Meaning:** Location allocation detail for open demand **Key:** lad_domain, lad_dataset, lad_nbr, lad_line **Table:** ps_mstr **Area:** Engineering **Meaning:** Product structure: parent and component bill of material links **Key:** ps_domain, ps_par, ps_comp, ps_ref, ps_start **Table:** ro_det **Area:** Engineering **Meaning:** Routing operation detail **Key:** ro_domain, ro_routing, ro_op **Table:** so_mstr **Area:** Sales **Meaning:** Sales order header **Key:** so_domain, so_nbr **Table:** sod_det **Area:** Sales **Meaning:** Sales order line detail **Key:** sod_domain, sod_nbr, sod_line **Table:** cm_mstr **Area:** Sales **Meaning:** Customer master **Key:** cm_domain, cm_addr **Table:** ih_hist **Area:** Sales **Meaning:** Invoice history header **Key:** ih_domain, ih_inv_nbr **Table:** idh_hist **Area:** Sales **Meaning:** Invoice history line detail **Key:** idh_domain, idh_inv_nbr, idh_line **Table:** abs_mstr **Area:** Shipping **Meaning:** Shipper and container master used in shipments **Key:** abs_domain, abs_shipfrom, abs_id **Table:** po_mstr **Area:** Purchasing **Meaning:** Purchase order header **Key:** po_domain, po_nbr **Table:** pod_det **Area:** Purchasing **Meaning:** Purchase order line detail **Key:** pod_domain, pod_nbr, pod_line **Table:** prh_hist **Area:** Purchasing **Meaning:** Purchase receipt history **Key:** prh_domain, prh_receiver, prh_line **Table:** vd_mstr **Area:** Purchasing **Meaning:** Supplier master **Key:** vd_domain, vd_addr **Table:** wo_mstr **Area:** Production **Meaning:** Work order header **Key:** wo_domain, wo_nbr, wo_lot **Table:** wod_det **Area:** Production **Meaning:** Work order component detail **Key:** wod_domain, wod_nbr, wod_lot, wod_part, wod_op **Table:** sct_det **Area:** Costing **Meaning:** Cost simulation detail by item and site **Key:** sct_domain, sct_sim, sct_part, sct_site **Table:** ad_mstr **Area:** Common **Meaning:** Address master shared by customers, suppliers, sites **Key:** ad_domain, ad_addr **Table:** code_mstr **Area:** Common **Meaning:** Generalized codes (validation lists and reason codes) **Key:** code_domain, code_fldname, code_value **Table:** glt_det **Area:** Finance **Meaning:** General ledger transaction detail **Key:** glt_domain, glt_ref, glt_line **Notes:** Key lists are typical, not exhaustive. Confirm with the Progress data dictionary of your own database because versions and customisations differ. Domain fields apply to domain-enabled releases. ## Content **Intro:** Anyone writing a QAD report, extract or migration mapping needs to know which table holds what. This reference lists the main EE tables with their purpose and typical keys, and is searchable by name, area or meaning. **Sections:** #### How to use the table **Body:** Type part of a table name or a business word, such as invoice or location, into the search box to filter the list. Use the Area column to see every table in a business domain at once, which is handy when scoping a data migration. Export the full list to Excel and add columns for record counts, owner and migration decision. The naming pattern helps: _mstr usually means a master or header table, _det a detail or line table, and _hist a history table. #### Understanding the naming and keys **Body:** QAD field names start with a table prefix, so pt_part belongs to pt_mstr and sod_line to sod_det. Domain-enabled releases add a domain field as the first part of most keys, which is why queries should always filter on it. Header and detail tables are joined on the order or document number, then line. A few tables such as in_mstr and ptp_det are per site, so one item can have many rows in them but a single row in the item master. #### Worked example: tracing an open order **Body:** To find what is holding a sales order line, start in sod_det for the line and quantities, join to so_mstr for the customer, read lad_det for the allocation against stock, then ld_det for the quantity on hand in the allocated location. If the stock sits in a location with a non-available inventory status, allocation will not satisfy the line. This chain of four tables answers most why is it not shipping questions. #### Common mistakes **Body:** Do not assume pt_mstr holds quantities, as stock lives in ld_det and in_mstr. Do not join across domains by accident. Do not treat history tables as editable: corrections are made by new transactions. Finally, never write to tables directly from outside QAD, because the application maintains related records and audit trails that direct updates will bypass. **Cta:** If you are mapping QAD tables for a migration or an AI layer, we can help review the mapping and the queries that depend on it. **Faq:** #### Are these table names the same in every QAD version? **Answer:** The core names have been stable for many releases, but fields and keys change, especially around domains. Always check the data dictionary of the database you are working with, and treat this list as a starting map. #### Where do I find quantity on hand? **Answer:** Quantity by location, lot and reference is in ld_det. Quantity totals per item and site are in in_mstr. Summing ld_det for an item and site should agree with the in_mstr figure unless there is a data problem. #### What does the _hist suffix mean? **Answer:** History tables hold posted records, such as invoices or receipts, and are generally not changed after posting. They are usually the right source for reporting on what actually happened. #### Can I use this for Adaptive ERP? **Answer:** Much of the structure carries over, but the cloud product may expose data through APIs and exports rather than direct database access. Use this list to understand concepts and map fields, then check the supported interfaces. ## Search terms qad table list, qad pt_mstr, qad ld_det, qad tr_hist, qad database schema, qad table names, qad sod_det, qad data dictionary --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json