Transactions Used in SEM-BCS

Please let me know some transactions used in SEM-BCS

Hi Balaji,
Check these two threads on SEM-BCS T-codes:
SEM Transaction Codes
Re: SEM BCS T-Codes
Reward points if helpful. *
Regards,
Subhasha Ranjan

Similar Messages

Transactional data for SEM-BCS

Dear experts!
We are working in a SEM-BCS project and wonder which is the best solution to load data from FI-GL into BCS.
As far as I know there are two possibilities to do this:
.) extract form RFBILA00 and then use the flexible upload method
.) load the data into a FI-GL-cube in BW and then use the read from data stream method
Does anybody have experience with these two variants and know about the advantages/disadvantages?
Does it make a difference if you use new or old general ledger (concerning the load scenario)?
For me the load from the info cube looks more elegant, but the sap help documentation describes only the RFBILA00-extract (if you look for integration with other SAP systems).
Thanks in advance for any help.
Best regards
Michael

Hi Michael,
- Abt. RFBILA00 - I tried to use it but refused. Maybe I wasn't lucky enough, but I couldn't get partners.
- Abt extraction to BW - try to use 0SEM_BCS_10.
- I also used to activate extraction total records to GLT3 and then using the generic datasource extracted it in BW.
- There are many ways for extacting data in BW. I even saw such a decision where the whole huge BSEG table was used.
A work with new GL, IMHI, is preferable for BCS consolidation since there are some features that make a life a bit easier (it's easier to setup ERP in order to extract all info needed).

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

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

New GL features (Profit Center Segmentation) in SEM-BCS

Experts,
I'm planning to use New GL feature (Profit Center Segmentation) in ECC 6. I also intent to use SEM-BCS as consolidation report.
Can this New GL feature be used in SEM-BCS? Please let me know how to use them in SEM-BCS.
Thank you for your respond.

Sorry I was away.
I am in ECC 6 and the New GL report gives Profi center report . But I ca get the comfort like 8A ledger with drill down.
My doubt is will the new GL report takes care of all CO related transactions w/o GL?
Thanks, Chitra

Upload FS Items master using flexible upload-SEM-BCS

I want to upload FS Items master using flexible upload in SEM BCS. I was wondering if i could have a sample upload format of the file. Kindly help.
Ramanathan
[email protected]

Hi Ramanathan and welcome to SDN!
Everything depends on your settings in a flexible upload method.
You may use a comment character (like an asterisk) to show fields names and choose a fields delimiter (say, ';').
In this case you may have a file for upload something like the following.
These are fields in a header
Field1 Field2 Field3 Field4 etc.
Field1Val;Field2Val;Field3Val;Field4Val
These are fields in rows
Field5 Field6 Field7 Field8 etc.
Field8Val;Field8Val;Field8Val;Field8Val
Field8Val;Field8Val;Field8Val;Field8Val
Field8Val;Field8Val;Field8Val;Field8Val
Best regards,
Eugene

Transaction code to run SAP SEM BCS

I want to know that what is the transaction code to run SAP SEM BCS.. please reply to me if u know the transaction code for that.
thanks in advance..
regards.
Mohankumar.G

Hi,
UCWB - to run the workbench
UCMON - to run the monitor.
Best regards,
Eugene

SEM BCS: Transaction to install BCS

Hi! All....
Can anyone tell the transaction to install the delivery example of BCS ?
Thanks,
Victor

Hi Victor,
It's not a t-code. It's a procedure.
Follow the notes:
736226 - SEM-BCS 400 - Activation of the SAP delivery example
859893 - SEM-BCS 60- Activating the SAP delivery example
741004 - SEM-BCS - Activating delivery performance reference example
Best regards,
Eugene

Inconsistent Query Result in SEM-BCS using Virtual Info Provider

We have just upgraded to BW 7.0 and SEM-BCS 6.0. When we run an existing 3.5 BW query for BCS through the Virtual Info Provider against the basic consolidation cube, we are getting inconsistent results. Sometimes we get the correct result, and other times our results are not rolling up correctly causing an out of balance on our balance sheet query. We did not make any hierarchy changes between the query executions. Has anyone else experienced this? We cannot see the cause of the inconsistency. Everything looks good when running through RSRT DEBUG. Any help on pushing us in the right direction to solve this would be appreciated.
Thanks,
Rob

Hi Rob,
Could you please let me know how you have resolved this issue? Thanks.
Regards,
Ashok

Any landscape recommendations for 2004s BI & SEM-BCS 6.0 ?

Hi,
in addition to our ERP 2005 we plan to set up a separate central BI 7.0 for following integrated NW2004s scenarios:
- Enterprise wide central reporting, query and analysis.
- BI Integrated Planning (successor of SEM-BPS).
- SEM-BCS 6.0.
Question:
Should the BCS be installed on a separate system, because of patch interdependencies with the central BI?
If yes, does BCS still need its own local BI, or can it run remotely with the central BI (like the old BW-BPS)?
Similar sap recommendations exist only for SEM-BPS, which we won't use in favor of BI Integrated Planning.
I searched the whole sap.marketplace for this, in vain.
The installations and combination-possibilities are beautifully explained, but no official recommendations about what should all be put on one central BI and what should be better kept apart.
Rumors say you should keep SEM out of your central BI and give it its own BI, to avoid painful patch/release dependencies.
What about the "single point of truth"-conecept in one central BI then?
Thank's for any hints ...
Robert

Hi Eugene,
thanks for your callback. Here an example:
Say, you need a BI-Patch (urgent bug-fix) or may be a BI-Upgrade to be able to use new functionalities for your Enterprise wide central reporting, query and analysis (since you don't use the BI only for BCS).
So, you would have to wait, until the same is also available for SEM-BCS, as it it tightly coupled to the BI (e.g. direct writing to transactional cubes, query via virtual cube augmented with data at query-runtime).
Notes like 727776 and 317339 just make me suspicious.
A similar SAP Help-hint is only available for BW-BPS (but we will use BI integrated Planning)
http://help.sap.com/erp2005_ehp_02/helpdata/en/44/584041b02e4c0de10000000a1550b0/content.htm
Since more and more SAP-Applications need a BI, i am desperately missing a comprehensive overview, which of them should not be placed in the same BI for technical reasons (e.g. one sap-note says Bank-Analyzer and SEM-BCS should not be on the same BI).
Regards
Robert

2004s BI & SEM-BCS 6.0 in one System?

Hi,
Rumors say you should keep SEM out of your central BI and give it its own BI, to avoid painful patch/release dependencies.
Should the SEM-BCS be installed on a separate system, because of patch interdependencies with the central BI?
If yes, does BCS still need its own local BI, or can it run remotely with the central BI (like the old BW-BPS)?
Similar sap recommendations exist only for SEM-BPS, which we won't use in favor of BI Integrated Planning.
We plan to set up a separate central BI 7.0 for following integrated NW2004s scenarios:
- Enterprise wide central reporting, query and analysis.
- BI Integrated Planning (successor of SEM-BPS).
- SEM-BCS 6.0.
Thank's for any hints ...
Robert

Hi Eugene,
thanks for your callback. Here an example:
Say, you need a BI-Patch (urgent bug-fix) or may be a BI-Upgrade to be able to use new functionalities for your Enterprise wide central reporting, query and analysis (since you don't use the BI only for BCS).
So, you would have to wait, until the same is also available for SEM-BCS, as it it tightly coupled to the BI (e.g. direct writing to transactional cubes, query via virtual cube augmented with data at query-runtime).
Notes like 727776 and 317339 just make me suspicious.
A similar SAP Help-hint is only available for BW-BPS (but we will use BI integrated Planning)
http://help.sap.com/erp2005_ehp_02/helpdata/en/44/584041b02e4c0de10000000a1550b0/content.htm
Since more and more SAP-Applications need a BI, i am desperately missing a comprehensive overview, which of them should not be placed in the same BI for technical reasons (e.g. one sap-note says Bank-Analyzer and SEM-BCS should not be on the same BI).
Regards
Robert

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

Preparation for Consolidation in SEM-BCS.

Hello All,
Im implementing SEM - BCS (BW-based). I have the following versions:
- R/3: SAP ECC 6.0
- BW: 7.0
- SEM: 6.0
What do I have to customize in R/3 in order to extract the correct data to BW?
Do I have to do all the customization in transaction SPRO (Enterprise Controlling -> Integration: Preparation for Consolidation)?
I know that I have to create the companies and assign them to the company codes. I also have to create group chart of accounts and assign it to the transactional chart of accounts.
Can I do this in the account master data or do I have to have a Financial Statement Version for the Group?
Is it necessary to maintain Transaction Types for Consolidation?
Do I have to customize the Consolidation Staging Ledger and extract the data from here to BW?
I think I have to customize all this, but because all this transactions are in EC-CS customizing and I want to implement SEM - BCS (in BW), Im not sure if this is the right path.
Can anyone help me?
Regards,
Helena

Helena Coelho wrote:Helena Coelho wrote:Helena Coelho wrote:Helena Coelho wrote:
GANSHA,
what you are telling me is:
- I don´t have to do the customization in ECC. The only thing I have to do is, identify the tables and extract the data I need to BW.
But this way, how does the system know, which postings are from group companies or not?
The company code in R/3 is equivalent to company (consolidation unit role) in BCS. The Group companies are created in BCS and the companies in BCS are under those group companies.
If I were you, I would check whether Fiscal Year Variant is same across all company codes in R/3. I would also check whether parallel currencies are activated or not. Non-activation of parallel currency is not issue, but I will try to understand what are all the currencies involved and the currency translation flow.
I have created the companies in ECC in order to fill the "Trading Partner" field in the master data ( vendor, customer and G/L accounts) and to use on FI postings.
Yes, you have taken the right steps.
I have created the transaction types in ECC in order to use them on FI postings.
None of this is necessary? I dont have all the company codes in SAP, some of the data will be uploaded to BW by file.
The transaction types in ECC are different from the transaction types (also known as Movement Types) in BCS. You will continue to maintain the FI transaction types.
Regarding the chart of accounts, I dont have a group chart of accounts. For what I understand theres two ways:
- creating a group chart of accounts in ECC and in BW will be available as part of the GL account master data
or
- creating Financial statement items for consolidation in ECC, Build a Financial Statement Version for the Group (linking the operational chart of accounts to the consolidation items).
I think, this is the only way for me to use the consolidation staging ledger (totals table GLT3)? Or am I wrong?
What you are telling me is that I dont have to do this in ECC, but in BCS customizing?
Im confused ... please help me!!!
Helena
In your ECC, whether GLT3 table is activated? In many clients' companies, GLT3 table is not activated. The GL totals data is available in BSEG table.
If you do not have Group COA/ Group GL accounts maintained now, there are many ways to get GL totals data with Group GL level info added. You have already mentioned the steps.
One more method is create a custom mapping table of Operational GL accounts with Group GL accounts outside R/3 (to be maintained as part of BW) and make your R/3 GL totals data to flow thru this table, so that the final data in BW is available in both operational GL accounts and Group GL accounts. Developers will be able to help you.
Edited by: GANSHA on Jan 11, 2008 8:39 AM

R/3 Data Source for SEM BCS

Hi Guys,
I am using 0FI_GL_4 data source of R3 for SEM BCS.Am i right in doing so,please guide.
As per my understanding transaction data has to be taken to BCS for consolidation and hence this is the relevent data source.
Please provide comments on my understanding.
We are working in the following enviornment:
R3 version ECC6.0
SEM BCS ver 6.0
BW ver 7.0
Best Regards
Amit

Hi Amit,
It is enough normmally.
There are many data sources. It all depends what is your reporting requirement or what level of data to be extracted.
Let me know your reporting requirements to answer further

Transactions Used in SEM-BCS

Similar Messages

Maybe you are looking for