DLA EBS blueprint for supply-chain finance and working-capital reporting

DLA EBS / Enterprise Business System Blueprint

Explore DLA EBS as the Defense Logistics Agency enterprise business system for global supply-chain finance, connecting FedMall, DAAS/DLMS, PIEE/WAWF, DIBBS, VSM, WebFLIS/FED LOG, DSS, ERP logistics, inventory valuation, AP, AR, GL, Treasury reporting, and statement support.

Explore blueprint Open lineage explorer Data model and tables

Core DLA EBS lineage scenarios

Demand -> EBS -> Inventory/GL -> Statement

System profile

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

What it is

DLA EBS is modeled as the Defense Logistics Agency enterprise business system and supply-chain finance backbone, with a public BSM commercial ERP modernization lineage.

Who uses it

DLA supply chains, DLA Finance, DLA Distribution, DLA Energy, Troop Support, Weapons Support, Disposition Services, vendors, customers, DFAS/reporting partners, and auditors rely on EBS data or outputs.

How it is used

It supports demand, customer orders, procurement, inventory, warehouse/distribution, vendor shipment, AP, AR, working-capital cost recovery, GL, reporting, and audit traceability.

Current status

Operational DLA enterprise environment in this model; DLA public pages show the surrounding application ecosystem, while exact current EBS modules and custom interfaces require DLA authority.

Why it is used

It integrates DLA logistics and finance so global supply-chain events can be controlled, fulfilled, valued, billed, reported, and audited from source transaction to statement.

Modeled feeder systems6

The blueprint models 6 major DLA EBS feeder/source categories from the public DLA application ecosystem; authoritative interface counts require DLA documentation.

FedMall / EEBPDAAS / DLMS / MILSPIEE / WAWFDIBBS / VSMWebFLIS / FED LOG / CatalogingDSS / Distribution / Depot Events

Search architecture

Lineage scenario

Clickable architecture map

End-to-end flow: business event to financial statement

Cards in the selected DLA EBS scenario path are highlighted. Click any card to inspect fields, T-codes, audit questions, and risks.

Source

DLA Source / Customer / Partner Applications

DLA portals, ordering, cataloging, procurement, distribution, logistics-transaction, vendor, invoice, and customer systems that originate business events.

EBS

DLA EBS Core ERP Capabilities

Commercial ERP-style supply-chain and financial capabilities for demand, sales orders, procurement, inventory, warehouse, finance, cost, and replenishment processing.

Detail

Supply-Chain / Subsidiary Detail

Material master, NSN, vendor, customer, order, inventory, shipment, contract, receipt, invoice, and supply-chain segment detail used for traceability.

Accounting

Accounting Layer

AP, AR, inventory valuation, cost of goods, budgetary/proprietary USSGL, GL, adjustments, and close accounting.

Reporting

Reporting / Treasury Layer

EBS reports, EA2 analytics, DDRS, GTAS, Treasury/CARS/FBwT, IPAC/G-Invoicing, audit extracts, and DLA management reporting.

Statements

DLA / DoD Statement Support

Working capital fund, inventory, AP, AR, net cost, SBR, Balance Sheet, note schedules, and audit-support reporting.

Selected layer

WEB FedMall / EEBP

Customer ordering and external business portal

What it does

Provides customer ordering, supplier access, requisition research, tracking, and external business portal activity that can initiate demand, sales-order, fulfillment, and billing processes.

Example transactions / objects

customer order
catalog search
supplier portal action
order tracking
status inquiry

Key fields for UoT traceability

order numbercustomer DoDAACNSNquantityfund codeprioritystatus

Audit questions

Does each customer demand trace to an EBS order or requisition event?
Are customer identities and DoDAACs valid?
Do portal statuses reconcile to EBS fulfillment and billing?

Common risk signals

customer order not accepted by EBS
invalid DoDAAC/fund code
portal status not reconciled
duplicate demand

Scenario lineage explorer

DLA Customer Order to Cash Path

Shows how customer demand flows from FedMall/DAAS through EBS order management, fulfillment, billing, AR, collections, reporting, and statement support.

Business flow

A customer order or requisition is submitted through a DLA portal or logistics transaction channel.
EBS validates customer, DoDAAC, NSN, priority, fund, and availability data.
Warehouse or distribution activity fulfills the order through pick, pack, ship, and status updates.
Billing and AR records are created and later settled through collection or offset.
Reporting and working-capital statements tie fulfillment, revenue, cost, and receivable balances back to source events.

AI / audit exception tests

customer demand not accepted by EBS
shipment without billing
billing without shipment
collection not applied
AR aging unsupported

Data model and tables

Where DLA EBS data lives and how the pieces join

Standard SAP product tables. Custom Z-tables, enhancements, and the exact module scope of this program are not public. Confirm in the program data dictionary.

Open SAP ERP reference

Table DLA EBS-1DLA EBS data objects by area

Table or record	Area	Holds	Key fields	Links to
`VBAK / VBAP`	Sales	Sales order header and items, used for reimbursable and customer orders	VBELN, POSNR	VBFA
`VBRK / VBRP`	Billing	Billing document header and items	VBELN, POSNR	BKPF-AWKEY
`VBFA`	Sales	Document flow from order to delivery to bill	VBELV, POSNV, VBELN, POSNN	LIKP, VBRK
`LIKP / LIPS`	Shipping	Delivery header and items	VBELN, POSNR	VBFA, MSEG
`MARA / MARC / MARD`	Material master	Material general data, plant data, storage location stock	MATNR, WERKS, LGORT	MSEG
`MBEW`	Valuation	Material valuation: price control, moving average or standard price, stock value	MATNR, BWKEY, BWTAR	Inventory GL accounts
`EKKO / EKPO`	Purchasing	Purchase order header and items	EBELN, EBELP	EKKN, EKBE
`EKKN`	Purchasing	Purchase order account assignment: GL account, cost object, fund	EBELN, EBELP, ZEKKN	FMIOI
`EKBE`	Purchasing	Purchase order history: goods receipts and invoice receipts	EBELN, EBELP, VGABE, GJAHR, BELNR	MSEG, RSEG
`MKPF / MSEG`	Inventory	Material document header and items. MATDOC in S/4HANA.	MBLNR, MJAHR, ZEILE	BKPF-AWKEY
`RBKP / RSEG`	Invoice verification	Logistics invoice header and items	BELNR, GJAHR	BKPF-AWKEY
`REGUH / REGUP`	Payments	Payment run header and paid items	LAUFD, LAUFI, VBLNR	BSAK cleared items
`BKPF`	Finance	Accounting document header	BUKRS, BELNR, GJAHR	BSEG; source object through AWTYP and AWKEY
`BSEG`	Finance	Accounting document line items with all account assignments	BUKRS, BELNR, GJAHR, BUZEI	FAGLFLEXA or ACDOCA; FMIFIIT through KNBELNR
`FAGLFLEXA / FAGLFLEXT`	Finance	New GL line items and totals by ledger. ACDOCA replaces both in S/4HANA.	RLDNR, RBUKRS, RYEAR, DOCNR, DOCLN	Trial balance extract to DDRS
`SKA1 / SKB1`	Finance	GL account master holding the DoD Standard Chart of Accounts	KTOPL, SAKNR / BUKRS, SAKNR	BSEG-HKONT

Join paths for tracing a balance to its source

Customer order to bill: VBAK to LIKP to VBRK through VBFA.
Bill to revenue and receivable: VBRK to BKPF through AWKEY, open items in BSID.
Supplier order to payment: EKKO to EKBE to RBKP to REGUP.
Inventory value: MARD and MBEW, agreed to inventory GL accounts.

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

DLA Mission Context

DLA manages the end-to-end global defense supply chain across military services, combatant commands, federal agencies, partners, and allied nations.

ERP Platform Profile

Modeled as DLA EBS with a BSM commercial ERP modernization lineage and SAP-style process/tables where public sources support an ERP interpretation; exact configuration requires DLA authority.

Data Standards & DAAS

DLMS, MILS, DAAS routing, DoDAAC, fund code, NSN, CAGE, and logistics data standards connect operational logistics transactions to financial consequences.

Master Data Governance

NSN/material, vendor, customer, catalog, plant/storage, condition, valuation class, fund, TAS, USSGL, and trading-partner values drive traceability.

Close & Reporting

Subledger-to-GL tie-outs, inventory valuation reconciliations, AP/AR aging, ATB, DDRS, GTAS, Treasury/FBwT, and statement package controls.

Audit Evidence

Customer orders, DLMS messages, catalog records, POs, receipts, WAWF invoices, warehouse movements, shipments, GL documents, extracts, and reconciliations.