DoD SAP Systems Profiled: GFEBS, GCSS-Army, LMP, Navy ERP, DLA EBS, and EBS-C

1. The DoD SAP portfolio at a glance

2. GFEBS

Purpose and history

• GFEBS is the Army General Fund accounting system. DoD IG describes it as a web-based ERP built by a contractor on a commercial off-the-shelf platform to standardize Army financial management, accounting, asset inventory, and asset management.
• Deployment ran from 2008 to July 1, 2012. In September 2010 it had about 8,700 users at 14 locations and handled under 2 percent of Army General Fund obligations. By June 2011 it had about 24,000 users at 105 locations.
• A separate instance, GFEBS-Sensitive Activities, executes classified activity. DoD IG lists it with GCSS-Army and the Corps of Engineers system among the systems that execute Army General Fund amounts outside GFEBS.
• The Army reported moving GFEBS to a commercial cloud ahead of schedule. The Army began streaming GFEBS transactions to Advana in 2023.
• In fiscal year 2013, only $129.2 billion of $266.5 billion in Army General Fund total budgetary resources, 48.5 percent, originated in GFEBS. Prior-year funding had stayed in legacy systems.

Business process areas

Line of accounting

Document types and workflow

Custom development

The public role-to-transaction mapping names more than 90 custom transactions. They cluster around five needs that the standard product does not meet for the Army: status of funds reporting in Army terms, the DDRS and SFIS trial balance extracts, cash reconciliation with the DFAS cash accountability system, federal forms such as the DD Form 448, DD Form 1354, SF 1080, and SF 1081, and interface error work lists. The full list by family is on the transaction code catalog page.

Audit findings with numbers

3. The Army ERP federation

GCSS-Army

• GCSS-Army replaced the Standard Army Retail Supply System, the Property Book Unit Supply Enhanced system, and the Standard Army Maintenance System-Enhanced, plus two tactical financial systems: the Single Stock Fund Middleware and the Funds Control Module.
• DOT&E describes it as built from commercial software adapted from a commercial ERP, with a production server at Redstone Arsenal and a continuity server at Radford. It supports tactical maintenance, materiel management, property accountability, tactical financial management, and logistics planning.
• The public maintenance transaction reference shows standard Plant Maintenance, inventory, purchasing, and time sheet transactions, Defense Forces transactions in the /ISDFPS/ namespace, and Army custom reports.
• Material requirements planning runs by MRP area for shop and bench stock, according to the custom transaction names in that reference.
• DoD IG lists GCSS-Army as the system that executes standard stock procurement for the Army General Fund.

AESIP

• The Army Enterprise Systems Integration Program is part of the GCSS-Army program. DOT&E states that it provides enterprise hub services, centralized master data management, and cross-functional business intelligence and analytics for the Army ERPs, including GFEBS and LMP.
• In SAP terms a hub of this kind distributes material, vendor, customer, and organizational master data to each ERP and brokers messages between them.

LMP

• DoD IG identifies LMP as SAP commercial off-the-shelf software for integrated logistics management: supply, demand, asset availability, distribution, financial control, and reporting.
• It was first deployed in 2003 and replaced two legacy national-level systems. It had 21,000 users in 2012.
• LMP carries the Army Working Capital Fund general ledger. Depot maintenance, arsenals, and wholesale supply run in it.
• In July 2025 the Army released an interface from the Army Contract Writing System to LMP for working capital fund purchases. Phase two, expected October 2025, was to add general fund and customer fund execution.

EBS-C

4. Navy ERP

• DoD IG describes Navy ERP as a mixed system classified under logistics that also processes budgeting and accounting transactions to prepare Navy General Fund and Navy Working Capital Fund statements.
• Six commands use it: Naval Air Systems Command, Naval Supply Systems Command, Naval Sea Systems Command, the Office of Naval Research, Strategic Systems Programs, and Naval Information Warfare Systems Command.
• In 2012 the Navy decided not to deploy it to more commands, citing cost, lack of standardization, and 255 audit-related problems. Other commands stayed on other systems.
• DODIG-2013-105 found that Navy ERP did not support $416 billion in military equipment assets reported through DDRS-AFS.
• In August 2019 the Navy completed a move of Navy ERP to SAP HANA in the cloud for about 72,000 users in 10 months against a 20-month plan. The stated next goal was to consolidate Navy financial systems into a single general ledger.
• DoD IG reported that the Navy legacy accounting system retired in December 2022 and its data moved to three systems.

5. DLA Enterprise Business System

• DLA began EBS in August 2000 as Business System Modernization, covering order fulfillment, supply and demand planning, procurement, technical quality, and finance. Core deployment finished in September 2007.
• Later releases added SAP Public Sector finance as the Enterprise Operational Accounting System in May 2010, inventory management and stock positioning from 2009 to 2011, real property in 2009 and 2011, eProcurement in December 2012, and Energy Convergence for fuel supply chains.
• EBS is the DLA general ledger of record. DFAS Columbus uses its data to produce DLA statements and report to DDRS.
• In fiscal year 2012 DLA processed most of more than $53.9 billion in budgetary authority through EBS. It was to manage nearly 5 million items across eight supply chains.
• DoD IG found that accounts receivable used 13 posting accounts crosswalked to a single DoD reporting account, that EBS did not separately record federal and nonfederal payables, and that advances in account 1410 did not agree with prepaid undelivered orders in account 4802.
• Trading partner data was unusable for eliminations: of seven posting accounts with a federal indicator, three reported a zero, two reported a two-digit code, and two reported no value.

6. What the profiles have in common