Home Random Page


CATEGORIES:

BiologyChemistryConstructionCultureEcologyEconomyElectronicsFinanceGeographyHistoryInformaticsLawMathematicsMechanicsMedicineOtherPedagogyPhilosophyPhysicsPolicyPsychologySociologySportTourism






Sending attachment files to iRAPT via EDI

Vendors should only use the 841 EDI Transaction Set to send attachments to iRAPT via EDI. Multiple attachments may be sent in a single transaction set.

Vendors should not use the 841 EDI Transaction Set for anything other than sending attachments to iRAPT.

Enveloping instructions for attachment data should only contain one document (i.e. one Transaction Set) transmitted with one 841 in an ISA/IEA. Example: only one shipment or finance document with its associated attachment(s) may be sent per interchange

Example:

ISA

GS^IN

ST^810

<810 segments here>

SE

GE

GS^SP

ST^841

<841 segments here>

SE

GE

IEA

Sending attachment files to iRAPT via FTP

Vendors may submit attachments that are related to an EDI document via FTP for some EDI transaction types. For more details about submitting attachments related to EDI transactions via FTP, see the iRAPT Vendor Guide applicable to each EDI transaction type.

Sending CDRL attachment files to iRAPT

CDRL attachments may only be submitted at the Line Item level of a transaction in association with an ELIN. CDRL attachments are not allowed for One Pay or EBS pay systems and may not be allowed for all transaction types. All CDRL information, including attachment file name (with file type) and System UID, must be submitted within the ELIN construct, not at the document level. For more details about submitting CDRL attachments, see the iRAPT Vendor Guide applicable to each EDI transaction type.

13 Attachments to This EDI Guide

1. Unit of Measure Table – Word document that lists the Unit of Measure Codes. Please refer to this list to review the DoD/ANSI X12 description and send ANSI X12 codes for EDI transmissions. File name: Unit_of_Measure.doc

2. iRAPT Data Element/Segment Cross Reference Documents – Word document that details in table format the usage of Segments and Data Elements arrayed in Transaction Set Order.

Commercial Invoice

Word document, File name: 810C_WAWF_4010_EDI_Detail.doc

 

Misc Pay Invoice

Word document, File name: 810C_MiscPay_WAWF_4010_EDI_Detail.doc

Navy Shipbuilding Invoice

Word Document, File name: 810C_NSI_WAWF_4010_EDI_Detail.doc

Cost Voucher

Word document, File name: 810CV_WAWF_4010_EDI_Detail.doc

 

Grant and Cooperative Agreement

Word document, File name: 810V Grants WAWF 4010 EDI Detail

 

Progress Payment

Word document,File name: 810P_WAWF_4010_EDI_Detail.doc

 

Performance Based Payments/Commercial Item Financing

Word document, File name: 810PBP_WAWF_4010_EDI_Detail.doc

Consolidated Service Invoice/Statement (Telecom)
Word document, File name: 811_WAWF_4010_EDI_Detail.doc

Receiving Report
Word document, File name: 856_WAWF_4010_EDI_Detail.doc

 

Receiving Report for Pack Update

Word document, File name: 856_Pack_Update_WAWF_4010_EDI_Detail.doc



 

Government Furnished Property

Word document, File name: 856_GFP_WAWF_4010_EDI_Detail.doc

 

Reparables Receiving Report

Word document, File name: 856_RRR_WAWF_4010_EDI_Detail.doc

 

COMBO

Word document, File name: 857_WAWF_4010_EDI_Detail.doc

Reparables COMBO

Word document, File name: 857_RCOMBO_WAWF_4010_EDI_Detail.doc

 

Specifications/Technical Information (attachments via EDI)

Word document, File name: 841_WAWF_4010_EDI_Detail.doc

Word document, File name: 841 Related BIN Segment Instructions

 

 

3. Certificate of Conformance (CoC) - Word document stating that when Vendors submit receiving reports via EDI, contractors will execute Certificate of Conformance (COC) by including the appropriate indicator in the transaction rather than through the inclusion or attachment of the text of the certificate. File Name: COC.doc

4. Construction Certificate - Word document - Construction Certification.
File Name: CICON.Cert.doc

5. Performance Based Payment Certificate - Word document - Performance Based Payment Certification. File name: PBP_Cert.doc

6. Mode of Shipment Codes– Word document that lists the Mode of Shipment codes.
File name: Mode_of_Shipment.doc

Associations

The complete list of EDI transaction sets can be found in the ANSI ASC X12 – Electronic Data Interchange X12 Standards, Version 4010. This information is available from:

Data Interchange Standards Association, Inc. (DISA)

http://www.disa.org

The Federal/DOD Implementation Conventions for ANSI X.12 may be obtained from:

http://www.defenselink.mil/bta/fedebiz/index.shtml

15 ISA/GS Enveloping Instructions

An example of interchange enveloping information is provided in the following tables. Detailed instructions may be found at this link: http://www.defenselink.mil/bta/FedeBiz/private/edit/document/guidelines/part10/Part_10_004030.pdf

Field Types included within the interchange table include:

· Nv Numeric Field where v = number of decimal positions, decimal is implied (i.e. 300 will be read as 3.00)

· R Decimal number. If value includes decimal, then iRAPT requires decimal point and value be sent: iRAPT will NOT imply or assume decimal points. Examples:

o 300 will be read into iRAPT as “300”

o 3.00 will be read into iRAPT as “3”

o 3.5 will be read into iRAPT at “3.5”

· ID Identifier

· AN Alpha/Numeric String

· DT Date/Time – All date Fields use this format: CCYYMMDD

· TM All time Fields use this format: HHMMSS


Note: The component element separator (ISA16) as well as the sub-element separator and segment terminator are prohibited in the transaction data fields.

Note: When submitting transactions for the 810P (GS08 = 004010D810P1), please do not include in the same file as other transaction types. 810Ps must be submitted in a separate transaction containing only other 810Ps.

 

 

Table 13‑5: ISA – Interchange Control Header

Data Elem. # X12 Name Format Min/Max Req. Des Entry/Implementation Note Type
ISA01 Authorization Information 2/2 M 00 – No Authorization Information Present ID
ISA02 Authorization Information 10/10 M Blanks AN
ISA03 Security Information Qualifier 2/2 M 00 – No Security Information Present ID
ISA04 Security Information 10/10 M Blanks AN
ISA05 Interchange ID Qualifier 2/2 M As instructed by VAN ID
ISA06 Interchange Sender’s ID 15/15 M EDI Identifier – Assigned by VAN AN
ISA07 Interchange ID Qualifier 2/2 M ZZ ID
ISA08 Interchange Receiver’s ID 15/15 M DMCCOLUMBUS or DMCOGDEN (Contact VAN to find out which. Entry is dependent on the selected VAN and its primary GEX connection.) AN
ISA09 Interchange Date 6/6 M Assigned by the Translation Software DT
ISA10 Interchange Time 4/4 M Assigned by the Translation Software TM
ISA11 Interchange Control Standard Identifier 1/1 M U – US community of ASC X12 ID
ISA12 Interchange Control Version 5/5 M Assigned by the Translation Software ID
ISA13 Interchange Control Number 9/9 M Assigned by the Translation Software N0
ISA14 Acknowledgement Requested 1/1 M 0 – No Acknowledgment Requested 1 – Interchange Acknowledgment Requested ID
ISA15 Test Indicator 1/1 M T – Test Data P – Production Data ID
ISA16 Component Element Separator 1/1 M As established within senders Translation Software AN

 

 

Table 13‑6: GS – Functional Group Header

Data Elem. # X12 Name Format Min/Max Req. Des Entry/Implementation Note Type
GS01 Functional ID Code 2/2 M IN – Invoice Information (810s) SH – Ship Notice Manifest (856) BS – Shipment & Billing Notice (857) RC – Receipt Notice and Acceptance (861) SP – Specifications/Technical Information (841) CI – Consolidated Invoice (811) MD – Department of Defense Inventory Management (527) ID
GS02 Application Sender’s Code 2/15 M Determined by Contractor and VAN (i.e. Cage Code) AN
GS03 Application Receiver’s Code 2/15 M ANSI allows 2/15, yet for iRAPT, a Contractor/Vendor must use one of the following values. WAWF01 – Wide Area Work Flow for Production. WAWF02 – Wide Area Work Flow For Testing. WAWF05 – Wide Area Work Flow for 4010 for Testing. (DSS-LOG) WAWF06 – Wide Area Work Flow for 4010 for Production. (DSS-LOG) WAWF07 – Wide Area Work Flow for 4010 for Testing (MISC PAY) WAWF08 – Wide Area Work Flow 4010 for Production (MISC PAY) WAWF09 – Wide Area Work Flow for 4010 for Testing (GFP) WAWF10 – Wide Area Work Flow 4010 for Production (GFP) WAWF11 – Wide Area Work Flow 4010 for Testing (Standard Transactions) WAWF12 – Wide Area Work Flow 4010 for Production (Standard Transactions) AN
GS04 Group Date 8/8 M Assigned by Translation Software DT
GS05 Group Time 4/8 M Assigned by Translation Software TM
GS06 Group Control Number 1/9 M Assigned by Translation Software N0
GS07 Responsible Agency Code 1/2 M X – Accredited Standards Committee X12 ID
GS08 Version/Release/Industry ID 1/12 M 4010 Filers: Enter appropriate version of the transaction set being submitted. (12 characters in bold below). 810C: 004010D810C1 2 December 2003 810V: 004010D810V2 16 January 2004 810P: 004010D810P1 25 November 2003 811: 004010D811T1 22 July 2009 856: 004010F856_3 November 01, 2004 857: 004010D857_2 5 January 2005 841: 004010F841P0 3 NOV 2003 527R: 004010F527D5 January 07, 2013 AN

 

Table 13‑3: GE – Functional Group Trailer

Data Elem. # X12 Name Format Min/Max Req. Des Entry/Implementation Note Type
GE01 Number of Transaction Sets included. 1/6 M Number of Transaction Sets (ST/SE pairs) included in the Functional Group. N0
GE02 Group Control Number 1/9 M Must match GS06 N0

 

Example:

 

GE*1*42204

Table 13‑3: IEA – Interchange Control Trailer

Data Elem. # X12 Name Format Min/Max Req. Des Entry/Implementation Note Type
IEA01 Number of Included Functional Groups. 1/5 M Number of included functional groups (GS/GE pairs) in the interchange. N0
IEA02 Interchange Control Number 9/9 M Must match ISA13 N0

 

Example:

 

IEA*2*000037746

 

Standard usage of ISA/IEA and GS/GE pairs in a WAWF EDI transaction:

ISA*00* *00* *ZZ*1NGC1 *ZZ*DMCOGDEN *071112*1244*U*00401*000037746*0*P*~

GS*IN*1NGC1*WAWF02*20071112*1244*42204*X*004010D810C0

ST*810*123000004

<body of 810>

SE*22*123000004

GE*1*42204

IEA*1*000037746

Sample of an ISA/GS for sending in a WAWF EDI transaction with attachments (sample shown is an 810 with the corresponding 841):

ISA*00* *00* *ZZ*1NGC1 *ZZ*DMCOGDEN *071112*1244*U*00401*000037746*0*P*~

GS*IN*1NGC1*WAWF02*20071112*1244*42204*X*004010D810C0

ST*810*123000004

<body of 810>

SE*22*123000004

GE*1*42204

GS*SP*1NGC1*WAWF02*20080516*1244*33445566*X*004010F841P0

ST*841*4001

<body of 841>

SE*6*4001

GE*1*33445566

IEA*2*000037746

 

*See Section 11 regarding sending attachments to iRAPT via EDI.


Date: 2016-04-22; view: 786


<== previous page | next page ==>
General Description | Resistors in Series and Parallel
doclecture.net - lectures - 2014-2019 year. Copyright infringement or personal data (0.004 sec.)