JD Edwards EnterpriseOne System Codes List
Every JD Edwards table, application, report and UDC list carries a system code. Knowing what 09, 41 and 43 mean lets you read object names, tables and UDC keys at a glance. This lookup lists the codes most consultants meet.
| System code | Module | Typical tables | Where the code appears |
|---|---|---|---|
00 | Foundation Environment | F0002, F0005, F0006 | UDC lists, next numbers, business units |
01 | Address Book | F0101, F0111, F0115 | Address numbers, search types, who's who |
03B | Accounts Receivable | F03B11, F03B13 | Invoices, receipts, customer ledger |
04 | Accounts Payable | F0411, F0413 | Vouchers, payments, supplier ledger |
09 | General Accounting | F0901, F0902, F0911 | Chart of accounts, balances, journal entries |
12 | Fixed Assets | F1201, F1202 | Asset master, depreciation |
30 | Product Data Management | F3002, F3003 | Bills of material and routings |
31 | Shop Floor Management | F3111, F3112 | Work order parts lists and routings |
32 | Manufacturing Accounting | F3202, F3203 | Work in process and variances |
34 | Requirements Planning | F3411, F3460 | MRP and master production schedule |
40 | Distribution Common (Foundation) | F4009, F40205 | Line types, shared distribution constants |
41 | Inventory Management | F4101, F4102, F41021, F4111 | Item master, branch plant, locations, cardex |
42 | Sales Order Management | F4201, F4211 | Sales orders and pricing |
43 | Procurement | F4301, F4311, F43121 | Purchase orders and receipts |
46 | Warehouse Management | F4600 series | Putaway and pick requests |
47 | EDI | F47011, F47012 | EDI transaction staging |
48 | Work Orders (Plant and Equipment) | F4801, F4802 | Work order header and text |
49 | Transportation Management | F4915 series | Shipments and loads |
98 | Technical Tools | F9860, F9210, F986110 | Object Librarian, data dictionary, job control |
55-59 | Reserved for customer use | Custom tables | Custom tables and objects, for example F5501 |
System codes group tables, programs and user defined codes. Customer built objects use the reserved codes 55 to 59 so that upgrades never overwrite them. Confirm tables in your own release.
JDE module to data map
Optional: ask for a worked map of the tables behind your installed JDE modules.
Optional. The tool and every export work without this. No spam.
How to use the list
Search by module name, such as inventory, or by number. The tables column shows the main tables that belong to the system so you can move from a module question to a SQL question quickly. Export to Excel to share a one-page cheat sheet with new team members or project analysts.
Where system codes appear
The system code is the first part of table names, so F4801 sits in system 48. It also keys user defined codes: the UDC table F0005 uses DRSY for the system code and DRRT for the code type. 00/DT is the document type list and 00/UM is the unit of measure list. Application and report numbers also start with the code, such as P4210 for Sales Order Entry and R42800 for update.
Custom work and reserved codes
JDE reserves system codes 55 to 59 for customer use, so custom tables such as F5501 and applications such as P5501 do not collide with Oracle objects. If you are auditing modifications, search Object Librarian for objects whose system code is in that range.
Common mistakes
Treating the system code as the module a user opens in the menu (menus group by task), assuming document type codes belong to one system only, and confusing system 03B with 03. Verify names against your release and installed modules before building integrations.
Frequently Asked Questions
What is a JDE system code?
It is a two character code that identifies a product area, such as 09 for General Accounting. It prefixes table numbers, programs and reports, and it keys user defined codes so that lists belong to the right module.
Why is Accounts Receivable 03B?
System 03 is the legacy AR system and 03B is the one used for the current Accounts Receivable ledger tables, which is why tables like F03B11 carry the B. Both exist in the product.
Which system codes can I use for custom objects?
Systems 55 through 59 are reserved for customers. Putting custom tables, applications and UBEs there keeps them separate from Oracle delivered objects and makes upgrade comparisons easier.
Does this list match every release?
The core codes are stable across releases, but modules installed and table details vary. Check Object Librarian and the Data Dictionary in your environment before you rely on a specific table number.
If you are mapping JDE modules to an integration or an AI assistant, we can help scope which tables and system codes are in play for your plants.
Related Tools
JD Edwards EnterpriseOne Core Table Reference
Searchable list of the JD Edwards EnterpriseOne tables you query most often, with column prefix and the key fields to filter on.
OracleJD Edwards Julian Date Converter
Turn a calendar date into the CYYDDD Julian number JDE stores in tables such as F0911 and F4801, with leap years handled.
OracleJD Edwards CNC Environment Health Check Checklist
A weekly or monthly checklist for JDE CNC admins covering servers, web tier, database, batch processing, security and backups.
OracleJD Edwards Package Build and Deployment Checklist
Step-by-step checklist for building and deploying JDE packages: pre-build checks, build, deployment, verification and rollback.
More Oracle tools
See all- JD Edwards Document Types Reference (OP, SO, OV, PV)
- JD Edwards UBE Job Scheduling Worksheet
- JD Edwards Table Reference (F4211, F4311, F0101, F4101, F4102)
- JD Edwards Tools Release Upgrade Checklist
- JD Edwards Orchestrator Design Template
- JD Edwards Security Workbench Worksheet
- JD Edwards Environment Refresh Runbook Template
- JD Edwards UBE Runtime Log Worksheet
- JD Edwards Next Numbers Capacity Worksheet