GCSS-MC is modeled as the Marine Corps Global Combat Support System used for logistics support processes such as supply, maintenance, property accountability, inventory, and readiness-related data.
GCSS-MC blueprint for Marine Corps logistics-to-finance lineage
GCSS-MC / Global Combat Support System-Marine Corps Blueprint
Explore GCSS-MC as a Marine Corps logistics support and business-process backbone for supply, maintenance, property accountability, inventory, readiness, finance handoff, and audit evidence without overclaiming the public technical stack.
4
Core GCSS-MC lineage scenarios
Unit logistics -> Finance -> StatementSystem profile
What it is, who uses it, and why it matters
Marine Corps supply, maintenance, responsible-officer/property, logistics command, MAGTF support, finance-interface, reporting, program-support, and audit stakeholders rely on GCSS-MC records or outputs.
It supports Marine Corps requisitions, receipts, issues, maintenance work orders, equipment status, inventory/accountable property, logistics reporting, finance handoff, and evidence retention.
Public platform details are limited; this model treats GCSS-MC as an operational Marine Corps logistics business system and marks exact modules, stack, and interfaces as requiring Marine Corps authority.
It gives Marine Corps units and logisticians a controlled transaction trail for mission logistics, readiness visibility, property accountability, and source evidence needed for finance and audit support.
The blueprint models 5 major GCSS-MC source/partner categories; this is not a certified production interface count.
Marine Unit Supply / Warehouse InputsMaintenance ShopsResponsible Officer / Property InputsDLA / DAAS / DLMS / FED LOGSABRS / DoN Finance / DFAS Partners
Clickable architecture map
End-to-end flow: business event to financial statement
Cards in the selected GCSS-MC scenario path are highlighted. Click any card to inspect fields, T-codes, audit questions, and risks.
Source
Unit / Logistics / Partner Source Events
Unit supply, maintenance, property, catalog, distribution, vendor, and finance partner events that originate before GCSS transaction control.
GCSS
GCSS Core Logistics Capabilities
Supply, maintenance, property, inventory, and readiness capabilities that control operational logistics activity before financial impact is summarized or interfaced.
Detail
Logistics Transaction Detail
Document-level logistics objects used to preserve the Universe of Transactions for material, requisition, work-order, asset, and inventory activity.
Finance
Financial Impact / Interface Layer
Budgetary, cost, inventory valuation, reimbursable, AP, and GL-facing activity exchanged with financial-management systems.
Reporting
Readiness, ERP, and Treasury Reporting
Operational readiness, logistics status, ERP extracts, trial-balance support, DDRS, GTAS, and reconciliation outputs.
Statements
Financial Statement Assertions
Statement line items and audit assertions supported by logistics-to-finance lineage, reconciliations, and retained evidence.
Scenario lineage explorer
Supply Requisition to Finance Posting
Traces a funded supply request from unit demand through GCSS supply execution, document detail, finance interface, and SBR support.
->
->
->
->
->
Business flow
- A unit or supply activity creates a mission-supported demand with document number, item, quantity, priority, and funding data.
- GCSS controls request status, sourcing, issue, receipt, backorder, cancellation, or turn-in activity.
- The requisition detail preserves the transaction population and status history for audit sampling.
- Finance-facing signals are exchanged with the applicable accounting system and reconciled by batch, count, amount, and period.
- Budgetary reporting ties obligations, delivered orders, outlays, and ULO review back to source demand evidence.
AI / audit exception tests
- invalid fund cite
- open requisition aged past policy
- interface reject
- finance posting without GCSS detail
- manual journal missing source support
Data model and tables
Where GCSS-MC 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 |
|---|---|---|---|---|
MTL_SYSTEM_ITEMS_B | Inventory | Item master | INVENTORY_ITEM_ID, ORGANIZATION_ID | MTL_MATERIAL_TRANSACTIONS |
MTL_MATERIAL_TRANSACTIONS | Inventory | Every stock movement | TRANSACTION_ID | MTL_TRANSACTION_ACCOUNTS |
MTL_ONHAND_QUANTITIES_DETAIL | Inventory | On-hand quantity by location | ONHAND_QUANTITIES_ID | Inventory valuation |
OE_ORDER_HEADERS_ALL / OE_ORDER_LINES_ALL | Order Management | Supply requests and orders | HEADER_ID, LINE_ID | Shipping and receiving |
PO_HEADERS_ALL / PO_DISTRIBUTIONS_ALL | Purchasing | Purchase orders and their accounting | PO_HEADER_ID, PO_DISTRIBUTION_ID | RCV_TRANSACTIONS |
RCV_TRANSACTIONS | Receiving | Receipts and deliveries | TRANSACTION_ID | MTL_MATERIAL_TRANSACTIONS |
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 |
Join paths for tracing a balance to its source
- Stock movement to accounting: MTL_MATERIAL_TRANSACTIONS to MTL_TRANSACTION_ACCOUNTS on TRANSACTION_ID.
- Receipt to order: RCV_TRANSACTIONS.PO_DISTRIBUTION_ID to PO_DISTRIBUTIONS_ALL.
- Logistics event to the Marine Corps ledger: subledger journal in the XLA tables, then the interface to the accounting system.
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
Supply and Maintenance Controls
Demand validation, document-number control, work-order support, issue/receipt status, cancellation rules, and aged open-transaction review.
Property and Inventory Governance
Custody, serial-number control, location, condition, inventory count, adjustment approval, valuation support, and loss/disposal evidence.
Interface and Reconciliation
DLMS/partner exchange, finance-interface batch controls, reject/suspense resolution, period cutoff, control totals, and source-to-posting tie-outs.
Readiness and Command Reporting
Equipment status, open parts demand, maintenance backlog, mission-readiness exception reporting, as-of-date control, and report population ownership.
Financial Reporting Support
USSGL/TAS mapping where applicable, SBR support, inventory/OM&S/PP&E assertions, net cost, DDRS/GTAS tie-outs, and audit schedules.
Master Data and Evidence
NSN/material, DoDAAC/UIC/RIC, fund cite, unit price, condition code, equipment, custodian, document number, and retained sample-support packages.