You can use this function to release forecast data from the InfoProvider to Supply Network Planning (SNP). The release takes place directly to SNP. In other words, you do not need to load the forecast data first into a planning area in Demand Planning and thus into the time series liveCache.
You can use the categories for forecast orders (FA, FB, FC, and FD) for the release to SNP. You can release the forecast data from the following objects of the SAP Business Information Warehouse (BW):
As data sources for the release, you choose an InfoProvider and a planning version and key figure contained in the InfoProvider. If you do not specify any characteristics for product and location under Data Source: Extended Settings, the system uses the characteristics 9AMATNR and 9ALOCNO.
If you are working with descriptive characteristics for the release, you must specify a consumption group. You must also create at least one planning object structure and a planning area in Demand Planning. This planning area is only required so that you can generate consumption groups. You do not need to create a characteristics combination or store any planning data in liveCache.
The standard settings for the grouping condition are product and location, since the release to SNP always takes place at location product level. SNP can only evaluate additional characteristics if you are working with descriptive characteristics. To do so, you must specify a consumption group for the release that contains these characteristics. You must also specify these characteristics in the grouping condition.
If you are working with location splits, you restrict the characteristics exclusively to the location. The system does not evaluate any other characteristics during the release.
For the release, you can use all periodicities that are available in the InfoProvider. If the selected InfoProvider contains months and weeks, for example, you can select precisely these periodicities, but you cannot select days. For a release of the periodicity month or week or day, the system reads the data from the InfoProvider aggregated to week, month, or day level, and releases the data in the same periodicity to SNP. If you choose more than one periodicity (for example, month and week), the system performs the release with technical periods. If the InfoProvider contains the week and day periodicities and you choose both periodicities for the release, the system also reads the data here from the InfoProvider in technical periods. In this case, the technical periods are identical to the day periodicity.
If you use fiscal year as the periodicity, the selected InfoProvider must only contain one single fiscal year variant.
If you want to release the data aggregated at the level of a periodicity, but this periodicity is not available in the InfoProvider, you can either use a daily buckets profile or a period split profile. For more information about daily buckets profiles, see Planning Buckets Profile. For information about period split profiles, see Time-Based Demand Distribution.
If you use a period split profile, select exactly one periodicity in the InfoProvider.
Before the release, you can find out how large the data quantity is that you transfer to SNP. To do so, use Number of Hits in InfoProvider. The system then determines the amount of data for the planning version in the InfoProvider in the specified period.
The system adjusts the specified period automatically to the smallest periodicity available in the InfoProvider. For example, if only the periodicity “month” is available in the InfoProvider, and you enter January 15, 2005 to December 15, 2005 as the period, the system determines the data in the period January 01, 2005 to December 31, 2005.
If you want to release forecast data from the InfoProvider to SNP, on the SAP Easy Access screen, choose Demand Planning ® Planning ® Release ® Release from InfoProvider to SNP.
In the selected InfoProvider, the data is available in the month and week periodicities. You have chosen both periodicities for the release. The following figure shows how the system determines the technical periods:
The period displayed in the figure comprises the months January to March. A technical period corresponds to the smallest unit of the periodicity you have chosen, that is, a week. January starts in the middle of the first week of the year, whereby the start of the following months can also be within one week. As a result, technical periods, which are shorter than a week, occur at the start and end of the affected months.