Funds Plan and Funds in SAP CRM Funds Management

In this document we will touch upon Funds Management objects like Funds Plan, Funds, Budget Posting etc. We will get into the configuration behind these objects and also focus on transaction level details and utility for each one of them.

Funds Management is an application in SAP CRM which assists manufacturers or owners of brands to administer and distribute the funds amongst its distributors or channel partners in order to engage in co-marketing activities. The channel partners consume these funds (money) in order to deliver on agreed goal for improving the presence of manufacturers products in the market and via Funds Management we can monitor the disbursement and usage of these funds.

SAP CRM Funds Management can be integrated to with the below applications within SAP CRM in order of the owner of a brand or manufacturer to achieve co-marketing or co-branding objectives:

1. Market Development Funds (MDF)
2. Trade Promotion Management (TPM)
3. Marketing Funds Management (MFM)
4. Claims Management

Funds Plan

Funds Plan is an high-level object in Funds Management which will act as an umbrella for associated funds under it. Funds Plan do not carry any money, however it is possible to assign Funds under it which eventually will be loaded with budget (money). It is to be noted that currency is always maintained as a default with the Funds plan, this is done to ensure that underlying Funds within a Funds Plan always  reflect common currency.

‘Funds Plan Type’ is associated with Funds Plan which defines the nature of the Funds Plan i.e. whether the Funds Plan is meant for MDF, TPM etc. and also there is a timeframe of budget expiry which is maintained at funds plan level. These expiry periods can be fixed, relative or none.

To configure Funds Plan please use the path ” IMG >> Customer Relationship Management >> Funds Management >> Funds Plan and Funds >> Define Funds Plan Types “

Funds

Funds are objects which contain the monies. The money i.e. Budget in the fund is provided to the channel partner by brand owner to execute the co-marketing or channel marketing activities in order to achieve an agreed outcome.

‘Fund Type’ outlines the specific objective behind creating a Fund. It captures the category which the Fund belongs to i.e. Fixed or Variable Fund. It also assists in setting up an association of the Fund with the way it is going to be spent i.e. promotional activities in paper, electronic media, social media, events, trade fairs etc. The nature of the spent is captured as an ‘Expense Type’ in the system.

‘Fund Attributes’ are very critical in ensure the downstream marketing objects like Marketing Program, Initiatives, Claims etc. can determine which Fund to be used at the execution layer of a co-marketing activity. Fund Determination is a procedure via which criteria’s are defined in order to identify one specific Fund which will be assigned to execute activities like Trade Promotions, Claims, Budget Postings etc. are performed.

Fund Checkbooks provide latest view of the money at different levels of a co-marketing spend process which includes budgeted, reserved, approved claims, settled etc.

To configure Funds please use the path ” IMG >> Customer Relationship Management >> Funds Management >> Funds Plan and Funds >> Define Funds Type“

As discussed we will need to assigned Expense Types to the Fund Type for the Fund to be utilized for a specific spend. Before that we will need to define expense types first.

Go to transaction path ” IMG >> Customer Relationship Management >> Funds Management >> Funds Plan and Funds >> Define Expense Type “

Once expense types are define we will assign Expense Type to Fund type in order to create the link. Go to transaction path ” IMG >> Customer Relationship Management >> Funds Management >> Funds Plan and Funds >> Assign Expense Types to Funds Types “

Once these configurations are done in the background, log in to CRM WebUI and make use of Business Role ‘CHM-CM – Channel Manager‘. Once the screen loads make use of left-hand side navigation pane and choose ‘Market Dev. Funds’ to create objects like Funds and Funds Plan.

Once we proceed from here, we create Funds Plan and after creating it we mark it as ‘Released’.

We proceed further to create a Fund, then add budget to the same. The budget to the fund is added via Budget Posting. Once the Fund is created and released we create a Budget Posting. Budget Posting is an object which is used to upload the money to a Fund. Below you will see a Fund with Budget loaded to it for usage.

With this we come to an end to this document. Once these Funds Plan and Funds are created and required Budget is allocated via Budget Posting, the scenario can be extended by Integrating Funds Management in CRM with MDF or TPM or MFM. One such integration between CRM FM and MDF will be discussed in the next document.

Continue reading

SAP BW Modelling Tools: ODP - Source System Editor

With SAP BW Modelling tools 1.17, user can create any source system directly from Eclipse based SAP BW Modelling tools. This is editor is only available for SAP BW/4 HANA system whereas in  SAP BW on HANA system user still need to define source system via traditional SAP GUI interface.

In SAP BW/4 HANA, these are few source systems which are available: – ODP based source system (SAPI, CDS, HANA, BW, SLT), HANA source system (SAP HANA Local Database Schema, SAP HANA Smart Data Access, SAP HANA Tenant Database schema), BIG Data and local file source system. We will see how to create ODP-SAPI source system.

The creation of new source system can be done via file menu, context menu of the project, Data source node and from data source folder (E.g. ODP_SAP, ODP_BW, HANA_LOCAL and so on). With the new source system editor, user must select as which type of source system he is creating as ODP based, HANA local source system, etc.

While defining ODP based source system, user must choose as what is the connection of source system. There are three type of connection from which user can choose: –

1. RFC to same system: – To connect to same system with RFC connection.

2. RFC to different system: – Connect to other system like SAPI, BW via RFC connection.

3. HTTP connection: – Connect to other system via HTTP connection. Here the user should navigate to SOA manager to create logical port for the Web services- which must be of same name as of source system.

User also need to create connection to the system if the connection with same name as of source system is not present. In new source system maintenance we have three different RFC connection which can be edited with edit button. The status icon shows whether the connection is fine or broken. For Example, if the one of the connection is broken then status for that connection will represent the same with red cross sign and if connection is fine then the same is represented by green check sign.  There are 3 connection that can be seen in ODP based source system maintenance screen: –

1. Logical Destination: – Used to connect to Remote System.

2. Dialog Destination: – used to connect to remote system with a dialog user. This is optional.

3. Callback Destination: – used to connect from remote system to BW system.

With respect to ODP based source system user have to select the context of ODP source from the dropdown menu “ODP Context”. These are the context  :-

1. [SAPI] DataSources/Extractors

2. [BW] SAP NetWeaver Business Warehouse

3. [ABAP_CDS] ABAP Core Data Services

4. [HANA] HANA Information Views

Another important option in new source system editor is “Remote tree” check box. The Upload tree menu on toolbar of source system maintenance screen is associated with status of remote tree in source system.

It is enabled for only source system type ODP and only when Remote tree is enabled. This option is not available for all other source system types, e.g. HANA data source, file. In this case, a “local tree” is used which is shared by all source system which do not have a “remote tree” and (in case of ODP) not for all releases.  For ODP-SAPI, the upload tree functionality brings the Hierarchy defined in source system application component. For ODP-BW, it uploads brings the info areas created.

Continue reading

SAP BW/HANA – Data Flow Migration Tool with Data Transfer

Audience: 

This Blog is primarily aimed at SAP BW Consultants who are planning to prepare the system for BW/4 HANA and also looking for options to migrate existing objects(DSO, MP) to new HANA Objects(ADSO, CP).

Scope:

We have recently upgraded our BW System from BW 7.5 SP4 to BW 7.5 SP8 with BW/4 HANA Starter Add on Installed.

There are some good blogs on the conversion process to deliver BW/4 HANA System, In this blog post i want to mainly concentrate on the Data Flow Migration Tool With Data Transfer option which is available now with BW 7.5 SP8 with BW/4 HANA Starter Kit Installed.

Below are the details of Installed software component version.

In BW 7.5 SP4, we have used RSO_CONVERT_IPRO_TO_HCPR to convert a Multi provider to Composite provider, by retaining the Same Info Provider name and BEX Queries. As a next step, we have waited for the migration option for complete data flow to new objects with Data transfer. And finally we are there with this upgrade and we have successfully tested the functionality in our Sandbox System. There were couple of issues we have seen and worked with SAP for Solutions and there were pilot notes we applied.So below is how we have started.

1. First upgraded our system from BW 7.5 SP4 to BW 7.5 SP8 with an expectation of having this migration tool available. But we realized, this is not the only pre requisite and SAP is providing this migration tool with data as part of their journey to BW/4 HANA.

2. So we have installed the SAP BW/4 HANA Starter Kit, still no luck. Transfer tool was not yet available( Starter Kit can also be installed as part of the upgrade)

3. Then SAP has provided us with 2383530 – Note which had a .XML file and Z program(Z_SAP_BW_NOTE_ANALYZER) for analyzing the notes and then we have applied around 360 notes using the XML file in the note. Finally, we installed 2500045 – Pilot note to install “Transfer Toolkit”.

4. Finally we have the Transfer Tool Kit available in our sandbox system.

Note – We are still on the compatibility mode, we haven’t switched our system to B4H.

How to Use the Transfer Tool Kit

1. We can either use Program RS_B4HANA_TRF or STC01/STC02 and select Task List as SAP_BW4_TRANSFER_INPLACE.

2. Once you the this, it will create a new task List Run and you will see below options, where we need to defined the scope , objects mapping etc.

3. We define the scope for the migration, Which Multi Provider and its data flow we want to migrate. I have used a MP(0TCT_C25), which had a cube(ZTCT_C25) under it. So the expectation is to get this MP converted to a Composite provider and Cube migrated to ADSO with Data and Queries are retained in the new MP with no changes to Enterprise ID’s

4. Below is the object List, we can select and UN-select the objects to be transferred.

5. We can run the process after defining the cope and objects list. It will execute each and every step we saw in screenshot in step2 and migrates the data flow to new objects and also copies the data along with request ID’s( we can also add a break point at each step to review the process)

6. Now we see a composite provider with same name and ADSO with same name as cube. We can also see the data copied to new ADSO and also the request management.

Continue reading

Creating New Date Rules in SAP CRM

This blog explains the process for creating new date rules in SAP CRM.

To create a new date rule, you need to perform a series of configuration and development steps:

1. Open the Date Rule customizing screen by going into the IMG and following the menu path: Customer Relationship Management > Basic Functions > Date Management > Define Date Types, Duration Types and Date Rules.

2. In the dialog structure that appears, select Date Rules, and then click the New Entries button. The screen shown below appears.

3. Enter a technical name for the rule such as “ZBOOKEX1”, and then enter a description such as “Book Example”.

4. Click Save, and you are prompted for a customizing request. If you don’t have an existing customizing request, you’ll create a new one; otherwise, you’ll select one for your work.

5. Go back to the overview screen of all existing date rules as shown below, select the date rule that you created, and then click the Details icon.

6. An overview screen appears showing all of the versions of the underlying XML that makes up the date rule as shown in the figure below. Double-click on the only row, and then you’re ready to start editing the XML of the date rule. There isn’t much documentation on this format, but to invoke an ABAP function module for date rules, you can enter a certain pattern as shown in the second figure and code below.

7. When you first open the editor, it will be in display mode. Click the Change button to insert the necessary XML code.

The Editor for Date Rules screen expects a certain pattern of XML to be entered that specifies the date rule as shown in the following code. The pattern has been derived by examining the delivered date rule in the system called “Planned Date (Activities)” with a technical key of “000000000002”.

<?xml version="1.0"?>

<SAPTimeRule>

  <ABAPTimeRule function="Z_CRM_DATE_CALC"/>

</SAPTimeRule>

8. After you’ve created the XML for the date rule that calls the ABAP function module you’ll create in the next step, save your work.

9. Before you can use this date rule in a date profile, you now must code the ABAP logic that will evaluate the date passed and return a result. Create a function module that has two importing parameters:

◉ _ CONTEXT: A type reference to IF_TIMECONTEXT.

◉ _ TIMEMESSAGE: A type reference to CL_TIMEMESSAGE.

Your function module also must return a reference value named ERROR that is of type XFLAG.

The context reference provides you access to the date data being manipulated in your function module. The interface allows you to retrieve the list of time events and then add back a special time event called the result, which is the result of your calculation and will populate the date type that will use this rule.

1 Function Module Logic: Date Context

To better understand this logic, let’s take a look at the following function module that calculates your date. The first call will be to get the event set from the context as shown in the code fragment:

li_eventset = context->get_eventset( ).

This is always needed to provide the result back and calculate any dates you may encounter.

Next you’ll get the GUID of the current transaction you’re processing so you can access any data needed for the calculation via the one order API. You’ll use the function module CRM_CONTEXT_GET_ACTUALGUID_OW to get this GUID.

After you have the GUID, you retrieve any other data from the business transaction using the one order OW function modules by passing in the header GUID. As you might have noticed, your function module doesn’t provide any data about the business transaction you’re working with directly.

If your calculation is based on another date, you first need to retrieve the value of that date by retrieving it from the event set. The following code fragment can be used to achieve this in your date rule function module:

li_tns_zfirstcont ?= li_eventset->get_by_name( lv_name ).

if li_tns_zfirstcont is initial.

  exit.

endif.

Note that you won’t want to process the date rule if the date you need to calculate hasn’t been entered or already calculated. Thus, you’ll exit the function module to prevent any short dumps with improper date calls.

One big difference of working with a date context as compared to standard ABAP time and date types is that you can’t perform simple add or subtract functions on the dates themselves. You instead need to create a duration that corresponds to how much you want to increment or decrement the date and then apply the duration to the date itself. To do this, create a new duration object using the class CL_TIMEDURA. You can then calculate the new date by using the static method CL_TIMECALC.

Continue reading

How to change/create InfoObjects with RSD1 as of BW 7.5 SP04 on HANA

Introduction

InfoObject maintenance in the BW Modelling Tools (BW-MT) was made mandatory starting with SAP BW 7.5 SP4 on HANA. Since then it is not possible to maintain/create InfoObjects from the SAP GUI using the transaction RSD1. Displaying though still works.

This change surprised the one or the other as this is the first existing BW object which must be maintained in the BW-MT. Up to now only new objects like Composite Provider and Open ODS Views were only available there.

It was tested under release 7.5 SP04.

Please read the disclaimer carefully

Be careful, by following this. You basically tell the system that it is not a BW on HANA system.
You should also consider that there is some stuff which can only be maintained in the BW-MT, for instance transitive attributes.
It should be only used in case you are running into problems using the BW Modelling Tools (BW-MT).

Step by Step

Step 1: Go to tcode- RSD1

- Call transaction RSD1
- You will see that the transaction is in display mode, i.e. no create or maintain button.

Step 2: Enter nohdb into the OK Code field

- Enter “nohdb” into the as per the following screenshot and press enter

Now you can see Maintain button in below screen.

Continue reading

ABAP CDS in SAP BW

Introduction

ABAP Core Data Services (CDS) Views were introduced with SAP ABAP 7.40 SP05. CDS allows the creation of rather complex views that by far exceed the capabilities of database views created in SE11. Besides their role in the ABAP Programming Language, CDS Views are the technology behind the virtual data model on top of the SAP S/4HANA application tables which, e.g. is used in SAP S/4HANA Analytics.

This aspect – the role of CDS in SAP S/4HANA Analytics – frequently brings up the question whether or how CDS might be used in the context of SAP BW powered by SAP HANA or SAP BW/4HANA.

The purpose of this blog is to clarify the role of CDS in SAP BW.

ABAP CDS in SAP BW – the reporting perspective

Since CDS is used to build the Virtual Data Model in SAP S/4HANA, a frequently asked question is, whether CDS Views could also be used to build a virtual layer on top of BW InfoProviders, most prominently Advanced DSOs, which could be consumed in analytic front end tools like in the SAP S/4HANA environment. Or, whether CDS could be used to enhance a SAP BW data model with data from a Z-table. The clear answer to this is – for a number of reasons: No.

The SAP BW data model

Anyone familiar with the way SAP BW generates database tables from its high level (InfoObject based) data model, knows that SAP BW entities typically are split into multiple tables with implicit relationships managed by the BW application. In addition, many of these tables contain technical fields which are of critical importance when writing to or reading from the object. All the logic that is required to correctly interpret these fields and deliver correct and consistent query results, is part of the BW application which creates the correct JOINs and filters at query runtime. All the SAP BW modeling artefacts (e.g. CompositeProviders, Advanced DSOs) are built such that they are aware of all these aspects and relieve the user from a detailed understanding.

The SAP BW security concept

SAP BW secures data from un-authorized access via Analysis Authorizations. This is again a concept specifically designed with the SAP BW data model in mind and it differs significantly from standard filter-based database security concepts. And just as with the data model aspects above, the evaluation and interpretation of Analysis Authorizations is done in the SAP BW application. Therefore, accessing SAP BW data via SQL or OpenSQL (which is the standard way to consume CDS views), would completely bypass the security layers of SAP BW and open the way for un-authorized access, which is prohibitive in pretty much any real world scenario.

Mixed Scenarios

These aspects have since long been the main reasons why SAP does not support direct consumption of SAP BW generated tables. As you may be aware, SAP BW powered by SAP HANA or SAP BW/4HANA provide capabilities addressing specifically this point – opening up SAP BW for SQL consumption. The approach taken here is to generate SAP HANA Calculation Views from the SAP BW data model that incorporate all the dependencies within the data model and the correct interpretation of all the technical fields and creating SAP HANA Analytic Privileges from SAP BW Analysis Authorizations to ensure security.

Conversely, when it comes to integrating non-BW data (e.g. in a Z-table or Z-view) with the SAP BW data model, this is done via Open ODS Views, which – conceptually – put a “SAP BW-shell” around a table or view.

Thus, also in this environment, CDS does not play a role in SAP BW.

SAP BW Technical Content

Tracking and monitoring the operations of a SAP BW system is one of the areas, where CDS in fact is playing a role. For example, SAP BW comes with tables containing statistics on loading and querying data, status information about load requests, etc. With SAP BW 7.5 SP04, CDS based technical content is shipped that provides administrators/modelers with such information. Being built on CDS, this content is much leaner and simpler than traditional SAP BW technical content, does not require loading of the data to a SAP BW InfoProvider, or even activation of SAP BW objects.

Consuming CDS Views in SAP BW

SAP BW can, however, leverage content built using CDS Views – most prominently SAP S/4HANA Analytics. For one, there is a dedicated Source System type ODP-CDS in SAP BW (since release 7.4) that allows to load data from a CDS View into SAP BW. This integration currently does not provide all services known from the classic extractor based data provisioning, but in certain scenarios it can be a valid option. Secondly, SAP S/4HANA Analytics content can be virtually consumed and combined with data in SAP BW via Open ODS Views.

ABAP CDS in SAP BW – the ETL perspective

One specific use case where CDS views can play a role are the SQL expert routines in SAP BW Transformations. To simplify, for example, a complex look-up on customer specific Z-tables in a transformation, it can be very useful to define a CDS view on top of these tables and use that CDS view within the SQL export routine.

Continue reading

SAP BW 7.3 Configuration Steps Part - 2

Introduction

This document will contain the basic BW Configuration steps after installation of SAP BW system. The configurations mentioned here are to be performed after system installation and basis configurations mentioned in SAP BW 7.3 Configurations part1 document. Here is the link https://saponlineguides.blogspot.in/2017/10/sap-bw-73-configuration-after-installation-of-bw-part-1.html

Step 1: Set Analysis authorizations in transaction code RSCUSTV23

Set “Current Procedure with Analysis Authorizations“.

Step 2: Hide 3.x Functions of Data Warehousing Workbench.

Path->SPRO->Display IMG-> Hide 3.x Functions of Data Warehousing Workbench.

Selecting below option can hide all 3.x functions of the DW Workbench for which there is a new functionality available.

Note: If the indicator is set, you are no longer asked if the old or new Data Sources should be transferred when they are replicated; they are always transferred as new Data Sources.

If you want to use old 3.x functionalities, don’t hide this function

Step 3: Set Traffic Light Color in the below path of IMG

If no data available then status would be green

Incase of warnings ,status would be in yellow

Step 4: Change source system name after transport in RSLGMP transaction or below path .

Path->SPRO-> IMG

Below settings needs to be done in quality and production systems. Which will convert  original source system name to target source

system name .

If we are transporting objects to quality system, target would be quality system .Original source system will be your development system where you have developed objects and moving to further landscape.

Step 5: Create Destination for Import Post-Processing in RSTPRFC or below path

Below setting needs to be done in target system (quality system and production system) before moving transports.

Process chain transport will fail ,in case of unavailability of below setting or ALEREMOTE password issue or RFC destination unavailability between BW development system to further landscape (TBD<->TBQ, TBP).

Step 6: Display of Numeric Values in the Business Explorer in RSCUSTV4 transaction code below path

Set “X” in case of ‘value division by zero’

‘does not exist’

‘number overflow’.

Any of above mentioned scenario in BEx report will give out put as “X”

In case of mixed currency or UOM ,report will show * value.

Step 7: Activate Personalization in BEx

Path->SPRO->IMG

It will allow you to personalize BEx variables, webapplication variable and BEx history.

Step 8: Set BEx Analyzer Version in RRMX_CUST or below path

Path->SPRO->IMG

Set BEx analyzer version to be called from RRMX

You can select either 3.x version or Sap Netweaver version.

Step 9: Maintain Web Protocol (HTTP/HTTPS)

Path->SPRO->IMG.

Specify HTTP or HTTPS as per requirement,

By default HTTP protocol will be called by web application designer or query designer.

Step 10: Set Standard Web Templates

Path->SPRO->IMG

Specified web Templates will be called for broadcasting, query pre calculation, EP reporting, adhoc analysis.

Step 11: Determine Settings for Web Templates

Path->SPRO->IMG

Below specified Web template needs to be activate from business content

Step 12: Maintain Source system ID’s in RSA1 transaction code

Path->

RSA1->TOOLS->Assignment of Source Syst.To Source Syst. ID.

Continue reading