Process documentationEDQA Event: Reassignment of Order Confirmations Locate this document in the navigation structure

 

During this process the event-driven quantity assignment (EDQA) executes a reassignment of order confirmations (ROC) in order, for example, to assign confirmed quantities from items with a low priority to items with a high priority.

Prerequisites

  • In integrated rule maintenance, you have created a rule and selected the Activate Reassignment of Order Confirmations checkbox for this rule. For more information, see Creating Rules.

  • You have made all the settings in Customizing for EDQA for the ROC.

    For more information, see Customizing for SAP SCM under   Advanced Planning and Optimization   Global Available-to-Promise (Global ATP)   Event-Driven Quantity Assignment (EDQA)   Reassignment of Order Confirmations (ROC)  .

  • You have made the basic settings for the SAP Business Workflow.

    For more information, see Customizing for SAP SCM under   SAP NetWeaver   Application Server   Business Management   SAP Business Workflow   Maintain Standard Settings  .

Process

  1. The system performs a rules-based ATP check (see Rules-Based Availability Check) for line items for which an insufficient quantity is available for the requested date. The document is linked to the activity Sales Order Confirmation that triggers the ROC event.

  2. In an order due list (ODL), the system determines items that can lose their confirmation.

  3. The system assigns a provisional confirmation to the items from the triggering document.

  4. The system transfers the information by means of the provisional confirmation to the OLTP system.

    It is not yet possible to deliver the items.

  5. You save the document in the OLTP system.

  6. SAP SCM performs backorder processing for the items determined in the ODL and reduces their confirmed quantity in favor of the triggering document. For more information, see Backorder Processing.

    Caution Caution

    Make sure that the system confirms the items in the triggering document at location level and does not take into account batches, storage locations, characteristics, and so on. This can lead to overconfirmations.

    End of the caution.

  7. The system posts in the OLTP system the confirmed quantity and the confirmed date for the items in the triggering document.

    Note Note

    If you manually change the item in a document after the ROC and before posting in the OLTP system, the system does not use the results of the backorder processing for this item. The same applies to all items that were fully or partially delivered.

    End of the note.

  8. The system updates the triggering document. When all of the items have been correctly posted in the OLTP system, the system changes solely the status of the triggering document. If it did not, the system would perform another availability check for the document.

More Information

For more information about the ROC event, see the SAP Library for SAP Customer Relationship Management (SAP CRM) under   Components and Functions   Sales   Availability Check   Availability Check using SAP APO   Additional ATP Functions in Service Parts Management   Controlling the ATP Check in the Sales Order   Reassignment of Order Confirmations  .