Multiple Keyfigures in BPC

Hi,
Is there a way to handle multiple keyfigures in BPC in one application?
Please help me understand
Thanks

Navin,
in SAP BW there r 2 main approaches in modilling infocubes:
1. Account Model
2. Keyfigure Model
Account model as u know is an approach when there is only 1 keyfigure in a cube.
Keyfigure model is as approach to create multiple keyfigures in a cube.
In different situations it might be useful to implement 1 or another approach. SAP BPC automatically creates cubes with only 1 keyfigure and there is no possibility to create standart multiple keyfigures via frontend.
Hope that info will be useful for u,
Dzmitry

Similar Messages

  • How to handle Multiple Keyfigures in BPC

    Hi,
    My BW cube is Keyfigure based, have 0quantity and 0amount. BPC cube is Account based it just has only one keyfigure,however there is a way to post multiple keyfigures to BPC by using MVAL keyword. Not sure how I can use this. Can someone throw more inputs on this.
    Appreciate for your help.
    Thanks,
    Vara

    Surya - Is it really requred to ADD new dimension? May be,  but better to understand the req and provide advise.
    Let us analyze a simple scenario:
    Example: BW Cube data          
    GL ACOOUNT     0AMOUNT     0QUANTITY
    Sales                              500             50
    Material Cost                              200             20
    Labor Cost                              150     
    Reneeth's Solution: Creating New Dimenstion          
    ACCOUNT         ZKEYFIGURE     signdata
    Sales         ZAMOUNT                           500
    sales         ZQUANTITY        50
    Material Cost         ZAMOUNT                           200
    Material Cost         ZQUANTITY        20
    Labor Cost         ZAMOUNT                           150
    My Advise: Manage with Existing "ACCOUNT" Dimension. rather adding a new dimension. 
    ACCOUNT                       Signdata     
    Sales.Amount     500     
    Sales.Quantity     50     
    Material Cost.Amount     200     
    Material Cost.Quantity     20     
    Labor Cost                         150     
    Having more dimensions, in my opinion is addl pain while creating reports and Input Templates.
    Thanks

  • How to Maintain multiple keyfigures in BPC

    Hi,
    I'm trying to re-produce a IP Planning scenario in BPC. We have a cube with multiple different keyfigures(ex: A,B,C)
    When we are creating application in applicationset we can create all characteristics of BI cube(IP Scenario) as dimensions in BPC then how can we handle keyfigures of BI Cube(IP Scenario) in BPC?
    I heared BPC will support only single keyfigure(Signeddata) but my scenario is not suitable for account base model in BI.
    BI Cube contains multiple keyfigures(ex:A,B.C)
    Please advice on the model to acheive in BPC as i',m new to BPC.

    Hi,
    Post the thread on the forum:
    SAP Planning and Consolidation, version for the Microsoft platform
    SAP Planning and Consolidation, version for SAP NetWeaver
    It's not the correct forum ,there is separate forum for BPC microsoft,NetWeaver 
    Regards,
    Indu
    Edited by: Indu Sharma on Jan 20, 2010 8:31 AM

  • Multiple keyfigure from different planning area based on attribute value

    Multiple keyfigure from different planning area based on the attribute value of Cost element charac.
    I need to obtain the value of the attribute in a fox function. Let me explain it further.
    Background :
    Planning area -
    Charac----
    KF
    area1 -
    Payscale group--- Amount
    Cost element------AmountVR
    area2--Payscalegroup----KF1
    KF2
    KF3
    Cost Element has an attribute "Type"
    Value for attribute "Type" = 1,2,3
    Based on the value of the attribute, the corresponding KF needs to be multiplied.
    Logic :
    If type = 1.
    AmountVR = Amount * KF1.
    elseif type = 2.
    AmountVR = Amount * KF2.
    elseif type = 3.
    AmountVR = Amount * KF3.
    endif.
    The problem I'm facing is that I'm not able to read the data of attribute "Type". None of the below statement retrieve the value of the "Type".
    TYPE = ATRV(Attribute,COSTELEMENT,CO_AREA)
    or
    TYPE = ATRV(Attribute,COSTELEMENT)
    Could you please help me in reading from a time dependent compounding InfoObject?
    Regards,
    Raghu

    Hi..
    Thanx Bindu..
    I have actual data for Month days..if i am craeting in same layout it is too large.
    that's why i am creating two layouts.
    below example for better undersatnding.
    Actual:
    D1 :D2: D3  :D4 : D5  :D6 : D7   :  FULLACT (sume of C(1)  sum of d1 to d7))
    10  :8  :12 :  10 : 14   : 6  : 10    :  70     
    Plan:
    D1EST : D2EST: D3EST :D4EST :D5EST: D6EST: D7EST:  FULLEST (sum of d1 to d7)
    10         :10        :  10      :  10      :10       :    10    :     10  :         70
    How can i read FULLACT value and that value i have to distribute  equally in planing layout and always FULLEST is equal to FULLACT.if not equal i have to throug error message hoe can i setup if you have sample code can you send it to me.
    what is your idea....
    Edited by: Eyda rose on Jun 4, 2008 4:59 PM

  • Multiple KF in BPC

    Hello All,
    We have KF Model in BW  with four Kf's and now we want implement this design in Account based model in BPC.
    Based on scn threads...we have created user defined dimension ZKEFIGURE in BPC and assigned four KF's as members to ZKEFIGURE in BPC.
    And In Transfomation file we have coded it as
    ACCOUNT=0ACCOUNT
    BATCH=ZBATCH
    TIME=0FISCPER
    ENTITY=0COMP_CODE
    CATEGORY=*NEWCOL(PLAN)
    RPTCURRENCY=*NEWCOL(USD)
    ZKEYFIGURE=*MVAL(ZRETARTA1|*NEWCOL(ZRETARTA1)||ZRETARTQ1|*NEWCOL(ZRETARTQ1))
    Error:
    just saying : Command Error: Newcol(
    Validation with file failed.
    Could someone help us. Thanking you inadvance for your valuable time.

    Hi Das,
    Thanks for your time & support.
    Not Sure...How does it behave BPC 10NW Version ?
    But it works for me with the below code....and this happened after 'n' number of trails with the small changes in dimension members as well.
    ZKEYFIGURE=*MVAL(ZRETARTA1|*NEWCOL(AMOUNT)||ZRETARTQ1|*str(QUANTITY))
    I have seen many experts are saying *MVAL is only for Time Dimension and *MKEY is for Multiple KF's but in my case it works in reverse with *MVAL.
    As a BW consultant I am very new to BPC....... If you have any idea please let me know.

  • Can we enter data in multiple currencies in BPC

    Hi all,
    In BPC, is it possible to enter data in transaction currencies other than in local currency?  For example, if the local currency of an entity is USD, but I need to enter data for the same Accounts in EUR, MYR and SGD as well and not have the system translate the amount in local currency to EUR, MYR and SGD.
    Thanks.

    Hi Tara,
    Thanks for your response.
    There are several reasons why we might need to enter the data in various currencies other than the local currency.
    Firstly, like you have mentioned, we need to enter the local as well as the translated currency amounts for accounts that have to be translated at historical rates.  Examples of such accounts will be equity account as you have pointed out.  If I understand you correctly, you are saying that it is possible to enter an amount in translated currency in addition to entering the amount in local currency?
    Secondly, due to requirements of a relatively new accounting standard, companies need to quantify the sensitivity of any exposures to a foreign currency to foreign exchange rates changes. 
    For example, the local currency Entity A is USD and it has a bank deposit in SGD 200.  If the exchange rate at report date is USD 1 to SGD 2, the SGD bank deposit will be translated and reported as USD 100.  Accounting standard requires the company to quantify how much the company will stand to gain or lose if the foreign exchange goes up by 10% or goes down by 10%.
    Thirdly, accounting standard also dictates that company discloses exposures to all currencies for financial instruments not denominated in the functional currency of the entity.
    Regards

  • Customer Exit Variable in formula to get values for multiple keyfigures

    Hi to all,
    I have query as defined in following scenario:
    CHAR_X     C_KF1 (based on KF1)     C_KF2 (based on KF2)     u2026     C_KFn (based on KFn)
    Value1                    
    Value2                    
    u2026                    
    Valuem                    
    C_KF = calculated key figure
    I need to create a customer exit variable that will search through selection e.g. CHAR_X/KF1 and give some result. I need this variable for every keyfigure (KF1-KFn). Using customer exit variable is the only solution.
    My question is: do I have to create formula variable (customer exit) representing every keyfigure separately (VAR1 u2013 VARn, like in below example)?
    CHAR_X     C_KF1 (using VAR1)     C_KF2 (using VAR2)     u2026     C_KFn (using VARn)
    Value1                    
    Value2                    
    u2026                    
    Valuem                    
    Or is it possible to create one general formula variable since the way to retrieve the value in variable is always the same (like in below example)? In this case, how do I pass the value of the respective keyfigure to this variable?
    CHAR_X     C_KF1 (using VAR_X)     C_KF2 (using VAR_X)     u2026     C_KFn (using VAR_X)
    Value1                    
    Value2                    
    u2026                    
    Valuem                    
    Thanks for your replies, points will be awarded!
    Cheers

    That is my concern, the value of variable is not the same.
    What variable should do is:
    take KF1 id, go through values for CHAR_X, get back one value
    This value would always be different, and also "KF" part in code of variable should be different, based on the column where the variable is being used (so, in column C_KF1 ,variable should "pick up" id of KF1, etc.).
    I hope it makes it more clear. For now, I do not have the code for variable yet, I am just interested in concept whether it is possible to pass the ID of keyfigure dynamically so I can make decision how to model this request.
    Thanks

  • Multiple hierarchies in BPC

    If an has 3 hierarchies, which hierarchy will be shown in the Member selector dialog box  when we click on the dimension to select a different member for the current view?

    Hi,
    It is related or linked to your Security, if you have total access, you can see all the members of that particular dimension
    with the hierachies.  You have a radio button to choose " Hierarchy"  and "Table".  You choose according to your requirement.
    I hope this will help you.
    Regards,
    B.S.RAGHU

  • Multiple Key Figures and SINGEDATA

    Hi Experts,
    There are different Key Figures in BI like Amount, Quantity, Number, Integer, Date, Time, and the associated Unit. Whereas, in BPC there is only one type of object is used for recording quantitative values for transaction in BPC, that is SINGEDDATA. This object is equivalent to a Key Figure in SAP NetWeaver BI. So, while extracting data from BI to BPC, there are multiple Key Figures in BI, then how to take these multiple Key Figures in BPC? Do we need to take multiple SINGEDDATA?
    Appreciate your help.
    Thanks

    Hello Qakbar -
    The typical practice is to map each BW key figure to a combination of SIGNDATA and another dimension, such as ACCOUNT (or any combination of one or more dimensions).  BPC is a true account based data model (only one key figure).
    You can use BW transformations along with Rule Groups to define how each multiple key figure based BW record can be broken into separate single key figure records.  These records can be stored in a BW staging cube for easy import into BPC upon demand. 
    Alternatively, you could use the BPC transformation command, MVAL, to allow loading of multiple Keyfigure BW records directly into BPC.
    Regards,
    Sheldon

  • Zero value in Amount field during transaction upload into BPC

    Hi Experts,
    When I run DM package to load transaction data from BW to BPC,I am getting warning error with rejected list which contains amount field as zero value.
    Is it possible to load records with amount value as Zero.My current EPM version is 10 SP14 Patch 1.
    Currently my cube is in load mode .I have understood that during transaction data upload the cube should be in load mode and during inputting data using input forms it should be in planning mode.Please correct me if I am wrong.
    Thanks,
    Raju

    Thanks for your quick turn around.
    I have multiple keyfigures which have zero values in some records hence I am getting zero values in Amount field.
    Shall I mark Real-Time  data Target can be planned; data loading not allowed always.
    Regards,
    Venkat

  • Design studio with BPC

    Hello Experts,
    How can I connect Design Studio with BPC cubes. I am Using DS version 1.3
    I need to create Design studio with BPC data.
    Gone through some documents but couldn't find out the way to do this.
    Regards,
    LKumar

    Hi Kumar,
    I have implemented a design studio on top of a BPC model by enabling the "use a source of data" in the BPC Admin website - it creates a multiprovider (name /CPMB/xxx) and we can then create bex queries on top of it with some limitations (no currency convertion by eg.).
    Design studio is managing this query as a standard BEX query - Only to display data ...
    Regards,
    Thomas
    PS: Please pay attention with multiple systems as BPC objects can have different names when transported (attributes). All references of BPC objects in Design studio would be then incorrect.

  • KPI cockpit : modelling question

    Hi,
    We are making a KPI cockpit in the Visual Composer based on BW keyfigures. In our application we have 4 tables in which we show the keyfigures based on different queries. Thus in one table we show multiple keyfigures from multiple queries thanks to the "union" operator. In the first column we show the different keyfigures (from different queries), in the next colums we show the values and trends
    This is how one of our table looks
    Key figure     Value           Trend          Exception
    Net Value     100 €            Down         Red
    Weight         20 Kg           Up             Green
    Headcount   25                 Same         Yellow
    The keyfigures above originate from different queries (co-pa, hr,...)
    But, now we'd like to offer drilldown possibility from the tables to detail queries and/or webreports but our biggest problem is that the target report is fully dependend on the keyfigure row that is selected from the table. Is it possible to create a model in VC in which the target report choosen is dependend on a certain row that is selected in the table ?
    thanks for your feedback

    Hi Double U,
    I'm not sure whether I fully understood your problem. Getting a row index from a table is not possible (e.g. row 3 is selected). Still you can distinguish by using the table field "Key_figure" in guard conditions. I don't know how you plan to invoke your reports, but you might do the following. Drag four connectors from the out-port of your table. An event listener for the "select"-event should be generated automatically. For every connector you define a special guard condition. For example:
    "IF(@key_figure=="Net Value",true,false)"
    would be the guard condition on the connector to your Detail Report on Net Value.
    In case this is not what you plan to do, please provide us with more details.
    Best regards,
      Benni

  • Launch of new NW2004s-BI Frontend from transaction rrmx

    Hi,
    my customer has upggraded to NW2004s. <b>We are on Support Package 7. The NW2004s-BI Frontend is FEP701.</b>
    When I enter <b>transaction <rrmx> the "old" BW 3.5 Bex Frontend launches.</b>
    Is there a <b>way to have <rrmx> call the new NW2004s-BI frontend?</b>
    I have been toggling the "Launch Legacy Version from RRMX" flag on and off in the new NW2004s BI Frontend but nothing but the 3.5 Analyzer lauches?
    Can you help with that issue?
    Thanks
    Christian

    Hi Christian! in this reply you could find your solution.
    <u><b> but attached file is available only by OSS!
    If you think this helps, don't forget give me points!</b></u>
    <b>see note 933768</b>
    <i>Symptom
    Error in Business Explorer Components like Analyzer, Report Designer, Web Application Designer, Query Designer, Open/Save Dialog, Value Help Dialog
    Other terms
    Business Explorer, Frontend, BW, BI 7.0, BI, Hotfix, advance correction, Analyzer, Report Designer, Web Application Designer, Query Designer, Open/Save Dialog, Value Help Dialog, Selector, characteristic restriction, filter, filter value, variables
    Reason and Prerequisites
    You have installed NetWeaver 2004s BI Add-On Frontend Patch 700, and you need a hotfix (advance correction) for certain problems that are caused by the BI Add-On (frontend).
    This note will be updated as solutions for newly detected problems are available. Hence you should check the actuality of this note, if you have already applied hotfixes for the patch level of your BI Add-On.
    Solution
    Attached to this note you will find frontend components (DLL files) that correct certain errors. You will find a list and descriptions of solved problems in the following. It is recommended to replace all respective DLLs in the setup directory of the BI Add-On with the attached DLLs. However, you can also selectively replace individual DLLs that are required for the solution of problems that you encountered. In the following it is described which DLLs are required to solve specific problems.
    The Open/Save dialog and the Value Help dialog (selector) are components that are used by several SAP Business Explorer applications. Hence, if you encounter errors in one of those applications, please also check the dialogs sections below for a solution.
    SAP Business Explorer Web Application Designer
    SAP Business Explorer Analyzer and Variables Screen
    New property to adjust the size of the Drop-down item added.
    Known errors occuring, while entering the values in variable screen pop-up, have been corrected
    SAP Business Explorer Query Designer
    Corrected critical error at saving of reusable elements (especially evident with calculated key figures using variables). We strongly recommend to apply this hotfix.
    If a presentation hierarchy is selected for a drilldown, it is not possible any more to restrict the characteristic to a hierarchy node from another hierarchy.
    Refresh problem solved with repeated query execution in web browser.
    Dimension preview is enabled again and allows scrolling.
    Problems with query variable order presentation and editing are solved.
    Structure member selections using calculated key figures display further calcuated key figure properties.
    Error with characteristic value variables replaced by queries corrected.
    Errors with structure member descriptions corrected.
    There were too many characteristics offered as aggregation reference for formulas. Now only characteristics of the corresponding InfoProvider are listed.
    Paste of multiple characteristics when restricting structure member selections is working again.
    Error when creating structure member hierarchies with formulas is solved.
    Copy and paste of a structure member without changing the focus was not possible. This is now enabled.
    Variables could not be entered in the editors for conditions and exceptions. This is possible now. Also variables for key date can now be entered.
    Error when adding attributes by drag and drop corrected.
    Sorted display of query elements corrected.
    Paste of a second reusable structure enabled again.
    It is not allowed to restrict a structure member to a characteristic value if the other structure already contains a restriction of this characteristic. This check is now implemented.
    Sometimes values for Zero Suppression were not correctly saved. This is corrected now (updated 04 May 2006)
    Restricted and Calculated key figure folders did not display if the user started Query Designer more than once from Analyzer. (updated 04 May 2006)
    It was not possible to delete a Characteristic from filter if a reusable filter contained this characteristic (updated 04 May 2006)
    Paste of InfoObjects and reusable Elements was errorneously possible to Exception and Condition area. Is frobidden now. (updated 04 May 2006)
    Text variables with repalcement path are now always not inputable (updated 04 May 2006)
    Variables were not displayed correctly if the user started Query Designer more than once from Analyzer. (updated 04 May 2006)
    There could be a runtime error (occasionally) in Anaylzer after user selected "Exit and use query" in Query Designer due to a still processed error check. (updated 04 May 2006)
    There is now a check if a presentation hierarchy exists on server. If not, the user is informed by a warning (updated 04 May 2006)
    New warning informs user about non existing presentation hierarchies (updated 15 May 2006)
    Formula variables with replacement path "by attribute" offer now only numerical attributes. (updated 15 May 2006)
    Empty formulas now cause an error message, not just a warning message, because queries with empty formulas are not executable. (updated 15 May 2006)
    For compounded characteristics in InfoProvider tree the compound info was not displayed in all cases, this is corrected now (updated 15 May 2006)
    Variables replaced by query result or by a replacement table can be just used in Filter. The user is informed by an error message if such variables are used anywhere else (updated 15 May 2006).
    Queries with cell were sometimes saved with wrong coordinates for cells. Such queries are not executable. This is corrected now. Wrong queries are auto corrected, if they are loaded and saved with this corrected version (updated 15 May 2006).
    Problem with "hanging" explorer during execution of a query in web solved (updated 15 May 2006).
    Variable order setting is now also possible for new queries (updated 15 May 2006)
    Empty structures cause now an error message, not just a warning message, because queries with empty structures are not executable. (updated 15 May 2006)
    There were some cases where Text variables were not stred correctly and as a consequence not replaced. All known issues are now corrected. (updated 15 May 2006)
    With this hotfix the Note 948374 should be also implemented in the backend system, it prevents some save prolems.
    Small usability improvements in Varible-, Exception- and Condition editor (updated 23 May 2006)
    Multiple keyfigures are not allowed in Filter, but it was possible to do this with copy and paste of multiselected keyfigures (updated 23 May 2006)
    There were cases where users could create different components with same technical names, this is checked now (updated 23 May 2006)
    Variables replaced by query result or by a replacement table reported an incorrect message if they were defined with "Input allowed = true", this is corrected (updated 23 May 2006)
    SAP Exit variables were errorneously not allowed to be used in non content systems, this is corrected (updated 23 May 2006)
    In variable editor for Formula variables replaced by attribute value there were not offered all possible numeric variables offered. This caused a runtime error if especially variables created with Query Designer 3.x were edited. This is corrected now (updated 23 May 2006)
    Due to a program error any saved formula might have been saved incorrectly, if it is using any variables (formula or text variables). This is a critical error which might lead to not understandable error messages during query execution or missing text variable replacement for formulas. The error is corrected the was that any corrupt query can be loaded and after a save it is repaired. We strongly recommend to use this hotfix for all installations!
    SAP Business Explorer Report Designer
    Introduced Versioning and added Version checks. More recent versions of Report Designer are able to design reports with new features. If such a report is edited with an older version of Report Designer some design features might be lost in the report or loading the report might not be possible.
    Images from Mime repository can be added to the report.
    Sequence of Report Sections is saved and loaded in the right order.
    Query Text Elements for more than one Dataprovider are correctly dsiplayed in the Report Item. Property Dialog shows the name of the Dataprovider of the selected Text Element.
    Conditional Formatting for Hierarchy nodes enabled.
    Open Dialog/Save Dialog
    Value Help Dialog (Characteristics Restriction/Filter Selection)
    Search can be performed by entering the search criteria in value help dialog and then by pressing the <Enter> keyboard button</i>
    <b>or see note 929632</b>
    <i>Symptom
    There are errors in Business Explorer components such as Analyzer, Report Designer, Web Application Designer, BEx Query Designer, Open/Save dialog, input help dialog.
    Other terms
    Business Explorer, Front end, BW, BI 7.0, BI, Hotfix, advance correction, Analyzer, Report Designer, Web Application Designer, BEx Query Designer, Open/Save dialog, input help dialog, selector, characteristic restriction, filter value, variables
    Reason and Prerequisites
    You have installed NetWeaver 2004s BI Add-On Front End Patch 02 and you require advance corrections for certain problems that are caused by the BI Add-On (front end).
    Solution
    You can find front end components (DLLs) that correct the errors described below attached to this note. We recommend that you replace all attached DLLs in the setup directory of the BI Add-On. However, you can also replace only those DLLs required to correct a problem that occurred in your system. The following sections describe which DLLs correct which problems.
    The Open/Save dialog and the input help dialog are components that are used by several SAP Business Explorer applications. Therefore, check whether the correction of a problem that occurred in one of the applications is described there.
    SAP Business Explorer Web Application Designer
               Up to now, there are no advance corrections.
    SAP Business Explorer Analyzer and variable screen
               To correct the problems in the Analyzer and the variable screenthat are described here, the files BExApi.dll, BExAddin.dll, BExAnalyzer.xla, BExVariableScreen.dll, BExLocalFormulaParser.dll, BExQueryDesigner.dll, BExSelectorAPI.dll and BExSelectorDialog.dll are required.
    In the variable screen, the formats for the calendar year and calendar month characteristics have not been transferred correctly to the server. As a result, error messages occurred during the check.
    When deleting an item in design mode, the system did not remove the displayed data of the item in analysis mode, rather it still displayed this data.
    The display of the checkbox item and the radio button item has been corrected.
    Errors occurred when you saved variants on the variable screen. All known errors have been corrected.
    The security certificate for the Analyzer has expired and the advance corrections contain a new security certificate.
    SAP Business Explorer Query Designer
                To correct the problems in the Query Designer that are described here, the files BExQueryDesigner.dll, BExSelectorAPI.dll and BExSelectorDialog.dll are required.
    Executing in the Web no longer opens different browser windows, rather the system always uses the same one.
    In certain cases, queries that contain attributes were not saved correctly and as a result, they could not be loaded. This problem has been corrected in all known the cases.
    In certain cases, queries that contain cells were not saved correctly and as a result, they could not be loaded. This problem has been corrected in all known the cases.
    If queries are saved incorrectly (for example with incorrect attributes or incorrect cells), the system issues messages for all cells that are incorrect and it refers to a possible solution. Currently, all text messages are in English and they will be translated in Support Package Stack 8.
    You can now insert and resort attributes at any position. You can do this using drag and drop or cut and paste.
    Formula variables with replacement path now also permit the setting of the dimension.
    If you edited attributes for an object and you then saved your changes immediately without exiting the field, the system did not save the change in this field. This problem has now been corrected.
    Texts of attributes are now displayed correctly after you load the query again (up to now, the system displayed only technical names).
    Constant selection was not displayed correctly in the context menu of a selection. Now, the system displays a checkmark to indicate that constant selection is activated.
    Attributes of display hierarchies are now displayed and saved correctly.
    The system no longer displays operators twice in technical names in formulas. Up to now, [+] + was displayed.
    The system no longer displays UIDs as technical names for structure items and cells in formulas.
    Structures with hierarchical structure items: In certain cases, structure elements disappeared during the hierarchical setup. However, these were saved and they caused an endless loop on the server. This problem has been corrected. You can use the BEx Query Designer to open queries that were saved with these "vanished" structure elements and the "vanished" structure elements are displayed again.
    Errors and terminations on the server now cause a message in the message window of the BEx Query Designer telling you to close and to restart the BEx Query Designer.
    For variables with replacement path, the system displayed too many characteristics (some technical characteristics) for the replacement characteristic. This problem has been corrected.
    Further consistency checks have been implemented and the corresponding messages are displayed in the message list. The system now checks not only queries but it also checks restricted and calculated key figures, variables, and cells.
    If you change a reusable element, the system does not save it automatically. An information message is displayed telling the user that saving the element may affect other queries. You can save the element normally using a save function in the context menu. If the element is used in the query, it is always saved with the query.
    When you exit the BEx Query Designer, the system checks which reusable elements have not yet been saved. The system displays a list containing all unsaved elements and it asks the user whether these elements should be saved.
    There is a new menu function "Save All" that saves all changed reusable elements.
    When you select text variables, the system now displays the correct variable type "Text variable" in the selection.
    You were able to use cut and paste for conditions and exceptions, but this always caused a runtime error. The functions have been deactivated for the moment to avoid program terminations.
    You can now define variables with a replacement from an attribute.
    You can now also display only posted values in the value help (read mode D).
    For text and formula variables with replacement path, you can no longer create on the technical characteristic 1TEXT or 1FORMULA. Any existing variables (that were created with earlier versions) are reported as incorrect and you should delete them.
    For restricted or calculated key figures or for variables, if you made changes and you saved these changes online and confirmed with OK, the system sometimes issued message "Not saved - object is not changeable". This problem has been corrected.
    When creating new reusable elements, the system only checked if the user was authorized to create new elements for this InfoProvider, but it did not check whether the user was authorized to create elements with the given technical name. This problem has been corrected.
    You can now move and copy cells using cut and paste and copy and paste. Unfortunately, you still cannot use drag and drop.
    In formulas, multiline headers of structure elements are correctly displayed in single lines and no longer in several lines.
    In certain cases, hierarchy node variables were saved without a corresponding hierarchy assignment and you could not use them in the report that was being executed.
    After each time you saved data, the context menu of the currently selected object was incorrect. This problem has been corrected.
    You could not delete filter values directly in the BEx Query Designer, rather you had to do this in the filter dialog.
    You could not change characteristics of attributes.
    The system now issues a corresponding success message after each successful saving process.
    SAP Business ExplorerReport Designer
               Up to now, there are no advance corrections.
    Open dialog/Save dialog
               Up to now, there are no advance corrections.
    Input help dialog (characteristic value restriction/filter selection)
               To correct the problems in the value help dialog that are described here, the files BExQueryDesigner.dll, BExSelectorAPI.dll and BExSelectorDialog.dll are required.
    You can now edit variables in the value help for all variable types and not only for characteristic value variables.
    You can now create variables in the value help for all variable types and not only for characteristic value variables.
    When changing an offset, negative offsets are displayed as -5 and no longer as 5-. Variable offsets are displayed directly in the right area of the value help.
    Variables as the to-value of intervals no longer cause terminations.
    In the value range editor, the value you entered manually was not transferred if you directly chose the transfer arrow.
    In the value help for reference characteristics, the system did not display the variables for basic characteristics and therefore there were usually fewer variables than in the BEx Query Designer.
    When you select the hierarchy, the system now correctly displays the date and version variables and no longer hierarchy variables as was incorrectly the case before.
    When you call the value help from the variable entry screen, the system sometimes displayed all master data values (read mode "M") even though it should only display posted values (read mode "D"). This problem has been corrected.</i>

  • APO relation with BI

    Hi experts,
    How is APO, BI and R3 integrated. I am interested in the data flow.
    How you move data from BI to APO and back.
    Secondly, i want to know about datasource 0APO_PPDS_ORDER_01. Is it in bi or apo?
    Also how livecache comes into the picture in this.

    Hi ,
    1.Bi/BW is used for reportimg purpose.Its is used to store the data from r/3 and as well as from APO.
    2.Data can be taken into BI/BW from APO by creating data source for that particular planning area.
    Then u create transformations and DTP process to transfer data from source to destination.
    Infopackage is also created which is used as data containers for the transfer process.
    3.LiveCache is a temporary storage area for the SCM system where the data can used while planning.
    4.So u can transfer data from APO Live cache to External BI/BW infocubes.
    5.Before transfer of data 1st we need to take care whether the infocube created has all the infoobjects that are used in POS of APO.
    6.APO has a internal BI/BW where u can transfer the data from internal APO infocube to external...U can pass data for a single keyfigure or multiple keyfigures...For that u need data extractors in BI/BW.
    7.APO and R/3 data can be passed using CIF integration model..

  • Security on the Input Schedule

    Hi,
    How does the Sceurity work on one global input schedule across multiple users in BPC. Does locking not be an issue when multiple users accessing the same input schedule at the same time. Can someoen tell me how locking works.
    Thanks,
    Vamsi

    Hi,
    In general Locking works depending on the quantity of data you send to the system and different combinations of dimension members across which you send the data.
    1) If the transaction has less than 10 data which is sent to the system then the locking is at record level.
    2) If the transaction has more than 10 data to be sent to the system then it performs sparsity check for the transaction and locks the data accordingly.
    a transaction is said to be Sparse when X>Y,
    Where,
    X=Number of dimensions *Number of unique members in each dimensions
    Y=Number of records * 5
    In case of executing a data Manager packages the locking is done for a package of data which contains large set of data records.
    The number of records a package contains for different application can be maintained using the parameter PACKAGE_SIZE in the transaction UJR0.
    You also find other parameters related to locking in the same transaction.
    But atlast the locking of data accessed concurrently is well managed by the system itself and we need not worry much about that.
    Hope it helps,
    Regards,
    G.Vijaya Kumar

Maybe you are looking for