Characteristics _organisational structure

hi there..
please let me know if my understanding is correct about the characteristics for which we can generate internal balance sheet and profit and loss statement.
1) with Classic GL is it only Business Area for which internal b/s and p&l can be created.
2) with New GL in addition to Business Area , internal balance sheet and profit and loss statement can be created for a)profit center and b) segment.
thank you,
V

Hi,
Both are possible except that Segment reporting was not there in 4.7
In 4.7 the balance sheet for Profit Center could only be prepared at month end after passing the data to Profit center accounting.
But in ECC 6 with New GL that is done in real time.
The moment you post the data Profit center accounting is updated and Statement of accounts can be taken any time.

Similar Messages

  • Info on CCM 2.0 characteristics - Fields length, data types & Desc

    Dear All,
    Does anybody know how or where I can get information about CCM 2.0 standard characteristics data structure?
    Or maybe the table name that holds this information?
    I need the following info:
    1. List of all Standard CCM 2.0 Characteristics
    2. Characteristics Data types (i.e Char)
    3. Characteristice Field lengths
    I have looked into the SAP help for CCM 2.o and the on SAP Servicemarketplace under instguides&IBC....could not find every thing I wanted.
    Regards,
    Grace

    Hi Grace,
    you can look in tables
    /CCM/C_CHAR
    /CCM/C_CHAR_ALS
    /CCM/C_CHAR_ASPT
    /CCM/C_CHAR_TXT
    /CCM/C_CHR_ALIAS
    and
    /CCM/C_DTYPE
    /CCM/C_DTYPE_HDR
    /CCM/C_DTYPE_T
    /CCM/C_DTYPE_TXT
    /CCM/C_DTYPE_VL
    /CCM/C_DTYPE_VLT
    in CCM to get the standard charcateristics and their default settings.
    Chris

  • Webi: unwanted zero rows suppression on BEx selection structure

    Hello,
    I have a Webi report/universe based on a BEx query having 2 structures: keyfigures in columns, characteristics selection structure in rows. We are still using BO XI 3.1 SP1.
    Now: the webi report suppresses the zero rows of the char structure, but we do not want that. in the bex query, there is no active zero rows suppression.
    I read in a similar thread about the opposite and that it will be fixed with XI 3.1 SP3:
    Re: Zero Rows suppression is not working in Webi report.
    Question: does anyone know, if "my" case is also solved by SP3? or anyone knows a workaround?
    Unfortunately the PDFs XI31_SP3_Fixed_Issues_1of2.pdf and XI31_SP3_Fixed_Issues_2of2.pdf of SAP note 1457545 contain no information about this point.
    Thanks and regards,
    Phil

    Hi Ingo,
    thanks for the workaround tip!
    In BEx query I tried with a calculated keyfigure set to "1" and alternatively with a restricted keyfigure set to "constant selection". Unfortunately, both did not work, the webi report was clocking long after the bex process was finished in BW.
    Then I got error WIS 30284 ( universe connection corrupt) and 30285 (no free memory). But maybe we just have an issue with webi server performance.
    anyway, thanks!
    Best regards,
    Phil
    Edited by: Phil on Jun 23, 2010 10:42 AM

  • Error message "Maximum number of drilldown characteristics exceeded"

    Hello,
    an user created a Web report. In the navigation block there are nearly 100 selection fields. If you make either "drilldown in the rows" or "drilldown in the columns" you recieve after 50 drilldowns the error message "Maximum number of drilldown characteristics exceeded" and it is not possible to proceed further. Does anybody has got an idea what this can be?
    Thanks!
    Regards,
    Christian

    Hi Check SAP Note No -
    Note 144478 - BEx: Termination/Message at 10th/20th drilldown characterstc
    1. Terminations occur when you drill down a large number of characteristics at the same time during interactive navigation in the Business Explorer Analyzer (Excel).
    2. In the global query definition, the system displays message 'Termination: the maximum number (10/20) of drilldown characteristics is exceeded' if the total of the characteristics and structures you are using exceeds
                  - 10 objects in Release 1.2B
                  - 20 objects in Release 2.0A/2.0B/2. 1C
                  during the definition of a query.
    Hope it helps
    regards
    Vikash

  • Portfolio analyzer-  No active analysis structure available

    Hi experts,
    We are planning to use portfolio analyzer. but i m getting an error "No active analysis structure available".
    I want to maintain this setting in config. but i m not having a clear understanding of this please help and suggest.
    Query 1.
    SPRO -> Financial Supply Chain Management -> Treasury and Risk Management -> Basic Analyzer Settings -> Reporting Characteristics -> Copy Sample Customizing Settings -> Analysis Characteristics and Structure: Activate Sample Sett
    in this link i have found 2 things
    a.  create charactersis  - i have run this and it s showing that "Characteristic WY....... already existed and was not changed"
    b. create chrachtersis and analysis structure  and in this config it is demanding  name of analysis structure..
        Please suggest which analysis structure wh should maintain here.
        is any structure provided by SAP ? or it is user defined filed ?
    Query 2.
    SPRO -> Financial Supply Chain Management -> Treasury and Risk Management -> Basic Analyzer Settings -> Reporting Characteristics -> Copy Sample Customizing Settings -> Analysis Structure: Copy Customizing from Sample Settings
    what is the use of above link.
    Thanks
    Gaurav Gupta

    Hi Gaurav,
    To activate analysis structure you can use the transaction AFWA.
    And then you have to run the transaction JBRGE and select all the checkboxes to recreate the environment.
    Regards,
    Sumant

  • Error while running wad report in portal

    Hi,
    when we try to run report from portal we get the following error
    " Label has specified invalid InfoObject = '0RPM_IHGU__0RPM_PFGU' "
    On double clicking i get the following :
    Diagnosis
    You have assigned an invalid attribute IOBJNM to the label. You cannot drag text to this InfoObject. The invalid value is 0RPM_IHGU__0RPM_PFGU
    System Response
    Procedure
    Assign a valid InfoObject to the Web item in the Web Application Designer, or override the specification in the Web template by assigning a valid value assignment to the parameter IOBJNM. All characteristics and structures are valid that are available in the query from which the query view obtains its data.
    Procedure for System Administration
      Notification Number RSR_WWW 101 
    The link will be calling 1 business content web template.
    It was working fine in Development system. We faced this problem after transporting to quality.
    Please provide pointers to resolve this error.
    Thanks & Regards,
    Rathy

    Hi,
    The system is unable to identify the InfoObject which has been assigned to the Web Item,
    Check if the InfoObject has been deactivated or is still available in the Query, the object seems to be a Navigational Attribute also check if anybody has changed the setting of the object to some thing else say display.  I get this message very often in development because of specifying wrong Structure Element to the IOBJNM
    Cheers.
    Ranga.

  • Short Dump ASSIGN_TYPE_CONFLICT in Virtual KF implementation

    Hi
    Iam getting a short dump in my virtual KF code. Here is the code that I have written. If I have only bill date it works fine. The minute I add company code it gives the short dump. Can you pls let me know what is it that Iam doing wrong. any help will be greatly useful. Thanks.
    INCLUDE ZXRSRU02
    DATA: L_S_CHANM TYPE RRKE_S_CHANM.
    DATA: L_SUBRC1 TYPE SY-SUBRC. "execute only, if key figure really used
    CASE I_S_RKB1D-INFOCUBE.
       WHEN '0SD_C03'.
                L_S_CHANM-CHANM = '0BILL_DATE'.
                L_S_CHANM-MODE  =  RRKE_C_MODE-READ.
                APPEND L_S_CHANM TO E_T_CHANM.
                L_S_CHANM-CHANM = '0COMP_CODE'.
                L_S_CHANM-MODE = RRKE_C_MODE-READ.
                APPEND L_S_CHANM TO E_T_CHANM.
                APPEND 'ZCOUNT1' TO E_T_KYFNM.
    ENDCASE.
    *Include ZXRSRTOP*
    DATA : G_POS_0SD_C03_0BILL_DATE TYPE I.
    DATA : G_POS_0SD_C03_0COMP_CODE(4).
    DATA : G_POS_0SD_C03_ZCOUNT1 TYPE I.
    Include ZXRSRZZZ
    FORM USER_0SD_C03 USING I_S_RKB1D TYPE RSR_S_RKB1D
      CHANGING C_S_DATA TYPE ANY.
      DATA: l_zcount1 TYPE int4.
      FIELD-SYMBOLS <L_0BILL_DATE>.
      FIELD-SYMBOLS <L_0COMP_CODE>.
      FIELD-SYMBOLS <L_ZCOUNT1>.
      ASSIGN COMPONENT G_POS_0SD_C03_0BILL_DATE
      OF STRUCTURE C_S_DATA TO <L_0BILL_DATE>.
      ASSIGN COMPONENT G_POS_0SD_C03_0COMP_CODE
      OF STRUCTURE C_S_DATA TO <L_0COMP_CODE>.
      ASSIGN COMPONENT G_POS_0SD_C03_ZCOUNT1
      OF STRUCTURE C_S_DATA TO <L_ZCOUNT1>.
      IF <L_0COMP_CODE> = 'AB99'.
        CALL FUNCTION 'ZCALC_WDAYS_BETWEEN_DATES'
          EXPORTING
            P_DATE1  = <L_0BILL_DATE>
            P_DATE2  = SY-DATUM
            P_CAL_ID = 'Z1'
          IMPORTING
            P_DAYS   = l_zcount1.
        <L_ZCOUNT1> = l_zcount1.
      ELSEIF <L_0COMP_CODE> = 'DC99'.
        CALL FUNCTION 'ZCALC_WDAYS_BETWEEN_DATES'
          EXPORTING
            P_DATE1  = <L_0BILL_DATE>
            P_DATE2  = SY-DATUM
            P_CAL_ID = 'Z2'
          IMPORTING
            P_DAYS   = l_zcount1.
        <L_ZCOUNT1> = l_zcount1.
      ENDIF.
    The short dump:
    ASSIGN_TYPE_CONFLICT
    "CL_IM_RSR_OLAP_BADI===========CP" or "CL_IM_RSR_OLAP_BADI===========CM002"
    "IF_EX_RSR_OLAP_BADI~INITIALIZE"
    get field postions for characteristics in structure
    LOOP AT i_th_sfc ASSIGNING <l_s_sfc>
         WHERE user_exit NE rrke_c_mode-none.
    field name in structure is keyreturnnm
    name of the global variable
      CONCATENATE '(SAPLXRSR)G_POS' i_s_rkb1d-infocube <l_s_sfc>-chanm
          INTO l_global_name
          SEPARATED BY '_'.
    fill the global variable
      UNASSIGN <l_global>.
    >>>>>>>>  ASSIGN (l_global_name) TO <l_global>.

    My suggestion is that you review the how-to papers on SDN regarding exit RSR00002 or RSR_OLAP_BADI.  These are alternative methods of accomplishing virtual characteristics and key figures.  The code you have given is for exit RSR00002 (although it is full of syntax errors so is not executable), but the short dump you are getting refers to RSR_OLAP_BADI, so you must have implemented that Class as well, but incompletely. 
    Which method are you attempting to use?

  • Restricted Key Figure and : Change Variable in WAD

    Hi everybody,
    I have a restricted key figure in my query, which is restricting all sales volumes of a product by time variable.
    I am using this restricted key figure instead of a real filter on the whole query because I have to view the total volume of this product and the volume in this year.
    This works very well, but I have no possibility to change the value of the time variable in the restricted key figure in WAD by a generic navigation block.
    How can i do this?
    Thanks,
    Alex

    Hi...
    The Web item Generic Navigation Block displays the navigational state of a query view in the Web application in the form of a table. All characteristics and structures in the query view are listed in the table and their filter values are displayed. You can change the navigational status of the query view. You can filter according to single values and remove the filter again.
    You want to see the results in tabular form and to be able to navigate
    through those results using key figures and characteristics.
    1. From the Start menu, open the Web Application Designer and start the Web
    Application Wizard
    a) Choose Start &#8594; Programs &#8594; Business Explorer &#8594; Web Application
    Designer &#8594; Tools &#8594; Wizard.
    Choose Next to skip the start page.
    2. Select the Generic Navigation Block item and accept the default settings for
    this item.
    a) In the Select Web Item dialog box, choose Standard Items &#8594; Generic
    Navigation Block, then select Next to transfer the item into your Web
    template.
    3. Assign the query Customers/Sales  as a Data Provider
    to the Generic Navigation Block web item. After assigning the Data Provider,
    accept the default values for the item attributes.
    a) Choose Query.
    b) The Open Query / View dialog box appears.
    From the Roles, select the query for Reporting&#8594; Unit: BEx
    Web Application Designer &#8594; Lesson: BEx Web Application Wizard &#8594;
    Exercise &#8594; Customers/Sales .
    Choose OK. The dialog box closes and you return to the Web application
    Wizard. Choose Next to reach the Edit Attributes dialog box. Since you
    want to accept the default properties of the item, choose Next.
    c) In the Overview dialog box, you see all the items you have selected so far.
    Add the Table Web item to your Web template and accept the suggested settings
    for this item.
    a) In the Overview dialog box, choose Add Item to add an additional item to
    your Web template. In the Select Web Item dialog box, select Standard
    Item &#8594; Table.
    Choose Next in order to transfer the item into your Web template.
    5. Assign the same Data Provider to this item as you did for the Navigation Block.
    Accept all the default settings for this item. Arrange the Web template to have
    the Generic Navigation Block before the Table.
    a) Both items in the Web template use the same Data Provider. Therefore, you
    can use the same entries for this item. Choose Next.
    b) Leave the properties of the table item unchanged. Skip over the Edit
    Attributes dialog box by choosing Next.
    c) Both Web items now appear in the Overview dialog box. Change the
    sequence of the two web items so that the Web template starts with the
    Generic Navigation Block. Use the up and down arrow icons to move your
    web items. Choose Next.
    6. Save the Web template.
    a) You do not have to make any entries in the Save Web Template dialog box.
    Choose Save to save your Web template.
    Save the newly-created Web template in your Favorites.
    give Description: ..................
    give Technical name: ...........
    7. Display the Web template in the browser.
    a) Choose Display theWeb template in theWeb browser .
    8. Exit the Web Application Wizard.
    a) Choose Exit. The Wizard window closes and the Web template is opened
    in the Web Application Designer where you can make additional edits
    as required.
    with regards,
    hari kv

  • 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

  • Generic navigation block,Hierarchy filter selection and Filter

    Hi all,
    Could any one explains what is the difference between a filter and Generic navitgation block & a filter and Hierarchy filters.
             How the filters in web reports differs the filters in queries.
    Regards,
    Preetham

    Hi,
    Filters:
    In your Web application, you can select filter values for characteristics and structures. The Web application is then filtered according to these selected values.
    Generic Navigation Block:
    The Web item Generic Navigation Block displays the navigational state of a query view in the Web application in the form of a table. All characteristics and structures in the query view are listed in the table and their filter values are displayed. You can change the navigational status of the query view. You can transfer characteristics and structures to an axis (rows or columns) or from an axis. You can filter according to single values and remove the filter again.
    Hierarchy Filter:
    You can search through leaves and nodes in the hierarchies of your Web application.
    Seen this?:
    http://help.sap.com/saphelp_nw04/helpdata/en/70/4c7ead79eaf0498afa31528072900d/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/35/a5507170d8c548a25e4e532f3917a3/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/35/a5507170d8c548a25e4e532f3917a3/frameset.htm
    assign points if useful ***
    Thanks,
    Raj

  • BADI for Virtual Characteristic

    Hi,
    I am able to use BADI to populate Virtual Key Figure, but getting an error when I use similar code for Virtual Char.
    Following are the details
    Characteristic InfoObjects IO_MATRAL, IO_PLANT, IO_CMATRL (virtual char)
    I want to assign the value of IO_MATRAL to IO_CMATRAL using BADI.
    Attributes are
    P_CHA_IO_CMATRL  associated type I (level: instance, visibility: private)
    P_CHA_IO_MATRL   associated type I (level: instance, visibility: private)
    DEFINE method
    method IF_EX_RSR_OLAP_BADI~DEFINE.
      DATA: l_s_chanm   TYPE rrke_s_chanm,
            l_kyfnm     TYPE rsd_kyfnm.
      FIELD-SYMBOLS:
            <l_s_chanm> TYPE rrke_s_chanm.
    CASE i_s_rkb1d-infocube.
       WHEN 'IC_SEKH'.
        l_s_chanm-chanm = 'IO_MATRL'.
        l_s_chanm-mode = rrke_c_mode-read.
        APPEND l_s_chanm TO c_t_chanm.
        l_s_chanm-chanm = 'IO_CMATRL'.
        l_s_chanm-mode = rrke_c_mode-read.
        APPEND l_s_chanm TO c_t_chanm.
    ENDCASE.
    ENDMETHOD.                    "if_ex_rsr_olap_badi~define
    INITIALIZE method
    method IF_EX_RSR_OLAP_BADI~INITIALIZE.
      DATA: l_global_name TYPE string.
      FIELD-SYMBOLS:
            <l_global>    TYPE i,
            <l_s_sfc>     TYPE rrkg_s_sfc,
            <l_s_sfk>     TYPE rrkg_s_sfk.
    there's no need to change this method
    Just create attributes for each charactersitic
    with name P_CHA_<characteristic> TYPE i.
    and constants for each key figure with name
    P_KYF_<key figure> TYPE i.
      CLASS cl_exm_im_rsr_olap_badi DEFINITION LOAD.
    get field postions for characteristics in structure
      LOOP AT i_th_sfc ASSIGNING <l_s_sfc>
           WHERE user_exit NE rrke_c_mode-none.
    field name in structure is keyreturnnm
    name of the global variable
        CONCATENATE 'P_CHA' <l_s_sfc>-chanm
            INTO l_global_name
            SEPARATED BY '_'.
    fill the global variable
        UNASSIGN <l_global>.
        ASSIGN (l_global_name) TO <l_global>.
        CHECK <l_global> IS ASSIGNED.
        <l_global> = cl_exm_im_rsr_olap_badi=>get_field_position_d(
                                           i_fieldnm = <l_s_sfc>-keyreturnnm
                                           i_s_data  = i_s_data ).
      ENDLOOP.
    endmethod.
    COMPUTE method
    method IF_EX_RSR_OLAP_BADI~COMPUTE.
      FIELD-SYMBOLS: <fs_io_cmatrl>   TYPE ANY,
                     <fs_io_matrl>    TYPE ANY.
      ASSIGN COMPONENT p_cha_io_matrl  OF STRUCTURE c_s_data TO <fs_io_matrl>.
      ASSIGN COMPONENT p_cha_io_cmatrl OF STRUCTURE c_s_data TO <fs_io_cmatrl>.
      <fs_io_cmatrl> = <fs_io_matrl>.
    endmethod.
    I am not getting any value in IO_CMATRL in the query.
    Even when I assign hardcoded value like 's', in compute method, it's not showing the value in the query result.
    Can you guys please suggest what am I missing here? (similar code works for Virtual keyFig. implementation)
    Thank you,
    Lakshmi

    Hi,
    In DEFINE Method
    l_s_chanm-chanm = 'IO_MATRL'.
    l_s_chanm-mode = rrke_c_mode-read.
    APPEND l_s_chanm TO c_t_chanm.
    l_s_chanm-chanm = 'IO_CMATRL'.
    l_s_chanm-mode = rrke_c_mode-read.
    APPEND l_s_chanm TO c_t_chanm.
    If u2018IO_CMATRLu2019 is your virtual characteristic u2026try changing the read mode to  rrke_c_mode-no_selection
    Thanks,
    Advait

  • RSR_OLAP_BADI -  initialization method

    We have created an  implementation using the RSR_OLAP_BADI. In the INITIALIZATION METHOD we are using the code shown below from one of the white papers. The code goes through the characteristics and key figures and finds there position in the table. That position is used in an ASSIGN statement in the COMPUTE METHOD so we can put a value in our virtual key figures. The code for characteristics works fine but the code for key figures does not.
    What we found in debug is that field VALUE_RETURNNM in  table I_TH_SFK does not contain a value for any of our key figures.
    Does anyone know how or where the table I_T_SFK is filled?
    Regards,
    Mike...
    **CODE:
    class cl_exm_im_rsr_olap_badi definition load.
    get field postions for characteristics in structure
      loop at i_th_sfc assigning <l_s_sfc>
      where user_exit ne rrke_c_mode-none.
    field name in structure is keyreturnnm
    name of the global variable
        concatenate 'P_CHA' <l_s_sfc>-chanm
            into l_global_name separated by '_'.
    fill the global variable
        unassign <l_global>.
        assign (l_global_name) to <l_global>.
        check <l_global> is assigned.
        <l_global> = cl_exm_im_rsr_olap_badi=>get_field_position_d(
        i_fieldnm = <l_s_sfc>-keyreturnnm
        i_s_data = i_s_data ).
      endloop.
    get field positions for key figures in structure
    loop at i_th_sfk assigning <l_s_sfk>
           where value_returnnm is not initial.
    name of the global variable
        concatenate 'P_KYF' <l_s_sfk>-kyfnm
            into l_global_name
            separated by '_'.
    fill the global variable
        unassign <l_global>.
        assign (l_global_name) to <l_global>.
        check <l_global> is assigned.
        <l_global> = cl_exm_im_rsr_olap_badi=>get_field_position_d(
                                           i_fieldnm = <l_s_sfk>-value_returnnm
                                           i_s_data  = i_s_data ).
      endloop.

    Fred,
    The reference to VALUE_RETURNNM is in the LOOP for Key Figures
    in methond INITIALIZE.
    get field positions for key figures in structure
    loop at i_th_sfk assigning <l_s_sfk>
    where value_returnnm is not initial.
    name of the global variable
    concatenate 'P_KYF' <l_s_sfk>-kyfnm
    into l_global_name
    separated by '_'.
    fill the global variable
    unassign <l_global>.
    assign (l_global_name) to <l_global>.
    check <l_global> is assigned.
    <l_global> = cl_exm_im_rsr_olap_badi=>get_field_position_d(
    i_fieldnm = <l_s_sfk>-value_returnnmi_s_data = i_s_data ).
    endloop.

  • ECCS - Adding Profit Center to Company Code Consolidation

    Hello Gurus,
    We use ECCS for our consolidation. We do only Legal consolidation and we also use Functional Area as a sub-item category for all the IS accounts. We are now trying to add Profit Center as one of the attributes. Initially, we planned to use the sub-item category, however, we can have only one and it's already taken by Functional Area. Is there a way I can
    1. Add PC as an attribute
    2. Enhance ECMCT to allow additional Sub-item?
    Appreciate your advice and guidance.
    Regards,
    Venkat

    The documentation at the menu path: t-code SPRO > Enterprise Controlling > Consolidation > Add Characteristics states:
    Add Characteristics
    The SAP standard consolidation database includes various preset characteristics, such as the consolidation unit, the financial statement (FS) item, the subitem, etc. If the information requirements of your group demand additional fields, you can define your own socalled custom characteristics.
    This step shows you two ways to add characteristics to the consolidation database:
    You can add up to five subassignments to the FS item.
    You can add navigation attributes to the characteristic consolidation unit. The system then automatically assigns the same attribute to the characteristics partner unit and investee unit as well.
    After adding a characteristic, the system generates the associated ABAP Dictionary objects and maintenance views.
    To the consolidation database, you can also add characteristics based on structures that already exist in the SAP system (e.g. Region). However, you can also add characteristics, the structures of which still need to be generated.
    Recommendation
    Since custom characteristics extend the consolidation database, you should carefully examine which characteristics are to be added. SAP recommends, in particular, that you first finish creating the new characteristics, and that you make sure that want to use this set of data, before you activate the new characteristics and start the generation. This way you can avoid time-consuming deletions if a characteristic must be removed. Also, keep in mind that you can no longer delete a characteristic once you have posted data with the characteristic.
    Example
    Examples of subassignments for FS items are the Product Group and the Geographic Region.
    An example of an attribute for consolidation units is the Company Type.
    Standard settings
    The standard SAP system already includes the following subassignments for FS items:
    Partner unit
    Subitem category and subitem
    Transaction currency
    Acquisition year
    Acquisition period
    Unit of measure
    The standard SAP system already includes the following attributes for the consolidation unit:
    Country
    Company
    Consolidation business area
    Profit center
    Controlling area
    The attributes company, cons business area, profit center and controlling area are particularly useful when you use the integrated collection of reported financial data from your consolidation units.
    Activities
    1. Reorganize the field catalog. When this is done, the system copies the system field catalog into the customer field catalog. Choose Extras -> Field catalog -> Reorganize.
    If you use integrated collection of reported data, during the reorganization you should include SAP's standard attributes in the selection. Note that, initially, these attributes are not included in the Reorganization selection screen.
    2. If desired, create one or more new characteristics.
    Enter the technical name (field name) of the new characteristic. The technical name must begin with the letters "ZZ".
    Also set the appropriate indicator to define how the structure of the characteristic is to be built.
    Technical Background Information:
    Description, type, and length are properties of characteristics that you can enter directly or define by assigning a data element or domain. Data elements and domains are ABAP Dictionary objects that act as a central store of table field properties:
    A data element defines the meaning of a field in business terms with texts and a reference to a domain.
    A domain describes the technical properties of the field and defines permissible values for the characteristic if either of the following conditions is met:
    - There is a list defining fixed values
    - There is a reference to a check table
    Normally data element and domain assignments are used to refer to check tables. You can, however, create a characteristic without any validation or texts by assigning a standard domain (for example CHAR07, NUM12).
    Ways to create a characteristic:
    a) Assigning a data element
    Activate this indicator and assign a data element. The domain assignment is made by assigning the data element.
    Note: If you run the elimination of IU profit/loss in transferred inventory and the system reads the required additional financial data from the totals database, you need to create the characteristic "product group" and assign it to data element FC_PRGRP.
    b) Assigning a domain
    Activate this indicator, then specify the meaning and assign a domain. By assigning a domain you define the type and length of the characteristic, and possibly you refer to fixed values or a check table.
    c) Referencing a characteristic
    Activate this indicator, then specify the description and set a reference to another characteristic. This has the effect of assigning the domain of the referenced characteristic.
    d) Creating a characteristic with a new data element and check table
    Activate this indicator, the specify the description, type (character or numeric), and length (1-32). The system generates a new check table for the characteristic.
    e) Creating a characteristic without a check table (using a standard domain)
    Activate this indicator and specify the description, type (character or numeric), and length (1-32). The system does not generate a check table.
    Caution: Assigning data elements or domains does not itself ensure that validation, reading characteristic value texts, and Possible Entries Help will work as expected. The following conditions must be given:
    The domain must have a check table or fixed values.
    There must be either a text table with references to the check table, or the texts must be in the check table itself.
    These conditions are always fulfilled by fields in the standard field catalog.
    3. If needed, define compound relationships between characteristics in the detail screen of Characteristic Maintenance.
    Some characteristics are dependent on other characteristics; that is, the values of dependent characteristics are meaningless in theabsence of values for independent characteristics. Such a relationship is called a characteristic compound. Technically, a check table then contains a key that consists of two parts.
    Example: The Region, a dependent characteristic (check table T005S), forms a compound characteristic with the Country, an independent characteristic, because a region can be maintained or interpreted only if a country is specified.
    Note the following restrictions when defining compounds:
    Compounds can only be defined for characteristics that have a check table.
    When a data element/domain is assigned, a compound is predefined by the existing check table.
    Compounds can only be defined while creating a dependent characteristic. You do this by specifying the independent characteristic in the detail screen.
    Only single compounds are permitted. Multiple compounds cannot be made.
    The compound must be defined while creating a new characteristic, and before the new characteristic is saved. This is because the save process generates the check table for the characteristic.
    Note: You do not use characteristic compounds to create regular assignments between two fields (such as, consolidation unit A having the local currency USD). Rather, a compound characteristic describes the structural dependency of one field on another (as in FS item 1111 in cons chart of accounts 01 being a different item than FS item 1111 in cons chart of accounts 02).
    4. Specify further properties of the characteristic:
    Define the display options and the sequence number of the characteristic for reports and so forth.
    Activate the Subassignment indicator for all characteristics used as subassignments for FS items.
    Activate the Fixed value in breakdown category indicator for all subassignments whose value is determined by the breakdown category (e.g., as with the characteristic subitem category).
    Activate the Default value indicator if applicable. Then the characteristic appears in the implementation step Define Default Values. A default value is not necessary and cannot be set if you activate the Fixed value in breakdown category indicator
    5. Enhance the checking specifications if needed:
    For characteristics without a standard check table, you can enter a text table, a text field, and a long text field. The text fields must use the field type character. You can also specify a view name, usually a view of the check table and text table.
    If the system fails to automatically determine the transaction codes for displaying and changing the master data, you can specify them manually.
    6. To the characteristic consolidation unit assign any newly created characteristics as an attribute. Only independent characteristics can be assigned as attributes to consolidation units.
    These attributes are used for sorting your consolidation units.
    Note: Prerequisite for assigning attributes is the reorganization of the field catalog, that is, you need to have copied the field catalog into the customer field catalog. To do this, choose Extras -> Field catalog -> Reorganize.
    7. Save and activate the new characteristic.
    The Save process stores the new data and, if applicable, creates new tables and views in the ABAP Dictionary.
    The Activation process sets the status of the tables, views, data elements, etc. to "active". It also generates the objects that are necessary to enable the consolidation functions to process the new characteristics.
    You can activate several characteristics in one step by choosing characteristic maintenance of all characteristics in the initial screen, selecting and activating the inactive characteristics.
    8. After activating the characteristic, you are asked whether to generate the view modules. Confirm the generation.
    If you exit Characteristic Maintenance and want to ensure that all view modules were generated correctly, choose Environment -> View maintenance modules -> Reorganize.
    9. Assign the new characteristics to field groups, if applicable.
    Field groups are groupings of characteristics. These let you structure the fields in the field catalog. Individual fields may belong to multiple field groups.
    Further notes
    Choose Extras -> Log display to display the logs for the activities Save, Activate and Delete.
    Edited by: Dan Sullivan on Oct 6, 2011 9:38 AM

  • 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

  • BI Developer duties in a project

    Hi,
    Can anyone please tell me the real time flow in SAP BI Project like the duties of BI Developer.
    And after developing the queries how will we deliver the reports the clients.
    Regards,
    Kumar

    Hi, here while speaking of SAP BI developer we need to recognize either it is BW backend or frontend developer.
    I believe you are more interesting in frontend = report developing. Developer is developing BW queries according technical (or just functional) design document. So he is really developing all of elements for (variables, calculated/restricted key figures, restricted characteristics, global structures, formulas, etc) BW queries in tool called BEx Query Designer. This is happening in usually in so called development system. Elements of queries and query it self are being transported form development to test (finally to production) system by SAP Transport Management System (STMS) which is tool provided by SAP for transporting objects across system landscape.

Maybe you are looking for