Platform knowledge base
Platform Knowledge Base
Architecture, data models, and table-level reference for the SAP, Oracle, DDRS, legacy, and Treasury platforms behind the DoD financial management systems in this suite.
Numbered reference tables
24 architecture and data model diagramsReferences
Browse the knowledge base
Compiled October 2026 from public vendor, DoD, DoD IG, GAO, DOT&E, and Treasury sources. Educational reference. Standard product tables and public sources only. Not an official DoD, DFAS, SAP, or Oracle publication.
Tables, Models, and Systems
One business event traced across SAP and Oracle tables, the SFIS and SLOA data standards, the DDRS trial balance, and the Treasury GTAS record, with the join keys that connect each layer.
7 tables, 2 diagramsPlatform referenceSAP ERP
How SAP ECC 6.0 and S/4HANA are built, how the organizational and document models work, and which tables hold the data behind GFEBS, Navy ERP, GCSS-Army, LMP, and DLA EBS.
13 tables, 5 diagramsPlatform referenceOracle E-Business Suite
How Oracle EBS Release 12 is built, how ledgers, operating units, and the Accounting Flexfield work, how Subledger Accounting links every transaction to the GL, and which tables hold the data behind DAI, DEAMS, and GCSS-MC.
13 tables, 5 diagramsSystem deep diveDDRS
How the Defense Departmental Reporting System turns Component trial balances into budget execution reports, financial statements, and the Treasury GTAS submission, with the module structure, record model, journal voucher rules, and audit history.
9 tables, 2 diagramsPlatform referenceLegacy, Treasury, and Analytics
How status-of-funds legacy systems differ from a transaction-level general ledger, what is public about CEFMS, MOCAS, the disbursing systems, and PIEE, and how the Treasury systems and Advana fit around the ERPs.
8 tables, 1 diagramSAP expert series
SAP and the DoD systems built on it, in eight parts
Architecture, every module, federal accounting, searchable catalogs of tables, transaction codes, and fields, interfaces, and referenced profiles of GFEBS, GCSS-Army, LMP, Navy ERP, and DLA EBS.
SAP Architecture
Product generations, the runtime that turns a screen entry into a committed document, the ABAP Dictionary, enhancement points, landscapes, authorizations, logging, archiving, and what changes on HANA and S/4HANA.
10 tables, 3 diagramsSAP expert series, part 2SAP Modules
Every SAP module a DoD ERP uses, each described the same way: purpose, organizational units, master data, document flow, tables, transactions, key configuration, integration, and audit notes.
20 tables, 1 diagramSAP expert series, part 3SAP Federal Accounting
How SAP Public Sector Management records budget authority, checks funds, tracks commitments through outlay, derives USSGL budgetary accounts, closes the year, and supports Treasury reporting, with the DoD IG findings that show where it breaks.
11 tables, 2 diagramsSAP expert series, part 4SAP Table Catalog
A searchable catalog of 425 standard SAP tables across Basis, finance, Funds Management, US Federal, controlling, projects, purchasing, inventory, sales, maintenance, real estate, and interfaces, with what each holds and its key fields.
4 tables, 0 diagramsSAP expert series, part 5SAP Transaction Codes
A searchable catalog of 556 SAP transaction codes by area and kind, flagged where the code appears in public GFEBS or GCSS-Army material, plus the documented Army custom transactions.
4 tables, 0 diagramsSAP expert series, part 6SAP Fields and Data Elements
A searchable catalog of 221 SAP fields with type, length, meaning, the tables that carry them, and how each one supports SFIS, SLOA, GTAS, or audit testing.
3 tables, 0 diagramsSAP expert series, part 7SAP Interfaces
Every interface technology an SAP ERP uses, the anatomy and status model of an IDoc, the standard message types and BAPIs behind financial and logistics postings, and what public sources show about the interfaces of each DoD SAP system.
9 tables, 2 diagramsSAP expert series, part 8DoD SAP Systems
Referenced profiles of each DoD system built on SAP: scope, scale, cost, ledger design, line of accounting, document types, custom development, audit findings with numbers, and current modernization status.
8 tables, 1 diagramSystem to platform map
Which reference applies to which system
Each system blueprint page also carries its own numbered table of data objects and join paths.