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

Similar Messages

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

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.

Concept of Integrated Consolidation Unit of SEM BCS

HI Experts,
I'm now in the SEM BCS 4.0 and BW 3.5 implementation. Previously I was the ECCS specialist and before the FI and AM specialist.
Now I'm in SEM BCS implementation.
I have one question in connection to the integrated consolidation unit. As the reference, I take the concept of this using the ECCS.
As you might know, the creation of integrated consolidation unit for using realtime update method in ECCS, is pulled from FI company ID.
Meanings if I set the configuration properly, I can pull out the company master data as the consolidation unit master data in consolidation monitor.
Now, in SEM BCS, I want to do the same thing. I mean, off course I can create company ID in R/3 and then create the consolidation unit manually using UCWB. But this scenario can create inconsistency, and I also think this is not the right concept of doing integration between R/3 and SEM BCS.
My question is : what is the concept of this master data integration, and what is the proper way to do it?
Any advise on this question is highly appreciated.
Thank you in advance.
regards,
Halim

Hi Halim,
You need to build properly your data basis in data model.
Assign your company to a consolidation unit role:
http://help.sap.com/saphelp_sem350bw/helpdata/en/dd/f3783bcfef4a2de10000000a114084/frameset.htm
I sent to you the file concerning BCS that you asked for in another thread.
Best regards,
Eugene

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 Data-Entry-Layouts

Hi all
We are currently planning a migration from EC-CS zu SEM-BCS. One goal is to replace the existing Excel-VBAs for data-entry, which are difficult to maintain.
Before we evaluate a solution outside of SEM-BCS we would like to check whether the Data-Entry-Layouts would be appropriate.
I was able to setup several forms (using data-driven or fixed structures). Data input works fine. Data is available in the cube after saving.
The problem: Whenever I open a data-entry-layout again the already existing data in the cube is not displayed. I can continue to enter data, which is also saved in the cube, but the already existing data is not displayed. This is not really user friendly.
- Does anybody have any idea what could be wrong with my forms?
- What are your experiences with the data-entry-layouts? Do you use them or do you use different ways to post data to SEM-BCS? What would you recommend?
Thank you
Best regards
Markus

The problem is solved by using all existing Support Packages. Obviously there was an issue with the data entry forms which was solved with one of the existing Support Packages.
Regards
Markus

Comparison between R/3-ECCS & SEM BCS

<b>Hi all,
We ve to compare thw two systems R/3 ECCS & SEM-BCS in detail as we are goin for consolidation i near future.
Could you all suggest some thing regarding this.
It will be very nice if you could suggest some parameters based on which these two are to be compared.
Regards,
Feddin.</b>

Feddin,
in EC-CS you have only one consolidation unit object. So if you are dealing with a matrix org then you have to compound for example company code and profit center into a CS unit object. This potenially creates a lot of units and therefore maintenance overhead.
With BCS you can keep the two dimensions separated and all combinations are valid (without the need to create them).
Regards
Marc
SAP NetWeaver RIG

SEM BCS Q&DB

Hi
I am looking for Q&DB relevant to SEM BCS BW based. Can any one send the link. Appreciate your help.
Regards
Chrizz

I doubt if there are updated version of 6.0 yet. Your best bet is to look on the BCS section of
service.sap.com/sem.
They are more likely info on 3.x and 4.0. There used to be an ASAP section with some questionaire on BPS and I think maybe something in BCS but things have moved around and I cannot find the ASAP section any more.
Hope this helps,
Mary

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

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

Authorizations for tasks (R_UC_TASK) / Best Practice SEM-BCS authorization

Dear Experts,
I am quite new to authorizations and in particular to SEM-BCS authorization. So I would be happy if you could help me with the following requirement:
We have to setup an authorization concepts for SEM-BCS. Among others we want to setup authorizations for consolidations tasks using authorization object R_UC_TASK. With this authorization object certain tasks can be restricted to certain characteristic values u2013 e.g. for a certain consolidation group or a certain consolidation unit. We have defined a role each for certain consolidation tasks. These roles are not restricted to any characteristic value yet. We have for instance a role u201Cregional controlleru201D who is allowed to perform certain BCS tasks on a regional level (consolidation unit level). This would mean that we would have to create the role u201Cregional controlleru201D for all consolidation units u2013 see example below:
Role 1: Regional Controller u2013 Cons. Unit 1000
Role 2: Regional Controller u2013 Cons. Unit 1100
Role 3: Regional Controller u2013 Cons. Unit 1200
Role n: Regional Controller u2013 Cons. Unit n
We have more than 400 consolidation units. So this would require a high effort. Is there instead a possibility of creating one role based on authorization object R_UC_TASK which just defines which activities can be performed (without restricting access to a certain consolidation unit). , and using second role which defines the consolidation unit access? u2013 see example below:
A
Role: Regional Controller
Role: Cons Unit 1000
B
Role: Regional Controller
Role: Cons Unit 1100
C
Role: Regional Controller
Role: Cons Unit 1200
In this case we only would have to maintain one role u201CRegional Controlleru201D and we only would have to assign the restriction for the consolidation unit. How could this be realized? Or do you have any other ideas to solve this requirement in a simple way?
Moreover I would be happy if you could tell me where I could find best practice scenarios for SEM-BCS authorizations.
Thanks a lot in advance!
Best regards
Marco

Hello Marco,
you can enter a master role in the description tab of a role. All fields populated via program PFCG_ORGFIELD_CREATE can be maintained in the role. All other fields will be taken from the master role. So you only need to populate the field for unit with the program.
Good luck
Harry

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

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

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

Similar Messages

Maybe you are looking for