Ansicht
Dokumentation

FAGL_MIG_DS_RESTORE - Reset Subsequent Implementation of Document Splitting

FAGL_MIG_DS_RESTORE - Reset Subsequent Implementation of Document Splitting

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You can use this program to reset the migration that you performed for the subsequent implementation of document splitting. Note that the program cannot be performed in a production system.

Integration

Prerequisites

  • You have created the worklists for all migration objects for the migration plans.
If you have not run the programs for determining the worklists, errors may occur when the reset program is run.
  • You have not activated document splitting in any of the assigned company codes.
  • The migration plan to be selected has not been completed. This also applies to migration plans that also have to be processed besides the selected plan.
For more information, see the SAP Notes for migration plans with document splitting.

Features

Selection

You can execute the program in three different variants:

  • Reset Migration Completely (transaction: FAGL_MIGDS_REST_ALL)
We recommend that you use this variant.
  1. Specify which migration plan you want to completely reset.
  2. Use the Reset or Reset and Delete indicators to specify whether all entries in the worklist obtain status 00 or whether the worklist is deleted completely. This applies to the worklist of open items and to the worklist of transferred documents.

Ensure that the affected tables only contain data that can be deleted. The program cannot distinguish whether data was generated by migration programs and can therefore be deleted or whether data was generated by a normal document posting, for example, and cannot be deleted. If the tables contain data that should not be deleted, you must not execute this program.
  • Reset Migration for Open Items (transaction: FAGL_MIGDS_REST_OP)
We recommend that you do not use this variant.
  1. Specify the migration plan and the open items that need to be reset. Use the Fiscal Year field to select all items of a fiscal year. The system only considers the open items contained in the migration worklist.
  2. Use the Reset or Reset and Delete indicators to specify whether the update to new General Ledger Accounting should only be reset for the selected items or whether the item itself should also be removed from the migration worklist. If you delete an item from the migration worklist, you cannot repeat the migration of that item.
Note
Note that entries in the totals table are not deleted. Only an adjustment posting is made.
  • Reset Migration for Transferred Documents (transaction: FAGL_MIGDS_REST_RP)
We recommend that you do not use this variant.
  1. Specify the migration plan and the documents that need to be reset. Using the Fiscal Year or Posting Periods fields, you can select all documents in a given period. The system only considers the documents contained in the migration worklist.
  2. Use the Reset or Reset and Delete indicators to specify whether the update to new General Ledger Accounting should only be reset for the selected documents or whether the document itself should also be removed from the migration worklist. If you delete a document from the migration worklist, you cannot repeat the migration of that document.
Note
Note that entries in the totals table are not deleted. Only an adjustment posting is made.

Standard Variants

Output

Features

The transactions FAGL_MIGDS_REST_OP and FAGL_MIGDS_REST_RP determine the selected migration objects from the migration worklist. Objects that are not in the worklist are not considered.

For the objects determined, the system deletes or adjusts all data updates to new General Ledger Accounting. This applies to the following data:

  • Line items and totals in the assigned ledgers
  • Document splitting information
  • Migration worklists
  • Balance carryforward values for reconciliation accounts

Transaction FAGL_MIGDS_REST_ALL is not based on the worklist. Consequently, it is important that the database tables only contain data that can be deleted.

Activities

Example

Notes on Background Processing

If you want to execute the program in the background, you must start background processing from within the respective transaction. You cannot schedule the program as a background job.

Notes for Migration Plans with Document Splitting

Notes on Resetting Individual Migration Objects






Vendor Master (General Section)   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 6193 Date: 20240531 Time: 113349     sap01-206 ( 98 ms )