Skip to end of metadata
Go to start of metadata


This document covers frequently asked questions from Consultants, Partners and Customers about SAP Integrated Business Planning Platform Topic - Calendars. If you have additional questions that need to be added, please contact the SAP IBP Customer Engagement Team (engage-ibp@sap.com).  


SAP IBP Platform Topic - Calendars  PDF | Recording

 Q: Can we have different Planning calendars for the same Plant based on suppliers, assembly, Mfg. Cells etc.?

A: 

You can do that by creating multiple calendar attributes and assign them to the corresponding master data type and then also to planning levels. If you for example have different calendars per supplier, assembly, manufacturing cell, then maybe you also have master data types for these like that:

Remember: if you want to use these calendars in time series and with the simplified key figure IBP_CALENDAR, it’s required to add the attribute to the planning level (as non-root).

Remember: if you want to use these calendars in OBP or TS Supply, then you have to adhere to the modeling restrictions there.

In other words: This is a question how to model and assign planning Calendars attributes to MDT in IBP. Let’s assume for TS world:

Calendar1 is Production Calendar and goes hand in hand with the location. You would assign this one to MDT for location You would upload your location master data and would assign the respective Planning Calendar IDx to Calendar1.

Locid

Descr

Calendar1

GeoLong

 

 

PLANT01

Plant Walldorf

ID1

 

 

 

 

PLANT02

Plant Hamburg

ID3

 

 

 

 

Let’s assume Calendar2 is driven by attribute Supplier.

SuppID

Descr

Calendar2

 

 

SUPP01

Samsung

ID4

 

 

 

 

SUPP02

Nokia

ID5

 

 

 

 

Let’s assume you have a planning level Product|Location|Supplier|Weekly and you have assigned the attributes Calendar1 and Calendar2 to this planning level.

For the Planning object  <Productx>|PLANT01|SUPP01@Weekly the planning Calendar ID’s ID1 and ID4 would be accessible and could be used in a key figure calculation on this level, e.g. to calculate the number of WorkingdaysInPlant@ Product|Location|Supplier|Weekly = IBP_CALENDAR(<a key figure>@Weekly, ‘Calendar1’)

 Q: Can factory calendars only be transferred from SAP-ECC/S4 HANA systems? Will it also work for integration with non-SAP ERPs?

A: Integration of factory calendar works from NetWeaver based systems either via SDI or via web service.

The upload of factory calendars from non-SAP-NetWeaver systems is not supported, here you can use the pre-installed factory calendars as basis. We hope that for next year we will see the factory calendar maintenance app which will then remove this limitation.

 Q: In time series based world: can we directly update non working days manually in IBP fiori  planning calendar app? Is there any way to upload these non working days from flat file directly in IBP?

A: We have a public service: SAP API Business Hub. At the moment this service is read-only, but it will be extended in future according to our plan so you would then be able to create, change, mark for deletion the planning calendars. If you think we should provide a file upload, maybe a new influence.sap.com entry would be nice!

 Q: If calendars are integrated through SDI, then we don't need to integrate through SAP_COM_0550. Correct?

A: Integration of factory calendar works from NetWeaver based systems either via SDI or via web service, never use both approaches. If you would use both, or if you would try to connect to more than one source system, then the „last one wins” would apply!

 Q: Is it possible to use 'planning calendars' for scheduling jobs?

A: The application job scheduling is based solely on factory calendars. The application jobs start based only on factory calendars and not on planning calendars.

 Q: Having a 3-layer system landscape, DEV-TST-PRD both for SAP S4 HANA and IBP, would you then transfer the factory calendars in S4 HANA DEV to IBP DEV and then transport to IBP TST + IBP PRD? Or from S4 HANA TST to IBP TST and from S4 HANA PRD to IBP PRD?

A: In a landscape with more than one system, we would advise that you either transfer factory calendars from the very same system into all IBP systems or you transfer matching pairs: IBP development system factory calendars from ECC development system, IBP test system factory calendars from ECC test system, IBP production system factory calendars from ECC production system. In case you transfer matching pairs, then please remember that the IDs of the factory calendars and planning calendars could differ. Make sure you do not transfer an object which contains a planning calendar ID across the landscapes (for example in permission filters or similar).

 Q: It is same ID for factory and planning calendar, but system keeps separate copy of it?

A: Yes, the factory calendars and the planning calendars are different objects. But the planning calendars in the IBP system automatically generate a corresponding planning calendar with the very same ID to simplify usage. This behaviour is independent on how you received the factory calendars: either preinstalled, or integrated via SDI or web service.

 Q: In response, will it use factory calendar or planning calendar?

A: All IBP functionality uses the planning calendars. Only the application job scheduling is based on factory calendars. But as every factory calendar in IBP has a twin in planning calendars which is automatically generated, things are simple.

 Q: I do not see a planning calendar Fiori app in our system. I don't see a planning basics tile group.  We only have S&OP module...why is this?

A: The authorizations are contained in the business catalog „Planning Basics” SAP_IBP_BC_PLAN_BASICS_PC which create the tile group „Planning Basics” where you will find the planning calendar Fiori app. The planning calendars are provided through the SAP IBP platform and are contained in all IBP licenses by default.

 Q: Is there any where-used functionality to check the usage of planning calendars in master data?

A: There is a where-used function executed once you mark a planning calendar for deletion. This prevents that you delete a planning calendar which is referenced by a calendar attribute in the master data. Apart of that, you can of course use Excel master data workbooks with the calendar attributes, but there is no general where-used of attribute values or planning calendar IDs.

 Q: Can I create factory calendars in IBP?

A: At the moment this is not possible. Only integration via SDI or web service is possible (and some factory calendars are pre installed content). We hope that for next year we will see the factory calendar maintenance app.

 Q: We can directly update exceptional days or non working days manually in planning calender Fiori app?  Is there any way to upload these days from flat file directly into IBP?

A: We have a public service: SAP API Business Hub. At the moment this service is read-only, but it will be extended in future according to our plan so you would then be able to create, change, mark for deletion the planning calendars. But there is no file-based upload at the moment.

For time-series based, you could go with a key figure which we call “adjusted working days”. This could be a calculated AND stored key figure based on IBP_CALENDAR calculation. There you could store exceptions manually as key figure. This could be one alternative to maintaining the planning calendars exceptional days. But there the use case must be investigated and discussed further.

 Q: Can we create a factory calendar in IBP from scratch?

A: At the moment this is not possible. Only integration via SDI or web service is possible (and some factory calendars are preinstalled content). We hope that for next year we will see the factory calendar maintenance app.

 Q: Is possible to MES connect with IBP Directly?

A: There is no standard integration between IBP and SAP MES (Manufacturing Execution System). Integration capabilities for IBP are described.

 Q: How do I import calendar from odata? My problem is: i need to schedule jobs within a ''custom calendar''. I see I cannot schedule jobs on custom calendars, so I need to do it via odata? If I want to try with odata, how do I do that?

A: The scheduling of application jobs is based on factory calendars. Therefore, you need to have factory calendars in your SAP IBP system. This you can achieve through two ways: via SDI or web service. But both of these possibilities require that you have an SAP ECC or SAP S4 HANA system. We hope to get a webservice and Fiori app for maintenance of factory calendars soon.

 Q: Any best practices around how to keep the calendars across the landscapes in sync? Challenge is to keep up the changes consistent across IBP development, IBP test, and IBP production. Is there a and change management process, as its configuration element?

A: Always use the same source system for the factory calendars integrated into IBP. There is no reason why not to use the very same ECC / S4 HANA system as source for IBP development, IBP test, and IBP production system. Instead of this option it’s possible to sync between matching pairs: ECC dev system with IBP dev system, ECC test system with IBP test system, etc. At the moment there is no export/import of factory or planning calendars in IBP.

 Q: Is it possible to have NW calendar and planning calendar with same ID?

A: Yes, because the factory calendars and the planning calendars are different objects. But the planning calendars in the IBP system automatically generate a corresponding planning calendar with the very same ID to simplify usage. This behaviour is independent on how you received the factory calendars: either preinstalled, or integrated via SDI or web service.

 Q: How are we able to take holidays into account for our own company and for our suppliers which have different bank holidays than our company? Is this part of planning calendar? Should we do this per supplier, country of the supplier, or otherwise?

A: You an achieve that depending on the exact use case in different ways. One option could be that your company calendar is maintained in factory calendars integrated from ECC. On top of these you create manually further planning calendars which specify the suppliers holidays as exceptional days. You could then use the two groups of calendars through different calendar attributes and then through different key figures. 

 Q: What modules are the planning calendars included with? Is this functionality only available with certain modules (i.e. demand planning, supply and response)?

A: The planning calendars are provided through the SAP IBP platform and are contained in all IBP licenses by default. Users will be able to see the Fiori app once you assign business catalog „Planning Basics” SAP_IBP_BC_PLAN_BASICS_PC. The app will appear in the tile group „Planning Basics”.

 Q: Are calendars useful only when day level planning is done?

A: You can use the planning calendars on any level. The calendar attribute is for example attached to location master data. Assign this attribute to the desired planning levels and you can consume the calendar information there. Based on the aggregation behaviour you configure, the key figure can provide you with the number of working days on any time profile level like week, month, etc. Remember to take care of the time dimension via SUM as aggregation and possibly do aggregation on any other dimension via MAX. This way you will get the working days of a week regardless of how many locations you aggregate over. See our example in the webinar.

 Q: Can the projected coverage key figure be calculated using the planning calendar? Is it possible to use IBP_CALENDAR to adjust logic of core key figures like coverage projected stock?

A: Yes, it’s possible to use the IBP_CALENDAR as input to the IBP_COVERAGE. Of course you cannot specify this directly but need to create a key figure which uses the IBP_CALENDAR and then this key figure is used in the IBP_COVERAGE.

 Q: Does IBP_GENERATE_MISSING_TP creates missing time periods and save them or just creates them on-the-fly for the specific key figure calculation?

A: IBP_GENERATE_MISSING_TP generates time period on the fly. This is done to prevent stored NULL values in the time series table. The generated time periods are not stored (and must not be stored by follow-up processes like copy operator).

 Q: In the example of IBP_GENERATE_MISSING_TP on slide 18 the key figure was stored?

A: Yes the key figure referenced by the IBP_GENERATE_MISSING_TP is a stored key figure in the presentation. But this key figure is used to define the planning level, to identify which planning objects are used, and to identify which periods are already available and which have to be generated. This key figure is not used to actually store the results. This is important: do not store the result of the IBP_GENERATE_MISSING_TP – if the result is used in a stored key figure, then activation will fail – if the result is used in a copy or disaggregation, then you can potentially blow your system through too much data being generated.

 Q: Does the amount of planning calendars influence the performance of the system? How many planning calendars can be handled by the system?

A: Tests have shown that there is no dependency between the number of planning calendars in the system and the performance of the processes using it. Of course there are some boundaries in case you go beyond several ten thousand planning calendars.

 Q: Can we say IBP_GENERATE_MISSING_TP can replace the COPY and create time period? Or is the IBP_GENERATE_MISSING_TP purely for planning calendars?

A: Yes, you can replace the copy operator with „create time perios” by using the IBP_GENERATE_MISSING_TP. But as always: this depends on your use case. The IBP_GENERATE_MISSING_TP would need to be mentioned correctly in the right places. Also keep in mind that you should set the horizon parameters in IBP_GENERATE_MISSING_TP in a meaningful way: the horizon in the parameters are applied without respecting the filter criteria! If you choose the horizon in the parameters too big, the memory consumption of your queries accessing the key figure which uses the IBP_GENERATE_MISSING_TP will be big, possibly too big for a single query – and then the query will potentially affect other processes in the system requesting memory at the same time.

Using the IBP_GENERATE_MISSING_TP you can avoid the storage of data on the database and you can use the result in all simplified key figures as if you would have data in all periods, this way AVG and others will provide correct values.

 Q: Does the IBP_GENERATE_MISSING_TP change the result of aggregated values? Does it have any effect on the aggregation behaviour?

A: On basic aggregations like SUM/MIN/MAX/AVG it will have no effect as they ignore NULL values. But it changes the result of the window functions (IBP_CAGGR and IBP_RAGGR) as these functions have different behavior with NULLs and missing periods as described in the help portal.

 Q: In the previous version, the coverage calculation in IBP is showing, for example a coverage of 3 days on Friday (due to the consideration of the non working days Saturday and Sunday) but in fact, the projected coverage is only one day, will it be solved with the introduction of the planning calendar? Is it possible to consider the planning calendar maintained in the projected coverage? 

A: Yes, it’s possible to use the IBP_CALENDAR as input to the IBP_COVERAGE. Of course you cannot specify this directly but need to create a key figure which uses the IBP_CALENDAR and then this key figure is used in the IBP_COVERAGE.

 Q: On time zone: is it configurable in each planning app or global parameter?

A: For a system wide default or (with IBP 2011) business user specific time zones, the global configuration is used (see here).

Certain planning operators allow to overwrite this setting through a new set of parameters (time zone calculation behaviour, time zone, or date & time). 

 Q: Is it planned to enhance the logic that the planning calendar will be recognized by customer source? Currently it will recognized only by location source?

A: IBP OBP doesn’t support customer source. Future roadmap shows plans to support VMI scenario with modeling of customer location and transportation lane.

 Q: What app do I use to integrate calendar via odata?

A: Integration of factory calendar works via SDI or web service. The maintenance of planning calendars in IBP through odata will be delivered with IBP 2011 and described in SAP API Business Hub..

 Q: Are there any plans on the roadmap to enable the calendar import from more than one ERP?

A: Currently no. The factory calendars have a data model which prevents that currently. The factory calendars reference holiday calendars and these in turn reference holidays. The holidays have a numeric key with only three digits. Merging the factory calendar from several systems would mean to also merge the holidays. This is not possible in a meaningful way. Therefore we currently only support integration of factory calendars from one source.

As soon as the maintenance (and export/import) of factory calendars within our IBP system is available, it would be a way to solve the issue through that.

 Q: How do I setup time zone for different locations?

A: The time zone mentioned in the webinar was not for calculation of transport durations or similar, but the time zone which is used to understand the time series time profile and the identification of the periods (buckets) in the time series functions. In order-based planning, the time zones are part of the location master data. But for time series the time profile is used and this defines for each period (bucket) a from- and to-timestamp. By default this timestamp is based on UTC, but this can be configured with IBP 2008 per system and with IBP 2011 by user even. To set this time zones up, the global configuration is used (see here).

 Q: Is there an option to not consider planning calendars during OBP planning runs?

A: You can achieve that by either not transferring the factory calendars from ECC / S4 HANA or even better by maintaining the ECC / S4 HANA factory calendars to have only working days.

 Q: Can you please briefly tell more about time zone and how it will affect scheduled jobs and what will be the impact of time zone on current period?

A: The time zone definition in the global configuration or the time zone parameter in the application jobs influences how the „current period” is calculated. The current period is the time bucket which is used to derive the planning horizon and to derive what is in the past and what is in the future. The planning horizon in the planning area is always defined relative to the current period. If you work on weekly level where the week starts on Monday and ends on Sunday, it’s of course important how you specify your time zone. Depending on that, a job scheduled in the early Monday morning would use identify the current week as the one of Monday or it would identify still the Sunday as current week.

 Q: Where do one link the calendar to supplier?

A: This differs a bit whether you are using order-based planning or time series based planning. If you are in order-based, then master data is maintained and integrated from ECC / S4 HANA and there the link is specified. For the time series based supply, the structures are also fixed. In case you are using time series and use the planning calendar in key figure calculation, then you are completely free on how you exactly do that. A proposal would be to have a calendar attribute in the same master data type as the supplier. In case your supplier is master data type „SUPPLIER”, then you can simply add a calendar attribute there as non-key called „SUPPLIERCALENDAR”. This attribute could be filled with the IDs of the planning calendar through usual master data maintenance options: data integration or maintenance in Excel master data worksheets.

 Q: Can the projected coverage key figure be calculated using the planning calendar?

A: This is dependent on the configuration the customer is using. From documentation perspective it should be possible. See the help. The coverage function uses as input the number of workdays by period.  Such a key figure was briefly described during our webinar and would definitely support the planning calendar.



  • No labels