Electronic Commerce

856 Customer Advance Ship Notice (ASN) Testing

856 CUSTOMER ADVANCE SHIP NOTICE (ASN) TESTING

This document is intended to describe the steps required to create an EDI 856 test file for use in
internal or external (partner) testing.

REQUIRED INFORMATION
 Testing partner’s ship-to, sold-to, ship-to DUNS
 Number of an existing delivery for testing partner in QA2

CONFIGURATION
 Complete the configuration referenced in the Trade Guide, Enterprise, and AI Routing steps
of the “EDI New Partner/Document Checklist”
 Contact the Customer Master Data team and ask that they update the ‘Customer grp. 1’ field
of the ship-to to be used for testing to either ‘CS’ or ‘UN’ depending on testing partner
requirements

INSTRUCTIONS
 Go to transaction VL03N and display the testing partner’s delivery

 From the ‘Outbound delivery’ drop down menu select ‘Display<->Change’

439211426.doc Page 1 of 5
 Electronic Commerce
856 Customer Advance Ship Notice (ASN) Testing

 From the ‘Extras’ drop down menu select ‘Delivery’ output and ‘Header’

TO CREATE A NEW OUTPUT

If no output exists for a new partner then use the following steps to create one. These steps
can also be used to create a new output off a delivery using a different generic partner profile.

 Fill in the output fields with the following information:

Output
Medium PartFunct. Partner Language
type
ZASN EDI SH 8758 EN

 Hit ‘Enter’ and an error message will display

 Disregard the message and hit ‘Enter’ again. The following message will display but does
not indicate an error.

 Highlight the new output line and select ‘Further data’

439211426.doc Page 2 of 5
 Electronic Commerce
856 Customer Advance Ship Notice (ASN) Testing

 When the output display screen displays confirm the ‘Dispatch time’ is set to ‘Send
immediately (when saving the application)’

 Green arrow back to the previous screen and save

 The output has been generated and can be found using the ‘Services for object’ link from
the delivery display or using WE02/WE05 IDOC display

439211426.doc Page 3 of 5
 Electronic Commerce
856 Customer Advance Ship Notice (ASN) Testing

TO CREATE A REPEAT OR CHANGE OUTPUT

If an output already exists then you can create either a ‘Repeat output’ or a ‘Change output’.
Unless information in the order, delivery, or shipment is changed, the only value that will be
different in a repeat vs. change output will be the E1EDL18_QUALF value. In a repeat output
the E1EDL18_QUALF value is ‘ORI’ and in a change output the E1EDL18_QUALF value is
‘CHA’. The ‘Change output’ will only be used if the customer requires that a resent ASN be
identified with an alternate field value in an element in the EDI 856. To create either output from
the delivery output screen do the following:

 Select and highlight the existing output line

 Then select either the ‘Repeat output’ or ‘Change output’ option to create the output.
 When the new output line displays select save and the new repeat or change output will
generate.

439211426.doc Page 4 of 5
 Electronic Commerce
856 Customer Advance Ship Notice (ASN) Testing

WHOLE TESTING PROCEDURE

 Find a delivery that can be used for testing, if you don’t find it ask OTC to create a new one
in a testing environment.
 Ask Master Customer to update the Customer Group 1 of the delivery to either CS or UN.
 Once, order, delivery and shipment have been created; output the 940 from the shipment. In
order to output the 940 do the following:
o Get into the shipment through VT02N and then GotoOutput and enter the following
entry:

o Tell someone at Exel you will be sending the testing 940, and then we have to
manually intervene to push the file over. For more information see the text under title
TESTING OUTBOUND DATA WITH EXEL IN QA
 Once Exel received the 940, they will send the inbound 856 (pick and pack information).
Now that we received the pick and pack information we are ready to send the ASN. In order to
create the ASN, follow the instructions under title TO CREATE A REPEAT OR CHANGE
OUTPUT.

TO SEND THE EDI 856 TO THE PARTNER FROM QA

 The X12 output that is created in QA2 will have to be FTP'd to PRD for transmission.
 The partner’s ISA ID has to be set up in Production Enterprise.
 The translation is in QA, but the file has to be sent through our production environment as it
had been created in production.

TO CREATE THE EDI 856 DOCUMENT

 If the output parameters in the WE20 partner profile is set to ‘Collect IDOCs’ then use
transaction BD87 to manually process the IDOC when ready to review the EDI 856 output
 In order for an EDI 856 output to generate successfully, all required configuration must be
complete.
 When testing is complete and the output is confirmed to meet the customer needs then use
the steps above to create an EDI 856 that can be sent to the customer for their review.

TESTING OUTBOUND DATA WITH EXEL IN QA

SCJ and Exel communicate via FTP. Exel FTPs into our system on a regular basis and picks up
files from the following two directories:
Production: entsys/rdc/fromscj
QA/Test: entqas/rdc/fromscj

On the QA system, outbound files are placed into a subdirectory underneath the “fromscj”
folder. This is done on purpose to stop any files created from internal testing. We have some
files that are created automatically, and we don’t always want to send data to Exel, so this
procedure was put in place to prevent our “garbage data” from “polluting” Exel’s test systems.
Here is the subdirectory:
entqas/rdc/fromscj/saptest

If we truly want to send files to Exel, then it is necessary to find the desired file in the “saptest”
folder and move it up to the “fromscj” folder so Exel picks it up the next time they FTP into our
system.
439211426.doc Page 5 of 5