Vous êtes sur la page 1sur 35

Ralph Stadter Development Support Financials

Intercompany Reconciliation
Background Information & Customizing Guide
2 ! "#rz 2 $%
&ersion $!$

Intercompan' Reconciliation

Table of Contents:
1 Purpose of this document................................................................................................5 2 Back round information..................................................................................................5
2.1 !n"ironment.............................................................................................................................................. 5 2.2 Purpose...................................................................................................................................................... 5 2.# Tar et roups............................................................................................................................................ 5 2.$ %upported processes................................................................................................................................ & 2!%!$ (rocess $!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ) 2!%!2 (rocess 2!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ) 2!%!* (rocess *!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ) 2.5 %er"ices..................................................................................................................................................... & 2.& ICR process cycle..................................................................................................................................... ' 2!)!$ Select Documents!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! + 2!)!2 ,ssign Documents ,utomaticall'!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! $2 2!)!* Reconcile Documents "anuall'!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! $* 2!)!% "ain tool-ar functions of the reconciliation screen!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!$. 2!)!. /ther functions of the reconciliation screen!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! $0

# ICR customi(in ..............................................................................................................1)


#.1 Preparations in the Reconciliation %ystem...........................................................................................1) *!$!$ General Settings!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! $+ *!$!2 Data Selection and Storage!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2 *!$!* Data ,ssignment!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2* *!$!% Data Reconciliation!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2% *!$!. Communication Support!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! *$ #.2 Preparations in the %ender %ystem....................................................................................................... #2 *!2!$ General Settings!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! *2 *!2!2 Define 1nhancements!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! *2 *!2!* /pen Item Reconciliation!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! *2 *!2!% G2 ,ccount Reconciliation!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! *2

$ Technical *etails.............................................................................................................#2
$.1 *ata %election.......................................................................................................................................... #2 $.2 *ata +ssi nment..................................................................................................................................... #5

5 Chan e ,istory................................................................................................................#5

Seite

Intercompan' Reconciliation

Table of -i ures:
Table 1: Pro rams for *ocument +ssi nment...............................................................12 Table 2: Pro rams for .anual *ocument Reconciliation..............................................1# Table #: -BICR1 / %tatus Icons........................................................................................1$ Table $: Process 001 +ttributes.......................................................................................1) Table 5: Process 002 +ttributes.......................................................................................11 Table &: Process 002 +ttributes.......................................................................................11 Table ': ICR *atabase Tables...........................................................................................11 Table ): -ield Catalo s / .andatory Role +ssi nments...............................................20 Table 1: -ield Catalo s / Recommended Role +ssi nments.......................................20 Table 10: B+dI -B2ICRC20013 -B2ICRC20023 and -B2ICRC200#: +"ailable .ethods ..........................................................................................................................................22 Table 11: Recommended Rule for +utomatic +ssi nment...........................................2# Table 12: B+dI -B2RC2+%%I45.!5T: +"ailable .ethods...........................................2# Table 1#: !6ample %ets.....................................................................................................2$ Table 1$: !6ample %et *efinition 71................................................................................25 Table 15: !6ample %et *efinition 72................................................................................25 Table 1&: Process 001 / *isplay Cate ory 100 Recei"ables.........................................2' Table 1': Process 001 / *isplay Cate ory 200 Payables..............................................2' Table 1): Process 001 / *isplay Cate ory #00 8pen Items..........................................2' Table 11: Proces 002 / *isplay Cate ory 100 Re"enue................................................2) Table 20: Proces 002 / *isplay Cate ory 200 !6pense.................................................2)

Seite

Intercompan' Reconciliation

Table 21: Process 00# / *isplay Cate ory 100 Recei"ables.........................................2) Table 22: Process 00# / *isplay Cate ory 200 Payables..............................................2) Table 2#: Process 00# / *isplay Cate ory #00 8pen Items..........................................2) Table 2$: Communication %tatus / *eli"ered 9alues...................................................21 Table 25: Processin %tatus / *eli"ered 9alues...........................................................21 Table 2&: B+dI -B2RC2PR!%!5T+TI85: +"ailable .ethods......................................#0 Table 2': *eli"ered Placeholders.....................................................................................#1 Table 2): :ey *ate for 8pen Item %election...................................................................## Table 21: 8rder of *ata %election *ependin on Transfer Type and *ata %ource....## Table #0: +uthori(ations for R-C users..........................................................................## Table #1: Chan e ,istory..................................................................................................#5

Seite

Intercompan' Reconciliation

1 Purpose of this document


3his document is intended for pro4ect mem-ers responsi-le for setting up the Intercompan' Reconciliation functionalit'! It e5plains the delivered standard customizing as 6ell as the options availa-le during configuration!

2 Back round information


3he Intercompan' Reconciliation solution 6as first delivered 6ith release 1R(2 previousl' e5isting programs RFICRC 7 RFICRC $7 and RFICRC2 ! %! It replaces the

2.1 !n"ironment
3he Intercompan' Reconciliation solution 8ICR9 is designed for use in Financial ,ccounting! It provides periodic control of documents 6hich descri-e the accounting transactions 6ithin the corporate group! ICR selects documents across S,( s'stems and clients! It is also possi-le to integrate e5ternal data into the reconciliation process! In order to avoid currenc' conversion differences7 the documents are reconciled in the transaction currenc'!

2.2 Purpose
3he purpose of ICR is to ensure that intercompan' documents from accounting transactions 6ithin the corporate group correspond to one another! It contains tools 6hich check that documents have -een correctl' assigned to a -usiness transaction and 6hich also ena-le 'ou to find corresponding documents easil' and to make additional assignments! ICR operates on the level of companies and partner companies 8trading partners9! If the reconciliation process is successful this 6ill ultimatel' lead to reduced differences in corporate group consolidation!

2.# Tar et roups


3here are t6o main groups 6ho 6ould -enefit from using this solution: $! Firstl'7 individual companies 6ould -enefit from matching up documents7 -ecause the' need to ensure that their o6n documents from accounting transactions correspond to the documents of internal trading partners to avoid dela's and disputes 6hen pa'ments are supposed to -e processed! 2! 3he consolidation parent can then make a glo-al check of the results for all the companies! 3he program is designed to maintain constant control and can -e run at an' time! 3his means that the deadline pressure 6hich normall' arises during monthl' closing and 'ear end closing can -e avoided!

Seite

Intercompan' Reconciliation

2.$ %upported processes


3he follo6ing processes are supported -' the delivered programs: Process 001 Process 002 Process 00# G2 /pen Items ,ccounts Customer;&endor /pen Items

2.$.1 Process 001


3his process is intended for reconciliation of open items! <ou should choose this process if most of 'our intercompan' receiva-les and pa'a-les are posted to G2 accounts!

2.$.2 Process 002


3his process is intended for reconciliation of documents 6hich are posted to accounts 6hich do not have open item management! 3his process is mostl' used for reconciliation of profit and loss accounts!

2.$.# Process 00#


3his process is intended for reconciliation of open items! <ou should choose this process if most of 'our intercompan' receiva-les and pa'a-les are posted to customer and vendor accounts!

2.5 %er"ices
3he ICR solution consists of 2 parts: $! (rocess independent services 2! (rocess dependent components 3he process independent services can also -e used for customer defined processes! Depending on the specific re=uirements 'ou ma' 6ant to cop' the programs of the delivered processes and modif' them to 'our re=uirements! 3he process independent services are contained in package FB_RC!

Seite

Intercompan' Reconciliation

2.& ICR process cycle


3he ICR process is -asicall' a c'cle of individual steps as sho6n -elo6:

Intercompany Reconciliation Process

Data Selection

Data Storage

Post Corrections *

Data Presentation & Analysis

Communication

; +"ailable throu h pro rammin interface <B+dI=


S,( ,G 2 .7 Intercompan' Reconciliation7 %

-i ure 1: ICR Process Cycle Data 6ill first -e selected from the sender s'stems and then stored centrall' in the reconciliation s'stem! 3he data is anal'zed and issues are communicated to the involved accountants! ,fter this corrections 8as 6ell as ne6 documents9 are posted! 3hese 6ill then -e included in the ne5t data selection! 3hese steps are represented in the programs to -e e5ecuted for ICR: $! Select Documents 2! ,ssign Documents ,utomaticall' *! Reconcile Documents "anuall' Data Selection & Data Storage (reparation for Data (resentation & ,nal'sis Data (resentation & ,nal'sis and Communication

3he programs and transactions involved in these steps depend on the reconciliation process!

Seite

Intercompan' Reconciliation

2.&.1 %elect *ocuments


>hen data selection is performed the relevant document lines are selected from the sender s'stems and stored in the reconciliation s'stem! >hich document lines are relevant depends on the process as 6ell as the time period of the current reconciliation c'cle! 2.&.1.1 Process 001: 4> 8pen Items 3he program for data selection of process $ is FBICRC $?D,3,?S12 and is assigned to transaction code FBICS$! 3he program can -e found in the S,( menu under the follo6ing path: SAP menu Accounting Financial Accounting General Ledger Periodic Processing Closing Check/Count Intercompany Reconciliation !pen Items

-i ure 2: -BIC%1 / %election %creen 3he program 6ill select the relevant data records for the specified companies! 3he fiscal 'ear and period 6ill -e used to determine the ke' date for the selection of open items! 3he program 6ill produce a protocol displa'ing some statistical information a-out the program run as 6ell as messages for an' issues that came up during the program run!

Seite

Intercompan' Reconciliation

-i ure #: -BIC%1 / Protocol

Seite

Intercompan' Reconciliation

2.&.1.2 Process 002: +ccounts 3he program for data selection of process 2 is FBICRC 2?D,3,?S12 and is assigned to transaction code FBICS2! 3he program can -e found in the S,( menu under the follo6ing path: SAP menu Accounting Financial Accounting General Ledger Periodic Processing Closing Check/Count Intercompany Reconciliation Accounts

-i ure $: -BIC%2 ? %election %creen 3he program 6ill select the relevant data records for the specified companies! Since this program is not 6orking 6ith open items determining the relevant data records is much more difficult! 3he relevant data records are all intercompan' document lines 6hich have -een posted to accounts to -e reconciled since the last successful data selection! In order to find these document lines the standard logic re=uires that a special ledger is created in the sender s'stems for ta-le FBICRC 23 8or FBICRCS 23 for releases A 1R(2 %9! 3his ledger should -e set up 6ith a ledger selection 6hich 6ill allo6 onl' relevant document lines to -e posted into the ledger: i!e! document lines 6here the trading partner is specified and 6hich are posted to the accounts 6hich 'ou 6ould like to reconcileB additional restrictions can also -e applied according to 'our needs! 3he program 6ill then select the ne6l' posted line items from this ledger and mark the selected line items as transferred 8field R3<(1 is set to %9! In case some of the previousl' transferred items have to -e transferred again 'ou have to mark the check-o5 Reselect "ata and specif' the posting date for 6hich the data is supposed to -e retransferred! 3he program 6ill produce a protocol displa'ing some statistical information a-out the program run as 6ell as messages for an' issues that came up during the program run! 3he content of the protocol is essentiall' the same as for FBICS$ 6hich is 6h' no screen shot is included here!

Seite

Intercompan' Reconciliation

2.&.1.# Process 00#: Customer @ 9endor 8pen Items 3he program for data selection of process * is FBICRC *?D,3,?S12 and is assigned to transaction code FBICS*! 3he program can -e found in the S,( menu under the follo6ing path: SAP menu Accounting Financial Accounting Customers Periodic Processing Closing Check/Count Cross#System Intercompany Reconciliation /r SAP menu Accounting Financial Accounting $endors Periodic Processing Closing Check/Count Cross#System Intercompany Reconciliation

-i ure 5: -BIC%# / %election %creen 3he program 6ill select the relevant data records for the specified companies! 3he fiscal 'ear and period 6ill -e used to determine the ke' date for the selection of open items! 3he program 6ill produce a protocol displa'ing some statistical information a-out the program run as 6ell as messages for an' issues that came up during the program run!

Seite

$$

Intercompan' Reconciliation

2.&.2 +ssi n *ocuments +utomatically


,fter the relevant documents have -een transferred to the reconciliation s'stem the' are anal'zed -' this program! 3he program tries to find documents -elonging to the same -usiness transaction using customiza-le rules! "atching documents are assigned to each other! 3he follo6ing programs are availa-le for the individual processes: Process $ 2 * Pro ram FBICRC FBICRC FBICRC $?D,3,?,SSIGC 2?D,3,?,SSIGC *?D,3,?,SSIGC Transaction FBIC,$ FBIC,2 FBIC,*

Table 1: Pro rams for *ocument +ssi nment 3he paths in the S,( menu are the same as for the data selection programs! 3he protocols of the programs provide some statistical information a-out the num-er of records anal'zed and the num-er of records 6hich could -e assigned using the rules set up in customizing! 3he follo6ing screen shot sho6s the protocol of FBIC,$! 3he protocols of the other programs provide the same information!

-i ure &: -BIC+1 / Protocol

Seite

$2

Intercompan' Reconciliation

2.&.# Reconcile *ocuments .anually


3his is the main transaction for intercompan' reconciliation! It is geared to6ards finding documents 6hich cause differences! 3he follo6ing programs are availa-le for the individual processes: Process $ 2 * Pro ram FBICRC FBICRC FBICRC $?D,3,?R1C 2?D,3,?R1C *?D,3,?R1C Transaction FBICR$ FBICR2 FBICR*

Table 2: Pro rams for .anual *ocument Reconciliation 3he program produces an overvie6 screen 6ith a tree structure sho6ing the compan' relationships 6hich re=uire reconciliation:

-i ure ': -BICR1 ? 8"er"ieA %creen 3he tree sho6s the compan' on the first level and the partner on the second level! 3he third level contains a link to the documents to -e reconciled! 3he second column sho6s the difference on the -usiness relationship level in the displa' currenc' 6hich the user can specif' on the selection screen! ,s mentioned -efore ICR 6orks on transaction currenc' amounts! But in order to displa' one total per -usiness relationship the transaction currenc' values are converted into a displa' currenc' during program e5ecution! 3he user can specif' the displa' currenc' to -e used on the selection screen! /nl' the -usiness relationships re=uiring action are displa'ed per default 8icons and 9!

Seite

$*

Intercompan' Reconciliation

Icon

.eanin Differences e5ist Co differences e5ist7 -ut some documents have not -een assigned 'et! 3heoreticall' this could -e caused -' several incomplete -usiness transactions 6hich are not -alanced 6ithin themselves -ut the overall -alance is zero -' coincidence! Co differences e5ist and all documents have -een assigned Co data records are availa-le for this -usiness relationship

Table #: -BICR1 / %tatus Icons 1ntries 6ith status Function Function Function and can -e added -' using the corresponding functions in the treeDs tool-ar! controls the size of the tree displa'! List !utput displa's the contents of the tree in a list! %ser Settings allo6s the user to maintain some detailed parameters!

3he user 6ill then click on one of the differences to displa' the documents for a -usiness relationship!

-i ure ): -BICR1 / Reconciliation %creen 3he screen is divided into * areas! 3he unassigned documents posted -' the compan' of the selected -usiness relationship are displa'ed in the left top area! 3he unassigned documents posted -' the partner of the selected -usiness relationship are displa'ed in the right top area! Documents 6hich 6ere assigned either automaticall' or manuall' are displa'ed in the -ottom part of the displa'! Eo6ever7 -' default document groups 6ith a -alance or zero are not displa'ed! 3he' can -e added to the displa' using function ! 3he la'out of the individual displa' areas can -e changed according to the userDs re=uirements!

Seite

$%

Intercompan' Reconciliation

2.&.$ .ain toolbar functions of the reconciliation screen


3he user can look for matching documents manuall'7 select them and assign them using function Assign Items! 3he assigned items 6ill then -e added to the -ottom part of the displa'! If the -alance of this ne6 document group is zero it 6ill not -e displa'ed! 3he user can also have the program suggest assignments using function Suggest Assignments! 3his 6ill displa' a list of rules 6hich can -e set up in customizing! ,fter the user selects one of the rules the unassigned documents are anal'zed using the selected rule and assignments are suggested! 3he selected rule in this e5ample checks for documents 6ith the same transaction currenc' and matching amounts!

-i ure 1: -BICR1 / %u

est +ssi nments

3he user can no6 anal'ze the suggestions7 select documents to -e assigned to each other7 and assign them using function Assign Items! Function "elete From "isplay 6ill delete the selected documents from the suggestion displa'! Function &nd Suggestions 6ill return the user to the previous screen! Note ,ll selected items 6ill -e assigned to the same document group independent of the displa'ed temporar' group num-er! 3his re=uires the user to anal'ze all of the suggestions -efore accepting the suggested assignments! (lease note as 6ell7 that the suggested document groups 6ill not necessaril' -alance to zero 8see group num-er 3 * in the a-ove screen shot9! Function Communication 6ill start a dialog 6hich can -e used to send template -ased messages to accountants in the partner compan'! ,s a first step the user has to select a template and the language of the message:

Seite

$.

Intercompan' Reconciliation

-i ure 10: -BICR1 / %elect Template /n the ne5t screen the user is offered contact persons 6hich the message is supposed to -e sent to! (er default the contact persons for the partner in the selected -usiness relationship are displa'ed! ,fter confirming the selected recipients the user 6ill -e taken to the S,(office send screen! 3he user can send the message 6ithout an' additional actions or displa' the document and edit it manuall' if necessar'! ,ll S,(office functions are availa-le for the document! Note <ou can use S,(office to send the messages e5ternall' to 'our email client! 3he user can specif' a default recipient in the %ser Settings and that 6a' receive a cop' of the correspondence in the email client as 6ell! ,fter sending the message or canceling the dialog the user returns to the reconciliation screen! Note If the message 6as sent successfull' the Communication Status of the documents 6hich the message 6as sent for is automaticall' set to 'ail Sent! If the user select the menu part of function Communication other related functions are also availa-le!

Function Set Status allo6s the user to set the status for a document! 3he standard status fields are Processing Status and Communication Status! /ther status fields can -e added through customizing!

Seite

$)

Intercompan' Reconciliation

2.&.5 8ther functions of the reconciliation screen


3he first functions in the tool-ar for each ,2& grid displa'ing documents are standard functions 6hich 6ill not -e e5plained in detail in this document: ,dditional ,2& standard functions are availa-le through Standard Functions! 3he' can also -e added to the ,2& grid tool-ar through this function! Standard Functions Sho( Functions in AL$ )ool*ar )emporarily or F (ermanentl'! Function "isplay "ocument 6ill displa' the original document in the original s'stem of the document! 3his is onl' availa-le if the original document is from an S,( s'stem and the appropriate RFC connection has -een maintained! Function Ser+ices ,or !*-ect allo6s the users to maintain pu-lic notes and attachments as 6ell as private notes! Function Function deletes the assignment of documents to a document group! controls the size of the -ottom part of the displa'!

Seite

$0

Intercompan' Reconciliation

# ICR customi(in
3he customizing is availa-le through the standard I"G 8transaction SPR!9 as 6ell as 2 additional transactions 6hich displa' the su-tree specific to Intercompan' Reconciliation: 3ransaction -BICI.4 Customizing for processes $ and 2 3his customizing is availa-le in S(R/ through the follo6ing path: SAP Customi.ing Implementation Guide Financial Accounting General Ledger Accounting Business )ransactions Closing Check / Count Cross#System Intercompany Reconciliation or SAP Customi.ing Implementation Guide Financial Accounting /0e(1 General Ledger Accounting /0e(1 Periodic Processing Check / Count Cross# System Intercompany Reconciliation Customizing for process * 3his customizing is availa-le in S(R/ through the follo6ing path: SAP Customi.ing Implementation Guide Financial Accounting Accounts Recei+a*le and Accounts Paya*le Business )ransactions Closing Count Cross#System Intercompany Reconciliation or SAP Customi.ing Implementation Guide Financial Accounting /0e(1 Accounts Recei+a*le and Accounts Paya*le Business )ransactions Closing Count Cross#System Intercompany Reconciliation

3ransaction -BICI.4#

#.1 Preparations in the Reconciliation %ystem


#.1.1 4eneral %ettin s
#.1.1.1 *efine Reconciliation Process +ttributes 3his customizing step contains some -asic settings for each reconciliation process! 3he delivered settings are sufficient and do not need to -e changed! (lease refer to the field documentation for additional information! Process 001 -ield Description Structure for Gnassigned Items Structure for ,ssigned Items Determine Group Reference ,utomaticall' ,pplication ID "essage 3emplate Group Contact (erson Data-ase Do Cot Displa' 3otals /vervie6 Screen Table $: Process 001 +ttributes H 9alue Intercompan' Reconciliation: G2 /pen Items FBICRC?S?DIS(2,<? FBICRC?S?DIS(2,<? H FBRC $ $ $ $?,SSIGC1D

Seite

$+

Intercompan' Reconciliation

Process 002 -ield Description Structure for Gnassigned Items Structure for ,ssigned Items Determine Group Reference ,utomaticall' ,pplication ID "essage 3emplate Group Contact (erson Data-ase Do Cot Displa' 3otals /vervie6 Screen Table 5: Process 002 +ttributes Process 00# -ield Description Structure for Gnassigned Items Structure for ,ssigned Items Determine Group Reference ,utomaticall' ,pplication ID "essage 3emplate Group Contact (erson Data-ase Do Cot Displa' 3otals /vervie6 Screen Table &: Process 002 +ttributes #.1.1.2 Create +dditional -ields

9alue Intercompan' Reconciliation: ,ccounts FBICRC?S?DIS(2,<? FBICRC?S?DIS(2,<? H FBRC 2 2 2 2?,SSIGC1D

9alue Intercompan' Reconciliation: Cust!;&en! /pen Items FBICRC?S?DIS(2,<? FBICRC?S?DIS(2,<? H FBRC * * H * *?,SSIGC1D

<ou can use the I"G step to define additional fields 'ou 6ould like to use during Intercompan' Reconciliation! 3he fields are defined separatel' for each process! 3he additional fields 6ill -e generated into the ICR data-ase ta-les: Process I* >ine Item Table Totals Table $ 2 * Table ': ICR *atabase Tables >hether a field is added to the 2ine Item 3a-le and;or the 3otals 3a-le depends on the 2evel of ,vaila-ilit' 'ou choose for the ne6 field! (lease refer to the field documentation for further information! #.1.1.# +cti"ate Processes 3he ICR solution uses the FIIS2 posting frame6ork to store document and totals information! 3he ta-les 6ere created as Special 2edger ta-les! In order to reduce the impact of unused processes the ta-les can -e deactivated in this I"G step! (lease set the flag Inacti+e for the processes 6hich 'ou 6ill not -e using! FBICRC FBICRC FBICRC $, 2, *, FBICRC FBICRC FBICRC $3 23 *3

Seite

$@

Intercompan' Reconciliation

#.1.1.$ +cti"ate Transaction *ata Tables 3his step 6ill add the additional fields 'ou customized to the transaction data ta-les and displa' structures and generate the FIIS2 posting frame6ork! If 'ou created an' additional fields the' 6ill not -e visi-le in the field catalog until this step has -een e5ecuted! Since the FIIS2 posting frame6ork is generated in this step 8if there 6ere an' changes 6hich re=uire the generation9 'ou have to -e careful a-out the time of e5ecution for this step! 3here should not -e an' documents posted in an' client of the s'stem 6hile this program is e5ecuted! #.1.1.5 .aintain -ield Catalo s In this step 'ou can assign predefined roles to the fields of the ICR data-ase ta-les! 3he follo6ing role assignments are mandator' for processes $ to *! -ield 5ame Role GRR1F R,SSC RC/"( R3CGR 3S2 Group Reference Cum-er 2eading (artner Gnit 2eading /rganisational Gnit (rimar' Currenc' Je' (rimar' ,mount

Table ): -ield Catalo s / .andatory Role +ssi nments 3he follo6ing role assignments are recommended! If 'ou do not 6ant to use the delivered status fields 'ou can assign the role Su-assignment instead! -ield 5ame Role CS3,3 (S3,3 Status Field Status Field

Table 1: -ield Catalo s / Recommended Role +ssi nments If 'ou added an' other fields to -e used as status fields 'ou should also assign the role %tatus -ield to these fields! (lease refer to the field documentation for further information!

#.1.2 *ata %election and %tora e


#.1.2.1 *efine Reconciliation Process *etail +ttributes 3his step defines some of the details regarding data selection and storage for each of the reconciliation processes! Reconciliation Process *etail +ttributes 3he Fiscal 2ear $ariant is used to derive the ke' date for open item selection in processes 3he Group Chart o, Accounts is used in processes Pro ram 8ptions If 'ou set the flag "isplay Company 0ame in Reconciliation "isplay the name of the compan' as maintained in ta-le 3++ 6ill -e displa'ed in the navigation tree ne5t to the compan' ID! <ou can specif' a version to -e used as a default for the main transactions of the process! &ersions pla' a secondar' role in the reconciliation process! Since the field is availa-le due to the FIIS2 frame6ork it can -e used to create separate sets of data! <ou can use different versions for testing purposes for e5ample! Eo6ever7 for productive use 'ou should al6a's use the same version since document details like assignment and status are version dependent! If 'ou set the flag 3ide $ersion ,rom Selection Screens the field 6ill not -e availa-le for input on the selection screen! 3hat 6a' 'ou avoid issues 6ith users 6orking in separate versions although the' should not! $ and $ and *! 2 to determine the relevant accounts!

Seite

Intercompan' Reconciliation

If 'ou set the flag Sho( Se4uential 0um*er on Selection Screen o, "ata Selection Program this field 6ill -e availa-le for input on the selection screen! (lease refer to the field documentation for additional information and dependencies! <ou can also specif' a "isplay Currency as a default for manual document reconciliation! 3he flag 3ide "isplay Currency From Selection Screen ena-les 'ou to enforce a displa' currenc' for all users! *ata %election If 'ou choose the Selection Strateg' 'inimi.e num*er o, RFC calls the data selection program 6ill select all relevant documents from the sender s'stems using one RFC call per sender s'stem! If 'ou set the flag Selection Strategy Is "e,ault !nly 'ou can specif' for each compan' 6hether the data of that compan' should -e selected in the collective RFC call or in a separate one! Example 3here are . companies 6ith data in s'stem (R$! 3he data volume for three of these companies is relativel' lo6! 3he other t6o companies have a lot of intercompan' postings on (R$! In order to optimize the runtime of the data selection 'ou specif' 'inimi.e num*er o, RFC calls as the selection strateg' and set the flag Selection Strategy Is "e,ault !nly! In the compan' specific settings 'ou set the flag Separate Selection Process for the t6o companies 6ith the high data volume! 3he data selection program 6ill start three separate RFC calls to the sender s'stem! 3he first one 6ill select the data for the three companies 6ith lo6 data volume! 3he other t6o calls 6ill select the data for the -igger companies! If 'ou choose the Selection Strateg' 'inimi.e data trans,er +olume per RFC call the data selection program 6ill create a separate call to the sender s'stem for each compan'! 3he Sender Ledger specifies 6hich ledger data for process 2 is to -e read from during data selection! If 'ou set the flag Sender Ledger Is "e,ault !nly 'ou can specif' a different sender ledger per compan'! 3he data selection program 6ill store the selected documents in the Recei+ing Ledger! Note 3he ledgers 'ou specif' here do not actuall' have to -e created in the Special 2edger customizing unless 'ou 6ant to use additional S2 functions like reporting! In order to ena-le later addition of general S2 services 'ou have to specif' a ledger name! <ou can specif' an' ledger 6hich has not -een created 'et! Eo6ever7 'ou should -e careful not to create a ledger 6ith this name for a different purpose later in time! If 'ou do create ledgers in I"G activit' "e,ine Ledger 'ou must set the properties of the ledgers as descri-ed in the documentation of that activit'!

Note For process 2 the data selection program 6ill ignore all local companies 6hich have the same Sender 2edger and Receiving 2edger! #.1.2.2 *efine >ed er In this I"G step 'ou can set up a Special 2edger! (lease note that for the core functionalit' of ICR it is not necessar' for 'ou to set up a Special 2edger in the Reconciliation S'stem! <ou onl' need to set up a ledger if 'ou 6ant to use general S2 functionalit' 8e!g! reporting9! If 'our reconciliation s'stem is also used as a sender s'stem 8i!e! there is a productive compan' code running in the same client of the same s'stem9 'ou have to create the sender ledger! "ore details are availa-le in the section 56768 GL Account Reconciliation! Before 'ou can define an' ledgers for ICR 'ou have to make sure that glo-al ledgers are active 8transaction GC&/: I"G path Financial Accounting Special Purpose Ledger Basic Settings Per,orm Preparation or Financial Accounting /ne(1 Special Purpose Ledger Basic Settings Per,orm Preparation9!

Seite

2$

Intercompan' Reconciliation

#.1.2.# *efine !nhancements Gse this activit' to implement B,dIs FB?ICRC? 3he follo6ing B,dI methods are availa-le: .ethod ,DD?FI12DS?3/?B1?S121C31D ,DD?ICF/R",3I/C?3/?D,3,?R1C/RD $7 FB?ICRC? 27 and FB?ICRC? *! +"ailable in B+dI FB?ICRC? FB?ICRC? FB?ICRC? FB?ICRC? FB?ICRC? FB?ICRC? FB?ICRC? FB?ICRC? FB?ICRC? FB?ICRC? FB?ICRC? FB?ICRC? FB?ICRC? FB?ICRC? FB?ICRC? FB?ICRC? FB?ICRC? FB?ICRC? FB?ICRC? FB?ICRC? FB?ICRC? FB?ICRC? $7 * $7 27 * $7 27 * $7 27 * * $ $7 27 * $7 27 * $7 27 *

Bse ,dd additional fields to -e selected from FI document ta-le Change field contents of a data record to -e reconciled ,dd or delete data records to -e reconciled

CE,CG1?D,3,?3,B21

CE,CG1?D,3,?3,B21?S1CD1R?S<S

,dd or delete data records to -e reconciled in the sender s'stem Convert G2 /pen Items to -e used in (rocess * Convert ,R;,( /pen Items to -e used in (rocess $ "ap compan' IDs in case the' are not consistent throughout the s'stem landscape 8this can also -e achieved in method ,DD?ICF/R",3I/C?3/?D,3,?R1C/RD ,dd data from e5ternal sources using selfI defined logic Change the selection restrictions of data selection

C/C&1R3?D,3,?FR/"? C/C&1R3?D,3,?FR/"? ",(?C/"(,C<?IDS

$ *

SG((2<?/3E1R?D,3,

R1S3RIC3?S121C3I/C

Table 10: B+dI -B2ICRC20013 -B2ICRC20023 and -B2ICRC200#: +"ailable .ethods (lease refer to the implementation of C2?I"?FB?ICRC? $ for detailed information and e5ample implementations of the individual methods! 3his class implements the interface of B,dI FB?ICRC? ho6ever7 the implementation can also -e used for other processes 6ith minor ad4ustments! #.1.2.$ Companies to be Reconciled 3his part of the customizing allo6s 'ou to define the properties for all companies 6hich are supposed to -e included in reconciliation! 3here is e5tensive documentation availa-le for the individual fields! (lease refer to this documentation during customizing! $7

Seite

22

Intercompan' Reconciliation

#.1.# *ata +ssi nment


#.1.#.1 .aintain 5umber Ran e for 4roup Reference 5umbers Gse this I"G step to set up the num-er range intervals for the group reference num-ers of the individual reconciliation processes! (lease note that 'ou have to maintain the num-er range interval 10 for each of the processes 'ou 6ould like to use! #.1.#.2 *efine Rules for *ocument +ssi nments In this part of the customizing 'ou can set up rules 6hich can -e used to find matching documents! <ou can set them up to -e used during Automatic Assignment or to -e availa-le during Manual Reconciliation! Note If 'ou set the flag %se Rule "uring Assignment Program Run for a rule it 6ill -e used during automatic assignment! 3hese rules are not availa-le during manual reconciliation! <ou should set up the follo6ing rule for automatic assignment: Rule %eC5r 8r Bnit -ield $ $ R1FCR Compare 1=ual Partner -ield R1FCR

Table 11: Recommended Rule for +utomatic +ssi nment 3his rule 6ill assign all documents 6hich are related to the same -usiness transaction to each other if the reference num-er 6as posted correctl'! <ou should esta-lish organizational rules 6ithin the corporate group 6hich 6ill ensure that all intercompan' transactions are posted 6ith the proper reference num-er! ,ll documents 6ith the same reference num-er should then -e assigned to each other during automatic assignment! <ou should not add an additional condition to the automatic rule that the amounts should match! First of all using operators other than Equal has a severe impact on the performance of automatic assignment! ,lso7 it does not make sense from a -usiness logic point of vie6 to assign documents to each other onl' if the amounts match! If several documents have -een assigned to the same -usiness transaction -' posting the same reference num-er then the user should -e a-le to see all documents -elonging to that -usiness transaction right a6a'! 3he main goal of intercompan' reconciliation is to identif' all documents -elonging to the same -usiness transaction and to make sure that these documents 6ere posted correctl'! If one of the documents 6as not posted correctl' 8e!g! 6ith 6rong amount and ; or transaction currenc'9 it speeds up the reconciliation process if the user can see this immediatel' 6hen anal'zing the documents during Interactive Reconciliation! ,ll necessar' information is availa-le right a6a'7 i!e! the user can see immediatel' 6hich document 6as posted incorrectl' and re=uest a correction posting! If documents are onl' assigned to each other if the amounts match7 the users have to tr' and find documents -elonging to the same -usiness transaction -efore -eing a-le to check 6hether or not the' 6ere posted correctl'! 3his slo6s do6n the process unnecessaril'! #.1.#.# *efine !nhancements Gse this activit' to implement B,dI FB?RC?,SSIGC"1C3! 3he follo6ing B,dI methods are availa-le: .ethod (R/C1SS?,F31R?,SSIGC?,22 (R/C1SS?,F31R?,SSIGC?SICG21 Bse 15ecuted after all rules have -een processed 15ecuted after each rule has -een processed

Table 12: B+dI -B2RC2+%%I45.!5T: +"ailable .ethods (lease refer to the implementation of C2?I"?FB?RC?,SSIGC"1C3 for detailed information and e5ample implementations of the individual methods!

Seite

2*

Intercompan' Reconciliation

#.1.$ *ata Reconciliation


#.1.$.1 %et Bp Reconciliation *isplay In this step 'ou can specif' 6hether the navigation tree in the reconciliation displa' is supposed to -e using the primar' organizational units onl' or the secondar' organizational units as 6ell! 3he second option is onl' availa-le if 'ou added fields as secondar' organizational units 8I"G activit' Create Additional Fields: additional fields have to -e set up 6ith A+aila*ility K3otals Items: Su-assignmentLB I"G activit' Maintain Field Catalogs: additional fields must have -een assigned the roles KSecondar' /rganizational GnitL and KSecondar' (artner GnitL respectivel'9! #.1.$.2 *efine %ets In this activit' 'ou have to set up value sets 6hich 6ill -e used in the ne5t I"G step Set Up Display Categories and Subcategories! 3he sets simpl' contain the values 6hich 6ill -e used to separate the individual t'pes of accounts used in intercompan' reconciliation! 3his is a rather technical part of the customizing for 6hich 'ou need to kno6 some technical details a-out G2 accounts and customer ; vendor accounts! In field Description 'ou can enter a te5t 6hich identifies the set for 'ou! In field Data Element 'ou should specif' the data element used for the field in the check ta-le of the characteristic 'ou 6ant to use! 3he main thing a-out the data element is that the technical settings have to -e correct 8i!e! t'pe7 length7 conversion e5it9! If 'ou 6ant to -uild sets for G2 accounts 'ou should use data element SA90R! If 'ou 6ant to -uild sets for customer accounts 'ou should use data element 9%00R7 for vendor accounts LIF0R! 3he other fields are optional and onl' necessar' if 'ou 6ould like to have value help and te5ts availa-le 6hen maintaining the single entries for the sets! %et I* $ 2 * % %$ %2 %* . .$ .2 .* ) 0 *escription ,ll ,ccounts G2 Receiva-les G2 (a'a-les Revenue ,ccounts Revenue Eard6are Revenue Soft6are Revenue 2icenses 15pense ,ccounts 15pense Eard6are 15pense Soft6are 15pense 2icenses Customers &endors *ata !lement S,JCR S,JCR S,JCR S,JCR S,JCR S,JCR S,JCR S,JCR S,JCR S,JCR S,JCR JGCCR 2IFCR Te6t Table SJ,3 SJ,3 SJ,3 SJ,3 SJ,3 SJ,3 SJ,3 SJ,3 SJ,3 SJ,3 SJ,3 JC,$ 2F,$ Te6t -ield 3H3. 3H3. 3H3. 3H3. 3H3. 3H3. 3H3. 3H3. 3H3. 3H3. 3H3. C,"1$ C,"1$ %uperordinate Characteristic AChart of ,ccountsM AChart of ,ccountsM AChart of ,ccountsM AChart of ,ccountsM AChart of ,ccountsM AChart of ,ccountsM AChart of ,ccountsM AChart of ,ccountsM AChart of ,ccountsM AChart of ,ccountsM AChart of ,ccountsM

Table 1#: !6ample %ets In field Text Table 'ou can specif' the te5t ta-le for the characteristic for 6hich 'ou 6ant to create the set! For G2 accounts 'ou should specif' S9A) as te5t ta-le! For customer accounts the te5t ta-le is 90A:7 for vendor accounts LFA:! In field Text Field 'ou can specif' the field of the te5t ta-le 6hich contains the descriptive te5t for the accounts! For G2 accounts the te5t field is );)<=7 for customer and vendor accounts it is 0A'&:! Field Superordinate C aracteristic needs to -e maintained if the te5t ta-le contains ke' fields other than client7 language ke'7 and the characteristic itself! For G2 accounts 'ou need to specif' the Chart o, Accounts 'ou 6ant to use! For customer and vendor accounts 'ou do not need to specif' an'thing!

Seite

2%

Intercompan' Reconciliation

%ets: %in le !ntries In this part of the set customizing 'ou can specif' the actual values 6hich are supposed to -e contained in a set! 1ach set can have several entries! (lease note that the individual entries are com-ined 6ith each other 6ith a logical !R! Example %et %$ %$ Re+enue 3> Re+enue 3> %eC5r $ 2 >oA $ * ,i h $@@ *@@

Table 1$: !6ample %et *efinition 71 During the program run each data record is anal'zed 6hether it is contained in a set or not! For this set $ all data records 6hich have an account -et6een $ and $@@ /R * and *@@ are contained 6ithin the set!

Note If 'ou 6ould like to include all possi-le values in a set 'ou can also specif' values 6hich do not represent an actual account! 3he follo6ing set contains all possi-le values for customer7 vendor7 or G2 accounts: %et %eC5r >oA ,i h $ ) 0 All Accounts Customers $endors $ $ $ NNNNNNNNNN NNNNNNNNNN NNNNNNNNNN

Table 15: !6ample %et *efinition 72 #.1.$.# %et Bp *isplay Cate ories and %ubcate ories In this I"G step 'ou set up 6hat categories are supposed to -e used for interactive reconciliation for each process! 3he displa' categories are the third level of the navigation hierarch'! Example Display "ierarc ies (rocess $: !6ample Tree %etup , C$ C2 (a'a-les Receiva-les B C$ C2 /pen Items (rocess 2: !6ample Tree %etup C$ C2 Revenue Comment Compan' (artner Displa' Categor' (a'a-les Displa' Categor' Receiva-les Compan' (artner Displa' Categor' /pen Items containing -oth receiva-les and pa'a-les accounts

Comment Compan' (artner Displa' Categor' Revenue

Seite

2.

Intercompan' Reconciliation

15pense

Displa' Categor' 15pense

Seite

2)

Intercompan' Reconciliation

(rocess *: !6ample Tree %etup , C$ C2 (a'a-les Receiva-les B C$ C2 (a'a-les Receiva-les /pen Items

Comment Compan' (artner Displa' Categor' (a'a-les Displa' Categor' Receiva-les Compan' (artner Displa' Categor' (a'a-les Displa' Categor' Receiva-les Displa' Categor' /pen Items containing -oth receiva-les and pa'a-les accounts

3his maintenance is set up as a hierarch' of * steps: $! Reconciliation (rocesses 2! Displa' Categories *! Displa' Su-categories First 'ou have to choose for 6hich process 'ou 6ould like to maintain the displa' categories! /n the ne5t level 'ou create the displa' categories! ,ll 'ou need to do here is to give the displa' categor' an ID and a description! If 'ou set up several displa' categories the' 6ill -e displa'ed in the order of the Displa' Categor' ID! >hatever 'ou choose as 'our description is the te5t 6hich 6ill -e displa'ed in the navigation hierarch'! /n the third level 'ou specif' 6hich sets are supposed to -e included in the displa'7 i!e! if 'ou choose a displa' categor' in the navigation tree7 6hich documents are supposed to -e sho6n! For each entr' 'ou specif' -oth a set for the compan' and for the partner data records! <ou could look at the displa' categories as sort of a filter for the data to -e reconciled! (lease refer to the e5amples -elo6 for further details! Example Display Categories Process 001: %ubcate ory $ %eC5r $ Company -ield R,CC3 Company %et 2 Recei+a*les Partner -ield R,CC3 Partner %et * Paya*les

Table 1&: Process 001 / *isplay Cate ory 100 Recei"ables %ubcate ory $ %eC5r $ Company -ield R,CC3 Company %et * Paya*les Partner -ield R,CC3 Partner %et 2 Recei+a*les

Table 1': Process 001 / *isplay Cate ory 200 Payables %ubcate ory $ %eC5r $ Company -ield R,CC3 Company %et $ All Partner -ield R,CC3 Partner %et $ All

Table 1): Process 001 / *isplay Cate ory #00 8pen Items

Seite

20

Intercompan' Reconciliation

Process 002: %ubcate ory $ $ $

%eC5r $ 2 *

Company -ield R,CC3 R,CC3 R,CC3

Company %et %$ %2 %* Re+6 3> Re+6 S> Re+6 Lic6

Partner -ield R,CC3 R,CC3 R,CC3

Partner %et .$ .2 .* &?p6 3> &?p6 S> &?p6 Lic6

Table 11: Proces 002 / *isplay Cate ory 100 Re"enue %ubcate ory $ $ $ %eC5r $ 2 * Company -ield R,CC3 R,CC3 R,CC3 Company %et .$ .2 .* &?p6 3> &?p6 S> &?p6 Lic6 Partner -ield R,CC3 R,CC3 R,CC3 Partner %et %$ %2 %* Re+6 3> Re+6 S> Re+6 Lic6

Table 20: Proces 002 / *isplay Cate ory 200 !6pense Process 00#: %ubcate ory $

%eC5r $

Company -ield RCGS3

Company %et ) Customers

Partner -ield R&1CD

Partner %et 0 $endors

Table 21: Process 00# / *isplay Cate ory 100 Recei"ables %ubcate ory $ %eC5r $ Company -ield R&1CD Company %et 0 $endors Partner -ield RCGS3 Partner %et ) Customers

Table 22: Process 00# / *isplay Cate ory 200 Payables %ubcate ory $ $ %eC5r $ 2 Company -ield RCGS3 R&1CD Company %et ) 0 Customers $endors Partner -ield R&1CD RCGS3 Partner %et 0 ) $endors Customers

Table 2#: Process 00# / *isplay Cate ory #00 8pen Items

Seite

2+

Intercompan' Reconciliation

#.1.$.$ *efine Possible %tatus for *ocuments In this activit' 'ou can maintain the status te5ts and icons to -e used during interactive reconciliation! 36o status fields are defined as part of the standard deliver': $! Communication Status 2! (rocessing Status 3he follo6ing status icons and values are delivered as part of the standard for each process: Communication %tatus %tatus $ 2 * % Te6t "ail Sent Fa5 Sent 3alked on (hone Created Cote Icon

Table 2$: Communication %tatus / *eli"ered 9alues Processin %tatus %tatus $ 2 * % Te6t In (rocess /n Eold Clarification Ceeded Re=uested Correction (osting Icon

Table 25: Processin %tatus / *eli"ered 9alues

Seite

2@

Intercompan' Reconciliation

#.1.$.5 *efine !nhancements Gse this activit' to implement B,dI FB?RC?(R1S1C3,3I/C! 3he follo6ing B,dI methods are availa-le: .ethod ,DD?CGS3/"1R?GI?FGCC3I/CS CE,CG1?DIS(2,<?GRID CE,CG1?"1SS,G1 CE,CG1?C,&IG,3I/C?3R11 CE1CJ?,SSIGC?/J CE1CJ?GC,SSIGC?/J C/C3,C3?(1RS/C?CE,CG1?,G3E Bse ,dd Functions to "ain 3ool-ar Change (roperties ; Settings of the Grid Controls Change "essage 3e5t 8e!g! Replace (laceholders9 Change (roperties ; Settings of Cavigation 3ree Check >hether ,ssignment Is /J Check >hether ,ssignment "a' Be Deleted Check >hether Gser Eas ,uthorit' to Change Contact (erson Disa-le Standard Functions of Gser Interface Do not useO (rocessing for ,dded Functions ,dd Items to Cavigation 3ree 8e!g! ,dditional Columns9

DIS,B21?S3,CD,RD?GI?FGCC3I/CS ",(?C/"(,C<?IDS (R/C1SS?CGS3/"1R?GI?FGCC3I/CS C,&IG,3I/C?3R11?,DD?I31"S

Table 2&: B+dI -B2RC2PR!%!5T+TI85: +"ailable .ethods (lease refer to the implementation of C2?I"?FB?RC?(R1S1C3,3I/C for detailed information and e5ample implementations of the individual methods!

Seite

Intercompan' Reconciliation

#.1.5 Communication %upport


3he communication support of ICR contains the functions to maintain a contact person data-ase and to create and send template -ased messages! 3he contact persons can -e used as recipients for these messages! #.1.5.1 *efine +pplication I* In this activit' 'ou can define application IDs! 3he mandator' ID for Intercompan' Reconciliation is FBRC 6hich is part of the delivered customizing! #.1.5.2 *efine Contact Person *atabase In this step 'ou can set up the contact person data-ases 'ou 6ould like to use as part of ICR! Simpl' define a contact person data-ase -' specif'ing a Contact (erson Data-ase ID and maintaining a description! In the fields Group By )a*le and Group By Field 'ou can specif' 6hether 'ou 6ould like to group contact persons -' organizational units! If 'ou 6ould like to group the contact persons -' companies 'ou have to specif' ta-le )==: and field RC!'P! Note If 'ou are using secondar' organizational units and 6ould like to organize 'our contact persons accordingl' 'ou 6ould have to specif' a different ta-le and field! >hen using the communication support functionalit' of the interactive reconciliation the program 6ill automaticall' suggest the contact persons maintained for the partner compan' of the current displa'! Depending on the num-er of contact persons per organizational unit 'ou could also group the contact persons -' compan' and then use a field like "epartment to ena-le 'our users to find the -est recipient! Gse function "aintain Contacts to navigate to the contact person maintenance! If 'ou supplied a ta-le and field name 'ou 6ill -e prompted to select an organizational unit! If do not choose an organizational unit the s'stem 6ill displa' the complete list of e5isting contact persons! Eo6ever7 if 'ou create a ne6 contact person this contact person 6ill not -e assigned to an' organizational unit! #.1.5.# .aintain Placeholders for .essa es In this step 'ou can define placeholder to -e used in messages! 3he follo6ing placeholders are delivered for all three processes and 6ill -e replaced -' the standard functionalit' of ICR: Placeholder *escription . $ $. 2 2. * % Table 2': *eli"ered Placeholders If 'ou create additional placeholders 'ou have to replace them in a B,dI implementation 8FB?RC?(R1S1C3,3I/CCE,CG1?"1SS,G19! #.1.5.$ .aintain .essa e Templates In this activit' 'ou can create message templates 6hich can -e used during interactive reconciliation to send messages including information a-out the conte5t and the documents of the current reconciliation! 3he placeholders 6hich 6ere defined in the previous step can -e inserted and deleted using special functions in a tool-ar! <ou can use the function Import )emplate in order to import an' other e5isting template in an' language in 6hich it has -een maintained! 3his is useful if 'ou 6ould like to create a second template 6ith a similar te5t or if 'ou 6ant to translate a template into a different language! Je' Date Compan' Compan'Ps Documents (artner (artnerPs Documents ,ssigned Documents GserPs Came

Seite

*$

Intercompan' Reconciliation

#.2 Preparations in the %ender %ystem


If 'our sender s'stem has a release -efore 1R(2 % please refer to note 0+@2%* for additional information!

#.2.1 4eneral %ettin s


Gse the steps in this part of the I"G to check 6hether the assignments of compan' codes to companies is complete! For process $ and 2 'ou should check 6hether the relevant operational accounts have -een assigned to the appropriate group accounts! For (rocess * 'ou need to check 6hether the customer and vendor accounts have -een set up 6ith the appropriate trading partner!

#.2.2 *efine !nhancements


<ou can implement some of the B,dI methods in the sender s'stem as 6ell! Gse these activities to implement the appropriate ones!

#.2.# 8pen Item Reconciliation


Co additional activities are necessar' for process $ and process *!

#.2.$ 4> +ccount Reconciliation


In order to support data selection from the sender ledger 'ou ma' have to complete the steps in this -ranch of the I"G! <ou need to at least make sure that the ta-les are not inactive and that 'ou define a ledger7 assign the appropriate companies7 activities7 and ledger selections!

$ Technical *etails
$.1 *ata %election
3his part of the document descri-es the program logic of the data selection programs! >hile there are * different data selection programs most of the logic is implemented in class C2?FBICRC?S1R&IC1S! ,s a first step the program selects the specified companies from ta-le FBICRC $ $ and checks 6hether the user is authorized to run data selection for the specified companies 8authorization o-4ect F?R(R/C9! If the user specified an' companies 6ithout having the proper authorization the program 6ill displa' 6arning messages regarding these companies and the' are e5cluded from processing! It is not necessar' to change the selection criteria7 though! If the program is not running in test mode the program 6ill then tr' to lock the companies for 6hich data is supposed to -e selected! If an' of the companies are alread' locked the program 6ill create corresponding messages for the log and e5clude the companies from processing! 3he remaining companies 6ill then -e anal'zed regarding their RFC connections! 3he companies are grouped depending on the RFC connection and the data transfer t'pe! 3he RFC connections are then checked in parallel tasks running in the reconciliation s'stem! 3he program first checks the availa-ilit' and the release of the sender s'stem using function module RFC?S<S31"?ICF/! Ce5t the program 6ill call function module FB?ICRC?RC/"(?RFC?D1S3?CE1CJ 8FB?ICRCS?RC/"(?RFC?D1S3?CE1CJ for releases A 1R(2 %9! 3his function module checks 6hether an' compan' codes are assigned to the specified companies7 passes -ack the logical s'stem for each compan'7 and updates the DDIC structures for data selection 8FBICRC?S?S121C3? $7 FBICRC?S?S121C3? 27 or FBICRC?S?S121C3? * depending on the process9! If there are issues 6ith the RFC connection7 no compan' code has -een assigned or the DDIC structure cannot -e updated the program 6ill add corresponding messages to the log and e5clude the respective companies from processing! If the program is running in update mode the program sets the status of the remaining companies to 5 Reconciliation Running!

Seite

*2

Intercompan' Reconciliation

For processes $ and * the program derives the ke' date for open items using the 'ear and period entered on the selection screen in com-ination 6ith the fiscal 'ear variant from the reconciliation process detail attri-utes 8transaction FBIC $ 9! Example Reconciliation (rocess Detail ,ttri-utes Fiscal <ear &ariant Fiscal <ear entered on selection screen (osting (eriod entered on selection screen Je' date for selection of open items Table 2): :ey *ate for 8pen Item %election 3he selection restrictions and fields to -e selected are added to internal ta-les 6hich 6ill later -e used for data selection! 3he program 6ill create packages of companies 6hich can -e selected 6ith one RFC using the logical s'stem determined 6ith function module FB?ICRC?RC/"(?RFC?D1S3?CE1CJ7 the selection strateg' of the individual companies7 the transfer t'pe and the data source! Co6 the actual data selection is e5ecuted in the follo6ing order depending on the transfer t'pe and the data source! 5r. Transfer Type *ata %ource $! 2! *! %! .! )! 0! 2 ,s'nchronous 3riggered From Reconciliation S'stem 2 ,s'nchronous 3riggered From Reconciliation S'stem N /ther $ S'nchronous via HI $ S'nchronous via HI S(,C1 ,s'nchronous via Direct RFC Connection S(,C1 ,s'nchronous via Direct RFC Connection S(,C1 Documents of Current (rocess $ Documents of /ther (rocess 2 File Gpload S(,C1 Documents of Current (rocess $ Documents of /ther (rocess S(,C1 Documents of Current (rocess $ Documents of /ther (rocess J% 2 $ $2 *$ Decem-er 2 $

Table 21: 8rder of *ata %election *ependin on Transfer Type and *ata %ource Note 3he RFC users in the sender s'stems re=uire authorization for authorization o-4ect S?RFC -ield 9alue RFC?3<(1 RFC?C,"1 FGGR SDIF FBICRC?S1R&IC1S 8sender s'stem M 1R(2 ,C3&3 $) 815ecute9 %9 %9 FB?ICRCS?S1R&IC1S 8sender s'stem A 1R(2

Table #0: +uthori(ations for R-C users >hen all of this has -een completed the program calls B,dI method SG((2<?/3E1R?D,3,! If an' data is supplied via B,dI the transferred data records are checked using function module FB?ICRC?B,DI?D,3,?CE1CJ! For processes $ and * all currentl' relevant open items have to -e transferred each time the data selection program is e5ecuted! 3he logic for standard data selection is implemented in function modules FB?ICRC?BS?S?S12?RFC for process $ and FB?ICRC?BS?DJ?S12?RFC for process *! If an' of 'our companies provide their data records via upload files the' need to ensure that the upload files also contain all relevant open items! For process 2 onl' ne6l' posted items have to -e transferred! 3he logic for standard data selection is implemented in function module FB?ICRC?21DG1R?S12?RFC! 3he function module reads data records 6ith R3<(1 S(,C1 from the sender ledger on ta-le FBICRC 2, 8FICRCS 2, for releases M 1R(2 %9

Seite

**

Intercompan' Reconciliation

specified in the Reconciliation Process "etail Attri*utes! If the program is running in update mode the function module 6ill set field R3<(1 to % for all data records 6hich 6ere transferred! If ne6 documents are posted in the sender s'stem the' 6ill -e transferred to the ledger 6ith R3<(1 S(,C1! 3hese ne6 data records 6ill -e included in the ne5t data selection program run! If there are pro-lems 6ith the selected data in the reconciliation s'stem 'ou can delete them using the appropriate au5iliar' program! 3he data records can then -e retransferred using the respective option on the selection screen of FBICS2! ,s a ne5t step the data records are completed! For process 2 this mainl' means that the B,dI method ,DD?ICF/R",3I/C?3/?D,3,?R1C/RD is called! For processes $ and * the programs compares the currentl' transferred data records to the previousl' transferred data records! If a data record 6as transferred again it is updated 6ith the information from the ne6 data selection run 8e!g! changed reference num-er9! If a data record is transferred for the first time it 6ill -e added to the reconciliation data-ase! If a data record 6as transferred in a previous data selection -ut is not transferred in the current program run -ecause it 6as cleared or cancelled in the meantime it is deleted from the reconciliation data-ase! (reviousl' transferred data records are identified -' the com-ination of the follo6ing parameters: Compan' Se=uential Cum-er Fiscal <ear (eriod &ersion

3his means that if one of the compan'Ds data sources 8identified -' the com-ination of compan' and se=uential num-er9 should fail or -e e5cluded during one program run the data of this data source is not deleted -ut remains untouched! , sideIeffect of this logic is that once data has -een loaded into a period for a specific data source the onl' 6a' to delete all of that data is to use the respective au5iliar' program! 3his also means that if 'ou should QrenameD 'our companies R i!e! cop' the entries and give the ne6 entries a different se=uential num-ers and then delete the original entries R e5isting data records 6ill not -e QmigratedD! <ou have to delete the data and then run data selection to have the data records availa-le! During this program phase the num-er of transferred data records is created so it can -e used in the protocol! In case the program is running in update mode the changes to the data are posted to the data-ase! Right -efore the changes are saved7 B,dI method CE,CG1?D,3,?3,B21 is called! ,fter6ards the protocol information is split up into individual logs for each compan' and stored for later reference! 3hen the companiesD status is updated and the totals are recalculated to reflect the changes to the documents! ,s a last step the protocol is displa'ed!

Seite

*%

Intercompan' Reconciliation

$.2 *ata +ssi nment


3his part of the document descri-es the program logic of the data assignment programs! >hile there are * different data selection programs the main logic is implemented in class C2?FBICRC?S1R&IC1S and in function module FBRC?RGC?,G3/1H1C?RG21S! ,s a first step the program selects the specified companies from ta-le FBICRC $ $ and checks 6hether the user is authorized to run data selection for the specified companies 8authorization o-4ect F?R(R/C9! If the user specified an' companies 6ithout having the proper authorization the program 6ill displa' 6arning messages regarding these companies and the' are e5cluded from processing! It is not necessar' to change the selection criteria7 though! If the program is not running in test mode the program 6ill no6 check 6hether an' of the companies is locked for data selection! If an' of the companies are alread' locked the program 6ill create corresponding messages for the log and e5clude the companies from processing! Co6 the documents for the specified -usiness relationships are selected and split up into packages per compan' and partner! In case of an update run each data record is locked! 1ach of the packages is then anal'zed -' function module FBRC?RGC?,G3/1H1C?RG21S in a separate task according to the information specified in parameters Ser+er Group and 'a?6 Calls per RFC "estination on the selection screen! ,fter processing of each rule7 B,dI method (R/C1SS?,F31R?,SSIGC?SICG21 is called! ,fter all rules have -een processed B,dI method (R/C1SS?,F31R?,SSIGC?,22 is called! In case of an update run the changes in assignment are saved and the locks on the individual records are released! Right -efore the changes are saved7 B,dI method CE,CG1?D,3,?3,B21 is called! ,lso7 individual logs per compan' are created and stored! ,s a last step the protocol for the program run is displa'ed!

5 Chan e ,istory
*ate $0 Sanuar' 2 $+ Sune 2 0 0 9ersion $! $!$ Chan es Release of original version $! Ce6 e5ample data in 3a-le $.: 15ample Set Definition T2 for customer and vendor accounts 2! ,dditional information regarding special ledgers in 56:6767 "e,ine Ledger Table #1: Chan e ,istory

Seite

*.