SAP BPC NW 10.0 Intercompany Matching Guide

________________________________________________________________________

SAP BPC NW 10.0 Knowledgebase

Intercompany Matching & Booking Implementation Guide

A SAP EPM Community Service

Author: Chief Architect:
Sulthan Mohammad Jothi Periasamy
SAP EPM/BPC Project Lead/Manager/Architect SAP HANA/EPM/BI/EIM Community Thought Leader
01/01/2012
SAP EPM Community Member SAP BPC/BOBJ/BW/MDM Community Domain Champion
sulthan1@gmail.com Joesaran@gmail.com , (916)-296-0228 - Cell

CloneSkills, Inc., http://www.CloneSkills.com , Info@CloneSkills.com , 1.800.836.8959, Page - 1

________________________________________________________________________

Table of Contents

i. Business Scenario ..................................................................................... 3
ii. Overview .................................................................................................... 3
iii. Business Example...................................................................................... 4
iv. Solution Building Blocks: ............................................................................ 8
v. Create and Populate Dimensions & Model:.............................................. 11
vi. Set up Logic Scripts ................................................................................. 18
vii. Set up Business Rules ............................................................................. 21
viii. Set ups in the Excel Interface of the EPM add-in. .................................... 26
ix. Appendix: ................................................................................................. 40
x. Status on the log files of FXTRANS package. .......................................... 40
xi. Status on the log files of ICDATA package. ............................................. 40
xii. Status on the log files of ICBOOKING package. ...................................... 40
xiii. Dimension Structures ............................................................................... 41
xiv. Structure of Rate Model (IC_Rates) ......................................................... 43
xv. Disclaimer: ............................................................................................... 44

01/01/2012


________________________________________________________________________

Business Scenario:
During moth end/period close, there are situations where each
company is struggled with differences in the intercompany Accounts
Receivable / Accounts Payable reconciliations. The main problem for
this imbalance between subsidiary GL posting is that the data
accessibility and integration across organization and its source
systems.

The option of using one model with data access controlled via
member access profiles for the data source dimension may take
security too complex. For this reason, a separate intercompany
matching model is considered.

Overview:
This document illustrates the necessary steps required to set up a
simple Intercompany Matching application. A typical Intercompany
Matching process will have the following functionalities.

• The data is collected either by an Input Schedule or by using
the Data Import option in the Data Manager package. In this
guide, it is assumed that data is already collected.
• Currency Conversion process is used to translate the local
currency to the matching currency using the standard Currency
conversion package
• ICDATA process is used to copy the data into unique data
source members to facilitate the reconciliation.
• ICBOOKING process is used to generate the balancing entries
• Intercompany matching report is created using EPM add-in
Excel functions to identify the mismatches.

01/01/2012


________________________________________________________________________

Business Example:

01/01/2012


________________________________________________________________________

Intercompany matching:

A France Entity (FR) owes US entity for a business transaction of 100
EUR. The intercompany members of France (Seller) and US (Buyer)
are I_FR & I_US respectively. The transactions are written as given in
the following table.

Entity Intco Account Datasrce Local
Currency

FR I_US AS27480000 – Other Loans INPUT 100

US I_US LI16870000 – Other Debts INPUT 130

Currency Translation

For the above transactions, the local currency is translated into
EURO and the EUR/USD exchange rate of 1.40 is used in this case.

Entity Intco Account Datasrce Value
EUR

FR I_US AS27480000 – Other Loans INPUT 100

US I_US LI16870000 – Other Debts INPUT 92.86

01/01/2012


________________________________________________________________________

ICDATA process

This IC matching process generates the following 4 different new
records based on the Data source structure.

Entity INTCO Account Datasrce Value
EUR

FR I_US AS27480000 – Other Loans Debit1 100

US I_FR AS27480000 – Other Loans Debit2 100

FR I_US LI16870000 – Other Debts Credit1 92.86

US I_FR LI16870000 – Other Debts Credit2 92.86

ICBOOK Process

The difference of 7.14 is corrected by one of the entities using the
ICBOOK process to book the differences according to the specific
rules mentioned in the business rules section.

01/01/2012


________________________________________________________________________

Solution Data Model
Model:

SAP EPM/BPC Project Lead/Manager/Architect
/Architect SAP HANA/EPM/BI/EIM Community Thought Leader
01/01/2012


________________________________________________________________________

Solution Building Blocks:

Models needed:

o ICMatchBooking - Finance/Reporting type model and the
data entry mode is of year-to-date.
o Rates – Standard reference model to store the exchanges
rates.

Dimensions needed:

The model ICMatchBooking uses the following dimensions
(minimum required properties and dimensions are used to keep
it simple)
Dimension Name Dimension Type
IC_ACT A – Account
IC_TRL D – Audit
CATEGORY C – Category
ENTITY E – Entity
FLOW S – Subtables
RPTCURRENCY C – Currency
TIME T – Time
IC_INT I -- Intercompany
SCOPE G -- Group

The model Rates uses the following dimensions (minimum
required properties and dimensions are used to keep it simple)
Dimension Name Dimension Type
R_ACCOUNT A – Account
CATEGORY C – Category
R_ENTITY E – Entity

01/01/2012


________________________________________________________________________

INPUTCURRENCY C – Currency
TIME T – Time

Data Manager Packages:

The following standard DM packages are used with no
customization.

1. FX Restatement – for currency translation
2. ICDATA – for copying data into unique data source
members
3. ICBOOKING – to generate the balancing entries.

Business Rules

1. Currency Translation Business Rule
2. Intercompany Bookings Business Rule

Note: No business rule is required for ICDATA.

Logic Scripts:

1. An FXTRANS.LGF logic file for currency translation will
translate into a reporting currency that is selected at run
time.
2. An ICDATA logic file for intercompany reconciliation
3. An ICBOOKING logic file for booking the matching
differences.

01/01/2012


________________________________________________________________________

Implementation Steps:

01/01/2012


________________________________________________________________________

Create and Populate Dimensions & Model:

Step 1 Log into Web Admin Client using Primary Admin account
(or any account with necessary task profile access that can create
Model/Dimension and other building blocks)

01/01/2012


________________________________________________________________________

Step 2 Click on “Planning and Consolidation Administration”
option at the lower right corner.

01/01/2012


________________________________________________________________________

Step 3 Create all the dimensions under Dimensions tab.

01/01/2012


________________________________________________________________________

Step 4 Add a property called IC_ORGINE of size 2 to the
datasrce dimension. The ICDATA program copies from the INPUT
Data source into the Credit and Debit members based on the
Intercompany_ORIGINE property.

Add the following members to the dimension IC_TRL.

01/01/2012


________________________________________________________________________

Step 5 The intercompany dimension of type I, is important
for the intercompany matching. This DIM must have another property
called ENTITY whose values are Entity names.

01/01/2012


________________________________________________________________________

Step 6 The accounts used for Intercompany matching must
have the RATETYPE of CLO as follows.

01/01/2012


________________________________________________________________________

Step 7 Create the Financial ICMatchBooking model with
the following structure.

Note: Rate Model – IC_Rates is referenced in this model.

01/01/2012


________________________________________________________________________

Set up Logic Scripts

1. Click Administration tab/Rules/Logic Scripts and choose the
model (ICMatchBooking) as follows.

01/01/2012


________________________________________________________________________

2. Create the following 3 scripts and the contents of the scripts are
given below.

01/01/2012


________________________________________________________________________

01/01/2012


________________________________________________________________________

Set up Business Rules

1. Click Administration tab/Rules/Business Rules and choose the
model (ICMatchBooking) as follows.

01/01/2012


________________________________________________________________________

2. Add the following 2 rule types by clicking “Add/Remove rule
Types”

01/01/2012


________________________________________________________________________

3. Click on the currency Translation and add the following 2 rules
for the translation. The contents for the AVG & CLO are also
given below.

01/01/2012


________________________________________________________________________

01/01/2012


________________________________________________________________________

4. Now click on “Intercompany bookings” rule types. Then create
the following rule for the parent ID CTLICEND00. The content
of the business rule is as follows. Here the type must be S-
Seller rule which will post intercompany differences to the
buyer.

01/01/2012


________________________________________________________________________

Set ups in the Excel Interface of the EPM add-in.

1. Go to the Start page of the Planning and Consolidation main
page and click the EPM Office Add-in Excel at the right side
under the Launch tab.

01/01/2012


________________________________________________________________________

2. It opens up the EPM connection manager and prompts to
choose the connection as follows.

3. Double click the model that you have created for the
ICMatching (Click on ICMatchBooking).

01/01/2012


________________________________________________________________________

4. In the following screen, click Data Manager tab. Then click
“Organize”,”Organize package list” to go the package
maintenance Screen.

01/01/2012


________________________________________________________________________

5. Click “Package” at the top left corner, then click “Add a
package”.

Then press “select”, to select the process chain in the above
screen. Task type can be either user package and/or admin
package.

01/01/2012


________________________________________________________________________

6. Select the process chain /cpmb/ICDATA under the script
logic, then press okay.

01/01/2012


________________________________________________________________________

7. Now name the package as follows and then press Add to add
the package.

8. Follow the steps 5 through 7 to add other packages for
FXTRANS & ICBOOKING

01/01/2012


________________________________________________________________________

9. Click EPM tab. Then click new report to the following screen.

01/01/2012


________________________________________________________________________

10. The following input form is used to load the data into
RATE model (IC_rates).

01/01/2012


________________________________________________________________________

11. Using the report editor, create the following input
schedule form to load the data for the ICMatchBooking
model.

Note: the data in the shaded area is out of scope, it can be ignored.

01/01/2012


________________________________________________________________________

12. By clicking “Save data”, the data is saved into ICMatchBooking
model.

Press OK to clear the popup window.


01/01/2012


________________________________________________________________________

13. Now run the currency translation package “FX Restatement” by
choosing Data Manager tab/ Run package option. After the
successful execution of the pacakge, the screen looks as
follows.


01/01/2012


________________________________________________________________________

14. Now click the “New Report” under EPM tab and create the
following report using the report editor. The ICMatching report
looks as follows.


01/01/2012


________________________________________________________________________

15. Now to copy the data into the unique source members
(Credit1/Debit1/Credit2/Debit2) to make the reconciliation
easier, run the ICDATA package. After the successful run,
the screen looks as follows.


01/01/2012


________________________________________________________________________

16. Now run the ICBooking package to generate the
balancing entries. After the successful execution of the
package, the output should like as follows.

As we defined the Seller rules in the logic script, the above
report explains that the seller (FR) is correct and therefore
the difference goes to the buyer (US). The ICBOOKING
package posts offsetting entries to make intercompany
Accounts payable equal Accounts Receivable

01/01/2012


________________________________________________________________________

Appendix:

Status on the log files of FXTRANS package.
LOG BEGIN TIME:2012-01-17 01:41:47
FILE:ROOTWEBFOLDERSENVIRONMENT073_1ADMINAPPICMatchBookingFXTRANS.LGF
USER:NEWEPM073
APPSET:ENVIRONMENT073_1
APPLICATION:ICMatchBooking
RUN CURRENCY CONVERSION
3 SUBMITTED, 3 SUCCESS, 0 FAIL.

SCRIPT RUNNING TIME IN TOTAL:4.02 s.
LOG END TIME:2012-01-17 01:41:50
File path:
ROOTWEBFOLDERSENVIRONMENT073_1ICMatchBookingPRIVATEPUBLICATIONSNEWEPM073

Status on the log files of ICDATA package.
LOG BEGIN TIME:2012-01-17 01:42:57
FILE:ROOTWEBFOLDERSENVIRONMENT073_1ADMINAPPICMatchBookingICDATA.LGF
USER:NEWEPM073
RUN ICDATA

LOG END TIME:2012-01-17 01:42:59
File path: ROOTWEBFOLDERSENVIRONMENT073_1ICMatchBookingPRIVATEPUBLICATIONSNEW

Status on the log files of ICBOOKING package.
LOG BEGIN TIME:2012-01-17 02:18:59
FILE:ROOTWEBFOLDERSENVIRONMENT073_1ADMINAPPICMatchBookingICBOOKING.LGF
USER:NEWEPM073
RUN ICBOOKING

LOG END TIME:2012-01-17 02:18:59
File path: ROOTWEBFOLDERSENVIRONMENT073_1ICMatchBookingPRIVATEPUBLICATIO

01/01/2012


________________________________________________________________________

Dimension Structures

01/01/2012


________________________________________________________________________

01/01/2012


________________________________________________________________________

Structure of Rate Model (IC_Rates)

01/01/2012


________________________________________________________________________

Disclaimer:
This description is a preliminary version and not subject to a license agreement
or any other agreement with SAP®. This document contains only intended
strategies, developments, and functionalities of the SAP product and is not
intended to be binding upon SAP to any particular course of business, product
strategy, and/or development. Please note that this preview is subject to change
and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP
does not warrant the accuracy or completeness of the information, text, graphics,
links, or other items contained within this material. This preview is provided
without a warranty of any kind, either express or implied, including but not limited
to the implied warranties of merchantability, fitness for a particular purpose, or
non-infringement.

SAP shall have no liability for damages of any kind including without limitation
direct, special, indirect, or consequential damages that may result from the use of
these materials. This limitation shall not apply in cases of intent or gross
negligence. The statutory liability for personal injury and defective products is not
affected.
________________________________________________
SAP Community Contributors:

SAP EPM/BPC Project Lead/Manager /Architect SAP HANA/EPM/BI/EIM Community Thought Leader
SAP EPM Community Member SAP BPC/BOBJ/BI/MDM Community Domain Champion

Contact Us For:

IC Eliminations
Ownership Calculations
Consolidation Leading Practices and Design Advisory
Minority Interest and Equity Calculations, and Much More …

01/01/2012


SAP BPC NW 10.0 Intercompany Matching Guide

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (20)

Similar to SAP BPC NW 10.0 Intercompany Matching Guide

Similar to SAP BPC NW 10.0 Intercompany Matching Guide (20)

More from Jothi Periasamy

More from Jothi Periasamy (20)

Recently uploaded

Recently uploaded (20)

SAP BPC NW 10.0 Intercompany Matching Guide