SEM-BCS BAPI object's

Earlier I used a site http://ifr.sap.com for search BAPI of objects. Now the given site is closed. Prompt, where it is possible to learn about BAPI objects in SEM-BCS?

What i know so far ( i am new comer in BCS ), the source data basis is only applicable when do 'Load from data stream'. i have not explore the others.
i fill source data basis with 'Data basis'.
i'm not sure this will work because i am stuck in upload master data.
anyway, have you try to create master data and the delete it in workbench?
can you delete it? because when i tried to delete, errors come.

Similar Messages

  • SEM BCS - Error in Consolidation Area

    Dear Experts,
    When i save my consolidation area, there is an error message.
    it is "Syntax error in GP_ERR_UCDTYPE, row 8.880".
    The Diagnosis said "Component called REFYEAR already exists".
    I can not found "REFYEAR" in my system.
    I am using info cube 0BCS_C11.
    Please help....
    Thanks in advance.

    Hello
    Though I am not an expert in this area I have found the following information with a similar problem in another customer that maybe useful:
    "On the basis of your problem description it seems that you assigned in
    the data basis maintenance the `SEM-BCS info-object catalogue` for
    characteristics and key figures to the two info-object catalogues (on
    the first tab strip of data basis maintenance). This makes the trouble.
    Please read the F1 help carefully and if you need an extra info-object
    catalogue, then please create one. Please note that the SEM-BCS standard
    info-object catalogues are NOT appropriate for this purpose.
    F1 help:
    "InfoObject Catalog for Characteristics
    InfoObject catalog of the SAP Business Information Warehouse to include
    additional characteristics.
    Use
    You use this field as follows:
    In a data basis, the InfoObject catalog contains the quantity of
    additional fields that can be selected on the Additional Financial Data
    tab page for investments and equity.
    In a source data basis, the InfoObject catalog portrays the definition
    of an external field catalog, which can be used in a method of the
    category Flexible Upload, if a data basis was allocated to the source
    data basis."
    In order to remove the info-object catalogs you can use the transaction
    UCWB01.
    Hope it helps .
    Regards
    Javier

  • SEM BCS in SAP ERP 6.0

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

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

  • SEM-BCS how to make Consolidation Unit with Business Area

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

    Following are the answer to your questions…
    Q:   What to do for using this cube in BCS?
    A:    Add the business area to the cube. Generate the data basis and the business area gets added to all ODS/DSO , virtual cube.
    Suggestion: To avoid deleting the Profit center cube, since you can reduce the complication.
    Q:   Is it the problem about DATA BASIS Role?
    A:   No. Assign the role of subassignment or consolidation unit as needed. If you are giving the role of consolidation unit to business area, you need to insert the char Partner business area also in the cube.
    Q:   Is there some materials to solve this situation?
    A:   Refer the matrix consolidation material in help.sap.com from BCS portion.  As per SAP literature any relevant object can be made as second consolidation unit such as business area, functional area etc. Don’t 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.!!!..

  • 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

  • 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

  • FI-GL Activating for Consolidation SEM BCS

    Hello together,
    can somebody tell me in a few steps how to activate the FI-GL (0FI_GL_6) that it can be used for consolidation in SEM BCS. My problem is that FI_GL_6 (and also FIGL_C10 for new FI-GL) have not all required fields for consolidation in SEM BCS, especially movement type is missing.
    I know how to use the BCS data collection functionality "load of data stream" and I also know how to activate the BI Content for FI (and how to connect the data basis from BCS with the "FI Cube" via source data basis).
    But how can I prepare the FI Cube (DataSource, InfoSource) that it concludes all neccessary informations?
    I need following InfoObjects in the BI Content: how to?
    these InfoObjects are not containend in the standard FI-GL Business Content...or do you know other possibilities for getting FI-GL data in BW and ready for consolidation in BCS?
    0PCOMPANY
    0MOVE_TYPE
    nicht notwendig
    0FUNC_AREA
    0COMP_CODE
    0PROFIT_CTR
    0COUNTRY
    0PCOMPANY
    0GL_ACCOUNT
    Thanks for support

    Hi MP M,
    Hi Install all the components related to that flow.I mean Datasource,Transfer rules,Infosource,Update rules,Cube.Then nothing is missing in this flow which are in BI Content.
    For the Info objects not in the flow
    Search them individually from the BI Content and Install them.Later you map them respective fields in the transfer rules manually.Then maintain update rules to them.
    Hope this helps
    Regards
    Karthik

  • 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

  • Cartesis Vs SEM BCS Advantages / Disadvantages

    Experts
    Can somebody guide me, with advantages and disadvantages of implementing Cartesis Vs SEM BCS solution in major business scenarios ?
    e.g Comparitive study of these two tools on diffrent business aspects.

    This question keeps popping up - doesn't anyone use the 'search' function? - so I'll repeat what I posted, paraphrasing a discussion with a SAP sales director in Australia:
    Re: Cartesis solution in SAP portfolio
    SAP SEM-BCS is supported until 2013.
    but SAP now owns 3 consolidation tools, each is currently valid.
    - BCS,
    - BPC (from Outlooksoft) and
    - Cartesis (from Business Objects) all perform consolidation,
    Each has its pros and cons;
    - BCS - very good consolidation engine but not so user-friendly.
    - BPC - user-friendly but not so good consolidation, also has a non-SAP layout.
    - Cartesis - better consolidation engine than BPC but not as good as BCS. More user-friendy than BCS but not as good as BPC, again non-SAP layout.
    Although each is currently valid, there will be a combination of the best of all 3 in a new product with a SAP layout (or the same new product will be combined into a new release under the name of an existing product) at a date to be determined.

  • SEM-BCS authorization or Security Guide

    Hello,
    Last year We went Live with SEM-BCS Project.Now We need to restrict all the t-Code's in SEM-BCS. During the Go-Live We have provided  Full authorization's to everyone.Now Auditor's are bugging us to restrict the access in the SEM-BCS system.If Possible anyone can provide authorization or Security Guide for BCS Project
    Vijay

    Hello Again,
    Guide Contain's Only Authorization Object's & Default SAP Defined Roles. But Here it a different Scenario. SEM-BCS team has provided me 30 T-Codes & I am supposed to Pick all the Default Values for all the T-Codes.
    I am doing it from T-Code: SU24 & Updating it in Excel. My Question's are
    1. How to get more Knowledge on the Tcodes
    2. How it will Function
    3. In what way we can restrict the Feild values & Activities for the T-codes.
    My functional team Have no Knowledge on this Objects & what activities should be there.
    Now i need to explain them each & every T-Code & what does each feild & Activity Do. If there is any Go-Live document for this it will be really helpful for me.
    For All 30 T-codes I need to create Custom Roles &  Audit need's No Astrick for new custom Roles.
    Vijay

  • 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,
    <b>See the following links first:</b>
    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
    <b>BASICS OF BCS:</b>
    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.
    <b>check these links also:</b>
    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

  • SEM BCS - Step for Load from Datastream

    Hi,
    What are steps to configuration "Load from DataStream".
    What kind of infocube that i should use?
    Thanks in advance.

    Hi,
    There are rather lot threads reg the issue.
    For example:
    Re: BCS configuration
    Re: How is data loaded into the BCS cubes?
    Re: Which info object should be used for Financial statement line (BPS and BCS)
    Re: SEM-BCS: Load from data stream
    Feel free to ask if something is not clear.

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

Maybe you are looking for