Hierarchy

⤷

⤷

IMG Activity
ID | SIMG_CFMENUOLMDOMDG | Define Splitting of Forecast Requirements for MRP |
Transaction Code | S_ALR_87000663 | IMG Activity: SIMG_CFMENUOLMDOMDG |
Created on | 19981222 | |
Customizing Attributes | SIMG_CFMENUOLMDOMDG | Define Splitting of Forecast Requirements for MRP |
Customizing Activity | SIMG_CFMENUOPP1OMDG | Define Splitting of Forecast Requirements for MRP |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_CFMENUOLMDOMDG |
In this step, you define:
- the periodicity in which forecast requirements are taken into consideration and are split on the time axis in MRP
- for how many periods the forecast requirements are taken into consideration in the net requirements calculation
The splitting indicator is defined depending on the period indicator.
The period indicator defines the periodicity used to record the historical values for the forecast and the periodicity to be used to output the forecast values.
However, this periodicity may be too large for the planning run. Therefore, you can use the splitting indicator to,
- split monthly values into daily and weekly forecast requirements, and to
- split weekly forecast values into daily forecast forecast values.
In this step, you can also limit the number of forecast requirements for which the net requirements calculation is to be carried out.
To split the forecast requirements for a material, the splitting indicator defined here is assigned in the material master record.
Note
The splitting of the forecast requirements is only relevant for capying forecast values to MRP. It has no influence on the forecast execution.
Example
Month 1 2 3 4 5 6
Forecast values 100 100 100 100 100 100
The planning run should provide the following forecast values:
in the 1st month daily
2nd month weekly
3rd - 6th month is also taken into account
Here, you must set the following defaults in the system:
Number of days = 1
Number of weeks = 1
Periods = 4
The following forecast values result for material requirements planning:
Month 1: forecast requirements are created for every workday
Month 2: on the first workday of the week, a requirement of 25 is created
Month 3 to 6: on the first workday of the month, a requirement of 100 is created
Planned orders are not created for the entire planning horizon but only for 6 months.
Actions
Define the following in the field entitled, "No. of days":
- how many periods are to be calculated to the day in MRP
Define the following in the field entitled, "No. of weeks":
- how many periods are to be calculated 'to the week' in MRP
Define the following in the field entitled, "No. of periods":
- for how many periods - in addition to the periods to be split - is the system to carry out the net requirements calculation in the planning run.
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | SIMG_CFMENUOLMDOMDG | 0 | (HLA0006803 A HLA0006800) O HLA0001815 |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
V439P | V - View | SM30 | 02 | Splitting Forecast Requirements |
History
Last changed by/on | SAP | 19981222 |
SAP Release Created in |