Hierarchy
EA-FIN (Software Component) EA-FIN⤷
FI-GL-GL-CL (Application Component) Closing Operations⤷
FB_RC (Package) Reconciliation Tool
IMG Activity
| ID | SIMG_CFMENUFBRC009 | Define Rules for Document Assignments |
| Transaction Code | S_PLN_62000511 | (empty) |
| Created on | 20040317 | |
| Customizing Attributes | SIMG_CFMENUFBRC009 | Define Rules for Automatic Document Assignments |
| Customizing Activity | SIMG_CFMENUFBRC009 | Define Rules for Automatic Document Assignments |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUFBRC009 |
In this Customizing activity, you can define rules for document assignments. You can specify that rules are to be executed automatically. That is, the data records are assigned automatically based on these rules when the appropriate program is started.
Rules that are not set to be used automatically are available when reconciling data records manually. You can use these rules to find matching or similar data records.
Multiple Rules
If you set up several rules for automatic assignment, the rules are processed sequentially in the same order as they are shown in the Customizing view:
Rule SeqNr OrgUnit Field Compare Partner Field
100 100 REFNR Equal REFNR
200 100 REFNR Equal DOCNR
This means that first the data is analyzed using rule 100. Any data records assigned to a document group by this rule are excluded from further processing and therefore not be analyzed by rule 200.
Example
Company Partner Doc. (DOCNR) Ref. (REFNR) Curr. Amount
C1000 C2000 1000000121 R121 EUR 500,00
C1000 C2000 1000000127 R121 EUR 1.350,00
C2000 C1000 2000000342 R121 EUR -500,00
C2000 C1000 2000000343 1000000121 EUR -1.000,00
Results of automatic assignment:
Group Company Doc. Curr. Amount Partner Doc. Curr. Amount
2003 C1000 1000000121 EUR 500,00 C2000 2000000342 EUR -500,00
2003 C1000 1000000127 EUR 1.350,00
Document C2000 2000000343 is not assigned to the document group, although it matches document C1000 1000000121 based on rule 200. The first three line items are excluded from processing when rule 200 is processed.
However, if you run automatic assignment once with rule 100 only and then with rule 200 only, document C1000 1000000121 is added to the document group.
Multiple Conditions in One Rule
If you have multiple conditions within one rule, these conditions are linked with a logical AND, that is, all conditions must be met to have documents assigned to each other.
Requirements
One of the most important points in the preparation of intercompany reconciliation (ICR) is that organizational measures must be taken in order to derive at a mechanism or posting rules that allows for posting of a unique identical reference number that can be posted in all documents related to a business transaction by both partners involved in the business transaction. If this cannot be ensured, it slows down the reconciliation process significantly. Note that this reference number does not have to be posted in the same field by both partners, since different sender fields for the reference number can be specified per company.
If it is not possible to post a unique reference number, you should analyze the documents to try and find a combination of values posted in all the involved documents that could be used to create a unique identifier for each business transaction. In this case, you could implement one of the Business Add-Ins (BAdIs) available in the Customizing activities Define Enhancements to combine these fields into field REFNR and create a unique ID. For more information, see the documentation in the Help Portal and SAP Note 863630 (attached document, chapter 3.1.2.3 Define Enhancements in Intercompany Reconciliation - Background Information & Customizing Guide).
Standard settings
Rule Automatic Processing SeqNr OrgUnit Field Compare Partner Field
SAP0050 X 10 REFNR Equal REFNR
SAP0100 __ 10 RTCUR Equal RTCUR
SAP0100 __ 20 TSL Opposite Amount TSL
SAP0200 __ 10 RTCUR Not Equal RTCUR
SAP0200 __ 20 TSL Equal TSL
Activities
Example
Recommendation
The processing of rules containing conditions other than Equal is very time consuming. You should use Equal as the only condition for rules which are supposed to be processed automatically.
We recommend that you use only the rule REFNR = REFNR for automatic assignments. This rule assigns all documents that are related to the same business transaction to each other if the reference number was posted correctly. All documents with the same reference number are then assigned to each other during automatic assignment. You should not add an additional condition to the automatic rule, for example, RTCUR = RTCUR (matching transaction currency), TSL -1 TSL (matching amount), or RCOMP = RASSC (documents posted by the same company are not assigned to each other).
It does not make sense from a business logic point of view to assign documents to each other only if the amounts match. If several documents have been assigned to the same business transaction by posting the same reference number, the user should be able to see all documents belonging to that business transaction right away. This is the main purpose of the bottom part of the interactive reconciliation screen.
Note
The more document groups with a difference are displayed in the bottom part of the screen, the faster it is to find the documents causing the difference on the business partner level. It does not help the reconciliation process if only document groups netting to zero are displayed in the bottom part of the screen. This means is that the user has additional manual effort in finding documents posted with reference to the same business transaction before being able to determine which documents are causing the difference.
The goal of intercompany reconciliation is to identify all documents belonging to the same business transaction and to make sure that these documents were posted correctly. If one of the documents was not posted correctly (for example, with wrong amount and / or transaction currency), it speeds up the reconciliation process if the user can see this document group and notice at first glance which document stands out and needs to be corrected.
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 1 | Mandatory 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 | SIMG_CFMENUFBRC009 | 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 |
| VC_FBRC0085 | C - View cluster | FBRC005 |
History
| Last changed by/on | SAP | 20041110 |
| SAP Release Created in | 500 |
