Activation of a new SEM BCS instance

When a brand new BCS implementation is started, there are a lot of

kinks. These steps below from the OSS Note # 753688 are very detailed in what needs to be done in that

case.

The procedure with the activation differentiates between an SEM new installation and an upgrade in

item 2b (Copying of the example from client 000).
1. The SEM installation is a new installation
The

delivery client 000 is copied into a new customer client xxx by client copy. With that the content is available in client

xxx, however, not active yet. The client is still empty concerning SEM Customizing.
a) Check the prerequisites for the

activation of the content in an existing client according to item 4.
b) Create an RFC connection (Transaction SM59) of

type 3 with the name 'SEM-BCS_BW' (Details see item 5).
c) Start report UC_CONTENT_ACTIVATE in the respective client in

which you want to activate the content. As an activation BOM enter:
o for Release 3.2: SEM-BCS-320-1
o for

Release 3.5: SEM-BCS-350-1
Start the report (Background execution is recommended).

With that the content is activated in the current client.
Technical note: You can

display the log of the activation with Transaction 'Analyze application log' (SLG1) with object FINB_TR and subobject

TRANSPORT.
1. An upgrade was imported
The SAP content for SEM-BCS exists in client 000 and has to be

copied into an existing or a new client.
a) Check the prerequisites for the activation of the content in an existing

client according to item 4.
b) Copying the example
If the prerequisites are met and if you want

to use an existing client for the purpose of the activation, you have to copy the example into the current client. For this

purpose start Transaction SCC1 (Copying according to transport request) in the current client (Not equal to '000'). Enter

'000' as a source client and one of the BOMs (depending on the release) as a transport request:
o Release 3.2: SEM-BCS

-320-1-T
o Release 3.5: SEM-BCS-350-1-T
Consider the difference in the name in contrast to

the activation BOM.
After this step, the content is available in the current client.
a)

Activating the content
Create an RFC connection as described under 1.b.

Activate the example with report UC_CONTENT_ACTIVATE as described under 1.c.
1. Activation of foreign languages for the

content
If you have successfully activated the SAP content, it is possible to activate texts in foreign

languages (Not equal to German). The texts are available in the system with the installation of the respective language and

only have to be activated in the SEM-BCS.
The content has the German language.
a) For this purpose

start program UGMDTR10 (consider related notes).
b) Select the variant appropriate for the release
o Release 3.2:

SAP&_BCS_320 (Content SEM-BCS 3.2)
o Release 3.5: SAP&_BCS_350 (Content SEM-BCS 3.5)
and select

the language that you want to add to the content.
Example: You use German and English in the

system. The content already exists in German, in addition, you want to activate English:
Start

report UGMDTR10 with the corresponding SAP variant and language 'EN'.
1. Prerequisites for the activation of the

content and more procedure
The content contains data basis 01 with the consolidation areas 10, 30 and 35.

The consolidation area-dependent settings are configured as examples for consolidation area 10.

One own consolidation chart of accounts is assigned per consolidation area:
o Consolidation area 10 -

consolidation chart of accounts 20 (US-GAAP)
o Consolidation area 30 - consolidation chart of accounts 30 (GCC, ARE

in the financial statements)
o Consolidation area 35 - consolidation chart of accounts 35 (GCC, ARE in profit and

loss statement)
The consolidation areas 30 and 35 only contain an upload method for items, a consolidation

chart of accounts according to GCC (30: GCC with appropriation of retained earnings in the profit and loss statement) and the

required account assignment types.
The fiscal year variant K4 (Calendar year, 4 special periods) is

delivered with the content.
a) Make sure that the BW content was activated. In particular, ensure the InfoObjects

0BCS_PRGRP and 0CS_COIAC.
b) Create the RFC connection with the fixed name SEM-BCS_BW with Transcation SM59 (Details see

item 5).
c) Activate the content only if you have not defined any consolidation areas with the keys "10", "30" and "35"

yet in your system!
d) The following BW InfoObjects receive specifications by the content and might therefore overwrite

your settings. Therefore check before the import whether you have used these InfoObjects before and avoid overlappings!
o

Version 0CS_VERSION (100)
o 0CS_CHART - Consolidation chart of accounts (20, 30, 35)
o 0CO_AREA - Controlling area

(9999)
o 0CS_ITEM - Item
o 0MOVE_TYPE - Flow type (100-999)
o 0FUNC_AREA - Functional area (1000-4000)
o

0COUNTRY - Country
o 0BCS_DOCTY - Document type (05-61)
e) Make a change in data basis 01 and save it (Then undo it

again) in order to start the generation. Check whether you want to assign other data streams, for example, for

documents.
f) Make a change analogously in the consolidation areas 10, 30 and 35.
g) With the content no consolidation

units (Companies or profit centers) are delivered. In order to test other functions (For example, the monitor), it is

necessary to create at least a company and a profit center and to include them in a hierarchy.
h) Check the content and

adjust it if necessary.
1. Details for the creation of the RFC connection SEM-BCS_BW
Data basis 01 of the

content example contains the RFC destination SEM-BCS_BW which refers to the BW client of the used BW system.

In order to start the maintenance of the data basis it is necessary to set up this destination even if the activation

occurs in the BW client. In this case, you can delete the destination in the data basis maintenance after the successful

start.
If you activate the content example in a non-BW-client (other client on the local BW System or

remote system), the RFC destination has to be set up and operative to be able to access the BW objects referenced by the

content. Note: In this case, you can also use a Trusted/Trusting connection (see related notes).