Hi Prasad,
SNP2 tab has got 3 fields, demand profile, supply profile and deployment profile.
1) Demand Profile:-
a) Demand horizons :- These horizons enable you to define how the system calculates the total demand in three different time horizons: short-term, mid-term, and long-term.
In SNP customizing, you group categories into category groups and assign these categories to key figures. For example, you can specify the categories that contribute to the sales order key figure. You then map this assignment of categories to key figures for short-term, mid-term planning, and long-term planning.
u2022 Category group in customizing (first field): demand horizon 1 = short-term planning
u2022 Category group in customizing (second field): demand horizon 2 = mid-term planning
u2022 Category group in customizing (third field): everything beyond demand horizon 2 is considered long-term planning.
b) Forecast horizon:-Specify the number of days beginning when the transaction associated with this horizon is initiated out into the future to indicate when the forecast horizon is valid.
Within this horizon, SNP does not use the forecast to calculate total demand. Beyond this horizon, SNP calculates total demand as either the forecast or the sales orders (whichever is greater) plus the other demands (dependent and distributed demand, planned and firmed)
c) Pull deployment horizon:- Specify the number of days beginning when the transaction associated with this horizon is initiated out into the future to indicate when the pull deployment horizon is valid.
Within this horizon, SNP considers all inventory for deployment calculations. Only demand within this horizon is considered in the deployment calculation. Distribution begins on the first day for which requirements exist in the system and ends with the last day of the pull deployment horizon.
d) Period split:- Define how you want the system to disaggregate planning data by time when you release the demand plan from Demand Planning to SNP.
Choose one of the following options:
u2022 BlankThe data is disaggregated to all of the workdays in the specified horizon.
u2022 1The data is disaggregated to all of the workdays in the specified horizon, but released only for those days that fall in the present and future.
u2022 2The data is disaggregated to the workdays in the present and future and released for the same days.
2) Supply profile:-
a) Supply horizon:- These horizons enable you to define how the system calculates the total supply in three different time horizons: short-term, mid-term, and long-term.
In SNP customizing, you group categories into category groups and assign these categories to key figures. For example, you can specify the categories that contribute to the distribution receipts key figure. You then map this assignment of categories to key figures for both short- and a mid-term planning:
u2022 Category group in customizing (first field): supply horizon 1 = short-term planning
u2022 Category group in customizing (second field): supply horizon 2 = mid-term planning
u2022 Category group in customizing (third field): everything beyond supply horizon 2 is considered long-term planning.
b) Production horizon :- Specify the number of days beginning when the transaction associated with this horizon is initiated out into the future to indicate when the production horizon is valid.
Within this horizon, SNP does not plan production.
c) Stock transfer horizon:- Specify the number of days beginning when the transaction associated with this horizon is initiated out into the future to indicate when the stock transfer horizon is valid.
Within this horizon, SNP does not plan shipments.
d) Push deployment horizon:- Specify the number of days beginning when the transaction associated with this horizon is initiated out into the future to indicate when the push deployment horizon is valid.
Within this horizon, SNP considers all inventory for deployment calculations.
3) Deployment profile:-
a) Fair share rules:-If demand exceeds supply, SNP uses fair share logic to calculate deployment based on the available to deploy (ATD) quantity, the open sales orders, the safety stock, and the forecast. You specify a fair share rule in the product master data to identify how you want the fair share logic to be implemented:
u2022 The objective of fair share rule A is to distribute the stock proportionally to all distribution centers (DCs) according to demand.
u2022 The objective of fair share rule B is to raise the stock levels in all DCs to approximately the same percentage of target stock level.
u2022 The objective of fair share rule C is to distribute the stock according to priority of the demand at the DCs.
b) Push rules :- SNP uses push logic to calculate deployment when the available to deploy (ATD) quantity can adequately cover the demand within the system You specify a push rule in the product master data to identify how you want the push logic to be implemented:
u2022 With pull distribution (leave the field blank), all demand within the pull deployment horizon is met through deployment. Distribution occurs according to the due date specified at the DCs.
u2022 With pull/push distribution (enter P in the field), all the demand within the pull deplyment horizon is met through deployment immeditately, without regard to the requirement dates specified by the DCs.
u2022 With push distribution (enter X in the field), all the requirements defined in the system are met through deployment immediately
Regards
R. Senthil Mareeswaran.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.