Thursday, May 3, 2018

IBP- CPI Integration - Best Practices for Extracting Data out of IBP

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.
  1. 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.
  2. You should avoid the concurrent execution of the Data Export Task. Instead, you schedule the Data export task sequentially 
  3. 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)
  4. 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')
  5. 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

Monday, April 2, 2018

First SAP IBP Certification published.

C_IBP_1711

SAP Certified Application Associate - SAP Integrated Business Planning (1711)

Delivery Methods:
Certification
Level:
Associate
Exam:
80 questions
Sample Questions:
View more
Cut Score:
64%
Duration:
180 mins
Languages:
English


Description

  • The "SAP Certified Application Associate - SAP Integrated Business Planning (1711)" certification exam verifies that the candidate possesses the basic knowledge in the area of the SAP Integrated Business Planning. This certificate proves that the candidate has a basic overall understanding within this consultant profile of the industry solutions, and can implement this knowledge practically in projects under guidance of an experienced consultant. It is recommended as an entry-level qualification to allow consultants to get acquainted with the fundamentals of SAP Integrated Business Planning.

Notes

  • To ensure success, SAP recommends combining education courses and hands-on experience to prepare for your certification exam as questions will test your ability to apply the knowledge you have gained in training.
  • You are not allowed to use any reference materials during the certification test (no access to online documentation or to any SAP system).

Topic Areas

Please see below the list of topics that may be covered within this certification and the courses that cover them. Its accuracy does not constitute a legitimate claim; SAP reserves the right to update the exam content (topics, items, weighting) at any time.

Solution Architecture > 12%

Describe the benefits of implementing SAP's Integrated Business Planning solution.



General Configuration of a Planning Area > 12%


User Interface > 12%

Use SAP Fiori to personalize the user experience.

Advanced Analytics & Reporting > 12%

Perform analytics and create reports.


Key Figures & Attributes > 12%

Create and use key figures.


Planning Operators  8% - 12%

Use Planning Operators.


Statistical Forecasting < 8%

Manage a statistical forecast.

Thursday, March 1, 2018

Skip to end of metadata
Go to start of metadata
This post is used for ongoing SAP customer communications related to SAP Integrated Business Planning major release upgrades.
For the upgrade process and communication Information, please see this link.

Upcoming Planned Upgrades

  • SAP IBP 1802: Applied to Customer Systems February through March 2018  (Planned Release to Hosting February 6, 2018)
  • SAP IBP 1805: Applied to Customer Systems May 11 through June 8, 2018  (Planned Release to Hosting May 8, 2018)
  • SAP IBP 1808: Applied to Customer Systems August 10 to August 31, 2018 (Planned Release to Hosting August 7, 2018)
  • SAP IBP 1811: Applied to Customer Systems November 9 to November 30, 2018 (Planned Release to Hosting November 6, 2018)
Future timings of upgrades are subject to change.
Published SAP Integrated Business Planning Roadmap: LINK
Upgrade Notification Guidelines
  • Upgrade notifications are sent to system administrator contacts.
  • Emails are sent from: sapcloudsupport@alerts.ondemand.com
    Tip: make sure your email software doesn’t block this email address to avoid it going to your SPAM/Junk Mail email.
  • Specific schedule of customer system updates will be communicated via email.
  • SAP provides code fix support only for "n-1" versions. ie. when a new version (version "n") is "Released to Hosting," support is dropped for the "n-2" version.
  • Upgrade notifications are only provided for major release upgrades.
  • Hot Fix Collections (HFC) and Emergency Patches (EP) are applied during the regular Contract Maintenance Period. Customer communications are not provided for HFC or EPs.

Upgrade NOTIFICATION for SAP Integrated Business Planning

Notification Purpose
As part of SAP’s continued commitment to provide you with high value applications, we will be upgrading SAP Integrated Business Planning 1711 systems to SAP Integrated Business Planning 1802.
When
  • Upgrade window: Friday 10 PM Local Data Center Time to Monday 3 AM Local Data Center Time
  • Expect your systems to be unavailable during this period. This is consistent with the contracted maintenance windows.
  • SAP will apply this upgrade from February through March 2018 (see above).
Important Information
Visibility Filters → Permission Filters
To reflect the fact that visibility filters can now also be used to control write access, the term permission filter replaces visibility filter in the IBP applications and in the documentation as of 1802.  Particularly, the Visibility Filters app has been renamed to Manage Permission Filters. Also see the  "Permission Filters" section in the What’s New in 1802.
Activation of Planning Area
  • Generally, you do not need to reactivate your planning areas when you upgrade. However, you may have to reactivate to take advantage of certain capabilities. Please review What’s New in 1802 for more information (available as of RTH, planned for Feb 6).
  • For additional activation guidance, please review the model configuration guide (available as of RTH, planned for Feb 6). If activation ends with an error you cannot solve, please create a customer incident.
Excel add-in
  • The upgrade generally does not require that you install the new version of the IBP Excel add-in. You can decide to install the new version at any time, for example, when you wish to use the new features that are available with the new add-in version. For more information, see What’s New in 1802 (available as of RTH, planned for Feb 6).
  • Customers can download and install the latest Excel add-in version on the SAP Support Portal. For more information about restrictions related to the IBP Excel add-in, please check SAP Note 2519069
  • To apply the latest version of the Excel add-in, please uninstall your current Excel add-in and re-install the new Integrated Business Planning Excel add-in. For more information on how to install the Excel add-in see Setting Up the IBP Excel Add-In (Administrators) and Setting Up the IBP Excel Add-In (Business Users).
  • For guidance on packaging and deploying the Excel add-in to end users, please see SAP Note 2114654.
  • For supported configurations and prerequisites, please see SAP Note 2135948.
  • For the IBP 1711 version of the IBP Excel add-in, you download a zip-archive from the SAP Support Portal , in which you find:
    • IBP_Add-in_NET45_x64.exe: This file installs the IBP add-in as a single ribbon for 64-bit Excel installations
    • IBP_Add-in_NET45_x86.exe: This file installs the IBP add-in as a single ribbon for 32-bit Excel installations
    • IBP_Add-In_SbS_x86: This file installs the IBP ribbon as an additional ribbon next to the EPM ribbon (side-by-side installer) for 32-bit Excel installations
    • IBP_Add-In_SbS_x64: This file installs the IBP ribbon as an additional ribbon next to the EPM ribbon (side-by-side installer) for 64-bit Excel installations
  • For the IBP 1802 version of the IBP Excel add-in, you download a zip-archive from the SAP Support Portal , in which you find:
    • IBP_Add-in_NET45_x64.exe: This file installs the IBP add-in as a single ribbon for 64-bit Excel installations
    • IBP_Add-in_NET45_x86.exe: This file installs the IBP add-in as a single ribbon for 32-bit Excel installations
    • IBP_Add-In_SbS_x86: This file installs the IBP ribbon as an additional ribbon next to the EPM ribbon (side-by-side installer) for 32-bit Excel installations
    • IBP_Add-In_SbS_x64: This file installs the IBP ribbon as an additional ribbon next to the EPM ribbon (side-by-side installer) for 64-bit Excel installations
  • For a list of available IBP Excel add-in versions and the features they contain, please see SAP Note 2394311.
Activities by end-user after the upgrade
  • End-users need to clear their browser cache.
  • SAP recommends that customers delete old transports after every upgrade.
  • Note: Transports must be transported between systems at the same version level.
Questions? Who you should contact.
  • For scheduling changes, please contact engage-ibp@sap.com or submit a customer incident.
  • For application and technical support, please use standard SAP support (support.sap.com).

Saturday, January 2, 2016

SAP Press new book - SAP APO: Technical Principles and Programming

My new SAP Press book - SAP APO: Technical Principles and Programming

Wednesday, July 30, 2014

Data inconsistencies in SNP

 
Symptom

There are inconsistencies in your system that can cause errors in interactive Supply Network Planning (SNP), SNP mass processing, and SNP data extraction. The system may issue the following error messages:
  • E207(/SAPAPO/TSM) 'No liveCache anchor found.
  • E020(/SAPAPO/OM_TS) 'Time series does not exist'
  • E219(/SAPAPO/TSM) 'Invalid data status'
  • E230(/SAPAPO/TSM) 'No plannable characteristics combinations available'
  • E001(/SAPAPO/SDP_MD) 'Planning object could not be determined'
  • E085(/SAPAPO/SDP) 'Error reading data - planning book cannot be processed'
Memory consumption in the liveCache increases disproportionately in relation to the master data volume.


Other Terms

/SAPAPO/TS_LCM_CONS_CHECK, /SAPAPO/TS_LCM_CONS_CHECK_ALL,
/SAPAPO/TS_LCM_REORG_SNP, /SAPAPO/TS_LCM_REORG


Reason and Prerequisites

SNP master data is created in the system for the APO master data. This enables navigation in SNP interactive planning. The SNP master data corresponds to the aggregates defined in the SNP planning area and is saved in the database tables.
           Aggregate Database table
           9AMALO /SAPAPO/MATLOC
           9AMALORE /SAPAPO/MATLORES
           9ALORE /SAPAPO/LOCRES
           9AMALA /SAPAPO/MATLANE
           9AMALARE /SAPAPO/MATLARES
           9AMAPR /SAPAPO/MATPPM
           9AMARE /SAPAPO/MATRES
           9AREPR /SAPAPO/RESPPM
           9AACPR /SAPAPO/ACTPPM
           9AMALOSA /SAPAPO/MALOSA
           9AMALASA /SAPAPO/MALASA

If you create master data in APO or change assignments, you must also create the missing SNP master data or time series. The SNP master data and the time series in the liveCache should normally be updated by the initialization of the planning version (and not by /SAPAPO/TS_LCM_CONS_CHECK).

These master data changes can lead to inconsistencies in one of the following situations:
  • The version is not initialized, or the initialization job terminates.
  • Jobs for changing the master data are terminated.
  • This problem is due to a program error.



Solution

Initialize the planning version
Initialize a version that has already been initialized, without first deinitializing it and without changing the initialization period (delta initialization).
  • For planning areas that do not have a time series key figure, it is sufficient to initialize one version.
  • For planning areas with time series key figures, you must initialize each version.


Correct inconsistencies
If the inconsistencies were generated by a program termination or a program error, you can correct them using /SAPAPO/TS_LCM_CONS_CHECK.

Correct the cause of the error
If the inconsistencies were generated by a program error, it is necessary to find the cause of the error and remove it. To ensure that SAP Support can find the cause of the error, you need to provide an exact description of the process that resulted in errors:
  • Which master data was changed and how?
  • Was the planning version initialized?
  • You can use the existing check programs to check the consistency of your data for each step: If you know which step led to the error, SAP can analyze your process with a view to providing a correction.

There are three check programs that you can use for consistency checks in SNP: /SAPAPO/TS_LCM_CONS_CHECK, /SAPAPO/TS_LCM_REORG_SNP and /SAPAPO/TS_LCM_REORG. You can execute the programs in repair mode by setting the "Repair" indicator. You should always block the planning version by setting the "Block planning version" indicator.

Check with /SAPAPO/TS_LCM_CONS_CHECK
This report checks the following for a version of a planning area:
  • The consistency of the SNP master data.
    It checks for all characteristics combinations, whether master data exists (unnecessary characteristics combinations), and whether there is master data without SNP master data (missing characteristics combinations).
    Since the SNP master data is version-independent, you only need to execute the master data check for one version of the model.
  • The liveCache anchors and time series in the liveCache.
    The report checks whether there are liveCache anchors and time series in the liveCache for the time series key figures for all characteristics combinations.
    If the 'Check liveCache anchor' indicator is set, the report checks whether the corresponding characteristics combinations exist for all liveCache anchors (only for DP planning areas).
    In the case of planning areas with time series, the time series must be checked for each version.

To correct the inconsistencies, you can execute the report in repair mode. For example, you can execute it before the planning run or after a mass change to master data to ensure a consistent status.
  • If you have set the "Check SNP master data" indicator, the report creates the missing SNP master data in repair mode and deletes the unnecessary SNP master data. Since the SNP master data is version-independent, you only need to execute the master data check for one version of the model.
  • If the planning area has time series key figures, the report deletes the liveCache anchors without SNP master data and the related time series in the liveCache in repair mode.


Check with /SAPAPO/TS_LCM_REORG_SNP
The report checks whether there is SNP master data for all liveCache anchors for a version of an SNP planning area. This check is required after you have deleted a large amount of master data.

To delete the superfluous liveCache anchors and the related time series in the liveCache, you can run the report in repair mode.

Check with /SAPAPO/TS_LCM_REORG
The report checks for a version for all DP and SNP planning areas whether there are liveCache anchors for all time series in the liveCache. This check is necessary if technical inconsistencies occur after a job was terminated.

To delete the unnecessary time series without liveCache anchors, you can run the report in repair mode.


Sequence of steps:
We recommend that you execute these program steps in the following sequence:
    1. /SAPAPO/TS_LCM_CONS_CHECK
    Since superfluous SNP master data is deleted, this program must be executed first.
    2. /SAPAPO/TS_LCM_REORG_SNP
    This program should be executed regularly for SNP planning areas with time series key figures after master data has been deleted in the system.
    3. /SAPAPO/TS_LCM_REORG
    This program should be executed after jobs are terminated to repair any technical inconsistencies in the liveCache.

Frequency of execution:
You should monitor the check programs over a sufficiently long period to estimate whether and when exactly they are required. Under normal circumstances, they should be used only to localize errors that create inconsistencies. You should execute the /SAPAPO/TS_LCM_CONS_CHECK program more often than the /SAPAPO/TS_LCM_REORG_SNP program and this more often than the /SAPAPO/TS_LCM_REORG program.
  • /SAPAPO/TS_LCM_CONS_CHECK
    Since the SNP master data does not depend on either the planning area or the version, you only have to check the SNP master data for one version of the model. The consistency check is not required after the planning version has been initialized. In the normal process flow, the consistency check should not take place before the planning run, but it can be carried out weekly, for example.
  • /SAPAPO/TS_LCM_REORG_SNP
    This program should be executed regularly after master data is deleted in the system. How often the program is executed depends on the quantity of deleted master data. You can always execute the program after a large quantity of master data is deleted, on a weekly basis, for example.
  • /SAPAPO/TS_LCM_REORG
    This program should be executed monthly to check the consistency of the time series in the liveCache.



Header Data

Released On 05.06.2009 09:57:53
Release Status Released for Customer
Component SCM-APO-SNP-BF Basic Functions
Priority Correction with medium priority
Category Consulting


Validity
This document is not restricted to a software component or software component version

References

This document refers to:
SAP Notes
1384831   9AMAPR inconsistencies for PDS in inactive version
1344612   Performance: Planning areas with time series key figures
1331576   Initialization and Delta Handling for SNP Master Data
1045639   Consulting notes in SNP/CTM
997456   Delta queues level 2 are not deleted
669287   Superfluous time series for SNP planning areas
402046   Error message 'No LiveCache anchor found'

This document is referenced by:
SAP Notes (6)
1045639   Consulting notes in SNP/CTM
1331576   Initialization and Delta Handling for SNP Master Data
1344612   Performance: Planning areas with time series key figures
1384831   9AMAPR inconsistencies for PDS in inactive version
997456   Delta queues level 2 are not deleted
669287   Superfluous time series for SNP planning areas

Thursday, July 3, 2014

Wondering why your SNP PA consistency and SNP Planning run takes too long to run? Try this note

Source: https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3133333135373626
SAP Note 1331567

Symptom
Whenever you create/change/delete APO Master Data, the SNP planning objects need to be updated. This note explains the process for updating SNP Master Data and the time series objects in liveCache.


Other Terms
Delta Queue, /SAPAPO/TS_PAREA_INITIALIZE, /SAPAPO/TS_LCM_CONS_CHECK, /SAPAPO/TS_LCM_QUEUE_UPDATE


Reason and Prerequisites
SNP Master Data is a (redundant) combination of APO Master Data entities and is used to access master data faster. SNP Master Data are so called planning objects and correspond to the aggregates defined in the planning object structure. SNP Master Data is used to access master data more efficiently (performance).


Solution
In order to avoid SNP inconsistencies you must run the initialization of the planning area and planning version after updating master data and before any every Master Data access in SNP (Interactive Planning, Heuristic Planning Run, Optimizer, ...).

The process for updating SNP Master Data cosists of following steps:
    1. Any change in APO Master Data is recorded in Delta Queue Table Level 1 (/SAPAPO/TSQUEUE):
    • Object Type (product, resource, ppm, transportation lane, ...)
    • Object Key (matid, resuid, ...)
    • Action (create, update, delete)
    • Sometimes the model
    2. The change documents stored in /SAPAPO/TSQUEUE are converted into SNP Delta Queue Level 2 entries. This step corresponds to program /SAPAPO/TS_LCM_QUEUE_UPDATE.
           Delta Queue Level 1 is analyzed (model(s) and version(s) are added), the possible characteristic combinations of Master Data are determined and stored to the Delta Queues Level 2.
           As a result, Delta Queue Level 2 will contain the combination of all keys of the changed master data, for all active planning areas and versions that are relevant for SNP.
              There are following Delta Queue Level 2 tables:            Aggregate Delta Queue Level 2 table
           9AMALO /SAPAPO/TSQMLO Material Location
           9AMALORE /SAPAPO/TSQMLOR Material Location Resource
           9AMALA /SAPAPO/TSQMLA Material Lane
           9AMALARE /SAPAPO/TSQMLAR Material Lane Resource
           9AMAPR /SAPAPO/TSQMP Material PPM/PDS
           9ARE /SAPAPO/TSQR Resource
           9AREPR /SAPAPO/TSQRP Resource PPM/PDS
           9AACPR /SAPAPO/TSQAP Activity PPM/PDS
           9AMALOSA /SAPAPO/TSQMLOSA Scheduling Agreement-Mat.-Loc.
           9AMALASA /SAPAPO/TSQMLASA Scheduling Agreement-Mat.-Lane
    3. For the planning area and planning version which is currently processed, the Delta Queue Level 2 entries are processed to create missing SNP Master Data.
              The SNP Master Data Tables are the following:            Aggregate Database table
           9AMALO /SAPAPO/MATLOC  (not SNP)
           9AMALORE /SAPAPO/MATLORES
           9ALORE /SAPAPO/LOCRES
           9AMALA /SAPAPO/MATLANE
           9AMALARE /SAPAPO/MATLARES
           9AMAPR /SAPAPO/MATPPM
           9AMARE /SAPAPO/MATRES
           9AREPR /SAPAPO/RESPPM
           9AACPR /SAPAPO/ACTPPM
           9AMALOSA /SAPAPO/MALOSA
           9AMALASA /SAPAPO/MALASA
    4. For one planning area and planning version, the Delta Queue Level 2 entries are processed to create missing time series objects in liveCache (liveCache anchors). At the end of this step the Delta Queue Level 2 entries are deleted.


Remarks:
  • Steps 2 and 3 are automatically processed before every Master Data access in SNP (Planning Area Initialization, Interactive Planning, Planning Run, Optimizer, ...)
  • Step 4 is not automatically processed, you must run initialization of the planning area and planning version.
    To not impact the performance, you must keep the delta queue level 2 tables as small as possible, this means step 4 needs to be processed for ALL initialized planning areas and planning versions.
  • If your APO Master Data is frequently updated and for performance reasons, the report /SAPAPO/TS_LCM_QUEUE_UPDATE equivalent to step 2 can be scheduled in background.
  • If you change/delete/add master data frequently and run consistency check report without performing snp relevant operations first, it is advised to run the report /SAPAPO/TS_LCM_QUEUE_UPDATE before as the Delta Queue Level 1 remains in this case and this can lead to remaining superfluous data.
  • In certain cases, the deletion of APO Master Data is not reflected to SNP Master Data and resulting of possible superfluous entries. This is due to performance reasons as the update of APO Master Data can occur frequently. It has no impact on SNP functionalities but can be fixed if needed by the consistency check report /SAPAPO/TS_LCM_CONS_CHECK.
  • You can check how many entries are in your system in the queue tables by running report Z_LCM_QUEUE_REORG which is attached to note 960941.




Header Data
Released On 26.04.2011 12:10:23
Release Status Released for Customer
Component SCM-APO-SNP-BF Basic Functions
Priority Recommendations / Additional Info
Category Consulting


Validity
This document is not restricted to a software component or software component version
References
This document refers to:
SAP Notes
1929402  Performance improvement in SNP queue update
1824737  Deadlock with tables of SNP master data
1809718  Don't check master data changes in SNP interactive planning
1560556  Master Data: missing entries for aggregates using resource
1408297  Performance improvement of Delta queue level 2 processing
1344612  Performance: Planning areas with time series key figures
1235120  Performance: SNP master data queue processing
960941  Performance: delta queues level 2 are not deleted
577038  Data inconsistencies in SNP
This document is referenced by:
SAP Notes (9)
577038  Data inconsistencies in SNP
1824737  Deadlock with tables of SNP master data
1235120  Performance: SNP master data queue processing
960941  Performance: delta queues level 2 are not deleted
1560556  Master Data: missing entries for aggregates using resource
1809718  Don't check master data changes in SNP interactive planning
1909789  Entries in table /SAPAPO/TSQUEUE deleted due to missing authorizations
1408297  Performance improvement of Delta queue level 2 processing
1344612  Performance: Planning areas with time series key figures