Navy ERP — Navy Enterprise Resource Planning

Navy ERP (Navy Enterprise Resource Planning) is the Department of the Navy's SAP-based business system of record for financial management and supply-chain, acquisition, and maintenance management. It is a single, integrated instance of commercial SAP software through which the Navy's major commands — NAVAIR, NAVSEA, NAVWAR (formerly SPAWAR), NAVSUP, the Office of Naval Research, and Strategic Systems Programs — budget, account for, requisition, and audit a large share of the Navy's resources. Where older Navy business processes ran in dozens of separate, single-purpose accounting and supply applications, Navy ERP put finance and supply in one system so a material transaction and its financial effect are recorded together. It is developed and sustained by NAVSUP Business Systems Center (NAVSUP BSC) in Mechanicsburg, Pennsylvania, and managed as an acquisition program under the Program Executive Office for Manpower, Logistics and Business Solutions (PEO MLB) — specifically its Navy Enterprise Business Solutions (Navy EBS) program office. This page is the canonical reference for what Navy ERP is, the business areas it runs, its long and well-documented history, how it replaced legacy systems, the Navy supply reference data it carries, and how access works.

At a glance

• What it is: The Navy's integrated, SAP-based enterprise system for financial, supply-chain, acquisition, and maintenance management — the Department of the Navy's financial system of record for the transactions it carries.
• Built on: Commercial off-the-shelf SAP software (historically the SAP Business Suite on NetWeaver), running on the SAP HANA in-memory platform in the cloud since 2019.
• Operated/developed by: NAVSUP Business Systems Center (NAVSUP BSC), Mechanicsburg, PA, under Naval Supply Systems Command (NAVSUP).
• Acquisition program management: Program Executive Office for Manpower, Logistics and Business Solutions (PEO MLB), through its Navy Enterprise Business Solutions (Navy EBS) program office.
• Used by: Originally six systems commands — NAVAIR, NAVSEA, NAVWAR (formerly SPAWAR), NAVSUP and its Fleet Logistics Centers, ONR, and SSP — and, following the January 2026 fleet migration (U.S. Fleet Forces Command, U.S. Pacific Fleet, Navy Reserve Forces Command), nearly 100,000 users worldwide.
• Access: Authenticated DoD business system; CAC plus an approved, role-based account. Not public.
• Reference data it carries: Navy master cognizance (COG) and stock-location (SLOC) supply-management reference data; see the Navy Cognizance Symbols (COG Codes) reference.

What it is

Navy ERP is an integrated business system, not a single-function tool. The phrase "enterprise resource planning" describes a class of commercial software — pioneered by vendors such as SAP — that runs an organization's core back-office processes (finance, supply, procurement, maintenance, human resources) in one shared database so the processes connect to each other instead of being copied between separate applications. Navy ERP is the Department of the Navy's implementation of that idea on SAP software.

Concretely, Navy ERP is the financial system of record for the budgets and transactions it carries: the authoritative ledger that Navy leadership relies on for the accounts in the system. It is simultaneously a supply-chain and materials-management system, a acquisition and project-financial system, and a maintenance and workforce system. The defining feature is integration — the same transaction that issues a part also records its financial effect, because finance and supply share one system rather than reconciling between two.

It is governed by Department of the Navy financial-management and supply policy and sits inside the DoD's broader business-systems-modernization framework — which is why so much of its public documentation comes from oversight bodies (GAO and DOT&E) rather than only from the program itself.

Why it exists

Before Navy ERP, the Navy's business processes ran in a sprawl of separate, single-purpose legacy systems — many command-specific, many decades old, frequently duplicating the same transaction in incompatible ways and unable to give leadership a consolidated, auditable view of money and materiel. The federal push for financial auditability made that fragmentation untenable: an organization cannot pass a financial audit when its records live in dozens of disconnected ledgers that do not reconcile.

Navy ERP exists to solve that with one integrated system of record. The goals are consistent across the program's documentation: integrate finance and supply so they are managed together; standardize the Navy's acquisition, financial, supply, maintenance, and workforce business processes across commands that historically each did things their own way; retire the costly legacy applications; and produce an auditable system of record that supports the Department of the Navy's drive toward a clean financial-audit opinion.

That single-system, integrated-finance-and-supply ambition is exactly what made the program large and hard — and is also why it matters to logisticians: a very large share of the Navy's budget and supply activity is executed inside it. As the Navy's financial system of record, Navy ERP manages roughly 56% of the Navy's total obligation authority and facilitates more than $145 billion in financial transactions each year, and — following the January 2026 completion of the fleet migration described below — supports nearly 100,000 users.

History and lineage

Navy ERP has one of the most extensively documented histories of any DoD business system, because oversight agencies tracked it closely.

• The four pilots (late 1990s–early 2000s). The Navy did not start with one ERP; it started with four separate SAP ERP pilot projects, one at each major systems command:

  • SMART — Naval Supply Systems Command (NAVSUP)
  • SIGMA — Naval Air Systems Command (NAVAIR)
  • NEMAIS — Naval Sea Systems Command (NAVSEA)
  • CABRILLO — Space and Naval Warfare Systems Command (SPAWAR)

  The pilots went live in the early 2000s (Cabrillo in 2001, NEMAIS in 2002, SIGMA in 2002, SMART in 2003).

• The $1B finding and convergence (mid-2000s). The Government Accountability Office reported that the Navy had spent roughly $1 billion on the four pilots and concluded they were redundant, incompatible, and limited in scope. The Navy consolidated them into a single converged program — the Navy ERP that exists today — and GAO publicly warned the converged effort to adhere to best business practices "to avoid past failures."

• Template 1 and the converged releases (2008 onward). The converged program's first increment was organized as Template 1, fielded in releases:

  • Release 1.0 — Financial and Acquisition (the largest release: general-fund and Navy Working Capital Fund finance such as billing, budgeting, and cost planning; acquisition such as contract awards and budget exhibits; and workforce applications such as personnel administration and training).
  • Release 1.1 — Wholesale and Retail Supply.
  • Release 1.2 — Intermediate-Level Maintenance.

  Release 1.0 reached initial operational capability at NAVAIR in 2008, followed by phased deployment at the other commands; the supply release was fielded into the early 2010s.

• Cloud migration (2019). In August 2019, Navy ERP completed a major technology refresh, migrating to the SAP HANA in-memory platform in the cloud (AWS GovCloud, using SAP's secure HANA cloud offering). The migration was reported as the Navy's largest IT system to move to the cloud and was completed roughly ten months ahead of its original ~20-month plan, timed to the start of the fiscal year.

• Fleet migration and system-of-record status (2024–2026). The Navy then moved to bring its remaining major commands — including U.S. Fleet Forces Command, U.S. Pacific Fleet, and Navy Reserve Forces Command — onto Navy ERP, with the goal of running "every single transaction" through one general ledger. The Navy announced completion of that migration in January 2026, and GAO records that as of March 2026 Navy ERP is the Navy's financial system of record.
• S/4HANA modernization (underway). A second modernization phase is migrating the SAP application layer from SAP ECC 6.0 to SAP S/4HANA (SAP S/4HANA Cloud Private Edition received DISA Impact Level 4 provisional authorization in May 2024, enabling its use for DoD), implemented with SAP NS2. As of this review the ECC-to-S/4HANA cutover is in progress; a completion date is not confirmed from a current public source.

The throughline: the integrate-finance-and-supply, one-system-of-record mission has been constant since the convergence; the release structure, the hosting platform, and the SAP version underneath have evolved.

How it works / is structured

Navy ERP is best understood as one SAP system carrying several integrated business areas, sitting on a modern cloud platform and connected to a wide range of external systems.

The business areas it runs

Across its documentation, Navy ERP covers these functional areas:

• Financial management — general-fund and Navy Working Capital Fund accounting, budgeting, billing, cost planning, and the general-ledger function that makes it the financial system of record.
• Supply-chain / materials management — wholesale and retail inventory, requisitioning, receipt, and issue of material; integration of the supply transaction with its financial effect.
• Acquisition and project/program financials — contract awards, activity-based costing, budget exhibits, and project-level financial management.
• Plant and intermediate-level maintenance — maintenance management for the plant and intermediate-level work the covered commands perform.
• Workforce / personnel administration — personnel administration, training, and related workforce functions, including timekeeping for some commands.

The SAP foundation

Navy ERP is built on commercial off-the-shelf SAP software. Historically this was the SAP Business Suite — SAP ERP Central Component (ECC) plus Supply Chain Management, with Business Intelligence, Process Integration, and the Enterprise Portal — on the SAP NetWeaver platform. Since 2019 it has run on the SAP HANA in-memory database platform in the cloud. It is repeatedly described as one of the largest SAP implementations in the world and the Department of the Navy's single instance of SAP for the processes it covers.

Integration with other systems

Navy ERP is not an island: program documentation describes it interfacing with roughly 50 external automated systems to exchange acquisition, financial, manpower/personnel, and logistics data. This is what lets it serve as the Navy's enterprise hub while still exchanging data with DoD-wide and Navy-specific systems for catalog, requisitioning, personnel, and disbursing functions.

The reference data it carries

For logisticians, one of the most practically important things Navy ERP holds is the Navy's live supply-management reference data, including the master cognizance symbol (COG) and stock-location code (SLOC) assignments. The COG is the two-character code prefixed to a National Stock Number that tells a Navy logistician the stores account (and therefore funding) and the cognizant inventory manager for an item; its authoritative current values live in the Navy supply systems, with the master listing carried in Navy ERP. See the Navy Cognizance Symbols (COG Codes) reference for how to read a COG, and note that because manager assignments change as commands reorganize, the live Navy ERP listing is more authoritative than any cached table.

Public vs authenticated access

Navy ERP is an authenticated DoD business system, not a public website. There is no public, no-login interface to the system itself: it carries financial and supply transactions and controlled management data, so it is reachable only by provisioned users on authorized networks.

What is public is the documentation and program information about Navy ERP — the program's own site, oversight reports (GAO, DOT&E), and command pages describe what it is and how it is run. This page aggregates that public information. To actually transact in Navy ERP — post a financial entry, requisition material, manage maintenance — you need a CAC and an approved, role-based account.

How to get access

Access to Navy ERP follows the standard pattern for a controlled DoD financial/supply system: a Common Access Card plus a role-based account approved through your command.

1. Confirm the requirement. With your supervisor or command supply/financial-management point of contact, establish that Navy ERP access is required for your duties and identify the specific functional roles you need.
2. Have a valid CAC. Navy ERP is CAC-authenticated; ensure your Common Access Card and PKI certificates are current.
3. Submit the account/role request through the Navy ERP access process. Route the request through your command using the current Navy ERP / NAVSUP account-request process, specifying the roles tied to your job. Because it is a system of record, separation-of-duties rules constrain which roles one person may hold (you generally cannot hold conflicting roles such as both initiating and approving the same transaction).
4. Complete required training and approvals. Finish any role-specific training and obtain the supervisor, security, and functional approvals the process requires.
5. Log in and verify your roles. Once provisioned, log in with your CAC and confirm you can perform the transactions your roles authorize.

The practical takeaway: there is no self-service signup. Navy ERP access is provisioned by your command for the specific job you perform, and the role set you receive is deliberately narrow.

Common tasks

Because Navy ERP is a full SAP business suite, the universe of in-system transactions is vast and role-specific — finance, supply, acquisition, and maintenance specialists each work a different set of transactions, and the exact screens are behind authentication and change across releases. Rather than document role-specific SAP transactions that this page cannot verify against the live system, the structured tasks on this page cover the two things a logistician most reliably needs around Navy ERP: requesting access, and resolving the Navy supply reference data (COG/SLOC) it carries. For in-system transaction procedures, rely on your command's current Navy ERP role training and the program's official guidance.

Common gotchas

• "Navy ERP" is not one screen. It is a large SAP system spanning finance, supply, acquisition, and maintenance. What a user can see and do depends entirely on their assigned roles — two people can both be "in Navy ERP" and have completely different access.
• Roles are deliberately narrow, and separation of duties is enforced. As a financial system of record, Navy ERP restricts conflicting role combinations. Expect to request exactly the roles your job needs and no more, and expect approvals to take time.
• It is the financial system of record — accuracy propagates. Transactions posted in Navy ERP feed the Navy's authoritative accounting and supply records. An error does not stay local; correct it through the proper process rather than working around it.
• The reference data is live; cached tables drift. The master COG/SLOC and related supply reference data are maintained in the system. A printed or downloaded cognizance table can be stale; the Navy Cognizance Symbols (COG Codes) reference explains the structure, but the current manager assignment is whatever the live Navy ERP listing says.
• Old URLs and portal paths change. Navy ERP moved to the cloud in 2019 and its access portals and reference-data paths have shifted across that migration. Reach the current request and reference paths through your command or the official program site rather than a saved link.
• It is not the catalog. Navy ERP requisitions and manages material; it does not define what an NSN means. For catalog identity, characteristics, and DoD-wide management data, use the DLA catalog — see WebFLIS and PUB LOG.
• It is not afloat unit-level supply. Enterprise and inventory-control-point supply runs in Navy ERP, but unit-level and afloat supply procedures are governed separately under NAVSUP P-485 Online. Know which world your task lives in.

When to use this vs alternatives

Navy ERP is the Navy's enterprise business backbone, but it is one system among several a logistician touches. Use the guide below to keep them straight.

• Use Navy ERP when you are working the Navy's enterprise finance, wholesale/retail supply, acquisition, or maintenance processes at the major commands and inventory control points it covers — and when you need the authoritative financial and supply record.
• Use the Navy Cognizance Symbols (COG Codes) reference to read the two-character COG; Navy ERP carries the live master COG/SLOC assignments, while the reference page explains how to decode the structure.
• Use WebFLIS or PUB LOG to identify an item — its NSN, characteristics, part-number cross-references, and DoD-wide management data. Navy ERP uses that catalog identity; the DLA catalog defines it.
• Use FedMall for catalog-based ordering of commercial and government items through the DoD e-commerce marketplace. Navy ERP handles the enterprise requisition and financial side; FedMall is a procurement/ordering channel.
• Use NAVSUP P-485 Online for the Naval Supply Procedures that govern unit-level and afloat supply — a different layer from the enterprise system.

In short: reach for Navy ERP to execute and account for the Navy's enterprise finance and supply at the major commands; reach for the DLA catalog systems to identify items, and for the Navy supply publications to follow unit-level procedure.

Training and authoritative references

Navy ERP training is delivered through the program and the commands as role-based training tied to the specific transactions a user is authorized to perform; it is not generally available as open public courseware, because the system itself is authenticated. For authoritative public information about the program, the best sources are the Navy ERP Program site and NAVSUP Business Systems Center, which develops and sustains the system; the SECNAV (RDA) program page for acquisition context; and the oversight record, which is unusually rich for this program — the Government Accountability Office (GAO) reports (including GAO-05-858) document the pilot-era history and convergence, and the Director, Operational Test and Evaluation (DOT&E) annual assessments document the release structure and fielding. Links to each are in the references list on this page. For the supply reference data Navy ERP carries, the governing Navy supply procedures are in Naval Supply Procedures (NAVSUP P-485).

Interesting context

Navy ERP is, in a sense, a monument to how hard enterprise software is even for an organization with effectively unlimited resources. The program's origin story is not a clean success — it is four parallel ERP pilots (SMART, SIGMA, NEMAIS, and CABRILLO, one per systems command) that the Government Accountability Office concluded had largely wasted about a billion dollars before being judged redundant and consolidated. That public reckoning is unusual: most large IT failures are quietly absorbed, but Navy ERP's were reported to Congress and became a frequently cited case study in ERP-implementation literature. The converged program that rose from those pilots then became one of the largest SAP implementations in the world, integrating finance and supply for the Navy's major commands into a single system — and, in 2019, the Navy's largest IT system to migrate to the cloud, a move the team finished roughly ten months ahead of schedule and timed to the turn of the fiscal year.

There is a deeper logistics-history thread, too. The reason Navy ERP matters so much to a working logistician is the same reason the cognizance symbol exists: the Navy has always needed to know who manages a part and how it is funded, and to keep money and materiel reconciled. The COG packed that into two characters on a National Stock Number decades ago; Navy ERP is the modern enterprise expression of the same instinct — one integrated system where the supply transaction and its financial effect are recorded together, so the Navy can finally answer, with an auditable record, the oldest logistics questions of all: what do we have, where is it, who manages it, and what did it cost?

Last verified

This page was last reviewed on 2026-06-21. Most prior verification flags are now resolved against authoritative public sources: the program office (corrected from PEO EIS to PEO MLB / Navy Enterprise Business Solutions after the May 2020 reorganization), the pilot-era costs and history (GAO-05-858: ~$1 billion across SMART/SIGMA/NEMAIS/CABRILLO), the scale figures (~56% of total obligation authority; >$145 billion in transactions per year per GAO-26-107119; nearly 100,000 users after the January 2026 fleet migration), the ~50 external interfaces (DOT&E), the financial-system-of-record status (GAO records this as of March 2026), and the cac_required access type. Items that remain genuinely unconfirmed and are stated conservatively: the exact ECC→S/4HANA cutover completion date (transition confirmed as underway, not complete), the current live account-request route/URL, and the current master COG/SLOC reference-data access path (legacy CAC-gated path could not be re-verified; erp.navy.mil was unreachable from the verification environment). These three should be confirmed against current official sources / SME before publishing any specific procedure or URL. To suggest a correction, use the site's correction path.