SAP ABAP IMG Activity FAGL_MIG_OPITEMS_CRE (Process Document Splitting Information for Open Items)
Hierarchy
☛ SAP_FIN (Software Component) SAP_FIN
   ⤷ FI-GL (Application Component) General Ledger Accounting
     ⤷ FAGL_MIG_CONVERSION (Package) Future Standard Reports for Building Data
IMG Activity
ID FAGL_MIG_OPITEMS_CRE Process Document Splitting Information for Open Items  
Transaction Code S_AC0_52000620   (empty) 
Created on 20050301    
Customizing Attributes FAGL_MIG_OPITEMS_CRE   Process Document Splitting Information for Open Items 
Customizing Activity FAGL_MIG_OPITEMS_CRE   Process Document Splitting Information for Open Items 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name FAGL_MIG_OPITEMS_CRE    

Purpose

You use this program to generate entries in the document splitting tables for open items that were posted before the migration date.

Note:

Document splitting for these open items is not covered by this program. However, you can use a Business Add-In (BAdI) to add account assignments to the open items. This does not change the open items.

Integration

Prerequisites

  • You only execute the program for migration plans with document splitting. Document splitting must therefore be active in all company codes assigned to the migration plan.
  • You have closed the fiscal year preceding the migration date.
  • You have created worklists for open items.
    In the IMG activities for worklist creation, you have created a worklist containing all open items in the previous fiscal year. The status of each individual open item is also written to the worklist. You can call status administration by choosing Analyze Migration Status. If you have not created the worklist for all migration plans, statuses cannot be managed consistently.
  • You have implemented the BAdI FAGL_MIGR_SUBST.
    You can use the BAdI to add account assignments to open items that are posted without document splitting. For more information on the prerequisites that you must fulfill, see Information on Defining Document Splitting Information for Open Items.
  • If you derive the segment from the profit center, you need to have set the Segment Derivation Is Active indicator in the IMG activity Make Settings for Segment and Segment Derivation. If you have implemented the BAdI FAGL_DERIVE_SEGMENT, it overrides each segment derivation.
  • The dataset to be migrated and the Customizing settings have a consistent status.

Selection

  1. In the Migration Plan field, enter the plan containing the open items you want to process.
  2. In the Other Selections area, you can select individual documents.
  3. Under Processing Parameters, you can choose between update run and test run. We recommend first performing the program in the test run so that you can resolve any (validation) errors.
    When you execute the program in an update run, the tables for document splitting as well as the status table are updated (see Analyze Migration Status). This overwrites the status of an open item.
  4. Under Output Control, you can select the type of output.
  5. In the Parallel Processing area, you can execute the program using parallel processing.
    If you set this indicator, the system displays three additional fields that allow you to specify the package size, the number of parallel processes, and the server group. The entries for package size and number of parallel processes are mandatory. You can leave the Server Group field empty. The default server group is used.
    See also the notes under "After calling the BAdI" below.

Features

The open items are selected from the worklist. If an error has occurred for an open item (such as during validation), an error message is issued and the open item is not transferred to the tables for document splitting.

Status Management

If an open item has a status other than 10, the program displays the item as not processed or as containing an error.
The following statuses are possible:

  • 00: Open items with this status have not yet been processed with this program in an update run.
  • 01: Open items with this status have been processed with this program in an update run. However, an error occurred.
  • 10: Open items with this status have been successfully processed with this program in an update run. Entries have been generated in the document splitting tables. Open items with status 10 cannot be processed by this program again. You first need to change the status to 00.
  • XX: This status is not considered in this program. This status is set once all open items have been posted subsequently to new General Ledger Accounting.

Note:
Since open items can also be assigned to more than one migration plan in cases involving a non-calendar fiscal year variant, the status of an open item is adjusted independently of the migration plan selected.

Example:
The open item 100000090 exists in the worklist for migration plan MP1 as well as in the worklist MP2. When you execute the program for migration plan MP1, the status of this open item is updated in migration plan MP1 as well as in migration plan MP2. Previously, you had determined the worklists for both migration plans. However, the program does not display the documents of migration plan MP2.

For a deeper analysis of processing, perform the activity Analyze Migration Status.

Validation

In the BAdI:

You can perform your own checks in the BAdI FAGL_MIGR_SUBST. You can use structure ES_MESSAGE to send a message to the calling program. You can use the following fields:

  • ES_MESSAGE-TYPE : Message type
  • ES_MESSAGE-ID: Message class
  • ES_MESSAGE-NUMBER: Message number

The message text is determined by the program. When a message is issued, processing of the open item is canceled and it receives status 01.

After calling the BAdI:

The system checks the validity and correctness of the changes you have made in the BAdI in structure CS_MIG_ASGMT. The following checks are called:

  • Were the fields changed in a manner that is not permitted?
  • Were the fields filled correctly?

Caution:
When implementing the BAdI, ensure that you fill all selected fields with the correct values. Furthermore, CO substitution at event 1 and CO validation at event 1 are processed during validation.
For more information, see the section #Prerequisites# above.

If the system finds an error, a corresponding error message is attached to the open item and processing of the open item is canceled.
Note:

  • The first error message to occur is always logged. Other errors may have occurred without being logged.
  • A change made to a BAdI requires some time before it reaches all application servers. This is of particular relevance when the program is executed using parallel processing. For this reason, you should wait until the change to the BAdI has reached all servers before executing the program using parallel processing.

Use

Requirements

Standard settings

Activities

Example

Business Attributes
ASAP Roadmap ID 252   Prepare Data Transfer Fields 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG FAGL_MIG_OPITEMS_CRE 0 HLA0006520 Basic Functions 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
IMGDUMMY D - Dummy object FAGL_MIG_CRESPLIT  
History
Last changed by/on SAP  20050301 
SAP Release Created in 600