Function documentationPromotion Planning

 

A special mapping function from BI-BPS creates a link between SAP CRM and APO and allows planned figures to be exchanged between the two systems.

Integration

Within the framework of sales planning, planned quantities (InfoCube 0CSAL_C02) are sent from SAP NetWeaver Business Intelligence (SAP Netweaver BI) to APO. In APO supply network planning and demand planning are used to determine whether these planned quantities can reasonably be supplied from a logistical viewpoint. The results of this planning in APO are sent back to SAP NetWeaver BI where sales planning can be adapted accordingly.

Prerequisites

To allow for value integration, the following objects must be taken from the Business Content and must be active in the relevant SAP NetWeaver BI System.

Object Name

Technical Description

Object Name

Technical Description

Object Name

Technical Description

InfoCube

Sales Planning

0CSAL_C02

CRM Input

9ACRMIN

APO Output

9AAPOOUT

InfoObject

Characteristics

APO Location

0APO_LOCNO

APO Location

9ALOCNO

APO Location

9ALOCNO

APO Product

0APO_PROD

APO Product

9AMATNR

APO Product

9AMATNR

BP

0BPARTNER

APO Plan version

9AVERSION

APO Plan version

9AVERSION

CRM Product

0CRM_PROD

Customer

0CUSTOMER

Material

0MATERIAL

Version

0VERSION

Value type for reporting

0VTYPE

Key Figures

Baseline

0BASE_QTY

Plan (Basis)

9APLANB

Supply Plan (Basis)

9ASPLANB

Uplift

0UPLI_QTY

Plan (Promo)

9APLANP

Supply Plan (Promo)

9ASPLANP

Total

Plan (Total)

9APLANT

Supply Plan (Total)

9ASPLANT

DataSource*

APO Location Mapping

0APO_LOCMAP_ATTR

APO Product Mapping

0APO_MATMAP_ATTR

APO Product Attribute

0APO_PROD_ATTR

APO Location Attribute

0APO_LOCNO_ATTR

*here you only see the DataSources that are not used or required as standard defaults for providing master data for the specified InfoObjects

All of these Info Objects are part of the standard InfoCubes that are delivered.

You should note that InfoCubes 0CSAL_C02 and 9ACRMIN are transactional Basis cubes whereas 9AAPOOUT is a normal Basis cube.

The following characteristics are also used as attributes for other InfoObjects (also delivered in the standard), to ensure correct assignment in Mapping:

InfoObject

Attribute

0APO_LOCNO

0CUSTOMER

0APO_PROD

0MATERIAL

0BPARTNER

0CUSTOMER

0CRM_PROD

0MATERIAL

0CUSTOMER

0APO_LOCNO

0CUSTOMER

0BPARTNER

0MATERIAL

0APO_PROD

0MATERIAL

0CRM_PROD

The InfoObjects and their related attributes should be provided with the necessary data from the InfoSources of the same name with the help of the corresponding DataSources*.

InfoSource

DataSource*

Source System

0APO_LOCNO

0APO_LOCNO_ATTR

APO

completes attr. 0CUSTOMER

0APO_PROD

0APO_PROD_ATTR

APO

completes attr. 0MATERIAL

0BPARTNER

0CRM_BPCUST_ATTR

CRM

completes attr. 0CUSTOMER

0CRM_PROD

0CRM_PR_MAT_ATTR

CRM

completes attr. 0MATERIAL

0CUSTOMER

0APO_LOCMAP_ATTR

APO

completes attr. APO_LOCNO

0CUSTOMER

0CRM_CUST_ATTR

CRM

completes attr. 0BPARTNER

0MATERIAL

0APO_MATMAP_ATTR

APO

completes attr. 0APO_PROD

0MATERIAL

0CRM_MAT_PR_ATTR

CRM

completes attr. 0CRM_PROD

Note Note

When loading data using DataSource 0APO_LOCMAP_ATTR, the location type (LOCTYPE) should be restricted to 1010 (location type Customer) for the corresponding InfoPackage on the tab page Select Data. You then see in the field EXT_LOCNO the SAP ECC customer that you need for 0CUSTOMER and in the field LOCNO you see the corresponding APO location.

End of the note.

You must also make sure that the master data from APO and from and SAP NetWeaver BI and SAP CRM side contain data records that are in agreement with each other so that unique assignment is possible.

To ensure communication between both systems (SAP NetWeaver BI and APO), you need to maintain the RFC destination to the APO System from the SAP NetWeaver BI System.

In BI-BPS you should create three basis planning areas.

You also need a multi-planning area. This is where the exchange of planned figures – Mapping – will take place.

The required planning elements such as levels, packages and functions with parameter groups must be included in this multi-planning area.

For more information on making these settings, see the documentation for BI-BPS under SAP Strategic Enterprise Mgmt. -> Business Planning and Simulation (SEM-BPS) -> Planning Environment.

Features

A special mapping function from BI-BPS creates a connection between the APO and CRM systems, enabling an exchange of planning figures between the two systems.

I. Mapping planned figures from SAP CRM/SAP NetWeaver BI into APO

You select the level at which planning is to take place (Selection criteria: business partner, product, time, unit of measure) and enter the planning figures in the corresponding planning layout.

The following planning functions are delivered:

  • Planning area 4CRMSP03 Sales planning: data transfer

  • Planning level: 4SP02000 Data transfer: SEM -> APO

  • Planning function: SPPF1100 Planned quantities are transferred to APO (with relevant parameter group)

  • SPPF1200 Copy delta version (with relevant parameter group)

  • Planning sequence: SPPS110 Data transfer

  • Planning level: 4SP03000 Data transfer APO -> SEM

  • Planning function: SPPF2100 Planned quantities are transferred to APO (with relevant parameter group)

  • Planning areas 4CRMSP04 and 4CRMSP05

By executing the planning function for mapping, the following selections can be made:

Determination of:

  • Product

    1. Each product selected in SAP CRM is assigned to a help variable and then using the FOX instruction “..ATRV ("Material",Product)....” the attribute “Material” is determined in CRM.

    2. This material is also assigned a variable and using a corresonding FOX instruction “..ATRV ("APO-Product", Material)....” the attribute “APO-Product” is read in CRM.

    3. The SAP CRM APO-product is also assigned to a help variable.

    4. The contents of the variable are copied to a help variable for the APO product in APO.

  • Business partner

    1. Each selected business partner in CRM is assigned to a help variable and then using the FOX instruction “..ATRV (“Customer”, Business Partner)...” the attribute “Customer” is determined in CRM.

    2. This customer from CRM is assigned a variable and then using a FOX instruction “..ATRV (“APO-Location”, Customer)...” the attribute “APO-Location” is read in CRM.

    3. The SAP CRM APO location is also assigned to a help variable.

    4. The contents of the variable are copied to a help variable for the APO location in APO.

  • Time and unit of measure

    1. Each time and unit entry is assigned to the help variable for the relevant SAP CRM objects and sent directly to the corresponding variables for the APO objects.

Actual mapping only takes place when the operands are assigned {..,..}. Each individual key figure value along with the relevant characteristics from SAP CRM are copied into the corresponding APO key figure.

When running the procedure a predefined value is copied with each data record, so that you can see the processing status of the data record.

PRIVATEA: Processing and mapping key figures

CRM Version

1

APO Version

TPM02

B: Release and mapping key figures

CRM Version

2

APO Version

0

II. Mapping planned figures from APO into CRM or BW

You select the level at which planning is to take place (Selection criteria: business partner, product, time, unit of measure) and copy the planned figures from APO to BW.

By executing the planning function for mapping, the following selections can be made:

Determination of:

  • Product

    1. Each selected product in APO is assigned to a help variable.

    2. The contents of the variable are copied to a help variable for the APO product.

    3. For this APO product in CRM the FOX instruction “..ATRV ("Material",APO-Product)....” is used to determine the attribute “Material” in CRM.

    4. This material in SAP CRM is also assigned a variable and using the corresponding FOX instruction “..ATRV (“CRM-Product”, Material)....” the attribute “CRM-Product” is determined in CRM.

    5. The SAP CRM product is copied to a help variable.

  • Business partner

    1. Each selected location in APO is assigned to a help variable.

    2. The contents of these variables are copied to a help variable for the APO location from CRM.

    3. For this APO location from CRM the FOX instruction “..ATRV ("Customer", APO-Location)...” is used to determine the attribute “Customer” in SAP CRM.

    4. This customer is then assigned to a variable and then using another FOX instruction “..ATRV (“business partner”, customer)...” the attribute “business partner” is determined in CRM.

    5. The business partner is copied to a help variable.

  • Time and unit of measure

    1. Each time and unit entry is assigned to the help variables for the relevant APO objects and sent to the corresponding variables for the SAP CRM objects.

Actual mapping only takes place when the operands are assigned {..,..}. Each individual key figure value along with the relevant characteristics from APO are copied into the corresponding SAP CRM key figure.

A predefined value is copied with each data record, so that you can see the processing status of the data record.

PRIVATEProcessing and mapping key figures

APO-Version

TPM02

CRM-Version

1

Example

  • Maintain the RFC destination to APO in SAP NetWeaver BI.

  • Create three basis planning areas in BI-BPS and assign an InfoCube to each one. Make sure that when you define planning areas for cubes that are not in the local system (for example, APO cubes) the correct RFC destination is defined.

  • Define a multi-planning area and assign one of the three planning areas as a basis. Include one of the planning elements that is required for mapping in the multi-planning area and adapt the selections and settings to your requirements.

Mapping the SEM System into the APO System

Corresponding characteristics in SAP NetWeaver BI and APO have different technical definitions and are provided with different conversion rules so that the values of these characteristics can be mapped onto each other. Master data attributes are assigned to the corresponding characteristics in SEM whose definition and conversion behavior corresponds to that of the APO characteristics.

By accessing the attribute values in Mapping (in the FOXFORMEL-Editor) the characteristics are determined and copied into APO.

Simple example

SEM business partner should be mapped to the APO location

The attribute 0APO_LOCNO is assigned to the SEM characteristic 0BPARTNER, which has the same data type, data length and conversion behavior as the characteristic 9ALOCNO in APO.

In the FOXFORMEL editor, the value of the attribute is read using the instruction

....ATRV ('Attribute', characteristic variable) ....

and is copied to the relevant characteristic in APO.