Académique Documents
Professionnel Documents
Culture Documents
http://scn.sap.com/docs/DOC-50032
:Introduction
Strategy '10' is one of the frequently used and frequently discussed MTS
strategies. In this document we try to explore this strategy with the
.relevant configuration setttings
Strategy 10 is particularly useful for pure make-to-stock scenarios and
the sales requirements have no effect in the production. The production is
based on production plans transferred via demand program/ manually
entered PIRs. Strategy 10 is also referred as Net Requirements Planning
:and few important features of this strategy are
.Sales Order requirements do not affect the production
No concept of PIR consumption through customer requirements, since
.customer requirement is not relevant for pure make-to-stock production
.PIR reduction happens with PGIs for Sales Order delivery
.It is often used in make-to-stock REM
Strategy Group 10 and a suitable availability check group without RLT (in
:standard, availability check group 02)
When working with multiple BOMs and production version wise BOM
selection, use the menu function Settings -> Production Version in the
schedule line tab in MD61/ MD62 to enable the production version column,
.so that you can define PIRs according to the production versions
The system finds requirement type as LSF derived from the configuration
of the strategy 10. It is defined in OPPS transaction (for a reference of
assignment of Requirement Types to the planning strategies, take a dump
from T461S table). Check the entry for requirement types for independent
requirements in OPPS configuration for strategy 10. Since
stock/requirements list or MD04 is a dynamic report, we should be able to
.see the PIRs entered (here in MD61) in MD04
We run MRP, get the procurement proposals from MRP (in this example
planned orders), and convert them to production orders (in case of REM,
the production is based on planned orders and the planned orders are nonconvertible), and produce against the production orders and do the PGI
.against SO delivery
After running MRP, system generates planned orders to cater the
requirements; lot size plays an important factor for the planned receipt
.quantities
In this example, I have converted the first planned order (you can perform
.partial conversion) fully
Now we post confirmation for the production order (for simplicity, we have
activated auto GR through control key PP03 in routing of the FERT and
auto GI through backflush indicator of the ROH material master backflush
.indicator in MRP2 view), and get the stock of the FERT
:Sales Order
.We now create a sales order of 30 pieces in VA01 transaction
In the procurement tab, we find the Requirement Type as KSL and
Schedule line category as CP in standard system. The system finds the
.item category as TAN in standard system
These are derived from the settings for planning strategy OPPS, and from
the configurations in SD. As discussed earlier, the requirement type for
customer requirements is defined as KSL for strategy 10 in OPPS (table
.T461S)
The schedule line category and the item category are derived as discussed
here. In SPRO -> Sales and Distribution -> Sales -> Sales Documents ->
Sales Document Item -> Assign Item Categories (SM30 transaction view
V_T184), we define that based on the Sales Document type and item
category group the value for the item category. The SD document type
that I chose in this example is ZDSE, and the item category group in
.Sales Organization view of the material master we have selected NORM
In SPRO -> Sales and Distribution -> Sales -> Sales Documents
->Schedule Lines -> Assign Schedule Line Categories (SM30 transaction
view V_TVEPZ), it is defined that the proposed schedule line category for
:item category TAN and MRP Type PD combination will be CP
We save the sales order and check the stock/requirements list. The sales
.order is displayed, but it does not affect the available quantity
Technically speaking, this depends on the value of VBBE NODIS (No MRP)
field value for the sales order, line item and schedule line combination. For
.requirement type KSL, in standard it is 1
The reason the PIR is not reduced is that the PIR lays in future 11.12.2013
than the PGI for delivery 08.12.2013 and we do not have any forward
consumption period maintained in material master. As per OSS note
772857 Question # 3, the reduction occurs in the time scale up to the
current date and the oldest planned independent requirements are
reduced first. By maintaining the consumption period forwards, planned
independent requirements are used for the reduction from the current
date up to the number of days in the future entered there. The used
consumption mode is not effective. It is recommended to go through OSS
.note 38687
:References
SAP Help - Demand Management: Net Requirements Planning (10) Demand Management (PP-MP-DEM) - SAP Library
OSS notes: 772857, 38687
,Best Regards
Rajen
Views Tagsnone (add) Tasks: planning Tags: mrp, availability_check, 10596
md04, production, pir_reduction, pir_consumption, pir, mts, md61,
requirement_class, strategy_10, net_requirements_planning,
make_to_stock, requirement_types
Average User Rating
4.6
(ratings 5)
inShare0
Tweet
Comments
Comments 8
.Keep Sharing
,Thanks
Anupam Sharma
Like (0)
I would like to know the difference between the strategy 10 and 11 and
where they are used in practical purpose what is mixed mrp indicator
.purpose in strategy 11
Regards
Kalyan
Like (0)
.Thanks in advance
,Regards
Anuj
Like (0)
Thanks
Like (0)
Top of Form
Name
Email Address
Website Address
Add Comment
Bottom of Form
Top of Form
Name (Required)
Website Address
Save
Bottom of Form
Top of Form
[placeholder]
document.delete.DOC-50032
Bottom of Form
Delete Document
?Are you sure you want to delete this document
Cancel
Delete
Actions
.Login to follow, like, comment, share and bookmark content
Login Register
Incoming Links
Re: PIR LSF Reduction
!...Re: Planned Order not Generated
Re: MTO- Production Strategy-10 Setting to Reduce PIR , as soon as Goods
Issue Happens
Useful documents on SCN
Re: Deduct Sales from PIR's - Mid Month MRP
Re: new user of PP module
Follow SCN
Site Index
Contact Us
SAP Help Portal
Privacy
Terms of Use
Legal Disclosure
Copyright
Jive Software Version: 5.0.6.2 , revision:
201308121150.54f5b14.release_5_0_6_2