cancel
Showing results for 
Search instead for 
Did you mean: 

SEM BCS

Former Member
0 Kudos

Hi all,

In order to implement BCS I am using ECC FI as the operational system. ECC folks are in the process of building Group chart of accountin FI for BCS.

Next I need to bring this Group chart of account in BCS. Can you suggests the work around for this?

Thanks

RJ

Accepted Solutions (1)

Accepted Solutions (1)

former_member197269
Active Contributor
0 Kudos

There are several option with this. The most common is that the FI Group Accounts are, in BCS defined as FS Items on a 1-to-1 basis. Depending on the data model it may require mapping of FI Group Account to FS Item in BW update/transfer rules or in BCS data load method.

Another option in BCS is to have totals FS Items. These are like hierarchy nodes and usually cannot be posted to for the Actual (100) version. These are similar to group accounts in FI and therefore, it depends on what you want in BCS - FI account-level detail with sub-totals at the group account level, or less detailed higher level goup accounts as FS Items. They store subtotals of the individual FS Items assigned to them. Alternatively FS Item hierarchy nodes can be only text nodes.

Hope this helps.

Please assign points as a way to say thanks

Former Member
0 Kudos

Ravi,

Thanks for sharing the thoughts.

I need a chart of account to go ahead with consolidation area in BCS. Right now I have consolidation chart of account in the BCS cube. That is coming from ECCS. Should I remove Consolidation chart of account from the BCS cube and put FI chart of account?

Thanks again

RJ

Former Member
0 Kudos

You don't need to - can't you map one to the other in yout rules?

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

The transfer of ECC group account to BCS FSI is a specific activity. It does not follow the normal BW transfer of data. BCS read the mapping via BW attribute. So be more carefull with this area (as well as the transfer of company ID and company code mapping).

I give you the copy of the procedure of extracting master data mapping.

Procedure: Extracting Master Data Mapping

Here we discuss the mapping between the master data (not the master data itself, which you need to

maintain in SEM-BCS).

There are two kinds of master data relevant to setting up the integrated data mode for ECC and SEM-BCS:

• General Ledger (GL) Account

• Company Entity

Both kinds of master data have their local and group fields.

For example, in ECC a company code posts transactional data to its operation GL accounts. This information

needs to be translated into the FS items of its company entity later on when the subsidiary submits the

operational data into the consolidation system.

Therefore, both the mapping between the operational GL account and FS items and the mapping between the

company code and the company need to be established and visible in SEM-BCS. You can store the mapping

information in various places, such as in ECC, flat files, BW, or in SEM-BCS. Regardless of where the

mapping is stored initially, it should always be recognized in SEM-BCS in one way or the other.

If your subsidiary uses ECC (old R/3) as the operational financial system, we suggest that you store the initial

mapping in ECC. We suggest that you use table SKA1 for the GL accounts and table T001 for the company

entities.

If your subsidiary does not use ECC, you can store the initial mapping in a flat file.

GL Account Mapping:

Extract Mapping to the Business Warehouse – Standard Approach

You are going to load GL account mapping stored in ECC table SKA1 into the master data of InfoObject for

the GL Account. Note that BW master data for GL account varies across different components. For example

0ACCOUNT denotes the operational GL account in the function of Profit Center Accounting while

0GL_ACCOUNT denotes the operational GL account in the function of General Ledger Accounting. Here we

use 0ACCOUNT for illustration purpose. 0ACCOUNT should have a navigational attribute “0CS_Item,” which

is analogous to the group GL accounts.

The use of navigational attribute has two advantages:

• To facilitate BCS to retrieve the mapping at a later stage

• To allow you to jump back from the consolidation reports to the operational reports

Here are the steps:

1. Go to transaction code RSD1 (InfoObject maintenance screen), create 0CS_ITEM as a navigational

attribute of info object 0ACCOUNT. Activate info object 0ACCOUNT.

2. Go to BW administration workbench, create InfoSource and assign DataSource for master data

extraction for 0ACCOUNT. Make sure to include 0FS_ITEM in your extractor.

3. Extract master data from ECC into InfoObject 0ACCOUNT.

After performing the above steps you successfully replicate the GL account mapping in the BW master data

table. This table will be read into SEM-BCS at a later stage during the task run of “Read from Data Stream”.

Extract Mapping to the Business Warehouse – Alternative used for Solution Validation

Since the mapping between the operational chart of accounts “INT” and the group chart of accounts “20” is not

yet available in the current release of the ECC component, for the ease of testing during the Solution

Validation we are going to store the mapping initially in a flat file instead of in the standard ECC table SKA1.

In this flat file we map each GL account in chart of accounts “INT” into the FS items in chart of account “20”.

Here are the steps:

1. Store flat files GLACCOUNT_KEY_QE2_SS and GLACCOUNT_TEXT_QE2_SS in your local PC:

The first file has the mapping between the GL account keys and the FS item keys.

The second file stores the texts for the GL accounts.

2. Go to transaction code RSD1 (InfoObject maintenance screen), create 0CS_ITEM as a navigational

attribute of info object 0ACCOUNT. Activate info object 0ACCOUNT.

3. Go to BW administration workbench, create InfoSource and assign DataSource for master data

extraction for 0ACCOUNT. Make sure to include 0FS_ITEM in your extractor.

4. Extract both flat files from the first step into InfoObject 0ACCOUNT.

After performing the above steps you successfully replicate the GL account mapping in the BW master data

table. This table will be read into SEM-BCS at a later stage during the task run of “Read from Data Stream”.

Customize “Load from Data Stream” in Consolidation Workbench.

The purpose of this setting is to allow the system to access the mapping relationship in BW during the task run

of “Read from Data Stream” and transform the PCA data into BCS format.

How you customize the BCS depends on how you performed “Extract Mapping to the Business Warehouse.”

According to our approach in this scenario – use of navigational attribute to store the corresponding group

account – you will then use the rule of “Moving” the navigational attribute in BCS customizing.

regards,

Halim