Ansicht
Dokumentation

ATP_BOP_RUN - Run Backorder Processing in ATP

CL_GUI_FRONTEND_SERVICES - Frontend Services   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Purpose

You can use Backorder Processing(BOP) to check material availability when the demand or supply situation in your order fulfillment process has changed and you want to check if previously calculated confirmations for sales orders or stock transport orders are still realistic. For example:

• A sales order is canceled, thereby freeing up stock quantities.

• An important customer increases the requested quantity for a material and would therefore like to consume stock which is currently confirmed for other sales orders.

• A production order providing planned supply is running late.

Not reacting to the changed availability situation can result in confirmed quantities exceeding available quantities. This can result in availability checks for over-confirmed materials failing, leaving you unable to release materials for delivery creation.

Integration

Backorder processing runs are scoped on the basis of defined variants to meet your business requirements and processes. The requirements included in a run are filtered and prioritized on the basis of the defined segments which are part of the variant. The filters used in backorder processing are defined on the basis of characteristics that can be found in the system, for example, sales organization, sold-to party, material, plant, or any combination thereof.

Prerequisites

1. In the Configure BOP Segmentapp, you create a new segment and define filters (referred to as Selection Criteria in the app) and the desired sequence of the requirements by assigning sort attributes. The resulting segment can be used in your variants.
2. In the Configure BOP Variant app, you create a variant by picking the segment created in the Configure BOP Segment app. You define how the requirements in the segment are handled by assigning the segment to a confirmation strategy. For example: your segment filters requirements that belong to a high-priority customer. You want the customer's requirements to be confirmed on the requested date - to do this, you assign this segment to the confirmation strategy Win.

Features

Selection

BOP Variant:

• Selecting the BOP variant defines which requirements and confirmation strategy are considered when the backorder processing run is executed.

Options:

• Simulation Mode: Use this indicator to execute backorder processing in simulative mode. In simulative mode, the BOP run performs a mass availability check for the selected requirements but does not update the requirements to reflect the results of the availability check.

• Execute Fallback Variants: Use this indicator to use fallback variants during the backorder processing run.

• Regenerate Variant Artefacts: Use this indicator to forcefully regenerate runtime objects if, for example, you notice inconsistencies between the variant definition and the runtime objects. Note that the definition of a variant determines which requirements are included in a run and their priority. When a variant is created or changed, runtime objects are generated in the backend. The runtime objects determine the requirements and their priority.

• Parallel Doc. Update Profile: Use this field to specify how the system should handle parallel updates to business documents after a backorder processing run has been executed and has resulted in differences to multiple business documents. Note that update profiles are available in SAP S/4HANA only and are maintained in Customizing activity Define Profile for Parallel Processing of Sales Orders After BOP.

• Re-evaluate Changed Settings: Use this indicator to trigger a re-evaluation of the backorder processing run to reflect any changes that may have been made to, for example, master data.

Message Log:

• Display Log: Use this indicator to display the log after the backorder processing run has completed.

• Force Log: Use this indicator to ensure that a log is created when your backorder processing run is executed. If you have specified a variant in Variant Name and select Force Log, you can specify the retention period for the logged data (in Validity in Days) and scope the data that is to be logged in in the Monitor BOP Run app by selecting one of the following options in Granularity (note that restricting the amount of data that is logged may have a positive impact on the performance of the availability check):

• Errors and Warnings: Log contains all error and warning messages.

• Nothing: Log contains no messages.

• Trace: Log details the requirements for which messages have been generated.

• All: Log contains all error and warning messages.

• Errors only: Log contains all error messages.

• Runtime Statistics: Use this indicator to log the runtime information when your backorder processing run is executed. Runtime Statistics will be enabled for selection only if the Force Log is selected. If you select Force Log and select Runtime Statistics, the runtime information would be logged even when the Granularity option selected is Nothing.

Check Log:

• Granularity: Use this dropdown to define the availability check data that is to be displayed in the Monitor BOP Run app. Note that if you restrict the amount of data to be logged by selecting Header Data Only, this may have a positive impact on the performance of the availability check and the following fields in the Monitor BOP Run app will not contain any data for the run:

• Processed Requirements

• Processed Requirements Fully Confirmed On-Time

• Processed Requirements Fully Confirmed

Standard Variants

Output

Depending on the options defined in Message Log, a simple log is displayed. For a detailed output, use the Monitor BOP Runapp.

Activities

Example

BAL Application Log Documentation   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 8024 Date: 20240520 Time: 074312     sap01-206 ( 150 ms )