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.

6

Core DEAMS lineage scenarios

Source -> SLA -> GL -> GTAS

System profile

What it is, who uses it, and why it matters

What it is

DEAMS is the Defense Enterprise Accounting and Management System, modeled here as the Department of the Air Force Oracle-based financial-management environment.

Who uses it

Air Force and Space Force financial managers, resource advisors, budget users, acquisition/payment partners, DFAS and reporting stakeholders, and auditors rely on DEAMS outputs.

How it is used

It supports budget execution, procure-to-pay, travel accounting, reimbursables, cost accounting, assets, SLA, GL, Treasury reporting, and statement support.

Current status

Operational DAF financial-management system; this page uses public information and Oracle federal-financial process patterns rather than claiming exact DEAMS configuration.

Why it is used

It standardizes DAF accounting, connects source events to GL/reporting, and supports auditability across Air Force and Space Force financial operations.

Modeled feeder systems7

The blueprint models 7 major DEAMS feeder/source categories.

DTSWAWF / PIEESPS / EDADCPS / PayrollMission / Logistics SourcesG-Invoicing / IPACTreasury / Disbursing

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.

Source

DAF Source / Feeder Systems

Air Force, Space Force, DFAS, contracting, travel, payroll, logistics, and Treasury-facing systems where financial business events originate.

DEAMS

DEAMS Core Business Processes

Oracle-based federal financial management processes for budget execution, procure-to-pay, reimbursables, cost accounting, assets, and close.

Detail

Detailed Transaction Objects

Document, subledger, interface, and reconciliation records that preserve Universe of Transactions evidence before GL summarization.

Accounting

Accounting Layer

Oracle SLA, USSGL budgetary/proprietary accounting, GL journal lines, account derivation, and drillback controls.

Reporting

Reporting / Treasury Layer

DEAMS reporting, DDRS, GTAS, CARS/FBwT, USSGL crosswalks, G-Invoicing/IPAC, and external reporting outputs.

Statements

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

  1. Requisition demand and contract award/modification evidence establish the procurement requirement.
  2. DEAMS creates PO/agreement lines, shipments, distributions, and budgetary control records.
  3. PIEE/WAWF provides receipt, acceptance, and invoice evidence.
  4. AP validation, matching, holds, approvals, and payment-ready processing create accounting events for SLA.
  5. SLA creates subledger journal entries and transfers supported accounting to GL.
  6. 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.

Open Oracle E-Business Suite reference
Table DEAMS-1DEAMS data objects by area
Table or recordAreaHoldsKey fieldsLinks to
GL_JE_BATCHES / GL_JE_HEADERS / GL_JE_LINESGeneral LedgerJournal batch, header, and linesJE_BATCH_ID, JE_HEADER_ID, JE_LINE_NUMGL_BALANCES; GL_IMPORT_REFERENCES
GL_BALANCESGeneral LedgerPeriod balances by account combinationLEDGER_ID, CODE_COMBINATION_ID, PERIOD_NAME, ACTUAL_FLAGTrial balance extract to DDRS
GL_CODE_COMBINATIONSGeneral LedgerAccount strings: fund, USSGL account, and other segmentsCODE_COMBINATION_IDEvery transaction distribution
GL_IMPORT_REFERENCESGeneral LedgerLink from a journal line to a subledger journal lineJE_HEADER_ID, JE_LINE_NUM, GL_SL_LINK_IDXLA_AE_LINES
XLA_AE_HEADERS / XLA_AE_LINESSubledger AccountingSubledger journal entriesAE_HEADER_ID, AE_LINE_NUMXLA_EVENTS, XLA_TRANSACTION_ENTITIES
XLA_TRANSACTION_ENTITIESSubledger AccountingOne row per accounted transaction, with the source transaction IDENTITY_IDAP_INVOICES_ALL, AP_CHECKS_ALL, RCV_TRANSACTIONS
XLA_DISTRIBUTION_LINKSSubledger AccountingLink from a journal line to one source distributionAE_HEADER_ID, AE_LINE_NUM, SOURCE_DISTRIBUTION_ID_NUM_1AP_INVOICE_DISTRIBUTIONS_ALL
FV_TREASURY_SYMBOLSFederal FinancialsTreasury Account Symbol masterTREASURY_SYMBOL_IDFV_FUND_PARAMETERS
FV_FUND_PARAMETERSFederal FinancialsFund attributes: fund value to TAS and fund categoryFund value, ledgerFund segment of GL_CODE_COMBINATIONS
FV_BE_TRX_HDRS / FV_BE_TRX_DTLSFederal FinancialsBudget execution documents: appropriation, apportionment, allotmentDOC_ID, TRANSACTION_IDSubledger Accounting, then GL
FV_BUDGET_LEVELSFederal FinancialsBudget distribution levelsBUDGET_LEVEL_IDFV_BE_TRX_HDRS
FV_BE_INTERFACEFederal FinancialsOpen interface for funding documents from budget systemsSOURCE, GROUP_ID, RECORD_NUMBERFV_BE_TRX_HDRS
FV_FACTS_ATTRIBUTESFederal FinancialsUSSGL attributes for Treasury reportingAccount and attribute setGTAS bulk file
PO_REQUISITION_HEADERS_ALL / LINES_ALL / PO_REQ_DISTRIBUTIONS_ALLPurchasingRequisitions and their accounting distributionsREQUISITION_HEADER_ID, DISTRIBUTION_IDPO_DISTRIBUTIONS_ALL.REQ_DISTRIBUTION_ID
PO_HEADERS_ALL / PO_LINES_ALL / PO_LINE_LOCATIONS_ALLPurchasingPurchase order header, lines, and shipmentsPO_HEADER_ID, PO_LINE_ID, LINE_LOCATION_IDPO_DISTRIBUTIONS_ALL
PO_DISTRIBUTIONS_ALLPurchasingOrder accounting distributions and encumbrancePO_DISTRIBUTION_IDRCV_TRANSACTIONS, AP_INVOICE_DISTRIBUTIONS_ALL
RCV_TRANSACTIONSReceivingReceive, accept, deliver, returnTRANSACTION_IDPO_DISTRIBUTION_ID
AP_INVOICES_ALL / AP_INVOICE_LINES_ALL / AP_INVOICE_DISTRIBUTIONS_ALLPayablesInvoice header, lines, and distributionsINVOICE_ID, INVOICE_DISTRIBUTION_IDAP_INVOICE_PAYMENTS_ALL
AP_CHECKS_ALL / AP_INVOICE_PAYMENTS_ALLPayablesPayments and the invoices each one paidCHECK_ID, INVOICE_PAYMENT_IDFV_TREASURY_CONFIRMATIONS_ALL
AP_INVOICES_INTERFACEPayablesStaging for invoices from WAWF and other feedersInterface INVOICE_IDAP_INVOICES_ALL
RA_CUSTOMER_TRX_ALL / RA_CUSTOMER_TRX_LINES_ALLReceivablesCustomer invoices, including reimbursable billingsCUSTOMER_TRX_IDAR_PAYMENT_SCHEDULES_ALL
AR_CASH_RECEIPTS_ALLReceivablesReceipts and collectionsCASH_RECEIPT_IDAR_RECEIVABLE_APPLICATIONS_ALL
PA_PROJECTS_ALL / PA_TASKS / PA_EXPENDITURE_ITEMS_ALLProjectsProjects, tasks, and cost transactionsPROJECT_ID, TASK_ID, EXPENDITURE_ITEM_IDPA_COST_DISTRIBUTION_LINES_ALL
FA_ADDITIONS_B / FA_BOOKS / FA_DEPRN_SUMMARYAssetsAsset master, financial rules, depreciationASSET_ID, BOOK_TYPE_CODEFA_DISTRIBUTION_HISTORY

Join paths for tracing a balance to its source

  1. 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.
  2. 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.
  3. Invoice to obligation: AP_INVOICE_DISTRIBUTIONS_ALL.PO_DISTRIBUTION_ID equals PO_DISTRIBUTIONS_ALL.PO_DISTRIBUTION_ID.
  4. Obligation to commitment: PO_DISTRIBUTIONS_ALL.REQ_DISTRIBUTION_ID equals PO_REQ_DISTRIBUTIONS_ALL.DISTRIBUTION_ID.
  5. Account to Treasury symbol: fund segment of GL_CODE_COMBINATIONS to FV_FUND_PARAMETERS, then to FV_TREASURY_SYMBOLS.
  6. 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.