EDI 856 TEST PROCEDURES

Transcription

1 EDI 856 TEST PROCEDURES FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT

2 EBMX Connectivity Requirements EBMX supports multiple communication protocols. Each trading partner is expected to send and receive documents with the protocol of their choice. An EBMX communication/migration overview containing a summary of these protocols is available at Select Electronic Business Message exchange(ebmx). CHASE Prerequisites 1. You must be able to wrap the 856 ASN transaction with: ISA/IEA interchange version You must be able to conform to FCA Group s implementation of the ANSI ASC X12 transaction set: 856--Ship Notice/Manifest (ASN) (version CHRY) 3. You must be able to receive and conform to FCA Group s implementation of the ANSI ASC X12 transaction sets: Application Advice (version CHRY) Functional Acknowledgement (version ) Additional Requirements: o o o Only one GS/GE is allowed per ISA/IEA. Only one ST/SE is allowed per GS/GE. Only an 856 is allowed inside the ISA/IEA enveloped (e.g. 810s, 997s or any other transaction sets are NOT allowed in the same envelope with the 856). CHASE Requirements FCA requires the following functions to be successfully tested: 1. Send ASNs (856) using your selected communication protocol. 2. Receive Functional Acknowledgement (997) and Application Advice (824) using your selected communication protocol. 07/23/ FCA US

3 CHASE Testing Procedures NOTE: If you experience problems with connectivity, bad or missing data, or installation issues, it is your responsibility to resolve these issues before continuing testing. 1. Generate a test 856 ASN/ASC based on the FCA Group s Implementation Guide for the Ship Notice/Manifest (856) transaction set. a. Use your FCA supplier id as a test supplier code. That is, put your FCA supplier id" in the ISA06 (Interchange Sender ID) element of the ISA (Interchange Control Header). NOTE: In ISA08 use as the receiver for an ASN and use 04000FC in ISA08 for an ASC. ASN ISA*00* *00* *ZZ* Your FCA Id *ZZ*04000 * *1200*U*00204* *0*P*<~ ASC ISA*00* *00* *ZZ* Your FCA Id *ZZ*04000FC * *1200*U*00204* *0*P*<~ Note: for clarity, the segment terminator will not be included in the following segment descriptions. Also, put your FCA supplier id in the GS02 (Application Sender Code) element of the GS (Functional Group Header) segment. NOTE: In GS03 use as the receiver for an ASN and use 04000FC in GS03 for an ASC. ASN GS*SH*Your FCA ID*04000*890307*1200*20*X*002040CHRY ASC GS*SH*Your FCA ID*04000FC*890307*1200*20*X*002040CHRY For the N1 segments, put "01000AA" in the N104 (Identification Code) element of the N1 (Name) segment with the "SU" (Released Supplier) qualifier in the N101 (Entity Identifier Code) element. Use "01000BB" in the N104 (Identification Code) element of the N1 (Name) segment with the "SF" (Ship From) qualifier in the N101 (Entity Identifier Code) element: N1*SU**92*01000AA N1*SF**92*01000BB b. Use "04012" as the test FCA receiving plant. That is, for the N1 segments for the Ship To Location (N101 = "ST") and Ultimate Destination (N101 = "MA"), populate data element N104 with "04012" in the N104 (Identification Code) element of the N1 (Name) segment with the "ST" (Ship To) qualifier in the N101 (Entity Identifier Code) element. Data element N104 (Identification Code) element of the N1 (Name) segment with the "MA" (Ultimate Destination) qualifier in the N101 (Entity Identifier Code). N1*ST**92*04012 N1*MA**92* /23/ FCA US

4 c. Use your FCA assigned supplier code as the test Bill of Lading number. This will distinguish your tests from those of other suppliers. That is, put your FCA assigned supplier code in the REF02 (Reference Number) element of the REF (Reference Numbers) segment with the "BM" (Bill of Lading) qualifier in the REF01 (Reference Number Qualifier) element. REF*BM*63909 d. Use your FCA assigned supplier code as the test Packing Slip number. This will distinguish your tests from those of other suppliers. Examples: REF*PK*63909 e. Use "0AAAAAA1BB" as the test Part Number. That is, put "0AAAAAA1BB" in the LIN03 (Product/Service ID) element of the LIN (Item Identification Detail) segment with the "BP" (Buyer's Part Number) qualifier in the LIN02 (Product/Service ID Qualifier) element. LIN**BP*0AAAAAA1BB*EC*REL f. Complete the remaining segments and elements of the ASN according to the guidelines in FCA's Implementation Guide for the Ship Notice/Manifest (856) transaction set. 2. Receive the corresponding Functional Acknowledgement (997) and the Application Advice (824). Please note that the EDI communications contact information is on page 11. a. If your ASN data contains syntax errors, you will receive a 997 with the syntax errors noted in the AK3 and AK4 segments. There will also be the message, "SYNTAX ERROR - REVIEW FUNCTIONAL ACKNOWLEDGEMENT (997)" in the NTE segment of the 824. This is a translation software problem and you should contact your software provider for assistance. b. If you receive only an 824 (without a 997) with one of the following messages in the NTE segment, you should take the corresponding corrective action: "INTERCHANGE SENDER ID IS NOT ON TRADING PARTNER FILE" Check your outgoing ISA segment to make sure you have your proper supplier code in the Interchange Sender ID (ISA06). If the supplier code is correct, contact EDI Communications to verify that you are properly set up on the FCA trading partner files. "INTERCHANGE RECEIVER ID IS NOT EQUAL TO 04000" Check your outgoing ISA segment to make sure you have "04000" in the Interchange Receiver ID (ISA08). "APPLICATION SENDER ID IS NOT ON TRADING PARTNER FILE" Check your outgoing GS segment to make sure you have your proper supplier code in the Application Sender Code (GS02). If the supplier code is correct, contact EDI Communications to verify that you are properly set up on the FCA trading partner files. 07/23/ FCA US

5 "APPLICATION RECEIVER ID IS NOT EQUAL TO 04000" Check your outgoing GS segment to make sure you have "04000" in the Application Receiver Code (GS03). "UNABLE TO INTERPRET EDI DATA RECEIVED" This can be caused by several conditions including, but not limited to: o The ISA segment is the improper length. It must always be exactly 106 bytes o The element separator and sub-element separator are the same character o A missing segment terminator o ISA segment is missing Refer to the "Enveloping" section for the correct format of the ISA segment "NO EDI DATA RECEIVED BY THE CHASE SYSTEM" This usually occurs if FCA receives an envelope without any data or non-x12 data is within the envelope "INVALID FAST BATCH TRANSACTION" Check your outgoing GS segment to make sure you have "SH" in the Functional ID (GS01) and check your outgoing "ST" segment to make sure you have "856" in the Transaction Set ID Code (ST01). Any other values will produce this error message. If you encounter any of these conditions, contact your software supplier for assistance! c. Under normal conditions you will receive both the 997 and the Examine the 997 Functional Acknowledgement returned by the CHASE ASN System. a. Successful delivery of an 856 ASN transaction will result in a 997 Functional Acknowledgement containing only AK1, AK2 and AK5 segments, followed by an AK9 segment. b. Should an ANSI X12 syntax error condition arise, the 997 will contain AK3 and AK4 segments as well as the AK1, AK2, AK5 and AK9 segments. c. If the AK3 and AK4 segments are present due to syntax errors, see Appendix C, "997 ERROR CODES," for an explanation of the error codes contained within the AK3 and AK4 segments. Syntax errors are caused by translation software. Contact your software supplier for assistance. 4. Examine the 824 Application Advice returned by the CHASE ASN System. a. Successful delivery and processing of an 856 ASN will result in an 824 Application Advice that does not contain TED (Technical Error Description) or NTE (Note) segments. These two segments are only used to describe processing errors. b. Should an error condition arise due to bad data, error messages will be returned in the TED and NTE segments. The error code(s) contained in the TED segment will be found in the TED01 (Application Error Condition) element. A text description of the field in error is in the TED02 (Free Form Message) element. A copy of the bad data is in the TED07 (Copy of Bad Element) element. TED*11*ASN-PART/PLANT/SUPPLIER***** /23/ FCA US

6 Error messages from the CHASE ASN system are contained in the NTE segment and will be found in the NTE02 (Free Form Message) element. NTE*LIN*INVALID PART/PLANT/SUPPLIER COMBINATIONN/L See "FCA 824 ERROR MESSAGES" for a list of error messages contained within the TED and/or NTE segments. NOTE: In the test environment, the year-to-date totals will always disagree. This is a non-fatal FCA System error, and the CHASE ASN System will process this ASN. 5. Send FCA an 856 ASN transaction to cancel a previous successful ASN and receive the corresponding 997 Functional Acknowledgement and 824 Application Advice. That is, element BSN01 (Transaction Set Purpose Code) must contain a "01" (zero, one) for cancellation as opposed to "00" (zero, zero) for original. The Supplier Code, Receiving Plant, Ship Date, Packing Slip Number, Bill of Lading Number, and ASN Shipped Quantity must be the same as those on the original ASN being cancelled. These fields are used to match the two transactions. If all fields do not match, the cancellation will fail and you will receive the ASN System Error Message "CANCELLATION TRANS SUBMITTED AND NO MATCHING ASN". 6. When you are able to send and cancel 856 ASNs and receive 997 Functional Acknowledgements and 824 Application Advice s without errors, you have successfully completed CHASE ASN System testing. 7. When you have completed testing of your ability to perform all the functions listed above using your test data, contact: Jeff Besh - (248) You will need to supply the Ship Date, Bill of Lading, and Packing Slip numbers of your successful ASN tests for confirmation. 8. You are now ready to send production ASNs to the FCA CHASE ASN System. 07/23/ FCA US