What's New In Wide Area Workflow (WAWF) v4.0

WAWF Version 4.0 includes the following enhancements:

ECP 0425 "Electronic Submission of Attachments in EDI"
The community has requested the capability to submit attachments via EDI. Currently, Vendors who submit EDI transactions to WAWF have to use the Web to attach the documents. This creates an additional manual effort for the vendor. In addition, transactions that are not source Inspected and Accepted may result in duplicate transactions to the payment system. Creating additional manual work for the Government where the payment system does not automatically handle duplicates.

Implementation of the requirements within this ECP will provide the Vendors the capability to submit attachments electronically via EDI without requiring manual intervention. The attachments will be placed within an EDI 841Transaction Set, which identifies that the document contains an attachment. The EDI 841 Transaction will be submitted in conjunction with the initiating transaction set that is associated to the attachment, i.e. EDI 810, 857 or 856. Upon import into the WAWF application, the attachment will be viewable. (Reference the 841 Related BIN Segment Instruction Document and/or the 841 WAWF 4010 EDI Detail Document)

ECP 0470 "Add Cost Voucher and Invoice 2-in-1 document types for EBS"
The community has requested the WAWF application be enhanced to provide Vendors the capability to select and process Cost Vouchers and 2n1 documents for the Enterprise Business System (EBS) Pay Office (SL4701). Adding the Cost Voucher and 2n1 document types will allow DLA Vendors the ability to utilize all document type currently available in WAWF.
Implementation of the requirements within this ECP will provide Vendors the capability to create and process Cost Vouchers and 2-in-1 documents for the EBS Pay DODAAC SL4701.

ECP 0485 "Line Item Structure"
The community has requested the WAWF application be modified to capture Exhibit Line Items, Informational Line Items and Separately Identified Sub-Lines within the WAWF receiving and property Transfer functionality (IAW DFARS 204.7104). In addition, allow contractors to submit additional pRFID data that will reflect the actual physical package configuration by enabling multiple pack loops when CLIN/SLIN-level alone is not sufficient for Full Material Visibility (DFARS 252.211-7006 applies).

Implementation of the requirements within this ECP will provide the capability to capture Exhibit Line Items and both the Informational and Separately Identified Sub-Lines on a Receiving Report and provide Multiple Box Packing capability within the pRFID functionality.

ECP 0489 "Add Line Item Warranty Indicator"
The community has requested the WAWF application be modified to provide Contractors the capability to identify CLIN, SLIN, or ELIN items that are supported with a warranty.

Implementation of the requirements within this ECP will provide the capability to identify items on a Receiving Report or Property Transfer document that have an applicable warranty associated to them.

ECP 0491 "Government Initiator On Behalf of Business Concern"
The community has requested the capability for a Government Acceptor to prepare and submit a Non-Federal Miscellaneous Payment on behalf of a Vendor, Business or Individual via the Web, EDI or SFTP. The functionality would provide the government initiator the capability to create a Miscellaneous Payment using the Vendor’s CAGE Code/Employee Identification Number (EIN), EIN or Social Security Number (SSN). This functionality will require the initiator to provide substantiating information (attachment) to support the payment. In addition, the community has requested the capability for a Government Acceptor to prepare and submit a Federal Miscellaneous Payment via of EDI or SFTP.

Implementation of the requirements within this ECP will permit a Government Initiator the capability to create and submit a Non-Federal Miscellaneous Payment Invoice on behalf of a Vendor, Business or Individual via the Web, EDI or SFTP. In addition, provide the Government Initiator the capability to create and submit a Federal Miscellaneous Payment Invoice via EDI or SFTP.

ECP 0499 "Outbound Using Web Services To View Attachments"
The community has requested the capability to inform locations receiving either legacy or standard transactions that an attachment exists for the applicable document and to permit all external users the capability to view attachments without having to log into the WAWF application.

Implementation of the requirements within this ECP will provide an external user the capability to view an attachment without having to log into the WAWF application. To accomplish this requirement the following Web Services functionality has been incorporated:

The external user will access their System Web Service Client to request a list of URLs to the document’s attachments by using methods in the Web Service functionality.

User must supply to the Web Service method call the following information to obtain a list of URLs associated with an acquisition document:

• System id /Password
• CAGE Code
• Contract Number
• Delivery Order Number
• Shipment Number

To obtain a list of URL's associated with a Government Furnished Property document the user will be required to enter the following information:

• System id /Password
• CAGE Code
• Contract Number
• Shipment Number
• Delivery Order Number
• From Location Code

The external user’s request to the WAWF Web Service will return a list of specific URLs matching the criteria provided by the requestor.

Upon return of the list of URLs, the external user will have the option to select the specific attachment for review.

Instructions and other documents supporting this functionality can be accessed by click the following links created under "About WAWF" within the application:

• Link: Attachments WSDL File
• Link: Web Service Java Client File
• Link: Using Web Service Java Client Help

ECP 0500 "Update of Construction Invoice Process"
The community has requested new functionality within the WAWF application to process Navy Construction/Facilities Invoices. This particular functionality will allow Vendors the capability to create and submit a construction or facility invoice on behalf of the Navy via the Web, SFTP or EDI.

Implementation of requirements within this ECP will provide the Vendors the capability to create and submit Navy Construction or Facility Invoices. The revised functionality will incorporate business processes and procedures to support of the Navy’s field components, providing them capability to process, review and accept Construction or Facility Invoices using the WAWF application functionality.

ECP 0503 "Standard Transactions Phase II - Standard Invoices"
The community has requested Standard Transaction Phase II-Standard Invoices be incorporated within the WAWF application. The Phase II functionality will expand upon Standard Transaction Phase I functionality to include Standard Invoice/Voucher transactions, which will apply to Commercial Invoices, Commercial Invoice Fast Pay, Commercial Invoice 2n1, Cost Vouchers, Grants Grant and Cooperative Agreement, Commercial Item Financing, Performance Based Payment and Progress Payments. The system will provide enhanced routing by further defining the "sign up" process to identify the payment request source document type for an extract and establish a new Pay Office type to support the "end state".

Implementation of the requirements within this ECP will provide an external system to receive Standard Transactions in support of Commercial Invoices, Commercial Invoice Fast Pay, Commercial Invoice 2n1, Cost Vouchers, Grants Grant and Cooperative Agreement, Commercial Item Financing, Performance Based Payment and Progress Payments. The functionality will allow an external entity to sign up to receive Workflow, Informational or Accounting standard extract by the type of document.

Document Types Allowed
If the Standard Pay DoDAAC is signed up for Standard Pay Request (Workflow), the following document types may be created.
• CI, CIFP, CV Direct, PPR Post Pay
If the Standard Pay DoDAAC is signed up for Standard Approved Pay Request (Workflow), the following document types may be created.
• Grant Vouchers, CV Interim, CV Final, CI2N1, PBP, CIF, PPR Pre Pay, PPR Post pay (loss condition)
If the Standard Pay DoDAAC is signed up for Standard Acceptance/Approval notice (Informational), the following document type may be created.
• RR
In addition to what is noted in the above bullets, if the Standard Pay DoDAAC is signed up for Standard Pay Request (Workflow) AND signed up for Standard Acceptance/Approval notice (Informational), the following document type may also be created
• COMBO

Specific Extracts
Each specific standard extract is associated with a standard extract type as follows:

Standard Shipment Notice (Phase I)

• Standard Ship (Informational)
• Standard Ship (Workflow)
Standard Acceptance/Approval Notice (Phase I)
• Standard Acceptance
• Standard Acceptance (Accounting)
Standard Pay Request - Payment request submitted by a vendor to the government (Phase II):
• Standard Pay Request (Workflow)
• Standard Pay Request (Informational)
• Standard Pay Request (Accounting)
Standard Approved Pay Request - Payment request forwarded by one government user to another government user (Phase II):
• Standard Approved Pay Request (Workflow)
• Standard Approved Pay Request (Information)
• Standard Approved Pay Request (Accounting)

SAM Functionality
The system will permit the SAM to sign up an external system to receive a Standard Transaction by requiring the external system to identify:

• The specific role within the WAWF application affected
• The location code (DoDAAC, CAGE or Agency Accounting Identifier)
• The routing activity indicator associated to that location code
• The document type
• The extract type within that document type to base the extraction upon

Route Capability
The application will provide the capability to route "Standard Transactions" by these codes:

• Ship To DoDAACs
• Pay DoDAACs
• Admin DoDAACs
• Issue By DoDAACs
• Inspect By DoDAACs
• Accept at Other DoDAACs
• Agency Accounting Identifier or alias (e.g., AAA or FSN)

Standard Pay System
Provide a new standard Pay System Indicator that will apply to all document types that will allow for new Pay DoDAACs (validated against DAASC).

Standard Pay Offices will have no PSS edits applied to the data elements; they get WAWF edits for min/max

Standard Pay Offices will be sent only standard transactions

The system will permit the creation of a document when the location code entered equates to a Standard Pay Office and when that Pay Office permits the processing of that document type

ECP 0505 "Corrections Processing"
The community has requested the methodology to standardize the corrective process within the Standard Transaction functionality. The revised corrective functionality will provide the capability to ensure external entities (Logistic, Property, Accounting or Entitlement Systems) receive the appropriate extract submissions upon the original submission/acceptance/approval of a document, the resubmission/reacceptance/re-approval of a document or the cancellation of a document (voided).

Implementation of the requirements within this ECP will provide the capability for an external system to receive the appropriate standard extracts (original, corrective or cancellation) that are provided based on the status of a specific document within WAWF.

Relevant Definitions

• The following definitions will apply to standard extract submissions:
• Transaction Purpose Code "OO" original submission
• Transaction Purpose Code "CO" corrective submission
• Transaction Purpose Code "01" cancellation submission
  

Corrective Process/Functionality

Upon resubmission/reacceptance/re-approval of a specific document, the WAWF application will generate a corrective standard extract to the external system signed up to receive an external standard extract.

Upon cancellation (Voided) of a specific document, the WAWF application will generate a cancellation standard extract to the external system signed up to receive an external standard extract.