Hi all,

I'm using BPC 10.1 embedded version.

In my quality environment, I'm facing to unexpected behaviour when I run a planning function.

my case: a Analysis office workbook (version 2.0) contains a planning query and a plannong function to add a new row.

case1: I execute this function with a test user which owns 0BI_ALL and authorization from model for rs_planner. Planning is correctly executed, but the new row is not displayed. (Confirm by a rstt trace).

case2: I promote sap_all to my test user. The same function is executed and new row is displayed.

so, it's an authorization issue, but I don't success to locale the right authorization to fix the problem.

are you facing to the same issue ?

is there more authorization objects to assign to end users, which them indicated into the BPC administration guide?

Thanks à lot.

best regards,

Sebastien

Dear All,

As BPC admin, I have created a new task profile(TP1) with all the tasks, EXCEPT tasks pertaining to the following ones:

- Maintain Environment
- Maintain Security

I have created a new user and assigned this profile(TP1) to the user. When the new user tries to create a model(after logging in), it fails, giving the following error message:

----------------------------------------------------------
You do not have authorization for InfoCube /CPMB/JKIKEVG
InfoCube/InfoProvider  does not exist
----------------------------------------------------------

Note that, the new user has been given basic roles at the SAP BW side.

Is this an error? Or, Is this behaviour expected by design? Does this mean that, only users, with SAP_ALL privilege, can create models?

Pls. help to resolve if this is an error.

Thanks,
Peri

You have basic to intermediate knowledge of BPC script logic syntax and you have to troubleshoot a BPC logic issue.  By following the steps in this survival guide, you can identify the root cause for most logic issues and resolve them if they are due to known bugs.

Pre-requisites:

1. Basic knowledge of BPC logic syntax.  The following are the online help for Logic Keyword References and syntax

BPC 10.1 classic

BPC 10

BPC 7.5

1. Knowledge of UJKT.  UJKT is a BW transaction code that invokes an ABAP program through SAPGUI for testing BPC logic script.  UJKT will show you more detailed diagnostics and you can verify if your script is working correctly.
   • For more details see UJKT user guide
2. Access to an exact copy of the BPC environment/model where the logic is not working as expected.  This is required to run tests and to simplify the problem logic script. If you do not have an exact copy create a copy using BPC Administration functions.
3. The following steps should followed in the prescribed order.

Identify the problem with the following questions: The questions can be roughly divided as What, When and How

WHAT

1. What version of BPC and NW are in use?
2. What type of logic is executing? (Script logic or business rule)
3. Is the logic producing a specific error? If yes,
   1. Review and analyze the error in the logs or system dump
   2. Look for any existing notes and KBA for the error
4. Is the logic completing successfully but producing incorrect results?
5. Is the problem data dependent, e.g. happens only to a specific date or account?  If yes,
6. Is there anything special about the data region that is not producing correct results? For example, is it the start of a calendar year, or a specific base node that was recently added or moved (master data modification)?
7. Does the problem happen in all systems, DEV, QA, and production? If the problem does not happen in all systems then what are the differences between the systems.  Be Specific about
   1. Notes applied, SP version difference for BPC and BW,
   2. Transaction and master data differences, especially if the problem is data dependent

WHEN

1. When did the problem start
   1. Has the logic ever completed successfully for the problem data region?
   2. When was the last time the logic completed correctly?
   3. What has changed since it last worked as expected? If you don’t know the exact answers then establish a probable scenario by following questions
2. How often and when do you execute the logic?
3. When was the last time the logic validated correctly, was your system on the same version?
4. Who executes the logic
5. What is the usual process or the data region for executing the logic
6. Does the problem happen, every time the logic is executed?
7. If random when does it seem to happen most often?  Does it seem to happen after a recent master or transaction data modification?
8. How often does master data change and what changed in the last modification?

HOW

1. Steps to reproduce
   1. How is the problem logic invoked, is it through DM package or is it executed as default logic when sending data
   2. If the problem logic is the default logic, can be executed when sending data or through a DM package, are the results the same both ways?
2. Does the logic produce the same behavior when executed through UJKT?

Trouble Shooting Steps

1. Use a simplified version of the logic, it needs to be a single block of statements with one simplified *REC statement.  There are two ways that a logic script can have many blocks.
   1. The logic has multiple *WHEN/ENDWHEN, *RUNALLOCATION or *RUN_PROGRAM blocks repeated several times in one file.  Remove all but one block for testing.
   2. Logic file has several *INCLUDE statements.  Every *INCLUDE statement references a new logic file.  When you execute a logic with several included files, you are executing all the logic contained in all the included files. Find the logic within the included file that is causing the problem and test only that logic.  Simplify the logic as described in step 1.i before testing it.
2. Replace as many parameterized values (anything between %) or variables (anything between $) with hard coded values. Often the problem is due to parsing of a parameterized value.  Removing the parameters and then adding them back one by one will show which one is causing the problem
3. Use simplified test data region, either the problem data region or any data region with test data available.
   1. Reduce the data region that is tested by replacing parameterized scope statements in *XDIM_MEMBERSET with individual parent or child nodes.
   2. If the problem is occurring for a particular data region, then replace the parameters in *XDIM_MEMBERSET with only the members that are to be tested.
   3. If the problem is occurring for all data region, then use a random test date region.  Replace the parameters in *XDIM_MEMBERSET with the specific data region selected for testing.
   4. Reduce the scope by removing keywords likeunless if that is the root cause of the error.
4. Reduce the complexity of *REC statements. Remove all the nested WHEN/ENDWHEN and REC statements. Refer to Example 1 in attached file for more clarification.
5. Test the logic using UJKT, first by running in simulated mode
6. Review the error in UJKT.If you do not find any error when executing the simplified version of the logic through UJKT, add to the complexity of the original script in stages and test.
7. Review the diagnostics generated in UJKT.  Refer to example 2 in the attached document for more clarification
8. If the logic is for executing business rules, validate that the scope and context are passed correctly and then follow the guide for troubleshooting business rules, and master data configuration

Analysis of the information:

1. In most simple cases, you experience a problem after one or more of the following situations is met.  In such cases, you need to reproduce and verify the issue, using a simplified version of the logic and executing through UJKT. You can report the problem to SAP if it has not already been reported. The cases that qualify for this are:
   1. After System upgrade / migrate form a different version of BPC,
   2. After applying some notes,
   3. Changes made to master data
   4. Logic being executed for a new data region for the first time
2. If the problem is not due to any of the above conditions then you need to analyze the information further. Typically, you have development, QA and production systems.  You need to focus on two different lines of analysis when the problem happens in all systems and when it does not.
   1. The problem happens in all systems, but the same logic was working in the past few years and you don’t know exactly when the problem started,
      1. Focus on the last time the logic was validated and tested successfully in each system and confirm if you were on the same version of BPC and BW.  Sometime code bugs can remain hidden until you validate the logic. Refer to Example 3 in the attached document for further clarification
   2. The problem happens only in one system.  Analyze differences in master data and transaction data as well as system versions and configuration.
      1. Focus on differences between the problem system and working system.  Make sure to consider, notes, system upgrades, master data, transaction data
      2. If you confirm all versions and notes applied are the same across the system, then focus on master and transaction data differences.  By narrowing the scope to just one data region, as described in trouble shooting steps – items 2 and 3,  you can find and test the problem data region.
3. What if the error happens only when it is invoked a certain way?  This can be very well due to differences in the scope of the logic.  When the logic is invoked through data manager (DM) its scope is what is known as "external scope" set by the values selected through DM interface. When the logic is invoked through other methods it is subject to "internal scope" set by *XDIM_MEMBERSET.  For example default logic can be invoked by executing DM package DEFAULT_FORMULAS or when sending data through input forms.  The same default logic could have different results due to differences in the scope.  to learn more about the scope of default logic please review the SCN document.
   
   

When logic is executed through UJKT its scope can be controlled.  If the problem does not happen when executed with a simplified scope then the root cause is in the scope or the parsing of parameterized values for scope.

Hi All

We are seeking a method to manipulate the row definition, inner dimension member based on two scenarios: Please see the example and scenarios below:

What we have tried:

*By default, we have the fund member selector linked to the first dimension (account) property (FUND). This produces the correct results for scenario 2 above.

*We have a EPMDIMENSIONOVERRIDE for the fund. This produces the correct results for scenario 1 above.

*We have used EPMOLAPMEMBERO to reference the local member value. However this results in multiple funds being displayed for each account. 

What we need:

We need a method to be able to toggle between scenarios 1 & 2, with the row defintion being dynamically updated (after refresh).

Is there any API or EPM formula that allows the member selector, dimension property to be overriden/manipulated?

Any other ideas?

Any assistance much appreciated

Glen

why time dimension aggregate last month only  in the quarter level with balance sheet account and aggregate all 3 month in the p&l account

Hi ALL BPC GURUS'

Not able to See Values in WEB Report/Input Template - If I selected Base Members option Including Parent Option, but when I use only Base Members or descendants or children then report shows value.

Any Idea why this kind of error occurs. Presently we are in SAP BPC 10.0 NW - SP 19 Level.

Error Screenshot when Selected With Including Parent - Balance Sheet & Base Values

Screenshot when Selected With out Including Parent -Only  Base Values  are displayed

Hi All,

I am looking for any solution, where the Description of Local Member changes dynamically.

I know we can have one dynamic local member description based on single variable cell reference( as shown in EPM Academy videos).

My scenario is I have Row A with Segment, Row B  as Product. For Difference Segments by Products like can be same or different.

In Column A I have Time and Column B I have Account.

To get repletion of Column of Columns headers, I have created Column A and Column B as Local members.

I want description of Column A which is having Local member relating to Time, description of Segment.

Here is the screenshot of my Report.

I have tried creating another local member based on Row formula, it works fine but Formatting is wrong? I have 35 Segments, so I want to use EPM Formatting feature than excel formatting by cell.

How to change the formatting to get the first report like format for the new Local Member(New Desc in the above screenshot)?

Thanks

Hi All,

Please help on the below error. We are using SAP BPC 10.1 classic and BW on HANA

Thanks,

Naidu

Dear experts, I need your help please.

We have an installation of SAP BPC 7.5 on windows 2008 and sql 2018, and we are asked to migrate to a new hardware with windows 2012 R2 and Sql 2012.

After this we will do an upgrade to BPC 10.1

For what I see in PAM it is not possible to install BPC 7.5 on windows 2012.

Should I do the upgrade before and then migrate, or there is any workaround?

The urgency is to leave the windows 2008 because of the maintenance costs.

Many thanks in advance.

Best regards,

José Alves

Hi experts,

Is there a possibility to set up the transformation or the conversion to read a property of one dimension (DIM1) to define the target member in another dimension (DIM2).

E.g. if the property x of DIM1 = "yes", then the data record should be saved on Member1 in DIM2, otherwise the data record should be saved on Member2 in DIM2.

Hope you can understand my issue and help me with this.

Thanks and best regads,

Sofija

Hi experts,

I have to do a report that depends of radio button show BASMember of selected member (first option) or show CHILDREN of selected member (second option) in rows.

How can I do with EPMDimensionOverride function? I would like that when user select radio button automatically change my report.

Thanks!

Hi all,

After chaging an ACCOUNT from LEQ to INC, we are facing the following reporting issue related to ACCOUNT hierarchy:

We have changed member properties, the hierarchy and processed the dimension successfully several times,  but the reporting issue has not been solved. We can only create reports using account basemembers.

We have run UJA_DATA_CHECKER program and shows no errors.

We have also applied SAP note 1673094.

Our system: BW    Release 740 SP-level  0012

                   BPC: Release  810 SP-level  0007

Any ideas?

Thanks,

Carlos

Hi experts,

I would like to protect sheet for users, that only can change context members and they see new values on report.

the procedure that I have achieved is:

1. Select all cells of my sheet:

2. Active Blocked option

3. Create a password to protect workbook or worksheet.

Is this correct?

Is possible to protect my report in another way? How?

Thanks!

Hi experts,

I am getting the following delivery status error whenever mail is sent or received in BPF. Any solution to solve this issue? Please share me any information on how the mail is triggered and place to make adjustments.

Thanks

Praveen

Hello,

I have an installation of SAP ERP on HANA. I would like to use BPC 10.1 Embedded (i.e. BPC web  / EPM Addin for Microsoft as front-end) on the same system. As per my understanding, you do not need to install the CPMBPC and HANABPC components to use BPC 10.1 embedded only.

I have carried out all the necessary steps for BPC installation and post-installation as per the installation guide for BPC embedded. 

However, when I try to connect to the system using BPC Web, I get stuck at the screen with message 'Querying Available Environments'.

Has anyone faced this issue before and how did you resolve it?

Is it possible to use BPC Web / EPM-Addin for Microsoft without installing the CPMBPC and HANABPC components?

Thanks,

Ninad

I would like to change the Default formatting sheet numbers to be financial with commas, decimals, and parentheses around negatives. I know how to use the formatting sheet but would like to change the default sheet globally. Any help is appreciated.

Thanks,

Michael

Dear all,

I have set up a Work Status template for my consolidation application.

The issue is that I have several dimensions in my header and I would like to make it easier for the users: do you know if there's a way to set some default values for some dimensions? in this way the user should not select a specific member for each dimension.

Thanks a lot for your valuable answers

Best regards

Hi Experts,

I have multiple forecast cycles (F1 to F12) in my Category dimension and would like to dynamically bring the active one based on a property ISFORECAST=Y into the data manager package link. How can this be done in the DMP?

Regards,

Shariq

Dear all,

I have set up a Journal template for my consolidation application.

The issue is that I have several dimensions in my header and I would like to make it easier for the users: do you know if there's a way to set some default values for some dimensions? in this way the user should not select a specific member for each dimension.

Thanks a lot for your valuable answers

Best regards

Hello All,

I am trying to load in Currency Exchange Rates into BPC. The exchange rate field we are trying to bring in uses FLTP (Floating point number) Data Type. This shows as scientific notation.

When I try to LOAD_INFOPROVIDER_UI and bring in this field, the load Aborts and we get an ABAP dump "CONVT_NO_NUMBER" with Short Text: "Unable to interpret "2.722999999999999E-01" as a number."

I'm assuming I need to do something in the Transformation/Conversion files to convert this FLTP value into a number, but I haven't figured out exactly how to do this.

I tried doing js:Number(Value) in the formula field, js:Number(%internal%) in the internal column and js:Number(%external%) in the external column.

I also tried using js:parseInt(Value) in each of the fields like Number above.

Any ideas would be great!

Regards,

Alexander

Specs:

CPMBPC 801 SP5 (equiv to 800 SP12)
EPM SP 18 Patch1