SAP Community - BW Planning

How to read a mapping inside FOX planning function without using ABAP

2021-05-13T15:43:17+02:00

Hello all,

Not a long time ago I faced an issue with reading a mapping from a planning function. Before HANA was invented it was a no-brainer. We created a functional module and read it through "call function". But what is the best approach now when we shouldn't use ABAP inside planning functions anymore? (To be specific, the system which I'm using is BW4HANA).

It seems that the only one way to do it is to use a relatively new BI-IP function “Accessing InfoProviders”.

So I did a few setups:

Direct update ADSO with a technical key figure (because we need to build an aggregation level on top of it);

A composite provider;

An aggregation level;

To read a mapping a following code should be written:

INFOPROVIDER ZAGGLEV1.



FOREACH A, B IN SELECTION.



   KF = ZAGGLEV1.{ZKF, ZINFOPROV1, A, B }.

   IF KF = 1. 

       {ZAMOUNT, ZINFOPROV2, A, B} = …

   ENDIF.



ENDFOR.

It looks a little weird comparing to a function module call, but it works and works on HANA.

But in my case, it didn't work. So, I tried to find out what might be causing the problem. The problem was that a characteristic with conversion routine was involved. It was one of those PS/PPM characteristics which have a technical GUID. So, it has only a few visible master data (which are used in the mapping) but hundreds GUIDs.

I tried different approaches to solve this obstacle including a composite provider with a left join (left join the ADSO which contains the mapping with the characteristic which contains GUID in its attributes). It was a good try but the absolute wrong one because it's impossible to build an aggregation level on top of such a composite provider.

So, at the end I created a calculation view which joins the ADSO and another calculation view which is used to access the master data of my troubled characteristic.

This is how the mapping looks like before the join:

And this is how it is after:

And the last step, I used this calc view in the composite provider connecting GUID directly to my troubled characteristic:

This how the mapping finally looks like through LISTCUBE:

Now the code mentioned earlier works fine.

So, this is the only one way which I found to read a mapping inside BI-IP planning function without using ABAP. If you know something better, please share it with me.

Most common issues with Analysis for Office 2.8 SP6

2021-05-20T19:26:14+02:00

Dear SAP Community,

we have rolled out Analysis for Office 2.8 SP6 to a wider group of users. While doing that we gained some experience on the behavior and issues that occured while rolling out this new version. I have collected all issues and the resolution steps in order to help you in case you are facing similar issues. One important remark: I can not judge whether there are any dependencies on other Excel Add-ins or applications that you are using.

General:

Do I need to uninstall my current Analysis for Office?

It is not required to uninstall your current version of AfO but we have observed that some users where facing issues after directly upgrading with uninstalling the current AfO instance. My suggestion would be to install the latest version first and see if everything is working as excpected.

Do I have to do anything after the Update?

Please clear your AfO Cache after the updating by going the following path: Open AfO → File → Customize Analysis → Options → Platform → Clear Cache. Note: there won't be any message coming up after pressing the button. Clearing the cache can resolve the following issues: numbers are displayed incorrectly, functions are not getting executed or the the formatting is disrupted. You may also deactivate the workbook caching.

Specific error messages:

I am getting a message saying "Unsecure connection". What do I have to do?

Don't worry, in case your connections have been secure before and if the connections did not change, then this will not be a security problem. If you do not want to receive this message any more you can turn it off by doing the following: open Analysis for Office → File → Analysis → Customize Analysis → Technical Configuration → change the setting AllowInsecureConnections to „yes“.

I am getting a message saying "Couldn't establish a secure connection". What do I have to do?

This message comes up when you try to open a file from a local drive which has been saved with an older version of Analysis for Office and the name of the system connection has changed. In order to resolve this you have to open the local file and manually establish a connection by going to Insert Data Source Define → Select source for Analysis → And then connect to your preferred system. After that you can open and refresh the workbook and then you have to update the settings by going to Analysis for Office → File → Analysis → Customize Analysis → Technical Configuration → Tick the box for ForceRefreshConnection and save the workbook. After that you should be able to open the local file without any problems.

Edit: This message will occur for different reasons. You can turn this off by starting AfO as an Administrator (Right click on the application icon and select "Run as Administrator" from the context menu). Go to Analysis for Office → File → Analysis → Customize Analysis → Technical Configuration → Untick the box for EnableWarningForFailedSnc. After restarting AfO the message should not show up anymore.

I am getting a message saying "An error occurred while trying to apply the default User Interface Customization profile". What do I have to do?

1. uninstall AfO 2.8

2. remove manually the outdated EPMAddin folder under C:\Program Files (x86)\SAP BusinessObjects\Office AddIn\Plugins\EPMAddin

3. reinstall AfO 2.8

I am getting a message saying: "Error details: Could not load file or assembly 'FPMXLClient.Common, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannof find the file specified."

If you haven't upgraded yet to AfO 2.8, please uninstall all previous versions of Analysis for Office. By doing this you can avoid above error message. In addition you should also manually remove the outdated EPM Addin folder under C:\Program Files (x86)\SAP BusinessObjects\Office AddIn\Plugins\EPMAddin. Keep in mind that this might remove your Favorites from the SAP Logon Pad and you might want to save them before.

If you are already getting this error message, please uninstall all previous version of Analysis for Office and check if the issue got resolved. If the error message remains, please also re-install AfO 2.8 SP6. After that the issue should be resolved.

After the upgrade AfO is glitching. Eg when using the scrollbar the dropdown menus are randomly opening. What can I do?

This is issue is mainly occuring when using a secondary monitor. When AfO is opened on the primary monitor there should not be any issue. Please check the following settings.

I am getting a message saying: "The given assembly name or codebase was invalid. (Exception from HRESULT: 0x80131047)"

As per SAP Note 2876424 we can try the following:

Uninstall Analysis for Office

Afterwards check if the folder "C:\Program Files (x86)\SAP BusinessObjects\Office AddIn" is empty

Then remove the node "HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\Addins\SapExcelAddIn" via registry settings (i.e. regedit)

Reinstall AO and check if the issue is solved.

I am getting a message saying: "Downloading file:///C:/Program Files (x86)/SAP BusinessObjects/Office AddIn/SapExcelAddIn.vsto did not succeed"

Please check if the SapExcelAddin.vsto file is available under C:/Program Files (x86)/SAP BusinessObjects/Office AddIn/. If the folder is empty, it might be an indicator that the installation did not work properly. In this case we would advise you to check this with your local IT Team as there might be an issue with your machine or there might be some dependency with older installations of AfO.

Summary:

As you can see in the above list, there were a couple of issues that we were facing when distributing the latest AfO Version to our user community. We were either able to resolve these issues on our own or by reaching out the SAP Support. So i hope that this list will help you in case you are facing similar issues from your end. Please feel free to add any further issues that you are facing or any other tips that would be helpful for the SAP Community.

Best regards
Pascal

How to Collect TVARVC Table Entries in Transport Request

2021-11-16T08:09:33+01:00

In this Blog post we will understand how can we capture the Entries within TVARVC Table in a Transport Request for moving it across systems.

Before we proceed with the steps lets understand the Purpose of TVARVC Table below :

TVARVC :

TVARVC is standard table given by SAP to store the data under variants. we can put the values in TVARVC table to avoid hardcoding and/or creation of custom tables.

Now that we have got a bit of overview of the purpose of TVARVC Table existence , lets try to understand how do we move the entries we make within this table across different system (Dev > Quality > Production)

Lets try to understand it via Steps below :

Go to SE16 Tcode , and give the Table name which is TVARVC in our case.

2. Click Enter and the Give the Values you want to Capture in TR in Variable Name Field as in the following Snapshot and Click Execute.

3. Once you are within the Table ,

a. Select the Entries that you want to Capture within Transport request.

b. Once you are done selecting entries , Click More Option from Menu Bar > Table Entry > Transport Entries

c. Once you click on Transport Entries , It will give you a pop-up to Collect the entries in Transport request , Select the already existing TR or Create a new TR as per your requirement.

4. Once you select the Transport Request for capturing Entries , Your entries are captured within that particular TR which you can use for moving the entries across systems.

Conclusion:

By Following the above steps , you can capture the entries you make in TVARVC for your requirements and move it across systems this enables direct capturing of entries from within TVARVC table.

— Sources of the pictures are screenshots I have taken from SAP and no image is taken from the internet.

Hope the above Information added a bit of value to your time and knowledge .

If you enjoyed reading it do give it a Like and would be happy to read your feedback in the comments section.

How to Process Multiple Files from Application Server via ABAP Program

2021-12-28T20:09:53+01:00

In this Blog Post we will understand how to process multiple files of certain File Masks from Application Server (AL11) via ABAP Program.

Lets try to understand it via following steps :

Input to our Executable Program will be following 3 parameters:

File Mask for processing Files from Server (e.g. ABC* , files starting with ABC*)

Directory path from Application Server where File are stored.

Process Chain to execute that consists of steps for Processing this Files.

In the next step, we will get all the Files from Application Server using Function "EPS2_GET_DIRECTORY_LISTING" and we will pass directory path and File mask we passed as an Input to this Function Module and the Function will return a table with the details related to the files fetched from Application Server.

CALL FUNCTION 'EPS2_GET_DIRECTORY_LISTING' 

EXPORTING



iv_dir_name = lv_iv_dir_name

file_mask   = lv_file_mask



TABLES

dir_list = lt_file_tab



EXCEPTIONS



invalid_eps_subdir      = 1

sapgparam_failed        = 2

build_directory_failed  = 3

no_authorization        = 4

read_directory_failed   = 5

too_many_read_errors    = 6

empty_directory_list    = 7

OTHERS                  = 8.



IF sy-subrc = 0.

"sorting by name to get the oldest file

SORT lt_file_tab BY name.

ENDIF.

2. As a next step, we wanted the count of Files fetched from server with same File Mask we passed, to achieve this we will make use of Internal table where we have passed data related to Files fetched from Server.

*Code to get count of Files

DESCRIBE TABLE lt_file_tab LINES files_count.

3. Now since we have the count of files fetched for processing, we will execute a DO Loop based on the the count of files fetched and Call Function "RSPC_API_CHAIN_START" for executing process chain we passed as a parameter to the program and also which contains the steps that Processes the Files fetched.

*Code to loop through Files Count and Executing Process chain correspondingly



IF files_count >= 1.



DO files_count TIMES.



CALL FUNCTION 'RSPC API CHAIN START'

EXPORTING

i_chain  = p_pchain



IMPORTING

e_loqid = lv_logid.

4. Once process chain is executed in above step within same DO loop execution , we will check the status of Process chain before beginning the next iteration of DO Loop by calling Function "RSPC_API_CHAIN_GET_STATUS" and passing process chain name and log id of the Process chain run which we will get as a output from previous function call of "RSPC_API_CHAIN_START".

IF sy-subrc <> 0.

ELSE.



  DO.

    WAIT UP TO 2 SECONDS.



    CALL FUNCTION ‘RSPC_API_CHAIN_GET_STATUS‘

    EXPORTING

      i_chain = p_pchain

      i_logid = lv_logid



    IMPORTING

      e_status = lv_status.



    IF lv_status = 'G' OR lv_status = 'R'

      EXIT.

    ENDIF.

  ENDDO.

    IF lv_status = ‘R'.

      MESSAGE ‘File has errors' TYPE "E”

      EXIT.

    ENDIF.

ENDIF.

ENDDO.

5. Once, we get status of Process chain from previous function call of "RSPC_API_CHAIN_GET_STATUS" if its Green or Red we will exit that particular Iteration of DO Loop to process next file ( In this particular scenario , Process chain has step to move the file to different folders based on the execution status of DTP)

Conclusion :

By following the Steps above, we can process multiple files from Application server with same file masks by harnessing the use of Standard Functions from SAP.

— Source of the Code I have taken from my SAP system and no code is taken from the internet.

Hope the above Information added a bit of value to your time and knowledge .

If you enjoyed reading it do give it a Like and would be happy to read your feedback in the comments section.

How to Recover Objects not visible within InfoArea

2021-12-31T09:20:53+01:00

In this Blog Post we will understand how to handle a situation when Objects are not visible within InfoArea.

Problem Statement :

Often when there are Role level and authorization related Changes from Basis or Security Team on User ID, User's might not be able to see the Modelling Objects and Query related Elements within the InfoArea and it creates a kind of confusion when no object is visible to work upon which used to exists before.

This issue often occurs due to Shared Buffer that exists on Application Server.

Lets try to Understand how we can resolve this Issue.

Solution :

Go to T-Code : RSOSM, which is often used for BW Search for SAP HANA Maintenance.

2. You will get the above Screen , Scroll to the bottom of the screen and click on "Configure BW Search" , You will be presented with the below Screen.

3. Once you are within "Configure BW Search" Section, You can see the status of your Shared Buffer as "Shared Buffer is Filled" and a Delete Icon besides that Status.

4. Click on that Delete Icon , it will delete your Shared Buffer and the Status will be changed to "Shared Buffer is not filled" as below.

5. Now , go back to your InfoArea and hit Refresh , You will be able to see all your Modelling Objects and Query related Elements back within InfoArea.

Conclusion:

By Following the above steps you will be able to clear up your shared buffer and able to see the missing Objects back within your InfoArea.

— Sources of the pictures are screenshots I have taken from SAP system and no image is taken from the internet.

Hope the above Information added a bit of value to your time and knowledge .

If you enjoyed reading it do give it a Like and would be happy to read your feedback in the comments section.

End of BI-IP – What‘s next? A viewpoint on the SAP Planning Portfolio 1

2022-06-04T19:30:27+02:00

Introduction

The SAP Portfolio for planning is changing. The system landscape for reporting and planning is enhanced by SAP Analytics Cloud (SAC). Or maybe you are in the middle of a S/4 HANA project or a BW/4 project is going on.
However your current planning system landscape looks like, chances are high that you will be impacted by a SAC, S/4 or BW/4 project.

The aim of this blog is to help and guide you in case you need answers on how your planning strategy should look like.

In this part the approaches, the criteria on how we want to compare, the applications and an outlook will be given.

In a second blog which is planned to be released in Q3/2022 we will present more detailed results.

Approaches

From the authors point of view, coming from the planning and analytics world, there are currently 3 main approaches on how your planning architecture could look like. Of course, there may be different flavors of it:

Business Warehouse Approach

SAC Native Approach

S/4 Approach

Each of the approaches makes sense depending on where you come from and where you want to be in the near future. The tricky question is how to find out what's best for a certain customer with a certain history. And the answer is not a simple one. It might also be the case that you use more than one of the approaches above. And in the long-term perspective also Datawarehouse Cloud (DWC) might play a role.

Approach 1 might be especially interesting for you in case you invested heavily in SAP IP in the past and want to reuse your investments. Maybe you would like to use an appealing frontend like SAC instead of BEx and still stay on the same model.

Approach 2 might be interesting for all kinds of customers, with or without any history of SAP IP.

Approach 3 might be interesting for any S/4 customers.

Comparing the Approaches

To give direction and also to make experiences in real world environments, we decided to build applications and compare them. For this purpose we will use the following criteria:

Master Data Synchronization

Authorization Management and Generation

Reference Data Integration

Disaggregation and Logic

Automatic Loads

Performance

Licence

Debugging Options

Look & Feel

Usability

Integration

Flexibility

Applications

The applications we are currently working on are the following ones:

Approach 1: A betting game application for the soccer world cup. The users can enter their bets, the scoring function and more complex functions are implemented in the Business Warehouse and visualized with SAC. Additionally, SAC is also serving as an Application Development Environment

Approach 2: An application for entering the daily steps is implemented. The users can capture their daily activities and see trends over time. There will be no Business Wareshouse in the system landscape. All logic and all application development is done in SAC

Approach 3: We plan data live in the S/4 HANA system and write data into the ACDOCP table

The implementation of the applications is already quite enhanced, and we are working on comparing the results based on the defined criteria.

Outlook

In the next blog we will present the results of our comparison and you will get a summary of our experiences. I can already reveal that every approach has its strenghts and that we had emotional discussions about the approaches inside our team.

We will also have a look on the degree of maturity of the different products used in the different approaches.

The final result will be a decision tree which should serve you in getting a better feeling what is right for your special, unique situation.

Lessons learned while working on BW Planning – TPM project

2022-07-28T16:33:13+02:00

Hello Developers,

Recently I got an opportunity to work on a BW TPM project. Compared with pure BW Modeling project I had to explore things related to Planning, Configuration required in BW and CRM and mainly how and where to debug on encountering errors when executing Queries and Planning Functions from Web-UI. Documenting few points which were helpful during the development cycle.

BW Queries and Planning Functions Execution

When BW Queries and Planning Functions (PFs) are called from CRM Web-UI it might encounter errors while executing them. Error description might not help us to identify the root cause because of which we need to debug Class/Method.One of the important Class related to execution of BW Objects is Class *CL_IMP_OBJECT. Below are few of the Methods from the same related to Query and Planning Function execution.
- IF_IMP_OBJECT~EXECUTE_QUERY – This Method will execute BW Query, we can set Break Point before it’s called to check Filters, Variables etc... being passed.
- IF_IMP_OBJECT~HANDLE_EVENT – This Method will identify which Planning Functions (PFs) to be executed for the selected Query and Event_ID triggered.
- EXECUTE_PLANNING_FCT – This Method executes each of the Planning Function configured for Query and Event_ID identified at HANDLE_EVENT Method.
- ENHANCE_QUERY_FILTER & ENHANCE_EVENT_FILTER – These Methods check and update Query Filters and PF Filters respectively which gets called when executing Queries and PFs accordingly.When we create Custom Planning Function and configure it for say Event 3 (After Update Cell) still it might not get executed on changing data if PF related filter code is not maintained in Methods of Class *CL_RSCRM_IMP_EVENT_PF_B4.Similarly for New Queries check Methods of Class *CL_RSCRM_IMP_QUERY_B4 and maintain Query Technical name like data maintained for Standard Queries.

Types of Custom ‘Planning Function Type’ based on Class

We can have Class ‘Without Reference data’ OR ‘With Reference data’.For Class Without Reference data Interface and Methods would be:

For Class With Reference data Interface and Methods would be:

Method ‘GET_REF_DATA_SEL’ is used to apply filter for selecting Reference data.We can create Public-Static Methods to include Custom logic in With / Without Reference data Interface types.

Identifying which BW Query is mapped in CRM Web-UI screen

In CRM Web-UI click on any of the Query Data cell and press Ctrl + Alt + D
Pop-up window appears in which select ‘Show Data Source Picker’

In the next screen select ‘queryinfo’

Click ‘Esc’ on keyboard, List of queries on the screen selected is displayed.

On encountering IMP_CORE and PE Errors

When we encounter these errors check for logs generated in “SM21”. If no logs exist then go to TCode “RSTT” and Activate Trace for your ID, perform the same action to reproduce error. Later De-Activate Trace for your ID. If Traces are generated, then Execute them to check errors being reported.

Based on the information we can identify which Function Module to set Break Point for debugging and identify the root cause.

Best practice while performing calculation of Keyfigure in Class

When populating Keyfigure based on CASE condition, ensure it also has ELSE part to populate.
Eg: CASE WHEN INFOPROV = ‘ZADSOX1’ THEN ZADSOX1.ZKF1 ELSE 0 END AS ZKF_CUSTOMThough “ELSE 0” might not be logically and syntactically required, include it to avoid potential technical issues which may arise due to populating NULL value into Keyfigure.

Hope this information will help Developers working on BW TPM projects to understand better about Class, Method, TCode to check for identifying root cause of errors encountered. Please share your comments and feedback !!

Move your SAP BPC applications to SAP Analytics Cloud

2022-08-09T23:05:11+02:00

Since 2007, when SAP acquired Outlooksoft, SAP BPC has been a part of SAP’s product portfolio and the number of SAP BPC customers quickly grew from mere 700 customers in 2007 to tens of thousands of customers and users over the years. SAP BPC provided a rock-solid on-premise planning solution for customers. When the world economy embraced cloud technology, SAP was able to satisfy that need with SAP Analytics Cloud, its flagship analytics and planning SAAS solution. Though SAP has promised customers using on-premise solutions that their investments are safe and secure as announced in its product strategy, the on-premise users themselves are facing a number of challenges. The current economic, social and technology scenario posed formidable tests and trials for planners of on-premise solutions. This is not only because of Covid-19 but also because of other factors as well. Let us briefly discuss the challenges that posed to planners today.

Changing customer expectations driven by disruption in the economy

We are living in an era of disruption of all kinds. Supply chain disruptions due to lockdowns, wars, sanctions; monetary and fiscal disruptions due to high inflation, global debt, currency volatility and added to that is the digital disruption where data is the new oil and enterprises that can leverage the ever-growing data to make decisions can thrive while those who can’t, will be left behind. The business planners are facing new challenges like

How to empower through process automation to free up time to do more meaningful work

How do we drive maximum cost synergies to fund innovation

How do we better engage our employees to attract and retain top talent

How do we deliver a next-generation customer experience in a world of disruption

How do we focus on spending and resource requirements today and for tomorrow

Covid-19 and beyond

Since 2020 Covid-19 has presented unprecedented challenge to all enterprises and tested the technological and managerial limits of planners all over the world. The annual plans and forecasts had to be changed frequently, the drivers for the plans had to be adjusted every week if not every day, the agility of business planning solutions to adapt to changes in the planning models underwent stress test. After this pandemic goes into the history books, for many businesses, it will take a while to return to the pre-pandemic state. The challenge to the business planners is how to smoothen this ride and find opportunities in this challenge.

All these factors are leading the organizations to move to the cloud-based planning solution from their traditional on-premise solutions and SAP BPC is no exception. The easiest and smoothest transition for SAP BPC customers to cloud is SAP Analytics Cloud. With SAP Analytics Cloud, customers can leverage Planning and Analysis on a single solution. SAP Analytics Cloud provides a set of rich planning capabilities that allows organizations to plan across various lines of business, connecting operational to financial plans. SAP Analytics Cloud is always online with your most trusted data. It is an unbroken experience of agility and value. All this leads to a world where business decisions and strategies are constantly informed and updated with confident, authoritative planning.

Why move now?

Moving now to SAP Analytics Cloud allows organizations a lot of benefits. Here are a few of them:

Extended Planning and Analysis

Extended Planning and Analysis (xP&A) is the evolution of financial planning and analysis; creating and connecting strategic, financial, and operational plans across the enterprise to optimize performance.SAP Analytics Cloud is well suited to execute Extended Planning and Analysis (xP&A) strategy. Let us discuss this strategy a bit more to understand how SAC helps to execute this strategy.

Crowdsource plans and budgets – Typically organizations consist of many lines of business such as sales, marketing, information technology, supply chain, human resources etc. Each line of business in turn plan their annual activities, budgets and monthly/quarterly forecasts. The planning cycle includes preparing the planning model, identifying planning drivers, importing master and transactional data; scheduling planning processes; entering plan data and adjustments; doing the planning calculations, spreading, distributions and allocations; reviewing the actual vs budget variance; and finalizing and publishing the results. Each line of business follows these steps with some minor variations. When an organization prepares strategic plans and annual budgets, they crowdsource the plans budgets from these various lines of businesses. SAP Analytics Cloud can help in planning and forecasting for various lines of business. Moreover, it has delivered content for those lines of business. Crowdsourcing plans and budgets from the lines of business becomes easy with SAP Analytics Cloud since all those models reside within the same solution.

Linking operational and financial planning – The plans of the individual lines of businesses need to be linked together. If there is no linking through exchange of master data, assumptions and results, the plans and forecasts crowdsourced from the lines of businesses tend to be siloed. For example, operational budget in terms of sales units to be sold in different territories, product mix, supply routes etc. should be in sync with the plans and forecasts of cost of sales, cost center expenses etc. The planning models for various lines of business can share the plan data using the functionality such as public dimensions, cross model data actions etc. within SAP Analytics Cloud thereby facilitating linking of operational and financial planning.

Embed within enterprise applications – The transactional data required for the actual vs budget variances comes from the enterprise applications. SAP Analytics Cloud has built-in connectors for various enterprise applications such as Success Factors, S/4 HANA, SAP BW, Ariba, Concur, Fieldglass etc. that allow direct acquisition of the required transactional data.

Next generation FP&A (Financial Planning and Analysis) tools

The corporate decision making has evolved from being linear or top-down following hierarchical order to dynamic, self-service, involving faster iterations to augmented and decentralized decision making that involves instantaneous and continuous adjustments using artificial intelligence. SAP Analytics Cloud provides the machine learning and predictive tools for augmented analytics.

Integration with S/4 Hana

SAP Analytics Cloud provides two-way built-in integration with S/4 Hana to import and export the data. In addition, it allows you to perform analytics with live connectivity to S/4 Hana where the data never leaves the customer firewall. SAP Analytics Cloud is even embedded within S/4 Hana for analytics.

Pre-built content

When you move to SAP analytics Cloud, you can avail the pre-built content available to get a head start for your implementation and get started with SAP analytics Cloud with ease. The available content includes the content developed by SAP as well as the content developed by SAP partners.

Smart Insight and Smart Discovery

SAP Analytics Cloud provides a single solution that combines planning, analytics and predictive. You can leverage the smart insights smart discovery provided by the predictive tools to incorporate into your planning models, visualize the results, use advanced features such as visual formulas, simulations using value driver tree etc. to take your planning to the next level by incorporating the strategic business insights into your plans and forecasts.

Hence there is no better time than now to move your BPC applications to SAP Analytics Cloud.

Introducing – BPC Embedded Access Rights

2022-08-23T17:50:24+02:00

SAP recently introduced BPC Embedded Access Rights. In this blog, let us understand the details of this SAP Business Planning and Consolidation Embedded Access Rights.

Why BPC Embedded Access Rights

The strategic solution that SAP has for XP&A is SAP Analytics Cloud which is offered on public cloud and combines planning, predictive and business intelligence functionality into one product. SAP also has SAP Business Planning and Consolidation to address financial planning requirements for customers who require an on-premise solution. As stated earlier in SAP BPC Strategy, though our cloud-based planning solution, SAP Analytics Cloud, represents our strategic and most innovative business intelligence and planning solution, the SAP BPC product will receive continuous innovations, bug fixes, and investments in infrastructure topics with SAP Analytic Cloud. For the customers to take advantage of the latest innovations that can address the challenges to the planners, the enterprises should be running on SAP Analytics Cloud platform. However, we have thousands of customers that use SAP Business Planning and Consolidation in its various versions. This poses a formidable task of moving these customers quickly and smoothly to SAC. The customers should be allowed to move at their own pace, without disruption of their planning processes and in phased manner if they prefer so. In order to facilitate this process, some customers chose to complement their planning process with SAC and some others chose to add new planning process in SAC.

In addition to moving the business process from BPC to SAC, the BPC customers also used to encounter another obstacle in licensing. A planning user typically required a license for BPC as well as SAC even if he/she wanted to use BPC Live to plan in both the systems. The BPC Embedded Access Rights are intended to obviate this dual licensing for BPC Live scenario and facilitate smooth transition to SAP Analytics Cloud. Hence, to summarize, the reason why SAP introduced BPC Embedded Access Rights is to avoid double licensing for customers using BPC Live to plan in SAC and BPC.

What are BPC Embedded Access Rights

At this time, BPC Embedded Access Rights are applicable only to BPC Live connections. The BPC live-connection is available for the integration of BPC Embedded models with SAP Analytics Cloud (It is not available to BPC Standard models). It can be used in SAC stories, SAC Analytic Designer applications and Analysis for Office, edition for SAC , workbooks. With BPC Embedded Access Rights, users who only input via SAC Planning into BPC (Embedded) with BPC Live connection will no longer require a BPC Standard or Professional license. This change is:

Applicable to SAC live planning to BPC Embedded model deployment mode only (Note, BPC Standard model deployment mode does not support live planning access)

Available for BPC on-premise, PCE or PTO

Pertinent for BPC for BW Netweaver or BPC for BW/4HANA

Applies to SAC Planning Standard or Professional users (an SAC BI user can not publish data into BPC)

Includes ability to plan via Analysis for Office (included in the SAC Planning license)

For users requiring SAC BI only access to BPC data, this can be achieved via the BW Live connect (for which no BPC licenses are required)

How a customer can get BPC Embedded Access Rights

The customer must license at least a minimum quantity of BPC in order for administrators to create and maintain a BPC environment and the BPC Live Connection that is used by SAC to connect to BPC or BW-IP. Beyond that, leveraging the SAP Cloud Extension Policy (CEP) a customer is able shift maintenance cost to a SAP Analytics Cloud subscription.

In which customer situations BPC Embedded Access Rights are not applicable

As sated above, BPC Embedded Access Rights are currently available only for BPC Live connections. This also means that there can be some customer situations regarding BPC Licenses which are not covered by BPC Embedded Access Rights. Here are some of such scenarios:

BPC Embedded Access Rights are not available for BPC Standard models since BPC Live connection is not available for BPC Standard models

BPC Embedded Access Rights are applicable only for BPC Standard license and not for BPC Professional If a customer wants to add more BPC Professional users then the license policy for BPC Professional users will apply.

Customers using BPC Workflows are not covered by BPC Embedded Access Rights

BPC Embedded Access Rights are intended for planning scenarios using BPC Live connection and hence customers using BPC only for Consolidation will not be covered under BPC Embedded Access Rights

What about customers using BW-IP

BW-IP is an older Netweaver technology customers could use to build highly complex and bespoke planning applications. BW-IP is not available in BW/4HANA and hence BW-IP customers find themselves stuck on the older Netweaver 7.x platform. Often BW-IP customers use tools like BEx for user access. As BEx is end-of-life and not available in BW/4HANA again this becomes a barrier for customers.

While BW-IP is not available in BW/4HANA without BPC license, it is possible to upgrade and access the BW-IP models if the customer adopts BPC; creates a BPC model against the old BW-IP logic to be used in SAC with BPC Live connection. Therefore, with BPC Embedded Access Rights, BW-IP customers now have a way more simplified opportunity to move to BPC for BW/4HANA and preserve their BW-IP models, and then allow user access to these models via SAC Planning.

Where to get more details

More details about topics around BPC Embedded Access Rights are available at the following locations:

SAP Note 3150518 describing the BPC Embedded Access Rights

Details about how to set up BPC Live connection with Direct CORS connection

Details about how to set up BPC Live connection with Tunnel connection

Capabilities and limitations of BPC Live connection

Trigger Process Chain from SAC with BPC Live Connection

2022-09-22T07:15:38+02:00

We built a planning application in SAP Analytics Cloud using SAP BPC Live Connection. The requirement was for the users to be able to load the actuals data in the BPC System from the application and also get a real time status whether the data load got completed.

Since we have the Planning trigger in SAC Stories, we thought we could use that to trigger a process chain in the backend system. There is a very good blog related to this issue which we followed where we build a planning function using fox formula. Inside the fox formula you can call the function module to trigger the process chain.

You can read the link below for this :

https://blogs.sap.com/2015/07/08/how-to-trigger-a-process-chain-using-a-planning-function-in-sap-design-studio/

However with the above approach since we are going to trigger the planning sequence from SAC, we couldn't find any way to send back messages to SAC about the process chain status. It was becoming difficult for the users to check the latest status of the data load in SAC.

So while trying to search a better approach we realized that there are two standard planning function types provided by SAP for this purpose.

0RSPL_START_PROCESS - Start a Process Chain

0RSPL_GET_PC_LOG - Get Logs from a Process Chain

As shown below you can find the planning function types in BI Content under Function Type for Planning. When you use these for the first time, you need to activate them from the BI Content.

Once activated the Planning Function types are ready for use.

Now lets look at the step by step process to create the Planning sequence to trigger a process chain.

Since our planning function will have to based on an Aggregation Level, we need a Plan DSO and a Aggregation level as the first step. Create DSO and Aggregation level as shown below. You can create a Custom InfoObject to store Process Chain ID. The DSO is of type Direct Update, Planning enabled.

2. The next step is to create planning function on this aggregation level that we created.

Enter the Name of the Process chain in the parameter as shown below :

3. Now lets create a planning filters as shown below.

Enter the process chain name in the Planning Filter as shown below.

4. Once the planning function and planning filter is created, we have to create a Planning Sequence. Add the planning function and planning filter that we created before in the planning sequence.

Save the planning sequence and execute it. As shown below you will see a message that the Planning sequence executed without errors.

Go to RSPC and check the logs for the process chain to see if it got executed. As shown our process chain got executed below :

Now create another planning function and planning sequence to check the process chain logs.

5. To use this planning sequence in SAC, we will need a Model in SAC. So lets go to BPC Environment and create a model. You first need to create an environment for your project if you dont already have it, and then create the model.

Select the plan DSO now that we created before.

6. Now lets go to SAC and create a BPC Model from the BPC Live Connection. Create a sample query on the aggregation level as shown below and you can use that in the SAC Model. See below :

As shown below create a SAC Model from BPC Live Connection. In BPC Environment select the environment and the BPC model we created in previous step and then select the BW Query and click on ok and save the model.

7. Now create a blank story and add Planning Trigger Object as shown below.

Add a planning trigger in the story and select BPC Planning Sequence Trigger. Here select the model that we created in the previous step.

As shown above my planning trigger is added to the SAC Story. I added one more trigger for the planning sequence ZAGG_PC_PS1 for checking the logs.

Now go to view mode and click on the first planning trigger.

As shown you get a message that the planning sequence is executed without errors. This means that the process chain is executed in the backend. To check the status of the process chain click on the second planning trigger.

It gives the status of the process chain as ok which means the process chain executed successfully. If the process chain fails you can see the errors here and if the status is active it means the process chain is running. You can click the button multiple times to check the status of the process chain.

How Business Warehouse can help you in IBP Projects

2023-02-16T09:36:55+01:00

Introduction and Motivation

Currently, there are different projects related to Integrated Business Planning ongoing. One motivation could be to have a successor for APO (Advanced Planning and Optimization).

In case your system landscape contains a Business Warehouse system, you might be interested on how to utilize it in your IBP Projects. This question is exactly the scope of this blog.

Architecture

Reference Data for IBP

Most likely, the IBP system will have a direct connection to your ERP system for synchronization of some master data and some other things. When it comes to special requirements, the ERP system might not be the best source system to take and you will not be able to extract data in a granularity which can be digested by IBP. Let's think about the requirement to aggregate the reference data along a customer planning hierarchy. Instead of reinventing the logic in ERP or in IBP, you might like to reuse it from existing planning applications in Business Warehouse. This is just one example. You will have more harmonization and aggregation requirements for different areas of reference data in your project. For such cases, Business Wareshouse can be a very helpful system.

Most likely the level of detail for IBP will be something like:

Planning Customer

Planning Material

Calender Year

Calender Month

Plant

Sales Organization

Version

Quantity

The reference data might be on a very different level and it can be very painful to bring all data to a proper granularity without a Business Warehouse.

Some data might only be available in Business Warehouse, like external data from the market which you would like to use for your planning process.

Backwards Integration to ERP

But not only the integration of reference data is required. You will also most likely find the requirement to write data back from IBP to ERP. Let's take the COPA Module as an example and the retraction transactions KELC and KELR. You can't use those transactions in ERP together with IBP directly, as IBP does not allow you to implement BEx Queries.

You could use the Business Warehouse again to write data back from IBP to an aDSO in Business Warehouse first and consume it via BEx Queries and utilize the ERP transactions you already might have in place.

SAP Cloud Platform Integration for Data Services (CPI-DS)

Most probably you will also find CPI-DS in your IBP project. CPI-DS can be used to read e.g. the aDSO table, where you put the reference data in. It can also be used to trigger the loading process of the results of IBP into Business Warehouse.

On a very high level your architecture could look like the one in the following picture.

High Level Architecture

Summary

During the project preperation, it is very helpful to list all sources which should be integrated to support the process inside IBP. It might be helpful to use an existing Business Warehouse to collect, harmonize and aggregate the data to the needed granularity for IBP.

Be prepared for interfaces. Don't underestimate the effort to connect the systems and the integration between the systems.

Make sure you have clean master data and harmonized processes.

Accelerate Your Move from SAP BPC to SAP Analytics Cloud (SAC) for planning with a migration guide

2023-03-09T19:02:22+01:00

For the last more than 15 years, SAP Business Planning and Consolidaiton (SAP BPC) provided a rock-solid on-premise planning solution for customers. When organizations transitioned to cloud technology, SAP was able to satisfy that need with SAP Analytics Cloud, its flagship analytics and planning SAAS solution. Though SAP has promised customers using on-premise solutions that their investments are safe and secure as announced in its product strategy, many on-premise users themselves are facing a number of challenges such as

How do we drive maximum cost synergies to fund innovation

How do we better engage our employees to attract and retain top talent

How do we engage with Machine Learning and AI to help support planning

How do we collaborate with plans across enterprise

All these factors are leading the organizations to move to the cloud-based planning solution from their traditional on-premise solutions and SAP BPC is no exception. The easiest and smoothest transition for SAP BPC customers to cloud is SAP Analytics Cloud. With SAP Analytics Cloud, customers can leverage Planning and Analysis on a single solution. SAP Analytics Cloud provides a set of rich planning capabilities that allows organizations to plan across various lines of business, connecting operational to financial plans. SAP Analytics Cloud is always online with your most trusted data.

Now SAP provides a migration guide for customers who have deployed SAP BPC. This document also provides guidance (for Planning only – not for Consolidation) on how to integrate SAP Analytics Cloud with S/4HANA and SAP BW. This document covers topics such as dimensions and models, calculation logic, validation rules, reports, work status, security, audit etc. to name a few.

When you are ready to take the next step, you can get the details at SAP Note 3308697 or contact us at movebpc@sap.com to get the guide and learn more about using SAP Analytics Cloud for Planning to migrate your BPC investment to the Cloud and accelerate your business & financial transformation.

BW: Creation of custom KeyFigures InfoObject

2023-03-27T15:24:09+02:00

When you would like to extend your InfoProvider of some KeyFields which you will create on your own, you cannot use the standard procedure. Usually you would use Transaction FCOM_MET tool for extension, however in this case it is prohibited and you cannot do that this way. These steps need to be performed for ACDOCA/ACDOCP fields which are made for Unit or Quantity.

For creation a new KeyFigure InfoObject you need to use BW Modeling Tools in Eclipse app. In this app you will locate your system and open it. Then you need to right-click the system and choose: New -> InfoObject...

Creation of InfoObject

This will open pop-up screen, where you define your InfoObject. This can be done in several ways, depending on of what you need at the moment. As an example I will create InfoObject for new Quantity. You can assign it to your InfoArea, or to the Original Package /ERP/SFIN.

Definition of InfoObject

You can then see your new InfoObject under the InfoArea you chose. The configuration is up to you at this point. It is good to use the same configuration as it is for the delivered one. It might look like this:

After all of this is done, you can proceed into the backend to do mapping.

Open Transaction RSA1 and switch it to Edit Mode, so you can do changes. Select the InfoProvider you want to enhance of this field. It will open 2 new windows on the side. One if for selecting other fields, the other one is your InfoProvider. From the selection you can use the drag-and-drop function to enhance InfoProvider.

Selection of new InfoObject

Add the field into the desired location, in this case Quantity under KeyFields. Right-click the InfoObject and select "Provider-Specific Properties".

Here you can choose to which ACDOCA/ACDOCP field should be your InfoObject refered to (This might be completely different from the field I have chosen).

Assinging of ACDOCA/ACDOCP field.

All you need to do now, is to save this InfoProvider, activate it and then you will see your new KeyFigure InfoObject in InfoProvider.

When you will create your own Unit as well, you would need to reference it to this Quantity InfoObject, which you would do in Eclipse under: Aggregation - Referenced Characteristic.

Please share your feedback or thoughts in the comment section.

Follow me for more tips about BW or BPC in general, so I can create more post about these topics.

You can also follow BW Planning, post and answer questions (https://answers.sap.com/tags/369280904654660339247670897548678), and read other posts on the topic (https://blogs.sap.com/tags/369280904654660339247670897548678/) for more content.

You might suggest some topic, you would like to know more about in my DMs as well, so I know on which topics should I focus.

How to add Cost Center Hierarchy into CDS View selection screen

2023-03-31T03:52:38+02:00

In SAP Delivered CDS View for Cost Centers - Actuals/ Cost Centers - Plan/Actual, or even your own custom created CDS View, you might need to have Cost Center Hierarchy and Cost Center Node on the selection screen within WebDynpro version of the app. You can select Cost Center Hierarchy as an additional filter, but it will not be visible among other variables.

In order to be able to see Cost Center Hierarchy on selection screen, you will need to create your own CDS View, as you cannot modify SAP Delivered one. You can create copy of the CDS View C_COSTCENTERQ2001, which has the Cost Center Hierarchy already in the code, but it is commented out by default.

You will find this code under the Rows characteristic:

@AnalyticsDetails.query.axis: #ROWS  

IsStatisticalCostCenter,  

 

@AnalyticsDetails.query.variableSequence: 50

@Consumption.filter: { selectionType: #INTERVAL, multipleSelections: true, mandatory: false }

@AnalyticsDetails.query.totals: #SHOW

@AnalyticsDetails.query.axis: #ROWS

@AnalyticsDetails.query.display: #KEY_TEXT

CostCenter,

 

//@AnalyticsDetails.query.variableSequence: 81

//@Consumption.filter: {  selectionType: #HIERARCHY_NODE, multipleSelections: true, mandatory: false,

//                        hierarchyBinding : [    {type: #USER_INPUT, value: 'CostCenterHierarchy', variableSequence: 80 } ] }

//@AnalyticsDetails.query.displayHierarchy: #FILTER

//@AnalyticsDetails.query.totals: #SHOW

//@AnalyticsDetails.query.axis: #ROWS

//@AnalyticsDetails.query.display: #KEY_TEXT

//CostCenter as CostCenterChildNode,

//_CostCenter[1:ValidityEndDate   >= $parameters.P_KeyDate and 

//                    ValidityStartDate <= $parameters.P_KeyDate]._Text[1:Language = $parameters.P_Language].CostCenterName as CostCenterChildNodeName,

 

 

@AnalyticsDetails.query.variableSequence: 86

@Consumption.filter: {  selectionType: #HIERARCHY_NODE, multipleSelections: true, mandatory: false,

                                      hierarchyBinding : [  { type: #USER_INPUT, value: 'GLAccountHierarchy', variableSequence: 85 } ] }

@AnalyticsDetails.query.displayHierarchy: #FILTER

@AnalyticsDetails.query.axis: #ROWS

@AnalyticsDetails.query.totals: #SHOW

GLAccount,

_GLAccountInChartOfAccounts._Text[1:Language = $parameters.P_Language].GLAccountName,

When you create a copy of this view, or you will use your own, you will need to replace this part of the code for this one:

@AnalyticsDetails.query.axis: #ROWS  

IsStatisticalCostCenter,  

 

 

@AnalyticsDetails.query.variableSequence: 86

@Consumption.filter: {  selectionType: #HIERARCHY_NODE, multipleSelections: true, mandatory: false,

                        hierarchyBinding : [    {type : #PARAMETER, value : 'P_ControllingArea'}, {type: #USER_INPUT, value: 'CostCenterHierarchy', variableSequence: 85 }

                                            ] }

@AnalyticsDetails.query.displayHierarchy: #FILTER

//@Consumption.filter: { selectionType: #INTERVAL, multipleSelections: true, mandatory: false }

@AnalyticsDetails.query.totals: #SHOW

@AnalyticsDetails.query.axis: #ROWS

CostCenter,

_CostCenter[1:ValidityEndDate   >= $parameters.P_KeyDate and 

                    ValidityStartDate <= $parameters.P_KeyDate]._Text[1:Language = $parameters.P_Language].CostCenterName,

 

@AnalyticsDetails.query.variableSequence: 96

@Consumption.filter: {  selectionType: #HIERARCHY_NODE, multipleSelections: true, mandatory: false,

                                      hierarchyBinding : [  { type: #USER_INPUT, value: 'GLAccountHierarchy', variableSequence: 95 } ] }

@AnalyticsDetails.query.displayHierarchy: #FILTER

//@Consumption.filter: { selectionType: #INTERVAL, multipleSelections: true, mandatory: false }

@AnalyticsDetails.query.axis: #ROWS

@AnalyticsDetails.query.totals: #SHOW

GLAccount,

_GLAccountInChartOfAccounts._Text[1:Language = $parameters.P_Language].GLAccountName,

As you can see in the changed code, the part with single Cost Center was removed completely and Cost Center Hierarchy with Cost Center Node took its place. In Cost Center Hierarchy and GL Account Hierarchy is a line:

//@Consumption.filter: { selectionType: #INTERVAL, multipleSelections: true, mandatory: false }

This line is there in case, you would like to select it not as a Hierarchy and Node, but just a single selection of Cost Center or GL Account. If you would like to have a single GL Account for selection, you need to uncomment this line and comment these two lines in the code for GL Account:

@Consumption.filter: {  selectionType: #HIERARCHY_NODE, multipleSelections: true, mandatory: false,

                                      hierarchyBinding : [  { type: #USER_INPUT, value: 'GLAccountHierarchy', variableSequence: 95 } ] }

@AnalyticsDetails.query.displayHierarchy: #FILTER

These two lines for Cost Center:

@Consumption.filter: {  selectionType: #HIERARCHY_NODE, multipleSelections: true, mandatory: false,

                        hierarchyBinding : [    {type : #PARAMETER, value : 'P_ControllingArea'}, {type: #USER_INPUT, value: 'CostCenterHierarchy', variableSequence: 85 }

                                            ] }

@AnalyticsDetails.query.displayHierarchy: #FILTER

At the end, you will need to create your own Fiori Tile with this CDS View in it, to be able to run it in Fiori Launchpad.

The result will look like this in Fiori.

Cost Centers - Actuals with Hierarchy

Please share your feedback or thoughts in the comment section.

Follow me for more tips about BW or BPC in general, so I can create more post about these topics.

You can also follow BW Planning, post and answer questions (https://answers.sap.com/tags/369280904654660339247670897548678), and read other posts on the topic (https://blogs.sap.com/tags/369280904654660339247670897548678/) for more content.

You might suggest some topic, you would like to know more about in my DMs as well, so I know on which topics should I focus.

How to: Adding Profit Center Group into selection screen

2023-05-02T10:39:23+02:00

This guide works only for BW Query which starts with /ERP/SFIN_***

Profit Center Group is not available by default in BW queries for Profit Center as:

/ERP/SFIN_V01_Q2701 – Profit Centers - Actuals

/ERP/SFIN_M01_Q2701 – Profit Centers – Plan/Actual

/ERP/SFIN_M01_Q2702 – Profit Centers – Plan/Actual YTD

/ERP/SFIN_M01_Q2703 – Profit Centers – Plan /Actual with Currency Translation

For enabling this field in BW queries you need to do several steps, before you can create/update WebDynpro Configuration for selected app.

1)SAP Note 3308885

This Note is adding two additional variables for the backend. Without this Note in your system, this guide will not work.

2)Eclipse – BW Modeling Tools

First you need to locate the query you want to modify(for purpose of example I have created my own as a copy from Profit Center – Actuals)

When you open the query, you need to switch to InfoProvider selection, so you are able to choose from it, but first in case you do not want to select single Profit Center anymore, you can delete variable which is already assigned under Filter: Fixed Values in /ERP/PROFTCTR (Only if you created a copy, you might have no variable there at all, which is also fine)

Then select /ERP/PROFTCTR, open Characteristic Value Variable, right-click to open pop-up and select New Variable

Then you need to create 2 new variable which have to be named /ERP/N_PROFTCTR01 and /ERP/H_PROFTCTR01 as they are being called by the Function Module with the same label.

You can use your own package and Description, the rest must be the same as below.

Creation of New Variable

After those two new variables are created, you then need to assign it to /ERP/PROFTCTR in the Filter of your query.

Double click on /ERP/PROFTCTR in Filter: Fixed vaule to open next selection. There you need to open Hierarchy Node Variables, select your new variable and click on Change…

Here you will assign Hierarchy Variable to the Node.

Then you need to just drag it to the Filter on the right and it will be assigned to /ERP/PROFTCTR. Filter definition should look the same as on the screenshot.

Afterwards you need to click on /ERP/PROFTCTR, select Hierarchy tab and do the same as for the Node. You will select the variable and when you do so, it will switch the flag of Activate Hierarchy to On.

At the end, you should be able to see Profit Center Group as part of your query in Transaction RSRT.

Now all you need to do is maintain WebDynpro configuration for your app, to assure, that the field is available for you in Profit Center reports.

You can use this guide to enable Profit Center Groups in any BW Query, as it is not limited just for Profit Centers Apps.

Please share your feedback or thoughts in the comment section.

Follow me for more tips about BW or BPC in general, so I can create more post about these topics.

You can also follow BW Planning, post and answer questions (https://answers.sap.com/tags/369280904654660339247670897548678), and read other posts on the topic (https://blogs.sap.com/tags/369280904654660339247670897548678/) for more content.

You might suggest some topic, you would like to know more about in my DMs as well, so I know, on which topics should I focus.

BW TPM - Issues and Resolution

2023-08-22T12:05:53+02:00

Everytime I work on Trade Promotion Management, I am always in awe of how beautifully the product is designed and how seamlessly it works integrating different systems like CRM, BW and S/4 HANA.

Having said that I am also bogged down with the multiple issues that come up when you are configuring the Trade Management CRM UI and trying to make all the pieces work. And even if you have worked on it in the past, every issue comes with its own set of challenges and you feel helpless at times not knowing what to do next. In the recent project I did as well, I faced multiple issues and thankfully I had the help from some of my peers who have been through this journey in the past as well as the product team who used to guide us on the way forward.

There are two helpful blogs below already on the topic which will guide you on your Trade Management BW journey.

https://blogs.sap.com/2019/01/03/tips-and-tricks-while-working-on-bw-tpm/

https://blogs.sap.com/2022/07/28/lessons-learned-while-working-on-bw-planning-tpm-project/

However, these blogs might be on slightly older versions of Trade Management. I have tried to document the issues we faced while working on Trade Management 4.0, FP6 and the resolution with the hope that it would be helpful for others who are in the same journey.

While creating a Plan in the CRM UI Screen, we got below BSP error.

Resolution:

In SU3 maintain the decimal settings. Change it from 1.234.567,89 to 1,234,567.89 in both CRM and BW systems. The decimal settings should be the same in CRM and BW system for your use ID.

2. PSM Initialization Failed for Object due to synchronization error

This is actually a common error which can occur due to multiple reasons. But usually its because the sync method is not able to create the combinations of the Plan data in the BW DSO and so the query read fails as there is no data.

When we debugged this, found that the Sync method was failing with below error.

Resolution:

As per the error, the Sales organization has not been mapped to fiscal year variant. The reason was that the DSO /JBPB/SAFV_M was not loaded.

The system checks the mapping of Sales Organization and Fiscal Year Variant in this DSO. The issue was resolved after loading data in this DSO.

3. Roll-in Planning Function not working

The reason was in the Code for Roll-in Planning function the data from /JBPB/IPLAN DSO was not getting read. The selections were passed correctly and data was there in the DSO, but it was still not getting read.

Then we found that there is a customizing setting in which we have to enable the Plan DSOs to be used in Planning Engine.

When we tried to maintain the setting here, we got a short dump.

Resolution:

We found one OSS Note (2899115) that has to be implemented to fix this, but since we did not have much time and the Note was getting updated, we decided to write a custom program and add the entries in the below standard table directly.

After updating this, the data started getting read from the /JBPB/IPLAN DSO in the planning function.

4. Short Dump while trying to activate DSO /JBPB/IPRSTG

While trying to activate DSO /JBPB/IPRSTG we were getting a dump in the development system.

The reason is the DB connection that is maintained in RS2HANA_View transaction code is missing from DBCO transaction.

Resolution :

Below is the OSS Note that mentions the solution.

https://launchpad.support.sap.com/#/notes/3212374

After maintaining the DB connection the issue was resolved and we could successfully activate the DSO /JBPB/IPRSTG.

5. Trusted RFC Connection not working

When we are working on TPM, we need to set up two RFC Connections in the CRM system. One will be the usual RFC connection that we need to create for the source system connection in BW. The other RFC connection will be a trusted RFC. The trusted RFC connection will have a Current user selected in the settings which means that whenever the data is read in CRM UI from BW, the current user is used instead of the background user.

So whenever we want to debug any errors in the CRM UI, we can easily set breakpoints with our own user ID in the BW system, if we use the trusted RFC. If we do not use the trusted RFC and use the other generic one, then we have to debug with the common background user which will be same for everyone, so other people using the system will run into the breakpoints that you set.

Usually the basis team will create trusted RFC with the name *_DEBUG eg. BWCLNT100_DEBUG.

You need to maintain this trusted RFC in the parameters in SU3 transaction in CRM system. The system will use the trusted RFC for the communication with BW only if you maintain it in the parameters in SU3. If you do not maintain it then common RFC will be used.

Resolution :

Once this is updated, you can perform debugging and troubleshooting with your own ID.

If your basis team needs any help with trusted RFC configuration you can use the below mentioned blog which is very helpful.

Setup a trusted RFC connection #sapadmin | SAP Blogs

After applying OSS Note above and updating user parameters to use trusted RFC, I was able to debug with my user ID.

6. Total Promotion Investment Value was not matching with Reserved/Prereserved values in the Fund usage

The issue was with the standard BW query /JBPB/C_PRM_PROMO_KPI_Q004. This query is used for the calculation of the Total Promotion Value that is displayed on the right side of the promotion screen. The calculation view in the standard query is not used now and should be replaced with the DSO /JBPB/ILTA.

Resolution:

So we created a custom query which is a copy of the standard query and replaced the Infoprovider with the standard DSO /JBPB/ILTA. Also remember to update the Z query in your config in CRM to replace the Promo KPI monitor standard query with the Custom query.

It worked fine after making the above changes. The prereserved value was populated along with the Total Promo Investment in the Promo KPI Monitor screen.

7.In promotion screen, Tree View was not loading. Even in Tree view we could see flat view data.

The problem was we were using custom Queries for Promotions that we had copied.

And there is some standard code to change Query filters which was executing only for standard queries. We have to update this code to implement it for the Custom queries as well that we create

Resolution:

Create custom Badi Implementation for BADI IMP_QUERY as shown below and create Custom Class which will be a copy of the standard class

Also activate this BADI in SPRO.

8. When we tried to create a new Version for Operational Plan, it was throwing BW planning function errors

When we debugged and checked the BW Planning function for Version Creation was failing because value '9' did not exist in /JBPB/SCINDIC InfoObject.

Resolution:

The solution was simple that we had to maintain master data for the Source Indicator Object. This should have values 1, A, B, C and 9.

So we maintained the value 9 as below :

After maintaining the master data, we were able to successfully create a new version for Operational Plan.

9. When we tried to compare different versions then we were getting below error which says Invalid Query

On checking more we found that the BW Queries for Version Comparison were not active in the BW system.

Below are the queries which we need to activate for Version Comparison.

/JBPB/C_VER_COMP_PNL	Version Comparison PNL Query
/JBPB/C_VER_COMP_PNL_PROD_TREE	Version Comparison PNL Product Tree

While activating the query in BI Content we were getting following error:

Resolution:

We found an OSS Note for this issue which is below

https://me.sap.com/notes/2861374/E

This OSS Note is applicable to Support pack level

SAPK-40003INTMAB. But our system was on

SAPK-40002INTMAB.

But as mentioned in the OSS Note that we needed to create assignment for the field

S_RRSPPR" in the Composite Provider /JBPB/C_VER. Since this assignment was missing in our system, I created that and then we tried to install the Query.

After this step, the Queries got installed successfully.

The Plan Version Comparison screen was loading fine after this.

10. Unable to assort products, product assortment is not saved in BW. (This issue came in the Quality System)

And when you debug you can figure out that the planning function to create the combinations in the Synchronize method is failing.

See below error message.

Resolution:

Post this we maintained the value 1 in the master data for InfoObject /JBPB/SCINDIC in both attributes as well as text and this issue was resolved.

Further we found that the combinations in the IPLAN Dso were still not created. We found the assortment entries getting stuck in CRM system in SMQ2.

Then we found that in one of the tables the entry was missing in Quality system.

We maintained the below entry in the table RSADMIN using the program SAP_RSADMIN_MAINTAIN.

After doing above steps the issue was resolved and data started getting saved in the IPLAN DSO.

I hope that these pointers will help everyone of us who are working on BW Trade Management.

UNCAUGHT_EXCEPTION ABAP Dump While Opening Infoobject in SAP BW system (7.50)

2023-08-30T14:38:16+02:00

There might come a time when you have perhaps preformed SP level upgrade of your BW system and you notice some objects are throwing ABAP dumps when you try to open them. If these are standard objects then there are ways you can fix the issue.

ABAP dump when trying to open object in BW system

Note: First identify if the issue happened in any of the lower environment i.e. DEV, QA etc. If the issue occured in the lower environment also then it could very well be that the object is inconsistent hence you might need to fix the same and then do a transport to the next target.

However if none of the lower environment faced this issue and only PRD then following is the option for you to follow in such case.

In my case after system upgrade when I try to option the Active/Delivery version of the InfoObject or execute Attribute change run of my object 0PM_ORDER I was getting the above mentioned dump in ST22. This was happening in SAP NetWeaver 7.5 SP27.

How to Fix this:

From the ST22 dump information, you need to find field L_S_DTA_PRO-IOBJNM and it will give you the object in question here.

Reinstall the InfoObject from BI Content using (tcode - RSOR) and removing checkbox "Match (X) or Copy". Please note that the Active version will be overwritten.

See reference SAP note 3106415 - InfoObject activation error: Nav. attribute &1 for characteristic &2 as InfoProvider cannot be used

Other options:

If you try the above and it still dumps then it is very likely that in the job log you will see this object is probably having dependencies with other objects or have dependencies from custom characteristics. In that case you will see messages like below:

InfoObject XXXXXXX is used in transfer rules (M) of characteristic XXXXXXX.

InfoObject XXXXXXX is used in transfer rules (M) of characteristic XXXXXXX.

....

Therefore, the proper way to fix the issue would be to re-transport 0PM_ORDER and its dependent objects, so the references are fixed in target system. Re-installing form BI Content will not work here because you could have other dependencies from custom characteristics aswell.

Hope this helps.

Custom Planning Solution in BW/4 HANA

2023-08-31T13:48:32+02:00

Introduction:

This article covers how to create custom planning solution BW/4 Hana. Its relevant for BPC Embedded or BW-IP (integrated planning).

Basic knowledge of BW IP, HANA and programming is required to understand the concept.

BPC embedded mainly uses BW-IP/PAK for planning. It has many standards functions available (e.g. Copy, Distribution, Repost, etc. ). But, there are many scenarios where the allocation/distribution logic can't be fulfilled using standard planning functions available. In that case we generally go for custom planning solution.

Generally in real-time scenario, there will be multiple levels of allocations also having multiple dimensions. In this article we will be discussing how to create a simple end to end custom planning solution and how to build the logic including error handling. In this scenario, we are going to use the same aDSO for transaction data as well as for allocated data. In real scenario, we can have different aDSO for transaction data and planned data.

Main Content:

Problem Statement:

Source data containing below information.

Costcenter Driver

Scenario	Calmonth	Control Area	Source CC	Target CC	Factor
ACT	202304	E001	AEA1001002	ABCDULSGR1	0.2
ACT	202304	E001	AEA1001002	ABCDULSGR2	0.4
ACT	202304	E001	AEA1001002	ABCDULSGR3	0.15
ACT	202304	E001	AEA1001002	ABCDULSGR4	0.25
ACT	202304	E001	AEA1001004	ABCDULSGR2	0.5
ACT	202304	E001	AEA1001004	ABCDULSGR3	0.3
ACT	202304	E001	AEA1001004	ABCDULSGR4	0.1
ACT	202304	E001	AEA1001004	ABCDULSGR5	0.1

Transaction Data

Scenario	Calmonth	Costcenter	Audit ID	Amount
ACT	202304	AEA1001002	A_001	100
ACT	202304	AEA1001004	A_001	200

Audit ID A_001 refers to source data (transaction data).

Audit ID A_002 refers to allocated data.

CC Master

CO_AREA	COSTCENTER	OBJVERS	DATETO	DATEFROM	OBJ_CURR	PROFIT_CTR
E001	ABCDULSGR1	A	31-12-9999	01-01-2017	USD	ABCDULSGR1
E001	ABCDULSGR2	A	31-12-9999	01-01-2017	USD
E001	ABCDULSGR3	A	31-12-9999	01-01-2017	USD	ABCDULSGR3
E001	ABCDULSGR4	A	31-12-9999	01-01-2017	USD	ABCDULSGR4
E001	ABCDULSGR5	A	31-12-9999	01-01-2017	USD	ABCDULSGR5

The requirement is to allocate the amount to receiver costcenters based on driver value. It will generate the allocated values with different audit ID. It should consider the profit% value entered by user as well.

Error handling: System should also validate if any of the receiver costcenter is not assigned to profit center. It should throw error message.

Parameter handling: User will pass the profit percentage value (%) as parameter. It will be used in the allocation to multiply all allocated amounts.

Solution:

Driver Data:

Create a planning enable aDSO for costcenter driver. Enable hana view generation.

Create the aggregation level and input sheet. Update the CC driver values as mentioned before.

Update the CC master data as mentioned before.

Transaction Data:

The below objects will be needed.

Create the aDSO for transaction data.

Create aggregation level.

Custom class

Planning function type using custom class

Planning function.

Planning sequence and filter.

aDSO for transaction data:

Aggregation level:

Create the aggregation level on top of transaction data aDSO. Pick all the fields from aDSO.

Custom Class

Create a Z empty class with interface IF_RSPLFA_SRVTYPE_IMP_EXEC.

Planning Function Type:

Create new planning function type using the class created above. Add a parameter as profit % (numeric value). info object 0SPL_TARGET is used.

Planning Function:

Create a planning function based on the planning function type. use the input ready formula variable for the profit %.

Planning function Filter:

Planning Sequence:

Logic Build:

Run the program RSPLS_SQL_SCRIPT_TOOL. Provide the parameters like below and execute. System will give code dump. Copy the code to the class created before.

Adjust the code as mentioned below. System generates the template code. The logic needs to be built in MY_HANA_PROCEDURE method. Its take into consideration of all the parameters defined for the planning function type.

CLASS zcl_cc_to_cc_demo DEFINITION

  PUBLIC

  FINAL

  CREATE PUBLIC .



  PUBLIC SECTION.

* Type for aggregation level ZAL_SRCAL

    TYPES: BEGIN OF y_s_zal_srcal,

             calmonth   TYPE /bi0/oicalmonth,

             costcenter TYPE /bi0/oicostcenter,

             co_area    TYPE /bi0/oico_area,

             zc_audit   TYPE /bic/oizc_audit,

             zc_scnro   TYPE /bic/oizc_scnro,

             currency   TYPE /bi0/oicurrency,

             amount     TYPE /bi0/oiamount,

           END OF y_s_zal_srcal.

    TYPES: y_t_zal_srcal TYPE STANDARD TABLE OF y_s_zal_srcal.

    INTERFACES if_amdp_marker_hdb.

    INTERFACES if_rsplfa_srvtype_trex_exec.

    INTERFACES if_rsplfa_srvtype_imp_exec.

    CLASS-METHODS: my_hana_procedure IMPORTING VALUE(i_view)   TYPE y_t_zal_srcal

                                               VALUE(i_profit) TYPE /bi0/oispl_target

                                     EXPORTING VALUE(e_view)   TYPE y_t_zal_srcal

                                               VALUE(e_msg)    TYPE if_rspls_sql_script=>y_t_msg

                                     RAISING   cx_amdp_error.

  PROTECTED SECTION.

  PRIVATE SECTION.

ENDCLASS.

CLASS zcl_cc_to_cc_demo IMPLEMENTATION.

  METHOD if_rsplfa_srvtype_trex_exec~trex_execute.

    DATA: l_r_sql_script   TYPE REF TO if_rspls_sql_script,

          l_procedure_name TYPE string,

          l_t_iobj_param   TYPE if_rsr_pe_adapter=>tn_t_iobj_param.

    l_r_sql_script = cl_rspls_session_store_manager=>get_sql_script_instance( i_r_store = i_r_store ).

*   The method if_rspls_sql_script~get_parameter_values returns a table of parameters

*   with the values given in the function definition

    l_r_sql_script->get_parameter_values(

      EXPORTING

        i_r_param_set             = i_r_param_set

        i_para_name_for_procedure = 'HANA_PROCEDURE_NAME'

      IMPORTING

        e_procedure_name          = l_procedure_name

        e_t_iobj_param            = l_t_iobj_param ).

*   The function parameter given mehtod paramenter i_para_name_for_procedure

*   will not be returned in the table e_t_iobj_param but the value of this

*   function parameter will be returned int the mehtod parameter e_procedure_name

*   This mechanisme can e.g. be used to define function specific SAP-HANA-procedure names.

*   Other examples to get the name of the SAP-HANA-procedure name which will be called can be

*     - you use the technical name of the planning function type:

*     - or you simply give the SAP-HANA procedure name in a string:

    l_procedure_name = 'ZCL_CC_TO_CC_DEMO=>MY_HANA_PROCEDURE'.

    r_s_view-view = l_r_sql_script->execute_sql_script(

        i_view                  = i_view

        i_t_iobj_param          = l_t_iobj_param

        i_proc_name             = l_procedure_name

        i_sql_script_returns_ai = abap_true

        i_r_msg                 = i_r_msg ).

  ENDMETHOD.

  METHOD if_rsplfa_srvtype_trex_exec~init_and_check.

    e_trex_supported  = rs_c_true.

  ENDMETHOD.

  METHOD my_hana_procedure BY DATABASE PROCEDURE FOR HDB LANGUAGE SQLSCRIPT

*                           For Options and declarations check the AMDP documentiation (ABAP Managed Database Procedure)

                           OPTIONS READ-ONLY

*                           OPTIONS SUPPRESS SYNTAX ERRORS READ-ONLY. "

                           USING /BI0/QCOSTCENTER.

    DECLARE lv_count INTEGER;

* ERROR HANDLING *

    lt_invalid = SELECT a."0RESP_CCTR" as cctr

                   FROM "_SYS_BIC"."system-local.bw.bw2hana/ZAD_CCDRV" as a

                   JOIN "/BI0/QCOSTCENTER" as b

                     ON a."0RESP_CCTR" = b.costcenter

                    AND a."0CO_AREA" = b.co_area

                 WHERE b.profit_ctr = '';

    SELECT COUNT (*) INTO lv_count FROM :lt_invalid;

    IF :lv_count <> 0 THEN

          e_msg = SELECT * from :e_msg UNION

                  SELECT '00' as msgid,

                         'E' as msgty,

                         '001' as msgno,

                          'Profit Center is missing' as  msgv1,

                          '' as  msgv2,

                          '' as  msgv3,

                          '' as  msgv4

                     FROM dummy;

           RETURN;

    END IF;

* ALLOCATION *

    e_view = SELECT * FROM :i_view where zc_audit = 'A_001'

             UNION ALL

             SELECT a.calmonth,

                    b."0RESP_CCTR" as costcenter,

                    b."0CO_AREA" as co_area,

                    'A_002' as zc_audit,

                    a.zc_scnro,

                    a.currency,

                    (( a.amount * b."0RSPL_FCWHT" )* (1+:i_profit)) as amount

               FROM :i_view as a

               JOIN "_SYS_BIC"."system-local.bw.bw2hana/ZAD_CCDRV" as b

                 ON a.calmonth = b."0CALMONTH"

                AND a.co_area = b."0CO_AREA"

                AND a.costcenter = b."0REQU_CCTR";

  ENDMETHOD.

ENDCLASS.

Execution:

First convert the aDSO to load mode. Then load the transaction data as mentioned before in manage datastore (BW cockpit). Convert the aDSO to plan mode.

Run1: (Verify the profit center)

System will throw error as ABCDULSGR2 costcenter is having blank profit center.

Run2: Allocation test

Update the profit center field of ABCDULSGR2 with any value. Then run the planning sequence with same selection. After execution save the plan buffer.

verify the values in LISTCUBE Tcode for the aDSO. The source values got allocated to receiver costcenters with profit of 8%.

Conclusion:

In this article we learnt the below things.

How to create a Custom planning function using AMDP.

How to handle error validation in planning function.

How to pass parameter to a planning function and how to use in the logic.

How to write the logic in AMDP planning method.

How to create end to end solution for custom solution in planning with all BW planning objects and AMDP class.

How to: Extension of CDS Views

2024-01-29T13:28:37.153000+01:00

There exist multiple alternatives for enhancing CDS Views for Analytical applications, including those such as Cost Centers - Actuals, Cost Centers - Plan/Actuals, amongst others.

As each of our inquiries consistently functions in coordination with either I_JournalEntryItemCube or I_ActualPlanJournalEntryItemCube, these cubes necessitate extension to efficiently integrate with your specific fields within the aforementioned applications.

CDS Query (object)	CDS Query (2C+SQL View)	CDS Query WebDynpro Configuration	App ID
C_CostCenterQ2001	CFICOSTCTRQ2001	FIS_FPM_OVP_IPACTCC	F0963
C_CostCenterPlanActQ2001	CFICCPLANACT2001	FIS_FPM_OVP_IPPLANACTCC01	W0081
C_ProfitCenterQ2701	CFIPROFCTRQ2701	FIS_FPM_OVP_IPACTPC	F0959
C_ProfitCenterPlanActQ2701	CFIPCPLANACT2701	FIS_FPM_OVP_IPPLANACTPC01	W0079
C_MarketSegmentQ2501	CFIMARKSEGMQ2501	FIS_FPM_OVP_IPACTMS	F0960
C_MarketSegmentPlanActQ2501	CFIMSPLANACT2501	FIS_FPM_OVP_IPPLANACTMS01	W0078
C_ProfitAndLossQ2901	CFIPROFLOSSQ2901	FIS_FPM_OVP_IPACTPL	F0958
C_ProfitAndLossPlanActQ2903	CFIPLPLANACT	FIS_FPM_OVP_IPPLANACTPL03	F1710
C_FunctionalAreasQ2801	CFIFAQ2801	FIS_FPM_OVP_IPACTFA	F1583A
C_FunctionalAreaPlanActQ2801	CFIFAPLANACT2801	FIS_FPM_OVP_IPPLANACTFA01	W0077
C_InternalOrderPlanActQ2101	CFIIOPLANACT2101	FIS_FPM_OVP_IPPLANACTIO01	W0076
C_SalesOrderQ2301	CFISALESORDQ2301	FIS_FPM_OVP_IPACTSO	F1582A
C_ProjectQ2201	CFIPROJECTQ2201	FIS_FPM_OVP_IPACTPR	F0961
C_ProjectPlanActQ2201	CFIPRPLANACT2201	FIS_FPM_OVP_IPPLANACTPR01	W0080

Custom Fields and Logic
The first option is to use the Fiori App Custom Fields and Logic where you can create your field, which will be afterwards present in table ACDOCA/ACDOCP and the Query you select. For this, you will need to know Business Context. You can use FINS_JOURNAL_ENTRY_ITEM as a Business Context and then fill in the rest such as Label, Type, Length etc.

Once the field is generated, you can enable it for CDS Views and select only those, where you would require this field for reporting.

All you need to do now is to Publish the changes and the field is available in our reporting apps.

In case you change your mind in the future, or you need to extend some other query, you can use the tab Data Source Extension in the app, select the query you want to extend, name the CDS VIew and then you can select any fields already present in I_JournalEntryItemCube or I_ActualPlanJournalEntryItemCube. The same applies when the field is present in the Cube, but not in the query itself as the query contains only some basic characteristics, but not all of them.
Extend the already created field in ACDOCA/ACDOCP

The Fiori App Custom Fields and Logic cannot offer you an extension based on fields, which are already present in the ACDOCA/ACDOCP table.
You will first need to enable your custom fields which start on ZZ_ or YY_ with transaction SCFD_EUI(see SAP Note 2672370).
This will create a connection to the Custom Fields and Logic App. You might see different Business Contexts as it is taken directly from the created field. You do not need to worry as Accounting: Market Segment can be used as well. The most important is if you are then able to select I_ActualPlanJournalEntryItemCube or I_JournalEntryItemCube from the list to enable usage.
Once the process is done, the field will be visible in Custom Fields and Logic under Custom Fields, where you can select it modify the usage and continue with the first step.
Using a field delivered by SAP, but not available in any CDS View Cube

There are fields in tables ACDOCA/ACDOCP which are not available in the CDS Cubes I_JournalEntryItemCube, I_ActualPlanJournalEntryItemCube. For this purpose, you need to follow these steps:
1. A CDS view that selects all of your required fields from your database table. Data Source Extension does not support the selection of fields in database tables, only CDS views can be selected as source.
2. This CDS view must be registered and released in transaction SCFD_REGISTRY. This is required to ensure that system upgrades do not break the extension (lifecycle stability)

For more information see another SAP Blog:
https://community.sap.com/t5/enterprise-resource-planning-blogs-by-sap/adding-field-in-standard-fiori-apps-of-s-4hana-with-custom-fields-and-logic/ba-p/13443650

4. Extension of Import Financial Plan Data

You want to use the Fiori App: Import Financial Plan Data with your custom fields, but this is not possible as the field is not present in C_GenericPlanQ3001. Once you do an extension for this CDS View, you will be able to import data for your custom field.

5. Extension of API A_CostCenter

You may come across an extension of API CDS View for SAP Analytical Cloud or any other purpose. The process is the same.

This can be extended in two ways.

The first way is to use the Fiori App: Custom Fields and Logic. In this app, you will create a completely new field, which will be added to the CSKS table (Master Data Cost Center) as well as in CDS View E_COSTCENTER, A_COSTCENTER and others, depending on what you choose.

The second option is to choose a field, which is already in the CSKS table and can be either your new custom-made or some other which cannot be seen within the API.

Extension in this case works the same way as with Custom Fields and Logic, except for the fact you need to create the code on your own. First, you need to extend the E_COSTCENTER of your new field and activate it. This will enable this field for I_COSTCENTER which is Master Data view on the table CSKS.

As a second step, you need to extend the A_COSTCENTER, which is the API for the Master Data. This will add the selected field to the Service API_COSTCENTER and enable it for reporting.

The code for the CDS Extension will look like this:

@AbapCatalog.sqlViewAppendName: 'Z_TEST'
extend view E_CostCenter with ZFO_EXTENSIOM
{
Persistence. verak as verak
}

@AbapCatalog.sqlViewAppendName: 'Z_TEST_A' 
extend view A_CostCenter with ZFO_EXTENSION_A
{
_Extension.verak as Z_VERAK
}

Due to the different syntax in both CDS Views, you need to use:

Persistence for the E_COSTCENTER (This needs to be extend first)
_Extension for the A_COSTCENTER

Please share your feedback or thoughts in the comment section.

Follow me for more tips about BW or BPC in general, so I can create more posts about these topics.

You can also follow BW Planning, post and answer questions (https://answers.sap.com/tags/369280904654660339247670897548678), and read other posts on the topic (https://blogs.sap.com/tags/369280904654660339247670897548678/) for more content.

How to trigger PaPM function from Analysis for Office

2024-02-13T09:47:40.567000+01:00

Let me share with your how to call PaPM function from Analysis for Office step-by-step.

Scenario allows user to update workbook by clicking on the button “Reconcile”. Button triggers remote call PaPM function by Function ID with parameters from workbook. In this case, variable “Planning version” value passed to PaPM function as selection fields.

To carry out into practice this scenario it is necessary proceed next steps:

Create the PaPM environment and functions for processing
Create the functional module additionally processing variables from workbook
Create the set of BW objects to realize the planning function
Create Macros to call the planning function

I describe each of them bellow in details.

1. Creating PaPM environment

My PaPM environment assumes reconciliation between two Model BW, implemented with Join and Writer function. Rules restricted by SELFLD0 and SELFLD1 fields, which are BW info-objects. SELFLD1 “Planning version” has a variable ZV_MSM_SELFLD1_01, which used in workbook. (SAP Help: SAP Profitability and Performance Management )

2. Creating the Functional Module

The functional module creating is carried out in thansaction SE37. Easy ABAP code allows implementing the necessary rules to construct the parameters string, passed to the standard functional.

FUNCTION ZNXI_RUN_BY_SELFLD1_FOX
  IMPORTING
    VALUE(I_ENV_ID) TYPE /NXI/P1_DTE_ENV_ID
    VALUE(I_VER) TYPE /NXI/P1_DTE_VER
    VALUE(I_FID) TYPE /NXI/P1_DTE_FID
    VALUE(I_PROC_ID) TYPE /NXI/P1_DTE_PROC_ID OPTIONAL
    VALUE(I_SELFLD1) TYPE /BIC/OISELFLD1 OPTIONAL
  EXPORTING
    VALUE(E_EXPTN) TYPE I. "Type’s used to easy access in FOX


  TYPES:
    BEGIN OF ls_AUXSTRC,
      /bic/SELFLD0 TYPE /bic/oiSELFLD0, "Dependent selection field
      /bic/SELFLD1 TYPE /bic/oiSELFLD1, "Selection field from Workbook
    END OF ls_AUXSTRC.

  DATA:
    l_selfld1 TYPE /BIC/OISELFLD1 VALUE '',
    l_pckg_sel TYPE /NXI/P1_DTE_PACKAGE_SEL VALUE '',
    l_tab_msg  TYPE BAPIRET2_TAB.

    E_EXPTN = 0. "OK execution by default

    IF I_ENV_ID IS INITIAL OR I_VER IS INITIAL OR I_FID IS INITIAL.
        E_EXPTN = 1. "Must be defined
        RETURN.
    ENDIF.

    IF I_PROC_ID IS INITIAL.
        l_selfld1 = I_SELFLD1. "If proccess wasn’t defined, selection field should be 
    ENDIF.

    IF l_selfld1 IS NOT INITIAL.
     SELECT SINGLE * FROM MYRELTBL INTO @DATA(ls_AUXSTRC)
      WHERE /BIC/SELFLD1 = @I_SELFLD1.

      CONCATENATE 'SELFLD0=( SELFLD0 = ''' ls_AUXSTRC-/bic/SELFLD0
        ''');SELFLD1=( SELFLD1 = ''' ls_AUXSTRC-/bic/SELFLD1 ''')' INTO l_pckg_sel.
    ENDIF.


    CALL FUNCTION '/NXI/P1_FW_RUN_FUNCTION_PC'
    EXPORTING
      i_env_id           = I_ENV_ID
      i_ver              = I_VER
      i_fid              = I_FID
      i_proc_id          = I_PROC_ID
      i_package_sel      = l_pckg_sel
      i_run_type         = 'RUN'
      i_rspc_synchronous = 'X'
      i_execute_post_run = 'X'
    IMPORTING
      e_tab_msg          = l_tab_msg.

IF l_tab_msg IS NOT INITIAL.
    E_EXPTN = 2. "Execution with errors
    RETURN.
ENDIF.

ENDFUNCTION.

To allow using the function ZNXI_RUN_BY_SELFLD1_FOX inside the FOX script, it should be declared in table RSPLF_FDIR via transaction SM30.

3. Creating the set of the BW objects to realize the planning function

The blog post How to Trigger BW Process Chains from Analysis for Office explains clearly and in detail how to create the set of objects for planning. As a result, set of ADSO ZNXIDZ20, Composit Provider ZNXIVZ20, Aggregation ZNXIAZ20 are created.

In my case, ADSO ZNXIDZ20 consists of combination of standard info-objects /NXI* and Info-object SELFLD1, which store the selection filed value. Using SELFLD1 gives easy access to the necessary type within the FOX script, described below.

The Planning function ZNXAZ20_F001 is a formula type function (0RSPL_FORMULA) with the next configuration:

The following FOX script inside the planning function ZNXAZ20_F001 looks like bellow.

DATA LV_ENV TYPE /NXI/ENV_ID.
DATA LV_VER TYPE /NXI/VER.
DATA LV_FID TYPE /NXI/FID.
DATA LV_PS_V TYPE SELFLD1.
DATA LV_ERR TYPE I.

LV_FID = VARV( 'ZV_MSM_NXIFID_01' ).
LV_PS_V = VARV( 'ZV_MSM_SELFLD1_01' ).
LV_ENV = VARV( 'ZV_MSM_NXIENV_01' ).
LV_VER = VARV( 'ZV_MSM_NXIVER_01' ).

CALL FUNCTION 'ZNXI_RUN_BY_SELFLD1_FOX'
EXPORTING I_ENV_ID = LV_ENV I_VER = LV_VER I_FID = LV_FID I_SELFLD1 = LV_PS_V
IMPORTING E_EXPTN = LV_ERR.
IF LV_ERR <> 0.
  MESSAGE E000( 0 ) WITH 'Error! Watch Application Monitor for details.'.
ENDIF.

4. Creating Macros to call planning function

And the last but not least, Workbook macros for Reconcile button should be defined.

Add Planning function ZNXAZ20_F001 to workbook with alias PF_1. Constant for Function ID and variable Planning version are defined on hidden Tech page:

After that, add macros code like bellow:

Public Sub ReconcileButtonAction()
    Call Application.Run("SAPExecutePlanningFunction", "PF_1")
    Call Application.Run(“SAPExecuteCommand”, "Refresh", "DS_1")
End Sub

Вesides the Planning function execution, the related data store with alias DS_1 might be refreshed.

How to add the planning function described in blog post Using Planning Objects in Analysis For Microsoft Excel .

Thank you for reading through and I hope you now get a knowledge to apply in your practice.

Irina.

SAP Community - BW Planning

How to read a mapping inside FOX planning function without using ABAP

Most common issues with Analysis for Office 2.8 SP6

General:

Specific error messages:

I am getting a message saying: "Error details: Could not load file or assembly 'FPMXLClient.Common, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannof find the file specified."

After the upgrade AfO is glitching. Eg when using the scrollbar the dropdown menus are randomly opening. What can I do?

I am getting a message saying: "The given assembly name or codebase was invalid. (Exception from HRESULT: 0x80131047)"

I am getting a message saying: "Downloading file:///C:/Program Files (x86)/SAP BusinessObjects/Office AddIn/SapExcelAddIn.vsto did not succeed"

Summary:

How to Collect TVARVC Table Entries in Transport Request

How to Process Multiple Files from Application Server via ABAP Program

How to Recover Objects not visible within InfoArea

End of BI-IP – What‘s next? A viewpoint on the SAP Planning Portfolio 1

Lessons learned while working on BW Planning – TPM project

BW Queries and Planning Functions Execution

Types of Custom ‘Planning Function Type’ based on Class

Identifying which BW Query is mapped in CRM Web-UI screen

On encountering IMP_CORE and PE Errors

Best practice while performing calculation of Keyfigure in Class

Move your SAP BPC applications to SAP Analytics Cloud

Changing customer expectations driven by disruption in the economy

Covid-19 and beyond

Why move now?

Extended Planning and Analysis

Next generation FP&A (Financial Planning and Analysis) tools

Integration with S/4 Hana

Pre-built content

Smart Insight and Smart Discovery

Introducing – BPC Embedded Access Rights

Trigger Process Chain from SAC with BPC Live Connection

How Business Warehouse can help you in IBP Projects

Introduction and Motivation

Architecture

Reference Data for IBP

Backwards Integration to ERP

SAP Cloud Platform Integration for Data Services (CPI-DS)

Summary

Accelerate Your Move from SAP BPC to SAP Analytics Cloud (SAC) for planning with a migration guide

BW: Creation of custom KeyFigures InfoObject

How to add Cost Center Hierarchy into CDS View selection screen

How to: Adding Profit Center Group into selection screen

/ERP/SFIN_V01_Q2701 – Profit Centers - Actuals

/ERP/SFIN_M01_Q2701 – Profit Centers – Plan/Actual

/ERP/SFIN_M01_Q2702 – Profit Centers – Plan/Actual YTD

/ERP/SFIN_M01_Q2703 – Profit Centers – Plan /Actual with Currency Translation

1)SAP Note 3308885

2)Eclipse – BW Modeling Tools

BW TPM - Issues and Resolution

UNCAUGHT_EXCEPTION ABAP Dump While Opening Infoobject in SAP BW system (7.50)

Custom Planning Solution in BW/4 HANA

Introduction:

Main Content:

Problem Statement:

Solution:

Driver Data:

Transaction Data:

aDSO for transaction data:

Aggregation level:

Custom Class

Planning Function Type:

Planning Function:

Planning function Filter:

Planning Sequence:

Logic Build:

Execution:

Run1: (Verify the profit center)

Run2: Allocation test

Conclusion:

How to: Extension of CDS Views

How to trigger PaPM function from Analysis for Office

1. Creating PaPM environment

2. Creating the Functional Module

3. Creating the set of the BW objects to realize the planning function

4. Creating Macros to call planning function