Oracle Apps and ASN

The ASN aka Advanced Shipment Notice is a document that is sent to a buyer in advance of the buyer receiving the product. It is typically used within the context of an EDI environment. It can be used to list the contents of an expected shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking carrier information, and configuration of goods within the transportation equipment. In the implementation of the transaction the latest the ship notice may be sent is the time of shipment. In practice the ship notices just arrive before the shipment.

 Basic Business Needs

• To receive a Shipping notice in Advance:
• Provide user the ability to electronically receive supplier ship notice into Purchasing by loading an ASN electronically into Oracle Apps using the Receiving Open Interface.

 Business Flow

Typical Process with company using Oracle EBS would be similar to this:

1. Supplier sends ASN.
2. EDI validates the data for EDI standards and inserts data into Receiving Interface tables.
3. Receiving Open Interface validates ASN data. If accepted shipment lines are populated.
4. Supply details are maintained.
5. Application Advice is generated. The supplier can check if there is a rejection of ASN through the advice.

Inbound Shipment Notice Transaction (856)

If you are using EDI Gateway , make sure you have done setup for Trading partner correctly. These are relevant Oracle Purchasing Profiles and Set-ups

The following is a list of the Purchasing set-ups related to the Receiving Open Interface.

1. RCV: Fail All ASN Lines if One Line Fails:If the profile option is set to 'Yes' and any line failed validation, no further validation is performed for the ship notice.
   If the profile option is set to 'No' and any line failed validation, the process continues with the next line.
2. ASN Control:In the Receiving Options window in Purchasing, select Warning, Reject, or
   None in the ASN Control field to determine how Purchasing handles the receipt against a purchase order shipment for which a ship notice exists.
3. PO: Enable SQL Trace for Receiving Processor :If the profile option is set to 'Yes', more detailed error data is provided in the View Log screen of the Submit Request window when you run the Receiving Transaction Processor.

 Data Flow Diagram

Here is data flow looks typically when you are using with EDI gateway.

Receiving Open Interface tables which got involved in this is:
RCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE

You can use Import Programs to submit ECEASNI.sql (856) to the Concurrent Manager to populate the Receiving Open Interface tables with data from the inbound interface file.This is applicable if you are using EDI Gateway , else you can directly use Receiving Open Interface (RCVTP) program.

Use Import Programs to submit the Receiving Open Interface (RCVTP) program to the Concurrent Manager to validate the data in the Receiving Open Interface tables.

Hope with this, you can easily implement ASN in EBS. Question, comments are most welcome.

References:
http://www.oracleappshub.com/edi/oracle-apps-and-asn/