Show TOC

 Responsive Replenishment with ATP Check

Use

To check whether the products to be delivered are available, SAP Supply Network Collaboration (SAP SNC) can first send the replenishment order to the supplier back-end system, where a sales order is automatically created and an ATP check is performed for the sales order. Only after the ATP check has been able to confirm the requested quantities and requested dates and times, does SAP SNC also send the replenishment order to the customer back-end system, where a purchase order is created.

Features

Process Overview

The ATP check in the supplier back-end system updates the sales order item with confirmation schedule lines. The supplier sends the sales order confirmation to SAP SNC, using an XML message of type ReplenishmentOrderConfirmation . SAP SNC adds the confirmation schedule lines to the replenishment order item, and compares them with the request schedule lines of the item. To do so, SAP SNC uses the deviation analysis from consensus finding (see Consensus Finding ). Depending on the results of the deviation analysis, SAP SNC then accepts or rejects the confirmation schedule lines. When all confirmation schedule lines of a replenishment order item are accepted, the item receives the status Accepted, and SAP SNC can copy the confirmation schedule lines as request schedule lines to the item. Only when all replenishment order items are accepted, does SAP SNC send the replenishment order to the customer back-end system, where a purchase order is created.

Note Note

An ATP check that creates subitems for items is not supported.

End of the note.
Replenishment Order Publication

To control the transmission sequence for the replenishment order (transmission to supplier back-end first for the ATP check, transmission to the customer back-end system only after the request data has been confirmed by the ATP check) you use the following validation checks:

  • RO_PUBLISH_DIRECT

    With this validation check, SAP SNC sends XML messages for replenishment orders directly (in other words, without using the Post Processing Framework). This validation check is active in the standard system.

  • RO_PUBLICATION_ATPRESULT

    You have to activate the validation check if you want to use Responsive Replenishment with ATP check . This validation check is not active in the standard system.

Approval Process

When SAP SNC receives the ReplenishmentOrderConfirmation message with the confirmation schedule lines from the supplier back-end system, it performs an approval process for the confirmation schedule lines. For this, it uses the deviation analysis of consensus finding (see the Process Overview section). If the confirmation schedule lines deviate from the request schedule lines more than allowed by the configurable quantity and time tolerances, the confirmation schedule lines and the item receive the status Rejected . Confirmation schedule lines that correspond to the request schedules lines within the tolerances receive the status Accepted . For more information about configuring deviation analysis, see Purchase Orders and Replenishment Orders: Settings for Consensus Finding .

Update of Request Schedule Lines

In the case of an accepted item, SAP SNC can copy the confirmation schedule lines as request schedule lines. The replenishment order is thus updated based on the ATP check. You can use the following validation checks to control the copying of confirmation schedule lines to the request schedule lines:

  • You use the RO_COPY_ONLY_1CONF_TO_REQ validation check if the supplier back-end system is an SAP ERP system. This validation check only copies the schedule lines if the item has only one confirmation line, and thus only one request schedule line is created when it is copied. For more information, see the Integration with an SAP ERP Back-End System section.

  • You use the RO_COPY_CONF_TO_REQ validation check if several request schedule lines can be processed through integration with the supplier back-end system. This validation check creates a request schedule line from every confirmation schedule line.

Processing Rejected Items on the SAP SNC Web UI

If the confirmation schedule lines deviate from the request schedule lines more than allowed by the quantity and time tolerances, SAP SNC assigns the status Rejected to the confirmation schedule lines and to the replenishment order item. The supplier can change rejected items on the SAP SNC Web UI using the Replenishment Order Details screen or the TLB screen. He or she can, for example, change the requested quantity or the delivery date/time of the request schedule line. To send the updated replenishment order to the supplier back-end system again for another ATP check, the supplier must republish the replenishment order (in case of a replenishment order assigned to a TLB shipment, this must be done on the TLB screen).

Publication of the Updated Replenishment Order

If all items of a replenishment order have the status Accepted , SAP SNC sends the replenishment order using an XML message of the VendorGeneratedOrderNotification type to the customer back-end system, where a purchase order is created.

To update the sales order in the supplier back-end system as well, SAP SNC sends the updated replenishment order to the supplier back-end system. There, an ATP check is performed again. The request schedule line following the approval process represents the availability situation, and so, for the item, the ATP check creates a confirmation schedule line that corresponds to the request schedule line. The supplier back-end system then sends the sales order back to SAP SNC. The approval process again determines a match (for the confirmation schedule line and request schedule line). This time, however, the validation check does not copy the confirmation schedule line, since the requested quantity and the requested date have not changed.

Alerts

The following alerts can refer to exception situations in this process:

  • Confirmed Item Quantity Violates Underdelivery Tolerance (alert type 7123)

  • Confirmed Delivery Date/Time Violates Delay Tolerance (alert type 7140)

  • Partially-Confirmed Replenishment Order Item (alert type 7124)

  • Late Confirmation of Replenishment Order Item (alert type 7125)

  • Replenishment Order Confirmation Rejected (alert type 7126)

For more information, see Replenishment Order Alerts .

Integration with an SAP ERP Back-End System

If the supplier uses an SAP system as the ERP back-end system, replenishment orders are transmitted using IDocs. Corresponding mappings are available as follows:

  • Send replenishment order to supplier back-end system

    A mapping is available that maps the ReplenishmentOrderNotification to the ORDERS.ORDERS05 IDoc. The IDoc is selected via a contents-based routing. For more information, see the Configuration of IDoc Selection section.

  • Send sales order with confirmation schedule lines to SAP SNC

    A mapping is available that maps the ORDRSP.ORDERS05 IDoc to the ReplenishmentOrderConfirmation . The ORDRSP.ORDERS05 IDoc does not contain a segment for request schedule lines. The IDoc transmits the requested delivery date at header level and an aggregated requested quantity at item level. The request data is displayed in the replenishment order on a request schedule line.

    Note Note

    From this, the following restrictions result for replenishment order collaboration with ATP:

    • During the approval process, only one request schedule line is allowed to be created for an item. Confirmation schedule lines can only be copied if there is only one confirmation schedule for an item. Therefore, you have to use the RO_COPY_ONLY_1CONF_TO_REQ validation check.

    • In this process, you can only create replenishment order items with one schedule line. Therefore, use the corresponding splitting function to create replenishment orders in SAP SNC. For more information, see Splitting of Replenishment Orders .

    End of the note.

  • Send replenishment order to supplier back-end system after approval

    Once the approval process has copied the confirmation schedule line as request schedule line, SAP SNC sends the replenishment order to the supplier back-end system. For this transmission, a mapping is available that maps the ReplenishmentOrderNotification XML message to the ORDCHG.ORDERS05 IDoc. The IDoc is selected via a contents-based routing. For more information, see the Configuration of IDoc Selection section.

  • Send replenishment order back to SAP SNC after new ATP check

    A mapping is available that maps the ORDRSP.ORDERS05 IDoc to the ReplenishmentOrderConfirmation .

Configuration of IDoc Selection

The selection of the IDoc for the sales order in the supplier back-end system is based on the ActionCode in the header of the ReplenishmentOrderNotification . When you publish a new replenishment order in SAP SNC, the ActionCode is set to Create (01). When you publish a changed replenishment order after the approval process, the ActionCode is set to Change (02). In the SAP NetWeaver Exchange Infrastructure (XI), you have to define a contents-based routing that selects the following IDocs:

  • Create ActionCode (01) -> IDoc ORDERS.ORDERS05

  • Change ActionCode (02) -> IDoc ORDCHG.ORDERS05