Home Random Page


CATEGORIES:

BiologyChemistryConstructionCultureEcologyEconomyElectronicsFinanceGeographyHistoryInformaticsLawMathematicsMechanicsMedicineOtherPedagogyPhilosophyPhysicsPolicyPsychologySociologySportTourism






EDI Transaction Sets

Data is submitted from the Vendors or Government entity using the standard American National Standards Institute (ANSI) X12 Transaction Sets. For detailed information regarding the rules and format of these Transaction Sets, please refer to the iRAPT EDI Implementation Guides prepared for the Department of Electronic Business Program Office. The iRAPT EDI Implementation Guides for Vendors are posted at the following Web site: https://wawf.eb.mil/.

The X12 formatted message is then received by the DoD GEX (Global Exchange Services) and translated to a User Defined Format (UDF). The information received is verified for errors and validated prior to introduction into the iRAPT system. E-mail confirmation notification is used to inform submitters if information was successfully accepted into the iRAPT application or rejected due to electronic errors. If data is rejected the e-mail is sent to the Initiator containing an appropriate error message(s) if necessary. Submitters should maintain a copy of any data sent until they receive an iRAPT confirmation e-mail stating that the data has been accepted successfully. Once the information is entered into the iRAPT application, it may be viewed and processed in document form on the Web.

The following table contains a list of the EDI Transaction Sets imported within iRAPT:

Table 6-2: EDI Transactions Sets Imported Within iRAPT

EDI Transaction Set Functionality
810C Commercial Invoice
810CV Cost Voucher
810C Misc Pay Miscellaneous Pay Invoice
810C NSI Navy Shipbuilding Invoice
810C Commercial Invoice (2n1)
810P Progress Pay Invoice
810PBP Performance Based Payment & Commercial Item Financing Invoice
810V Grants, Cooperative Agreement Vouchers, and Non-Procurement Instrument Vouchers
Telecom Invoice
Financial Information Reporting
Specifications/Technical Information
856 GFP Property Transfer Document
856 Pack/RFID Update Receiving Report Update – Pack/RFID Information
856 RRR Reparables Receiving Report
Receiving Report
COMBOs (Invoice/Receiving Report)
857 RCOMBO Reparables COMBO (Invoice/Receiving Report)
861 Navy Receiving Advice/Acceptance Certificate From Navy ERP/ILSMIS
861 UDF – Std. External Acceptance Standard External Acceptance – Inbound to iRAPT.
Receiving Advice/Acceptance Certificate From Distribution Standards System (DSS) of the Defense Logistics Agency (DLA)

XML Files

The inbound acknowledgement data via the 824 EDI Transaction Set – (Application Advice) from DFAS (Defense Finance and Accounting Service) or the Services/Agencies Accounting Systems basically provides the acknowledgement data via an EDI format to GEX, which is then converted to an Extensible Markup Language (XML) format to deliver inbound to iRAPT. Once these files have been submitted to iRAPT, the information provided will be used to either update the document status or set the flag to release the payment files to the appropriate Entitlement System. Either way, once the inbound XML data is received by iRAPT, an e-mail is sent to the Initiator. Once the initial Entitlement System 824 is processed successfully, all other 824s will be ignored.



The following table contains a list of the XML Files imported within iRAPT:

Table 6-3: XML Files Imported Within iRAPT

EDI Transaction Set Functionality
824 Navy Reject XML WAWF ACK NavyRejection Acknowledgment
824 Navy XML WAWF ACK Acknowledgment - Navy Acknowledgment for 810V
824 NSI XML WAWF ACK Navy Shipbuilding Invoice Acknowledgment
824 XML Accounting System WAWF ACK Services/Agencies Accounting System
824 XML WAWF ACK Acknowledgement Received from DFAS Entitlement Systems
MyInvoice XML WAWF ACK Information provided from the myInvoice System

Date: 2016-04-22; view: 974


<== previous page | next page ==>
Defense Logistics Agency | General Description
doclecture.net - lectures - 2014-2024 year. Copyright infringement or personal data (0.007 sec.)