SEM BCS Documents required

Hi Experts,
I would like to learn about BCS, how doesn't link to BW system. Can anybody share SEM BCS Documents.
SRI

Hi,
Check the below thread for more info:
Re: BCS module implementation
SEM BCS
http://help.sap.com/saphelp_nw04/helpdata/en/67/13843b74f7be0fe10000000a114084/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/events/sap-teched-03/using%20process%20chains%20in%20sap%20business%20information%20warehouse
Reg
Pra

Similar Messages

SEM-BCS Fi requirements

Hi all,
We are planning to work with SEM-BCS (Consolidation). Is there any requeriment or condition that you have to take care or implement in FI module regarding customizing? We are not using New-GL and the sap version is ECC 6.0.
Any help on this topic will be very usefull.
Thanks in advance.
Regards
Lionel

Yu need to d any custme r config setting in R/3 fr cnslidating.
Yu would be ding consolidating from BW to BCS Where yu t run the data stream t lad the data nce the BCS design has done.
For Customizing...
SEM-BCS
Transaction Codes
SEM BCS T-Codes
For BCS
http://help.sap.com/saphelp_nw70/helpdata/en/f5/e16f3a53dee246e10000000a11402f/frameset.htm
Edited by: Prasad B on Aug 20, 2008 1:42 AM

BW Based SEM BCS

Hello...
I have a problem as explained below , will appricate if anybody can share there experience to help me out of it. THX IN ADVANCE....
Problem :
We are using standard extractor 0SEM_BCS_10 for extracting R/3 data for SEM-BCS. We observed that Company ID of Trading partner was not being extracted even for those line items in FI which has Trading partner value.
We investigated and observed this extractor fetches data from new GL Stagging ledger and further noticed that the stagging ledger captures this information about trading partner only if Scenario "Preparation for Consolidation" is assigned to the stagging ledger. But the problem is extractor is capturing the above information only prospectively and we have the requirment to capture Trading partner information even for our historic data.
Is there any way we can achive this.
Thanks & Regards
Prabhakar

Hi
Do you have some document on BCS ?
Thanks
Satya

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

SEM-BCS without carry forward

Hi all,
Has someone configured SEM-BCS without the carry forward task.
And can you share the pros and cons of doing this?
Thanks, Alvin

Thanks Greg, Dan, Thibaud for your responses. he are very much appreciated.
I wanted to attract some debate/discussion on the matter. Personally, I am not convinced that carry forward is not used.
However a bit more context. My client is using SAP PBF and PBF can pass on Opening balances to BCS. BTW this relates to budgets more than actuals.
There are the usual related party eliminations and possibly consolidation of investments so that BCS can deal with them in a variety of reporting hierarchies.
Other requirements include
- budget may be increased/decreased 2-3 times a year
- these increases/decreases are captured as adjustments for the relevant period. This changed budget (sometimes for the same fiscal year) is the authority for spending
- there are 4 years of estimates (say Est1, Est2, Est3, Est4 representing each future year) and they do not roll on to each other. In other words, Est1 do not roll into est 2 and est 2 do not roll into est 3 and so on. Rather est 1 roll into est 1, est2 into est 2, either in the same fiscal year or the next fiscal year (it sounds confusing hence I hesitated to put that with my initial question)
So far, based on other conversations, I have gathered the following:
- Not generally done in BCS where opening balances are required
- Documents posted in the previous year will not inverse
- Consolidation adjustments relating to previous years will have to be re-posted in current period. Flexibility to report these adjustments for a particular period will be lost.
- Additional items/subitems will be required for opening balances, as compared to opening balances captured in period 00,
- Many BEx reports (probably some reclasses and allocations) that are looking for the beginning balances in the period 000 will start malfunctioning.
- Copy Tasks (this will used for different consolidation versions) may end up with incorrect data if they require previous period results
- Not being able to close book for the year?
Anymore input would be appreciated.
Cheers, A

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

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...

Unable to provide input value to InfoObject in SEM-BCS

Hello BI Experts,
I have created an infoobject 'ABC' in BI and have flagged 'With Master Data' and 'With Text'. This infoobject has an navigational attribute 'XYZ'(XYZ also has 'With Master Data' and 'With Text').
When I go to T.Code UCWB(BCS Workbench), I could able to see the infoobject 'ABC' and when I try to create master data for 'ABC', I do not see the input field for 'XYZ'. I want to input values in Infoobject 'XYZ' through this screen(SEM-BCS) and not through BI(right-click on infoobject 'Maintain Master Data). Please let me know, if I am missing anything.

Hi Shekar
I find the ICD setup very 'picky'! If you get one thing wrong, it doesn't work. I have detailed below the steps I usually advise people to tek. Check your setup and see if this helps.
1. Define Plan Type, Compensation Category = Others.
2. Define Plan. Link to Plan Type. Plan Usage = May not be in program. On Not in program Tab - define sequence, currency, enrollment rate (per pay period?), activity reference period (Monthly). Your settings may need to be different. On Plan details tab, enter plan years.
3. Plan enrollment requirements. On the general tab, plan sub tab, make sure the method = EXPLICIT. this allows the user to enter an input value for the ICD. THIS MAY WELL BE THE SOURCE OF YOUR PROBLEM!
Make sure the CERTIFICATION region is UNTICKED. This can also cause ICDs not to work.
ALLOWS UNRESTRICTED ENROLLMENT must be TICKED. Otherwise there is no eligibility to the ICD.
On the rates subregion, make sure the run strt date is set to ENTERABLE.
4. standard Rates form. Make sure the ACTIVITY TYPE and TAX TYPE are entered. Select the ELEMENT and the INPUT VALUE and TICK the ELEMENT AND INPUT VALUE REQUIRED field.
On the processing Information tab - TICK ASSIGN ON ENROLMENT, DISPLAY ON ENROLLMENT and PROCESS EACH PAY PERIOD. Enter PER PAY PERIOD AMOUNT in VALUE PASSED TO PAYROLL and OTHER in COMPENSATION CATEGORY.
Let me know if this works!
Regards
Tim

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.

SAP BPC Consolidations vs SEM-BCS

Hi all,
Has anyone compared the features/functionalities of SAP BPC Consolidation with SEM-BCS consolidation? What are the advantages of BPC Consolidation over SEM-BCS, and vice-versa? For a brand new implementation, what is the preferred tool?
Thanks,
Sujoy Banerjee

Hi Sujoy,
In general if you are starting out with a new implementation, BPC is the recommended solution for several reasons:
1) It's a unified solution offering both Consolidations and Planning
2) It's designed to be owned and managed by business users, not IT
3) It's integrated with the Enterprise Performance Management for Finance suite, which also includes profitability and strategy management
If however you need support for complex consolidation scenarios, such as legal consolidations, you may want to consider BCS.
You should be able to find several documents comparing the two solutions if you go the Support Center (https://websmp104.sap-ag.de/support) and do a document search on BPC vs. BCS.
Hope this helps.
Chris Clay

SEM BCS in SAP ERP 6.0

Hi Experts
have you worked with ERP 6.0 and SEM BCS into the ERP?
in ERP 6.0 all SEM components like BCS, BPS, CPM are in the same system as "add on" or I dont Know, is posible to work with this componentes from ERP?
I think is necessary install SEM BW and plug ins, I will apreciate your comments about this..
Thanks in advance

I realize that this is a BCS SEM forum and I do believe that OLAP is a better technology than OLTP for consolidation functionality, but there are "equivalent" BCS transactions in ECC as well. UCMON is "roughly" CX20. The consolidation menu is CX00(N) and customization is CX01(N). Both have been visible directly after entering "/n" in OK Code input field.
For more go to menu CX000 (nonCX transactions may not work due to reasons mentined earlier in the thread):
    SEM BCS - Business Consolidation
--      CX00BCS                        Business Consolidation
   CXGP                           Global Parameters
--      Master Data
   Consolidation Groups
   Consolidation Units
   FS Items
   Subitems
   Custom Subassignments
   CXRH                           Characteristic Hierarchies
--      Data Collection
   CXCD                           Monitor
   Reported Financial Data
   Additional Financial Data
   Manual Posting
   Automatic Posting
   Utilities
   CXV1                           Validation
--      Consolidation
   CX20                           Monitor
--      Manual Posting
   CX50                           Enter
   CX51                           Change
   CX52                           Display
   CXA0                           Mass Reversal
--      Automatic Posting
   CX54                           Interunit Elimination
   CX5U0                          Elim. of IU Profit/Loss in Inventory
   CX57                           Consolidation of Investments
   CXEC                           Reclassification
   CX24                           Preparation for Consolidation Group Changes
   Utilities
   CXV1                           Validation
---      Information System
   ECCS                           Consolidation Reports
   Tools
--      Business Information Warehouse
--      Business Explorer
   FC_BW_BEX                      Business Explorer Analyzer
   SEM_NAV                        Business Explorer Browser
   FC_BW_RSZV                     Maintain Variables
   FC_BW_RSZDELETE                Delete Query Objects
---      BW Administration
   FC_BW_RSA1                     Administrator Workbench
---      Tools
   S001                           ABAP Workbench
   S002                           Administration
   SBPT                           Business Communication
--      Business Engineer
   SPRO                           Customizing SEM BCS
--      Business Framework
   BAPI                           BAPI Explorer
   BAPI Development
   SWLD                           Business Workflow
--      SAPscript
   SE71                           Form
   SO10                           Standard Text
   SE72                           Style
   Administration
--      Hypertext
   SO70                           Structures
   SO72                           Documents
      ---      Find
          |
          |-----   Information System
   SO80                           Information Classes

SEM-BCS how to make Consolidation Unit with Business Area

Hi all,
I am newbie in SEM-BCS and implementing BW-based BCS. Our situation is as follows.
Situation
- we have 7 companies worldwide and 4 different Business areas.
   Every company consists of at least two business areas in R/3.
- we have sales transaction in FI among companies.
requirement
- we need consolidated F/S in whole consolidation group and consolidated F/S in Business area level.
actually, we are planning to make the consolidation unit in company level.
Do we have to break down consolidation unit in business area? or just breakdown category solves our requirement?
If we have sales transaction even between business areas within certain company, do we have to make it in business area?

Following are the answer to your questions
Q:   What to do for using this cube in BCS?
A:    Add the business area to the cube. Generate the data basis and the business area gets added to all ODS/DSO , virtual cube.
Suggestion: To avoid deleting the Profit center cube, since you can reduce the complication.
Q:   Is it the problem about DATA BASIS Role?
A:   No. Assign the role of subassignment or consolidation unit as needed. If you are giving the role of consolidation unit to business area, you need to insert the char Partner business area also in the cube.
Q:   Is there some materials to solve this situation?
A:   Refer the matrix consolidation material in help.sap.com from BCS portion. As per SAP literature any relevant object can be made as second consolidation unit such as business area, functional area etc. Dont fear. Once you start it the issue will be resolved in few days.
Expected complication:
If you are going to make business area as subassignment then it is simple. But if you are making business area as Consolidation unit, go for partner business area in cube.
Ensure with your BI consultant that all BCS messages are addressed in BI infoobject for business area specifically.
Things can get complicated only if we allow for it get complicated. But you are doing great.. Keep posted.. Good luck.!!!..

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

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

SEM BCS Documents required

Similar Messages

Maybe you are looking for