SAP ABAP IMG Activity FAGL_V_FAGL_MIG_BSEC (Store Alternative Clearing Relationship)
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_V_FAGL_MIG_BSEC Store Alternative Clearing Relationship  
Transaction Code S_AC0_52000623   (empty) 
Created on 20050301    
Customizing Attributes FAGL_V_FAGL_MIG_BSEC   Store Alternative Clearing Relationship 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name FAGL_V_FAGL_MIG_BSEC    

Use

You can influence the behavior of document splitting by change the clearing relationship of a clearing line. This is necessary in the following cases:

  • If you have create the clearing relationships of documents subsequently
  • If the clearing relationships of documents are incomplete
  • If the clearing process is to be excluded from document splitting

The document splitting programs always process clearings and expect to find document splitting information for the items to be cleared. If the document splitting information is missing or incomplete, the document cannot be posted subsequently.

Requirements

In Customizing for document splitting, you can assigned a document splitting method or an alternative document splitting method specific to migration.

Standard settings

Activities

If you want to influence clearing lines, create a customer message.

  • You change a clearing relationship for a document line by entering the corresponding data in the fields of the document line to be treated.
  • You assign the document line to be cleared in the fields that follow. In these fields, you enter the corresponding data for the cleared item.
  • You assign one of three actions to the line:
    • Add:
      If you want to add the clearing relationship, select the action Add . If you want to represent multiple clearing relationships with the same clearing line, you have to give the entries in the Seq. No. Clearing field a unique number (which can be a randomly chosen number).
    • Ignore Individual Clearing Relationships
      If you want to delete the clearing relationship, select the action Ignore Individual Clearing Relationships. If you want to delete multiple clearing relationships with the same clearing line, you have to give the entries in the Seq. No. Clearing field a unique number (which can be a randomly chosen number).
    • Ignore Entire Clearing
      If you want to delete all clearing relationships, select the action Ignore Entire Clearing. In this way, all clearing relationships for this clearing item are not used internally and no clearing is processed in document splitting. The fields of the cleared item are not used.

Ensure that the account and the amounts in the clearing relationships agree.

If you create additional clearing relationships for document lines that were posted before the migration date, you need to ensure that the assigned cleared items are already in the worklist of open items to be migrated or that they are included explicitly in that worklist.

In the migration of document line items contained in the table, the explicitly assigned clearing relationship is used in addition to the clearing relationships represented in posting table BSE_CLR to build the document splitting information, or any such clearing relationship is ignored. This is logged in the status management of the migration objects in the Adjustment field. You can use the activity Analyze Migration Status for this and analyze the log for migration-specific document adjustment.

Example

Business Attributes
ASAP Roadmap ID 152   Design data acquisition 
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_V_FAGL_MIG_BSEC 0 HLA0006520 Basic Functions 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20050525 
SAP Release Created in 600