DEAMS is the Defense Enterprise Accounting and Management System, modeled here as the Department of the Air Force Oracle-based financial-management environment.
DEAMS blueprint for Air Force and Space Force financial management
DEAMS / Defense Enterprise Accounting and Management System Blueprint
Explore DEAMS as a representative Oracle-based Department of the Air Force financial-management system, connecting DAF source systems, procure-to-pay, reimbursables, cost accounting, assets, SLA, GL, Treasury reporting, and statement support.
Core DEAMS lineage scenarios
Source -> SLA -> GL -> GTASSystem profile
What it is, who uses it, and why it matters
Air Force and Space Force financial managers, resource advisors, budget users, acquisition/payment partners, DFAS and reporting stakeholders, and auditors rely on DEAMS outputs.
It supports budget execution, procure-to-pay, travel accounting, reimbursables, cost accounting, assets, SLA, GL, Treasury reporting, and statement support.
Operational DAF financial-management system; this page uses public information and Oracle federal-financial process patterns rather than claiming exact DEAMS configuration.
It standardizes DAF accounting, connects source events to GL/reporting, and supports auditability across Air Force and Space Force financial operations.
The blueprint models 7 major DEAMS feeder/source categories.
Clickable architecture map
End-to-end flow: business event to financial statement
Cards in the selected DEAMS scenario path are highlighted. Click any card to inspect fields, T-codes, audit questions, and risks.
DAF Source / Feeder Systems
Air Force, Space Force, DFAS, contracting, travel, payroll, logistics, and Treasury-facing systems where financial business events originate.
DEAMS Core Business Processes
Oracle-based federal financial management processes for budget execution, procure-to-pay, reimbursables, cost accounting, assets, and close.
Detailed Transaction Objects
Document, subledger, interface, and reconciliation records that preserve Universe of Transactions evidence before GL summarization.
Accounting Layer
Oracle SLA, USSGL budgetary/proprietary accounting, GL journal lines, account derivation, and drillback controls.
Reporting / Treasury Layer
DEAMS reporting, DDRS, GTAS, CARS/FBwT, USSGL crosswalks, G-Invoicing/IPAC, and external reporting outputs.
DAF / DoD Financial Statements
Department of the Air Force and DoD statement outputs supported by reconciled trial balances, note schedules, and audit evidence.
Scenario lineage explorer
Requisition -> Award -> Receipt -> Invoice -> Payment
Shows how DAF procurement activity moves from demand and award evidence through DEAMS purchasing, AP, SLA, GL, reporting, and statement support.
Business flow
- Requisition demand and contract award/modification evidence establish the procurement requirement.
- DEAMS creates PO/agreement lines, shipments, distributions, and budgetary control records.
- PIEE/WAWF provides receipt, acceptance, and invoice evidence.
- AP validation, matching, holds, approvals, and payment-ready processing create accounting events for SLA.
- SLA creates subledger journal entries and transfers supported accounting to GL.
- Trial balance, GTAS, and statement lines rely on supported AP, expense, asset, and outlay populations.
AI / audit exception tests
- award without obligation
- invoice without receipt or acceptance
- SLA event not accounted
- payment without AP support
- subledger-to-GL transfer mismatch
Data model and tables
Where DEAMS data lives and how the pieces join
Standard Oracle E-Business Suite product tables. Program-specific extensions and descriptive flexfield usage are not public. Confirm in the eTRM for the release in use.
| Table or record | Area | Holds | Key fields | Links to |
|---|---|---|---|---|
GL_JE_BATCHES / GL_JE_HEADERS / GL_JE_LINES | General Ledger | Journal batch, header, and lines | JE_BATCH_ID, JE_HEADER_ID, JE_LINE_NUM | GL_BALANCES; GL_IMPORT_REFERENCES |
GL_BALANCES | General Ledger | Period balances by account combination | LEDGER_ID, CODE_COMBINATION_ID, PERIOD_NAME, ACTUAL_FLAG | Trial balance extract to DDRS |
GL_CODE_COMBINATIONS | General Ledger | Account strings: fund, USSGL account, and other segments | CODE_COMBINATION_ID | Every transaction distribution |
GL_IMPORT_REFERENCES | General Ledger | Link from a journal line to a subledger journal line | JE_HEADER_ID, JE_LINE_NUM, GL_SL_LINK_ID | XLA_AE_LINES |
XLA_AE_HEADERS / XLA_AE_LINES | Subledger Accounting | Subledger journal entries | AE_HEADER_ID, AE_LINE_NUM | XLA_EVENTS, XLA_TRANSACTION_ENTITIES |
XLA_TRANSACTION_ENTITIES | Subledger Accounting | One row per accounted transaction, with the source transaction ID | ENTITY_ID | AP_INVOICES_ALL, AP_CHECKS_ALL, RCV_TRANSACTIONS |
XLA_DISTRIBUTION_LINKS | Subledger Accounting | Link from a journal line to one source distribution | AE_HEADER_ID, AE_LINE_NUM, SOURCE_DISTRIBUTION_ID_NUM_1 | AP_INVOICE_DISTRIBUTIONS_ALL |
FV_TREASURY_SYMBOLS | Federal Financials | Treasury Account Symbol master | TREASURY_SYMBOL_ID | FV_FUND_PARAMETERS |
FV_FUND_PARAMETERS | Federal Financials | Fund attributes: fund value to TAS and fund category | Fund value, ledger | Fund segment of GL_CODE_COMBINATIONS |
FV_BE_TRX_HDRS / FV_BE_TRX_DTLS | Federal Financials | Budget execution documents: appropriation, apportionment, allotment | DOC_ID, TRANSACTION_ID | Subledger Accounting, then GL |
FV_BUDGET_LEVELS | Federal Financials | Budget distribution levels | BUDGET_LEVEL_ID | FV_BE_TRX_HDRS |
FV_BE_INTERFACE | Federal Financials | Open interface for funding documents from budget systems | SOURCE, GROUP_ID, RECORD_NUMBER | FV_BE_TRX_HDRS |
FV_FACTS_ATTRIBUTES | Federal Financials | USSGL attributes for Treasury reporting | Account and attribute set | GTAS bulk file |
PO_REQUISITION_HEADERS_ALL / LINES_ALL / PO_REQ_DISTRIBUTIONS_ALL | Purchasing | Requisitions and their accounting distributions | REQUISITION_HEADER_ID, DISTRIBUTION_ID | PO_DISTRIBUTIONS_ALL.REQ_DISTRIBUTION_ID |
PO_HEADERS_ALL / PO_LINES_ALL / PO_LINE_LOCATIONS_ALL | Purchasing | Purchase order header, lines, and shipments | PO_HEADER_ID, PO_LINE_ID, LINE_LOCATION_ID | PO_DISTRIBUTIONS_ALL |
PO_DISTRIBUTIONS_ALL | Purchasing | Order accounting distributions and encumbrance | PO_DISTRIBUTION_ID | RCV_TRANSACTIONS, AP_INVOICE_DISTRIBUTIONS_ALL |
RCV_TRANSACTIONS | Receiving | Receive, accept, deliver, return | TRANSACTION_ID | PO_DISTRIBUTION_ID |
AP_INVOICES_ALL / AP_INVOICE_LINES_ALL / AP_INVOICE_DISTRIBUTIONS_ALL | Payables | Invoice header, lines, and distributions | INVOICE_ID, INVOICE_DISTRIBUTION_ID | AP_INVOICE_PAYMENTS_ALL |
AP_CHECKS_ALL / AP_INVOICE_PAYMENTS_ALL | Payables | Payments and the invoices each one paid | CHECK_ID, INVOICE_PAYMENT_ID | FV_TREASURY_CONFIRMATIONS_ALL |
AP_INVOICES_INTERFACE | Payables | Staging for invoices from WAWF and other feeders | Interface INVOICE_ID | AP_INVOICES_ALL |
RA_CUSTOMER_TRX_ALL / RA_CUSTOMER_TRX_LINES_ALL | Receivables | Customer invoices, including reimbursable billings | CUSTOMER_TRX_ID | AR_PAYMENT_SCHEDULES_ALL |
AR_CASH_RECEIPTS_ALL | Receivables | Receipts and collections | CASH_RECEIPT_ID | AR_RECEIVABLE_APPLICATIONS_ALL |
PA_PROJECTS_ALL / PA_TASKS / PA_EXPENDITURE_ITEMS_ALL | Projects | Projects, tasks, and cost transactions | PROJECT_ID, TASK_ID, EXPENDITURE_ITEM_ID | PA_COST_DISTRIBUTION_LINES_ALL |
FA_ADDITIONS_B / FA_BOOKS / FA_DEPRN_SUMMARY | Assets | Asset master, financial rules, depreciation | ASSET_ID, BOOK_TYPE_CODE | FA_DISTRIBUTION_HISTORY |
Join paths for tracing a balance to its source
- GL line to subledger: GL_JE_LINES to GL_IMPORT_REFERENCES on JE_HEADER_ID and JE_LINE_NUM, then to XLA_AE_LINES on GL_SL_LINK_ID.
- Subledger entry to transaction: XLA_AE_HEADERS to XLA_TRANSACTION_ENTITIES on ENTITY_ID. SOURCE_ID_INT_1 is the invoice, payment, or receipt ID.
- Invoice to obligation: AP_INVOICE_DISTRIBUTIONS_ALL.PO_DISTRIBUTION_ID equals PO_DISTRIBUTIONS_ALL.PO_DISTRIBUTION_ID.
- Obligation to commitment: PO_DISTRIBUTIONS_ALL.REQ_DISTRIBUTION_ID equals PO_REQ_DISTRIBUTIONS_ALL.DISTRIBUTION_ID.
- Account to Treasury symbol: fund segment of GL_CODE_COMBINATIONS to FV_FUND_PARAMETERS, then to FV_TREASURY_SYMBOLS.
- Trial balance: GL_BALANCES joined to GL_CODE_COMBINATIONS with ACTUAL_FLAG A, and agreed to posted GL_JE_LINES.
Audit lens
Where the AI UoT analyzer should watch
These are the places where completeness, accuracy, timeliness, and traceability commonly break.
Completeness
Source events missing from the ERP, subledger items not posted to GL, or financial statement balances without supporting populations.
Traceability
Broken reference keys across feeder, interface, subledger object, GL document, trial balance, and statement line item.
Timing
Authorization, receipt, invoice, voucher, payment, and GL posting dates crossing accounting periods without appropriate accrual or adjustment.
Supportability
Transactions posted to GL without valid approval, contract, receipt, invoice, voucher, asset record, or other audit evidence.
Enterprise infrastructure
Support services that make the blueprint work
Oracle Master Data
Suppliers, customers, organizations, projects, programs, funds, accounts, assets, and DAF accounting strings.
Interfaces & Controls
Batch files, APIs, accepted/rejected records, control totals, suspense/error queues, and source-to-target reconciliation.
Workflow & Approvals
Requisition, purchase, invoice, journal, travel, reimbursable, asset, and close-adjustment approval routing.
Security & Access
Role-based access, segregation of duties, privileged access, system audit logs, and sensitive transaction monitoring.
Period Close
Interface resolution, subledger close, GL close, reconciliations, trial-balance extracts, and reporting package controls.
Data Governance
Authoritative sources, data definitions, SFIS/USSGL attributes, lineage, validation rules, stewardship, and issue remediation.
Modernization
Cloud hosting, integration modernization, reporting automation, audit analytics, and AI-enabled UoT testing.