NOTIONAL SCOPE

United States Air Force

Expeditionary Combat Support System
(ECSS)
Increment 1/Release 1 Wholesale
Supply w/Financials







Notional Scope


File Ref: ECSS Notional Scope
Doc Ref: ECSS Error! Reference source not found.
Document Control ii
1 DOCUMENT CONTROL
1.1 Change Record
3
Date Author Version Change Reference



Notional Scope


File Ref: ECSS Notional Scope
Doc Ref: ECSS Error! Reference source not found.
Document Control iii
Contents
1 Document Control ...................................................................................................... ii
1.1 Change Record ............................................................................................................ ii
2 Business Objectives .................................................................................................. 1
3 Project Assumptions and Constraints ..................................................................... 3
3.1 Project Assumptions ..................................................................................................... 3
3.2 Constraints ................................................................................................................... 3
4 Functional Processes ................................................................................................ 4
5 Application Modules ................................................................................................ 13
6 Scope Statement ...................................................................................................... 15
6.1 Technical Scope ......................................................................................................... 15
6.2 Organizational Scope ................................................................................................. 16
6.3 Geographic Scope ...................................................................................................... 16
6.4 Conversion Scope ...................................................................................................... 16
6.5 Interface Scope .......................................................................................................... 17
6.6 Reporting Scope ......................................................................................................... 17
6.7 Customization Scope .................................................................................................. 17
6.8 Workflow Scope .......................................................................................................... 17
6.9 Training Scope ........................................................................................................... 17
6.10 Out of Scope ............................................................................................................... 18




File Ref: ECSS Notional Scope
Business Objectives 1 of 18
2 BUSINESS OBJECTIVES
This scope document is restricted to the first release of the restructured ECSS program, consistent with the
Air Force (AF) and Office of the Secretary of Defense (OSD)-approved way ahead of December 2011
[pending]. The Analysis of Options Study determined and reported that the AF should begin ECSS
development and deployment with a release of Core Financials capabilities, based upon the commercial, off-
the-shelf (COTS) Oracle capabilities and utilizing the existing ECSS Oracle solution and other Department of
Defense (DoD) Oracle implementations as reference designs. This would be followed by other releases
which complete the Enterprise Resource Planning (ERP) contribution to compliance with the Chief Financial
Officers Act (CFO compliance) of 1990, and further releases which complete the set of desired ECSS
capabilities for logistics transformation and AF efficiencies.
A core financial system is defined by the Office of Management and Budget (OMB) Circular A-127 as an
information system that may perform all financial functions including general ledger management, funds
management, payment management, receivable management, and cost management. The core financial
system is the system of record that maintains all transactions resulting from financial events.
The Department of Defense (DoD) Financial Improvement and Audit Readiness (FIAR) guidance provides
instructions for implementing a consistent, Department-wide plan toward achieving financial improvement and
audit readiness objectives. In accordance with the 2010 National Defense Authorization Act Section 1003,
the FIAR Directorate developed the FIAR Guidance for reporting entities and service providers working
toward the goal of audit readiness. The FIAR Directorate supports a portion of the Office of the Under
Secretary of Defense (Comptroller) (OUSD(C)) mission to improve financial information most often used by
DoD decision makers. Under the leadership of the FIAR Directorate, two of the Departments strategic goals
in support of this mission are to 1) Achieve and sustain audit readiness, and 2) Achieve and sustain
unqualified assurance on the effectiveness of internal controls of which ECSS will support.
Wholesale Supply is the primary source for materiel required for depot level repair needs and provides retail
supply with materiel and materiel return service. Complimentary to this, Retail Supply is the primary source
for materiel required for base level mission support needs and provides base customers with a materiel return
service as defined in AFMAN 23-110.
ECSS plans to achieve full financial capability by implementing wholesale supply with supporting financials,
retail supply with supporting financials, and asset management with supporting financials.
The objective of the Wholesale Supply w/Financials release within ECSS is to enable the following end-to-end
processes: Budget to Report (B2R), Concept to Product (C2P), Plan to Stock (P2S), Procure to Pay (P2P),
and Order to Cash (O2C).

The capabilities by increment and release are identified in the following table, described in business terms,
with key subsumed legacy systems identified:

Capability Description Key Subsumed Legacy Systems
Increment 1/Release 1:
Wholesale Supply
w/Financials
Builds G/L capability and controls
for WCF accounting, sub-ledger
capability for WCF and GF
accounting, and integrates Depot
supply inventory, procurement,
order management, and item
master management,
NWRM/Controlled Materials and
IUID.
IMCS (MIICS/D043,
MIIDB/D043A,
AFERS/D143C,I&SSS/D043B,
BASES/D046, SNUD/D071,
MWAS/D086, PIECS/D155,
SSRAC/D169, AFPS/D220),
partial subsumption of
SMAS/H118 excluding medical,
FIABS/D035J, SCS/D035,
IMWRP/D035A, RAMP/D035C,
WMER/D035B, SSSC/D035D,
RDS/D035G, WARRS/D035K,
INSTOR/D035L, SIS/D035T,


File Ref: ECSS Notional Scope
Business Objectives 2 of 18
Capability Description Key Subsumed Legacy Systems
CAV-AF, SACS/D036,
PRPS/D203, partial subsumption
GAFS-R (WCF) and partial
subsumption of IAPS (H086)
wholesale transactions
Increment 1/Release 2:
Retail Supply
w/Financials
Integrates Retail supply inventory
systems, U2 program items, and
cryptologic management,
NWRM/Controlled Materials and
IUID.
SBSS/ILS-S/D002A, ALMSS,
CDAS, CLASS, SOCS,
IAPS/H086 WCF except medical
, Manual journal entries for AF
Academy
Increment 1/Release 3:
Asset Management
(General Equipment)
w/Financials
Integrates asset instantiation and
asset management for all AF
assets (eg. Equipment, IT,
vehicles, capital and GFE).
AFEMS/C001 except classified




File Ref: ECSS Notional Scope
Project Assumptions and Constraints 3 of 18
3 PROJECT ASSUMPTIONS AND CONSTRAINTS
The following are the key project assumptions and constraints:
3.1 Project Assumptions
The ECSS solution will be based upon the latest commercially available Oracle E-Business Suite (EBS)
capabilities. As of this Scope definition that version is 12.1.3.
As envisioned in the AOO Study report, additional ECSS releases will complete the ERP capabilities..
A fiscal year (FY) cutover is not required.
The implementation methodology for this release will be the Oracle Unified Methodology (OUM).
This scope further assumes that a robust design will be developed in a requirements refinement phase,
corresponding to OUMs Inception and Elaboration phases, and to BCLs Prototyping phase, which will
result in a handoff to a development and deployment team.
This scope document assumes that irrespective of milestone, Increment, Program, or other acquisition
determinations, this scope will be implementable within the chosen acquisition construct(s).
ECSS reporting capabilities for the production of financial statements, in this release and in future
releases, will be required for AF Working Capital Fund (WCF) only. Transactions captured in the General
Fund (GF) will be passed to the in-process ERP deployment of the Defense Enterprise Accounting
Management System (DEAMS).
Sufficient transformation of financial processes will occur to justify the business case for this
implementation.
Parallel remediation activities in legacy systems will not impact ECSS design or schedule.

3.2 Constraints
The AF, and the DoD, must be ready for FIAR assertion by 2016, in time for business entries made in the
2017 fiscal year to be auditable. The AF, and the DoD, must be audit-ready for the Statement of
Budgetary Resources for General Funds in 2014.



File Ref: ECSS Notional Scope
Functional Processes 4 of 18
4 FUNCTIONAL PROCESSES
The following business processes will be designed, developed, and deployed in this release. Some sub-processes
may not be executed in ECSS, others will eventually be executed in ECSS but not in this release. Lower level
process descriptions relevant to the scope will be defined in the Future Process Model documents. Listing of a
process area below does not imply that all lower-level processes are automatically in scope transformation and
ERP-enabling of some sub-processes at the lower levels may be deferred until later Releases.

Budget-to-Report (B2R):

Budget to Report (B2R) encompasses all business functions necessary to support the management of
resource allocation to translate the defense strategy into an annual defense budget and provide feedback for
program performance. The B2R business process supports the Air Force logistics requirements for Planning,
Programming, Budgeting, and Execution (PPB&E) process. This process establishes the financial foundation
such as chart of accounts, accounting calendar, and resource/cost centers (work centers or departments).
B2R supports Department of Defense (DoD) and Air Force financial policy by establishing financial business
rules and internal controls such as cost methodology and segregation of duties. B2R supports the collection
of the time phased allocation of funding for use in the Program Objectives Memorandum (POM) and the
financial details for the Budget Estimate Submission (BES) and execution reviews; the distribution and control
of funds; transaction processing in accordance with legislation, laws, Federal Accounting Standards Advisory
Board (FASAB), DoD, and Air Force regulations and policies; and the activities performed to deliver relevant,
timely, and accurate information to stakeholders and provide feedback for management decision-making and
program performance, such as trial balances, managerial cost reports, and support of financial statements,
footnotes, and treasury reporting.

B2R capabilities represented in R1 include:
Planning, Programming, Budgeting Management
o Establish the operating environment for transaction processing such as defining chart of
accounts, organization structure, accounting calendar, business rules, cost methodology,
segregation of duties, and allocation methodology.
o Facilitate data analysis and budget execution process.
o Support project based accounting.
Financial Execution
o Distribute funds from apportionment down to sub-allotments and continuing resolutions
o Updates to the budget will be incorporated into ECSS.
o Transfer subsidiary ledger accounting to the general ledger such as disbursements and
collections.
o Import, create, approve, and post journal entries (budgetary and proprietary accounting)
o Maintain projects such as changes to tasks, status, and funding.
Financial Report Management
o Coordinate and complete subsidiary ledger period close processes.
o Perform general ledger period close process including processing recurring journal entries,
accrual and accrual reversal journal entries, and processing gain/loss from foreign currency
revalued balances.
o Perform balancing activities and support the creation of Treasury and Interfund reports Generate
and publish management reports and support required federal report creation.
o Provide ad-hoc analysis and reporting.

B2R: Budget to Report
B2R.10 Perform Planning, Programming and Budgeting Support
o B2R.10.10 Establish Financial Controls, Policies and Business Rules
B2R.10.10.10 Establish and Maintain Financial Controls
B2R.10.10.20 Establish and Maintain General Ledger Foundation


File Ref: ECSS Notional Scope
Functional Processes 5 of 18
B2R.10.10.30 Establish and Maintain Funds Control Foundation
B2R.10.10.40 Establish Costing Foundation
B2R.10.10.50 Establish and Maintain Financial Rules
B2R.10.10.60 Support PPB&E Calendar of Events
o B2R.10.20 Collect Performance, Outcomes, Requirements and Financial Information
B2R.10.20.10 Identify PPB&E Data Needed and Appropriate Data Sources
B2R.10.20.20 Support Collection Information for PPB&E and Cost Accounting
o B2R.10.40 Establish Projects
B2R.10.40.10 Review Projects
B2R.10.40.20 Set Up and Activate Projects
B2R.20 Perform Fiscal Year Execution
o B2R.20.10 Receive and Distribute Budget Authority
B2R.20.10.10 Receive and Distribute Working Capital Fund
B2R.20.10.20 Project Execution
B2R.20.10.30 Notify Stakeholders
B2R.20.10.40 Manage AF GF Budget Distribution and Customer Funds
o B2R.20.20 Import Subsidiary Ledger Journal Entries
B2R.20.20.10 Establish Accounting
B2R.20.20.20 Transfer Subsidiary Journal Entries
B2R.20.20.30 Review Journal Entries
o B2R.20.30 Perform Manual Journal Voucher Processing
B2R.20.30.10 Create Manual Journal Voucher
B2R.20.30.20 Approve Manual Journal Voucher
B2R.20.30.30 Post Journal Entries
o B2R.20.40 Perform Funds Control Check
B2R.20.40.10 Review Fund Requests
B2R.20.40.20 Perform Commitment
B2R.20.40.30 Perform Decommitment
B2R.20.40.40 Perform Obligation
B2R.20.40.50 Perform De-obligation
B2R.20.40.60 Notify Stakeholders
o B2R.20.50 Perform Rescission, Reallocation, and Reprogramming
B2R.20.50.10 Review Rescission
B2R.20.50.20 Perform and Approve Rescission
B2R.20.50.30 Review Reprogramming
B2R.20.50.40 Perform and Approve Reprogramming
B2R.20.50.50 Review Reallocation
B2R.20.50.60 Perform and Approve Reallocation
o B2R.20.70 Manage Cash
B2R.20.70.10 Perform Cash Forecasting Support
B2R.20.70.20 Perform Cash Reconciliation and Balancing Support
B2R.20.70.30 Perform Interfund Reconciliation
B2R.30 Perform Reporting Support
o B2R.30.10 Close Subsidiary Ledgers
B2R.30.10.10 Coordinate Period Close Calendar of Events
B2R.30.10.20 Perform Accounts Payable Period Close


File Ref: ECSS Notional Scope
Functional Processes 6 of 18
B2R.30.10.30 Perform Purchasing Period Close
B2R.30.10.40 Perform Inventory Period Close
B2R.30.10.50 Perform Projects Period Close
B2R.30.10.70 Perform Cash Period Close
B2R.30.10.80 Perform Receivables Period Close
B2R.30.10.90 Perform External Subsidiary Ledger Period Close
o B2R.30.30 Perform General Ledger Preliminary Period Close
B2R.30.30.10 Establish Recurring and Reversing General Ledger Entries
B2R.30.30.20 Process All Pending Transactions
B2R.30.30.30 Revalue Balances (FX)
B2R.30.30.40 Reconcile Subsidiary Transactions to General Ledger Accounts
o B2R.30.40 Generate Management Reports and Perform Final Period Close
B2R.30.40.10 Establish and Maintain Reporting Requirements for ECSS
B2R.30.40.20 Analyze Financial Information (Reviews)
B2R.30.40.30 Close Current Period/Open Next Period
B2R.30.40.40 Publish /Distribute Report
B2R.30.40.50 Perform Year End Close

ECSS will generate the Trial Balance, 1307 reports and Treasury Reports. It is assumed that
the applicable financial data will be forwarded to DDRS for development of the official AF
Financial Statement.

Concept to Product (C2P)
Concept to Product encompasses all business functions necessary for Product Lifecycle Management (PLM).
These include enterprise problem reporting, engineering change control for item, product data engineering
change control, document management (including technical orders, engineering specifications, contractual
deliverables etc.), structured content management, Computer-Aided Design (CAD) authoring, input to
Centralized Access for Data Exchange and Unit Type Codes.

Increment 1 will not incorporate all functions of Product Lifecycle Management. Release 1 scope utilizes two
major portions of the future process model; C2P.10 Manage Assistance Request and C2P.50 Release
Enterprise Change. Increment 1, Release 1 C2P strategy focuses on Item Master and Item Management
Control System (IMCS) subsumption and satisfies requirements to properly communicate and workflow Item
Master related change requests. No additional functionalities are introduced by C2P in Releases 2-3.

C2P capabilities represented in R1 include:
Create and Manage Item Master Assistance Request
Enterprise Item Master Change Release Management
Capability to create, update and manage the Item Master and non-engineering Bill of Material

C2P: Concept to Product
C2P.10 Manage Assistance Request (AR)
o C2P.10.10 Create Assistance Request (AR)
C2P.10.10.10 Initiate Assistance Request (AR)
C2P.10.10.20 Initial Assistance Request (AR) Assessment
C2P.10.10.30 Close Assistance Request (AR)
o C2P.10.20 Detailed Assessment of Assistance Request (AR)
C2P.10.20.10 Analyze for Change
C2P.10.20.20 Provide Assistance/Information



File Ref: ECSS Notional Scope
Functional Processes 7 of 18
C2P.50 Release Enterprise Change
o C2P.50.40 Develop / Update Item Master
C2P.50.40.10 Establish Master Item Identifier
C2P.50.40.20 Assign or update Master Item logistics attributes
C2P.50.40.30 Assemble Master Item Package
C2P.50.40.40 Review/Approve Master Item Package
C2P.50.40.50 Baseline Master Item
C2P.50.40.60 Confirm Item Master
o C2P.50.50 Close AR/ECR/ECN
C2P.50.50.10 Verify and Certify Data Elements of ECN
C2P.50.50.20 Close AR, ECR, and ECN

Order-to-Cash (O2C):

Order to Cash encompasses all business functions necessary to accept and process customer orders
(internal/external) for services and/or inventory held for sale and internal consumption. This process supports
distribution/collections functions in order to manage customers, accept orders, prioritize orders, order
fulfillment, perform distribution, manage receivables/collections, and manage returns (internal/external).
While performing these business functions, O2C ensures funds availability before/during the order execution
process, ensures compliance/risk from external customer perspective, and ensures Order Promise to the end
customers. The operational discipline across these business processes provides a Perfect Order Fulfillment
in such a way that the shipments are delivered on-time, complete, accurate, and in perfect condition while
appropriate funds are ensured for debit.


O2C capabilities represented in R1 include:

Receivables/Collection Management
o Capability to generate customer/credit invoices (for shipments, services, project based billing,
etc.)
o Capability to generate manual invoices per stakeholder business rules
o Capability to receive, generate and perform debit transactions/customer refunds (including write
offs, customer returns,
o Capability to perform invoice adjustments
o Capability to process Auto Lockbox
o Capability to generate Dunning letters
o Capability to receive advance payments
o Capability to prorate invoices per shipped quantity/services
o Capability to perform receipt to invoice matching
o Capability to capture, log, and track customer correspondence
o Capability to generate and print/mail/email/fax customer facing documents (Invoices, notes, etc.)
o Capability to provide/track customer bad debt history, late payments, early payments, etc.
o Capability to generate Treasury reports, Federal and DoD reporting
o Capability to capture/publish audit trail of receivables execution activities
o Capability to receive and process receipt (account receivables) transactions
o Capability to perform collection investigation
o Capability to generate/track past due reporting
o Capability to generate Treasury report for receivables
o Capability to capture/publish audit trail of collections activities
Customer Management (Internal/External)
o Capability to create, update, and delete customers and customer related data
o Capability to support customer invoice discrepancies
Customer Return Management
o Capability execute Return Material Authorization (RMA) orders through receivables process
o Capability to process credits
Customer Order Management (Internal/External)


File Ref: ECSS Notional Scope
Functional Processes 8 of 18
Order Fulfillment (Pick, Pack, and Ship)
Price Management
Hold Management (Credit, Compliance, Export, etc.)
Distribution/Transportation Management
After Sales Support including Self-Service

O2C: Order to Cash
O2C.10 Manage Customer Orders
o O2C.10.10 Create Customer Order
O2C.10.10.10 Enter Order Header
O2C.10.10.20 Enter Line Details
o O2C.10.20 Book Order
O2C.10.20.10 Run Available to Process (ATP)
O2C.10.20.20 Book/Schedule Order
o O2C.10.30 Acknowledge Order
O2C.10.30.10 Acknowledge Order
o O2C.10.40 Update/Maintain Order
O2C.10.40.10 Modify/Cancel Order Header
O2C.10.40.20 Modify/Cancel Order Lines
O2C.20 Manage Transportation / Shipping
o O2C.20.10 Create/Review Shipment
O2C.20.10.10 Create/Review Delivery Details
O2C.30 Manage Receivables
o O2C.30.10 Manage Billing
O2C.30.10.10 Create/Import Invoices
O2C.30.10.20 Generate Invoices
O2C.30.10.30 Maintain Customer Invoices
o O2C.30.20 Manage Billing Receipts
O2C.30.20.10 Apply Billing Receipts
O2C.30.20.20 Maintain Customer Receipts
O2C.40 Manage Collections
o O2C.40.10 Manage Past-Due Receivables
O2C.40.10.10 Process Collection Actions
O2C.40.10.20 Record Collection Details
o O2C.40.20 Perform Collection Follow-up
O2C.40.20.10 Process Finance Charges
O2C.40.20.20 Maintain Customer Correspondence
O2C.50 Manage Customer Returns
o O2C.50.10 Manage Return Material Authorization
O2C.50.10.10 Receive Customer Request for Return
O2C.50.10.20 Create Return Material Authorization (RMA)
o O2C.50.20 Manage Return Receipt
O2C.50.20.10 Maintain Return Material Authorization (RMA)
O2C.50.20.20 Generate Customer Credit
O2C.60 Manage Customers
o O2C.60.10 Create Customer
O2C.60.10.10 Create Customer Master
O2C.60.10.20 Create Customer Sites
O2C.60.10.30 Perform Customer Validation


File Ref: ECSS Notional Scope
Functional Processes 9 of 18
o O2C.60.20 Maintain Customer
O2C.60.20.10 Review Customer Status
O2C.60.20.20 Update Customer Master/Sites
o O2C.60.30 Manage Customer Requests
O2C.60.30.10 Receive Customer Request
O2C.60.30.20 Review/Process Customer Request
O2C.60.30.30 Maintain Customer Service Metrics

Procure to Pay (P2P):
Procure to Pay encompasses all business functions necessary to obtain goods (both inventory and expense)
and services, sourced internally and externally through strategic partnership with Trading Partners. This
process supports requirements identification, sourcing, contract management, purchasing, payment
management, receipt/debt management, and vendor return management. While performing these business
functions, P2P ensures funds availability (for both obligation/commitment) before/during the purchase order
creation process, ensures collaboration with Federal/DoD contracting authority for regulations & policies,
ensures overall compliance/risk and warranty compliance from vendor (external only) perspective, and
ensures vendor performance for on-time delivery to the end user.

P2P capabilities represented in R1 include:
Contracts Management (through collaboration with Federal/DoD contracting authority)
o Capability to receive contracts via interface with DoD contracting systems
Requisition Management
Sourcing Goods and Services
Buy (procurement) Management
o Capability to prepare and approve purchasing documentation via interface
Receipts & Returns Management
o Capability to confirm that goods and/or services were delivered as ordered, any errors were
resolved, and formal acceptance of delivery was rendered by the government
Payables Management
o Capability to approve the request for payment by the commercial vendor or government trading
partner for goods or services rendered, which includes three-way matching of the invoice against
other transaction artifacts based on the pre-determined workflow for the transaction in question.
Upon completion of the matching process the transaction is authorized for payment.
o Capability to execute the payment process for transactions that have been authorized for
payment. Activities in scope include, but are not limited to, payment groupings, the application of
credit offsets, the generation of check and Electronic Funds Transfer (EFT) ready to pay files, the
certification of payment files, the confirmation and cancellation of payment files, payment
cancellation with and without re-issuances, and payment remittance notifications.
o Capability to comply with federal payment regulations including the Prompt Payment Act (Office
of Management and Budget - OMB Circular A-125).
o Capability to identify supplier invoice discrepancies
Vendor/Supplier Management
o Capability to update, terminate, renew Supplier and Supplier Data

P2P: Procure to Pay
P2P.10 Manage Requisitions
o P2P.10.10 Create Purchase Requisition
P2P.10.10.10 Auto-Create Purchase Requisition
P2P.10.10.20 Manual Purchase Requisition
P2P.10.10.30 Self-Service Purchase Requisition
o P2P.10.20 Approve Purchase Requisition
P2P.10.20.10 Review Purchase Requisition Package / Funds Availability
P2P.10.20.20 Approve Purchase Requisition
o P2P.10.30 Modify Purchase Requisition
P2P.10.30.10 Manual/Receive Purchase Requisition Change Request


File Ref: ECSS Notional Scope
Functional Processes 10 of 18
P2P.10.30.20 Review Purchase Requisition Change
P2P.10.30.30 Update Purchase Requisition
o P2P.10.40 Cancel Purchase Requisition
P2P.10.40.10 Cancel Purchase Requisition
P2P.20 Source Goods and Services
o P2P.20.10 Determine Source of Supply
P2P.20.10.10 Determine Source of Supply
o P2P.20.20 Manage Supplier Network
P2P.20.20.10 Identify Key Supplier
P2P.20.20.20 Identify / Qualify Supplier
o P2P.20.30 Manage Sourcing Business Rules
P2P.20.30.10 Establish/Update Approved Supplier List
P2P.20.30.20 Establish/Update Sourcing Rules
o P2P.20.40 Route Purchase Requisition
P2P.20.40.10 Route Purchase Requisition
P2P.30 Manage Contracts
o P2P.30.10 Create Blanket/Contract Purchase Agreement/Release
P2P.30.10.10 Create Blanket/Contract Purchase Agreement
P2P.30.10.20 Create Release
o P2P.30.20 Create Purchase Order
P2P.30.20.10 Enter PO Header
P2P.30.20.20 Enter PO Lines
o P2P.30.30 Approve/Distribute PO/Release
P2P.30.30.10 Approve PO
P2P.30.30.20 Distribute PO / Release
P2P.40 Manage Buys
o P2P.40.10 Manage Open Purchase Orders
P2P.40.10.10 Assess Open POs / Releases
P2P.40.10.20 Review Change Requests
o P2P.40.20 Receive and Respond to MOV Request
P2P.40.20.10 Monitor and Provide Status
P2P.40.20.20 Respond to Requests
o P2P.40.30 Modify/Approve Purchase Order
P2P.40.30.10 Update PO / Release
P2P.40.30.20 Review Funds
P2P.40.30.30 Approve PO/Release
o P2P.40.40 Cancel Purchase Order
P2P.40.40.10 Cancel PO / Release
P2P.50 Manage Receipts and Supplier Returns
o P2P.50.10 Manage Shipment Notifications
P2P.50.10.10 Receive Shipment Notifications (Manual/Electronic)
P2P.50.10.20 Review Shipment Notification (Manual/Electronic)
o P2P.50.20 Receive Goods or Services
P2P.50.20.10 Receive Goods or Services (Information)
P2P.50.20.20 Receipt Confirmation
o P2P.50.30 Process Return to Vendor
P2P.50.30.10 Coordinate with Supplier
P2P.50.30.20 Process Return to Supplier
P2P.60 Manage Payment
o P2P.60.10 Manage Invoice Receipts
P2P.60.10.10 Receive / Enter Supplier Invoices (Manual / Electronic)
o P2P.60.20 Manage Invoice Validations
P2P.60.20.10 Perform Initial Validation
P2P.60.20.20 Perform Invoice Match
o P2P.60.30 Manage Invoice Discrepancies
P2P.60.30.10 Resolve Invoice Match Discrepancies / Holds
o P2P.60.40 Manage Disbursements


File Ref: ECSS Notional Scope
Functional Processes 11 of 18
P2P.60.40.10 Perform Prompt Pay Analysis
P2P.60.40.20 Select Invoice for Payment
o P2P.60.50 Manage Payables
P2P.60.50.10 Perform Reconciliation
P2P.70 Manage Suppliers
o P2P.70.10 Manage Vendors
P2P.70.10.10 Create Vendor
P2P.70.10.20 Maintain Vendor
P2P.70.10.30 Manage Vendor Requests
o P2P.70.20 Measure Supplier Performance
P2P.70.20.10 Capture Supplier Performance Data
P2P.70.20.20 Evaluate Supplier Performance Data
o P2P.70.30 Evaluate Supplier Performance
P2P.70.30.10 Develop Supplier Strategy and Build Improvement Plan
P2P.70.30.20 Execute Supplier Process & Improvement Plan
o P2P.70.40 Monitor and Report Supplier Performance
P2P.70.40.10 Monitor Supplier Performance Against Plan
P2P.70.40.20 Report Supplier Performance Against Plan

Plan to Stock (P2S):
Plan to Stock encompasses all business functions necessary to setup and manage inventory for all types of
items (repairable, consumable, expense items and other low cost items) including Air Force owned inventory
and other items that are sent to the Air Force for repair (Foreign Military Sales and other Services). This
process will also encompass the replenishment planning for inventory planned items (consumables, expense
and low cost) that are not discretely planned using an Advanced Planning and Scheduling (APS) system,
based on stock levels determined by the Forecast to Plan (F2P) business flow. The inventory process will
include receipt, handling, warehousing, issuing, redistribution, cycle counting and disposal of materials used
both in operations and maintenance. Some of these functions may be contracted to an outside agency to
manage; however, the expectation is that all essential transactional information be sent to or from the Air
Force systems.

Legacy System will continue to be the origination point for demand planning and will feed demand data into
ECSS until cMRO capabilities are enabled to include the maintenance demand along with supply.

For AF-owned material stored at non-AF-owned warehouse locations, the Depot inventory process will be
real-time interfaced with DSS to include receipt, issuing, redistribution, cycle count management and disposal
of materials used both in operations and maintenance. These functions will be contracted to DLA or handled
by ICPs; however, the expectation is that all essential transactional information be sent to the Air Force
systems in real-time.

For Crypto, warehousing capabilities will be added in R2 in Retail Supply w/Financials.

P2S capabilities represented in R1 include:
Item and Inventory Setup Management
o Capability to perform necessary item and inventory setups required to support the financial
transaction auditability for all AF WCF
Replenishment Management (Execution)
Sourcing and Prepositioning of Inventory
Inventory Accuracy and Accounting Management
Manage Inventory Disposition

P2S: Plan to Stock
P2S.10 Establish Inventory and Replenishment Plan
o P2S.10.10 Establish/ Validate Org Inventory Item and Attributes
P2S.10.10.10 Validate Master Item Attributes
P2S.10.10.20 Create Sub-Inventories and Locators


File Ref: ECSS Notional Scope
Functional Processes 12 of 18
P2S.10.10.40 Review and Update Organization Level Item Attributes
o P2S.10.20 Establish Inventory Strategies
P2S.10.20.10 Perform Inventory Analysis for Replenishment
P2S.10.20.20 Establish Inventory Strategies by Item and Item Group
o P2S.10.30 Compute and Setup Appropriate Replenishment Parameters
P2S.10.30.10 Collect/Export Required Data to Compute Planning Parameters
P2S.10.30.20 Compute/Import the Necessary Parameters
P2S.10.30.30 Review Sourcing Rules and New Levels in Planning Models
P2S.20 Determine Source and Preposition Inventory
o P2S.20.10 Run Inventory Plan and Recommend Transfers and Requisitions
P2S.20.10.10 Run Min Max
P2S.20.10.30 Monitor Vendor Managed Inventory
P2S 20.10.40 Run Kanban
P2S.20.10.50 Review and Adjust Transfers and Requisition Recommendations
o P2S.20.20 Generate Replenishments
P2S.20.20.20 Generate Recommended Material Requisitions
P2S.30 Receive, Accept, Issue and Manage Inventory
o P2S.30.10 Manage Inbound Inventory
P2S.30.10.10 Review Inbound Activities
P2S.30.10.20 Material Receipt (Direct)
P2S.30.10.50 Resolve Discrepancies
P2S.30.10.60 Distribute Receipt Information
o P2S.30.30 Manage/Issue Outbound Inventory
P2S.30.30.10 Perform Pick/Pull of Items
P2S.30.30.30 Stage Item/Prepare Shipment
P2S.40. Update and Monitor Inventory Balances
o P2S.40.20 Maintain Balances for External Inventory
P2S.40.20.10 Process External Inventory Transactions
P2S.40.20.20 Reconcile Inventory Balances and Make Stock Adjustments
o P2S.40.30 Generate Management Reports
P2S.40.30.30 Generate Inventory Reports and Compute Metrics





File Ref: ECSS Notional Scope
Application Modules 13 of 18
5 APPLICATION MODULES
The following Oracle modules comprise the target-state architecture for this release which supports the
business processes noted above.
Area Module Notes
Financials General Ledger Budgetary and proprietary ledger and
sub-ledger accounting.
US Federal Financials
Treasury
Payments
Accounts Payable
Accounts Receivable
Advanced Collections
Financial Services Accounting
Hub
New Feature under investigation with
Oracle
Procurement Purchasing
Sourcing
iProcurement
Contract Lifecycle
Management

Order Management Order Management
Advanced Pricing
Logistics Inventory
Projects Project Costing Projects may support funds receipt and
distribution.
Project Billing
Project Management
Project Collaboration
Human Resources Human Resources Necessary for workflows and
authorizations
Approvals Management
GRC Application Access Controls
Governor
Used for segregation of duties and
enforcement of security requirements
Configuration Controls
Governor
Transaction Controls Governor
Preventive Controls Governor
BI Foundation Business Intelligence OBIEE is a natural candidate for
analytics, but EBS reporting may suffice
for a simple core financials release.
Business Intelligence
Publisher
BI Applications Financial Analytics
Supply Chain Analytics
Procurement & Spend
Analytics

Reports Discoverer
PLM Product Information
Management

Bill of Materials Supports the creation of Item Master
Inventory Configuration of Item Master
Product Data Hub Distribute Item Master Data
Install Base Warranty and Time Change Items
Learning
Management
Learning Management User
Productivity Kit (UPK)
Used to capture and create training
materials to the end user (lower level
transactional processes)


File Ref: ECSS Notional Scope
Application Modules 14 of 18
Area Module Notes
Tutor Used to capture and create training
materials to the end user (high level
business processes)
Articulate Used to create training documentation
Adobe Creative Suite
Tech Stack System Administrator Technical and administrative teams may
determine that IT operations are best
facilitated with a different mix of tools.
This technical stack may also be
supplemented by operational and
management tools outside the Oracle
environment.
Application Object Library
Workflow
Web ADI
Report Manager
Application Manager
XML Gateway
Alerts
BPEL Process Manager
Single Sign-On
SOA Suite for Oracle
Middleware
These additional modules, if available, will be enabled in the CRP architecture for discovery, and it may be
determined during prototyping that they should be used to support the business processes, in addition to or in
lieu of those noted in the preceding table:

Area Module Notes
Financials Cash Management
Procurement iSupplier Portal May be used for supplier collaboration
Project Contracts May provide additional capability for
supporting contract writing
Supply Chain
Planning
Advanced Supply Chain
Planning
May be required to address item
interchangeable and substitutability.



File Ref: ECSS Notional Scope
Scope Statement 15 of 18
6 SCOPE STATEMENT
The Wholesale Supply release builds G/L capability and controls for WCF accounting, sub-ledger capability
(Accounts Payable and Accounts Receivable) for WCF and GF accounting, integrates Depot Supply inventory
systems, procurement and order management (eg. FMS, GFE, GFM). Additionally, this release includes
implementing item master management.
This release contributes to the Wave 2 Statement of Budgetary Resources and Wave 3 Mission Critical Asset
Accountability (Existence and Completeness) components of the AF FIAR Strategy.
The following systems will be subsumed or partially subsumed as part of this release. Subsumed means
that all processing will be removed from those systems and they will be decommissioned; all required
functions are either mapped to the Oracle EBS or to new Report / Interface / Conversion / Extension (RICE)
objects. Partially subsumed means that other users of the system will continue to use it, or that only some
functions and capabilities will remain in production.
E2E Trading Partners Subsumed Systems
B2R AFMC/A4 Financial Inventory Accounting and Billing System
(FIABS/D035J)
C2P 591 SCMG Master Item Identification Control System (MIICS/D043)
C2P 591 SCMG Master Item Identification Database System (MIIDB/D043A)
C2P 591 SCMG AF/FLIS Edit and Routing System (AFERS/D143C)
C2P AFMC/A4 Item Manager Wholesale Requisition Process (IMWRP/D035A)
C2P ESC/HGGG, WPAFB Suspense and Control System (SACS/D036)
P2P ESC/HGGI, WPAFB Purchase Request Process System (PRPS/D203)
O2C AFMC/A4 Stock Control System (D035,B,C,D,G,K,L,T)
O2C AFMC/A4B Commercial Asset Visibility Air Force (CAV-AF)

E2E Trading Partners Partially Subsumed Systems
B2R ESC/HIQ, Gunter AFB,
DFAS
Standard Material Accounting System (SMAS/H118) except
Medical
B2R DFAS-HTSCA General Accounting and Finance System Rehost (GAFS-
R/H069R) WCF transactions only
P2P 754 ELSG, Gunter AFB Integrated Accounts Payable System (IAPS/H086) Wholesale
transactions only

6.1 Technical Scope
The Wholesale Supply w/Financials release encompasses the set up of computing hardware for multiple
environments, including conference room piloting (CRP) or prototyping; testing (multiple, as determined by
testing policies); development; production; continuity-of-operations (COOP); training; and archiving and
retention of pre-ECSS historical transactions.
The Advanced Distributed Learning Service, hosted by the Air Education and Training Command (AETC) will
be used for training. No ECSS-hosted learning management infrastructure is required.
Patches will be applied as available and as project development scheduling permits.
A Service Oriented Architecture will be used for designing and developing interfaces, conversions and data
exchanges where applicable. The AF enterprise service bus and messaging backbone will be leveraged as
the transport mechanism. Some examples of SOA design patterns include publish/subscribe, request/reply
and file transfer. Point to point interfaces will be discouraged.
An automated 2875 user access tool will handle user registration for the solution. This includes the
environment selection, duty selection, duty modification, inventory org codes, and security validation. The


File Ref: ECSS Notional Scope
Scope Statement 16 of 18
tool will synchronize duties and inv orgs as they are developed. Single Sign-on will authorize and
authenticate through CAC access.
The technical scope of the project also encompasses the setup of tools for project management, including
collaboration, scheduling, risk management, issues management, configuration management, and other
environments which support internal project (non-ERP) information technology processes. Appropriate AF
and DoD environments already in use may be exploited for these processes.

6.2 Organizational Scope
The organizational scope outlines the stakeholders that have a functional interest in the implementation of the
scope of this release. These stakeholders will participate in the functional governance structure depending on
the issues relevant to their stake.
E2E Stakeholder Stake
All AETC/A3IA Learning Management
All AF Career Fielding Managers
(AFCFMs)
Training
All AFAA Air Force Audit Agency Contribution to Audit Readiness
All MAJCOM/FMB, FMP and FMR WCF ownership
All SAF/FMB and FMR Financial compliance and responsibility for Financial
Improvement and Audit Readiness
B2R, P2P
and O2C
DFAS ESS and ERO Financial process operations, includes DFAS Training
personnel
All AFGLSC (SC) Management of the Item Master Control Center (IMCC),
Item Managers, Stock Fund management, Financial
Management
C2P AFMC/EN Item Master and Engineering
O2C AFMC ALC Supply Management Functions, includes FX
accounts
O2C AFSAC FMS
P2P, P2S DLA Wholesale Inventory Management
P2P SAF/AQCI AF Contracting
P2P and
O2C
Contractor Interface Control
Points (CICP)
Supply Management functions; Contractor Supported
Weapon Systems

6.3 Geographic Scope
The geographic scope of the release is not bounded. All users of subsumed legacy systems within this
release, whether at a depot, the Pentagon, HQ AFMC, DFAS, or at a GFM/GFE location, will be re-directed to
ECSS. The primary geographies will be the Air Logistics Centers, DFAS Columbus and HQ AFMC.
6.4 Conversion Scope
For the Wholesale Supply w/Financials release, the systems which are being subsumed will require
conversions.
Data archiving and retention mechanisms must be developed for subsumed systems.
Authoritative data sources subject to conversion will be determined in design.


File Ref: ECSS Notional Scope
Scope Statement 17 of 18
6.5 Interface Scope
All G/L and sub ledger postings must be structured for traceability to the source system, to the transmission
batch or message, and to the triggering event.
6.6 Reporting Scope
Operational, management, and analytical reports will be enabled to support the end to end capabilities within
this release, either from EBS or Oracle Business Intelligence Enterprise Edition (OBIEE).
6.7 Customization Scope
No modifications to the delivered Oracle software are within scope. Extensions or personalizations will be
developed as necessary to support business processes defined in Future Process Model.

6.8 Workflow Scope
All necessary workflows for general ledger, payables management, receivables management, order
management, product information management, and purchasing will be enabled. All necessary workflows for
interface exception handling and rerun will be enabled.

6.9 Training Scope
The AF Learning Management System (LMS) is the enterprise training management umbrella for ECSS
training. The AF LMS capabilities are delivered through the Advanced Distributed Learning Service (ADLS)
and managed by AETC. ADLS provides site security for trainee access and houses training material and
course content. ADLS is used to manage courseware, establish the learning environment, define learning
offerings, create and maintain learning activities, manage references and glossaries, manage instructors,
manage reports, manage learning resources, create learning activities and schedule sessions, manage
classroom course materials, manage learner enrollments and completions, prepare classrooms, provide
profile information, conduct instructor led activities, register for programs and enroll in learning activities, and
manage participation of learning activities. All training will be conducted through ADLS.
ECSS course content will meet current web-based course requirements of the DoD, AF, and those specific to
the LMS. Course content will meet Sharable Content Object Reference Model (SCORM) format
requirements, and Section 508 of the Americans with Disabilities Act (handicap accessibility) compliance
standards.
ECSS course development will take advantage of the built-in Oracle tools, Oracle Tutor and User Productivity
Kit, in order to streamline the creation and maintenance of end user process and training documentation.
Online performance support is through the Online Performance Support System (OPSS) to provide help and
reference for end users. A training instance (sometimes referred to as the training environment or
sandbox) is setup and populated with data that can be used during training exercises.



File Ref: ECSS Notional Scope
Scope Statement 18 of 18
6.10 Out of Scope
While FIAR and CFO Act compliance require a coordinated and consolidated effort of ECSS and other
financial system sustainment / investment programs, the scope documented here is only for the ECSS (ERP)
contribution to FIAR.
Product Lifecycle Maintenance (PLM)/Bill of Material (BOM) the execution of systems engineering activities
and bill of material data will be addressed in future releases.
Flying Hour Program. ECSS does not contain all the information for rate establishment, such as the Flying
Hour program. Therefore, it is not intended to be the Air Force rate analysis/establishment tool. Air Force
logistics data will be used in the legacy/current process to establish rates. The ECSS B2R process will not
create rates such as the civilian/military equivalency or flying hour rates. The actual creation of annual
reimbursable rates will be done outside of the ECSS B2R process.
GPC transactions are for General Funds expense purchases within DEAMS.