Total Transfer & Organizational Change (SEM-BCS)

Dear colleagues!
Got som challenge with processing a merger under consolidation of
investments in SEM release 4.0.
As I understand, the proper method to apply to mergers is a) a
divestiture of the old consolidation unit and b) postings of account
balances from old unit toward the new unit in the source system,
with subsequent data load.
Issue:
In our case a subsidary of the old parent (merged)"follows" the
merger
towards another consolidation group (old parent divested, subsidary
unchanged with new cons group assignment).
Client expects the merger to be physically carried out in period 6,
with a validity (back in time) starting with period 1, without
processing period 1-5 in the monitor. Client also expects the income
statement balances to be reversed from old cons group assignment and
posted under new cons group for the accum. balance from period 1-6.
Question:
Would anybody know (could give us) a brief description on what to
remember when setting the parameteres in preparation of the
organization change (total transfer)!?
Help is greatly appreciated.
Frank

Dan,
What C/I activity are we supposed to use if we want transfer a unit vertically up in the hierarchy?
And also, we are still getting an error with Organization Change scenario when we run our COI. Can we please send you a detailed document of the issue we are facing to your email id?
Thanks
Ramesh

Similar Messages

Total Divestiture_Consoli of Investment-SEM-BCS

Hi Experts,
When I carry out total divestiture the Subsidiaries balance is not getting reveresed. Only Goodwill and Minority Interest item is reversed but the subsidiaries data remains in the system.
I am using additional financial data for Investments and Equity. Reported data are uploaded thru flexi upload.
Please suggest !

Hi Halim,
For example I have divested the above company in the period 6 at Begining of the period. So loigically, there will not be any more trial balance from that subsididary. And the consolidation entries have been nullified. However, when i select the range from period 03 to 06 in the Total Records, it shows the balance in the G/L uploaded thru Flexiupload in the period 03. If I select total records for period 06 only, then too there is balance in G/W and MI passed thru Divestiture Activity as the original G/W and MI is in the period 03.
Also, when I am doing divestiture at the end of the period, I will be uploading TB of subsidiaries, hence there would be balance in G/L other than GW and MI in the current period as well.
Please suggest,
Regards,
USR

SEM-BCS: total transfer

Hello,
I need help.
Scenario: Two companies will be merging as one and falls under the same cons group.
Is total transfer (under COI) the correct activity to use?
If yes, please help share what are the different settings, changes, financial data, so I can test in the SEM-BCS.
Thank you in advance

Hi Jouan,
So are you trying to say that total transfer is not for merging one company to another company scenario?
For example company A fully acquired company B. So we intend to merge company B'sfinancial data into company A.
Can we use total transfer for this?
Thank you.
Krezel

Total transfer of equity consolidated unit using organizational change

Hi,
We have a scenario where we are doing total transfer of an equity consolidated unit (100% owned) from one company(old parent) to another (new parent)
The new parent is one level above the old parent in the hierarchy.
We've used organizational change logic and have set the divestiture dates/flag in the sender consolidation group and accordingly first consolidation dates/flag/OC number in the receiver consolidation group.
The investment AFD is submitted with "total transfer" with OC number.
There are multiple scopes of reported data for equity method in our configuration.
Each scope(equity pickup) is inturn created by reclassifying several equity accounts to a single BCS only item(the scope item)
When we run COI, the system posts one total divestiture document at the old conso group (where old parent is situtated) and posts a first consolidation, total divestiture, total transfer documents at the new conso group level (which is one level above the sender conso group)
The total divestiture document at upper level is reversing the divestiture document posted at old parent.
The first consolidation document jas only statistical items posted in it.
The real document to check is the "Totals transfer document" which actually reads the investment (at old parent and new parent) , the equity holdings adjustment data(the scope items) and adjusts the investment in subs at new parent with offset going to divestiture account but of double the value than the expected scope vlaue.
Issues faced:
Q1. Consolidation group change tasks (at PL02, 12, 22) are not posting any documents. Is there an issue? Since I am using these tasks for the first time and dont know if this is possible.
Q2. The total transfer document is reading the equity holdings data as double the expected value( for each of the scopes of equity method). What could be the possible reason? How to fix this?
Q3. I would appreciate if someone can clarify what kind of postings the system makes as part of divestiture/transfer in case of equity consolidated unit transfer.
Please help!
Thanks,
AJ

Thanks Dan.
Appreciate if you can help on the below points as well.
1. As part of divestiture/transfer postings: The system is reversing some Previous Year(PY) equity accounts into themselves. How can we get the system to eliminate them by posting to COI Clearing account. Basically, we dont want the PY accounts to be touched?
For the Retained earnings - PY account, the system is actually posting to COI clearing account.
These PY accounts are part of some scopes for equitization.
Is there any link between the "balance carry forward" - list of items table and the divestiture postings?
Does the system check this table while posting/reversing the equity(PY) accounts?
2. I want to understand the sequence in which the system posts the documents at the old parent and new parent (group) level.
The same activity number is there for Total Divestiture, total transfer documents posted at new parent level and total divestiture document posted at old parent level.
Does the system follow bottom up approach? Thereby creating total divestiture document at old parent level.
Followed by documents at upper level (new parent level)
Also , at the upper level(new parent level), does it post documents in the way they are shown in the log? (We havent changed the default sequence maintained in UCWB - COI settings). so it will post first consolidation doc, followed by total divestiture, followed by total transfer docs at the new parent level?
Is this the reason for the double value being posted at new parent for equity holding data?
Will studying the statistical items (corresponding to eliminated equity holding items) be relevant here to understand why at upper level there is double the value being posted by system?
Thanks.

General Questions about SEM-BCS Data Transfer

Please help me guys ! I need a clearer picture as to how exactly the loading of data should be done to SAP SEM-Busines Consolidation
Q1) Can I specify the Basic Cubes in my Data Basis Streams that I use for FI & CO in BCS-Workbench ? Or do I need to switch these cubes to Transactional, so it can be used in SEM-BCS ?
Q2) or Do I have to export the data out of my FI & CO cubes in BW to a FLAT FILE, and then load the Flat File into custom Transactional Cubes ?
Q3) Usually, for SEM-BCS would there be any direct connection to SAP R/3 or it`s via BW ?
Please help me with these initial issues guys ! Very much appreciated!

Hi Eugene,
 Great man! You`re back!...Nice to hear from yourself
 Anyways, I still am struggling to understand the Intergration from SEM-BCS with BW and/or R/3. If you have any material that can help me understand the intergration would be helpful.
 So, I had a look into the SAP Note 689229
 It says, all changes of master data nad hierarchies have to be made via the application layer by means of application SEM-BCS :-
a) By Flexible Upload
b) Manually in Consolidation Workbench
c) In Subordinate systems from transports
Hence, am I correct to assume that the only 2 options are permitted: Option (a) Flat File (b) Manually define the master data in BCS-Workbench ?
 So, now assuming that I need to define Consolidation Items into SEM-BCS.
Because there's too many, I would go with option (b) Flat File.
So, I create a Flat File containing the Consolidation Items. Next, how do I get this loaded into BCS-Console ?
Do I have to create a Transactional Info Cube and then load this Consolidation Items Flat File into it? Then following from there, I specify this Transactional Info Cube in my Data Stream ? or
Is there a way, I can directly read the Flat File from SEM-BCS ?
I use the following Info Cubes as source to my Data Basis:-
 Data Target | Virtual InfoProvider
TOTAL RECORDS = 0BCS_C50 | 0ECCS_C05
DOCUMENTS = 0BCS_DS12 | 0BCS_VC12
 P/S: We don`t use the SAP R/3 ECCS Module
Message was edited by: John Mcluskey

Transfer Under SEM-BCS

Hi Experts,
I am using additional financial data for Investments and Equity Data.
I want to perform transfer of Consolidation unit from One Group to another Group.
However, when I execute Transfer activities along with Change Organizational function, the Financial Data is transferd to target group but Goodwill data is not posted to Transferee Company.
Please suggest the procedure for Total Transfer with or without affecting Net Income.
Warm Regards,
USR

Hi,
I guess you tick the "extraordinary amortisation of goodwill" in the C/I system utilisation.
If you tick this function, then you have to provide the usefull life for its amortisation.
Hope it helps.
regards,
Halim

Implementation of SEM-BCS

Hi Experts,
i am trying to implement SEM-BCS. I am still new in it. Are there any documentation about step by step to configure SEM-BCS?
Thanks a lot for your help.

Hi,
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=bw-bcs&cat=sdn_all
Basics of BCS modelling -
Key figures -
You are generally not permitted to change any properties of the key figures used in SEM-BCS. The only exceptions to this are options that affect the display in Business Explorer and the "Characteristic is document property" setting.
If you want to use your own InfoObjects as key figures for totals records in the InfoCube, consider the following conditions:
1. SEM-BCS supports four roles for key figures in the data stream for totals records: Value in group currency, value in local currency, in transaction currency and quantity. You can assign a maximum of four key figures in the data basis accordingly. If you include additional key figures in the InfoCube, these cannot be processed in the consolidation. You are not permitted to assign other roles, such as 'subassignment,' to key figures either.
2. In SEM-BCS, the values are always stored periodically in the database. Furthermore, year-to-date values or non-cumulative values are not managed separately but result from cumulation in each case over the periods of the current fiscal year up to the current period. (This is a purely technical restriction. The consolidation functions greatly support the process with year-to-date values.) Therefore, you must define InfoObjects as cumulative values. Proceed according to the 0CS_TRN_GC, 0CS_TRN_LC, 0CS_TRN_TC, 0QUANTITY InfoObjects that are delivered.
3. You cannot use referencing key figures in SEM-BCS. If you want to define a key figure with a reference, to transfer the technical properties of the referenced InfoObject identically, you can simply create this with a template instead. However, if you want to use the special BW function linked with referencing key figures (see the online documentation in the BW), enter the referencing key figures in the InfoCube, but assign the referenced key figures to the data basis.
Characteristics
With the following characteristics, you are not permitted to make changes to the properties. Once again, the only exceptions here are the options that affect the display in Business Explorer:
0AC_DOCLN, 0AC_DOCNR, 0AC_DOCTEXT, 0AC_IVDOCNR, 0AC_IVPER, 0AC_IVYEAR, 0AC_OIDOCNR, 0AC_OIPER, 0AC_OIYEAR, 0AC_ORDOCNR, 0AC_ORPER, 0AC_ORYEAR, 0AC_RVDOCNR, 0AC_RVPER, 0AC_RVYEAR, 0BCS_AREA, 0BCS_AUTODL, 0BCS_BGPER, 0BCS_BGYEAR, 0BCS_COIACT, 0BCS_COIFUT, 0BCS_COIINA, 0BCS_COINRT, 0BCS_COIPGW, 0BCS_COITOA, 0BCS_CTFLG, 0BCS_DPER, 0BCS_DTEQI, 0BCS_GWLC, 0BCS_GWMAN, 0BCS_GWNEG, 0BCS_GWPROC, 0BCS_LCCMU, 0BCS_LCIC, 0BCS_OBJNR1, 0BCS_OBJNR2, 0BCS_OBJNR3, 0BCS_OBJNR4, 0BCS_OBJNR5, 0BCS_OBJNR6, 0BCS_OBJNR7, 0BCS_OBJNR8, 0BCS_ORGCH, 0BCS_ORGCHL, 0BCS_PRGRP, 0BCS_REFPER, 0BCS_REFYR, 0BCS_SEQNM, 0BCS_TASK, 0BCS_TASKGR, 0BCS_TASKTY, 0BCS_TAXSUP, 0CS_COIAC, 0CS_COINR, 0CS_PLEVEL, 0CURRENCY, 0DATE, 0UNIT, 0USERNAME
Compounding -
When you define the compounding of an InfoObject, some compound relationships are not supported:
You cannot compound subassignments to consolidation units.
You are not permitted to compound the document type and the (0CS_PLEVEL) posting level.
You cannot compound noncurrent assets and assets/liabilities to 0BCS_ALTYPE. In addition, you cannot compound to a characteristic from the totals cube, with the exception of consolidation units, partners, and so on, and their higher-level characteristics.
ODS objects / Virtual InfoProvider -
You can generate the ODS objects for additional financial data and the virtual InfoProvider from the data basis maintenance. However, you can also create these manually and enter them in the data basis. If you do this, create the ODS objects and virtual InfoProvider with the same characteristics and structure they would have had if generated by the data basis maintenance. You can only deviate very slightly from this.
You are not permitted to include the following InfoObjects in any InfoProvider, unless they are generated by the data basis automatically:
0BCS_AREA, 0BCS_REFPER, 0BCS_REFYR, 0BCS_TASK, 0BCS_TASKGR, 0BCSTASKTY
The following InfoObjects must not be contained in the InfoObject catalog, which is defined in the data basis:
0BCS_AREA, 0BCS_REFPER, 0BCS_REFYR, 0BCS_TASK, 0BCS_TASKGR, 0BCSTASKTY, 0FISCYEAR, 0FISCPER3
Time characteristics -
SAP consolidation SEM-BCS ignores changes with the 0FISCPER, 0FISCPER3, 0FISCVARNT and 0FISCYEAR time characteristics. If you make changes, for instance, if you create hierarchies or attributes, these are not taken into account by SEM-BCS. Therefore, there is no maintenance in the workbench, you cannot use the hierarchies or attributes in the functions of SEM-BCS for selections and so on, and you cannot use the attributes or hierarchies for selections in BW queries.
Characteristic values
The following InfoObjects may have the values set by default by SAP only . You are not permitted to change them, not even by using the BW master data maintenance:
0BCS_AREA, 0BCS_AUTODL, 0BCS_COISRT, 0BCS_CTFLG, 0BCS_DIDIEL, 0BCS_GWMEM, 0BCS_GWPROC, 0BCS_IPAAC, 0BCS_IPATTY, 0BCS_OBJNR1, 0BCS_OBJNR2, 0BCS_OBJNR3, 0BCS_OBJNR4, 0BCS_OBJNR5, 0BCS_OBJNR6, 0BCS_OBJNR7, 0BCS_OBJNR8, 0BCS_REPMOD, 0BCS_TASK, 0BCS_TASKGR, 0BCS_TASKTY, 0BCS_TAXSUP, 0BCS_TIMMOD, 0CS_COIAC, 0CS_PLEVEL
For these InfoObjects you can only use the tools of the master data service of the Financial Basis to synchronize master data, so the master data is transferred by the SEM-BCS tables to the BI tables, but not the other way round.
Predefined InfoObjects for individual roles
The system automatically uses most of the InfoObjects mentioned here to activate certain data streams. However, there also are some InfoObjects that you must manually enter in the cube for the totals records. Subsequently, you must assign certain roles to these InfoObjects. These roles are allowed for these InfoObjects only, you cannot assign these roles to other InfoObjects.
These are:
0CS_PLEVEL for the posting level role (required)
0BCS_CTFLG for the conversion role (optional)
0BCS_PRGRP for the product group role (optional)
Activate characteristics and key figures from BW Content
Before you create a data basis of SAP consolidation, you have to activate certain InfoObjects from BW Content.
1. You must always activate the following: 0CS_PLEVEL, 0FISCPER, 0FISCPER3, 0FISCVARNT, 0FISCYEAR.
2. If you use documents, you must also activate: 0AC_DOCLN, 0AC_DOCNR, 0AC_DOCTEXT, 0AC_IVDOCNR, 0AC_IVPER, 0AC_IVYEAR, 0AC_OIDOCNR, 0AC_OIPER, 0AC_OIYEAR, 0AC_ORDOCNR, 0AC_ORPER, 0AC_ORYEAR, 0AC_RVDOCNR, 0AC_RVPER, 0AC_RVYEAR
3. If you use the virtual InfoProvider, activate: 0BCS_REFPER, 0BCS_REFYR, 0BCS_REPMOD, 0BCS_TIMMOD also
4. If you use any data stream in addition to the totals records, also activate: 0BCS_OBJNR1, 0BCS_OBJNR2, 0BCS_OBJNR3, 0BCS_OBJNR4, 0BCS_OBJNR5, 0BCS_OBJNR6, 0BCS_OBJNR7, 0BCS_OBJNR8
5. If you use the data streams of the consolidation of investments, activate: 0ACQ_PER, 0ACQ_YEAR, 00BCS_BGPER, 0BCS_BGYEAR, 0BCS_COIACT, 0BCS_COIFUT, 0BCS_COIINA, 0BCS_COINRT, 0BCS_COIPGW, 0BCS_COISRT, 0BCS_COITOA, 0BCS_DPER, 0BCS_DTEQI, 0BCS_GWLC, 0BCS_GWMAN, 0BCS_GWMEM, 0BCS_GWNEG, 0BCS_GWOFFS, 0BCS_GWPROC, 0BCS_GWRED, 0BCS_LCCMU, 0BCS_LCIC, 0BCS_SEQNUM, 0CS_COIAC, 0CS_COINR
6. If you use organization changes, activate: 0BCS_ORGCH, 0BCS_ORGCHL
7. If you use data streams for stock and delivery data, activate 0BCS_PRGRP.
8. If you use data streams for assets/liabilities or noncurrent assets, activate: 0BCS_ALTYPE, 0BCS_DPER, 0BCS_DYEAR, 0BCS_IPADAU, 0BCS_IPALCM, 0BCS_IPATTY, 0BCS_RETBG
The list of the InfoObjects varies depending on the release. Of course, you do not have to activate InfoObjects that do not exist in your release.
You do not have to activate InfoObjects that are not explicitly specified. However, if you do not activate them, some functions may not be available to you. For example, if you do not activate the 0BCS_CTFLG InfoObject and do not use it for totals records in the InfoCube, the currency translation cannot display any currency translation differences on the initializing data records.
Attributes When you define the InfoObjects in BW, attributes can be assigned to InfoObjects. This results in the following restrictions:
In SEM-BCS 3.1B, 3.2 and 3.5, no InfoObjects that appear in the permanent parameters of a consolidation area or are fixed in a consolidation area may be attributes of an InfoObject used in SEM-BCS.
InfoObjects that are used as a consolidation unit must not have 0FISCVARNT as an attribute.
Note 727776 - Requirements of SEM-BCS for data model
Hope it Helps
Chetan
@CP..
Eugene Khusainov
Re: BCS - Modelling requirements
Posted: Feb 24, 2007 10:56 PM in response to: moini kembly Reply E-mail this post
Hi,
On this phase you should determine and describe the following:
- sources of data to be consolidated (R/3, flat files, 3rd parties)
- methods of receiving/uploading these data into BW
- the appropriate BW objects (characteristics, key figures, cubes etc.)
- time characteristics to be used (is it enough to have only fiscal chars? do you need the calendar ones too?)
- is data upload to be directly into totals cube? if not - consider the intermediate cube. What kind of data transformation is to be done during upload of data from interim cube to the totals?
- methods of getting data into totals cube (flexible upload, reading from datastream, manual entries)
- will you need additional financial data? if yes, which ones and how will you load this data?
- what types of data you need to consolidate (actual, plan, forecast etc.)
- how many chars will be given the VERSION role?
- plan the number of consolidation areas. The best way is to have the only one. it will minimize the customization.
- how many consolidation units hierarchies do you have (for example, if you need consolidated reports according to management and IFRS structure of the group, then you have 2 hierarchies)?
- determine the structure of the group hierarchies.
- what is the group's currency? is it one currency or several ones?
- determine the currency translation methods for each data type.
- make sure that all consolidation units have the same chart of accounts. if not, consider the mapping or transformation of the numbering of accounts.
- consider the currency translation types for different groups of accounts in the balanse sheet (for example, fixed assets and equity - historical rate, retairned earnings - everage rate, non-monetary items - current rate etc.).
- consider the kind of translation - periodic/cumulative for different data types and reports.
- determine the set of consolidated reports as an output.
- which custom characteristics you need to bring to the totals cube in order to get the reports needed?
- which standard chars you'll have to customize and how exactly (bringing new attributes, customizing the std or creating the custom chars)
- if you'll replace a standard char with a custom one, consider that some another chars may depend on the char to be replaced. it's especially true for a company code. if you use a custom char for a company, then you have to use the reference chars for partner company, investee company, allocation company etc.
- will your consolidation units be one-dimension structure (by company) or it is a matrix one? if the latter, what is the second cons unit?
- will the BCS functionality cover all your consolidation needs? if not, consider the workarounds. reclassification is to be considered as a tool # 1.
It's just an incomplete introduction to the issues to be determined during a blue-print phase.
Re: BCS in NW2004s
Re: BCS - Data modelling KF question
Re: BCS - Virtual Cube Query error
Re: BCS- data basis
Re: BCS - Virtual Cube problem
Re: BCS - Consolidation group data
check these links...
http://help.sap.com/saphelp_sem40bw/helpdata/en/67/f7e73ac6e7ec28e10000000a114084/frameset.htm
Re: Synchronize Master Data between BCS and BW within the same SEM system
/message/1508507#1508507 [original link is broken]
http://sap.ittoolbox.com/groups/technical-functional/sap-sem/dataflow-from-r3-to-sem-bcs-950671
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/6e01a04e-0a01-0010-dfbe-951c2c39d169 [original link is broken]
http://help.sap.com/saphelp_nw2004s/helpdata/en/c4/9057475ca611d4b2e30050dadfb23f/frameset.htm
Hareesh

SEM-BCS: Merger

Hello Experts,
I have this scenario below:
Two companies will be merging as one company. Both of these companies falls under the same consolidation group.
We plan to use vertical or horizontal merger. However, its not found in the set of COI activity in SEM-BCS.
Is it available in SEM-BCS?
If so, please help provide helpful documentation.
Thank you so much in advance for the big help.
Regards,
Krezel

hi Krezelmina Adjad,
See the following links first:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/cfa4ba90-0201-0010-6480-ea9498dcfceb
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/98c4d590-0201-0010-e480-eca9942ffede
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/51ae9d90-0201-0010-92b9-82ef8e5458e7
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3ed09790-0201-0010-c28e-c639f87d40b9
BASICS OF BCS:
Basics of BCS modelling -
Key figures -
You are generally not permitted to change any properties of the key figures used in SEM-BCS. The only exceptions to this are options that affect the display in Business Explorer and the "Characteristic is document property" setting.
If you want to use your own InfoObjects as key figures for totals records in the InfoCube, consider the following conditions:
1. SEM-BCS supports four roles for key figures in the data stream for totals records: Value in group currency, value in local currency, in transaction currency and quantity. You can assign a maximum of four key figures in the data basis accordingly. If you include additional key figures in the InfoCube, these cannot be processed in the consolidation. You are not permitted to assign other roles, such as 'subassignment,' to key figures either.
2. In SEM-BCS, the values are always stored periodically in the database. Furthermore, year-to-date values or non-cumulative values are not managed separately but result from cumulation in each case over the periods of the current fiscal year up to the current period. (This is a purely technical restriction. The consolidation functions greatly support the process with year-to-date values.) Therefore, you must define InfoObjects as cumulative values. Proceed according to the 0CS_TRN_GC, 0CS_TRN_LC, 0CS_TRN_TC, 0QUANTITY InfoObjects that are delivered.
3. You cannot use referencing key figures in SEM-BCS. If you want to define a key figure with a reference, to transfer the technical properties of the referenced InfoObject identically, you can simply create this with a template instead. However, if you want to use the special BW function linked with referencing key figures (see the online documentation in the BW), enter the referencing key figures in the InfoCube, but assign the referenced key figures to the data basis.
Characteristics
With the following characteristics, you are not permitted to make changes to the properties. Once again, the only exceptions here are the options that affect the display in Business Explorer:
0AC_DOCLN, 0AC_DOCNR, 0AC_DOCTEXT, 0AC_IVDOCNR, 0AC_IVPER, 0AC_IVYEAR, 0AC_OIDOCNR, 0AC_OIPER, 0AC_OIYEAR, 0AC_ORDOCNR, 0AC_ORPER, 0AC_ORYEAR, 0AC_RVDOCNR, 0AC_RVPER, 0AC_RVYEAR, 0BCS_AREA, 0BCS_AUTODL, 0BCS_BGPER, 0BCS_BGYEAR, 0BCS_COIACT, 0BCS_COIFUT, 0BCS_COIINA, 0BCS_COINRT, 0BCS_COIPGW, 0BCS_COITOA, 0BCS_CTFLG, 0BCS_DPER, 0BCS_DTEQI, 0BCS_GWLC, 0BCS_GWMAN, 0BCS_GWNEG, 0BCS_GWPROC, 0BCS_LCCMU, 0BCS_LCIC, 0BCS_OBJNR1, 0BCS_OBJNR2, 0BCS_OBJNR3, 0BCS_OBJNR4, 0BCS_OBJNR5, 0BCS_OBJNR6, 0BCS_OBJNR7, 0BCS_OBJNR8, 0BCS_ORGCH, 0BCS_ORGCHL, 0BCS_PRGRP, 0BCS_REFPER, 0BCS_REFYR, 0BCS_SEQNM, 0BCS_TASK, 0BCS_TASKGR, 0BCS_TASKTY, 0BCS_TAXSUP, 0CS_COIAC, 0CS_COINR, 0CS_PLEVEL, 0CURRENCY, 0DATE, 0UNIT, 0USERNAME
Compounding -
When you define the compounding of an InfoObject, some compound relationships are not supported:
You cannot compound subassignments to consolidation units.
You are not permitted to compound the document type and the (0CS_PLEVEL) posting level.
You cannot compound noncurrent assets and assets/liabilities to 0BCS_ALTYPE. In addition, you cannot compound to a characteristic from the totals cube, with the exception of consolidation units, partners, and so on, and their higher-level characteristics.
ODS objects / Virtual InfoProvider -
You can generate the ODS objects for additional financial data and the virtual InfoProvider from the data basis maintenance. However, you can also create these manually and enter them in the data basis. If you do this, create the ODS objects and virtual InfoProvider with the same characteristics and structure they would have had if generated by the data basis maintenance. You can only deviate very slightly from this.
You are not permitted to include the following InfoObjects in any InfoProvider, unless they are generated by the data basis automatically:
0BCS_AREA, 0BCS_REFPER, 0BCS_REFYR, 0BCS_TASK, 0BCS_TASKGR, 0BCSTASKTY
The following InfoObjects must not be contained in the InfoObject catalog, which is defined in the data basis:
0BCS_AREA, 0BCS_REFPER, 0BCS_REFYR, 0BCS_TASK, 0BCS_TASKGR, 0BCSTASKTY, 0FISCYEAR, 0FISCPER3
Time characteristics -
SAP consolidation SEM-BCS ignores changes with the 0FISCPER, 0FISCPER3, 0FISCVARNT and 0FISCYEAR time characteristics. If you make changes, for instance, if you create hierarchies or attributes, these are not taken into account by SEM-BCS. Therefore, there is no maintenance in the workbench, you cannot use the hierarchies or attributes in the functions of SEM-BCS for selections and so on, and you cannot use the attributes or hierarchies for selections in BW queries.
Characteristic values
The following InfoObjects may have the values set by default by SAP only . You are not permitted to change them, not even by using the BW master data maintenance:
0BCS_AREA, 0BCS_AUTODL, 0BCS_COISRT, 0BCS_CTFLG, 0BCS_DIDIEL, 0BCS_GWMEM, 0BCS_GWPROC, 0BCS_IPAAC, 0BCS_IPATTY, 0BCS_OBJNR1, 0BCS_OBJNR2, 0BCS_OBJNR3, 0BCS_OBJNR4, 0BCS_OBJNR5, 0BCS_OBJNR6, 0BCS_OBJNR7, 0BCS_OBJNR8, 0BCS_REPMOD, 0BCS_TASK, 0BCS_TASKGR, 0BCS_TASKTY, 0BCS_TAXSUP, 0BCS_TIMMOD, 0CS_COIAC, 0CS_PLEVEL
For these InfoObjects you can only use the tools of the master data service of the Financial Basis to synchronize master data, so the master data is transferred by the SEM-BCS tables to the BI tables, but not the other way round.
Predefined InfoObjects for individual roles
The system automatically uses most of the InfoObjects mentioned here to activate certain data streams. However, there also are some InfoObjects that you must manually enter in the cube for the totals records. Subsequently, you must assign certain roles to these InfoObjects. These roles are allowed for these InfoObjects only, you cannot assign these roles to other InfoObjects.
These are:
0CS_PLEVEL for the posting level role (required)
0BCS_CTFLG for the conversion role (optional)
0BCS_PRGRP for the product group role (optional)
Activate characteristics and key figures from BW Content
Before you create a data basis of SAP consolidation, you have to activate certain InfoObjects from BW Content.
1. You must always activate the following: 0CS_PLEVEL, 0FISCPER, 0FISCPER3, 0FISCVARNT, 0FISCYEAR.
2. If you use documents, you must also activate: 0AC_DOCLN, 0AC_DOCNR, 0AC_DOCTEXT, 0AC_IVDOCNR, 0AC_IVPER, 0AC_IVYEAR, 0AC_OIDOCNR, 0AC_OIPER, 0AC_OIYEAR, 0AC_ORDOCNR, 0AC_ORPER, 0AC_ORYEAR, 0AC_RVDOCNR, 0AC_RVPER, 0AC_RVYEAR
3. If you use the virtual InfoProvider, activate: 0BCS_REFPER, 0BCS_REFYR, 0BCS_REPMOD, 0BCS_TIMMOD also
4. If you use any data stream in addition to the totals records, also activate: 0BCS_OBJNR1, 0BCS_OBJNR2, 0BCS_OBJNR3, 0BCS_OBJNR4, 0BCS_OBJNR5, 0BCS_OBJNR6, 0BCS_OBJNR7, 0BCS_OBJNR8
5. If you use the data streams of the consolidation of investments, activate: 0ACQ_PER, 0ACQ_YEAR, 00BCS_BGPER, 0BCS_BGYEAR, 0BCS_COIACT, 0BCS_COIFUT, 0BCS_COIINA, 0BCS_COINRT, 0BCS_COIPGW, 0BCS_COISRT, 0BCS_COITOA, 0BCS_DPER, 0BCS_DTEQI, 0BCS_GWLC, 0BCS_GWMAN, 0BCS_GWMEM, 0BCS_GWNEG, 0BCS_GWOFFS, 0BCS_GWPROC, 0BCS_GWRED, 0BCS_LCCMU, 0BCS_LCIC, 0BCS_SEQNUM, 0CS_COIAC, 0CS_COINR
6. If you use organization changes, activate: 0BCS_ORGCH, 0BCS_ORGCHL
7. If you use data streams for stock and delivery data, activate 0BCS_PRGRP.
8. If you use data streams for assets/liabilities or noncurrent assets, activate: 0BCS_ALTYPE, 0BCS_DPER, 0BCS_DYEAR, 0BCS_IPADAU, 0BCS_IPALCM, 0BCS_IPATTY, 0BCS_RETBG
The list of the InfoObjects varies depending on the release. Of course, you do not have to activate InfoObjects that do not exist in your release.
You do not have to activate InfoObjects that are not explicitly specified. However, if you do not activate them, some functions may not be available to you. For example, if you do not activate the 0BCS_CTFLG InfoObject and do not use it for totals records in the InfoCube, the currency translation cannot display any currency translation differences on the initializing data records.
Attributes When you define the InfoObjects in BW, attributes can be assigned to InfoObjects. This results in the following restrictions:
In SEM-BCS 3.1B, 3.2 and 3.5, no InfoObjects that appear in the permanent parameters of a consolidation area or are fixed in a consolidation area may be attributes of an InfoObject used in SEM-BCS.
InfoObjects that are used as a consolidation unit must not have 0FISCVARNT as an attribute.
Note 727776 - Requirements of SEM-BCS for data model.
check these links also:
http://help.sap.com/saphelp_sem40bw/helpdata/en/67/f7e73ac6e7ec28e10000000a114084/frameset.htm
Re: Synchronize Master Data between BCS and BW within the same SEM system
/message/1508507#1508507 [original link is broken]
http://sap.ittoolbox.com/groups/technical-functional/sap-sem/dataflow-from-r3-to-sem-bcs-950671
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/6e01a04e-0a01-0010-dfbe-951c2c39d169 [original link is broken]
http://help.sap.com/saphelp_nw2004s/helpdata/en/c4/9057475ca611d4b2e30050dadfb23f/frameset.htm

Total transfer

Hi all,
We are using SEM-BCS 6.0 and we have a question.
We are having an inconsistency in the Totals Records after a total transfer in a downwards movement.
At the consolidation area GA01, consolidation unit PL01 has 100% participation in PL23 and PL23 has 100% participation in PL24.
Now we have done a downwards movement of PL24 from GA01 to GA08 where we have a total transfer of participation from PL23 to PL22.
We also execute the task "Change to Consolidation Group" in order to clear financial statement itens of PL24 at GA01.
The error we get is that in the consolidation of investments the elimination of the investment (posting level 30) is being posted to an incorrect partner company.
The partner company should be equal to the investee unit (that should be PL24) but is being posted to a partner company (PL22 and PL23).
In the Totals Records, the investee is correct (PL24) but the partner company is incorrect, is being posted as PL23 and PL22.
Example:
Investee unit - PL24
Company - PT23
item - 51000000 (equity item)
partner company - PL22 (should be PL24)
posting level - 30
Can you please help me?
Thanks for your help.
Best regards.

Because partner unit is not relevant for COI and only investee is relevant, partner unit is not changed with the total transfer. Only a manual entry will change the partner unit for posting level 30 records but it should not be necessary.

Total Transfer between paralel consolidation groups

Hello Gurus!
We are using SEM-BCS for legal consolidation of our consolidation hierarchy. The hierarchy stands as shown below in 04.2014:
CG00
     CU000
      CG20
          CU005
          CU001
     CG01
          CG19
               CU018
     CG02
     CG03
In period 04.2014, we have to make a transfer of one consolidation unit (CU001) from consolidation group CG19 to CG20.
In consolidation group CG19 in 03.2014, company CU001 is hold at 100% by consolidation unit CU018.
In consolidation group CG20 in 04.2014, company CU001 is transferred to this consolidation group, as well as the participation (100% of the shares) from company CU018 to company CU005.
The holding of the hierarchy is CU000 in CG00.
To execute the transfer, we created organizational change company and organizational change number in the master data tab. Afterwards, company CU001 was changed from consolidation group CG19 to CG20. In the company CU001 we set the mark for first consolidation with organizational change and indicated the ID of the organizational change.
After this definitions in the master data tab, we executed the task for consolidation group changes, obtaining the following result:
Balance sheet items were correctly posted in group CG20, as this the destination group of the transfer. But on the other hand, the elimination from the previous consolidation group (CG19) is being wrongly executed, as the elimination is being executed in consolidation group CG00, when this should be posted in CG19.
Could you help us understand what is being wrongly made, for the post being made in CG00 and not in CG19.
Thanks in advanced.

Thank you for your reply Dan.
Responding to your questions:
1) The operation wasn't made with indication of divestiture in period 004/2014. However I tried to test it with that indicator (divestiture with OC), and the results weren't diferent from the ones i'm obtain now.
2) The consolidation group changes were executed.
3) The whole balance sheet accounts. The consolidation group changes were executed at levels 02, 12 and 22.

Copy data posting level 20 - 30 is not allowed SEM BCS

Hi expert,
We need to copy data from a version to another version, is very
important for us to import documents with posting level 20/30. Copy
task is only used for documents with posting level 01 - 10. But, in EC - CS we could to execute the copy program for this kind of documents,
and we are migrating from Ec-cs to SEM BCS so, we need to keep the same
funcionality.
Any idea in order to solve it? Badi´s? user exits?
Thanks in advance,
Beatriz Bernardos

Hi
It is not possible to copy data at posting level 20 and 30 as they are group entries.
Logically, it should not allow one to copy the entry at posting level 20 and 30.
SAP doesnt support copying data at posting level 20 and 30.
I had same kind of requirement in all of my BCS project but I believe logically it is not correct to copy group level entry.
Alterntively, what you can do is,
create export datasource to load the data back into BCS integration cube from BCS total records virtual cube by changing posting level 20/30 to 01 or 10 in the update rule.
It still believe it will give you the wrong result in the report.
Please have a common understanding with customer that it is not possible copy posting level 20/30
Regards,
Manish

Remote Extractor and Real Time Infocube for SEM BCS

Hi Experts,
I have somes doubts about the integration between SEM and BW.
There is a cycle that have the next processes:
1.- begin in R/3 with the movements in FI, CO and/or general ledgers
2.- Activate the extractors standards for replicate/extract data to BW. For example, 0FI_GL_XXXX.
3.- Configure a method for take the information from BW to SEM.
4.- My doubt begin here... For take the information from SEM to the real time infocube, where I configure? What Have I for configure?
The real time infocube, What is the proposal? Where take the data? Here, Do the remote extractor begin to apply?
Thank you very much for your collaboration.
Regards,
Jeysi Ascanio

We're using 0FI_GL_20 to read directly from FAGLFLEXT into SEM-BCS via a BI remote cube. There are some basic transformations in BI to "populate" the remote cube, then a standard Load from Data Stream in BCS to do final mappings. In the BCS workbench, just create a source data basis off the remote cube.
This works at my current project due to fairly low ECC data volumes. If you are doing any complex mapping on the Company or Fiscal Year / Period infoobjects, you may need to create a inverse mapping routine in the remote cube to transfer selection criteria. If you see messages in the monitor following a data load such as "xx,xxx of xxx,xxx records ignored", that means that you are reading too much data from ECC and it is only getting filtered on the BCS side. We had this problem with a custom extractor and adding an inverse mapping routine cut the load from ~5min to 30sec. (Basically, the custom, template-delivered, extractor only had 0FISCPER, not 0FISCPER3 and 0FISCYEAR, so we would read all 17 K4 periods into BI, map them into BCS, then BCS would throw out the unneeded periods. Unfortunately, we did not have the option to change the extractor, so this was the best approach.).
If I had large data volumes, I would use a regular BI basic cube for staging (or possibly a multi-cube with a mix of basic and realtime, depending on the load requirements to BCS).
If you use 0FI_GL_20, I would strongly recommend you implement OSS Note 1245822, or be on SAP_APPL 603.0002 or later.
Hope that helps,
- Chris

How to Organizational Changes

Hi Team,
We are planning to use the Functionality Organizational Changes for Total Transfer and Partial Transfers of Consolidation units from one consolidaion group to other groups,
We have Configured the following
1.Enabled organisation change in the Consolidation area,
2.Created Organizational Change Number for Sending and Receiving Consolidation groups
3 Created Document types with posting level 02, 12, 22
4.Created a tasks.
5.Assigned Fs item in COI settings.
Do we need to do anything else in Consolidation of Investment for this?
What is Activity for Organizational Change logic and how to configure this.
Thanks in advance
Kind Regards
Sreedhar

HI
It will be good if you can send some scenarios as OC logic will need to be inserted in the MAster Data for Consolidation Units within a consoliodation Group indicating transfer is with OC logic and inserting that number & in few cases inputtign the end date as 06/2009 e.g in the sender & receiver group same data as starting
It again depends how is the move is it vertical move horizontal move or same level
then with his that OC logic Number you have to configure all Reciever & sender Entitties starting from the immeidate Parent to the uppermost parent
Hope this gives some clarity ,do rite back for more details
rgds
dheeraj

Multiple Fiscal Year Variant in the same client in SEM-BCS...

I have already looked at some earlier threads relating to this but didn't get a convincing answer to what I would like to know.
We have had a working SEM-BCS system with fiscal year variant K4. There was no need for defining leading fiscal year variant and none was defined. SAP, by default takes, K4 as the leading fiscal year variant.
Now there is a requirement for going on a different fiscal year variant for which we have created another databasis (there were a few other reasons besides these) with the same InfoObjects that we used earlier but with different fixed parameters, one of which is fisc year variant V9. Soon, we started experiencing bizarre dumps in the configuration which ultimately convinced me to define a leading fiscal year variant. I was reluctant to do so because there is a lot of old data (which will become 'historical' from new data basis point of view) from the working system on K4 that would still need to be reported on even when we have new BCS solution in the new fiscal year variant V9. That is not going away. There is a need to keep the old data for reporting (hence the rationale for a different data basis among a few others).
Since earlier Master Data was configured in the old fisc year variant K4, now I have defined the leading fiscal year variant as V9 so that MDF can appropriately identify the period dependency.
I would like to know if any of you have had an unexpected behavior from the system going forward. Does the system dump out when you try to read the old data (from earlier K4).
I have tried to explain the dilemma as clearly and succinctly as possible but if you need more clarifications, please do let me know.
I would really appreciate your help in this.

Is your requirement is that K4 to be changed to Z5.
The best way you can do it is in the transformation. Instead of directmapping,
Write a code like this in the trransformation to the cube
If SOURCE FIELD - 0FISCVAR eq 'k4'.
SOURCE FIELD - 0FISCVAR = 'Z5'.
I dont think we can change th data in the query being displayed. we can change the keyfigure values in query by frmulas etc...
but for a characteristic, i think we will be able to restrict bt not change the value.
to obtain the requirement, w have to get the data change before query designer that is in the cube leve.
Hope this helps,
Sri...

SEM-BCS Short Dump while executing Manual Posting Task

Hi SEM-BCS Colleagues,
I am having a peculiar problem with relation to the settings for Manual Postings. I have three scenarios for which I have defined manual document types and tasks 1) Standardizing Entry (Data Collection) 2) Manual Document in IU for adjustment 3) COI Group level manual postings. I am just creating and not changing any settings for document field properties also. I have configured monthly consolidation frequency and period category and I am posting document type 1 in Local Currency and 2 and 3 in Group Currency since they are after currency translation.
Have any of you faced similar problem and help me please?

Hello,
I am also getting short dump during data collection in BCS.
we recently upgraded the system to SP20. Is it anyway related to upgrade.
I also checked the MYSELF as a source system, but not found one.
Could you please let me know how you have solved this issue.
short dump:
Runtime Errors         PERFORM_TOO_MANY_PARAMETERS
Exception              CX_SY_DYN_CALL_PARAM_NOT_FOUND
Date and Time          04.12.2009 05:21:11
Short text
     Too many parameters specified with PERFORM.
What happened?
     In a subroutine call, there were more parameters than in the
     routine definition.
     Error in the ABAP Application Program
     The current ABAP program "SAPLRSDRI" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_DYN_CALL_PARAM_NOT_FOUND', was
      not caught in
     procedure "RSDRI_CUBE_WRITE_PACKAGE_RFC" "(FUNCTION)", nor was it propagated by
      a RAISING clause.
     Since the caller of the procedure could not have anticipated that the
     exception would occur, the current program is terminated.
     The reason for the exception is:
     A PERFORM was used to call the routine "CUBE_WRITE_PACKAGE" of the program
      "GPD1S8520HM8UV0U2XBDVPADF03".
     This routine contains 7 formal parameters, but the current call
     contains 10 actual parameters.

Total Transfer & Organizational Change (SEM-BCS)

Similar Messages

Maybe you are looking for