Update Rules for Updating in 9ASDDAT and 9APURDAT
The update rules that update the data in DataStore objects 9ASDDAT and 9APURDAT consist of the components described below. For a detailed overview of which components belong to which update rule, see Update Rules for Historical Data Capture.
The system checks which data from SAP ERP is relevant for stock transport orders. To do this, it checks the RESWK field. The data is relevant for stock transport orders only if the field does not contain its initial value.
The system checks which purchase order schedule lines are relevant for the demand history.
In the case of order data, the system takes into account only those purchase order schedule lines that do not have a higher-level order item number.
In the case of stock transfer data, the system takes into account only those purchase order schedule lines that are assigned to a main item. To do this, it checks whether the UEBPO field is filled. If this field is not filled, the purchase order schedule line is assigned to a main item.
The system identifies the GUIDs for the order items (POSID) for order and stock transfer data from SAP ERP.
For stock transport orders, the 2LIS_02_SCL DataSource does not fill the fields that are needed for historical data capture for the customer-facing location and for the stockholding location. For this reason, the system determines the locations for stock transfer data in the update rule.
The system uses the plant description in SAP ERP to determine the location short description in SAP Supply Chain Management (SAP SCM). The system then uses this location as both the customer-facing location and the stockholding location. The system then checks this location's replenishment indicator and takes a stock transport order into account only if the location is stocked.
For sales order items from SAP ERP SD, the system calls the SAP SCM global ATP check, which determines the first stockholding location and the customer-facing location for this sales order item.
The system checks whether all the required fields are filled. Examples of required fields include the following:
Product
Location
Order No.
Order Item Number
Purchase Order Schedule Line Number
Checking Locations
The system checks whether the locations are included in the product's current bill of distribution (BOD). If locations are not included in the product's current BOD, the system takes into account order items and stock transport orders that contain the relevant location product. When capturing historical data, the system does not take into account these order items and stock transport orders.
For more information about where you can see errors that occur during historical data capture, see Error Handling During Historical Data Capture.