Sap Forecasting and Replenishment Sap Fampr Warning Compress

7/31/2021
SAP Forecasting and Replenishment (SAP

F&R)
Generated on: 2021-07-31 14:56:02 GMT+0000
SAP Supply Chain Management (SAP SCM) | 7.0
PUBLIC
Original content: https://help.sap.com/viewer/39cdf8557a584dccbd9778782066bc73/7.0/en-US
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.
For more information, please visit the https://help.sap.com/viewer/disclaimer.
This is custom documentation. For more information, please visit the SAP Help Portal 1
7/31/2021
SAP Forecasting and Replenishment (SAP F&R)
Use
SAP Forecasting and Replenishment optimizes the internal logistics of retail companies by improving the replenishment
processes.
It aims to:
Cuts surplus stock in distribution centers and stores
Reduces stockouts in distribution centers and stores
Lessen the large amount of manual work required by implementing highly automated replenishment planning in stores
and distribution centers
Increase transparency in the supply chain through effective analyses
SAP F&R helps you minimize the total cost of ownership (TCO).
Integration
SAP F&R supports the import of data, such as:
Master data
Receipt of new and modi ed master data
Space management
Receipt of shelf data from a space management system
POS inbound
Receipt of sales data and updated historical sales data
Promotion planning
Receipt of data for planned promotions (demand in uencing factors)
Inventory management
Receipt of stock data
Purchasing
Receipt of manually created, created, or deleted order data
Supply chain execution
Receipt of partly or completely ful lled order quantities and consumption data from distribution centers
Store management
Receipt of store orders and store forecasts
SAP F&R supports the export of order proposals (which the purchasing system converts to purchase orders).
You can integrate an SAP Retail system or a different purchasing system. Connectivity is the process of receiving relevant data
from a sending system and exporting order proposals to the follow-up system. If SAP F&R receives external data, you need to
start the process in the sending system.
7/31/2021
For further information see Connection to the SAP Retail System.
 Note
SAP F&R provides an initial load for master data, historical sales or consumption data, demand in uencing factors
(DIFs), and stock data.
SAP F&R provides tools for the mass maintenance of F&R master data. When planning-relevant master data is not
available in SAP F&R, you can edit it in the master data retaining systems and then transfer it through the interfaces
in SAP F&R.
Constraints
SAP F&R does not support the following functions:
Although you can de ne time-dependent parameters, none of the processes support the use of planned master data.
SAP F&R does not provide a change history for master data.
SAP F&R does not change its parameters automatically on the basis of analysis or exception queries.
SAP F&R does not perform any general plausibility checks for parameter settings or settings in Customizing, however, it
does check the consistency of master data in maintenance.
Master Data
Use
If you wish to use SAP Forecasting and Replenishment (SAP F&R), you must ensure that at least the following master data
exists:
Product
Location product
Location
Supply network
Calendar
Procurement cycle (pro le)
Features
In SAP F&R, you have the following import and processing options for master data:
Master Data Objects Interface Individual Processing Mass Processing
Product x none none
Location product x none Modi able and time-dependent

parameters
Product hierarchy x x none
Location x x x
7/31/2021
Master Data Objects Interface Individual Processing Mass Processing
Location group x x none
Reference module x x none
Supply network: transportation x none Modi able and time-dependent

lanes for subranges parameters
Supply network: transportation x none Modi able and time-dependent

lanes for products parameters
Calendar none x none
Procurement Cycle (Pro le) x x none
Purchasing organization x none none
Purchasing organization x none none

assignment
Substitution assignment x x x
Contract x none none
Layout x none none
Unit of measure group x x none
Release pro le x x none
Rounding pro le x x none
SAP F&R also lets you de ne certain master data time-dependent: in this case, you specify a validity period for the
master data in question. If you want a parameter to be time-dependent, you must set this in Customizing. Note that the
ability to use time-dependent attributes function is limited to a prede ned set of modi able elds.
 Example
Example: You can use a different procurement frequency for confectionery products over the holiday period, which
contains additional order days and delivery days.
To edit time-dependent parameters in mass maintenance, you have to de ne them as modi able. You can de ne time-
dependent and modi able parameters independently of one another.
For more information about time-dependent parameters and modi able parameters in the master data, see the
Implementation Guide (IMG) of Forecasting and Replenishment under Master Data De ne Time-Dependent Fields and
Master Data De ne Maintainable Attributes .
Constraints
There are no interfaces for the following F&R master data:
Certain pro les, such as the restriction pro le
Calendars
 Note
You can transfer factory calendars as part of a Customizing transport. From these calendars, you can generate F&R-
speci c calendars (time stream IDs).
7/31/2021
 Recommendation
We recommend that you import the rest of the master data and that you use the interfaces with the inbound process
mode Using Interface Tables. In this mode, the system posts the data in the correct sequence (for example, location
and product master data before supply network). For more information, see the Implementation Guide (IMG) of
Forecasting and Replenishment under Interfaces De ne Message Types .
More Information
Overview of the Interfaces in SAP F&R
Inbound Master Data
Mass Processing of Master Data
Product
De nition
Products are material goods or services. They are the subject of business activities and are included in planning the value chain.
Products are location-independent.
Use
Products cannot be processed in SAP F&R. You have to transfer them from an integrated system (such as SAP Retail). For more
information about importing products, see Inbound Interface for Products.
More Information
Location Product
Product Hierarchy
Product Hierarchy
De nition
A product hierarchy models any number of strictly hierarchical product groups in a tree structure.
In SAP F&R, a product hierarchy is either a "true" product hierarchy (analogous to the article hierarchy in an SAP Retail
system) or a merchandise category hierarchy. In the latter case, the merchandise categories form the lowest level of the
hierarchy.
Use
You can create product hierarchies manually in SAP F&R or import an article hierarchy through the interface, for
example, from an integrated SAP Retail system.
SAP F&R uses product hierarchies for selection, for example, in the workbenches for order proposal management and in
the mass maintenance transactions.
You can use product hierarchies to de ne product hierarchy-dependent location groups.
7/31/2021
 Example
Products could have the following hierarchical relationship: Foods - Frozen Foods - Pizza.
 Note
The merchandise category that is de ned in SAP F&R must be entered as the valid merchandise category hierarchy in the
client-speci c customizing.
Settings for Hierarchy Structure and at Client Level
You de ne how many hierarchy levels you want the system to use, for example, for Structure Type Hierarchy and for
Object Type Product.
For more information about product hierarchies, see the Implementation Guide (IMG) of Forecasting and Replenishment
under Master Data De ne Hierarchy Structure .
SAP F&R uses this hierarchy structure when you create a hierarchy manually or transfer it to SAP F&R through the
interface.
You de ne a material category hierarchy, for example, which SAP F&R uses when selecting products from speci c
merchandise categories. For more information, see the IMG for Forecasting and Replenishment under Master
Data De ne Settings at Client Level .
More Information
Inbound Interface for Product Hierarchies
Hierarchy
Product Type Identi cation for Inbound Products
Use
You can import different source objects from external systems and add them to the SAP SCM product database. In some cases,
though, multiple source objects could have the same ID number but be considered different products: product 4711,
merchandise category 4711 and reference module 4711, and so on. SAP SCM needs to know what distinguishes these various
objects so that it can lter them properly in the user interface: for example, you want the F4 help to show a list of all products
in merchandise category 4711 rather than the single product 4711, or you want to see only the reference modules. To ensure this,
each incoming product has a product type based on the source object in the external system.
Integration
The Product Type elds in the MATMAP and MATKEY tables can contain the following entries:
Blank = Real product
1 = Merchandise category
2 = Merchandise category hierarchy node
3 = Regular product hierarchy node
4 = Reference module
7/31/2021
Using BAdI APO_BAPI_BUS10001 (method CHANGE_SAVEMULTIPLE2), you maintain the LT_PRODUCT_MAPPING
parameter to map the external product identi ers to these product types in SAP SCM.
BAPIs responsible for inbound processing use the PRODUCT_TYPE parameter to retrieve the external product identi ers.
Location
De nition
A location represents the source or target of a transportation lane in the procurement process. Location data includes, among
other things, the date on which the source location can deliver products and the date on which the target location can receive
them.
The following standard location types are relevant in SAP F&R :
External supplier
Distribution center
Store
Use
You can import locations through the interface - from an integrated SAP Retail system, for example - and then edit them in SAP
F&R.
To maintain locations, go to the SAP Easy Access screen and choose Forecasting and Replenishment Master
Data Location Maintain Locations .
More Information
Inbound Interface for Locations
Location Group
De nition
Location groups group locations together in a higher-level object.
Use
You can create location groups in SAP F&R (optional) or import them - for example, from an integrated SAP Retail system. In
SAP F&R there are the following location groups:
Product hierarchy dependent location groups
The locations can only belong to one location group. You can only de ne them without overlaps.
You use these location groups in mass processing for location products (to simplify data entry) to process parameters
for a location product at group level.
Product hierarchy dependent location groups are assigned to a node of a product hierarchy or merchandise category
hierarchy and only apply to that node (and its subnodes).
7/31/2021
You specify a reference location and assign dependent locations. To do so, go to the SAP Easy Access screen and choose
Forecasting and Replenishment Master Data Location Maintain Location Groups .
You do not have to create a hierarchy structure in Customizing in this case.
DIF dependent location groups ( DIF location groups)
Locations can belong to several location groups. You can de ne them with overlaps in a extended hierarchy. You use DIF
location groups to assign demand in uencing factors.
 Note
If you use DIF location groups, the location hierarchy you de ne in SAP F&R must be designated as a DIF location
hierarchy in the client-speci c Customizing.
Integration
Settings for Hierarchy Structure and at Client Level
You de ne how many hierarchy levels you want the system to use, for example, for Structure Type Hierarchy (or
Extended Hierarchy) and for Object Type Location.
For more information, see the Implementation Guide (IMG) of Forecasting and Replenishment under Master
Data De ne Hierarchy Structure .
You use this hierarchy structure when you create a hierarchy manually or transfer it to SAP F&R through the interface.
Note that you must have an appropriate structure in SAP F&R to import hierarchies.
You de ne a DIF location hierarchy, for example, which SAP F&R uses during location selection. For more information,
see the IMG for Forecasting and Replenishment under Master Data De ne Settings at Client Level .
More Information
Inbound Interface for Location Groups
Hierarchy
Location Product
De nition
A location product is a product that is assigned to a particular location.
Use
You can process modi able and time-dependent parameters for location products in the Replenishment Workbench (RWB)
individually or carry out mass processing of location products.
You can import location products from an integrated system (such as SAP Retail). For more information, see Inbound Interface
for Location Products.
Con guring Modi able and Time-Dependent Parameters
For more information about time-dependent and modi able parameters in the master data, see the Implementation Guide
(IMG) for Forecasting and Replenishment under:
7/31/2021
Master Data De ne Maintainable Attributes
Master Data De ne Time-Dependent Fields
Mass Processing
To maintain multiple location products at the same time, go to the SAP Easy Access screen and choose Forecasting and
Replenishment Master Data Product Maintain Location Products .
Deletion of Location Products
Use
You can delete location products that are agged for deletion together with their dependent objects in SAP F&R.
Integration
SAP F&R checks, on deletion of a master data object, which dependencies exist with other objects and weights the
dependencies in two steps:
With location products, primary dependencies exist for the following objects:
Open order proposals
Transportation lanes for products
Time series
Reference modules
Secondary dependencies exist with location products for the following objects (among others):
DIF occurrences
Stock data in the Logistics Inventory Management Engine (LIME)
Layout modules
Entries in the SCM component Collaborative Planning, Forecasting and Replenishment (CPFR)
Entries in interface tables for the BI System
The system runs a where-used check to determine the dependencies. For more information, see Where-Used List for
Master Data.
Archiving of location products is not planned (since SAP F&R is not the master data holding system).
There is a separate report available ( /SAPAPO/DM_REORG_PROD_LOC_TD) for deletion of the time-dependent data of
location products.
Prerequisites
You have imported master data for products and locations, for example, from the standard system (SAP Retail system).
As part of a delta transfer, you have transferred change records with deletion ag for location products, for example,
from the SAP Retail system.
Features
7/31/2021
You can delete the location products with report /FRE/DB_MATLOC_DELETE. In the standard system the report checks if the
system is still using a location product agged for deletion in the following places:
Interface tables (DIF) for location products
Extraction data for a linked BI system
Order proposal items with following types:
Replenishment-relevant items
Items to not transfer to the SAP Retail system
Substitution Assignments
If any one of the above conditions applies, the report does not delete the location product.
 Recommendation
You can de(activate) each check separately, however, we recommend that you activate all these checks.
 Note
Using the test run indicator, you can use the report in such a way that it only carries out a consistency check without deleting
the determined location products.
Activities
To delete location products, on the SAP Easy Access screen, you choose Forecasting and Replenishment Master
Data Reorganization of Master Data Delete Location Products .
Hierarchy
De nition
Hierarchies are used to model the relationships between master data objects of an object type (SAP F&R uses object types
product and Location).
Use
Once you have created a hierarchy structure in Customizing for structure types hierarchy and extended hierarchy, you can
transfer the hierarchies to SAP F&R through the interface or create them manually. You can then change and delete them in
hierarchy maintenance. To maintain hierarchies manually, go to the SAP Easy Access screen and choose Forecasting and
Replenishment Master Data Maintain Hierarchy .
You can create extended hierarchies for object type Location, such as DIF location hierarchies. For more information, see
Location Group.
You can create hierarchies for object type product, such as material category hierarchies. You cannot use extended
hierarchies here. For more information, see Product Hierarchy.
More Information
7/31/2021
Calendar
De nition
Calendars de ne exible time units and periods that SAP F&R uses for planning processes. A planning calendar is based on a
calendar and is mapped as a continuous time stream. Planning calendars are assigned to locations.
Use
You can import calendars (such as factory calendars) with a Customizing transport and create planning calendars with
reference to a calendar. SAP F&R uses planning calendars for scheduling. The system uses the planning calendar according to
the following rules:
If a calendar is not based on a factory calendar, SAP F&R uses the international factory calendar as a basis.
If a day is de ned as a workday in the planning calendar and in the factory calendar on which it is based, it is also
considered a workday in SAP F&R.
The day on which the business week starts in your calendar and how SAP F&R calculates the rst business week depend
on your client-speci c settings. For more information, see Business Week De nition.
You can assign and use three calendars for each location, based on the same or different planning calendars:
Order calendar
Corresponds to the production calendar in SAP SCM and de nes the working days in the purchasing department.
Goods receipt calendar
De nes the days on which a goods receipt is possible for a location.
Goods issue calendar
De nes the days on which a goods issue is possible for a location. External suppliers only need this calendar, for
example.
Maintaining and Assigning Calendars
For more information, see the Implementation Guide (IMG) of Forecasting and Replenishment under:
Master Data Maintain Calendar .
Forecasting and Replenishment Master Data Maintain Planning Calendar (Time Stream) .
You can also maintain the time stream of the planning calendar from the SAP Easy Access screen: Forecasting
and Replenishment Master Data Calendar .
You can assign the calendar in the master data for the locations.
To do so, go to the SAP Easy Access screen and choose Forecasting and Replenishment Master
Data Location Maintain Locations .
Scheduling
Use
7/31/2021
Scheduling calculates the decisive dates for an order proposal:
Planning date
Release date
Order date
Goods issue date
Delivery date
Availability date
The system calculates a day and time for these dates (with time stamp, such as 01:37:00).
The scheduling function does not have its own user interface. Instead, several applications in SAP F&R (such as the
Replenishment Workbench, the Product Workbench, and the F&R Processor) use it in the background.
Features
Scheduling takes different approaches to determining a valid order day and delivery day, dependent on the procurement cycle
and/or the planned delivery time:
If a procurement cycle is assigned to the transportation lane, the system derives the order day and delivery day from the
de nition of the procurement cycle as follows:
For procurement cycles with type order cycle/delivery cycle ( Forward Scheduling) and delivery cycle/order cycle
( Backward Scheduling), the system determines the order and delivery dates exclusively from the settings from
the procurement cycle (it also determines the planned delivery time from the procurement cycle).
For procurement cycles with type order cycle (forward scheduling) and delivery cycle (backward scheduling), the
system schedules using the planned delivery time determined from the transportation lane.
If no procurement cycle is assigned, the system schedules forwards exclusively. In this case, every working day is a valid
order day; the corresponding delivery day is calculated by adding the planned delivery time (from the transportation
lane) to the order day.
To calculate dates that are dependent on the order and delivery days (planning date, release date, goods issue date, availability
date), the system takes the following processing times into account from the transportation lane or the location product data:
Purchasing department processing time (order date - purchasing department processing time = planning date)
Order release time (planning date + order release time = release date)
Goods issue processing time (order date + goods issue processing time = goods issue date)
Goods receipt processing time (delivery date + goods receipt processing time = availability date)
 Note
If the processing times are not speci ed as multiples of days, the system rounds them up to full days during date calculation.
The following diagram illustrates how processing times are taken into account in scheduling:
7/31/2021
More Information
Scheduled Calculation of Replenishment Parameters
Business Week De nition
Use
7/31/2021
Forecasting & Replenishment (F&R) stores data for weekly processes, such as weekly consumption and forecast data for a
particular product. F&R uses weekly information for display (for example, in the Replenishment Workbench Time Series Screen
and DIF Calendar) and reporting purposes. The de nition of what is considered a "business week" may be different in different
countries or organizations.
In Europe, Monday is considered the rst day of the week, while the United States uses Sunday as the rst day, and Saudi
Arabia uses Saturday. Therefore it is important to de ne the starting day of the week and how the system is to calculate the
rst week of the year.
Integration
In Customizing (IMG path: Forecasting and Replenishment > Master Data > F&R Customizing on Client Level), you must make
the following entries:
First Week Day
You enter the weekday you want the system to use as the start of a business week.
 Caution
Once you enter a date here and save it, you will NOT be able to change it again as this would invalidate any time
series data generated with the previous setting. When you choose Save, the system displays a message asking you if
you are sure you want to save this day. Check your entry carefully before proceeding.
First Week of the Business Year
You make entries in these elds to specify how the system calculates the rst week:
Day of Reference Date
Enter the number of the day of the month you want to use as a reference point.
Month Reference Date
Enter the number month you want to use as a reference point.
Determination Rule of Business Week
Select the rule you want the system to use for the calculation. You can either select one of the standard rules, or
use BAdI /FRE/DB_MD_BADI_006 to create your own rule.
Example
Consider the calendar for January 2005:
S M T W T F S
26 27 28 29 30 31 1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30 31
7/31/2021
For Europe, the week begins on Monday, and the rst week of the year (calendar week 01) must contain three days after the
reference date (January 1). In this case, January 1 is a Saturday, and the following three days fall into the next week. Therefore,
the system determines that the rst business week of the year starts on Monday, January 3.
In the United States, the week begins on Sunday, and the rst week of the year is the week that contains the reference date. If
you entered January 1 as the reference date, then according to the calendar, this day is actually the last day of the last week of
December 2004. Therefore the system determines that the rst business week of the year 2005 starts on Sunday, December
26, 2004.
Scheduled Calculation of Replenishment Parameters
Use
In the standard system, SAP F&R calculates replenishment parameters such as the minimum or maximum inventory with
reference to the planning date. You can override this standard behavior in Customizing.
Integration
Changing the determination time for planning parameters affects the following components of SAP F&R:
F&R Processor
Replenishment Workbench
Replenishment Workbench for Stores
Product Workbench
Prerequisites
In Customizing for scheduled evaluation of replenishment parameters, you have de ned a determination date other than the
planning date. For more information, see the Implementation Guide (IMG) of Forecasting and Replenishment under Master
Data De ne Scheduled Evaluation of Replenishment Parameters .
Features
The system can - dependent on your Customizing settings - determine the following replenishment parameters for a date that
is different from the planning date:
Maximum stock
Minimum stock
Target stock
Maximum target range of coverage
Minimum target range of coverage
As the determination date for these parameters, you can use the following dates (instead of the planning date):
Order date
Delivery date
Availability date
7/31/2021
Procurement Cycle (Pro le)
De nition
The procurement cycle de nes the frequency with which products are ordered or delivered (weekly on a speci c day of the
week, for example).
You can use the following types of procurement cycles in SAP F&R:
Strict order cycle
Strict delivery cycle
Combined order and delivery cycle
SAP F&R calculates the planned delivery time as the difference between the order date and the delivery date, dependent on the
procurement cycle type.
Use
SAP F&R uses the procurement cycle within scheduling to calculate order days and delivery days.
You can create and maintain procurement cycles in the master data for pro le data for the procurement cycle. On the
SAP Easy Access screen, choose Forecasting and Replenishment Master Data Procurement Cycle .
You can assign a procurement cycle pro le to the transportation lanes for subranges or the transportation lanes for
products.
You can import procurement cycles. For more information, see Inbound Interface for Procurement Cycles.
Supply Network
De nition
A supply network consists of transportation lanes. It determines which products can be delivered between which locations.
Use
You can only procure products when transportation lanes exist between the possible locations in your system. You import
the transportation lanes through the interface.
In SAP F&R, the supply network is made up of the following levels:
Transportation Lane for Subranges
De nes replenishment-relevant settings at the subrange level or for all subranges. The transportation lane exists
between a source location and (one or all) target locations, as well as (one or all) subranges. When distribution
centers are involved, the subranges are merchandise categories; when external vendors are involved, they are
vendor subranges.
Transportation Lane for Products
Exists between a source location and (one or all) target locations.
If you have de ned certain parameters for the transportation lanes for products and subranges as modi able and time-
dependent in Customizing, you can change these parameters in mass processing. To maintain the transportation lanes
7/31/2021
of a supply network, go to the SAP Easy Access screen and choose Forecasting and Replenishment Master
Data Supply Network Maintain Transportation Lane for Products or Maintain Transportation Lane for Subranges.
Integration
Source determination
SAP F&R uses the transportation lanes for source determination. The system uses parameter BWSCL of the location product to
evaluate a supply source control, which determines the available source locations from all transportation lanes. Of these
locations, source determination selects a valid internal or external supply source - by priority, if de ned.
Depending on your settings in client-speci c master data Customizing, you may also be able to use the following functions in
source determination:
If SAP F&R determines more than one valid transportation lane, it selects the lane with the highest priority. You can use
the purchasing organization for source determination. In this case, SAP F&R gives higher priority to transportation lanes
whose purchasing organization is identical to the main purchasing organization of the target site (compared to
transportation lanes without an identical purchasing organization). For more information, see Inbound Interfaces for
Purchasing Organization Data.
You can decide whether the system should only consider transportation lanes with listed products in source locations. In
this case, a listing check is also performed for the distribution center (DC) determined as the supply source. If the
selected product is not listed at the DC, SAP F&R rejects the DC as a source of supply.
For more information, see the Implementation Guide (IMG) for Forecasting and Replenishment under Master Data De ne
Settings at Client Level .
More Information
Inbound Interfaces for Supply Network Information
Maintaining Transportation Lanes in the Supply Network
Use
You can create data for transportation lanes for the delivery network and de ne some as time-dependent. For example, you can
de ne procurement cycles whose validity is shorter than that of the transportation lane and only covers the duration of a sales
promotion.
Integration
Transportation lanes contain important parameters for the relationship between source and target location, for
example, procurement cycles for determination of the ordering and delivery dates or rounding rules.
If you have speci ed a parameter (for example, the procurement cycle) in both processing transactions for
transportation lanes (subranges and products), the system gives the highest priority to the parameter from the
transportation lane for products.
You can change the time-dependent data for transportation lanes (as well as the time-dependent data of location
products or of transportation lanes for subranges), using an interface import or by maintaining the transportation lane.
The scheduling calculates order dates and delivery dates with reference to the transportation lane. It evaluates the
time-dependent data of the transportation lanes to determine the planned delivery time and the procurement cycle.
7/31/2021
Prerequisites
You have imported transportation lanes from a connected system (such as SAP Retail) through the interface.
In Customizing of the time-dependent elds, you have used the similarly-named indicator to de ne which attributes of
the transportation lanes the system is to use time-dependently. You can use the following elds time-dependently:
Procurement cycle ( PROCYC)
Planned delivery time ( PLIFZ)
Procurement priority ( SPRIO)
With this indicator, you can temporarily assign a higher priority to one transportation lane.
Activation indicator ( BZQ_ACTIVE)
With this indicator, you can temporarily lock or activate a transportation lane.
 Note
The ags for procurement priority and activation have an immediate effect on source determination.
Features
You an assign a validity period to a transportation lane and maintain it for one of the following data combinations:
For a transportation lane for products:
Source location, destination location, and product
For a transportation lane for subranges:
Source location, destination location, destination location type, subrange of source location, and replenishment
planner
The destination location and subrange are optional. If they are not speci ed, then the transportation lane is valid for all
target locations and subranges.
You can delete time-dependent transportation lane data whose validity has expired:
Transportation lanes for products: with report /FRE/DB_REORG_LANE_TD.
Transportation lanes for subranges: with report /FRE/DB_REORG_TRPROD2_TD.
Activities
Maintaining Transportation Lanes
On the SAP Easy Access screen, choose Forecasting and Replenishment Master Data Supply Network Maintain
Transportation Lane for Products or Maintain Transportation Lane for Subranges.
Deleting Transportation Lanes
On the SAP Easy Access screen, choose Forecasting and Replenishment Master Data Reorganization of Master
Data Transportation Lanes for Products or Transportation Lanes for Subranges.
Substitution Assignment
7/31/2021
De nition
Assignment of a follow-up or replacement product to an original product. Together with the switchover information, this forms
the basis for consideration of product substitution in replenishment planning in SAP F&R.
Use
The system processes substitution assignments with location with greater priority than assignments without location. For more
information, see Displaying and Changing Substitution Assignments.
Displaying and Changing Substitution Assignments
Use
You use this function in order to display the follow-up and replacement product relationships that have been imported by way of
the inbound interface for substitution assignments and also to change some control parameters.
 Example
You display substitution assignments that are valid as of a certain date and do not yet contain a substitution merge pro le.
You select an assignment and assign a substitution merge pro le.
Integration
With this function, you cannot create or delete substitution assignments. You can create substitution assignments in a
connected SAP Retail system and export them to SAP F&R.
For each storage level, at any time, no more than one replacement product and no more than one follow-up product can
be assigned to an original product.
SAP F&R evaluates the switchover information belonging to a substitution assignment in the following areas:
Forecast and requirement calculation
Product Workbench and Replenishment Workbench
Cause Determination
Detail display for order item
Features
Selection
You can select substitution assignments according to different criteria. In addition to selection using location or product, you
can use the following options:
Include generic assignments
You can specify that the search result is to also contain assignments for which neither a location nor a location type is
de ned.
Substitution merge pro le
Output
7/31/2021
In the output view you can use the following functions:
Display detail data on selected substitution assignments, for example the conversion factors (with reference to the base
units of measure) for the original and the substitute product.
Select new selection criteria without switching screens.
Edit the following elds:
Consumption reference factor
This detail is only possible with follow-up product assignments.
Activities
1. On the SAP Easy Access screen, choose Forecasting and Replenishment Master Data Product Substitution
Substitution Assignments .
2. You enter at least one search criteria and carry out the search. The system displays the list of selected substitution
assignments.
3. In order to assign a (different) substitution merge pro le and a consumption reference factor to substitution
assignments, you switch to the change mode, edit this data and save your entries.
Mass Maintenance of Master Data
Use
SAP F&R provides transactions for the mass maintenance of master data, for example, to change data elds that the system
does not supply through default pro les from Customizing. You can maintain all elds that have been released for manual
changes. This applies to:
Location products
Locations
Transportation lanes for products
Transportation lanes for subranges
 Note
To avoid data inconsistencies, if you can supply elds with data through an import from the master data retaining system,
you should only make changes in that system.
Integration
In the Product Workbench, you can display all the master data for a location product, but you cannot maintain it.
Prerequisites
You have made the following settings in master data Customizing:
7/31/2021
You have con gured the elds to allow manual maintenance under Maintainable Attributes. For more information, see
the Implementation Guide (IMG) of Forecasting and Replenishment under Master Data De ne Maintainable
Attributes .
You have de ned planning responsibilities for planning and assigned them in SAP F&R. Only valid persons responsible can
be assigned to a location product in master data administration. For more information, see the Implementation Guide
(IMG) of Forecasting and Replenishment under Master Data Assign Planning Responsibilities .
If you want to use elds time-dependently, you have agged them accordingly. For more information, see the
Implementation Guide (IMG) of Forecasting and Replenishment under Master Data De ne Time Dependent Fields .
Features
Location Products
To start mass maintenance for parameters of location products, go to the SAP Easy Access screen and choose Forecasting and
You can maintain the data there at the location group level.
Locations
You can change data such as the calendars in the mass maintenance of locations. To do so, go to the SAP Easy Access screen
and choose Forecasting and Replenishment Master Data Location Maintain Locations .
Supply Network
You can perform mass maintenance of the modi able and time-dependent parameters for transportation lanes in the supply
network.
To maintain transportation lanes for products, go to the SAP Easy Access screen and choose Forecasting and
Replenishment Master Data Supply Network Maintain Transportation for Products .
To maintain transportation lanes for subranges, go to the SAP Easy Access screen and choose Forecasting and
Replenishment Master Data Supply Network Maintain Transportation for Subranges .
 Example
You change the following modi able, time-dependent elds: The optimizing horizon and the restriction pro le.
More Information
Master Data
Demand In uencing Factors (DIF)
Purpose
To achieve an automatic replenishment process that creates optimized order quantities, you need an accurate prediction of
future demand. This is normally done by using forecasting algorithms that calculate future demand volume based on historical
data. The following factors impact the quality of the demand forecast
High quality of the historical data on which the forecast is based
Selection of the most appropriate forecast model that describes the demand characteristics of a speci c produce
7/31/2021
The effect of past and future external in uences on demand (these are also known as Demand In uencing Factors, or
DIFs)
The Demand In uencing Factors (DIF) module provides input data for the automatic replenishment process. It allows the
demand forecast to take into account the effect of predictable external factors on demand. It also allows you to review, manage,
and adjust the DIFs as necessary.
Some examples of DIFs are:
Promotions and advertising campaigns
Public holidays or vacations (Easter, Thanksgiving, Christmas)
Sports events (Super Bowl, Soccer World Championship)
Sales prices and price changes
Unusual weather conditions (heat waves, hurricanes)
Implementation Considerations
In addition to the examples mentioned above, you can de ne DIFs for any other factors that can be quanti ed, maintained,
stored, and used to explain the sales or demand of a product. Such factors could include the aggregated store sales, total sales
area, shelf facings, store traffic, and so on.
 Note
You should choose DIFs carefully (especially the metric DIFs) during implementation so as not to overload the system or
decrease forecast accuracy.
Features
The in uence of DIFs is related to the time during which they are in effect:
Event DIFs are external events that are limited to a speci c and usually short time interval; that is, they have discrete
occurrences. Examples include promotions, advertising campaigns, or any calendar-related events such as public
holidays or sports events. The occurrences can be either yes-or-no events (that is, they occur or do not occur, such as
public holidays) or they can have a certain intensity (for example, hurricanes or heat waves). Those types of DIF are
generally valid for a larger selection of locations and products, and may not be product speci c.
Slow changing DIFs have a particular value that changes only occasionally; for example, a product's sales price. Such DIFs
are generally valid for only one product at a single location.
Fast changing DIFs change on an almost continuous basis that can be described by a time series rather than by individual
occurrences or changes to a DIF; for example, aggregated store forecasts as a predictor for the distribution center
forecast.
For new store openings, where no historical data exists for predicting future demand, you can de ne a reference store. The
system can use the historical data from the reference store to forecast demand for the new store. You can also de ne
reference products.
As part of the preparation of the forecast calculation, you can specify that exceptionally high or low values (outliers) be
automatically excluded. Since the occurrence of a DIF might cause an outlier-like sales/consumption value, you can suppress
the outlier correction function for periods that contain a DIF occurrence and instead explain the exceptionally high value by the
occurrence of the DIF.
7/31/2021
DIF occurrences can be active or inactive. Inactive DIF occurrences are ignored by the forecast calculation. If you are not certain
whether an event will occur, you can make the DIF inactive, then reactivate it when the situation is resolved.
There are two special types of DIFs:
Correction factor. You can correct forecasted demand values with a manually entered factor (for example, for rst-time
or one-time occurrences of a regular DIF).
Ignore. You use an ignore DIF to exclude historical demand periods from forecasting (for example, in the case of
unforeseen events that distort the consumption gures). The system uses average historical demand values instead.
DIF data that is no longer needed can be reorganized (deleted from the database),
DIF Workbench
Use
The DIF Workbench provides all the features and functions for managing DIFs.
A navigation tree displays all DIF objects on the left side of the screen, along with their assignments to locations and
products. It provides an overview of the existing DIF occurrences and also serves as a selection tool for the occurrence
list
The navigation tree is for display only - you cannot change the content. However, you can choose how you want the
information to be shown; for example, sort all products for a given location, or sort all locations where a given product is
sold. You can save the view as a user-speci c default so that your customized screen displays the same way each time
you access the DIF Workbench.
When you select a DIF (for example, Super Bowl) from the navigation tree, the right side of the occurrence list shows all
occurrences for that DIF. Each line in the list represents one occurrence and all its attributes. You can create, delete, or
change occurrences as necessary. If you are changing an occurrence, that occurrence is locked so that other users
cannot change it at the same time. There is also an Undo and an Undo All function that you can use to discard your
changes
You can select DIF occurrences from any level in the navigation tree (that is, DIF, DIF occurrence, location, or product
level).
The navigation tree is only updated when you save your changes.
On the lower right, the system shows any exceptions that may require user intervention. An example might be a rst-
time occurrence of a DIF: since it has not previously occurred, there is no history on which the system can predict future
impact. Errors in inbound data transmission also cause exceptions to appear.
In addition, you can jump from the main screen to screens for the following:
Detail view that gives detailed information for a single DIF occurrence. You can maintain the attributes for that
occurrence and its assignment to locations and products. (See Assigning DIF Occurrences for more information.) You can
also add a memo to a DIF occurrence to provide additional detail about an incident (for example, a temporary store
closing due to storm damage).
External data display that lists the actual values and validity periods for DIF occurrences that use external data (sales
price and time series). You can branch to this external data display from either the occurrence list or from the detail
view. (See DIF External Data Display for more information.)
Because different users have different responsibilities, they can:
Create selection variants for the DIF Workbench to re ect, for example, their responsibilities for speci c locations and/or
products.
7/31/2021
Con gure the DIF navigation tree and store it as a user-speci c default.
Assigning DIF Occurrences

Use
Depending on how a DIF is de ned, you can assign DIFs to locations (or location groups) and products, or to locations or location
groups only. It is also possible to assign a DIF occurrence generically; that is, to all products or all locations.
You can select a range of products or locations (or location groups). These are then displayed in the Assignment List. For
generic assignments, the list shows an asterisk instead of the location or product ID and description. The list can contain both
existing and potential assignment records.
In the Detail View change mode, there is an additional column indicating the current status of a record:
Assigned (currently stored in the database)
Created (assigned but not yet saved)
Deleted (but not yet saved)
DIF External Data Display
Use
For DIFs using external data, only dummy occurrences exist. They contain no actual values or validity periods. The External Data
Display lists the actual validity periods (valid from and valid to) and values by location and product for these DIFs. It also shows
header information about the DIF occurrence using this external data.
The values are displayed as they are used in the forecast calculation; that is, including any scaling factors applied to the original
values. The list also indicates whether there was a eld over ow or a zero result when applying the scaling factor.
 Recommendation
The amount of external data to be displayed for a single DIF occurrence can be very large, since a DIF occurrence can be
assigned to a large number of locations and products. Therefore, it is suggested that you restrict the data to be displayed
before you make your selection. You can make restrictions based on location, product, and time period
The External Data Display only allows you to view the data. You cannot make any adjustments to it.
Related Sales Dependency
Use
Related sales dependency refers to the impact of one product's sales on the sales performance of other products. This includes
both:
Cannibalization, where the effect is negative. For example, when a major brand of shampoo has a buy-one-get-one-free
promotion, the store brand shampoo may experience a decline in sales during that promotion period.
Affinity or halo effect, where the effect is positive. For example, if you have an in-house promotion on frankfurters, sales
of frankfurter buns will likely increase accordingly.
The system treats this as DIF (Demand In uencing Factor) information and transfers it to the forecasting engine. The forecast
calculation takes dependencies into account when predicting future sales of these products.
7/31/2021
The product on promotion is considered the leading product, and the product whose sales are affected is the dependent
product. The leading product's promotion is treated as a regular DIF, whereas the dependent product's data is considered an RS
DIF ( Relates Sales DIF). These DIFs are displayed graphically as separate time series in the Time Series screen.
 Note
The uni ed forecast shows the effects of all relevant DIFs for a given period. It is not possible to isolate and view the RS DIFs
alone if regular DIFs are included in the forecast.
You can de ne bidirectional pairs, where the leading and dependent products switch roles; that is, for two given products, the
leading product in one relationship becomes the dependent product in the other relationship.
You can view related sales dependencies in the various SAP F&R applications (Replenishment Workbench, Product Workbench,
and so on). You can see a list of all dependent products for single leading product, or all leading products for a single dependent
product.
Integration
The system does not automatically detect a dependency. You must de ne it manually. All dependencies are de ned at the
product level.
You can de ne a dependency in the Maintain Relates Sales Dependency screen, along with a validity area:
Generic (for all locations)
Speci c (for individual stores or store groups)
For a certain type of location (stores or distribution centers)
The system performs an authority check: if you do not have the proper authorization, you cannot maintain relates sales
dependencies.
DIF Schemas for Special Events
Use
You can calculate the estimated forecast error separately for regular periods and periods with special events. You de ne these
special events using the existing DIF functionality. You can also specify for which of the existing DIFs the system is to calculate
the estimated forecast error and thereby the safety amount separately. All periods with occurrences of these DIF are then
treated separately from the regular periods.
It is also possible to group multiple DIFs so that one common estimated forecast error and one safety amount are calculated
across all occurrences of the group DIF.
Integration
The forecast calculates a separate estimated forecast error per DIF schema and location product. The estimated forecast error
is calculated based on all periods where an occurrence of the DIFs assigned to the schema is active. This estimated forecast
error is the basis for the safety amount calculation for all future periods where an occurrence of a DIF assigned to the schema is
active. Such periods do not in uence the regular estimated forecast error and safety amount calculation for periods where
there is no active occurrence of a DIF assigned to the schema. In this way, you can achieve a more speci c safety amount
calculation for periods with special events such as promotions.
7/31/2021
Another effect of using a DIF schema is that the variability of periods with such special events does not have an effect on
regular periods without such events.
It is possible to de ne several DIF schemas and to assign one or more DIFs to each schema. However, you can only assign a DIF
to one schema. Only Boolean DIFs can be assigned to a DIF schema.
Activities
In Customizing for Demand In uencing Factors (IMG path: Forecasting and Replenishment > Demand In uencing
Factors > De ne DIF Schemas), you can de ne DIF schemas that can be used to calculate a speci c safety amount
during the validity period of DIF occurrences assigned to a schema. This is similar to the Customizing activity for de ning
DIF groups.
In Customizing for Demand In uencing Factors (IMG path: Forecasting and Replenishment > Demand In uencing
Factors > De ne Demand In uencing Factors), you use the DIF Schema eld to assign a schema to a DIF.
In order to use the DIF schema functionality, you must activate the DIF schema in the forecasting pro le. This provides
you with greater control of the DIF schema function, since you can use a forecast pro le to activate the function for
speci c location products.
In Customizing for the F&R Processor (IMG path: Forecasting and Replenishment > F&R Processor> Maintain Service
Level Pro les), you can specify additional service levels for each de ned DIF schema. The service level is the primary
differentiating factor between the various schemas.
DIF Reports
Use
The following reports are available:
Reorganization of DIF data (deletion of DIF occurrences)
DIF occurrences and their assignments to locations and products become obsolete when their validity period ends
before the forecasting time horizon. They also may become obsolete if a DIF is no longer used (removed from
Customizing) or if DIF occurrences are deactivated. This report, which can be run in the background, allows for mass
deletion of DIF data.
The report provides log information. Deleted objects are not stored to any archive.
Detection of rst-time occurrences
Future rst-time occurrences of a DIF have no effect on the forecasted demand since the forecast algorithms require
historical occurrences to estimate the future effect. This report, which can be run in the background, detects these rst-
time occurrences.
Detection of overlapping occurrences
This report detects all overlapping occurrences of a DIF within a given time period and that are assigned to the speci ed
locations and products.
Weighting Pro les
Use
The forecast algorithms in SAP Forecasting & Replenishment calculate forecasts by taking into account regular, week-based
DIFs (Demand In uencing Factors). The forecasts can be broken down subsequently into daily values that are then used in the
7/31/2021
requirements calculation and requirements quantity optimization. Daily values are calculated from the weekly values using
weighting pro les for the week (weekly pro les).
The system calculates dynamic weekly pro les from historical consumption data on a daily basis at either the location or
location product level (in other words, based on the consumption data for all products or on an individual product in a location).
In cases where it is not possible to calculate a dynamic pro le (for example, for new products that have no consumption history)
you can use a static weekly pro le.
Both the dynamic weekly pro les and the static weekly pro le show how consumption is distributed across a week. During a
speci c event, the distribution of consumption during a week can differ greatly from the regular distribution. For example, a
retail promotion can result in high consumption of a product at the start of a week, whereas high consumption is usually only
registered on the weekend.
You can replace the dynamic and static weekly pro les for a certain period and certain location products or locations with your
own customized pro les. If you want to replace an existing weighting pro le for a period longer than one week, you can choose
between the following weighting pro les:
Time-dependent weekly pro le. This is used in the same way as a static weekly pro le for all weeks in the relevant
period. The seven weighting factors in a weekly pro le represent the individual weekdays as a percentage of the total
consumption for the week. They correspond to the weekdays in consecutive order, starting with the rst weekday. The
sum of the factors does not have to equal 100%.
Event pro le. This means that the pro le pattern applies for the duration of an event, regardless of the day on which the
event starts and nishes and how many weeks it lasts. If necessary, the system can generate several different weekly
pro les for the forecast and the requirement calculation from this event pro le.
Because a speci c event may last for different lengths of time (for example, a retail promotion may last 10 days the rst time
and 12 days the next) but with the same consumption pattern each time, you can create a weighting pro le that has no xed
duration. You can then scale this to suit different periods and requirements by extending or shortening the time period.
For correction DIF occurrences, you can use a de ned weighting pro le to distribute a value that is valid for more than one day
to the individual days in a validity period. That is, you can take non-work days (days without consumption) into account by
distributing the percentage value from these days to the other days.
Since irregular consumption patterns such as the above can occur repeatedly for a certain event (for example, a retail
promotion), you can create the weighting pro les as reusable objects by assigning a unique ID to each pro le. You create,
change and delete weighting pro les as master data. You then assign weighting pro les to location products by entering the
weighting pro le ID in the appropriate DIF occurrence record.
You can also specify a weighting pro le as a default value for a DIF; the system automatically assigns this pro le when new
occurrences of this DIF are created. The value can be overwritten manually or deleted. If the DIF occurrence is created by the
inbound interface, a pro le assignment de ned in the interface overrides the default value.
 Note
You cannot assign a weighting pro le to a DIF occurrence with an "ignore historical value" category because this only affects
periods in the past.
Integration
In Customizing for DIF de nitions, you can specify that a DIF is used only for weighting pro les by entering W in the DIF Type
eld.
You can use the maintenance function in the master data to customize a weighting pro le as default value for new DIF
occurrences.
7/31/2021
Scaling a weighting pro le involves the time-based extension or shortening of a pattern that arises from the weighting factors
of the pro le to another period of time. This means that the number of weighting factors of the pro le is increased or reduced
to a different number, without altering the pattern of the weighting pro le. In addition to a scaling algorithm in the standard
delivery, a BAdI is available for customer-speci c scaling.
Converting an Event Pro le into Weekly Pro les
The system rst scales the event pro le to the validity period of the DIF occurrence. This means that the number of weighting
factors for the pro le is reduced or increased to the number of calendar days included in the validity period of the DIF
occurrence. If the duration of the DIF occurrence does not correspond to a whole number of weeks, the system uses one of the
following methods to ll up whole weeks, depending on the setting in the weighting pro le:
Filling up with a constant weighting factor: For the remaining days in the week(s) that are not covered by the event
pro le, the system generates a constant weighting factor. The value of the weighting factor is derived from a parameter
in the pro le. Valid values are:
Zero: For the remaining days in the week, use a weighting factor of zero.
Minimum: For the remaining days in the week, use the smallest of the existing weighting factors in the week as
the weighting factor.
Medium: For the remaining days in the week, use the mean value from the weighting factors in the week as the
weighting factor.
Maximum: For the remaining days in the week, use the highest of the existing factors in the week as the weighting
factor.
Scaling to whole weeks with the threshold value: The threshold value speci es the number of days in a week that has
been started, from which point the week is lled up to a whole one (in other words expanding the weighting pro le to this
week). If this threshold value is not reached, the weighting pro le is extended so that the part of the week that has been
started is no longer covered by the pro le.
Interfaces
Use
Interfaces enable you to connect SAP Forecasting and Replenishment (SAP F&R) to an ERP system (purchasing system). The
transferred data affects replenishment planning in SAP F&R. To calculate replenishment, and to plan in SAP F&R, you require
data that you import via the interface.
You can carry out the data exchange between the sending system and SAP F&R by using Remote Function Calls or by sending
SAP Exchange Infrastructure messages. To import data into SAP F&R, you must make certain settings in the sending system
(for example, technical settings for transfer and selection of the data). The sending system can be a SAP Retail system
(standard system) or a non-SAP system.
 Note
For performance-related reasons (following an initial data transfer), we recommend, if possible, that you send only changed
data to SAP F&R.
Integration
7/31/2021
You must create calendars in SAP F&R. You can import all other master data, with the exception of the optional restriction
pro le. The sending side must organize the transfer of the remaining data required in SAP F&R, and control the transfer using
regular background jobs, for example. SAP F&R cannot request the data. To continue working with the results of the
replenishment calculation (order proposals) in the follow-up system, you must export the order proposals from SAP F&R. You
can start this export either automatically or manually in SAP F&R.
SAP F&R supports the import of the following data:
Master data from a master data retaining SAP system (such as SAP Retail) or master data from a non-SAP system
POS Data
Data from a Logistics Execution system (LE)
Data from a stock managing system
Data from a store retailing system
Data from a shelf optimization system
Promotion data and demand-in uencing factors
For more information, see the Overview of the Interfaces in SAP F&R.
Features
You must always approach the F&R inbound interfaces from the sending system. For this, you can select the following
transfer methods for the data exchange:
Call-up of function modules in SAP F&R
The interface connection is commonly made using Remote Function Calls (RFC).
For every interface, you can use a Business Add-In to implement a customer-speci c processing block and to change the
data before posting in SAP F&R. For more information, see the SAP Implementation Guide (IMG) for Forecasting and
Replenishment under Interfaces Enhancements Using Business Add-Ins .
For the interface processing of SAP F&R, you can specify the following data processing options in Customizing:
Processing by interface tables
The system stores the data temporarily, in order to process it at a speci ed point in time. We recommend that
you set this option as an inbound process mode and then schedule the execution using background jobs.
When the data is saved temporarily in the interface tables, you can restart inbound processing at any time. If
processing is interrupted for any reason (for example, due to a power cut), you can resume it without loss of data.
Direct processing
The system posts the data immediately without storing it temporarily.
For further information, see the Implementation Guide (IMG) of Forecasting and Replenishment under
Interfaces De ne Message Types .
Constraints
You cannot export master data that was created or changed in SAP F&R to other systems, as no outbound interfaces are
planned for this.
7/31/2021
More Information
Interface Processing
Connection to the SAP Retail System

You can use the following inbound and outbound interfaces in SAP F&R:
Import
The following table shows the principal inbound interfaces in SAP F&R:
Interface RFC Function Module For more information on each interface, see:
Master Data
Product /FRE/BIF_PRODUCT_INBOUND2 Inbound Interface for Products
Location product /FRE/BIF_PRODLOC_INBOUND2 Inbound Interface for Location Products
Product hierarchy /FRE/BIF_PRODH_INBOUND2 Inbound Interface for Product Hierarchies
Location /FRE/BIF_LOCATION_INBOUND2 Inbound Interface for Locations
Location group /FRE/BIF_LOCGROUP_INBOUND2 Inbound Interface for Location Groups
Supply Network /FRE/BIF_TPSRC_INBOUND3 Inbound Interfaces for Supply Network

Information
Transportation lanes for subranges /FRE/BIF_TRSUB_INBOUND2 Inbound Interfaces for Supply Network
Information
Transportation lanes for products /FRE/BIF_TRPROD_INBOUND2 Inbound Interfaces for Supply Network
Information
Procurement Cycle /FRE/BIF_PROCYC_INBOUND2 Inbound Interface for Procurement Cycles
Reference module /FRE/BIF_REFMOD_INBOUND2 Inbound Interface for Reference Modules
Layout module /FRE/BIF_LAYOUT_INBOUND3 Inbound Interface for Layout Modules
Unit of measure group /FRE/BIF_UOM_INBOUND2 Inbound Interface for Unit of Measure Groups
Rounding Pro le /FRE/BIF_ROUND_INBOUND2 Inbound Interface for Rounding Pro les
Release Pro le /FRE/BIF_RELPRO_INBOUND2 Inbound Interfaces for Release Pro le Data
Release pro le assignment /FRE/BIF_RELPROAS_INBOUND2 Inbound Interfaces for Release Pro le Data
Purchasing organization /FRE/BIF_EKORG_INBOUND3 Inbound Interfaces for Purchasing Organization

Data
Purchasing organization assignment /FRE/BIF_EKORGAS_INBOUND3 Inbound Interfaces for Purchasing Organization

Data
Substitution assignment /FRE/BIF_SUBASST_INBOUND Inbound interface for substitution assignments
Transaction Data
Time series data (stock, consumption, goods /FRE/BIF_TSD_INBOUND2 Inbound Interface for Time Series Data
movement)
7/31/2021
Interface RFC Function Module For more information on each interface, see:
Demand in uencing factors /FRE/BIF_DIF_INBOUND2 Inbound interfaces for demand in uencing

factors
Contracts /FRE/BIF_CONTRACT_INBOUND Inbound interface for contract information
Order proposals /FRE/BIF_ORDER_INBOUND3 Inbound interface for order proposals
Switchover information /FRE/BIF_SUBSSW_INBOUND Inbound interface for switchover and switch

back information
Export
For the data export, SAP F&R supports the outbound interface for order proposals. You can reach this interface by way of the
following RFC function module: /FRE/BIF_ORDER_OUTBOUND.
Use
Interface processing is needed to exchange data with connected systems. Only after error-free posting of the imported data,
can SAP F&R take account of this data in replenishment planning.
Interface processing can work in two different modes:
If you use interface tables ( buffer mode), SAP F&R rst saves the data in buffer tables (interface tables). In a second
step, it then posts the data using scheduled background processing. This way you can prevent master data changes
during the replenishment process and you can ensure the consistency of the master data.
 Recommendation
We recommend that you use the buffer mode and that you carry out the transfer report using a background job at
least once a day in order to work with current data in the forecast. The buffer mode has the following advantages:
Prevents system being overloaded by peaks that cannot be estimated
Scales system load (caused by interface processing)
Safeguards time-critical applications by physical decoupling
Provides consolidated data
In direct processing ( direct mode), SAP F&R posts the data directly. If updating fails, SAP F&R ags the records that
could not be posted as incorrect, and saves them in buffer tables. SAP F&R creates an exception for each incorrect
record. You can process the records manually (like in buffer mode) or transport them again. This is controlled in the
sending system. In direct mode, you cannot de ne a background job to post the data.
In SAP F&R Customizing, you de ne which mode the system is to use for which interface. For more information, see the
Implementation Guide (IMG) of Forecasting and Replenishment under Interfaces De ne Message Types .
Process
1. You start the transfer in the sending system.
2. You post the data in the F&R interface processing (report /FRE/BIF_INB01). This step is required in the recommended
processing using interface tables. It does not apply with the direct mode.
7/31/2021
3. In the interface workbench you check if the system has posted the imported data without errors. You can correct
erroneous inbound data there and then post it again. In the productive system only the Status eld is changeable. In the
test client, all elds can be changed.
Inbound Master Data
Use
The master data interface is needed to import master data from connected systems. Which systems this data comes from
depends on your business processes and your system landscape and is a factor in the implementation.
Integration
SAP F&R assigns the appropriate default pro les from Customizing to the created master data. You can use the
provided standard pro les as default pro les or create copies of them and then adapt the copies to meet your speci c
needs. You can ag your copies as the default pro les for future master data imports.
For more information on the existing interfaces, see the overview of the interfaces in SAP F&R. Between the master
data objects that can be transferred, there exist dependencies that you must take into account.
Restrictions
SAP F&R does not export new or changed master data. Therefore master data that was changed in SAP F&R is
not synchronized with a follow-up system.
SAP F&R excludes products that are agged for cross-docking from automatic replenishment in a distribution
center.
You must create the calendar and the restriction pro le in SAP F&R.
Prerequisites
The sending system must control the F&R inbound interface. This requires scheduling in the sending system.
You have de ned in SAP F&R Customizing which master data you wish to import and process. You must make the
following minimum settings:
For each message type, you set the mode for processing the import data (for example, processing via
interfaces). For more information, see Interface Processing.
You de ne for which elds it is to be possible to import the content using an interface. For more information, see
the Implementation Guide (IMG) of Forecasting and Replenishment under Interfaces De ne Maintainable
Attributes .
Master data can only be imported correctly if the corresponding location and product master data exists in SAP F&R. If
this is not the case, SAP F&R stores this data agged as incorrect in the appropriate interface table. You can repost this
data using the Interface Workbench.
Features
You can import complete master data records or only changes to master data.
When you import master data, SAP F&R checks whether incorrect or unprocessed records already exist for an object in the
buffer tables. If so, the new record overwrites existing records. This procedure reduces the volume of data within the interfaces
and helps to consolidate data in the run-up to posting.
7/31/2021
This means that if you transfer master data changes to SAP F&R several times a day, but the posting job only runs once a day,
data can be consolidated in advance.
Inbound Interface for Products
Use
You use this interface to import product master data from other systems into SAP F&R.
Integration
You can use a Business Add-In ( /FRE/IF_CON_BADI_005) to enrich and change the imported product data. For more
information, see the Implementation Guide (IMG) for Forecasting and Replenishment under Interfaces Enhancements
Using Business Add-Ins BAdI: Product Data Enrichment .
If SAP F&R transfers identical ID numbers for different products from a sending system, you can use a Business Add-In (
APO_BAPI_BUS10001) to identify the products uniquely. For more information, see Product Type Identi cation for
Inbound Products.
Prerequisites
In the sending system, you have de ned which products you wish to export to SAP F&R.
Features
You can import the following product data:
Basic data
Product descriptions (language-dependent texts)
Units of measure
Activities
1. The integrated sending system starts the transfer and calls appropriate function module for the interface in SAP F&R.
2. You then post the data in SAP F&R.
More Information
Master data: Product
Inbound Interface for Location Products
Use
This interface enables you to import master data for location products from other systems into SAP F&R.
Integration
7/31/2021
Dependencies exist between a location product and location and product master data.
Prerequisites
You can only post location products if the related product and the related location exist in the master data of SAP F&R.
Features
You can import the following information:
Basic data
Time-dependent parameters of the location product
Alternatively, SAP provides a new interface for the location product data. For more information, see SAP Note 1169925.
Activities
More Information
Master data: Location Product.
Product Type Identi cation for Inbound Products
Use
You can import different source objects from external systems and add them to the SAP SCM product database. In some cases,
though, multiple source objects could have the same ID number but be considered different products: product 4711,
merchandise category 4711 and reference module 4711, and so on. SAP SCM needs to know what distinguishes these various
objects so that it can lter them properly in the user interface: for example, you want the F4 help to show a list of all products
in merchandise category 4711 rather than the single product 4711, or you want to see only the reference modules. To ensure this,
each incoming product has a product type based on the source object in the external system.
Integration
The Product Type elds in the MATMAP and MATKEY tables can contain the following entries:
Blank = Real product
1 = Merchandise category
2 = Merchandise category hierarchy node
3 = Regular product hierarchy node
4 = Reference module
Using BAdI APO_BAPI_BUS10001 (method CHANGE_SAVEMULTIPLE2), you maintain the LT_PRODUCT_MAPPING

parameter to map the external product identi ers to these product types in SAP SCM.
7/31/2021
BAPIs responsible for inbound processing use the PRODUCT_TYPE parameter to retrieve the external product identi ers.
Use
You use this interface to import hierarchical relationships between products into SAP F&R.
Integration
You can use a Business Add-In ( /FRE/IF_CON_BADI_006) to enrich and change the imported product hierarchy data. For
more information, see the Implementation Guide (IMG) under Forecasting and Replenishment Interfaces Enhancements
Using Business Add-Ins BAdI: Product Hierarchy Data Enrichment .
Prerequisites
In the sending system, you have de ned which product hierarchies you wish to export to SAP F&R.
In order to create or modify a hierarchical relationship, the corresponding products must exist in SAP F&R.
Features
You can import the following information:
Product hierarchy nodes
Links between product hierarchy nodes
Activities
More Information
Master data: Product Hierarchy
Inbound Interface for Locations
Use
You use this interface to import location master data into SAP F&R.
Integration
The location can be one of the following types:
Distribution center
Store
7/31/2021
Vendor
You can use a Business Add-In ( /FRE/IF_CON_BADI_007) to enrich and change the imported location data. For more
information, see the Implementation Guide (IMG) for Forecasting and Replenishment under Interfaces Enhancements
Using Business Add-Ins BAdI: Location Data Enrichment .
Prerequisites
In the sending system, you have de ned which locations you wish to export to SAP F&R.
Features
You can import the following information to SAP F&R:
Basic data
such as location type, time zone, pro le name
Descriptions
Language-dependent texts
Communication data
such as telephone, fax, e-mail, URL
Activities
More Information
Master data: Location
Use
You use this interface to import location groups into SAP F&R.
Integration
You use location groups in the de nition of demand in uencing factors and in mass processing of master data.
You can use a Business Add-In ( /FRE/IF_CON_BADI_008) to enrich and change the imported location group data. For
more information, see the Implementation Guide (IMG) for Forecasting and Replenishment under
Interfaces Enhancements Using Business Add-Ins BAdI: Location Group Data Enrichment .
Prerequisites
In the sending system, you have de ned which location groups you wish to export to SAP F&R.
7/31/2021
Features
You can import the following location group types:
Location group for DIF
Location group for master data
Activities
More Information
Master data: Location Group
Inbound Interfaces for Supply Network Information
Use
Using these interfaces, you import data on the ow of goods of products and subranges between the individual locations for
which you wish to plan.
Integration
You can process time-dependent and modi able parameters for transportation lanes for subranges in mass processing.
On the SAP Easy Access screen, you choose Forecasting and Replenishment Master Data Supply Network Maintain
Transportation Lane for Subranges .
You can use Business Add-Ins (BAdIs) to enrich and change the imported transportation lanes. For more information, see
the Implementation Guide (IMG) for Forecasting and Replenishment under Interfaces Enhancements Using Business
Add-Ins .
BAdI: Transportation Lanes for Subranges Enrichment ( /FRE/IF_CON_BADI_010)
BAdI: Transportation Lanes for Products ( /FRE/IF_CON_BADI_011)
 Note
You can transport transportation lanes for products from the purchasing system together with the related external
procurement data to SAP F&R.
You can use a BAdI ( /FRE/IF_CON_BADI_012) to enrich and change the external procurement data. For more
information, see the Implementation Guide (IMG) for Forecasting and Replenishment under
Interfaces Enhancements Using Business Add-Ins BAdI: External Procurement Data Enrichment .
Prerequisites
In the sending system, you have de ned which transportation lanes you wish to export to SAP F&R.
Before the import of the transportation lanes, you have already imported to SAP F&R the locations and location
products that are used in the transportation lanes.
7/31/2021
When you transfer transportation lanes for products, you must also transfer the related external procurement data at
the same time.
Features
You can carry out the transfer of the transportation lanes for subranges or products independently of each other:
Transportation lanes for subranges (SAP F&R uses the message type TRSUB for these):
Transfer of basic data for transportation lanes for subranges and their dependencies
Transportation lanes for products (SAP F&R uses the message type TRPROD for these):
Transfer of basic data for transportation lanes for products
External procurement data (SAP F&R uses the message type TPSRC for these):
Transfer of basic data for the supply network
Activities
More Information
Master data: Supply Network
Inbound Interface for Procurement Cycles
Use
You use this interface to import procurement cycles from other systems into SAP F&R. SAP F&R requires the procurement
cycle within scheduling in order to determine the order days and delivery days.
Integration
In order to be able to use the procurement cycle in replenishment planning, you must assign a delivery relationship to it.
You can assign this assignment either interactively in SAP F&R using mass maintenance of transportation lanes for
products ( /FRE/MASS_TRPROD) or when you import the supply network (of external procurement data).
You can use the Business Add-In ( /FRE/IF_CON_BADI_017) to enrich and change the imported procurement cycle
data. For more information, see the Implementation Guide (IMG) for Forecasting and Replenishment under
Interfaces Enhancements Using Business Add-Ins BAdI: Procurement Cycle Data Enrichment .
Features
You use this interface to de ne, modify, and delete procurement cycles in SAP F&R. You can import the following information:
Procurement cycle type (for example, delivery cycle or order cycle)
Planned delivery time
7/31/2021
Period with unit of time (daily or weekly cycle)
Activities
More Information
Master data: Procurement Cycle
Inbound Interface for Reference Modules
Use
You use this interface to import reference modules (and reference assignments) into SAP F&R.. The system uses reference
modules to create a forecast for products without historical sales data.
Integration
Reference modules consist of header and item data. The item data represents the reference of the module. You can
assign reference modules to several location products to reduce the amount of data. Reference modules contain all
location products whose consumption values are to be used to compile an arti cial time series. For more information,
see Creating an Arti cial History with References.
Using the Business Add-In ( /FRE/IF_CON_BADI_023), you can enrich and change the imported reference module
Interfaces Enhancements Using Business Add-Ins BAdI: Reference Module Data Enrichment .
Prerequisites
In the sending system, you have de ned which reference modules you wish to export to SAP F&R.
The products and locations used in the imported reference modules must exist in the SAP F&R master data.
Features
Location
Number of the reference module
Valid-to date of the reference module
Reference Determination Type
Activities
7/31/2021
Inbound Interface for Layout Modules
Use
You use this interface to import layout modules into SAP F&R. You use layout modules to group articles that you want to display
in the same place in a store. A layout module can correspond to one or more shelves.
Integration
Layout modules map the shelves in the stores. You use layout modules in the store for planning and in sales.
A layout module can contain several layout module versions. A layout module version has a validity period and
contains the products on a shelf. You can assign a product to several layout module versions and you can also
position a product in different places on the shelf within the same layout module version. If the validity period
changes, the system requires the layout module version.
Layout module variants relate to exactly one layout module version and they are used to map regional or store-
speci c variations in layout modules. Layout module variants have exactly the same validity period as the version
to which they relate. They contain newly added products and products to be removed, that is, only the changes to
the layout module version; they contain no unchanged products.
You assign the layout modules to stores using layouts and assortments. You can assign layouts to the
assortments in a store. Each layout consists of one or more layout modules. Using the layout area, you map the
spatial assignment of a layout module in the layout. SAP F&R saves the data at product-location-layout module
level. The assignments are time-dependent.
You can use the Business Add-In ( /FRE/IF_CON_BADI_020) to enrich and change the imported layout module data.
For more information, see the Implementation Guide (IMG) for Forecasting and Replenishment under
Interfaces Enhancements Using Business Add-Ins BAdI: Layout Module Data Enrichment .
Prerequisites
If you use a product in a layout module more than once, you must add up and transfer the stock-related control
parameters in the sending system. If a product is placed in several layout modules, the parameters are rolled up within
SAP F&R.
From within an SAP Retail system, you can only transport released layout modules for planning-relevant and placed
products to SAP F&R. If a product is placed in several layout modules, the parameters are rolled up within SAP F&R.
You use the base unit of measure in the sending system for stock-related control parameters.
Features
Product
Location
Layout module
Layout module version
Validity start and nish
7/31/2021
Minimum stock
Maximum stock
Target stock
 Note
SAP F&R aggregates the minimum stock, maximum stock, and target stock at the location/product/validity period
level. The system takes these aggregated quantities into account when calculating the order quantity (of a location
product) during the FRP run.
Inbound processing in SAP F&R supports the creation, modi cation, and deletion of objects. In addition, you can use the
following functions within inbound processing for layout modules:
Deletion of all layout modules with an assignment to a location
Deletion of all assignments to a layout module. This applies to all versions of the layout module in question.
Deletion of all assignments to a layout module and a version. The system deletes the speci ed version of the layout
module concerned.
Deletion of all assignments to a product. This applies for all assignments to a product over all locations.
Aside from this, SAP F&R does not have a user interface for maintaining layout modules.
Activities
Inbound Interface for Unit of Measure Groups
Use
You use this interface to import unit of measure groups into SAP F&R. The system uses the unit of measure groups in order
quantity optimization.
Integration
You can hold products in different units of measure and also group units of measure. SAP F&R considers the order units
of the unit of measure group during rounding or when creating order proposals. Unit of measure groups are assigned to
supply networks. You can import this assignment using this interface or you can assign the unit of measure groups
manually in mass processing of transportation lanes for products.
You can use a Business Add-In ( FRE/IF_CON_BADI_019) to enrich and change the imported unit of measure group
Interfaces Enhancements Using Business Add-Ins BAdI: Unit of Measure Group Data Enrichment .
Features
You use this interface to de ne, modify, and delete unit of measure groups in SAP F&R. You can import the following
information:
7/31/2021
Name of the unit of measure group
Indicator for taking units of measure into consideration
Units of measure
Activities
More Information
Unit of Measure Groups
Inbound Interface for Rounding Pro les
Use
You use this interface to import rounding pro les. SAP F&R uses these in order quantity optimization to round to logistical units
of measure.
Integration
You can also transfer the assignments of rounding pro les to supply relationships using this interface. You can also
assign the rounding pro le to a transportation lane interactively in SAP F&R in mass processing of transportation lanes
for products.
Using the Business Add-In ( /FRE/IF_CON_BADI_018), you can enrich and change the imported rounding pro le data.
Interfaces Enhancements Using Business Add-Ins BAdI: Rounding Pro le Data Enrichment .
Features
You use this interface to de ne, modify, and delete rounding pro les in SAP F&R. You can import the following information:
Zero rounding indicator
Unit of measure
Threshold value for rounding up and down
Activities
More Information
Rounding Pro les
7/31/2021
Inbound Interfaces for Release Pro le Data
Use
You use these interfaces to import release pro les and their assignments. SAP F&R uses this data in the automatic release of
order proposals.
Integration
In release pro les, you de ne conditions that SAP F&R takes into account when releasing order proposals. A possible
release criterion could be the minimum order value for orders.
You can export released order proposals to an SAP Retail system, where you can then create orders based on them.
You can use Business Add-Ins to enrich and change the imported data. For more information, see the SAP
Implementation Guide (IMG) for Forecasting and Replenishment under Interfaces Enhancements Using Business Add-
Ins .
BAdI: Release Pro le Data Enrichment ( /FRE/IF_CON_BADI_021)
BAdI: Release Pro le Assignment Data Enrichment ( /FRE/IF_CON_BADI_022)
Features
Using two separate interfaces for release pro les and their assignments, you can de ne, change and delete release pro les and
their assignments in SAP F&R. You can import the following data:
Release Pro les
They contain data such as:
Pro le number (unique identi er for the pro le)
Destination location and source location
Subrange
Short text
Object and value of the release condition
Condition type
Dimension
Threshold value
Currency
Priority
Valid-to date
Release Pro le Assignments
Using these, you group release pro les at the level of source location - target location - vendor subrange.
Activities
7/31/2021
More Information
Order Proposal Management: Release Pro le
Inbound Interfaces for Purchasing Organization Data
Use
You can import the following data to SAP F&R:
Purchasing organizations
Purchasing organization assignments
Integration
SAP F&R copies purchasing organization data in the following places:
In the source of supply data (as an attribute of the transportation lane)
In the master data:
The list of all purchasing organization data and its text description
All assignments of purchasing organizations to locations and the indicator for the standard purchasing
organization of the location
The following Business Add-Ins (BAdIs) let you make customer-speci c changes to the imported purchasing organization
data:
BAdI: Enrichment of Purchasing Organization Data ( /FRE/IF_CON_BADI_025)
BAdI: Enrichment of Purchasing Organization - Assignment Data ( /FRE/IF_CON_BADI_026)
For more information, see the SAP Implementation Guide (IMG) for Forecasting and Replenishment under
Interfaces Enhancements Using Business Add-Ins .
You can display the purchasing organizations and purchasing organization assignments that have been imported to SAP
F&R but you cannot change them.
The system shows in mass processing of locations if purchasing organization assignments exist. If they do exist, you can
display the purchasing organizations assigned to the target location together with the indicator for the standard
purchasing organization.
 Note
Changes to the purchasing organization assignments are only possible by way of a new initial or delta data transfer.
Prerequisites
You have made the settings for interface processing and set the indicators for purchasing organizations and purchasing
organization assignments there under selections for product/target location.
7/31/2021
If the system is to take purchasing organization assignments into account in source of supply determination, you have
made appropriate settings in client-speci c Customizing of the master data. For more information, see the IMG for
Forecasting and Replenishment under Master Data De ne Settings at Client Level .
Features
You can transfer purchasing organization data and purchasing organization assignments in SAP F&R using the complete
initial data transfer. Report FRE_EKORG_ASSIGN_INIT_LOAD lets you start an initial data transfer from the SAP Retail
system for the purchasing organizations only.
You can carry out a delta data transfer of locations from an SAP Retail system. Here the system also transfers the
assignments of the purchasing organizations to locations.
If the system (see prerequisites) takes the imported purchasing organization data in the source of supply check into
account, it uses only the transportation lane where the purchasing organization is assigned to the target location. If
multiple transportation lanes exist, the system uses the one with the standard purchasing organization.
Activities
Inbound Interface for Substitution Assignments
Use
With this interface, you can import the following data of a substitution assignment to SAP F&R:
Original product
Substitute product
Substitution control with the following types:
Follow-up product, time-controlled
Follow-up product, event-controlled
Replacement product, event-controlled
For more information on the compatibility of the substitution controls of imported substitution assignments, see System
Behavior on Import of Substitution Assignments.
Location and location type
 Note
If the substitution assignment is valid globally, the system SAP Retail system (the master data retaining system)
does not transfer a location or location type.
Start and end of the switchover period
Conversion factor
The system imports a conversion factor for conversion of the base units of measure for each of the original and
substitution products; the system uses in both cases as default the value 1 and takes account of the conversion factor,
7/31/2021
for example, when merging the consumption data.
If the eld location is lled on import of a new (not yet existent in SAP F&R) substitution assignment and no substitution
merge pro le is speci ed, the system allocates to the substitution assignment that substitution merge pro le that is
agged as the default pro le for the location type. The system uses the global default pro le for substitution
assignments without location. For more information, see the Implementation Guide (IMG) of Forecasting and
Replenishment under Substitution Products Substitution Merge Pro les .
Consumption reference factor
On import of a new assignment, the system uses as default the value 1.
 Note
If you import substitution assignments from a linked SAP Retail system, these contain no substitution merge pro le and no
consumption reference factor.
Integration
You can display data that the system could not post (due to an error) in the interface workbench and you can process it
there.
You can display imported substitution assignments and add data. For more information, see Displaying and Changing
Substitution Assignments.
SAP F&R does not plan location products for which a lock on product substitution is set in the master data. This applies
to the automatic (FRP run) and manual replenishment planning (using the Planning Workbench or Product Workbench).
Using a Business Add-In (BAdI) ( /FRE/IF_CON_BADI_029), you can change the imported data customer-speci cally.
Interfaces Enhancements Using Business Add-Ins BAdI: Enrichment of Substitution Assignments .
SAP F&R evaluates the information that a substitution assignment has been deleted in the master data retaining
system.
Prerequisites
You carry out interface processing (report /FRE/BIF_INB01) and set the indicator for substitution assignments under
selections for product/target location.
Features
In inbound processing, the system carries out the following checks:
The master data on the products, locations, and location products contained in the substitution assignment exists in
SAP F&R.
If the eld location is lled, the system checks if the location product (that results from the location and the original or
substitute product) exists in the master data.
At any time, no more than one replacement product and no more than one follow-up product per storage level (location
or global level) is assigned to an original product.
 Note
7/31/2021
In the case of a follow-up product assignment, the system performs the other checks as described below.
Import of a follow-up product assignment with location
If now switchover has yet occurred for the imported substitution assignment (which means no switchover or switch back
information exists) and SAP F&R plans both the original and the follow-up product, the system displays the following lock
behavior:
It sets a lock indicator in the master data for the location product that contains the follow-up product.
If a lock indicator is set in the master data of the location product for the original product, the system removes
this.
Import of a follow-up product assignment without location (global assignment)
The system determines for the original product of the substitution assignment all location product combinations that
contain the original product (from the imported global substitution assignment) as a product.
For each location product found, the system checks if there is a location-speci c substitution assignment with the same
original product. If no location-speci c substitution assignment exists in SAP F&R, the system uses the global
assignment for this location and carries out the lock behavior described above.
For more information, see System Behavior on Import of Substitution Assignments (example).
On the import of a deletion record for a substitution assignment, the system checks if switchover or switch back
information exists for this:
If no switchover or switch back information exists, the system deletes the substitution assignment directly.
If switchover or switch back information exists, the system sets a deletion ag for the substitution assignment.
SAP F&R can delete a (location-speci c) substitution assignment as soon as the deletion program for switchover
information has deleted the related switchover information. For more information, see Deleting Obsolete
Switchover Information.
Activities
 Note
The system can only post the substitution assignment if the check criteria have been ful lled; otherwise it ags the
assignment as erroneous and issues an exception.
System Behavior on Import of Substitution Assignments
Posting of substitution assignments and lock logic with location products

The example in the following table illustrates the system behavior on import of substitution assignments with and without
speci cation of the location product:
Location Products in the System Prior to the Import
7/31/2021
[L = Location; O = Original product; F = Follow-up product]
L1 | O1
L2 | O1
L3 | O1
L1 | F1
L2 | F2
On import of the location-speci c substitution assignment L1: U1 -› F1 with switchover to the follow-up product F1 and on import
of the global substitution assignment L*: U1 -› F2 with switchover to the follow-up product F2, the system behaves as follows
with regard to the location product:
Import of Substitution Assignments in Speci ed System Behavior

Sequence
L1: O1 -> F1
Following successful checks, the system posts the assignment
it unlocks the location product L1 | O1
it sets the lock for the location product L1 | F1
L*:O1 -> F2
Following successful checks, the system posts the global
assignment.
The system determines all location products L*| O1, that is, L1 | O1,
L2 | O1 and L3 | O1
The system matches the location products with the imported

assignments and runs the lock behavior:
L1 | O1: because of the assignment already imported L1: O1 ->

F1 the import of assignment L*: O1 -> F2 has no effect
L2 | O1: the system locks the location product L2 | F2 and

unlocks L2 | O1
L3 | O1: as there is no location product L3 | F2, the import of

assignment L*: O1 -> F2 has no effect
Compatibility of imported substitution assignments

The following graphic illustrates the compatibility of imported substitution assignments using the contained substitution
controls and assortments:
7/31/2021
Inbound Transaction Data
Use
Several inbound interfaces are available to import transaction data into SAP F&R. SAP F&R needs the transaction data for
automatic replenishment. SAP F&R updates the transaction data in the order in which the transfer takes place.
 Note
SAP F&R does not compare the data with the data that already exists. In contrast to master data, the system always
expects a full transfer for transaction data - with the exception of stock and consumption data (sales).
Integration
For more information on the existing interfaces, see the Overview of the Interfaces in SAP F&R.
Prerequisites
In the sending system, you have de ned which transaction data you wish to export to SAP F&R.
To import transaction data, you must de ne in Customizing how the inbound interface is to work. You must also set the
transaction types. You can use an RFC connection or an XI connection.
7/31/2021
Features
SAP F&R provides the following inbound interfaces for transaction data:
Time series data
You use this interface to process the following data:
Time series, for example, POS data
Stocks
Goods movements
Demand in uencing factors
Order proposals
Switchover and switch back information
Contract information
Inbound Interface for Time Series Data
Use
You use this interface to import consumption data, stock information, and goods movements into SAP F&R. The system saves
this data at location product level.
Integration
SAP F&R uses the consumption time series for the forecast calculation and the result of the stock projection for the
requirements calculation.
You assign the time-series-speci c key gure parameters in a time series pro le to the locations.
You can use the Business Add-In ( /FRE/IF_CON_BADI_003) to enrich and change the imported time series data. For
more information, see the Implementation Guide (IMG) for Forecasting and Replenishment under
Interfaces Enhancements Using Business Add-Ins BAdI: Customizing Time Series .
Prerequisites
For inbound processing of the time series data, the locations and products that appear in the time series must exist in
the master data of SAP F&R.
In order to store data in SAP F&R as time series, you have assigned the appropriate key gure parameters of the time
series to the product movement types ( Quali er) in SAP F&R Customizing. For more information, see the
Implementation Guide (IMG) of Forecasting and Replenishment under Interfaces Maintain Time Series Interface .
You de ne which movement type SAP F&R is to update in the time series and whether the movement type is stock-
relevant. If the movement type is stock-relevant, SAP F&R corrects the stock with the time series value of the relevant
movement type. If you import stock-relevant data, you must post the stock before the consumption. The sending system
must ensure that the required product movement types are available in SAP F&R.
Features
7/31/2021
The interface transfers data in different levels of granularity (day, week) and assigns a time stamp to it (for example, on
which day consumption occurred).
The interface can transfer absolute values or value changes.
Absolute values (summed data) overwrite existing time series values.
In the case of value changes, SAP F&R adds (or subtracts) the transferred time series value to the (from the)
existing time series value.
If the transferred consumption data and goods movement data is stock-relevant, SAP F&R cleans up this data on
updating the stock.
Activities
More Information
Transaction data: Time Series Management
Inbound Interface for Demand In uencing Factors
Use
You use this interface to import demand in uencing factors into SAP F&R.
Integration
The system uses DIF occurrences in order to ag unusual or greatly modi ed consumption patterns that are due to
temporary causes (for example, sales promotions or holidays such as Christmas).
Using the Business Add-In ( /FRE/IF_CON_BADI_015), you can enrich and change the imported demand in uencing
factors. For more information, see the Implementation Guide (IMG) for Forecasting and Replenishment under
Interfaces Enhancements Using Business Add-Ins BAdI: Demand In uencing Factors Enrichment .
Prerequisites
In the sending system, you must de ne which factors SAP F&R is to consider as demand in uencing factors.
Demand in uencing factors must exist in SAP F&R for you to be able to assign them to the locations, products, location
products, and location groups.
Features
You can import the following demand in uencing factor information:
Basic data
Descriptions
(language-dependent texts)
7/31/2021
Assignment
This de nes which demand in uencing factor is relevant for which location product, product, or location group.
Activities
Inbound Interface for Contract Information
Use
With this interface, you can import the following data for a quantity or value contract to SAP F&R:
Contract number in the purchasing system (such as a connected SAP Retail system)
Product (this must be known in SAP F&R)
Product-related target quantity (including unit of measure) or target value
Released quantity (including unit of measure) or released value
Start and end of the contract validity period
Vendor (must be known in SAP F&R)
Target location (this can also be empty)
Overbooking indicator
Speci es if exceeding the contract limit (target value or target quantity) is allowed.
Variant indicator
Speci es if the product in the SAP Retail system corresponds to the variant of a generic article and if the contract has
been created in the SAP Retail system at the level of the generic article. On transfer to SAP F&R, the SAP Retail system
breaks down a contract for generic articles into contracts for replenishment-planning-relevant variants of the generic
articles. SAP F&R holds contract information for these variants at product level.
Purchasing organization and the relevance indicator for the purchasing organization
The latter speci es if the system has to take the purchasing organization into account in contract determination. If this
indicator is set, the system does not allow assignment of a contract where the purchasing organization differs from that
in the order item.
For more information on the technical procedure (use of buffer tables for the imported data) when transferring the contract
data, see Interface Processing.
Integration
 Note
You can supply this interface from an SAP Retail system or from a different purchasing system.
7/31/2021
Contract data transmitted by a purchasing system that does not meet certain minimum requirements (for example,
because the vendor is missing or the product is not known in SAP F&R) is rejected as invalid by SAP F&R. You can display
data that the system could not post in the interface workbench.
After deleting contract assignments for order items in the SAP Retail system, SAP F&R uses an import of changed order
information (delta data transfer) to automatically update the contract number assignment in the order proposal items.
Using a Business Add-In (BAdI) ( /FRE/IF_CON_BADI_027), you can enrich or change the imported contract data
speci cally for the customer. For more information, see the Implementation Guide (IMG) for Forecasting and
Replenishment under Interfaces Enhancements Using Business Add-Ins BAdI: Inbound Contracts .
Prerequisites
Before call-up of the F&R Interface Processing, you have imported contract data from a purchasing system.
You carry out interface processing (report /FRE/BIF_INB01) and set the indicator for contracts under selections for
source location / target location.
Features
Following the import of contract information, the system can determine contracts when creating a new order proposal item or
changing an existing one.
For more information, see Using Contract Information in Order Proposal Items.
Activities
Inbound Interface for Order Proposals
Use
Using this interface, you import new or changed orders from a purchasing system. From the incoming orders, SAP F&R
generates order proposals in inbound processing or it updates existing order proposals.
Integration
If the order that is imported from the external system is based on an order proposal already transferred by SAP F&R,
then SAP F&R only transfers the changed data.
Using the Business Add-In ( /FRE/IF_CON_BADI_013), you can enrich and change the imported order proposal data.
Interfaces Enhancements Using Business Add-Ins BAdI: Order Proposal Enrichment (Inbound) .
You can access the order proposals using the Replenishment Workbench and Product Workbench.
Prerequisites
In order to generate order proposals, you need to know the required master data in SAP F&R including:
7/31/2021
Location
Product
Location product
Supply network
Procurement cycle (pro le)
In the sending system you have de ned which order proposals are relevant for planning in SAP F&R. The sending system
must transfer, in addition to the order data, also the information on goods receipts and partial deliveries to SAP F&R.
Features
You must import newly created, changed, or cancelled orders or order items from a purchasing system (such as an SAP Retail
system). This includes orders from distribution centers and stores. The purchasing system reports completely or partly ful lled
orders using this interface. SAP F&R requires the current status of goods receipts for the automatic replenishment process.
Activities
Inbound Interface for Switchover and Switch Back Information
Use
With this interface, you can import data to SAP F&R including data on a switchover from the original product to the substitute
product and also on a switch back from the replacement product to the original product:
Original product
Substitute product
Receiving location
Location type of receiving location
Issuing location
Location type of issuing location
Substitution control with the following types:
Follow-up product, time-controlled
Follow-up product, event-controlled
Replacement product, event-controlled
Switchover date
Evaluation date
Switchover types:
Switchover
7/31/2021
Switch back
Switchover reasons:
Event-controlled - Availability check
Event-controlled - BAdI
Time-controlled
Reference document number for original product
Number and item of the procurement document for the original product (in the purchasing system, such as an SAP
Retail system), for which the product substitution was made.
Reference document number for substitute product
Number and item of procurement document that the system created during product substitution.
Order proposal for original product
Number and item of the order proposal for the original product (in the purchasing system, such as an SAP Retail
system), for which the product substitution was made.
Order proposal for substitute product
Number and item of the order proposal for the substitute product that the system created during product substitution.
Integration
You can display data that the system could not post (due to an error) in the interface workbench and you can process it
there.
When new information is created on switchovers or switch backs in SAP F&R, the SAP-F&R System creates the following
exceptions:
Exception for the switchover (for follow-up and replacement product)
Exception for the switch back (for replacement product)
You can evaluate the generated exceptions in the standard system using the Exception Reporting in your BI or F&R
System. This way you can ascertain, for example, how often the system has replaced a product within a certain time
period.
When importing switchover information with the substitution type follow-up relationship, the system proceeds as follows:
It executes a lock logic in the location product.
If this is set in the substitution merge pro le, then the system sets a reference for the follow-up product: After a
switchover to the follow-up product, the system enters the original product as a reference in the follow-up
product master data at location product level. If a reference entry already exists here, the system overwrites this.
For the follow-up product, the system sets the valid-to date of the reference to the day before the start of the
merge period.
Entering the reference has as a consequence that SAP F&R consumption data of the original product (with sales
or goods issue date before the switchover date) is used as historical consumption data for the follow-up product.
You can display, enrich, and delete switchover and switch back information, as well as create new entries. For more
information, see
Displaying Switchover Information
Creation and Enrichment of Switchover Information
7/31/2021
Deleting Obsolete Switchover Information
SAP F&R does not plan location products for which a lock on product substitution is set in the master data. This applies
to automatic (FRP run) and manual replenishment planning (using the Replenishment Workbench and Product
Workbench).
If the master data with the substitution assignment contains a substitution merge pro le, the system transfers this to
the switchover and switch back information.
Using the Business Add-In (BAdI) ( /FRE/IF_CON_BADI_028), you can enrich and change the imported switchover
information speci cally for the customer. For more information, see the Implementation Guide (IMG) for Forecasting and
Replenishment under Interfaces Enhancements Using Business Add-Ins BAdI: Enrichment of Switchover Information .
Prerequisites
You carry out interface processing (report /FRE/BIF_INB01) and set the indicator for switchover information under
selections for product/target location.
Features
In inbound processing, the system carries out the following checks:
The master data on the products, locations, and location products contained in the switchover and switch back
information exists in SAP F&R.
For the switchover information, there is a substitution assignment in SAP F&R with the following properties:
matching original and substitute product
matching substitution control
the evaluation date of the switchover information is within the switchover period of the substitution assignment
Matching of the target location from the switchover information with the location from the substitution
assignment (or use of a global assignment).
The system processes substitution assignments with location with greater priority than assignments without
location.
The system checks and ensures that a location product in SAP F&R appears in no more than one switchover information
at any particular time.
The system guarantees the uniqueness of the switchover information by way of one of the following alternatives:
It does not post incoming switchover information because other switchover information already exists.
It posts incoming switchover information and overwrites existing switchover information.
It posts incoming switchover information and deletes existing switchover information.
For more information, see Rules for Processing Incoming Switchover Information.
 Note
The system can only post the switchover information if the check criteria have been ful lled; otherwise it ags the switchover
information as erroneous and issues an exception.
Activities
7/31/2021
Rules for Processing Inbound Switchover Information

To ensure that a location product appears in no more than one switchover information at any one time, SAP F&R applies certain
rules to the processing of switchover information:
Basic Rules
A switchover to the follow-up product has priority over a switchover to a replacement product. This can lead to the
following when the time periods overlap:
The system does not post an imported switchover to a replacement product because the location product already
appears in a switchover to the follow-up product.
On import of a switchover to the follow-up product, the system deletes a switchover to the replacement product
that has already been posted or changes it (by shortening the merge period).
When posting a switchover to a follow-up product, the posting time is relevant. The switchover to a follow-up product
that is posted rst has priority over a switchover that is imported later. As soon as SAP F&R has posted a switchover to a
follow-up product, it can no longer transfer switchovers for the same original product.
When posting a switchover to a replacement product, the switchover time is relevant. The switchover to a replacement
product with a later switchover time has priority over a switchover to a replacement product with an earlier switchover
time.
If the time periods overlap, the system shortens a switchover information that lies further in the past and posts in
addition the newer switchover to the replacement product.
Additional rules
Following a switchover to a follow-up product, the original product cannot appear as the original product of a substitute
product in switchover information; an exception is the case where the system subsequently posts the switchover to the
follow-up product (because SAP F&R - for example, due to technical problems with the data transfer - could only import
the data with a delay). Here, some items of existing switchovers to the replacement product may be deleted (however,
not with the follow-up product).
Inserting a new switchover to the follow-up product before an existing switchover may not change the lock situation of
the location products of the existing switchover.
A location product can only appear in one switchover at any time (as an original or substitution product).
Actions on switchover to a replacement product

On switching to a replacement product, the system has the following possibilities to ensure that the rules are adhered to:
It shortens the merge period and forces a switch back if one does not yet exist.
On import of a switchover to the follow-up product, the system deletes items from an existing switchover to the
replacement product or also the complete switchover.
Outbound Interface for Order Proposals
7/31/2021
Use
You use this interface to export order proposals from SAP F&R. These order proposals are a result of manual or automatic
replenishment planning.
Integration
They generate orders from the exported order proposals in the follow-on system (such as an SAP Retail system).
Following the export, SAP F&R changes the status of the order proposal to transferred. Once the order proposals have
this status, you can no longer change them in SAP F&R.
Using the Business Add-In ( /FRE/IF_CON_BADI_014), you can enrich and change the exported order proposal data.
For more information, see the Implementation Guide (IMG) of Forecasting and Replenishment under Interfaces De ne
Message Types .
If, in place of the SAP Retail system, you wish to connect a different purchasing system, you can use a Business Add-In (
/FRE/IF_CON_BADI_016) for the system call-up. For more information, see the Implementation Guide (IMG) for
Forecasting and Replenishment under Interfaces Enhancements Using Business Add-Ins BAdI: Order Outbound
Activation/RFC .
Prerequisites
In SAP F&R, in Customizing of the message type, you have set the RFC destination of the receiving system for message
type ORDER. For more information, see the Implementation Guide (IMG) of Forecasting and Replenishment under
Interfaces De ne Message Types .
You can only export released order proposals from SAP F&R.
Features
You can transfer order proposals to the SAP Retail system or to an external purchasing system.
Activities
You call the relevant function module in SAP F&R to start the transfer. For more information, see the Overview of the Interfaces
in SAP F&R.
Interface Workbench
Use
This application enables you to display incorrect data records from interface processing, and to change the status.
If errors occur when posting interface-processing data, SAP F&R ags the data records as exceptions and saves them to the
database. The displayed exceptions provide you with an overview of the error situation, and enable you to identify possible
causes of errors.
Integration
All incorrect records are organized according to object in the Interface Workbench.
There are two kinds of errors:
7/31/2021
Semantic errors
In this case, SAP F&R tries to post an object that does not exist yet. This error can be caused by objects being
transferred to SAP F&R at different times. To correct the error, you need to re-import the data simultaneously.
Technical errors
These include, for example, incorrect data formats in the interface record. To remove the error, you must correct the
relevant elds in the sending system, and re-import the data.
Prerequisites
In interface processing, you have entered parameters that SAP F&R uses for posting of the interface data. These include:
Parallel processing
The server group
The number of parallel processing jobs
Activities
In the Interface Workbench, the following procedure is possible:
SAP F&R creates the worklist automatically. All incorrect interface records are selected and displayed. By selecting a
record, you can see the details and you can modify the record in processing mode.
Once you have manually corrected a record, set the status to N ( Not Processed). If SAP F&R nds this information in the
PSTATUS eld of the interface record, it posts the record in the next processing run.
To export the data, you schedule a background job. This takes the interface processing parameters into account.
 Note
Alternatively, and independently of the background jobs, you can also transfer the order proposals directly from the
Replenishment Workbench or use the mass release of order proposals. For more information, see
Direct Transfer of Order Proposals
Manual Release of Order Proposals
To start the Interface Workbench, go to the SAP Easy Access screen and choose Forecasting and Replenishment
Interfaces Interface Workbench .
More Information
Transfer of Consumption Data from SAP BI
Use
You use this function (as a replenishment planner or an administrator) in order to import consumption data from SAP BI to SAP
F&R.
7/31/2021
If the consumption data in SAP F&R is incomplete, you can load consumption data from SAP BI for speci c location products
(that are already available in SAP F&R).
Integration
For new location products - which usually have not yet been planned in SAP F&R - you can perform an initial supply by
transferring consumption data from SAP BI.
Therefore, you do not have to save consumption data in SAP Retail at all, or at most for the time required for running a
delta supply.
SAP F&R takes the consumption data from the SAP BI InfoProviders and stores it in times series.
 Note
You can delete the consumption data in SAP Retail using the Delete Consumption Data in SAP ECC function.
To save resources, you can save the consumption data in the SAP Retail system until the delta load is performed or in
general in SAP BI.
Prerequisites
The consumption data in SAP BI ful lls the following conditions:
The consumption data is stored on one of the following levels:
Product (article)
Location (store, distribution center)
Granularity (day, week)
The consumption data is stored in SAP BI with reference to the following product parameters:
Granularity (day or week)
Base unit of measure
You can only use the following objects as data sources (InfoProviders) in SAP BI:
InfoCubes
Standard DataStore objects
MultiProviders (that are made up of a combination of InfoCubes or standard DataStore objects)
For the initial data supply from SAP BI, you have activated the initial data supply in Customizing of the alternative data sources
for consumption data and processed the related pro le. For more information, see the Implementation Guide (IMG) of
Forecasting and Replenishment under Interfaces Alternative Provision of Consumption Data .
Activate Alternative Transfer of Consumption Data from BI
Process Pro le for Alternative Transfer of Consumption Data from BI
Activities
Initial Supply of Consumption Data From SAP BI
7/31/2021
You de ne the information for the read access in SAP BI in the initial data supply pro le in SAP F&R. Here you de ne the system
and the data source in SAP BI (the InfoProvider) from which SAP F&R is to transfer the consumption data. You can create
default pro les for stores and distribution centers by choosing the relevant indicator. You activate the initial supply of
consumption data from SAP BI. If you select data transfer according to the worklist, SAP F&R transfers the consumption data
from SAP BI for all new location products (from the worklist).
 Note
There is no check to see whether there is already any consumption data for a location product in SAP F&R or whether SAP
F&R has transferred consumption data by way of the time series interface.
To transfer consumption data from SAP BI, you start the program for initial transfer of sales data from SAP BI manually, or you
schedule it periodically.
In order to import consumption data from SAP BI, you choose from the SAP Easy Access screen Forecasting and
Replenishment Interfaces Initial Transfer of Consumption Data From BI .
Connection to the SAP Retail System
Use
You can exchange the following data between SAP F&R and the standard system (SAP Retail system):
Master data (transferred from SAP Retail to SAP F&R)
Transaction data (transferred from SAP Retail to SAP F&R)
Order proposals (transferred from SAP F&R to SAP Retail)
Purchase orders (transferred from SAP Retail to SAP F&R)
Prerequisites
If you want to connect the standard system with SAP F&R you have to de ne SAP ECC as an SAP Retail system.
The connection is available for the following releases:
SAP ECC 600
SAP ECC 500 with Plug-In (SP10 PI 2004_1_500)
SAP R/3 4.70 (Enterprise) with Plug-In (SP10 PI 2004_1_470)
SAP R/3 4.6C with Plug-In (SP10 PI 2004_1_46C)
For more information, see the SAP Library under SAP Retail Distributed Data Processing SAP F&R Integration .
Activities
You always start the transfer to SAP F&R from the standard system. There are reports for collecting, preparing, and sending
data from the standard system. You can schedule these reports for background processing once or several times a day. The
reports call function modules in SAP F&R that start the import of data in SAP F&R.
You always start the transfer to the standard system from SAP F&R. The standard system buffers the imported order proposals
internally and then converts them successively into purchase orders.
7/31/2021
The standard interface has the following limitations:
You must transfer generic articles and structured articles (prepack, set, display) from an SAP Retail system into SAP
F&R as follows: SAP F&R adopts the variants of generic articles as single articles. When structured articles are involved,
you can decide whether you want the sending system to send the components or the header articles (analogous to
generic articles). The order data interface in SAP F&R cannot re-merge these variants or components, however, but you
can still transfer them to SAP F&R for replenishment planning there.
For sources of supply, you can transfer contracts, purchasing info records, and supplying site relationships from the site
master data of an SAP Retail system into SAP F&R. Source lists and scheduling agreements are not considered in SAP
F&R.
More Information
Transaction Data
Use
SAP F&R uses the following transaction data among others:
Order proposals
Time series
These include: POS data (sales histories) of stores, goods issues of distribution centers, and forecast data
 Note
The system does not save orders in time series. However, it can take this data into account when calculating the time
series.
Stocks
You must initiate the import of the transaction data to SAP F&R by way of an export from the connected system (for example,
SAP Retail).
Integration
SAP F&R uses transaction data together with data from the following SAP SCM functions:
Time Series Data Management TSDM (TSDM)
Compressed Data Management (CDM)
Order Data Management (ODM)
In SAP F&R, you can display, enrich, and delete the transaction data that you have imported for the product substitution
via the inbound interface for switchover and switch back information. For more information, see Switchover Information.
Features
7/31/2021
You have the following options for processing in SAP F&R:
Import of the time series via interfaces
Display the time series (click link to retrieve) in the Replenishment Workbench, the Product Workbench, and Cause
Determination
Aggregation of certain time series for the forecast in distribution centers
Aggregate the time series from daily periodicity to weekly periodicity
Archive time series (this deletes obsolete time series)
More Information
For more information on the time series interface, see time series.
Forecasting and Replenishment Processor (FRP)
Use
The F&R Processor controls automatic replenishment. Automatic replenishment is made up of forecast calculation and
requirements calculation, along with requirement quantity optimization.
This process gives you a greater degree of automation. In automatic replenishment, SAP F&R determines the future
requirement for a location product, while taking various factors into account.
Prerequisites
Automatic replenishment requires the following data to calculate future requirements:
Master data
Time series
Current stock
Open purchase orders
SAP F&R must import this data.
Process
1. For the forecast, SAP F&R uses time series (for example, sales history of the stores, goods issues or alternative
historical data in the distribution center). SAP F&R uses statistical methods to determine potential future consumption.
You assign the methods depending on the selling class.
2. Using the forecast, the current stock, and the open purchase orders, the requirements calculation determines the
requirement for a location product for the future demand periods.
3. The requirement quantities for all planned future demand periods form the basis for subsequent requirement quantity
optimization. During the calculation of forecasts and requirements, SAP F&R creates exceptions so that you can
evaluate automatic replenishment. Examples for exceptions are unusually high sales or unusually severe lost sales.
More Information
7/31/2021
Forecast
Requirement Calculation
Requirement Quantity Optimization
Administration
Background Processing of the FRP Run
Forecast
Use
You can use the forecast in SAP F&R to determine future consumption for a location product. This means you can ensure
product availability while at the same time keeping stock levels low. The forecast is a key process in SAP F&R.
Process
In the forecast, SAP F&R determines the future demand for a location product using historical data. Based on the assigned
forecast technique, the forecast determines future consumptions using the sales history. In uencing factors here are, for
example, product lifecycles of trend and seasonal products. The selling classes that are determined in the forecast enable you
to use selling-class-speci c parameters. Products are allocated to selling classes according to the classi cation mean value.
Forecast
The forecast is based on the demand history that you import into SAP F&R using the interface. You can have the data from the
sales history undergo data cleansing. You can adjust high values (consumption peaks) and low values (consumption troughs)
and analyze zero values. If they are attributed to stockouts, SAP F&R replaces the null values by mean values (depending on
your settings in the forecast pro le).
You can also take account of demand in uencing factors (DIFs) in the forecast.
By examining historical occurrences of DIFs and their effect on historical demand, the system derives the potential effects on
consumer behavior in the future. It is important that the DIFs contribute signi cantly to the quality of the forecast and that they
can be de ned for past and for future events. You can also import DIFs from an external system (for example, a promotion
planning system) or you can create and process them manually.
You can manually enter planning data and thus override the regular forecast values in the requirements calculation.
The forecast is performed according to the settings in the frequency pro le.
Result
The result of the forecast is:
The mean forecast contains the future consumption in which all expected uplifts and downlifts are taken into
consideration.
The maximum forecast contains the mean forecast and, in addition, the safety stock. By de ning a certain service level,
SAP F&R calculates a dynamic safety stock during the forecast, which depends on the expected forecast errors and the
replenishment lead time.
You can save the forecast including a safety amount as a time series. The expected forecast error can also be saved as a
time series.
7/31/2021
More Information
Pro les Relevant for Forecast
Forecast Frequency
Requirement Calculation Pro le
Time Series Management
Demand in uencing factors
Use
In the forecast pro les, you de ne parameters that SAP F&R uses in forecasts. Forecast-relevant pro les in uence the
calculation of the forecast in the F&R Processor.
Activities
Here you can make the following parameter settings for the forecast calculation:
1. The base pro le contains basic settings for the location. You make settings here for the boundaries between the selling
classes and for the forecast horizon. If you have not de ned a forecast horizon in the master data for the location
product, the system uses the forecast horizon de ned in the base pro le.
Assign the base pro le in the master data for the location.
On the SAP Easy Access screen, choose Forecasting and Replenishment Master Data Location Maintain Locations .
For more information about the base pro le, see the Implementation Guide (IMG) for Forecasting and Replenishment
under Forecasting and Replenishment Processor Maintain Base Pro les .
2. The forecast pro le affects location product settings for the forecast.
These include settings for data cleansing (formatting the time series data), selling-class-dependent assignment of
forecast methods, and settings for seasonal products.
You can enter the following settings (among others) in the Basic Settings area:
How many historic FRP periods to use
Whether the FRP should include consumption from the current week in forecast calculation
Whether SAP F&R should save the forecast result for the location product including the safety amount in a
time series
You can enter the following settings (among others) in the Preparation area:
Correct Lost Consumption
If the system calculates a day with potential lost consumption (day's closing stock = 0) within a period, it
modi es the weekly consumption time series by calculating a local mean, which takes the number of days
with and without stock into account within the affected single period.
Outlier Correction: You can de ne whether you want FRP to correct outliers in consumption troughs
and/or consumption peaks. You can specify a general and a selling class-speci c factor for consumption
troughs, for example, as well as a speci c number of weeks for outlier correction. You can also specify a
7/31/2021
percentage to exclude the weekly consumption values with the greatest deviations from outlier
calculation.
Among other settings, the Forecast Methods area lets you con gure SAP F&R to determine the forecast method
for the selling class (such as fast moving items) automatically.
In the default settings, SAP F&R uses the results of parameter optimization for forecast method
Regression. You can set a ag in the forecast pro le to override this default setting. Among other things,
you can also con gure the adaptivity, for example, and instruct the system to give weight recent
consumption periods more heavily than older periods. You can enter the adaptivity manually (in the
forecast pro le) or have the system calculate it automatically through parameter optimization. If you only
want to consider the last two consumption periods in forecast calculation, you can con gure the local
adaptivity parameter.
If you use the smoothing forecast method, you can con gure the smoothing factor for historical weekly
consumption time series, for example, as well as for seasonal cycles. In addition, you can con gure how
strongly SAP F&R should take the calculated seasonal effect into account.
You can con gure settings in the Variance Calculation area to determine how SAP F&R calculates the standard
deviation (of forecast errors).
You assign the forecast pro le in the master data for the location products. To maintain location products, go to the SAP
Easy Access screen and choose Forecasting and Replenishment Master Data Product Maintain Location Products .
For more information about the forecast pro le, see the Implementation Guide (IMG) for Forecasting and
Replenishment under Forecasting and Replenishment Processor Maintain Forecasting Pro les .
3. The exception base pro le relates to a location. Here you control the output of exceptions for consumption data and
stock data in the Replenishment Workbench and the Product Workbench. These include:
Zero consumption exception
Low consumption exception
Overstock exception
You assign the exception base pro le in the master data for the location. For more information about the exception base
pro le, see the Implementation Guide (IMG) for Forecasting and Replenishment under Forecasting and Replenishment
Processor Maintain Exception Base Pro les .
4. The exception pro le relates to a location product. It contains settings for the output of exceptions in the Replenishment
Workbench and the Product Workbench after running the F&R Processor. These include:
New DIFs
Difference between the actual sales gures and the forecast sales gures for the current week
General outliers for historical sales
Exceptions for the start and end of a listing period
You assign the exception pro le in the master data for the location product. For more information about the exception
pro le, see the Implementation Guide (IMG) for Forecasting and Replenishment under Forecasting and Replenishment
Processor Maintain Exception Pro les .
5. The service level pro le contains settings for different service levels.
You assign the service level pro le in the master data for location products. For more information, see Service Level
Pro le.
6. In the process control pro le, you determine whether you want to de ne the forecast frequency for locations or for
location products. In addition, you determine for parameter optimization whether you wish to de ne the frequency
7/31/2021
pro le for locations or for location products.
You assign the process control pro le to the location data in Administration. In start administration, go to the SAP Easy
Access screen and choose Forecasting and Replenishment Forecasting and Replenishment Processor Administration .
For more information about the process control pro le, see the Implementation Guide (IMG) for Forecasting and
Replenishment under Forecasting and Replenishment Processor Maintain Process Control Pro les .
7. The forecast frequency pro le contains settings for the frequency of the forecast calculation.
You assign the forecast frequency pro le in the process control pro le or in the master data for location products. For
more information, see Forecast Frequency.
You can de ne the forecast frequency dependent on the following objects:
ABC classi cation of the location product
Selling class of the location product
Individual location products (de nition of assignment level)
Whole location
For more information about the forecast frequency pro le, see the Implementation Guide (IMG) for Forecasting and
Replenishment under Forecasting and Replenishment Processor Maintain Forecast Frequency Pro les .
Parameter Optimization
Use
You use this function to automatically optimize the parameters for the forecasting techniques regression and or smoothing. The
forecast calculation uses the optimized parameters. Parameter optimization can take place as follows:
For the automatic selection between regression and smoothing
For all parameters of the regression forecasting technique
For the seasonal consideration for forecast the smoothing forecasting technique
You de ne optimization you want to use in Customizing.
 Recommendation
This function takes a lot of time. Therefore, you should only schedule parameter optimization in a critical time window (creation
of order proposals) if sufficient time is available.
Integration
You can activate and deactivate parameter optimization in the process control pro le for FRP. If the frequency of parameter
optimization is dependent on the forecast calculation days, you can con gure a corresponding frequency type that is either
location-speci c or location-product speci c. For more information, see Forecast-Relevant Pro les.
Prerequisites
The FRP Dispatcher must be activated in order to enable use of the automatic parameter optimization within the FRP
run.
7/31/2021
You can de ne how often you want the system to execute parameter optimization for each frequency type (daily, weekly,
or dependent on forecast calculation) in the frequency pro le for parameter optimization. For more information, see the
Implementation Guide (IMG) for Forecasting and Replenishment under Forecasting and Replenishment
Processor Maintain Process Control Pro les .
Features
You can perform parameter optimization in the following ways:
With the FRP Dispatcher
You can use the FRP Dispatcher to perform parameter optimization within the critical and non-critical time period. To do
so, you must add the SAFRUN_CALIB task to the Dispatcher pro le you use. You must add this task in the
MD_AND_TECH_SYNCH sequence (non-critical time period) or in the AUTO_REPL_AND_OPRM sequence (critical time
period). Alternatively, you can create a separate sequence for the above task and add it to the appropriate place in the
Dispatcher pro le.
With report /FRE/UI_FRP_SAFRUN_CALIBRATION
If you want to perform parameter optimization outside the Dispatcher-controlled FRP run (neither in the critical nor in
the non-critical time period), schedule this report as a background job whenever appropriate. For more information, see
Background Processing of the FRP Run.
Activities
In assign the process control pro le in administration, go to the SAP Easy Access screen and choose Forecasting and
Replenishment Forecasting and Replenishment Processor Administration .
More Information
FRP Dispatcher
Forecast Frequency
Forecast Frequency
Use
The forecast frequency determines how often you run the forecast. You use this function as a replenishment planner to de ne
the forecast frequency.
Integration
Assign the forecast frequency pro le to the relevant location products in the process control pro le for the location or in
mass processing for location products.
You maintain the process control pro le in Customizing. For more information, see the Implementation Guide
(IMG) for Forecasting and Replenishment under Forecasting and Replenishment Processor Maintain Process
Control Pro les .
To start mass maintenance for location products, go to the SAP Easy Access screen and choose Forecasting and
You assign the process control pro le to the location in Administration. To do so, go to the SAP Easy Access screen and
choose Forecasting and Replenishment Forecasting and Replenishment Processor Administration .
7/31/2021
Prerequisites
You have con gured the settings for the forecast frequency pro le in Customizing. You either use the standard pro le (
SAPDEFAULT) or you have de ned custom values in a default pro le. For more information, see the Implementation Guide
(IMG) for Forecasting and Replenishment under Forecasting and Replenishment Processor Maintain Forecast Frequency
Pro les .
The following frequency types are available:
Daily
Weekly
Depending on the requirement calculation
Requirement calculation days for the location
The system runs the forecast on the days on which the requirement calculation for the location is performed.
You de ne the days on which the requirement calculation is performed for the location in the process control
pro le.
Requirement calculation days for the location product
The system runs the forecast on the order day for the location product. You de ne the order day for a location
product in scheduling.
First requirement calculation day for the location product in a week
The system runs the forecast on the rst order day of a week for the location product. If there is more than one
order day for the location product in a week, a forecast is performed on the rst order day of the week only. There
is no forecast on the other order days in the week.
Features
You can carry out the forecast for a location or a location product at different intervals.
The F&R processor derives the frequency of forecast calculation from the forecast frequency pro le.
Activities
In the process control pro le, you select one of the following forecast frequency types and assign it to a forecast frequency:
Dependent on the ABC classi cation of the location product
Dependent on the selling class of the location product
Statically for location products
Statically for locations
More Information
FRP Dispatcher
Start Pro le
7/31/2021
Use
You use the requirement calculation in SAP F&R to determine the future requirement expected for a location product. This
means you can ensure product availability while at the same time keeping stock levels low.
Requirement calculation takes manually entered and activated planning data into account, therefore replacing the calculated
forecast values. For more information, see planning data.
Prerequisites
You have already con gured the settings for the F&R Processor in Administration.
The future consumption values calculated during the forecast form the basis of the requirement calculation.
Process
1. In Scheduling, SAP F&R determines the possible order dates for each location product. The future demand periods are
calculated using the supply network, the procurement cycles, the replenishment lead time, and the different calendars.
In this process step, SAP F&R determines the order dates, delivery dates, and availability dates within the de ned
optimization horizon (how many demand periods in the future will be considered).
2. SAP F&R distributes the future consumption values from the forecast amongst the different demand periods, thus
determining the future requirement. You can take several demand periods in the future into consideration. SAP F&R
uses this option as the basis for requirement quantity optimization (RQO), which takes place at a later stage.
3. Based on the future requirement, SAP F&R can calculate the dynamic minimum stock. If the current stock falls below the
dynamic minimum stock (reorder point), SAP F&R includes the location product automatically in the requirement
calculation.
4. The calculated net requirement for a demand period is made up of the following:
Dynamic target stock
Current actual stock
Open goods movements (receipts and issues)
5. Depending on the replenishment type (RP type), SAP F&R can execute the requirements calculation with a manual
target stock or manual minimum stock and a reorder point. You de ne the reorder point in the master data for the
location product.
 Example
In the master data you have set RP type 09 (manual target stock and manual reorder point) and the reorder point as
10 pieces. If the level of stock falls below the reorder point of 10 pieces, SAP F&R includes the location product in the
requirement calculation.
More Information
Service Level Pro le
Multi-Step Requirements Calculation
7/31/2021
Use
In the requirement calculation pro le, you de ne parameters that SAP F&R uses in the requirement calculation.
Features
The requirement calculation pro le contains all settings for the requirement calculation for a location product. This includes the
following settings:
For calculating the minimum stock
For distributing consumption among the days in the week
For the replenishment type (RP type)
SAP F&R uses the RP type to switch automatically between manual and automatic replenishment.
For using the aggregated order forecast for the multilevel requirements calculation
Basic settings
You can con gure requirement calculation to set negative stock values to zero, for example, or specify a target stock
that you want the system to retain at the end of the listing.
Activities
To maintain location products and assign the requirement calculation pro le there, go to the SAP Easy Access screen and
choose Forecasting and Replenishment Master Data Product Maintain Location Products .
For more information about requirement calculation pro les, see the Implementation Guide (IMG) for Forecasting and
Replenishment under Forecasting and Replenishment Processor Maintain Requirement Calculation Pro les .
Multi-Step Requirement Calculation

The basis of the multi-step requirements calculation is the order forecaset of the relevant target location. In a source location,
you can use the multi-step requirements calculation as an alternative to the regular forecast or as a demand in uencing factor
(DIF) for the regular forecast. For the source location, the system aggregates the order forecasts of the corresponding target
locations (according to the current delivery schedule). For more information, see Order Forecast.
Order Forecast
Based on a delivery schedule, the order forecast calculates the expected order quantities. Using the regular forecast that is
based on sales days, the order forecast calculates the requirements for future periods. In addition to the delivery schedule
(ordering days, delivery days, availability days), the order forecast takes the current stock and the open orders into account.
The calculation also takes the rounding into account.
Service Level Pro le
Use
Unforeseeable uctuations in requirements can cause a higher demand for a product and therefore lead to stockouts. To
prevent stockouts and take variations in requirements into account, the system adds a safety amount to the result of the
7/31/2021
forecast. This safety amount increases (non-linear) with your de ned service level, the estimated forecast error, and the range
of coverage.
Features
You can de ne the service level depending on the inventory turnover of a product (its selling class) or depending on the
importance of a product in the assortment as a whole (by ABC classi cation). If the selling class or the ABC indicator of the
location product changes, the system automatically uses the appropriate service level in the requirement calculation.
In addition to the service level, you can use a special service level.
The following special service levels are available:
Service level for new location products
The system uses this service level if the number of sales periods for a location product is between three and six.
Service level for determining stockouts
The system uses this service level to avoid stockouts in the stock period. If the forecast requirement exceeds the
expected stock, including the expected goods receipts, the system issues an exception.
Service level for location products with an expiration date
The system uses this service level to avoid being left with stock that is past its expiration date. The requirement
calculation determines how many products will be sold by the expiration date. If the net requirement is higher than this
number, the system issues an exception.
Service level for location products with maximum stock level
The system uses this service level so that the permitted maximum stock level is not exceeded. The separate
requirement calculation determines how many products can be ordered before the maximum stock level is exceeded. In
the requirement calculation pro le, you can de ne whether the maximum stock represents a threshold value for the
requirement quantity or causes an exception to be issued (hard or soft limit).
Service level for location products with target range of coverage
The system uses this service level to make sure that the minimum or maximum range of coverage is met. Depending of
the target range of coverage, the system increases the requirement to cover the minimum target range of coverage or
issues an exception if the maximum target range of coverage is exceeded.
Service level per DIF schema
You can de ne this optional service level in addition to the regular service level. For the period in which the DIF occurs,
this service level replaces the regular service level. You can de ne this service level for each selling class and ABC
indicator.
Service level high season schema
For periods with high seasonality (high season schema), you can de ne a separate service level. The FRP can determine
a high season schema automatically. SAP F&R combines periods with high seasonality that exceed a de ned threshold in
a high season schema. You can de ne this service level for each selling class and ABC indicator.
Activities
You de ne the individual service levels in a service level pro le. You assign the pro le at location product level.
You can de ne the regular service level dependent on the ABC indicator and the selling class. The system uses the following
sequence when determining the service level:
7/31/2021
1. Determination based on the ABC indicator and the selling class
2. Determination based on the ABC indicator
3. Determination based on the selling class
4. Determination without ABC indicator and selling class
For more information about the service level pro le, see the Implementation Guide (IMG) for Forecasting and Replenishment
under Forecasting and Replenishment Processor Maintain Service Level Pro les .
Example
The table below illustrates how the system calculates the service level:
ABC Indicator Selling Classes
- Default value USS1 USS2 SS1 SS2 FS1 FS2
Default value 96% - - 90% 91% - -
A - - - 91% 92% 97% 98%
B 94% - - - - - -
C - - - - 89% - 93%
Location product with ABC indicator A and selling class FS1
Considering the service level of 97%. As there is a service level de ned for the combination of ABC indicator A and selling
class FS1, this service level is used.
Location product with ABC indicator B and selling class SS2
Considering the service level of 94%. As no service level is de ned for the combination of ABC indicator B and selling
class SS2, the default value for ABC indicator B is used.
Location product with ABC indicator C and selling class SS1
Considering the service level of 90%. As no service level is de ned for the combination of ABC indicator C and selling
class SS1, and as there is no default value for the ABC indicator C, the default value for SS1 is used.
Location product with ABC indicator C and selling class FS1
Considering the service level of 96%. As no service level is de ned for the combination of ABC indicator C and selling
class FS1, nor are there any default values for ABC indicator C and selling class FS1, the general default value is used.
Preallocation
Use
Promotions and seasonal events, such as Christmas, can lead to an unusual uplift in customer demand. To meet this demand,
you can use a preallocation pro le to move merchandise deliveries to stores or distribution centers to an earlier timeframe
than originally needed. This allows you to distribute the workload over more weeks and thus avoid logistical bottlenecks at peak
demand times.
The Maintain Preallocation Pro le screen contains a table where you can enter a source week, target week, and percentage to
be preallocated to the target week. You then assign the pro le to location product combinations using the Location Product
7/31/2021
Mass Maintenance transaction. The requirement calculation uses this information when determining forecasted quantities for
each store.
 Example
Suppose the original demand of a popular toy would be 40 pieces to be delivered to each store in week 51. However, you
know that an exceptionally high delivery quantity for this week would cause a logistic bottleneck. In this case, you can shift a
portion of the forecast demand to an earlier timeframe, so that stores will receive an additional 20 pieces in week 49 and an
additional 10 pieces in week 50, leaving only 10 pieces for week 51.
The preallocation pro le for this might look like the following:
Source Week Target Week Percentage
2007 51 2007 49 50%
2007 51 2007 50 25%
You enter a percentage of the total delivery, not the number of toys. Also, the weeks are expressed in yyyyww format. The
system distributes the additional demand equally over all sales days within the target week.
 Note
Only the forecasted demand is shifted from the source week to the target weeks for the purpose of demand calculation.
However, the real demand will only occur in the source week. This means that the stock in the target week will be higher than
the real demand, but the preallocated part of the stock cannot be sold prior to the source week. Therefore, the preallocated
demand is virtually reserved during demand calculation for the source week
A single preallocation pro le can contain multiple source weeks and multiple target weeks. It is also possible for one source
week to have several target weeks. However, you cannot have a week that is both a source and target week in the same pro le.
The target week must always be earlier than the source week; that is, you can only move deliveries to an earlier point in time,
not later.
You can create, copy, and delete preallocation pro les.
Integration
The system checks whether the demand for a given week exceeds the hard or soft limits maintained in Customizing, such as:
Maximum quantity that can be ordered without exceeding the maximum stock
Maximum quantity that can be ordered without exceeding the shelf life duration
Maximum quantity that can be ordered without exceeding the maximum target range of coverage
Preallocated quantities can override soft limits for the rst demand period only, but not the hard limits.
 Example
Suppose the maximum stock limit for a product is 60 pieces and the net demand for the rst demand period is 50 pieces.
The preallocated demand would generate an order for 70 pieces.
If the maximum stock is a soft limit, the system generates a warning message but still orders the full 70 pieces.
If the maximum stock is a hard limit, then the system generates a warning and reduces the order to 60.
7/31/2021
The replenishment planner must determine the preallocation percentages manually. There is no automatic determination
based on sales volume.
Preallocation is only considered during replenishment calculation. Preallocated quantities are not visible in the SAP F&R user
interface (for example, in the Replenishment Workbench).
Requirement Quantity Optimization
Use
During automatic replenishment planning, the system optimizes the requirement quantities after requirement quantity
calculation. The FRP run generates optimized order proposals in accordance with your optimization settings. In this process,
among other things, SAP F&R optimizes your net requirements to enable the use of logistical order units or reduce overall
costs.
To carry out requirement quantity optimization, you must have de ned the necessary pro les and group settings
according to your business needs. For more information, see:
Rounding Pro les
Capital Lockup Pro les
Restriction Pro les
Order Balancing Pro les and Order Balancing Groups
You can deactivate individual optimizing steps in Customizing. For more information, see Pro le for Requirement
Quantity Optimization.
You con gure some of the pro les and group settings listed above - such as the capital lockup pro le and the restriction
pro le - in Customizing, and the rest in the application.
 Note
You can assign the de ned pro les in the master data. SAP provides a standard reference pro le (with the exception
of the order balancing pro le) that you can either adopt unchanged or copy and modify under another name. If you do
not assign a different pro le in the master data, the system uses the standard pro le.
You can run optimization for speci c products and order proposals. Net demand rounding and capital lockup
optimization are product-speci c; the restriction checks are order-proposal-speci c. Order balancing optimization can be
product-speci c or product group-speci c.
Integration
With the exception of rounding, SAP F&R only applies requirement quantity optimization during automatic planning. You
can check compliance with the restrictions and round the order proposal quantities in manual planning, but you cannot
perform any other optimization steps.
Rounding
SAP F&R rst applies rounding to the demands of all demand periods. In the later optimization steps, it checks whether
it should add the rounded requirements for the order proposal quantity to the demands from the rst requirements
7/31/2021
period.
You can perform rounding for order proposal items that were created manually and automatically. If rounding causes
automatic planning to exceeds the maximum stock, you can generate an exception and (through soft and hard limits)
control whether or not you want to allow the maximum stock to be exceeded.
You can activate manual rounding with a toolbar button in the Replenishment Workbench and the Product Workbench.
The Rounding Status column for order proposal items shows you whether and how SAP F&R rounded a given item.
During requirement quantity optimization, SAP F&R considers hard and soft limits that are derived from the parameters
in the location product's master data. This limits may prevent optimization by the system based on vendor restrictions,
economic order quantity, or order balancing because it cannot ll up an order proposal with demands from future
demand periods (after the rst period).
Soft limit
The order proposal quantity can only exceed a soft limit if this is needed to cover the demand of the rst demand
period. Soft limits are derived from the following parameters:
Minimum shelf life
Maximum target range of coverage
Maximum stock
The value for maximum stock is stored in the master data for the location product. You can de ne whether
this parameter should be a hard or soft limit in the requirement calculation pro le. The maximum stock is
con gured as a stock limit in the default settings. For more information, see the Implementation Guide
(IMG) for Forecasting and Replenishment under Forecasting and Replenishment Processor Maintain
Requirement Calculation Pro les .
If the demand from the rst demand period exceeds the soft limit, the system optimizes demand such that the
demand only covers the rst demand period, but does not use any other demand periods for llup.
Hard limit
The order proposal quantity must comply with this limit, which is derived from the following parameters:
Stock at end of the listing period (requirement calculation pro le)
The discontinuation date is stored in the master data for the location product.
Maximum stock (see above)
In this case, the system trims the requirement quantity in accordance with the limit and does not ll up any
further. It does so even if the order proposal quantity can no longer cover demand from the rst demand period.
 Example
Example of how the system uses the maximum stock limit:
The threshold value is 200 pieces and demand from the rst demand period is 300 pieces. If a soft limit is
de ned, SAP F&R calculates a proposed order quantity of 300 pieces. If the hard limit is used, however, only 200
pieces are calculated.
 Note
The calculation details and the rounding log show which limit the system used and why. For more information, see
General Functions in the OPM Workbenches.
7/31/2021
Figure 1: The following graphic shows the integration of requirement quantity optimization in the automatic replenishment process:
 Note
Optimization to an additional restriction can override the result of an order balancing optimization.
Features
Product-Speci c Optimization
You can use the following pro les and group settings together with a product (or, if an order balancing pro le is involved, with a
product group):
For more information, see Determination of Units of Measure for Rounding or Ordering.
Rounding Pro les
You can run order balancing optimization at either the product or product group level.
Order-Proposal-Speci c Optimization
You can use the Restriction Pro le with reference to an order proposal. For more information, see Restriction Check During
Automatic Replenishment Planning.
7/31/2021
Constraints
The system does not perform capital lockup optimization, the restriction check, or order balancing during manual planning (for
order proposals that you create manually in the Replenishment Workbench or Product Workbench).
Use
Unit of measure groups (UoM groups) are groups of one or more units of measure that you either allow as units of measure for
a product or exclude from the set of possible UoMs for the product. You can assign UoM groups for the products of both the
deliverying and receiving locations.
Integration
You assign the UoM group in the master data, to a combination of product and target or destination location:
The unit of measure group for the source location contains the units of measure that the source location delivers,
such as pallets and boxes if a vendor only ships a product in pallets and boxes.
The unit of measure group that you assign to the destination location de nes the units of measure that can be
sent to the destination location. For example, you can assign the unit of measure group so that shops in the
center of town are not sent any pallets.
 Note
For more information, see Determination of Units of Measure for Rounding or Ordering.
You can use a BAdI to implement your own custom logic as to which unit of measures you want SAP F&R to use for RQO,
and another BAdI to implement a custom check of whether the rounding unit agrees with the allowed order unit. For
more information, see the Implementation Guide (IMG) under Forecasting and Replenishment Requirement Quantity
Optimization Enhancements Using Business Add-Ins
BAdI: Check Unit of Measure Group ( /FRE/FU_RQO_BADI001)
BAdI: Rounded Unit for Ordering ( /FRE/FU_RQO_BADI002)
You can import unit of measure groups. For more information, see Inbound Interface for Unit of Measure Groups.
Features
You can also set an exception ag. If you set the indicator, you can assign all units of measure de ned for the product to the
product, except for those de ned in the unit of measure group.
Activities
To maintain rounding pro les, go to the SAP Easy Access screen and choose Forecasting and Replenishment Requirement
Quantity Optimization Maintain Unit of Measure Groups .
Example
Example 1
Unit of measure group 001
7/31/2021
Unit of measures PC, BOX, PAL
Exclusion indicator: Not set
The only units of measure allowed in this example are piece, box, and pallet.
Example 2
Unit of measure group 002
Unit of measures BOX, PAL
Exclusion indicator: Set
All units of measure are allowed in this example, except box and pallet.
Rounding Pro les
Use
SAP F&R requires logistical rounding pro les for requirement quantity optimization to round quantities to multiples of a unit of
measure, for example, or to switch between units of measure.
Integration
You assign the rounding pro le in the transportation lanes for products. On the SAP Easy Access screen, you choose
Forecasting and Replenishment Master Data Supply Network Maintain Transportation Lane for Products .
You can import rounding pro les. For more information, see Inbound Interface for Rounding Pro les.
Prerequisites
To perform rounding, you must have de ned the rounding parameters in the pro le for requirement quantity optimization.
Rounding must be active in the basic settings of the pro le. The tables below illustrate how the Rounding Type and Rounding
Mode parameters affect rounding behavior:
Rounding Type Rounding Behavior
Total requirement The threshold values are calculated using the following formula:
1 - | (rounded quantity - requirement quantity) / rounded quantity |
[The quantity calculated within the absolute value brackets ("| ... |") is
always used as a positive value, for example, | -10 | = 10.]
Individual logistical unit of measure Depends on the percentage missing to the nearest multiple of a unit
Rounding Mode Rounding Behavior
Rounding up and down to the largest unit of measure is The system uses the largest possible unit of measure as the order unit.
preferred
Always prioritize rounding up over rounding down The system always tries to round up to a unit of measure. If this is not
possible the system rounds down.
For more information, see Pro le for Requirement Quantity Optimization.
7/31/2021
Features
You can de ne rounding rules that specify the percentage from which the system rounds for a given unit of measure. You
can specify threshold values for rounding quantities up and down. Based on these rules, requirement quantity
optimization determines which of the permitted units of measure is most suited as the requirement quantity.
You can use zero rounding. It determines what happens when the rounding result is zero and no purchase order can
therefore be created. You can choose which of the following rules you want the system to use:
Do not round to zero
Round every possible rounding unit down to zero
Only round the unit of measure with the smallest base unit down to zero
Activities
In maintain rounding pro les, go to the SAP Easy Access screen and choose Forecasting and Replenishment Requirement
Quantity Optimization Maintain Rounding Pro le .
Example
Pallets and boxes are possible rounding units. Rounding shows that the order quantity is so small that it will not ll a whole
pallet. The system rounds down to zero, which means nothing is ordered. You have the following options for zero rounding:
If you select the rounding mode in which SAP F&R rounds every possible rounding unit down to zero, no purchase order is
created because the system rounds the rounding unit pallet down to zero.
If you select the option in which SAP F&R only rounds the unit of measure with the smallest base unit of measure down
to zero, the system cannot round down to zero, as the unit of measure pallet is not the smallest possible unit. The
system checks whether a box can be ordered. If so, it orders the box; if the quantity is too small for a box as well, nothing
is ordered, because no smaller rounding unit is de ned.
If you choose the option that SAP F&R cannot round down to zero, the system orders a box.
Use
Sometimes it makes business sense to order a larger quantity than is actually required. Before doing so, you need to compare
the procurement costs with the storage and capital lockup costs - while taking future demand into account.
You use the capital lockup pro le to compare the capital lockup costs with the ordering costs to determine the most cost-
effective order quantity. Ordering costs are xed costs for each order item in a valid currency, irrespective of the ordered
quantity (for example, logistics costs).
Integration
You assign the capital lockup pro le to a location product in the master data. To do so, go to the SAP Easy Access screen
and choose Forecasting and Replenishment Master Data Product Maintain Location Products .
If you want to implement your own logic as to which storage unit SAP F&R uses for capital lockup optimization, you can
use Business Add-In ( /FRE/FU_RQO_BADI004). For more information, see the Implementation Guide (IMG) for
Forecasting and Replenishment under Requirement Quantity Optimization Enhancements Using Business Add-
Ins BAdI: Change Storage Unit for Capital Lockup Optimization .
7/31/2021
Prerequisites
To execute capital lockup optimization, you have selected a default pro le for requirement quantity optimization and you have
not deactivated the capital lockup check in the basic settings of the pro le. For more information, see Pro le for Requirement
Quantity Optimization.
Features
You can activate and deactivate the capital lockup check itself in the pro le.
You have to specify a percentage for the capital lockup and an amount for the ordering costs.
Optional: You can specify parameters for storage costs, such as a stackability factor.
Activities
You create the capital lockup pro le in Customizing. For more information, see the Implementation Guide (IMG) for Forecasting
and Replenishment under Requirement Quantity Optimization Maintain Capital Lockup Pro les .
Restriction Pro les
Use
The restriction pro le determines the minimum quantity, multiples, or discount scales for an order proposal.
You can use restriction parameters to de ne the minimum quantity, weight, volume, or price an order proposal must have.
Integration
You assign the restriction pro le to the transportation lane for subranges. On the SAP Easy Access screen, you choose
Forecasting and Replenishment Master Data Supply Network Maintain Transportation Lane for Subranges .
Features
You can choose whether you want the restriction check to use the gross weight or the net weight.
You can de ne two independent restriction checks:
Main restriction check
This minimum restriction refers to a minimum quantity, weight, price, or volume.
Additional restriction check
You can set either a minimum restriction or a restriction for multiples or discount scales here. This restriction also
refers to a quantity, weight, price, or volume.
 Note
You can perform a check of the additional restriction even if you have not de ned a main restriction. For more
information, see Restriction Check During Automatic Replenishment Planning.
Activities
7/31/2021
To maintain restriction pro les, go to the SAP Easy Access screen and choose Forecasting and Replenishment Requirement
Quantity Optimization Maintain Restriction Pro le .
Example
Example 1
You can select the restriction category Minimum restriction for both restriction checks, once for a xed unit of measure, for
example, box and once for the price.
Example 2
You cannot de ne a restriction check for minimum order quantities, instead you should select the restriction category Multiple.
Example 3
For the rst restriction check you can de ne a minimum quantity and discount scales.
Use
You use these objects to control order balancing optimization ( order balancing), which you use to distribute the order proposal
quantity equally.
Order balancing distributes requirements for a location product to the order balancing week automatically. You can de ne the
order balancing week freely, for example, from Wednesday to Tuesday. In order to avoid logistical bottlenecks at weekends, for
example, in both the source location and destination location, you can distribute the requirements of a week over the individual
goods receipt days of the week for the destination location. The diagram below illustrates requirement quantity distribution
before and after order balancing.
7/31/2021
 Note
You cannot shift requirements into the future, for example, if you have increased requirements on the rst day of the order
balancing week, you cannot distribute the increase to the subsequent days.
Integration
You assign the order balancing pro le to an order balancing group.
You assign the order balancing group to a location product in the master data. To do so, go to the SAP Easy Access
screen and choose Forecasting and Replenishment Master Data Product Maintain Location Products .
Features
Order Balancing Pro le
You can con gure the basic settings for order balancing in the order balancing pro le.
Depending on which order balancing type you con gure, the system can distribute the order proposal quantities of each
individual location product or the entire proposal quantity of all location products contained in an order balancing pro le
equally along an order balancing week.
You can select the relevant order proposals for order balancing with regard to the planning date, delivery date, or
delivery date, and you can specify how many order balancing weeks are considered in the order balancing horizon.
7/31/2021
 Example
Three location products have been ordered on the planning date. One of them has its delivery date in week 1, another
in week 3, and the last one in week 4. The order balancing horizon is three weeks and the delivery date is the
reference date for order balancing. The system carries out order balancing for weeks 1 and 3 (SAP F&R balances the
quantity of all the goods receipts that belong to weeks 1 and 3). The location product with delivery date in week 4 is
not included in order balancing, because the goods receipt lies outside the order balancing horizon.
Order Balancing Group
You can create and maintain order balancing groups to perform order balancing according to the same rules for several location
products. During automatic replenishment, SAP F&R distributes the order proposal quantities of these location products across
an order balancing week.
Activities
You create the order balancing pro le in Customizing. For more information, see the Implementation Guide (IMG) of
Forecasting and Replenishment under Requirement Quantity Optimization Maintain Order Balancing Pro les .
To maintain order balancing groups, go to the SAP Easy Access screen and choose Forecasting and
Replenishment Requirement Quantity Optimization Maintain Balancing Groups .
Pro le for Requirement Quantity Optimization
Use
The rules that the system uses to optimize the requirement quantity depend on this pro le, which you de ne in Customizing. It
contains location-speci c rounding parameters and restriction parameters. For more information, see the Implementation
Guide (IMG) of Forecasting and Replenishment under Requirement Quantity Optimization Maintain Requirement Quantity
Optimization Pro les .
Integration
For more information about the hard and soft limits that SAP F&R takes into account during requirement quantity optimization,
see Requirement Quantity Optimization (RQO).
Features
You can select a particular RQO pro le as your default pro le. SAP F&R uses this default pro le whenever you create
new locations.
You can switch off individual optimization steps in the basic settings.
You have the following options for rounding with threshold values:
Round to a single logistics unit of measure
Rounding depends on the percentage that is missing for the nearest multiple of a unit. If the next unit is not
reached, the system calculates the percentage of a full unit that has been met. If the result is greater than the
de ned threshold value for rounding up, the system can round the gure up to the next greater full unit. If the
result is less than the de ned threshold value for rounding down, the system can round the gure down to the
next lesser full unit.
Rounding to a total quantity
7/31/2021
Threshold values relate to the total quantity of the ordered units and not to an individual purchase order unit.
 Note
The percentage from which SAP F&R rounds up is de ned as the difference between the rounded-up quantity and net
requirement, divided by the rounded-up quantity and multiplied by 100.
The percentage from which SAP F&R rounds down is de ned as the difference between the net requirement and
rounded-down quantity, divided by the rounded-down quantity and multiplied by 100.
Which of the allowed rounding rules the system uses depends on which of the following options you have de ned as the
rounding mode:
The system gives priority to the largest unit of measure when rounding up and down. It uses the largest possible
unit of measure as the order unit.
The system always gives priority to rounding up over rounding down. It always tries to round up to a unit of
measure. If this is not possible the system rounds down.
If none of the de ned rounding rules is permitted, the system calculates an alternative quantity. You can customize the
alternative rounding rule for this case:
No Rounding
The system converts the net requirement quantity to the de ned order unit. You can de ne how many decimal
places the system should include for individual units of measure in Customizing for units of measure.
Rounding to a de ned order unit
The system rounds the net requirement quantity up to the de ned order unit.
Round down to the best suited permitted unit of measure
The system rounds down to the nearest unit of measure to the net requirements.
Other Restriction-Speci c Parameters
Percentage to discard order proposals
This percentage relates to the main restriction check. If the total order quantity for an order proposal lies below this
percentage, SAP F&R cancels the order proposal.
Percentage for optimization
If the total order quantity for an order proposal lies below this percentage, the system does not ll up the quantity to the
main restriction.
Percentage threshold for order value for generation of exception
The system generates an exception if a supplier's main restriction cannot be ful lled, even though SAP F&R took
demand from all periods for all products into account. You can suppress this exception generation, however, if the main
restriction is ful lled at least up to the speci ed percentage.
Fill-up method
This parameter relates to the minimum restriction check. If the requirement quantity for a period falls below the
minimum order quantity, the system uses requirements from other periods to reach the minimum quantity. This lets you
con gure how SAP F&R lls up requirements to meet the minimum order quantity.
Determination of Units of Measure for Rounding or Ordering

7/31/2021
The system checks the following parameters before performing rounding:
Percentage rate for discarding requirement of a product (if net requirement is < 1)
Article-speci c minimum order quantity
Permitted units of measure for rounding
The following settings have an effect on the units of measure that the system selects for rounding or ordering:
Order unit
It is assigned to the transportation lane for products (connection between location product and source location). SAP
F&R copies this assignment through the interface. If no unit of measure is de ned, the system uses the base unit of
measure of the product as the order unit. The order unit is always one of the units of measure that are permitted for
rounding and ordering even if it is excluded by a unit of measure group.
Variable order unit
This setting determines whether SAP F&R can only round a product up to the order unit, or whether any allowed unit of
measure can be used. The following options exist:
Variable unit of measure for rounding and ordering
The system can round up to any de ned unit of measure. The product is ordered in the rounded unit of measure.
Variable unit of measure for rounding but not for ordering
The system can round to any de ned unit of measure, but orders the product in the order unit.
Variable order unit is permitted for neither rounding nor ordering
Rounding and ordering are performed in the order unit.
UoM groups de ned for the source and destination locations
Rounding Pro les
How does the system determine the unit of measure for rounding?
You assign the parameters to determine potential rounding units in the master data for the transportation lane for products:
If you have not de ned a rounding pro le, no rounding is performed. The system uses the base unit of measure for the
quantity.
If you have de ned a rounding pro le but no variable unit of measure for rounding, the system rounds the quantity
required to the order unit.
If you have assigned a rounding pro le and de ned a variable unit of measure for rounding, the system calculates the
permitted order units based on the unit of measure groups for the source and destination locations. The following
rounding units are permitted:
The order unit
The intersection of units of measure as de ned in the following places:
In the product master data
In the rounding pro le
In the unit of measure groups
7/31/2021
How does the system determine the nal order unit?
SAP F&R determines the possible order units for a transportation lane for products as follows:
If a variable unit of measure is not permitted for the purchase order:
The order unit de ned in the master data for the transportation lane for products is the only unit of measure that is
permitted. The system converts the rounded amount (or, if no rounding pro le is assigned, the net requirement) to the
order unit. If the result is not an integer, SAP F&R calculates the decimal places, trimming the result to the allowed
number of decimal places in the process.
If a variable unit of measure is permitted for the order:
The permitted order units correspond to the permitted rounding units.
Restriction Check During Automatic Replenishment Planning
Main Restriction Check

Requirement quantity optimization checks whether an order proposal ful lls the main restriction.
If the order proposal does not ful ll the minimum restriction, requirement quantity optimization checks whether the order
quantity is so small that SAP F&R should cancel the entire order proposal (due to the percentage threshold to discard the order
proposal). If this is the case, the system issues an exception. Otherwise, requirement quantity optimization checks whether the
order proposal (OP) can be optimized according to the restriction parameters. To do so, it also uses the restriction parameters
in the Pro le for Requirement Quantity Optimization.
If the quantity for optimization is not large enough, it remains as it is and the system issues an exception. Otherwise SAP F&R
optimizes the order proposal on a requirement-dependent basis. In this case, the system uses the preplanned requirement
from future demand periods to reach the minimum quantity. This is done for all of the supplier's products that can be ordered
on the order proposal date. If the system has taken several periods into account to achieve this, it issues an exception.
SAP F&R concludes optimization in the demand period based on the Fill-up method parameter: when the minimum order
quantity is reached or the system has taken the requirement into account for all products within a particular period. If the
minimum order quantity for a supplier is not reached even through the system has added all the demand periods for all of the
supplier's products, the system issues an exception.
Additional Restriction Check

After optimizing the order proposal according to the main restriction, you can perform an additional restriction check.
Additional minimum restriction
You can check another minimum restriction from a different restriction type (price, quantity, weight,or volume). In the
restriction pro le you can de ne a percentage for discarding the order proposal. If the optimized quantity is not above
this percentage rate, in relation to the minimum restriction, the system discards the order proposal.
Restriction check for multiples
SAP F&R checks whether the optimized order proposal quantity is a multiple of a de ned value. If not, the system
increases the quantity so that a multiple is reached. If the smallest multiple is not reached (although SAP F&R has added
all the requirements from all demand periods together) the system checks whether the quantity is greater than the
percentage rate at which the entire order proposal is discarded. If not, the system does not create an order proposal and
generates an exception; if so, the system creates an order proposal and also generates an exception.
Discount scales
7/31/2021
You use discount scales when the supplier gives discounts for de ned order quantities. Optimization checks whether the
optimized order quantity quali es for at least the lowest discount segment. If not, SAP F&R increases the quantity with
the requirements for future demand periods until the lowest discount threshold is reached. After this, the system
calculates the most economical order quantity, including all the de ned discount scales that apply from the existing
demand periods. The system compares the supplier's discount with the percentage of storage costs. If the smallest
discount scale is not reached (although the system has added all the requirements from all demand periods together)
requirement quantity optimization checks whether the quantity is greater than the percentage rate at which the order
proposal is discarded completely. If not, the system does not create an order proposal and generates an exception; if so,
the system creates an order proposal and also generates an exception.
Fallback strategy
You can use this setting to de ne the system response when a sufficient quantity is available for the order proposal, but
requirement quantity optimization cannot use a multiple or discount scale. In this case, you can deactivate the additional
restriction check or specify that SAP F&R should calculate an OP quantity that is as close to the additional restriction as
possible (but below it) , as close to the additional restriction as possible (but above it), or as close to the mean value of
the multiple or discount scale range as possible.
Restriction Check after OP Processing in an OPM Workbench

After you create or change the order proposal in the Replenishment Workbench or Product Workbench, SAP F&R checks all the
de ned restrictions. The workbench shows whether or not the order proposal meets the restrictions. If you use discount scales
as an additional restriction, you can display the scale conditions in the restriction pro le view. Note that the system does not
optimize the order proposal with regard to ful lling the de ned restrictions, however.
Product Substitution in the Forecast and Requirements Calculation
Use
You can use this process in order to take account of the switchover information that has been either imported for product
substitution or generated in SAP F&R as part of the forecast and requirements calculation in SAP F&R.
Using the master data assignments and switchover information transferred from SAP ECC to SAP F&R, SAP F&R automatically
plans the follow-up product or the original product in the case of a replacement product.
 Note
You can use this process both in connection with SAP ECC and also exclusively with SAP F&R and your own systems from
which you import the required data.
Prerequisites
You have activated the consideration of substitute products at client level in SAP F&R. For more information, see the
SAP Implementation Guide (IMG) under Forecasting and Replenishment Master Data De ne Settings at Client Level .
You have de ned a substitution merge pro le in SAP F&R Customizing. For more information, see the IMG under
Forecasting and Replenishment under Substitution Products Substitution Merge Pro les .
You have imported the following data to SAP F&R:
Substitution assignments. For more information, see Inbound Interface for Substitution Assignments.
Switchover information. For more information, see Inbound Interface for Switchover and Switch Back Information.
If you have de ned the use of a Business Add-In in the substitution merge pro le, you must implement this BAdI (
/FRE/FU_FRP_BADI008). For more information, see the SAP Implementation Guide (IMG) under Forecasting and
7/31/2021
Replenishment Substitution Products Enhancements Using Business Add-Ins BAdI: FRP - Merge Stock and
Consumption .
Process
1. You generate switchover information and enrich the switchover information. For more information, see Creation and
Enrichment of Switchover Information.
2. If there is a switchover to the follow-up product, then SAP F&R controls planning of original and follow-up products using
lock behavior in the location product.
3. According to the settings de ned in the substitution merge pro le, the system merges (before the start of the forecast
and requirements calculation) the stocks, consumptions and order proposals of the original product with those of the
substitution product.
For more information, see Merging of Transaction Data.
4. The forecast and requirements calculation generates order proposals whereby the system takes the product
substitution (including the merged transaction data and the generated DIF occurrences) into account:
In a switchover to the follow-up product, the system plans the follow-up product and generates order proposals
with the follow-up product.
In a switchover to the replacement product, the system plans the original product (if planning of the original
product is scheduled in SAP F&R) and generates order proposals with the original product.
If SAP F&R is already planning the replacement product, it also generates order proposals with the replacement
product.
 Note
Following a product substitution with switchover to the replacement product, SAP F&R continues to plan the same
products as prior to a switchover. If the system, for example, was not planning the replacement product before a
product substitution, then the situation does not change after the product substitution.
Lock Behavior with Location Products
Use
SAP F&R controls the planning of location products that appear in substitution assignments or switchover information with
follow-up relationships using the lock indicator lock for product substitution in the location product master data. Depending on
whether the switchover has occurred or not, the system sets and removes the lock for the original or follow-up product.
Features
On the import of a substitution assignment with follow-up relationship, the system sets the lock for the location product
containing the follow-up product and removes the lock for the location product containing the original product. SAP F&R
ensures this way that it plans the original product and not yet the follow-up product.
After a switchover from the original product to the follow-up product, the system sets the lock for the location product
containing the original product and removes the lock for the location product containing the follow-up product. SAP F&R
ensures this way that it is planning the follow-up product and no longer the original product.
 Note
SAP F&R does not plan location products for which the lock indicator lock for product substitution is set.
7/31/2021
Merging Transaction Data
Use
You can merge consumption data, stocks, and order proposals of a substitution product and the related original product for the
forecast and requirements calculation. The objective here is to take into account in automatic replenishment planning, the
special characteristics of consumption and stock data following a product substitution.
Integration
The system uses the merged data for the forecast and requirements calculation.
Forecast
In order to be able to create an exact forecast, the system considers the historical sales data of the original product together
with the sales data of the substitution product.
In order to be able to carry out an exact requirements calculation from the switchover date, the system considers the stock
information and order proposal quantities of the original product together with the corresponding data of the substitution
product.
Merging operation
The system evaluates the following for this:
the master data saved in the substitution assignment for example, the conversion factors.
the substitution merge pro le
You de ne in the pro le if the system is to merge transaction data, and if so which data - if it is only to merge in
the case of follow-up relationships, only with replacement relationships, or with both.
You determine the follow-up time measured in days following a switchover or a switch back.
 Note
The system always merges the data with the substitution merge pro le that is valid at the time of merging.
Therefore, changes to the substitution merge pro le have no effect on already existing merge results.
the switchover information
The system searches the switchover and switch back information for an active entry.
 Caution
In the case of switchover information without substitution merge pro le, there is no merging.
Calculation of the merge period
SAP F&R determines the merge period on import of the switchover information and also on creation and enrichment of the
switchover information. The system limits the merging of the transaction data to a time span that starts with the switchover
date and where the end dates are different depending on the substitution control:
for the follow-up product, event and time-controlled:

7/31/2021
The end of the merge period is derived from the switchover date plus follow-on period. With event-controlled, the merge
period can be set up to the end of the switchover period.
for the replacement product, event-controlled:
The end of the merge period is derived from the switch back date plus follow-on period.
The following graphic illustrates the relationship between the switchover period and the merge period.
 Caution
The merge period must not necessarily lie within the switchover period. With substitution control follow-up product,
time-controlled, the merge period can lie outside the switchover period.
You specify the follow-up time in accordance with your business requirements. For example, it may be appropriate, in
the case of perishables, not to have any follow-on time.
DIF occurrences
Using the substitution merge pro le, you control the creation of DIF occurrences for replacement relationships. You can de ne
whether the program for creation and enrichment of switchover information is to create DIF occurrences for the replacement
product, the original product, or for both. For more information, see DIF Occurrences on Product Substitution.
Prerequisites
7/31/2021
You have ful lled the prerequisites for product substitution in the forecast and requirements calculation.
Features
As part of product substitution, you have the following options for preparing the data for replenishment planning:
For planning of the follow-up product, following a switchover from the original product to the follow-up product, you can
merge the transaction data of the follow-up product with the data of the original product. For more information, see
Merging the Transaction Data of Follow-Up Products.
For planning of the original product, following a switchover from the original product to the replacement product, you can
merge the transaction data of the original product with the data of the replacement product. If the replacement product
is contained in the assortment, you can plan the original and replacement products with the merged data. For more
information, see Merging the Transaction Data of Replacement Products.
You can display the merge results for consumption and stock data in the following places:
in the Replenishment Planning Workbench
in the Product Workbench
Cause Determination
 Note
The actual transaction data remain unchanged even after merging. The system also provides the merged transaction data in
addition and uses it in the forecast and requirements calculation as current data.
Merging Transaction Data with Follow-Up Relationships
Use
During switchover to the follow-up product, the system merges stocks, consumptions and open order proposals of the follow-up
and original products according to the settings in the substitution merge pro le.
Prerequisites
Features
The system uses the following algorithms for merging:
Merged consumption (follow-up product) = actual consumption of original product + actual consumption of
follow-up product
Merged stock (follow-up product) = current stock of original product + current stock of follow-up product
Merged open order proposals (follow-up product) = current open order proposals of original product + current
open order proposals of follow-up product
Only for the follow-up product, does the system take into account the current open order proposals of the original
and follow-up product within the merge period.
During the merge period, the system uses the merge results when planning the follow-up product.
7/31/2021
Merging Transaction Data with Replacement Relationships
Use
During switchover to the replacement product, the system merges stocks, consumptions and open order proposals of the
original and replacement products according to the settings in the substitution merge pro le.
Features
The system merges differently depending on whether the location product belonging to the replacement product is contained in
the standard assortment or not.
 Note
The system evaluates the listing information that is valid on the planning date (the system uses the formula "planning date
minus one day"). If a location product is listed for a planning date, the product belongs to the standard assortment.
Replacement product not contained in assortment
During the merge period, the system uses the merge results when planning the original product. The system uses the
following algorithms for merging the consumption, stock, and order proposal data:
Merged consumption (original product) = actual consumption of original product + actual consumption of
replacement product
Merged stock (original product) = current stock of original product + current stock of replacement product
Merged open order proposals (original product) = current open order proposals of original product + current
open order proposals of replacement product
Location product for replacement product is not contained in the assortment
Replacement product contained in assortment
The system uses the consumption, stock, and order proposal data here differently to the case above:
Consumption data
The merged consumption data serves as a forecast basis. The system uses the following procedures for merging:
no merging
Only the actual consumption data of the original and replacement products serves as a forecast basis.
Customer-speci c
Merging of the consumption data results from the implementation of the Business Add-In BAdI: FRP - Merging of Stock
and Consumption.
Daily forecast
For the original and replacement products, the system uses the forecast data (current values) that has been created in
a previous forecast run as merged consumption data.
daily forecast or corrected consumption
The system calculates the merged consumption data as follows:
7/31/2021
for the original product from the forecast data (current values) of the original product that has been created in a
previous forecast run
for the replacement product from the actual consumption data of the replacement product, corrected with the
forecast data (current values) of the original product that has been determined in a previous forecast run
Average
For the original and replacement products, the system uses the average consumption data in each case as merged
consumption data.
Stock data
The system uses the merged stock and order data for requirements calculation. The system uses the following algorithms for
merging the stock data:
no merging
The system uses only the actual stock data of the original and replacement products for the requirements calculation.
Customer-speci c
Merging of the stock data results from the implementation of the Business Add-In BAdI: FRP - Merging of Stock and
Consumption.
Consideration of goods receipt quantities
The system calculates the merged stock data as follows:
for the original product: from the current stock of the original product, increased by the quantity of the
replacement product that has been delivered in place of the original product and decreased by the sum of
merged consumption less actual consumption of the original product
for the replacement product: from the current stock of the replacement product, decreased by the quantity of the
replacement product that has been delivered in place of the original product and increased by the sum of merged
consumption less actual consumption of the original product
Open order proposals (order proposal quantities)
The system uses the following algorithms for merging:
no merging
The system uses only the the actual open order proposals of the original and replacement products for the requirements
calculation.
merging
SAP F&R calculates the merged open order proposals on the following basis:
for the original product: from the open order proposals with the original product and the open order proposals
with the replacement product, that SAP F&R has imported as a result of a substitution in the logistics system.
for the replacement product: from the open order proposals with the replacement product. The system does not
take into account here the open order proposals with the replacement product that SAP F&R has imported as a
result of a substitution in the logistics system.
 Note
Merging of stocks and open order proposals is only logical if the connected logistics system also transfers - as part of the
switchover and switch back information given to SAP F&R - the numbers of the procurement documents (as reference
7/31/2021
document numbers) in which a substitution has taken place within logistics. Only when this information is available, can SAP
F&R determine the orders with the replacement product belonging to the original product.
More Information
DIF Occurrences on Product Substitution
DIF Occurrences on Product Substitution
Use
Following a switchover to the replacement product, the system creates DIF occurrences according to the settings in the
substitution merge pro le.
Integration
The system uses DIF occurrences in order to explain notable uctuations in the consumption data of a location product.
For more information, see Demand In uencing Factors.
After starting the program to create and enrich switchover information, the system automatically creates DIF
occurrences according to the substitution merge pro le.
 Example
The system automatically creates DIF occurrences for the source location:
You set, for example, in the substitution merge pro le a DIF ID for the original and the replacement product in the
source location (the DC) and also merging for the store. You assign this pro le to a substitution assignment with
location type store. Once the product substitution has been run, the system merges the transaction data for the
store. In addition, the system creates DIF occurrences of type Ignore Historical Values for the combination of original
product and DC and also the combination of replacement product and DC. Therefore, SAP F&R ignores the irregular
goods issues of the DC in the forecast calculation for the DC. If the DC delivers to 1000 stores, and a substitution
assignment exists for each store with the same substitution merge pro le, then, for each store, SAP F&R creates DIF
occurrences for the DC in case of product substitution. This can be up to 1000 DIF occurrences for the combination of
original product and DC and also up to 1000 DIF occurrences for the combination of replacement product and DC.
The system also takes into account DIF occurrences that have been created manually in the DIF Workbench.
 Note
If SAP F&R merges transaction data for a DC following a product substitution at this DC, ensure if possible, that the
system does not create a DIF occurrence for the DC following a product substitution at a store.
If a DIF occurrence of type Ignore Historical Values exists, SAP F&R ignores irregular goods issues of the DC in the
forecast calculation for the DC. Note that SAP F&R forms a mean value in the DIF period from the consumption
values taken before and after the period. In cases where it is not possible to derive a mean value, SAP F&R uses the
forecast procedure for newly listed products.
Prerequisites
7/31/2021
You have created DIF IDs of type Ignore Historical Values , which you wish to use in the substitution merge pro le. For
more information, see the Implementation Guide (IMG) of Forecasting and Replenishment under Demand In uencing
Factors DIF Occurrences .
You can only create DIF occurrences that use DIF type Ignore Historical Values.
Features
By specifying DIF IDs in the substitution merge pro le, you can determine which DIF occurrences (with reference to
source and target location) you wish to create.
To create the DIF occurrences, you can run the program for Creating and Enriching Switchover Information.
More Information
Merging Transaction Data with Replacement Relationships
Administration
Use
SAP F&R requires the following information: the servers (or server group) on which the programs of the F&R Processor are
installed, where SAP F&R can store the data for communication, and the locations for which you want to calculate automatic
replenishment. You cannot perform automatic replenishment with SAP F&R without these settings.
Prerequisites
You must reserve sufficient memory space for the data from automatic replenishment that is required for communication.
Features
You con gure the control settings for automatic replenishment in the following administration areas:
Administration for system data
Administration for locations
Activities
1. To start administration for the F&R Processor, go to the SAP Easy Access screen and choose Forecasting and
Replenishment Forecasting and Replenishment Processor Administration .
Administration of system data
You have to con gure the server on which the programs of the F&R Processor are installed and the server
on which the system can store the les for communication. The system calculates the relevant paths
automatically.
You can de ne whether SAP F&R should perform parallel processing on the server and how big the
packages for the various process steps (replenishment calculation, DIF processing, and importing and
exporting of les) should be.
Administration for locations
You must set the following for each location:
7/31/2021
Activation period
You de ne the start and end dates of the time period for which you want to perform automatic
replenishment.
Server location
Enter the server on which SAP F&R is to store the data for communication.
Process control for location
Assign a process control pro le. The process control pro le de nes the days on which the F&R Processor
performs automatic replenishment, for example.
Additional activities (beyond regular process control)
You can specify a date to schedule additional steps that you want FRP to perform outside the con gured
frequency:
Initialization of the following data:
Historical time series (parameter initial consumption data)
Demand in uencing factors (parameter initial DIFs)
Con guration data (parameter init. tech.)
Additional forecasting run
More Information
Use
You use this function to con gure a process control pro le. You can either control the FRP run through the FRP Dispatcher or
schedule report /FRE/FRP_MID_BASIC for background processing.
 Note
You cannot use both options. If you have activated the FRP Dispatcher, you cannot use report /FRE/FRP_MID_BASIC.
Prerequisites
You must assign the process control pro le to the relevant location in Administration.
Features
If you use the FRP Dispatcher:
Once you activate and start the Dispatcher in the operative system, it keeps a service program (daemon) active
in the background that starts the FRP run automatically, once a day (usually at night), for all the con gured
locations.
7/31/2021
If you have to restart the FRP run (in case of technical problems on the application server, for example) you have
the following options:
You can use report /FRE/UI_FRP_PROC_LOC_BY_DISP to reset the status of the affected locations. The
Dispatcher processes them again, even if it has already processed them for that planning date.
If you start the report for all locations, the system takes any existing order proposals into account as open
purchase orders, and does not create them again. If you deleted the new order proposals before starting
the report, however, the system creates them again.
You can run report /FRE/UI_FRP_PROC_LOC_AFTER_ERR after you have corrected the errors for all
locations (or for the locations that were not processed completely: In this case, processing only executes
the steps of the FRP run that have not been processed yet (as speci ed in the Dispatcher pro le) after
the last successfully processed step.
If you do not use the FRP Dispatcher:
To execute automatic replenishment, you have to schedule processing of program /FRE/FRP_MID_BASIC once a day
as a background job. The F&R Processor performs automatic replenishment according to your settings in the process
control pro le.
SAP F&R can process the individual process steps in automatic replenishment (calculating replenishment, DIF
processing, and importing and exporting les) at different times. In a repeat run, you can either repeat the entire
replenishment process or start from a certain process step (for example, if the process step was not executed
successfully or if a program terminates). SAP F&R has to perform the process steps in the de ned numeric order (for
example, process step 1 cannot follow process step 3).
Activities
For more information about the process control pro le, see the Implementation Guide (IMG) for Forecasting and
Replenishment under Forecasting and Replenishment Processor Maintain Process Control Pro les .
FRP Dispatcher
Use
The FRP Dispatcher controls the individual process steps of the F&R Processor. When you use the FRP Dispatcher, you bene t
from the following additional features - in contrast to scheduling the FRP run as a background job:
Buffering of data during the forecast process to keep system load to a minimum
Greater exibility to adjust the execution of the F&R Processor to suit your process control (controlling of the
sequences)
A monitoring tool to call the current status of all process steps (for example, transfer of master data, transaction data,
or forecast run)
Prerequisites
You have to con gure the following pro le and administration settings before you can activate and start the FRP Dispatcher:
 Note
You can leave the SAP default pro les ( SAPDEFAULT) unchanged or copy them, adapt them to your requirements,
and save them as your own pro le. You can create your own pro les in Customizing.
7/31/2021
All times entered in the pro les relate to the time zone of the location concerned. The system always uses the time
zone that is de ned for a location. If the time zone of the location is different from the settings in the user data, there
may be differences in time from the user's point of view.
Dispatcher pro le
In the dispatcher pro le, you de ne the sequence of the individual process steps according to which the F&R Processor
works.
Process control pro les
For each sequence or location, you have de ned the day of execution (planning day) and the time frame in which the
system is to execute this process step. As the process control pro le de nes the time frame for location processing, the
start times you enter here must match the times speci ed in the start pro le.
Start pro le
Here you de ne how the F&R Processor is to work for a location.
If you want to execute the F&R Processor in a single step (the system executes all process steps sequentially at
the same time), you only need one start pro le. For each planning day, the day of execution and the time frame in
which the system starts the F&R Processor is de ned.
If you want to execute the F&R Processor in several steps (the process steps are performed at different times),
you need the relevant number of start pro les. For each planning day, the day of execution and the time frame in
which the system is to perform this process step is de ned.
According to the settings you have made in the start pro le, the F&R Processor starts as soon as the sales data has
arrived, provided the earliest start time has already been reached. The F&R Processor does not start until this time is
reached. If the sales data for a location is not available at this time (for example, due to a technical problem), the F&R
Processor starts when the latest start time is reached. If you want the system to take the sales data into account, you
have to set the Consumption Update Required ag.
Administration
You have assigned the following objects to the location that is to be processed automatically in Administration under
Location Data:
Dispatcher pro le
Process control pro le
Start pro le
Processing level
 Note
If you have selected processing level S, you must assign a start pro le to each sequence in the dispatcher
pro le.
If you have selected processing level P, assign the start pro le to the location in FRP administration.
Process
To activate and start the FRP Dispatcher, go to the SAP Easy Access screen and choose Forecasting and
Replenishment Forecasting and Replenishment Processor Activate and Start Dispatcher .
7/31/2021
The FRP Dispatcher works as a background process within the F&R Processor. Once it has been activated and started, the FRP
Dispatcher is always active. The Controller and the Event Handler support the FRP Dispatcher in its function. Depending on your
settings in the start pro le, the FRP Dispatcher starts the F&R Processor. The system repeats the following process steps
according to the settings you have made in the start pro les:
1. The FRP Dispatcher checks whether a change of day (planning day per location) has been produced by the settings in the
process control pro le. If a change of day has taken place, the system reconstructs the worklist for the FRP Dispatcher.
2. The FRP Dispatcher checks whether there is a location in the worklist for which it is to start replenishment planning. If
system resources are available for processing (depending on the system resources and the settings in administration for
location data), the F&R Processor starts for this location.
3. The Controller always checks whether the FRP Dispatcher is active. If it is inactive, the Controller restarts it.
4. The Event Handler checks whether there is any new consumption data for the F&R Processor and forwards the
information for each location to the FRP Dispatcher.
To check the result of the F&R Processor, on the SAP Easy Access screen choose:
Forecasting and Replenishment Forecasting and Replenishment Processor Check Location Status .
Result
The F&R Processor produces order proposals and new time series values.
Dispatcher Pro le
Use
The FRP Dispatcher is a function for automating the start of the forecast and requirement calculation and adjusting it to suit
your business processes. In the dispatcher pro le, you de ne the order of the process steps (sequences and tasks) within the
F&R Processor.
Integration
You use the dispatcher pro le and the start pro le to control the F&R Processor.
Prerequisites
You have de ned the sequence of process steps in Customizing for Forecasting and Replenishment under Forecasting and
Replenishment Processor Maintain Dispatcher Pro les .
 Note
SAP provides a standard pro le. To get error-free results from the F&R Processor, you have to follow the speci ed sequences
and you must not delete any sequences or tasks.
You have assigned the dispatcher pro le to a location in the Forecasting and Replenishment Processor application under
Administration.
Start Pro le
Use
7/31/2021
In the start pro le, you de ne the time parameters at which the F&R Processor (or individual sequences of the F&R Processor)
is to start automatically.
Integration
You use the dispatcher pro le and the start pro le to control the F&R Processor.
Prerequisites
You have de ned the time parameters in Customizing for Forecasting and Replenishment, under Forecasting and
Replenishment Processor Maintain FRP Start Pro les and assigned the start pro le to the dispatcher pro le under Maintain
Dispatcher Pro les.
You have assigned the start pro le to a location in the Forecasting and Replenishment application under Forecasting and
Replenishment Processor Administration . Note the following:
To process all the sequences of a location in order, choose execution level P (Pro le) in Administration.
To assign different start times to individual sequences, choose execution level S (Sequence) in Administration. You must
also assign a start pro le to the sequence in the relevant Dispatcher pro le.
Activities
In the start pro le, you de ne the time between the beginning and the end of the planning day that is de ned in the process
control pro le at which location processing is to start. You do this for each planning day. That means you de ne the day of
execution for each planning day (from the process control pro le) and the earliest and latest start time at which the system is
to execute this sequence in the start pro le.
 Note
If you set the Consumption Update Required indicator in the start pro le, the F&R Processor cannot start until the
consumption data has been transferred.
 Example
You set the FRP Dispatcher to start between 2 a.m. and 4 a.m.
If you also set the Consumption Update Required indicator, the following occurs:
The consumption data is available at 3:45 a.m. This means that the F&R Processor starts for the location in
question at 3:45 a.m.
The consumption data is available at 5 a.m. This means that the F&R Processor starts for the location in
question at 4 a.m.
If you do not set the Consumption Update Required indicator, the F&R Processor always starts at 2 a.m. for the
location in question.
Exception Management
Use
7/31/2021
You use exception management with the Exception Workbench to allow different users (for example, a replenishment planner or
a system administrator) to access F&R exceptions.
The system creates exceptions automatically in different business processes. It assigns these exceptions to objects (for
example, locations, products, and order proposals) in the corresponding business areas (for example, forecast, replenishment).
Users may be interested in exceptions from different sources. For this reason, each user can subscribe to different business
areas, allowing them to access the exceptions in these areas. You can also select exceptions on the selection screen in the
Exception Workbench on the basis of business criteria (for example, business objects) and technical attributes (for example,
priority and creation date).
Features
Exception Workbench
In exception management, the system processes exceptions from different business areas, stores, and products. The Exception
Workbench is the central tool here. For more details, see Exception Workbench.
Aside from the Exception Workbench, you can also review and con rm the relevant exceptions in the following applications:
Product Workbench: Exceptions for the selected location product
For more information, see Exceptions.
Replenishment Workbench: Exceptions for order proposal and order proposal items
For more information, see Exceptions.
DIF Workbench: Exceptions for the selected objects in DIF occurrences
Interface Workbench: Exceptions for data in inbound and outbound interfaces
Customer-speci c replacement messages
You can de ne your own texts for the F&R exception messages in the system.
1. You de ne the following objects in the message maintenance transaction (transaction code SE91):
A custom message class
A custom message number
The alternative text
 Recommendation
We recommend copying the original parameters (such as the location number or location product number) of a
standard message, as you may lose important information otherwise.
2. Assign the alternative text to the original message in Customizing, under Forecasting and Replenishment Exception
Management Assign Customer Speci c Replacement Messages .
If an alternative message text has been created and assigned, SAP F&R replaces the standard text with the replacement text
when the corresponding message is displayed. Note that the actual data storage of the exceptions remains unaffected.
More Information
F&R Exceptions
7/31/2021
Alert Monitor

Sap Forecasting and Replenishment Sap Fampr Warning Compress

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sap Forecasting and Replenishment Sap Fampr Warning Compress

Uploaded by

Copyright:

Available Formats

7/31/2021

SAP Forecasting and Replenishment (SAP

SAP Supply Chain Management (SAP SCM) | 7.0

Original content: https://help.sap.com/viewer/39cdf8557a584dccbd9778782066bc73/7.0/en-US

For more information, please visit the https://help.sap.com/viewer/disclaimer.

SAP Forecasting and Replenishment (SAP F&R)

Cuts surplus stock in distribution centers and stores

Reduces stockouts in distribution centers and stores

Increase transparency in the supply chain through eﬀective analyses

Receipt of new and modi ed master data

Receipt of shelf data from a space management system

Receipt of sales data and updated historical sales data

Receipt of data for planned promotions (demand in uencing factors)

Receipt of stock data

Receipt of manually created, created, or deleted order data

Supply chain execution

Receipt of store orders and store forecasts

Procurement cycle (pro le)

Master Data Objects Interface Individual Processing Mass Processing

Product x none none

Location product x none Modi able and time-dependent

Product hierarchy x x none

Master Data Objects Interface Individual Processing Mass Processing

Location group x x none

Reference module x x none

Supply network: transportation x none Modi able and time-dependent

Supply network: transportation x none Modi able and time-dependent

Calendar none x none

Procurement Cycle (Pro le) x x none

Purchasing organization x none none

Purchasing organization x none none

Contract x none none

Layout x none none

Unit of measure group x x none

Release pro le x x none

Rounding pro le x x none

Certain pro les, such as the restriction pro le

Inbound Master Data

Mass Processing of Master Data

You can use product hierarchies to de ne product hierarchy-dependent location groups.

Settings for Hierarchy Structure and at Client Level

Product Type Identi cation for Inbound Products

Blank = Real product

2 = Merchandise category hierarchy node

3 = Regular product hierarchy node

The following standard location types are relevant in SAP F&R :

Product hierarchy dependent location groups

You do not have to create a hierarchy structure in Customizing in this case.

DIF dependent location groups ( DIF location groups)

Con guring Modi able and Time-Dependent Parameters

Master Data De ne Time-Dependent Fields

Deletion of Location Products

Open order proposals

Transportation lanes for products

Stock data in the Logistics Inventory Management Engine (LIME)

Entries in interface tables for the BI System

Interface tables (DIF) for location products

Extraction data for a linked BI system

Order proposal items with following types:

Items to not transfer to the SAP Retail system

Goods receipt calendar

De nes the days on which a goods receipt is possible for a location.

Goods issue calendar

Maintaining and Assigning Calendars