Ansicht
Dokumentation

PPC_HEADRECS_COMPARE - Checks existence of and process flags for records in APO and R/3

ABAP Short Reference   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Title

Consistency Report for DI Backflush

Purpose

The report reads backflushes from the DI System and the APO System and displays the inconsistencies between the two systems with regard to the backflushes selected.

Integration

This report is only useful if you are using the DI Backflush functions with the APO.

Prerequisites

The only prerequisite is the existence of backflushes from the scenario "DI Backflush with APO".

Features

Selection

Alongside the creation date and the backflushing system (APO), there is the "Check Only with HeadIDs from R/3" indicator on the selection screen.

• If the "Check Only with HeadIDs from R/3" indicator is inactive (default), the system reads all backflushes in the APO and in the DI System that lie within the creation period entered using the creation date.

• If the "Check Only with HeadIDs from R/3" is active, the system first reads the backflushes in the DI System matching the selection criteria and then reads the backflush data belonging to these backflushes in the APO. When the system selects like this, it does not take into account backflushes that exist only in the APO and not in the DI System.

Standard Variants

Output

The report writes any inconsistent backflushes in a list. You can then use the reporting tools for DI Backflush to check each individual backflush.

An inconsistent backflush is put into one of four categories:

• The indicator that shows the progress of the synchronous processing has a different value in the APO System to the value in the DI System.
  This situation is not necessarily an inconsistency. It can occur if the information message, that informs the APO that this indicator has set in the DI System, is still in the CIF (core interface) and the APO therefore does not know that this indicator has been set. In case of doubt, check the CIF queues.

• The indicator that shows the progress of asynchronous processes has a different value in the APO to the value in the DI System.
  This situation is not necessarily an inconsistency. It can occur if the information message, that informs the APO that the indicator has been set in the DI System, is still in the CIF (core interface) and the APO therefore does not know that the indicator has been set. In cases of doubt, check the CIF queues.

• The backflush exists in the DI System but not in the APO.
  This situation is not necessarily an inconsistency. It can also occur if the backflush has been deleted in the APO already but has not been archived in the DI System yet. Either the backflush data has not been archived yet or the archiving program has not identified the backflush as being ready for archiving yet. Look in the documentation for the archiving program to see which prerequisites must be met before a backflush can be archived.

• The backflush exists in the APO but not in the DI System.
  This situation is not necessarily an inconsistency. It should not occur, however, if the "Check Only with HeadIDs from R/3" indicator is active. It can occur if a backflush has already been saved in the APO but the information message to the DI System is still in the CIF (core interface). The DI System, therefore, does not know this. In cases of doubt, check the CIF queues. This situation can also occur if a backflush has been archived in the DI System already but the deletion report has not deleted it in the APO System yet.

Activities

The system cannot determine without any doubt whether a situation is inconsistent or not because backflushes that are in the CIF are not taken into account. In addition, after a certain status for a backflush, it is possible to delete or archive the backflushes in the APO or DI System independently from each other.

If there appears to be an "inconsistency" because confirmations/transfers are currently in the CIF, then this temporary inconsistency will probably not be listed when you next start the report.

If the report displays inconsistent backflushes, then you check each backflush individually. To do this, you use the evaluation tools for backflushing in the APO and in the DI System as well as the RFC monitor.

Example

General Material Data   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 4651 Date: 20240531 Time: 114656     sap01-206 ( 96 ms )