Kontakt

Ansicht
Dokumentation

RFARR_IL_CLEANUP - Clean Up Initial Load

RFARR_IL_CLEANUP - Clean Up Initial Load

PERFORM Short Reference   General Data in Customer Master  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

This program deletes objects created while a company code or a company code/migration package combination is in status Migration. You use the report to clean up the database after an initial load process for a company code or migration package failed.

After the cleanup you can repeat the initial load process.

Note: The clean-up also removes data which is created by non-operational load processes if it fits the entered selection criteria.

Example: While the operational load is feeding historical data into revenue accounting and reporting the creation of new orders, invoices and fulfillments in the source system creates revenue accounting data by non-operational load processes. Now the company code and migration package need to be reset because there has been an error in the configuration and a clean-up is performed. Within the clean-up all data is removed as the complete company code and migration package shall be reset to allow starting from scratch. All data for this company code and migration package has to be loaded again afterwards.

Integration

The operational load of the removed data has to be repeated. There might be additional actions required in the sender component to do so. For instance, for SAP SD, the indicator relevant for revenue accounting has to be reset on the sales order item using the reset function of the operational load for Revenue Accounting (FARRIC_OL) before the document can be loaded once again.

Prerequisites

  • The accounting principle/company code/migration package combination must have the status Migration. If no migration packages are maintained for a company code, the migration package space is implicitly used. The status of a migration package is set in customizing.
  • You have created revenue accounting items, performance obligations, and contracts for an accounting principle/company code/migration package combination on your database which is in status Migration.
  • No postings have been created for the revenue accounting contracts.
  • The POBs for the migration package to be cleaned up have not been manually moved to contracts including POBs related to different migration packages. Please keep in mind: The relation to a certain migration package might only be visible in the revenue accounting item which refers to the POB and not necessarily in the POB directly.

Features

Selection

Select the company codes and migration package and choose @15@ Cleanup (Execute).

You also have the option to run the program in simulation mode. In simulation mode, no data is removed from the database. We recommend that you always run a simulation before the cleanup is executed. This way you can identify errors and solve problems before you execute the cleanup.

Note: The counters of a simulation run might look different as for a real run.

Reason: Revenue accounting order items for the same header ID may be spread over several tables. Within the report processing blocks are split when a new table is worked off (one COMMIT per processing block). As in simulation mode the data for the header ID is not removed from the database, items in other tables still exist when these tables are processed. Therefore, the header ID can be picked up in different processing blocks during simulation mode. As a result, the counters in a simulation mode might not be identical to the actual run where all data related to a header ID is removed from database after it has been picked up for the first time.

You have the option to only clean up items related to certain header IDs. If you choose this option, in addition to the header ID, you must enter the source component and the logical system of the header IDs. If the items include items that are related to other contracts, all related header IDs for these contracts are also cleaned up, if possible.

It is not possible to select by source item component or source item logical system without defined header IDs, even if a company code is given.

The Maximum Block Size defines the maximum number of header IDs the program processes before the data changes are committed to the database.

The Switch to simulation mode parameter allows you to run the report in simulation mode. In simulation mode, no data is removed from the database. We recommend that you always run a simulation before the cleanup is executed. This way you can identify errors and solve problems before you execute the cleanup.

The Delete Return Order RAIs parameter is useful in case of deletion certain header IDs. There could be difference between sender component and RAR. E.g. SD sender component sends return order RAIs together with original order RAI. You don't have to specify document number of return order as parameter of operational load. In opposite FARR_IL_CLEANUP deletes return order RAIs only if you specify header id of return order as parameter or if you run cleanup for whole company code. If parameter Delete Return Order RAIs is set report deletes also return order RAIs which belongs to the original order RAI.

Standard Variants

Output

The application log records:

  • The number of deleted objects per table and block
  • Items which the program could not delete
The program cannot automatically delete invoice items or fulfillment items in status rawthat refer to an original item which does not exist. The migration package for these invoice and fulfillment items cannot be determined. They are listed at the end of the application log. You have to delete these items manually.
To avoid postprocessing activities, we recommend that you transfer raw items to status processable before you run the cleanup. That way you reduce the number of fulfillment and invoice items with no migration package assigned.
  • If you select single header IDs, the log lists the header IDs that are deleted.

Activities

If an error occurs, the cleanup report skips processing of the given block and continues with the next. After you have corrected the error, you must restart the report in order to clean up the remaining data. When the cleanup report runs successfully, it deletes all selected data without errors.

Example

The program has deleted the first block of data. The second block contains a contract, for which postings already exist. For this reason, the second block cannot be deleted. So, the program continues with the next blocks.

The application log explains in detail what caused the error. Before you can delete the second block, you must delete the postings.

Then you run the program again to clean up the second block of data.

To detect other errors the first run did not detect, you run the program in simulation mode. Then you rerun the cleanup.






SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 7808 Date: 20240601 Time: 053448     sap01-206 ( 159 ms )