Sage X3 Table Dictionary: How to Browse Tables and What PAYMENTD Holds
sage x3 table dictionary
Also searched as
- sage x3 paymentd table
- sage x3 database tables list
- sage x3 data dictionary lookup
Short answer
Sage X3 keeps its table definitions in a data dictionary you browse from the development area of the application. Tables are named in short uppercase codes, live in the folder's schema (often a schema named like the folder, such as SEED), and columns carry a numeric suffix like _0. PAYMENTD holds the line-level detail of payment entries, paired with a header table.
Applies to: Sage X3 V7, V11, V12 and later on SQL Server or Oracle; table and column lists vary by version and customization, so verify in your own dictionary
How to look up an X3 table
- 1Open the data dictionary functions in the development menu of the web client with a user that has development rights.
- 2Search the tables list by code or description, for example payment, to find PAYMENT-related tables.
- 3Open the table to see its columns with labels, types, lengths and links to menus or lists of values.
- 4Check the indexes and the key columns before writing any query that joins it.
- 5Note the activity codes and the module that owns the table, because it may be empty if the module is not used.
- 6Connect to the database with a read-only account and query the table in the folder schema, using its column names with suffixes.
- 7Cross-check results against the screen that displays the same data, to confirm you read it correctly.
How X3 names things
X3 tables use short uppercase codes, for example ITMMASTER for items, SORDER for sales orders and BPCUSTOMER for customers. In the database each column is the field name plus a suffix, commonly _0 for the first dimension, and some arrays add _1, _2 and so on. Every table also has a unique row identifier column used by the platform.
Use the dictionary rather than memory for table names. Verticals and customizations add tables and columns, and renamed or restructured tables appear between versions.
Payment tables and PAYMENTD
Payment entries in accounting are stored with a header record and line records. PAYMENTD is the detail table, holding the lines of a payment, such as the documents settled and the amounts, while the paired header table holds the payment's top-level data like the bank, date and number. Join them on the payment key columns shown in the dictionary.
Before reporting on payments, read how your folder uses them: settlement against invoices, on-account payments and bank reconciliation can sit in several related tables. Reconcile your query totals to a standard X3 report or screen first.
-- Illustrative pattern: confirm table and column names in your dictionary SELECT TOP 100 * FROM SEED.PAYMENTD ORDER BY CREDATTIM_0 DESC;
Staying safe in the database
Query with a read-only database user, preferably on a reporting copy. Do not update X3 tables directly, because business logic, audit information and consistency across tables are maintained by the application. For writes, use the application, representations or web services.
Try it here, free
Sage X3 Database Tables Reference
Key Sage X3 tables by module with what they store, typical key columns and naming conventions for SQL and reporting.
Common pitfalls
- !Updating tables with SQL, which bypasses X3 logic and breaks consistency.
- !Forgetting the column suffixes (_0) in queries.
- !Assuming a table name from another version or from a blog post.
- !Joining without checking keys and activity codes, which duplicates rows.
- !Running heavy queries on the production database in working hours.
How an ERP-grounded AI assistant handles this
Report writers lose hours translating a business question into joins across terse X3 tables. A private AI layer such as ERPray can read the dictionary, build the query for a question like open payments by supplier, show the SQL it ran, and respect X3 roles. It can run next to your database without sending schema data outside.
Frequently asked questions
Where is the Sage X3 data dictionary?
In the development area of the application, under data and parameters functions for tables, with access limited to users with development rights. It lists tables, columns, types and indexes for your own folder.
What does the _0 suffix mean on X3 columns?
It is the dimension index of the field in the database. Single-value fields end in _0, while array fields add further suffixes like _1 and _2. Always include the suffix when writing SQL.
What is the PAYMENTD table?
It holds the detail lines of payment entries in X3, linked to a header table. Use the dictionary in your version to confirm columns, and reconcile your totals against standard payment screens or reports.
Can I update X3 data with SQL?
It is not recommended. Direct updates skip application logic and can break consistency and audit trails. Use X3 functions, representations or web services for any write.
Related
Sage X3 API Documentation: REST (Syracuse), SOAP Web Services and Where to Find Docs
Sage X3 exposes data and business logic in two main ways: REST-style SData services through Syracuse, which read and write business objects as JSON or XML, and SOAP web services that publish X3 subprograms and objects. Official documentation is in Sage's online help and developer resources for your version.
How-toSage X3 REST API: Reading Sales Orders Through Syracuse
Sage X3 (version 7 and later) exposes data through Syracuse at a URL of the form /api1/x3/erp/ENDPOINT/REPRESENTATION, where the endpoint is the folder and the representation is a published object such as SORDER. A GET with credentials returns JSON, and you filter with a where clause and page with count and a link to the next page. Your integration user needs the right Syracuse and X3 rights for that representation.
How-toSage X3 Production Planning, Scheduling and Tracking
Sage X3 plans production from master data (items, BOMs, routings, work centers) through MRP or manual work orders, schedules operations against work center capacity, then records progress with production tracking. Setup quality in the BOM, routing and work center calendar decides whether the plan is believable.
Error fixDivision by 0 Error in Sage X3: Find the Cause and Fix It
A division by 0 error in Sage X3 means a calculation divided by a field that was zero or empty at runtime. Typical sources are a zero unit-of-measure coefficient, a zero quantity or base quantity on a BOM or routing, a zero price or rate, or custom 4GL or report code that never guards the denominator. Find the script and line from the error, then fix the data or guard the calculation.
How-toSage X3 Developer Studio: What It Does and How to Track Versions and Release Notes
Sage X3 Developer Studio is the development environment for building and changing X3 solution code and web pages, working with the Adonix 4GL scripts and the Syracuse web layer. To track versions, read the release notes and compatibility guides that Sage publishes for each version and patch rather than relying on remembered dates.
How-toSubcontracting in Sage X3: Setup, Flow, Packing and What MFGM Means
In Sage X3, subcontracting means an outside supplier performs one or more operations on your material. You flag the operation as subcontracted in the routing, the work order drives a purchase document to the subcontractor, components are sent, and the processed goods are received back into stock. MFGM is generally how people refer to the manufacturing module and its records, not a separate feature.
AI for ERPAI for Sage X3, Grounded in Your Own Ledgers and Stock Data
Add AI to Sage X3 finance and stock data without exporting it to a public model. On-prem and private-cloud LLMs for Sage X3 in the UK and France.
Stuck on Sage X3?
Talk to engineers who work inside Sage X3 every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- Sage X3 Database Tables ReferenceKey Sage X3 tables by module with what they store, typical key columns and naming conventions for SQL and reporting.
- Sage X3 Import Template WorksheetAn editable import tracker for Sage X3: which object, which import template, source file, records loaded, errors and owner, with error rates calculated.
- Sage X3 Maintenance Checklist and ScheduleA tick-box routine maintenance plan for Sage X3: database, batch server, Syracuse, backups, patches, security and testing.
ERP fixes and how-tos
- Sage X3 Production Planning, Scheduling and TrackingHow Sage X3 production planning works: master data, MRP, work orders, scheduling and shop floor tracking, and what to set up first. Practical overview.
- Sage X3 AI Integration On-Prem: A Private ArchitectureHow to add a private AI assistant to on-prem Sage X3: SQL read replica, Syracuse SData and web services, retrieval index, local GPU model and audit trail.
- Sage X3 maintenance guide: services, patches and databaseA routine maintenance checklist for on-prem Sage X3: services, Syracuse, database, logs, backups, patches and what to test before and after changes.
AI on your ERP
- AI for Sage X3, Grounded in Your Own Ledgers and Stock DataAdd AI to Sage X3 finance and stock data without exporting it to a public model. On-prem and private-cloud LLMs for Sage X3 in the UK and France.
- AI for Sage X3 Purchasing and Stock: Orders, Receipts and LotsAI for Sage X3 purchasing and stock: PO review, supplier delivery analysis, stock status and lot questions over X3 data using GraphQL, SOAP and private models.
Integrations
- How to connect Power BI to Sage X3Connect Power BI to Sage X3 through a warehouse, replica or API, use the on-prem gateway, build manufacturing dashboards and add natural-language questions.
- How to add AI agents to Sage X3How to add AI agents to Sage X3: a tool layer over SData and web services, read-first design, human approval on writes, and on-prem models for MRP and POs.