Show TOC

  Creation/Receipt of Advanced Shipping Notifications and Inbound Deliveries

Use

The following figure illustrates the receipt of an advanced shipping notification in the third-party order processing (TPOP) process:

After receiving the advanced shipping notification (ASN) for TPOP goods an inbound delivery is created by parsing the segments from the IDoc to the required tables, running the inbound validation framework, and then, if no errors occur, creating it

If the validation process detects errors, the system sends an error log containing information about what went wrong to SAP ICH. This is configurable based on the Customizing settings in validation framework. The inbound delivery can be saved on hold, or the corresponding ASN can be rejected

After the inbound delivery has been created, the purchase order data is updated in the ERP system and the vendor/supplier location is updated in SAP APO from SAP CRM.

This invoice references the ASN (or rather the statistical goods receipt document, and thus the ASN). This invoice is created regardless of whether the vendor/supplier regularly sends invoices or is paid through the ERS procedure. The ERP system creates an FI document.

Furthermore, when the inbound delivery is saved, SAP CRM Sales automatically receives the delivery information: a document flow entry is created for the inbound delivery (on header and item level) and delivery status, delivered quantities, and goods issue quantities are updated.

Finally, when the changes in the sales order are saved, the requirements are updated in SAP SCM.

Note Note

You can create, change and replace TPOP ASNs using the user interface in SAP ICH.

End of the note.
Supersession in ASN using EDI

The supersession process involves the following steps:

  1. Check Supersession in ASN

    The system checks if supersession i s reported in supplier ASN and based on that follow on processes is performed. The supplier sends the ASN usingIDoc. If supersession has taken place, the supplier would indicate this using a field in the segment of the IDoc. The system parses the segments of the IDoc and checks if supersession has taken place.

  2. Check customizing

    Suppliers could report supersession in ASN and during PO confirmations/change requests. System provides the option to the customer to disable supersession during ASN´s. This means that the ASN gets rejected by the system if supersession is reported in the ASN and the customer has disabled supersession in ASN’s using customizing. This customizing is not supplier specific. is applicable to all suppliers. The pre-condition is that supersession should be reported in the ASN.

  3. Get interchangeability master data from SAP APO and check validity of supersession

    Supersession master data is maintained in the SAP APO system. When supersession is reported using ASN, the system invokes the validation framework and a synchronous RFC call to SAP APO is made to check the validity of the supersession that is reported by the supplier. The delivery date in the ASN is used to check the validity. The pre condition is that supersession should be reported in the ASN.

  4. Change PO

    System creates the sub line item in the PO and copy all the relevant data from the main item. The main item is marked as statistical. The system creates the inbound delivery and post the statistical goods receipt for the sub line item. The pre-condition is that the supersession is valid.

  5. Pass information to SAP ICH

    The system passes the information to SAP ICH. The information is passed to SAP ICH usingIDocs. The IDoc segments contains indicators to inform ICH that supersession has taken place. The pre-condition is that the sub line items is created in the PO and the statistical goods receipt has been posted for the sub line item.

  6. Pass data to SAP CRM

    The system passes new sub line item of the PO and inbound delivery details to SAP CRM. The pre-condition is that the inbound delivery is created for the sub line item of the PO .