SEM-BCS (BW Reporting)

Hi All,
I would like to know how SEM-BCS stores data (balance values) in BW cube. If I have to generate a B/S report, how would I restrict the Key Figure to show balance as of the 2nd quarter? The issue is the ranging of the Posting Period. Is it (4 to 6) or 6(Last month of quarter) or (1 to 6)?
Thank.

it depends what you want. you want to show cumulative balance or non-cumulative balance from ytd.
since it is balance sheet, i would assume u r refereing to the cumulative balance from ytd ( which also includes the balance carry forward.)
in that you can restrict it to period 1 through 6.
other case:
you report only shows the monthly balances or transactions in the month. then you can go for period restriction period 6.
hope this helps.
Regards,
BWer
Assign points if helpful.

Similar Messages

SEM BCS-BW Reports development

Hi All,
I need help and suggestion from your side .
We have X -reports in SAP-BW whcih are actual & planning cubes based .
We have Reporting & Total cubes in separate system (SEM-BCS)
So req is that we need to develop Y-new reports in SEM-BCS as it is the X-reports which are avialable in SAPBW.
Problem is that while developing new Y Reports in SEM-BCS many Char Infobjects & Time Char,Key fig are missing in SEM-BCS cubes .
Please suggest me how to proceed.
Thanks&Regards
Venkat

Hi Venkat,
I'm afraid that there is not much we can help you with. Everything in your case depends on the specifics, details.
I can give only some suggestions. In many cases it's either impossible or meaningless to build all the reports from one reporting cube. That's why, first of all, try (yourself or with the help of functional people) separate all the reports you need to build into 1. using non-consolidated data (it might be a simple sum of all ConsUnits figures, without eliminations) and 2. using consolidated data.
For 1st category, I beleive, you may use just BW cubes. For the 2nd one - BCS cubes. Take into account that the BCS cubes have some limitations on the key figures and time chars usage. And it's not prudent (or feasible) to insert such non-standard (for BCS) infoobjects. Insist on reasonable limitation of reports to be built from the BCS cubes by those which are really relevant for consolidation.
Another investigation to be considered is: examine if planning, forecating and actual data are comparable -- I met such a situation when details and subassignments of budget data was significantly different from those of actual.
Edited by: Eugene Khusainov on Nov 5, 2008 6:34 AM

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

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

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.
<u>Question:</u>
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 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 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

SEM-BCS configuration

Hi Gurus,
I am in the process of implementing SEM-BCS consolidation based on BW. I don't know where to start and how to start. Anu body can help me to do the necessary configurations

Hi Latha,
It is good that you are starting to learn SEM-BCS. To do that you need to have the knowledge of Business Process. Since you are FI certified understanding of Business Process should not be a problem.
Add to this, it would be better to have knowledge also in BW. As SEM-BCS is an application the storage of Data will be in BW and also the reporting.
SAP provides enough documentation, at http://help.sap.com but initially you might not understand everthing at one shot. Keep trying.
Best of Luck.
Regards
Narayana Murty

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 Faq's

Hi Friends,
I will have technical discussion on SEM BCS. Please send me the some useful material on SEM BCS and
please send me any FAQ's from interview presepevtive.I would appriceiate if any body respond to this post.
It would be very great helpful for me.
what are the impaortant areas we need to cover.
Please ahre ur vies on this.
Will assign the points.
Thanks in advance.

Hi SAPSEM,
From your past posting I understand you are good in BW. Hence know well the distinction between basic cube, transcational cube, virtual cube and what context it is used. You must know why the reporting is prepared on VC. Cover the BCS dataflow, data stream ,reporting, performance, consolidation area properties, method/task/document type. Try to know well the master data part of BCS well.
Good BCS literatures is available in service.sap.com, but most exhaustive one is help.sap.com.
Compliments
Mani.

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

SEM-BCS on SAP-BW master data alignment

We are implementing SEM-BCS rel 3.2 on SAP-BW 3.2
In the SEM infoproviders some standard BW info-objects are used such as 0CO_AREA, 0COMPANY etc.
These info objects are also used in BW infoproviders.
In SEM-BCS the masterdata that is already available in these infoobjects is not visible. The documentation describes that the SEM system is leading concerning the master data.
When we create masterdata in SEM for these infoobjects, with te same key as used in BW (the same company number), it creates new records in the BW masterdata table and so deleting the attribute values in the BW tables.
Note 689229 describes some synchronization programs that can be used to synchronize master data from SEM into BW. It is also possible to use these programs to initially synchronize the BW masterdata to SEM so you don't have to create the master data in SEM but only have to enhance it.
Has anyone have experience with this issue and can you provide me with information what to do and what not to do.
Thanks, Wil Heijmans
Trespa International

Hi Wil,
it's right you'll have to synchronize the master data. When we implemented SEM-BCS 3.1 we had some problems with the reports so we used the following routine.
1. Upload attributes into SEM-BCS.
2. Put them into the hierarchies if needed.
3. Synchronize attributes to BW.
4. Do attribute change run in BW.
Synchronizing hierarchies was a bit painful so we decided to use different hierarchies (it helped at some other points too because we needed additional features in BW hierarchies like other InfoObjects).
Synchronizing BW attributes into SEM-BCS attributes was even worse because the standard BCS attributes could not be filled this way.
We worked on early SEM 3.1 as one of the ramp-up customers. The programs may have changed in the meantime but the one above has worked for us.
Best regards
Dirk

Difference between SAP BPC & SEM BCS

Hi Gurus,
What is the difference between SAP BPC & SEM BCS And throw some light on both?
Thanks in Advance,
Sandy.

Hi Sandy,
The functionality in BPC mainly 1) Planning 2) Consolidation
1) Planning : You can have any type planning scenario. Ex.: Sales planning. Based on the actual previous data
we will have some projection reports on the sales for future sales, so we can have planning scenario here . We can change
the projections as per our requirement for any number of times.
Ex 2: HR Planning. Based on the market condition we have recruitment planning, based on the actual data (Existing Emp.)
Ex 3: Accounts Expenditure planning like this we can have planning forecastings.
2) Consolidations : We can consolidate the group company, companies with currency translations, allocations, Inter Unit
eliminations, consolidated P&L accounts & Consolidated Balance Sheets are possible in this.
But where as in BCS you can do only 2 part. The first part is not possible. Hence I personally suggest you to learn BPC NW
it will be more useful. BPC is now going to integrated with BO (Buss. Objects) also from 7.5 ver onwards.
I hope this may help you.
Regards,
B.S.RAGHU

CONSOLIDATION EC-CS Vs SEM-BCS

< MODERATOR: Message locked. Please read the [Rules of Engagement|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement] before posting next time. no ALL CAPS in the subject. I'd also recommend that you post in the Consolidations forum instead of here.>
Hi All,
Please explain me the difference btween
1. CONSOLIDATION SEM BCS AND CONSOLIDATION
EC CS.
2. under what circumstances each SEM BCS or EC CS will be used.
3. if possible plz give an example or a scenario.
thanks in advance.
Regards
Sirisha

Hi,
BCS is Business consolidation and Simulation and EC CS is Consolidation and Simulation in ECC 6.0 BCS is entirely out side R/3 and EC CS is R/3, here they have included some features in R/3 for consolidation and at the same time BCS is out side R/3 and has more features....while taking the reports then you take help of BW... end of the day you will get the data from R/3 even for BCS also...
Hope understood
Thanks,
Vasu...

SEM-BCS (BW Reporting)

Similar Messages

Maybe you are looking for