Rule Based Availability Check

Rules-Based Availability Check 

Use

You use the rules-based availability check to automatically or manually optimize the decision-making process between different substitutions using predefinedrules.

Prerequisites

●      You have created products and locations.

●      You have made the general settings for Global Available-to-Promise (Global ATP).

●      You have made all the settings for the rules-based availability check.

●      You have made the settings for rules-based ATP in the check instructions in the SAP APO implementation guide (IMG) under Global Available-to-Promise (Global ATP)  General Settings  Check Instructions. 

●      The ATP time series must be saved in SAP liveCache.

●      You have defined a business transaction in the OLTP system and assigned it to an order type.

Features

The rules-based availability check is an iterative process, meaning that each step defines the subsequent check step based on the rules saved in the system. The following is determined in each step:

...

●      Check methods that are to be executed

●      Requirement groups for which the next check step should be carried out.

●      Criteria according to which the results of the check steps should be reflected.

After the system has performed a check step, it must be determined if the rules-based availability check should continue to be executed. The criteria used for determining this includes the check results, activation parameters (technical scenario, business transaction, and the activity type) and the values of the key combinations such as customer, sales organization, location product, product group. The new rule then determines the next check step.

No rules-based ATP can be executed for subitems in the sales order.

Example

Rule I means:

...

       1.      Search for a different substitute location, if one does not exist,

       2.      then search for a different procurement method.

Rule II means:

...

       1.      Search for a different...