Hierarchy
⤷ FI (Application Component) Financial Accounting
⤷ FB_ICRC (Package) Cross-System Intercompany Reconciliation
IMG Activity
ID | SIMG_CFMENUFBICRC007 | Define Ledger |
Transaction Code | S_PLN_62000470 | (empty) |
Created on | 20040312 | |
Customizing Attributes | SIMG_CFMENUFBICRC007 | Define Ledger |
Customizing Activity | SIMG_CFMENUGCU0GCL2 | Maintain Ledgers |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_CFMENUFBICRC007 |
In this Customizing activity, you can create and maintain a Special Purpose Ledger. This step is mandatory if you are configuring a system that is supposed to be used as a source system for intercompany account reconciliation. The ledger must have the following settings:
Property Value
Summary table FBICRC002T
Ledger posting allowed Yes
Write line items Yes
Transaction currency Yes
All other switches must be off.
You also have to perform the following activities, which can be accessed from ledger maintenance:
- Assign all companies to be reconciled.
- Assign the fiscal year variant you assigned in the Reconciliation Process Detail Attributes to all of the companies to be reconciled in the detail settings of this ledger.
- Assign at least activity RFBU (Write line items: Yes) and the field movement created in the previous step. You may want to assign the same activities as G/L using function Activities Like G/L and adjust the suggestions according to your requirements.
- Set up a ledger selection with BSEG-VBUND <> SPACE. In this ledger selection, you should also exclude any account types that are not to be reconciled.
- Set up and assign a field movement that populates fields with discrepant field names. You should create the following entries for your field movement:
Receiver Field Sender Table Sender Field
DOCDT ACCIT_GLX BLDAT
RACCT ACCIT_GLX ALTKT
RASSC ACCIT_GLX VBUND
REFNR ACCIT_GLX XBLNR
If you are not using a corporate chart of accounts you may want to use sender field HKONT for receiver field RACCT.
The sender field for receiver field REFNR depends on your business requirements. Follow this link for more information and some examples for reference number sender fields. If necessary, you can also assign an exit implementation for your receiver fields.
Dependencies
If you are not implementing the intercompany reconciliation process at the beginning of a new year, you have to subsequently post existing documents for this ledger. Otherwise, only documents that are posted after the activation of the ledger are included in the reconciliation process.
Before you can define ledgers for intercompany reconciliation, make sure that global ledgers are active. You do this in the Customizing activity Perform Preparation.
Standard settings
Activities
Example
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 2 | Non-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 | SIMG_CFMENUFBICRC007 | 0 | HLA0001205 | Closing Operations |
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 |
GLX_LEDGER | T - Individual transaction object | GCL2 | GCL2 | Change Ledger | ||
GLX_LEDGER | T - Individual transaction object | GCL3 | GCL3 | Display Ledger | ||
GLX_LEDGER | T - Individual transaction object | GCL1 | GCL1 | Create Ledger | ||
GLX_LEDGER | T - Individual transaction object | GCL4 | GCL4 | Delete Ledger | ||
GLX_LEDGER | T - Individual transaction object | GCL6 | GCL6 | Copy Ledger |
History
Last changed by/on | SAP | 20040330 |
SAP Release Created in | 500 |