Ansicht
Dokumentation

/SAPAPO/SDRQCR21 - Correction Report for Delivery Requirements and Sales Requirements

Fill RESBD Structure from EBP Component Structure   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Purpose

You can use this report to correct incorrect sales order and delivery requirements in the ERP system and SAP APO, and identify and correct data inconsistencies in the product allocation assignments.
In ERP, requirements are created in the sales order through the schedule line(s) and in the delivery through the item(s). In SAP APO, these requirements are stored in the SAP liveCache.

Integration

Prerequisites

Features

Data inconsistencies in product allocation assignment can arise through program errors, or through deleting queue entries. In particular, the SD order tables in SAP APO must be consistent and complete, so that backorder processing (BOP) for example can be done without errors.

You must use this report if you were unable to correct data inconsistencies using report /SAPAPO/CIF_DELTAREPORT (report /SAPAPO/CIF_DELTAREPORT3 does not include these checks).

Selection

You must limit the data to be checked by selecting an OLTP System; you can also limit the data by specifying a product or a location.

Standard Variants

Output

You can display the result in two ways:

• Using the ALV (ABAP List Viewer)

• As a simple list output sorted according to:

• Document number or

• Product and location

You can also choose not to display correct documents.

Activities

First, the system gathers order requirements and delivery requirements in SAP APO and in the ERP system. The requirements are then compared at field level (material availability date (MBDAT), open quantity, confirmed quantity, planned quantity, plant, and so on).

During the comparison, the system may identify the following inconsistencies and send the relevant creation/update/deletion events directly (if have did not start the report in test mode):

• The requirement exists in SAP APO but not in the ERP system
  Event: The requirement is deleted in SAP APO

• The requirement exists in the ERP system but not in SAP APO
  Event: The requirement is sent again from the ERP system to SAP APO

• There are differences in content (date/time, quantity) between the ERP system and SAP APO
  Event: The requirement is sent from the ERP system to SAP APO as an update

The system can determine the SD order and SD delivery requirements in the ERP system as follows:

• Using table VBBE

The requirements are stored in table VBBE.
If you assume that these are correct, you can choose this option. The determination of the open requirements then only contains a simple selection from this table (see Read Requirements from VBBE Table).

• Using the document flow and document status

The SD requirements in ERP are not read from the VBBE table; rather they are recompiled first based on the document flow and document status (see Build Requirements from Document Flow).
You have the option of updating the VBBE table with the result of this redetermination (see Update VBBE Table).

The SD order tables (/SAPAPO/POSMAPN, /SAPAPO/ORDADM_H, /SAPAPO/ORDADM_I, /SAPAPO/SCHEDLIN) are checked to see if they exist and are checked for consistency. The consistency check contains the check against ERP using the ERP tables for item (VBAP) and schedule line (VBEP). In the case of subitems, the consistency of the related main item is also checked (see Check SD Order Tables).

If you select the Check Descriptive Characteristics checkbox, the system checks for consistency between the ID of descriptive characteristics from liveCache nodes of SD requirements and the characteristic values of the corresponding item. The characteristic values are derived from the field catalog and - if used - from characteristic values of the characteristics-dependent planning stored for the item in SAP SCM.

Set the indicator Check Product Allocation Assignments to have the system identify and correct data inconsistencies in product allocation assignments as well.

You can use the block size to divide up the overall processing process into several blocks (see Block Size for Product/Location Combinations).

If the report is not executed in the test mode, you have the following additional options for sending the creation/update/deletion events:

• The events can be sent individually per document to SAP APO (see Send Events Individually to SAP APO).

• The events can be sent in a new task (see Send Events in New Task).

You can also define how many checks the system is to perform to identify inconsistencies (see Number of Checks), and how long the wait time between the checks is to be (see Wait Time Between Checks).

Example

Addresses (Business Address Services)   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 6216 Date: 20240424 Time: 234028     sap01-206 ( 87 ms )