IBP Issues and Errors

Issue: IBP Snapshot job fails. 

Details: sql syntax error: "SAPHANADB"."/IBP/CL_OPERATOR_SNAPSHOT=>CALCULATE_NUMBER_OF_TS_DATA": line 120 col 7 (at pos 5745): incorrect syntax near "placeholder": line 1 col 52 (at pos 52)

Resolution: Apply a technical global parameter to avoid QTM processing for SNAPSHOT operator.

Create a Parameter named: DONT_USE_QTM, and value was set to X in Parameter Group: SNAPSHOT.

----------------------------------------------------------------------------

Master data and transaction data objects between SDI and S4 Hana add-on

 

SAP Cloud Integration - Source and Target

 SAP Cloud Integration - Source and Target

Planning Calendars and S4 Integration

 

Use the Planning Calendars app to view the calendars that were integrated from SAP S/4HANA.

After the inbound integration with IBP, you can display the calendars that you assigned for production, transportation, shipping, and receiving along with their details in the Planning Calendars app. The IBP planning calendars were generated from the assigned calendars. In the app, you can also create new planning calendars based on calendars from your external system.

You can check the calendar assignments in the following apps:

·         Production calendars: View Locations and View Location Materials

·         Shipping calendars: View Location Materials

·         Receiving calendars: View Location Materials

·         Transportation calendars: View Transportation Lanes

Source: SAP.com

Order-based Planning Runs

 Order-based Planning Runs

Source: SAP

Unified planning process flow - IBP

 

Difference of IBP Version and Scenario

 

Difference of IBP Version and Scenario

Source: SAP IBP Online help

Object Type	Version	Scenario
Purpose	Alternate plans maintained over time.	On-the-fly “what if” scenarios
Created By	Administration user at time of configuration. (The number of versions is defined during configuration.)	Planner or end user (dynamically when using the system)
Created From	Planning Areas app, by choosing Versions, and then New.	IBP Excel add-in by choosing Create in the Scenarios group.
Change Method	Copy Customers copy data between versions. As a result, a version is based on a copy (or an overlay of multiple copies) and not on a collection of deltas. Changes to the base version (or to another version that you copied from) do not automatically “shine through” in the target version of the copy.	Delta The system keeps track of all changes to key-figure values as delta records inside the scenario. If, at the same time, changes are made in the base version, these are visible in the scenarios, unless there are conflicting scenario deltas, in which case those take precedence. This change method could be thought of as “shine-through” logic.