WAWF - Vendor Role
 

A vendor is a provider of goods and/or services to the government. It is a role used by vendors, suppliers, and contractors.

The Vendor uses WAWF to:

  1. Submit Invoices, Receiving Reports, and Vouchers
  2. Check the status of documents in the History Folder
  3. Correct and resubmit rejected documents
  4. Receive e-mail notification of awaiting actions

Vendors can submit documents electronically using one of three methods to submit data into WAWF:

  1. Interactive Web Application
  2. Electronic Data Interchange (EDI)
  3. Secure File Transfer Protocol (SFTP)

Vendor document submission

The graphic provides a depiction of the general WAWF Vendor Document Submission functionality. It portrays a Vendor submitting documents using the Web, SFTP, and EDI (all EDI transactions are done through GEX - Global Exchange Services). All documents submitted via SFTP are placed on the WAWF EDI/FTP Support Server. All EDI documents being received from GEX are placed on the WAWF EDI/FTP Support Server. Batch jobs are run on the Support server to place the documents in the WAWF database so they can be worked in the WAWF application.

These choices do not result in significant cost or require changes to existing processes. Vendors who submit many documents, or have many Line Items on each document, should use SFTP or EDI to submit data into WAWF. Vendors already using EDI will most likely prefer to use EDI with WAWF. SFTP would be less expensive to implement than EDI for new users. After a Vendor uploads a file to the WAWF system using SFTP/EDI, a system-generated e-mail message will notify him/her of any accepted transactions, accepted transactions with modified data, or rejected transactions.

WAWF's interactive Web-application has a session time-out feature. This means it is only appropriate for a Vendor who can enter and submit his/her documents in a short amount of time.

Additionally, the Vendor will receive system-generated e-mail advising him/her of action taken by the Government Officials. If a document is rejected, the Vendor will have the capability to correct the data and resubmit. Thus, only the individual data elements need to be corrected as opposed to re-typing the entire document. Finally, the Vendor will be able to view previously submitted documents and determine the current status, review actions taken by Government officials (to include access to the name, e-mail and telephone numbers), and as appropriate, initiate follow-on actions.


Document PDF Last Updated Notes
WAWF Invoice and Receiving Report COMBO 101 This training is focused on assisting vendors with creating the document called "Invoice and Receiving Report (Combo)", a single document that combines both an invoice (a payment request) and a receiving report, commonly called a "COMBO" Document April 2020 This training is focused on assisting vendors with creating the document called "Invoice and Receiving Report (Combo)", a single document that combines both an invoice (a payment request) and a receiving report, commonly called a "COMBO".

Roles Demo Doc Last Updated Notes
Foreign Vendor Support This is an overview of the Foreign Vendor Support workflow Demo video. This is an overview of the Foreign Vendor Support workflow Demo document. March 2023

The following demonstration will show a Foreign Vendor registration, where the Vendor makes a request to the Help Desk to add their Cage Code to the Vendor Group Structure.

Foreign Vendor Support (Guide)

WAWF Vendor working folders dropdown menu.


Vendors providing services or products to the DoD are authorized to create electronic documents in WAWF and route them to the appropriate DoD officials.

You have several decisions to make before you can start creating an electronic document from your contract:

  1. Is this contract eligible for electronic document submission into WAWF?
  2. What type of document should be created from this contract?
  3. Are the DoD activities on the document route ready to receive via WAWF? Do the DoDAACs contained on the contract have active users within WAWF?

NOTE: Your contract may contain a directive to create a specific WAWF document, or it may contain a FAR/DFAR clause number referring to a specific type of WAWF document.

The vendor selects the Create Document link from the Vendor dropdown menu to create documents in the WAWF web application.


Payment Type FAR/DFAR Clause
Commercial Item Financing FAR 32.202-1(b): Authorization
FAR 52.232-29: Terms for Financing of Purchases of Commercial Items
FAR 52.232-30: Installment Payments for Commercial Items
Construction Payment Invoice FAR 52.232-5: Payments Under Fixed-Price Construction Contracts
FAR 52.232-10: Payments Under Fixed-Price Architect-Engineer Contracts
Cost Voucher FAR 52.216-7: Allowable Cost and Payment
FAR 52.216-13: Allowable Cost and Payment-Facilities
FAR 52.216-14: Allowable Cost and Payment-Facilities Use
FAR 52.232-7: Payments under Time-and-Materials and Labor-How Contracts
Fast Pay Invoice FAR 52.213-1: Fast Payment Procedure
Grant Voucher DoDGARS 32.22: Payment
DoDGARS 33.21: Payment
DoDGARS 34.12: Payment
Non Procurement Instruments (NPI) Voucher DoDGARS 32.22: Payment
DoDGARS 33.21: Payment
DoDGARS 34.12: Payment
Invoice FAR 32.905: Payment and Process
Invoice and Receiving Report (Combo) FAR 32.905: Payment and Process
DFAR Appendix F: Material Inspection and Receiving Report
DFAR 252.246-7000: Material Inspection and Receiving Report
Invoice 2n1 FAR 32.905: Payment and Process
Navy Construction/Facilities Management Invoice

FAR 52.232-5: Payments Under Fixed-Price Construction Contracts
FAR 52.232-10: Payments Under Fixed-Price Architect-Engineer Contracts
FAR 52.236-18: Work Oversight in Cost-Reimbursement Construction Contracts
Performance Based Payment FAR 32.1003: Criteria for Use
FAR 52.232-32: Performance Based Payments
Progress Payment FAR 32.5: Progress Payments Based on Costs
FAR 52.232-16: Progress Payments
Receiving Report DFAR Appendix F: Material Inspection and Receiving Report
DFAR 252.246-7000: Material Inspection and Receiving Report

Sample of FAR/DFAR clause on the contract.


PLEASE NOTE: The data presented in the following demonstrations (CAGE Code, DoDAAC, user profile information, etc.) are for purposes of example only. All users must utilize their own personal information when creating WAWF Documents.


Document Demo Doc/PDF Last Updated Notes
Commercial Invoice Vendor Create Commercial Invoice Document Vendor Create Commercial Invoice Document October 2022 This is a demonstration of a Vendor creating a Commercial Invoice. Explained are the steps to be followed, the required fields to be entered and the 'Save Draft Document' capability.
Commercial Invoice Fast Pay Vendor Create Commercial Invoice Fast Pay Document Vendor Create Commercial Invoice Fast Pay Document October 2022 This is a demonstration of a Vendor creating an Invoice-Fast Pay document. It explains how an Invoice can be designated as "Fast Pay" and the application navigation in order to create this Invoice document.
Commercial Invoice Change Pay System EBS and MOCAS Vendor changing the Pay System of a Commercial Invoice Document for MOCAS and EBS Demo Video Vendor changing the Pay System of a Commercial Invoice Document for MOCAS and EBS Demo Document April 2020 This is a demonstration of a Vendor changing the Pay System of a Commercial Invoice Document for MOCAS and EBS.
Commercial Invoice from a Receiving Report Vendor Create Commercial Invoice Document from a Receiving Report Document Vendor Create Commercial Invoice Document from a Receiving Report Document October 2022 This is a demonstration of a Vendor creating a Commercial Invoice from a Receiving Report. The overview explains how the user would navigate the application and required search fields in order to create a Commercial Invoice.
Commercial Item Financing Vendor Create CIF Document Vendor Create CIF Document October 2022 This is a demonstration of a Vendor creating a Commercial Item Finance. Explained are the steps to be followed and an explanation of a Commercial Item Finance.
Construction and Facilities Management Invoice Vendor Create Construction and Facilities Management Invoice Overview Vendor Create Construction and Facilities Management Invoice Overview May 2023 This is a demonstration of a Vendor creating a Construction and Facilities Management Invoice document. Explained are the steps to be followed and an explanation of a Construction and Facilities Management Invoice..
Construction Payment Invoice Vendor Create CICON Document Vendor Create CICON Document October 2022 This is a demonstration of a Vendor creating a Construction Payment Invoice document. Explained are the steps to be followed and an explanation of a Construction Payment Invoice.
Cost Voucher - Final Vendor Create Final Cost Voucher Document Vendor Create Final Cost Voucher Document October 2022 This is a demonstration of a Vendor creating a Cost Voucher Final. Explained are the steps to be followed, the required entry fields and an explanation of a Cost Voucher.
Cost Voucher - Interim and Direct Submit Vendor Create Interim Cost Voucher Document Vendor Create Interim Cost Voucher Document February 2017 This is a demonstration of a Vendor creating a Cost Voucher Interim and Direct Submit. Explained are the exception amount in the parameter, the steps to be taken and an explanation of Cost Voucher and Direct Submit.
Creating Document from Template Vendor Create WAWF Document from a template Vendor Create WAWF Document from a template February 2017 This is a demonstration of a Vendor creating a document from a Template. Included is the application navigation, Template dropdown navigation and required fields to be entered.
Credit Invoice Vendor Create Credit Invoice Document Vendor Create Credit Invoice Document October 2022 This is a demonstration of a Vendor creating a Credit Invoice. Explained is the application navigation, the routing page required information and information on credit invoices.
DISA Credit Invoice Creating an Energy Invoice Overview Creating an Energy Invoice Overview May 2019 This is a demonstration of a Vendor creating a DISA Credit Invoice. Explained are the steps to be followed and information on a DISA Credit Invoice. For more information review the DISA Telecom Credit Invoice (PDF).
Energy Invoice Creating an Energy Invoice Overview Creating an Energy Invoice Overview February 2017 This is a demonstration of a Vendor creating an Energy Invoice. Explained are the steps to be followed and information on Energy Invoices.
Energy COMBO Creating an Energy COMBO Overview Creating an Energy COMBO Overview February 2017 This is a demonstration of a Vendor creating an Energy Invoice and Energy Receiving Report (Combo). Explained are the steps to be followed and information on Energy Invoices and Energy Receiving Reports (Combo).
Energy Receiving Report Creating an Energy Receiving Report Overview Creating an Energy Receiving Report Overview February 2017 This is a demonstration of a Vendor creating an Energy Receiving Report. Explained are the steps to be followed and information on Energy Receiving Reports.
Vendor Updating Time/Quality from the Vendor History Folder Creating an Energy Receiving Report Overview Creating an Energy Receiving Report Overview February 2017 This is a demonstration of a Vendor updating Time/Quality from the Vendor History Folder. Explained are the steps to be followed, the Search Criteria page and an explanation of the Vendor History Folder.
Grant Voucher Vendor Create Grant Voucher Document Vendor Create Grant Voucher Document February 2017 This is a demonstration of a Vendor creating a Grant Voucher document. Explained are the steps to be followed, the Create From Template option and an explanation of a Grant Voucher.
Invoice and Receiving Report(Combo) Vendor Create Invoice and Receiving Report COMBO Document Vendor Create Invoice and Receiving Report COMBO Document August 2023 This is a demonstration of a Vendor creating an Invoice and Receiving Report (Combo). Explained are the steps to be followed, the documents that Fcan be created from a Template and required entry fields.
WAWF Invoice and Receiving Report COMBO 101 n/a This training is focused on assisting vendors with creating the document called "Invoice and Receiving Report (Combo)", a single document that combines both an invoice (a payment request) and a receiving report, commonly called a "COMBO" Document April 2020 This training is focused on assisting vendors with creating the document called "Invoice and Receiving Report (Combo)", a single document that combines both an invoice (a payment request) and a receiving report, commonly called a "COMBO".
Invoice and Reparable Receiving Report(Combo) Vendor Create Invoice and Reparable Receiving Report COMBO Document Vendor Create Invoice and Reparable Receiving Report COMBO Document August 2023 This is a demonstration of a Vendor creating an Invoice and Reparable Receiving Report (Combo). Explained are the steps to be followed, the required fields and an explanation of Invoices and Reparables Receiving Reports.
Invoice 2-in-1 (Services Only) Vendor Create Invoice 2n1 Document Vendor Create Invoice 2n1 Document October 2022 This is a demonstration of a Vendor creating an Invoice as 2-in-1 (Services Only.) Explained are the steps to be followed and CAGE Code selection.
Invoice 2-in-1 (DISA Telecom) Vendor Create Invoice 2n1 Document Vendor Create Invoice 2n1 Document June 2016 This overview of ECP0884 describes the update to DISA Telecom. Now, in addition to entering a FABS pay location code, the initiator must also enter a FABS acceptance location code in order to create a DISA Telecom Invoice. This demo explains FAB code error messages and how to successfully navigate about them.
Miscellaneous Pay Voucher Vendor Create Misc Pay Document Vendor Create Misc Pay Document February 2017 This is a demonstration of a Vendor creating a Miscellaneous Pay Voucher. Explained are the steps to be followed and the information needed to successfully create this document.
Navy Construction Payment Invoice Vendor Create NAVCON Document Vendor Create NAVCON Document October 2022 This is a demonstration of a Vendor creating a Navy Construction/Facilities Management Invoice. Explained are the steps to be followed and the information needed to successfully create this document.
Navy Shipbuilding Invoice Vendor Create SUPSHIP Document Vendor Create SUPSHIP Document October 2022 This is a demonstration of a Vendor creating a Navy Shipbuilding Invoice. Explained are the steps to be followed and the information needed to successfully create this document.
Non Procurement Instruments (NPI) Voucher Vendor Create Non Procurement Instruments (NPI) Voucher Document Vendor Create Non Procurement Instruments (NPI) Voucher Document February 2017 This is a demonstration of a Vendor creating a Non Procurement Instruments (NPI) Voucher. Explained are the steps to be followed and CAGE Code selection.
Performance Based Payment Vendor Create PBP Document Vendor Create PBP Document October 2022 This is a demonstration of a Vendor creating a Performance Based Payment. Explained are the steps to be followed and CAGE Code selection in order to be successful.
Progress Payment Vendor Create PPR Document Vendor Create PPR Document February 2017 This is a demonstration of a Vendor creating a Progress Payment request document. Explained are the steps to be followed and CAGE Code selection in order to be successful.
Purchase Card Receiving Report Vendor Create Purchase Card Receiving Report Document Vendor Create Purchase Card Receiving Report Document December 2020 This is a demonstration of a Vendor creating a Purchase Card Receiving Report. Explained are the steps to be followed and CAGE Code selection in order to be successful.
Receiving Report Vendor Create Receiving Report Document Vendor Create Receiving Report Document August 2023 This is a demonstration of a Vendor creating a Receiving Report. Explained are the steps to be followed and CAGE Code selection in order to be successful.
Receiving Report Corrections Vendor Create Receiving Report Corrections Document Vendor Create Receiving Report Corrections Document April 2020 This is a demonstration of a Vendor updating a Receiving Report for Correction. Explained are the steps to be followed, the search criteria and Pay DoDAAC information.
Receiving Report Change Pay System EBS and MOCAS Vendor changing the Pay System of a Receiving Report Document for MOCAS and EBS Demo Video Vendor changing the Pay System of a Receiving Report Document for MOCAS and EBS Demo Document April 2020 This is a demonstration of a Vendor changing the Pay System of a Receiving Report Document for MOCAS and EBS.
Receiving Report from Invoice Vendor Create Receiving Report Document from an Invoice Document Vendor Create Receiving Report Document from an Invoice Document February 2017 This is a demonstration of a Vendor creating a Receiving Report from Invoice. Explained are the steps to be followed, the search criteria and Pay DoDAAC information.
Reparables Receiving Report Vendor Create Reparable Receiving Report Document Vendor Create Reparable Receiving Report Document August 2023 This is a demonstration of a Vendor creating a Reparables Receiving Report. Explained are the steps to be followed, CAGE Code, the search criteria and Pay DoDAAC information.
Adding an Embedded Item on a Reparables Receiving Report Add Embedded Item on RRR Overview Add Embedded Item on RRR Overview February 2017 This is a demonstration for reporting embedded items on a Reparables Receiving Report and Reparables COMBO. This demo explains the purpose of embedded items and Reparables Receiving Report and Reparables COMBO. It also describes the options/actions the user has.
FMS Requirements for RRRs FMS Requirements for RRRs FMS Requirements for RRRs December 2017 This overview of ECP1043 describes the updates to the FMS Requirements for Reparable Receiving Reports/Combos. Explained are the new FMS checkboxes, the additional fields on the Report and new pages.
Telecom Invoice (Contractual) Vendor Create Telecom Contractual Document Vendor Create Telecom Contractual Document October 2022 This is a demonstration of a Vendor creating a Telecom (Contractual) Invoice. Explained are the steps to be followed, CAGE Code, the search criteria and Pay DoDAAC information.
Telecom Invoice (Non-Contractual) Vendor Create Telecom Non-Contractual Document Vendor Create Telecom Non-Contractual Document February 2017 This is a demonstration of a Vendor creating a Telecom (Non-Contractual) Invoice. Explained are the steps to be taken, dropdown menus, and various pages that will be displayed.
Vendor Creating a Receiving Report with DMLSS Data Vendor creating a Receiving Report with DMLSS data Overview Vendor creating a Receiving Report with DMLSS data Overview December 2017 This overview of ECO0641 describes the overview of a Vendor creating a Receiving Report with DMLSS data. Explained is the Document Selection page, Pay DODAAC and the routing information for the Receiving Report.
Create Receiving Report and Reparables Receiving Report, Combo, and Property Routing Changes (ECP0654 in Version 5.1) Create Receiving Report and Reparables Receiving Report, Combo, and Property Overview Create Receiving Report and Reparables Receiving Report, Combo, and Property Overview June 2012 This overview of ECP0654 describes the updates for when an initiator creates a Receiving Report or Reparables Receiving Report in WAWF, including COMBOs.
Create GSA Contract Vendor Create GSA Contract Vendor Create GSA Contract December 2017 This is a demonstration of a Vendor creating a GSA Contract. Explained are the steps to be followed and the information needed to successfully create this document.
Unit of Measure Text Unit Of Measure Text Overview Unit Of Measure Text Overview December 2017 This is an overview of the Unit of Measure display. This explains the required fields, the Line Item Summary page and the Unit of Measure lookup on the WAWF Instructions Clause Information page.
Mandatory EDA Pre-Pop Mandatory EDA Pre-Pop Overview Mandatory EDA Pre-Pop Overview December 2017 This is an overview of Mandatory EDA Pre-Pop. This explains the Template indicator, checking for CLINs entered and messages to be displayed.
PureEdge View Only Folder PureEdge View Only Folder Overview PureEdge View Only Folder Overview June 2012 This is an overview of the WAWF "Hold Folder." This demo includes information of what this folder contains and basic navigation of how to use it.

For additional information on Attachments and Attachment Types training is available on the WAWF Attachments training page. Click this link to visit the WBT WAWF Attachments training page.


The image provides a preview of the WAWF Alert Messages - After Final Invoice.


PURCHASE REQUEST: If creating an FMS Receiving Report, either a Purchase Request or MILSTRIP Document Number is required. Always enter the MILSTRIP Document Number if there is one available.

MILSTRIP: If creating an FMS Receiving Report, either a Purchase Request or MILSTRIP Document Number is required. Always enter the MILSTRIP Document Number if there is one available. Please see additional notes below regarding FMS Case Identifier.

The FMS Case Identifier can be identified using Military Standard Requisitioning and Issue Procedures (MILSTRIP) information. This information is contained in the Document Number (Record Positions 30-44) and the Supplementary Address (Record Positions 45-50).

To differentiate among the implemented FMS cases, each LOA is assigned a unique case identifier. This unique case identifier is assigned by the Implementing Agency.

The case identifier has three major components:

  1. Country Code: A two-position code representing the purchasing country or organization. A list of DOD country/activity codes is found in SAMM, table C4.T2. For Pseudo LOAs, the country code is replaced by a Program Code that represents the Security Cooperation program authorizing the transfer. Program codes are listed in SAMM C4.T2 and C15.T2.
  2. Implementing Agency (or service) Code: A single alpha code that identifies the US MILDEP or other IA that manages the item/system requested and is responsible for preparing the LOA on behalf of the USG. The most common codes are “B” for Army, “D” for Air Force, and “P” for Navy. Refer SAMM table C5.T2 for a listing of IA codes.
  3. Case Designator: A three-position alpha code assigned by the IA to identify a specific offer to a country.

The 6 digit case identifier can be extracted from the Document Number, which is also used to the construct the requisition number and transportation control number, and the Supplementary Address (SUPPAD). The second and third characters of the Document Number (MILSTRIP RP 31 and 32) represent the Country Code, while the first character is the Implementing Agency code (RP 30). The Case Designator is the last three characters of the SUPPAD (RPs 48-50).

Sample of FAR/DFAR clause on the contract.


WAWF Vendor working folders dropdown menu.


WAWF Vendor Folders have a 2 step process

1. Enter in Search information to limit the number of records brought back in the folder.

Note: The more information entered on the search page, the easier it is to find a specific record.


Search Folder Page

The Search Page allows you to enter in search information for displaying specific records inside WAWF.

2. Select the Submit Button on the search page, and you will be taken to the Folder's results page with the list of records returned. See Below:

Vendor

Contractor or Supplier. The Vendor dropdown will be displayed when a WAWF vendor user cursors over the Vendor Link. If the WAWF vendor user clicks on the Vendor Link, the Vendor dropdown will be displayed as links on the page. This dropdown is used by WAWF Vendors to create, work, and view all of their WAWF Documents.

Create Document

Click this Link to create a Document in WAWF.

Document History Folder

A Link will be available to search for and view WAWF Documents created with the Vendors assigned Cage Code.

Rejected Receiving Reports Folder

A Link will be available to search for and work WAWF Receiving Reports which have been rejected back to you in the WAWF workflow.

Rejected Invoices Folder

A Link will be available to search for and work WAWF Invoices which have been rejected back to you in the WAWF workflow.

Correction Required Folder

A Link will be available to search for and work WAWF Receiving Report Documents which have been sent back to you for corrections.

Documentation Required Folder

A Link will be available to search for and add an attachment to WAWF Documents which have a Transportation Misc Fee greater then $100 and no attachment.

Saved Documents Folder

A Link will be available to search for Draft Documents which have been saved but are not yet submitted into the WAWF Application.

Pure Edge Folder

A Link will be available to search for WAWF Documents created prior to WAWF 3.0.0 using the PureEdge UWI Viewer. These documents are all in Readonly mode.

View Only users of PIEE will have access to PureEdge 2.0.D PIEE documents in readonly mode if any exist in the database for their DoDAAC or CAGE Code.

View Only

In addition to the Vendor actions outlined above, additional personnel who have a need to view documents can be granted access in a view only mode. Once a document has been captured and processed, it is made available for view only. Access to the documents is limited by the Contractor (CAGE) Code, to which the individual is responsible for monitoring. A single electronic copy of the document to be accessed by any authorized user with Web capability is available. Vendors will be able to query and view his/her previously submitted documents.


WAWF Vendor working folders dropdown menu.


EDI Submission Process

Electronic Data Interchange (EDI) is one of three methods, including Secure File Transfer Protocol (SFTP) and interactive Web-application, used to submit data into WAWF.

The objective of the WAWF Electronic Data Interchange (EDI) inbound interface is to provide contractors and Government entities the capability of submitting various types documents to the WAWF system using ANSI X12 EDI Transaction Sets.

This interface allows the submitter to supply the data necessary to perform inspection, acceptance, and payment and receipt processing functions available within the WAWF Web application.

Data is passed from the Contractor/Vendor to WAWF via Global Exchange Services (GEX).

Documents submitted via EDI must be formatted in the WAWF EDI Guide structure and sent to GEX.

GEX will submit document to WAWF for processing.

Any Vendor who is able to create and send an electronic file in the EDI format specified by WAWF and in compliance with the Federal/DoD Implementation Conventions is eligible to participate.


After having registered into the WAWF Web application, Vendors must contact the Customer Service Center (WAWF Help Desk) for testing and assistance.

The Customer Service Center will initiate a trouble ticket and put the Vendor in contact with the Joint Interoperability Test Command (JITC). JITC provides testing assistance.

See the Customer Support link in the footer of the page for contacting the Help Desk.


By contacting the Customer Service Center (WAWF Help Desk) the Vendor can get assistance with:

  1. EDI registration
  2. Trouble ticket for JITC testing assistance
  3. Connectivity instructions
  4. Technical questions regarding record layouts and software guidelines

After opening the trouble ticket and completing the EDI testing, the Vendor must complete a System Authorization Access Request (SAAR) DD Form 2875 to request authority to submit files using EDI to WAWF through the Ogden Defense Enterprise Computing Center (DECC).

Users must complete this form to request authorization to EDI from the Defense Enterprise Computing Center (DECC), located in Ogden, Utah.

After receiving the request, the DECC personnel will establish a directory for the user.

Once you have been activated in WAWF, you may sign into the WAWF application. To view EDI documentation, click on the Documentation dropdown menu:


For detailed information regarding the rules and format of the EDI Transaction Sets, please refer to the WAWF EDI Implementation Guides prepared for the Department of Electronic Business Program Office listed above.

If a WAWF user chooses to participate in EDI filing, guidelines set forth in the implementation guides must be followed.

Once a document populates WAWF, WAWF users are able to retrieve and review the document status throughout the life cycle of that document.

The status of an updated document is provided using a system-generated e-mail.

NOTE: See the Vendor Work Folders in WAWF Overview for help with viewing and reworking documents in the WAWF Web application.


WAWF Vendor working folders dropdown menu.


FTP Submission Process

Secure File Transfer Protocol (SFTP) is one of three methods, including Electronic Data Interchange (EDI) and interactive Web-application, used to submit data into WAWF.

Vendors already using EDI will most likely prefer to use EDI with WAWF. If you are new to both SFTP and EDI, then you should discuss the pros and cons with your systems administrator. In general, SFTP would be less expensive to implement than EDI for new users.


Vendors must complete the following steps before submitting documents using the WAWF SFTP Filing Program:

  1. Register into the WAWF Web application
  2. Request testing assistance
  3. Complete DISA System Authorization Access Request (SAAR), Form DD2875

A Vendor must complete the self-registration process to obtain a WAWF (Web application) USERID and password.

After having registered into the WAWF Web application, Vendors must contact the Customer Service Center (WAWF Help Desk) for testing and assistance.

The Customer Service Center will initiate a trouble ticket and put the Vendor in contact with the Joint Interoperability Test Command (JITC). JITC provides testing assistance.

See the Customer Support link in the footer of the page for contacting the Help Desk.


By contacting the Customer Service Center (WAWF Help Desk) the Vendor can get assistance with:

  1. SFTP registration
  2. Trouble ticket for JITC testing assistance
  3. Connectivity instructions
  4. Technical questions regarding record layouts and software guidelines

After opening the trouble ticket and completing the SFTP testing, the Vendor must complete a System Authorization Access Request (SAAR) DD Form 2875 to request authority to submit files using SFTP to WAWF through the Ogden Defense Enterprise Computing Center (DECC).

Users must complete this form to request authorization to SFTP from the Defense Enterprise Computing Center (DECC), located in Ogden, Utah.

After receiving the request, the DECC personnel will establish a directory for the user.

Due to current DISA security requirements, users must use a compatible Secure Shell (SSH2) client-product to communicate with WAWF via SFTP.


If a WAWF user chooses to participate in SFTP filing, guidelines set forth in the implementation guides must be followed.

Once a document populates WAWF, WAWF users are able to retrieve and review the document status throughout the life cycle of that document.

The status of an updated document is provided using a system-generated e-mail.


NOTE: see the Vendor Work Folders in WAWF Overview for help with viewing and reworking documents in the WAWF Web application.

NOTE: The Vendor is responsible for maintaining a copy of transferred files for correction or resubmission until notification of WAWF acceptance.


5.6.0 Release

The purpose of this ECP was to provide an FMS indicator on the existing Receiving Report. The following items have been added to the WAWF Receiving Report for FMS:

  • FMS Case Identifier
  • Project Code
  • Cube
  • Transportation Account Code
  • Special Package Markings / Special Handling Requirements

Foreign Military Sales (FMS) Demo:

Document Demo Doc Last Updated Notes
Foreign Military Sales (FMS) Foreign Military Sales (FMS) Foreign Military Sales (FMS) August 2014 This overview of ECP0714 shows how to create or add to a FMS Receiving Report through the Vendor link.

5.7.0 Release

The purpose of this ECP was to allow for the creation of an email distribution list that can be used when the next workflow user requires more than one individual be notified of a document submission via email. This functionality will now exist for EDI and/or SFTP input methods.

Additional e-mail notifications will be based upon the current web process for sending additional e-mail notices when submitting a document.



The purpose of this ECP was to provide a process whereby a DLA Energy vendor may elect to submit an Energy Price Corrected Invoice against an existing Energy Invoice document.

This is limited to positive adjustments and there are two possible scenarios for creating an Energy Price Corrected Invoice:

  1. The Energy Price Corrected Invoice is against a document not in WAWF.
  2. The Energy Price Corrected Invoice is against a document in WAWF.

DLA Energy Finance Demos:

Document Demo Doc Last Updated Notes
DLA Energy Finance DLA Energy Finance DLA Energy Finance April 2015 This is an overview of how a Vendor creates an Energy Price Corrected Invoice through the Create Document link.

The purpose of this ECP was to allow NAVCON to be used with the following Pay DoDAACs:

  • CAPS-W
  • One-Pay (NAVCON can be created with One-Pay today)

Allow Payment DoDAACs on NAVCON Demos:

Document Demo Doc Last Updated Notes
Allow Payment DoDAACs on NAVCON Allow Payment DoDAACs on NAVCON Allow Payment DoDAACs on NAVCON April 2015 This is an overview of a Vendor allowing payment DoDAACs on NAVCON through the Create Document link.

The purpose of this ECP was to provide a PDS Data Feed which requires changes in both WAWF and EDA:

  • EDA will create a data feed to WAWF with all available contract data for pre-pop use on all documents.
  • This Data Feed will be available through a web service.

WAWF will accept the additional data from EDA.

WAWF will be able to choose which data elements it needs to pre-populate from the increased contract data.

WAWF will be able to access the additional data elements for future enhancements.

Vendors will be able to access the PDS data web service by using their WAWF system to system credentials.


PDS Data Feed Demo:

Document Demo Doc Last Updated Notes
PDS Data Feed PDS Data Feed PDS Data Feed April 2015 This is an overview of the changes made to the PDS Data Feed. This includes the necessary information in order to call the EDA Web Service to retrieve the PDS XML.

5.8.0 Release

The purpose of this ECP was to provide Vendors the capability to look up Contracting Officer and Contract Specialist contact information in WAWF.

  • Vendors will have a “Contracting Officer Lookup” menu option added to the “User” menu.
  • Vendors can search for Contracting Officer contact information by contract number.
  • Vendors search results will be limited to the appropriate CAGE Codes.

CORT Tool Data Presented to Vendors Demo:

Document Demo Doc Last Updated Notes
CORT Tool Data Presented to Vendors CORT Tool Data Presented to Vendors CORT Tool Data Presented to Vendors November 2015 This is an overview of the CORT Tool Data that is presented to Vendors. This ECP was to provide Vendors the capability to look up Contracting Officer and Contract Specialist contract information in iRAPT.

The purpose of this ECP was to add a new parameter that increases the maximum attachment file size to 20 MB for the following document types:

  • Energy Receiving Report
  • Energy Commercial Invoice
  • Energy Price Corrected Invoice
  • Energy COMBO

All documents other than DLA Energy related documents will retain the 5 MB file size limit.


Increase the Size of Single File That Can Be Attached to Energy Doc Demo:

Document Demo Doc Last Updated Notes
Increase the Size of Single File That Can Be Attached to Energy Doc Increase the Size of Single File That Can Be Attached to Energy Doc Increase the Size of Single File That Can Be Attached to Energy Doc November 2015 This is an overview of the changes made to increase the size of single file that can be attached to the Energy Document. The new maximum attachment file size is now 20MB.

The purpose of this ECP was to permit Vendors and Government initiators to modify the routing fields following a document recall.

A Change DoDAAC column has been added to the Vendor History Folder. A link to change the document routing information will be available everywhere that a document recall is permitted.

The Pay Office DoDAAC may not be modified to equate to another pay system, as this affects document edits.

This update applies to every document type in the WAWF application.


Allow Vendor to Change All Fields on Recalled Docs Demo:

Document Demo Doc Last Updated Notes
Allow Vendor to Change All Fields on Recalled Docs Allow Vendor to Change All Fields on Recalled Docs Allow Vendor to Change All Fields on Recalled Docs November 2015 This is an overview of the changes made to allow a Vendor to change all fields on recalled documents. This ECP was to permit Vendors and Government initiators to modify the routing fields following a document recall.

The purpose of this ECP was to provide a new document save parameter that is applicable to Vendor create of DLA Energy documents. This separate parameter will initially be set to 30 days.

This applies to the following document types:

  • Energy Receiving Report
  • Energy Commercial Invoice
  • Energy Price Corrected Invoice
  • Energy COMBO

All documents, other than DLA Energy related documents, will remain with the currently set 7 day parameter for saved documents.

All government actions for DLA Energy roles will remain with the currently set 7 day parameter for saved documents.


Increase Number of Days a Document Can Be Saved Demo:

Document Demo Doc Last Updated Notes
Increase Number of Days a Document Can Be Saved Increase Number of Days a Document Can Be Saved Increase Number of Days a Document Can Be Saved November 2015 This is an overview of the increased number of days a document can be saved. The purpose of this ECP was to provide a new document save parameter that is applicable to Vendor create of DLA Energy documents.

The purpose of this ECP was for WAWF to continuously auto save data during a user’s session. This change is limited to the Time and Quality tab of the Energy Receiving Report.

This will allow the user’s work to be preserved if they time out of the application or any system issue causes the application to become unavailable.


Auto Save Demo:

Document Demo Doc Last Updated Notes
Auto Save Auto Save Auto Save November 2015 This is an overview of the Auto Save option. The purpose of this ECP was for iRAPT to continuously save data during a user's session.

The purpose of this ECP was to allow the Vendor to search on the Pay Official DoDAAC. This will bring back any documents with the given Pay Official DoDAAC.

In addition, a search by Contract Number where multiple CAGE codes may be selected for the search will be provided. The CAGE codes that may be selected will be limited to the CAGE codes for which the requestor is authorized.

The CAGE code will now be selected using a scrollable selection list. The Vendor will be able to select one, more than one, or all CAGE(s). If no CAGE(s) are selected, ALL CAGEs will be included in the document search.

If a CAGE code with no extension is selected, the search will include the CAGE and any CAGE + Extension documents. If a CAGE code + Extension is selected, the search will only bring back documents containing the CAGE + Extension.

These new search options are limited to the Vendor and Vendor View Only History Folders.


Search by Alternative Criteria Demo:

Document Demo Doc Last Updated Notes
Search by Alternative Criteria Search by Alternative Criteria Search by Alternative Criteria November 2015 This is an overview of the search by alternative criteria capability. The purpose of this ECP was to allow the Vendor to search on the Pay Official DoDAAC.

The purpose of this ECP was to update the Final Indicator functionality. For all WAWF documents where a final indicator is present (Final Invoice, Final Shipment, Final Voucher), the final indicator will require initiator input of ‘Y’ or ‘N’ and will no longer be systematically defaulted to ‘N’.

This update applies to all documents EXCEPT the following:

  • Commercial Item Financing
  • Performance Based Payment
  • Progress Payment
  • Miscellaneous Payment Voucher
  • Telecom Invoice (Non-Contractual)
  • Property

5.9.0 Release

The purpose of this ECP was to allow submission of credit invoices and documents via WAWF. The detailed information would be available in WAWF as a repository for DFAS A/R to pull in order to post funds back to the contract. The backup would also be in WAWF for research by DCMA, DFAS, and vendors.

The credit invoice will be based on the current invoice transaction used in WAWF today with some modifications.

The credit invoice will be viewable by the vendor and all view only roles with location codes associated with the document.


Credit Invoices in WAWF Demo:

Document Demo Doc Last Updated Notes
Credit Invoices in WAWF Credit Invoices in WAWF Credit Invoices in WAWF June 2016 This is an overview of the creation of a Credit Invoice in iRAPT by an Initiator. Most of the creation and the functionalities of a Credit Invoice will be similar to the creation of a Commercial Invoice.

The purpose of this ECP was to remove the Discount Amount/Discount Date option for MOCAS. Vendors will be allowed to only submit their invoices using the Discount Percentage/Due Days terms when they want to offer a Discount.

This applies to the following documents:

  • Commercial Invoice (standalone and as part of a combo)
  • Commercial Invoice (Fast Pay)
  • Commercial Invoice as 2-in-1
  • Telecommunications Invoice (Contractual)
  • Cost Voucher

Change MOCAS Doc Disc (Opt 2 – Remove Discount Amt/Date for MOCAS) Demo:

Document Demo Doc Last Updated Notes
Change MOCAS Doc Disc (Opt 2 – Remove Discount Amt/Date for MOCAS) Change MOCAS Doc Disc (Opt 2 – Remove Discount Amt/Date for MOCAS) Change MOCAS Doc Disc (Opt 2 – Remove Discount Amt/Date for MOCAS) June 2016 This is an overview of the changes to MOCAS Document Discount (Option 2-Remove Discount Amount/Date for MOCAS). Discount amount and date are no longer available in the MOCAS pay system.

The purpose of this ECP was to modify the Energy Receiving Report to provide for the addition of more than one Sub-Commodity for each Commodity entered on the Quality Tab.


Use of Alternative Fuels on Quality Tab Demo:

Document Demo Doc Last Updated Notes
Use of Alternative Fuels on Quality Tab Use of Alternative Fuels on Quality Tab Use of Alternative Fuels on Quality Tab June 2016 This is an overview of the new use of Alternative Fuels on the Quality Tab. For an Energy Receiving Report the user will now be able to add more than one Sub-Commodity for each Commodity entered on the Statement of Quality Tab. There is also now a delete option.

The purpose of this ECP was to populate the ordering instrument (i.e., contract number) field from the data available in EDA when an action arrives in WAWF or IUID with an “F” type order number.

The system will attempt to pre-populate the Reference Procurement Instrument Number (Reference Procurement Identifier) with the Ordering Instrument Number from EDA for Web, FTP/EDI documents, and IUID registry when the following conditions are met:

  • The Contract Number Type is DoD Contract (FAR) or Uniform PIID (4.16).
  • The entered Contract Number Fiscal Year (Contract Number Positions 7-8) is equal to or later than:
    • The value for ‘FiscalYearForDodContractFAR’ System Parameter for DoD Contract (FAR) documents.
    • The value for ‘FiscalYearForUniformPIID’ System Parameter for Uniform PIID (4.16) documents.
  • The entered Contract Number has an “F” in the 9th position.

WAWF will attempt to pre-populate the Reference Procurement Identifier with an “F” PIID for the following document types:

  • Progress Payment Request
  • Commercial Item Financing Request
  • Performance Based Payment Request
  • Energy Commercial Invoice
  • Credit Invoice
  • Commercial Invoice
  • Commercial Invoice (Fast Pay)
  • Commercial Invoice 2-in-1
  • Construction Invoice
  • Navy Construction Invoice
  • Navy Shipbuilding Invoice
  • Telecommunications Invoice (Contractual)
  • Energy Receiving Report
  • Receiving Report
  • Receiving Report (FMS)
  • Purchase Card Receiving Report
  • Reparables Receiving Report

Auto Populate Contract Number Based Upon PIID Demo:

Document Demo Doc Last Updated Notes
Auto Populate Contract Number Based Upon PIID Auto Populate Contract Number Based Upon PIID Auto Populate Contract Number Based Upon PIID June 2016 This is an overview of the capability to auto populate Contract Number based upon PIID. The document folder search query updates are explained.

The purpose of this ECP was to modify the Source/Source Energy Receiving Report to have two date fields on inspection: Inspection Date and Acceptance Date. Both of these fields are required and the extracts will not change.


DLA-E Receiving Reports for S/S Transactions Demo:

Document Demo Doc Last Updated Notes
DLA-E Receiving Reports for S/S Transactions DLA-E Receiving Reports for S/S Transactions DLA-E Receiving Reports for S/S Transactions June 2016 This is an overview of the DLA e-Receiving Reports for S/S Transactions. The purposed of this ECP was to modify the Source/Source Energy Receiving Report to have two date fields on inspection. These date fields include the inspection date and the acceptance date.

The purpose of this ECP was to create an edit in WAWF that will prohibit submission of a Fast Pay Invoice document type if the Contract is in EDA as PDS data, but is not designated as a Fast Pay Contract (does not contain the Fast Pay Clause).


Create an edit in WAWF that will prohibit submission of a Fast Pay Invoice if no receiving report is cited. The receiving report validation will occur under the following circumstances:

  • The provided Accept By location code has an active registered Acceptor role.
  • A value is not entered for the Accept By location code. This only applies to FTP/EDI submissions.

Suppressed for EDI and FTP pending DLA systems corrections.

The Accept By field is now mandatory for the web entry of Fast Pay Invoices.


An edit in WAWF was created, upon clicking the Submission Button, which will cause an alert/warning bubble to pop up if the following criteria is present:

  • Excluding “Void Status” Invoices.
  • The invoice being generated is an identical invoice number to a previously submitted invoice other than a trailing alpha character within the invoice.
  • Invoices must be on the same contract (to include DO).
  • Invoices must have the same gross amount.
  • Period of Performance dates, Service Start / End dates, and Delivery date match up as dictated by document type.
  • Additionally, CLIN data such as number, quantity and cost will be checked.

Fast Pay Require RR and Contract Clause Edit Demo:

Document Demo Doc Last Updated Notes
Fast Pay Require RR and Contract Clause Edit Fast Pay Require RR and Contract Clause Edit Fast Pay Require RR and Contract Clause Edit June 2016 This is an overview of the changes made to Fast Pay to require a receiving report and a Contract Clause edit.

The purpose of this ECP was to provide the vendor with the capability to either manually create an EDI 810 2-n-1 invoice in WAWF or submit a compliant electronic EDI/FTP 810 2-in-1 invoice file to WAWF via the Global Exchange (GEX). The GEX will be the single point of entry for vendor electronic invoice files. Receipt and Acceptance will be accomplished in an external system and interfaced to WAWF, as well as via WAWF on the Web. WAWF will create a final invoice that includes the Receipt and Acceptance information. WAWF will not create or store actual Receipt and Acceptance documents.

Even though the ‘FABS’ system will be added via a database script, the SAM will still need to register location codes to receive Standard Extracts against the new ‘FABS’ system before creation of a DISA Telecom Invoice will be permitted.

Standard Pay Offices and Ship To Location Codes may be registered for the ‘FABS’ system by using the ‘Standard Extract Registration’ link in the WAWF Admin Console.


DISA Telecom Demo:

Document Demo Doc Last Updated Notes
DISA Telecom DISA Telecom DISA Telecom June 2016 This is an overview of the DISA Telecom creation process.

Accounting Pre-Validations:

ECP899 provides the capability to interface with an accounting system to perform a funds availability check with that accounting system at the time of creation of specific WAWF payment request documents.

This ECP has been coded but is currently untested. Upon identification of an accounting system test partner, the ECP can be finalized.


Accounting Pre-Validations Demo:

Document Demo Doc Last Updated Notes
Accounting Pre-Validations PIEE Accounting Pre-Validations PIEE Accounting Pre-Validations December 2017 This is an overview of the changes made to the Accounting Pre-Validations. This includes the types of documents that iRAPT will perform account pre-validations for.

Shipping Validations:

  • Obtain Unit of Measure and Quantity of Items to be Delivered for each line item from EDA.
  • Determine Total Quantity Accepted for each line item from WAWF data based on the Contract Number / Delivery Order Number combination and status.
  • For each line item on the document:
    • If the Unit of Measure from EDA does not match the Unit of Measure on the document, a Unit of Measure warning message will be issued.
    • If the Unit of Measure matches and if Quantity Shipped on an WAWF document plus the total quantity already accepted is greater than the EDA quantity to be delivered against the contract / delivery order line item, a Warning Message will be issued.

Shipping validations affect the following document types:

  • Receiving Reports
  • Energy Receiving Reports
  • FMS Receiving Reports
  • Purchase Card Receiving Reports
  • Reparables Receiving Reports
  • Commercial Invoice as 2-in-1
  • Construction Invoice
  • Navy Construction and Facilities Invoice
  • Combo Submitted Receiving Report
  • Combo Submitted Reparable Receiving Report
  • Combo Submitted Energy Receiving Report

Invoicing Validations:

  • Obtain the Unit of Measure and the Total Contracted Amount for each line item from EDA.
  • Determine total amount paid against each line item from myInvoice data based on Contract Number / Delivery Order Number combination and status.
  • For each line item on the document:
    • If the Unit of Measure from EDA does not match the Unit of Measure on the document, a Unit of Measure warning message will be issued.
    • If the Unit of Measure matches and the Amount Invoiced on an WAWF document plus the total amount already paid is greater than the EDA Total Contracted Amount for the contract / delivery order line item, a Warning Message will be issued.

Invoicing validations affect the following document types:

  • Commercial Invoice
  • Energy Invoice
  • Fast Pay Commercial Invoice
  • Commercial Invoice as 2-in-1
  • Construction Invoice
  • Navy Construction and Facilities Invoice
  • Navy Shipbuilding Invoice
  • Telecommunications Invoice (Contractual)
  • Cost Voucher
  • Combo Submitted Invoice
  • Combo Submitted Energy Invoice

ECP899 provides the capability to interface with an accounting system to perform various payment pre-validations against the accounting system.


PIEE Validations and Edit Checks Demo:

Document Demo Doc Last Updated Notes
PIEE Validations and Edit Checks PIEE Validations and Edit Checks PIEE Validations and Edit Checks June 2016 This is an overview of the WAWF Validations and Edit Checks. This includes documents effected by invoicing and shipping validations. The required information for the invoice validation is explained.

The purpose of this ECP was to implement SABRS as the replacement accounting system for Navy General Fund Legacy-STARS-FL Budget Submitting Offices (BSOs).

BSOs will be migrated from the STARS-FL system to SABRS. However, they will continue to utilize One Pay as the entitlement system.

The current design of the WAWF SABRS Miscellaneous Payment (MP) document type only supports routing of transactions with funding loaded in SABRS accounting system to the CAPS-W entitlement system. This design will be expanded upon to allow for routing of transactions to the One Pay entitlement system for BSOs migrating to the SABRS system.

WAWF will allow a list of new SABRS AAIs to be used with the One Pay entitlement system for creating Miscellaneous Payment documents.


STARS to SABRS Entitlement System Routing (Navy) for Misc Pay Demo:

Document Demo Doc Last Updated Notes
STARS to SABRS Entitlement System Routing (Navy) for Misc Pay STARS to SABRS Entitlement System Routing (Navy) for Misc Pay STARS to SABRS Entitlement System Routing (Navy) for Misc Pay June 2016 This is an overview of the changes made to the STARS and SABRS Entitlement System Routing (NAVY) for Misc Pay. The purpose of this ECP was to implement SABRS as the replacement accounting system for Navy General Fund Legacy-STARS-Submitting Offices (BSOs).

5.10.0 Release

The purpose of this ECP was to add a Supply Condition code to WAWF Property Transfer and Reparables Receiving Reports:

  • At the line level
  • On the UID Tab for UID’d items

The approved Supply Condition Code list (same as in Registry) will be used and will be a drop down on the web.

The Supply Condition Codes will be:

  • Added to EDI and Flat File formats of Property Transfer and the Reparables Receiving Report.
  • Included in data injected into IUID Registry; update the Registry Supply condition code.
  • Included in transactions sent to Accountable Property System of Record (APSRs) and Repair systems.
  • This applies to both UID’d and nonUID’d items.
  • Supply Condition Code on Property Transfer and Reparables Receiving Reports will be optional.

Multiple Serial Numbers for Non-UII Items and Add Condition Code Demo:

Document Demo Doc Last Updated Notes
Multiple Serial Numbers for Non-UII Items and Add Condition Code Multiple Serial Numbers for Non-UII Items Multiple Serial Numbers for Non-UII Items February 2017 This is an overview of the changes made to the Serial Numbers for Non-UII Items and the Condition Code. Specifically, there is now a multiple Serial Number functionality. This demonstration is a Contract Property Shipper creating a document.

The purpose of this ECP was to provide the ability in WAWF for Lab POCs to create a “Quality Data Sheet”. The Quality Data Sheet will contain pre-loaded quality data which can be accessed by Shipping POCs (WAWF Vendors) and applied to an Energy Receiving Report.

A Quality Data Sheet will consist of test data for a single Commodity, Sub-Commodity, and Test Group combination.

  • For blended fuel mixtures, the Lab POC will create separate Quality Data Sheets. WAWF Vendors will be able to import the contents of multiple Quality Data Sheets to an Energy Receiving Report.

Vendors will be able to import the Quality Data Sheet test when creating a standalone Energy Receiving Report, when creating an Energy Receiving Report as part of a COMBO and when adding Quality Data to an existing Energy Receiving Report.

This functionality applies to the Web only.


DLA Energy TQ Preload Function Capability Demo:

Document Demo Doc Last Updated Notes
DLA Energy TQ Preload Function Capability DLA Energy TQ Preload Function Capability DLA Energy TQ Preload Function Capability February 2017 This is an overview of the changes made to the DLA Energy TQ Preload Function Capability. A new Energy Lab POC role has been added and Contractor DoDAACs will be prohibited from the Energy Lab POC role. There is also a new menu for the Energy Lab POC that provides two menu options: Create Quality Data Sheet and History Folder.
Vendor Create Statement of Quality Worksheet Vendor Create Statement of Quality Worksheet Vendor Create Statement of Quality Worksheet February 2017 This is a demonstration of a Vendor creating a Statement of Quality Worksheet through the "Statement of Quality" tab.

The purpose of this ECP was to update the Energy Receiving Report workflow e-mails to the Inspector DoDAAC for Energy Receiving Reports created with CoC or ARP selected. An entry has been added, as appropriate, that the document was released per CoC or ARP terms.

In addition, an edit has been added upon document creation to verify that, if CoC is selected, the contract actually contains the CoC clause. If the appropriate clause is not present, the system will prevent creation of a document with CoC selected.

The CoC clause requirements will apply to all Receiving Reports, Energy Receiving Reports and Reparable Receiving Reports created against contracts stored in EDA as PDS data.

This includes the COMBO method of creation for these documents as well as create via the Web, FTP and EDI.


DLA Energy TQ CoC/ARP Vendor Email Notification Demo:

Document Demo Doc Last Updated Notes
DLA Energy TQ CoC/ARP Vendor Email Notification DLA Energy TQ CoC/ARP Vendor Email Notification DLA Energy TQ CoC/ARP Vendor Email Notification February 2017 This is an overview of the DLA Energy TQ COC/APR Vendor Email Notification. The workflow email to the Inspector has been modified to insert a statement if the vendor selected COC or ARP while creating the Energy Receiving Report.

5.11.0 Release

The purpose of this ECP was to make available the Foreign Military Sales data requirements (FMS Case Number, etc.) for data entry for Reparable Receiving Reports and Invoice and Reparable Receiving Report (Combos).


FMS Requirements for RRRs Demo:

Document Demo Doc Last Updated Notes
FMS Requirements for RRRs FMS Requirements for RRRs FMS Requirements for RRRs December 2017 This overview of ECP1043 describes the updates to the FMS Requirements for Reparable Receiving Reports/Combos. Explained are the new FMS checkboxes, the additional fields on the Report and new pages.

The purpose of this ECP was for WAWF to require the Initiator to input ‘D’, ‘O’, or ‘S’ for WAWF Energy Receiving Reports and Energy Combo documents where a FOB indicator is present.

WAWF will no longer be systematically defaulting the FOB field to ‘S’.


DLA Energy FOB Indicator Required Demo:

Document Demo Doc Last Updated Notes
DLA Energy FOB Indicator Required DLA Energy FOB Indicator Required DLA Energy FOB Indicator Required December 2017 This is an overview of DLA Energy FOB Indicator Required. For Energy Receiving Report and Energy COMBOs, the FOB will be mandatory to create.

The purpose of this ECP was to default Web/EDI/FTP Submission CLIN values on a Cost Voucher to:

  • Unit of measure to a specific value
  • Quantity = 1
  • Unit price = Amount to be invoiced

The Vendor will enter a value for only quantity or unit price which will always equal the line item amount total.

Extracts will not be impacted and will extract the CLIN values as they do today.


Cost Voucher Line Item Field Updates Demo:

Document Demo Doc Last Updated Notes
Cost Voucher Line Item Field Updates CV Line Item Field Updates CV Line Item Field Updates December 2017 This is an overview of the CV Line Item Field Updates. "Unit Price" is now labeled "Amount Billed" on the Line Item Details page.

 Previous  Close