Source: SAP note - 2493042
You
are using SAP Cloud Platform Integration for data services to export key figure
data from an IBP application.
Please
note that SAP HANA Cloud Integration(HCI) has been renamed to SAP Cloud
Platform Integration(CPI)
Environment
- Supply Chain Management (SAP
SCM)
- Integrated Business Planning
(SAP IBP)
Cause
You
are using SAP Cloud Platform Integration for data services to export key figure
data from an IBP application.
For
extracting the key figure data, a calculation scenario is used to extract the
data out of IBP. A calculation scenario is a special construct in the SAP HANA
database that the integration service can use to read data from an IBP
application and to write to a file, or to write the data directly to the target
on premise system using a web service call. Calculation scenarios are generated
in the planning area of the IBP application.
While
defining the Data Export Task, it becomes essential to put necessary filters
and optimize the filter conditions to ensure that filter conditions are pushed
down to IBP.
- It decreases the run time of
Data Export Task and optimal usage the resource/CPU/Memory consumption.
- Minimize the impact of this
task on the normal business activities of the users.
- It also reduces the chances of
exceptions like connection reset which might lead to an open cursor IBP
and in turn impact the performance of IBP.
Resolution
Kindly
follow the below guidelines while designing the Data Export Task in CPI-DS.
- You should split the data
extraction needs into multiple tasks based on different filter conditions
wherever possible. You need to ensure that smaller data set is extracted
from IBP for the optimal usage of resources in HANA.
- You should avoid the concurrent
execution of the Data Export Task. Instead, you schedule the Data export
task sequentially
- You should always specify the
exact PERIODIDn attribute based on the time level you want to extract the
data, instead of selecting the generic PERIODID attribute in your
data flow. Please note PERIODIDn do not refer directly to the time
profile level. For your planning area PERIODIDn are mapped as follows to
the time profile level.
- PERIODID0 Day (Lowest Time
Profile Level)
- PERIODID4 Week
- PERIODID3 Month
- PERIODID2 Quarter
- PERIODID1 Year (Highest Time
Profile Level)
- You should not use the IN/NOT
IN operator, instead you can use the OR operator for filter conditions.
- For e.g. instead of PRDID
IN('X','Y') use (PRDID='X' OR PRDID='Y')
- You should put the filter on
PERIODIDn attribute instead of TSTFR for time period filter conditions.
You can give the relative filter conditions for the PERIODIDn.
- For e.g. If you want to
extract the data for the current period+12 periods in future, you can
define the filter as (PERIODIDn>=0 AND PERIODIDn<=12).
- If you only use the equal to
filter, then you need to provide the absolute technical PERIODID which
can be retrieved from the excel UI. The filter condition will be like
PERIODIDn=1067
- You may also use CPI
DateTime functions like WEEK_IN_YEAR, MONTH to meet the different
extraction requirement from the Business Perspective. You can refer to
the following help document for the full list of CPI DS functions: https://hcids.hana.ondemand.com/DSoD/help/index.html#5cc2bab3d53e43c1bfdeda50c6674625.html
Product
|
Product or Product
Version
|
||
|
SAP Integrated
Business Planning 1702
|
||
|
SAP Integrated
Business Planning 1705
|
||
|
SAP Integrated
Business Planning 1708
|
This document is
referenced by
|
Number
|
Title
|
||
|
2571962
|
|||
|
2565151
|
|||
|
2516625
|
