<?xml version="1.0" encoding="UTF-8" standalone="no"?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:gd="http://schemas.google.com/g/2005" xmlns:georss="http://www.georss.org/georss" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:thr="http://purl.org/syndication/thread/1.0" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-542925238086454287</atom:id><lastBuildDate>Tue, 24 Mar 2026 07:56:32 +0000</lastBuildDate><category>MM Ques and Ans</category><category>SAP MM Purchasing</category><category>SAP MM Material Master</category><category>SAP PP MRP</category><category>SAP MM Archiving</category><category>MM Inventory Management</category><category>Foreign Trade Data</category><category>SAP PM Order</category><category>Employee Trip</category><category>FICO Interview Questions</category><category>PM Questions and Answers</category><category>SAP PP BOM</category><category>PP Interview Questions</category><category>ASAP</category><category>SAP MM Vendors</category><category>SAP PP Production Order</category><category>Logistics Information System</category><category>SAP IMG Configuration</category><category>Accounting</category><category>FICO Financial Modules TC</category><category>FICO Periods</category><category>SAP PM Master</category><category>SAP MM Certification Exam</category><category>SAP MM Tcodes</category><category>SAP PP Goods Movement</category><category>Trip Status</category><category>FICO Account Posting</category><category>Logistics Invoice Verification</category><category>SAP PM Inventory Posting</category><category>SAP PP ABAP Reports</category><category>Certification</category><category>Commodity Codes</category><category>MM Configuration</category><category>PP Message / System Status</category><category>Tables SAP MM</category><category>FICO Tables</category><category>SAP MM Purchase Requisitions</category><category>SAP Output/Email</category><category>SAP PP Planned Order</category><category>Trip Entry Scenario</category><category>Trip Schema</category><category>SAP MM Workflow</category><category>SAP PM TCodes</category><category>ABAP</category><category>Free Downloads</category><category>HR FAQs</category><category>MM UserExits</category><category>SAP MM IDocs</category><category>SAP PM Tables</category><title>SAP Software Knowledge</title><description>SAP,ABAP PROGRAMMING,Reports,Bdc,SAP Scripts,Smart Forms,Module pool,ALV Interactive, Classic reports,ALE,EDI,Work Flow,User Exits,Customer Exits,BADI,BAPI</description><link>http://sapsoftwareknowledge.blogspot.com/</link><managingEditor>noreply@blogger.com (Technical Data)</managingEditor><generator>Blogger</generator><openSearch:totalResults>413</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><language>en-us</language><itunes:explicit>no</itunes:explicit><itunes:keywords>SAP,ABAP,PROGRAMMING,Reports,Bdc,SAP,Scripts,Smart,Forms,Module,pool,ALV,Interactive,Classic,reports,ALE,EDI,Work,Flow,User,Exits,Customer,Exits,BADI,BAPI</itunes:keywords><itunes:summary>SAP,ABAP PROGRAMMING,Reports,Bdc,SAP Scripts,Smart Forms,Module pool,ALV Interactive, Classic reports,ALE,EDI,Work Flow,User Exits,Customer Exits,BADI,BAPI</itunes:summary><itunes:subtitle>SAP Software Knowledge</itunes:subtitle><itunes:category text="Technology"><itunes:category text="Software How-To"/></itunes:category><itunes:owner><itunes:email>prakashkdv509@gmail.com</itunes:email></itunes:owner><xhtml:meta content="noindex" name="robots" xmlns:xhtml="http://www.w3.org/1999/xhtml"/><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-1321507334534725507</guid><pubDate>Fri, 09 Oct 2009 10:31:00 +0000</pubDate><atom:updated>2009-10-09T16:01:58.969+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP Production Order</category><title>Production Order Production Setup Time</title><description>&lt;p&gt;&lt;b&gt;My client has a production setup where there is a particular activity which has a setup time of 8 hrs when it is executed for the first time, but if another production order is taken up for the same material then the set up rime is zero. That is if I produce a material x at a particular work center the for the first time the set up time is 8 hrs, but if another production order of same material x is executed right after this order then the setup time is zero. Now, if we give the setup time as 8 hrs in routing then the system will calculate total time taking 8 hrs as setup time each time. Is there any way in which the system takes the setup time as zero when a production order for a particular material as repeated.&lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;&lt;span style="color: rgb(153, 0, 0);"&gt;Soumyadipta&lt;/span&gt;&lt;/b&gt; &lt;/p&gt;&lt;p&gt;Take a look at the functionality associated with the set up group and transition matrix, if I remember rightly though the setup times are only adjusted after production orders have been despatched in the planning table as this is the first time SAP is aware of the sequence of manufacture &lt;/p&gt;&lt;p&gt;&lt;b&gt;&lt;span style="color: rgb(153, 0, 0);"&gt;Paul&lt;/span&gt;&lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;If I am not wrong, setup matrix and transition matrix can be made use of when you go from one operation to the other in a particular routing. But, here there is only 1 operation in the routing and that operation is being repeated for different production orders of the same material. Can this different setup times be given for this same operation. &lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;&lt;span style="color: rgb(153, 0, 0);"&gt;Soumyadipta&lt;/span&gt;&lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;If I remember if setup group key is defined in the operation in the routing and then the transition times between setup keys is maintained in configuration.&lt;/span&gt; &lt;/p&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;So it's possible to create something like the following:&lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt; &lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;From Key 1 To Key 1        30 mins      &lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;From Key 1 To Key 2        8 hours  &lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt; &lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;So different the operations in orders for the same material should both have the same key and should have a setup time on 30 mins between them.&lt;/span&gt; &lt;/p&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;Then when a different material with a different setup key comes along in the manufacturing sequence it will pick up an 8 hour setup time&lt;/span&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;&lt;span style="color: rgb(153, 0, 0);"&gt;Paul&lt;/span&gt;&lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;I am facing a much similar problem. We have 15 work stations and daily 50 - 60 production orders are printed. I am maintaining production time as well as set up time in the routings ( There exists a separate routing for all the part no's ). When a production order is printed it copies the setup time from routings. Suppose in one work station there happens has to be 2 production orders processed one by one then the setup is only once. but due to the fact that setup is present in the routings the production order shows a non-conformity of setup time for the 2nd production order. How to solve this problem.&lt;/span&gt;&lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;&lt;span style="color: rgb(153, 0, 0);"&gt;Narendra S&lt;/span&gt;&lt;/b&gt; &lt;/p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;We have a similar situation in the company I work for, we don't actually maintain routings at material level but use reference operation sets at an aggregate level to represent the different production footprints (the link to each material is then made through the production version in the material master). &lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt; &lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;We measure the actual setup time confirmed in each order belonging to each footprint / family over a rolling three month period and maintain an average setup time in the reference operation set. This gets copied to each production order, but is only to make sure that a time allowance is left in each production week for set up to create meaningful capacity planning data.&lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt; &lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;When the planners develop the manufacturing schedule using the graphical planning table they then update the setup time in each order automatically with the setup times maintained in the transition matrix so it's more accurate, as it takes account of the order being made on the workcentre previously. So in our case two orders sharing the same footprint will have different setup times.&lt;/span&gt;</description><link>http://sapsoftwareknowledge.blogspot.com/2009/10/production-order-production-setup-time.html</link><thr:total>8</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-7545384138501135897</guid><pubDate>Fri, 09 Oct 2009 10:31:00 +0000</pubDate><atom:updated>2009-10-09T16:01:29.653+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP Production Order</category><title>Production Order Material Stock in Production Order</title><description>&lt;p&gt;&lt;b&gt;I have the problem in stock against production order:&lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;Our scenario is we don’t want to create a sales order. I create a production order that has 5 operations. The first operation is sub contracting. Through control key (External operation) I create the purchase requisition and convert purchase order in that operation. Through the PO I can issue the ROH and received HALB. When I received the HALB the stock of ROH is automatically reduced. But HALB stock doesn’t increase. In this case where is my HALB material for second operation? &lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;In this case how to proceed? &lt;/b&gt; &lt;/p&gt;&lt;p&gt;Do you have a material code for HALB? if you have material code than you can have stock increased. I think there's some mistake with the process. the subcontracting in operation is only for the operation, not the material. &lt;/p&gt;&lt;p&gt;In your configuration, you subcontract the first operation of the FERT production. and there's no stock increase of FERT or HALB when the first operation is completed (confirmation by purchase order...) &lt;/p&gt;&lt;p&gt;And what you want could be possible like this:  &lt;/p&gt;&lt;p&gt;You create the HALB material code, and you make it external procurement (F in standard) and with special procurement key subcontracting (30 in standard) (enter these fields in material master mrp2 view). Then you can create purchase order for the HALB material when needed, and send ROH material to the subcontractor for the purchase order and post goods receipt for HALB material and stock increases. And accordingly, since the production of HALB is a different process, not a sub process of FERT material, you should change the routing of FERT material to 4 operations, omitting the first operation, which is subcontracted production of HALB. And you should also change the BOM of the FERT material, and remove the ROH (which is used for producing HALB) and put the HALB material itself.&lt;/p&gt;</description><link>http://sapsoftwareknowledge.blogspot.com/2009/10/production-order-material-stock-in.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-2950793644945383040</guid><pubDate>Fri, 09 Oct 2009 10:30:00 +0000</pubDate><atom:updated>2009-10-09T16:01:03.800+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP Production Order</category><title>Production Order Automatic Conversion to Production Orders</title><description>&lt;p&gt;&lt;b&gt;Is there anyone out there who knows if it is possible to make an automatic change of planned orders to production orders right away - or perhaps even to skip the planned orders and create pp - orders instead? &lt;/b&gt;&lt;br /&gt;&lt;b&gt;I have a customer who want to do this (skip the manual conversion).&lt;/b&gt;&lt;br /&gt;&lt;b&gt;Perhaps it is impossible? &lt;/b&gt; &lt;/p&gt;&lt;p&gt;To create production orders in MRP run without checking first the order proposals (planned orders) is not a recommended process at all. It is against the accepted norms in production/inventory management and its MRP-2 logic on which SAP software is also based on. &lt;/p&gt;&lt;p&gt;If you have complex production - you'd have a nightmare closing all the production orders with the errors not resolved at the prior to conversion stage. On the other hand, if it is too simple production with only a handful of operations and no strict requirement of production control (which seems to be your case, for me), then please do away with production orders, and use the repetitive manufacturing where planned orders are the final. &lt;/p&gt;&lt;p&gt;I am confident that a consultant who can see the need and benefit for the wisdom of planned order conversion as a separate manual process, should ALWAYS be able to convince customer. &lt;/p&gt;&lt;p&gt;As always, the question is, whether you want the right shoe to fit the foot, or cut the foot to fit the shoe.&lt;/p&gt;</description><link>http://sapsoftwareknowledge.blogspot.com/2009/10/production-order-automatic-conversion.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-3358475311736985655</guid><pubDate>Fri, 09 Oct 2009 10:30:00 +0000</pubDate><atom:updated>2009-10-09T16:00:35.465+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP Production Order</category><title>Production Order Regarding Production Order Confirmation</title><description>&lt;p&gt;&lt;b&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;Production order confirmation with future date is not allowed&lt;/span&gt;&lt;/b&gt; &lt;/p&gt;&lt;p&gt;Future dates can be configured in the confirmation configuration.  &lt;/p&gt;&lt;p&gt;In configuration &lt;b&gt;&lt;span style="color: rgb(204, 102, 0);"&gt;OPK4&lt;/span&gt;&lt;/b&gt;, define confirmation parameters.  &lt;/p&gt;&lt;p&gt;When this configuration comes up, in the "&lt;b&gt;&lt;span style="color: rgb(204, 51, 204);"&gt;Checks&lt;/span&gt;&lt;/b&gt;" Sections, the last parameter says  &lt;/p&gt;&lt;p&gt;"&lt;b&gt;&lt;span style="color: rgb(204, 51, 204);"&gt;Date in the future&lt;/span&gt;&lt;/b&gt;."  &lt;/p&gt;&lt;p&gt;Check this box if you want your dates in the future.  &lt;/p&gt;&lt;p&gt;It determines whether dates in the future can be used in a confirmation. &lt;/p&gt;&lt;p&gt;If the indicator is not set, you cannot make any confirmations using dates in the future.  &lt;/p&gt;&lt;p&gt;If you try to do so, the system will issues an error message. &lt;/p&gt;&lt;p&gt;&lt;b&gt;What is the importance of Production Order confirmation? Is there any specification to use type of confirmation ie., CO11 or CO15 or CO11N ? &lt;/b&gt; &lt;/p&gt;&lt;p&gt;A confirmation documents the processing status of orders, operations, suboperations and individual capacities.&lt;br /&gt;You can enter a confirmation&lt;br /&gt;- For an Opeartion (co11/co11n)&lt;br /&gt;You have the following options:&lt;br /&gt;- To confirm quantities, durations, activities or personnel data.&lt;br /&gt;- To make a confirmation at a particular point in time (for example, at the start of setup or the finish of processing) enter a&lt;br /&gt;confirmation.&lt;br /&gt;- When you confirm time events, the system calculates the required duration. For example, the setup duration is the time between setup start and setup finish.&lt;br /&gt;- For an Order : CO15&lt;br /&gt;If you enter a confirmation at order header level, the system confirms all the operations that have a control key in which&lt;br /&gt;confirmation is optional or necessary. The quantitiesconfirmed in the operations are proportional to the quantities confirmed in the order header. &lt;b&gt;&lt;span style="color: rgb(102, 102, 0);"&gt;*--   Rajesh&lt;/span&gt;&lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;I want to stop the confirmation of production order whenever there is no goods issue to the production order so that I can get the correct material accounting report. I can't set backfliush indicator to the material at Routing level because we are handling the raw material in batches, so I have to assign the batches to issue the raw material.( tcode CO27 ).&lt;/b&gt;&lt;br /&gt;&lt;b&gt;We have set the criteria to release the production order is only availability of raw material in plant, so system checks only the availability of raw material &amp;amp; releases the order. Is it possible after issuing the raw material the release of order took place?&lt;/b&gt; &lt;/p&gt;Goods issues before release of order is not possible in SAP.&lt;br /&gt;You can think of following things.&lt;br /&gt;1) In opj4,you can block release of order if it has missing parts.&lt;br /&gt;2) By using 'user exit' it is possible to disallow confirmation if goods issues are not posted against each component.</description><link>http://sapsoftwareknowledge.blogspot.com/2009/10/production-order-regarding-production.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-196126021322743054</guid><pubDate>Fri, 09 Oct 2009 10:29:00 +0000</pubDate><atom:updated>2009-10-09T16:00:08.425+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP Production Order</category><title>Production Order What is Backflushing?</title><description>&lt;p&gt;&lt;b&gt;Can anyone tell me what is backflushing for? When is it use? &lt;/b&gt; &lt;/p&gt;&lt;p&gt;Back flushing is nothing but automatic goods issue. System will automatically posts the goods issue when you confirm the operations.You have no need to make manual issue. It will reduce the effort. &lt;/p&gt;&lt;p&gt;Backflushing is automatic accounting (Goods issues - 261 mvt) of material consumed for production, at the time of confirmation. Eg. When a 4 wheeler automobile is rolled out from assy line, 4 wheels &amp;amp; Tyres are deemed to be consumed and issued to production order automatically by way of backflushing by the system. &lt;/p&gt;&lt;p&gt;Assy line picks the material from stores/ Assy line and use.  &lt;/p&gt;&lt;p&gt;No Physical issue &amp;amp; Manual posting ( Goods Issue) by Stores.  &lt;/p&gt;&lt;p&gt;Backflush is used for material which are a must and having fixed relationship. &lt;/p&gt;&lt;p&gt;This can be configured in MRP2 Screen,Work centre, Routing and production order.  &lt;/p&gt;&lt;p&gt;Each has some special function.  &lt;/p&gt;&lt;p&gt;If you configure this in routing or production order you have no need to activate this in MRP2 or Work center screen. &lt;/p&gt;&lt;p&gt;MRP2 Screen defines whether material components are backflushed are to be made at the work center.  &lt;/p&gt;&lt;p&gt;&lt;b&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;When we do the back flush the backlogs are being created for the BOM components and we are getting the message "Backlogs from backflush were created or changed" - its just an informative message. Do you think this has got something to do with the negative postings ?&lt;/span&gt;&lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;Backlogs are created due to different reasons.&lt;/span&gt; &lt;/p&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;This message tells that "there is no sufficient stocks for the bom component/not able to backflush all the material due to plant data locked etc" at the time of backflushing the BOM Material and hence the Post-processing list is created that you have to Re-process for stock updation of each material.&lt;/span&gt; &lt;/p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;To avoid this you can confirm the following things.&lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;1.Ensure that suffecicient stock is available in the backflushing locations of each materail.&lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;2.To prevent the generation of "post-processing list" you can block the BOM from getting backflushed if sufficient stock is not available in specified location for the BOM COMPONENTS. To do this change the "REM profile" to "002"in MRP4 view for the BOM MATERIAL.(if the profile is not available you can crate it through SPRO).&lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;3. To clear the existing Backlog use transcation MF47 and re-process(be ensure that required stocks is available for each bom component)&lt;/span&gt;</description><link>http://sapsoftwareknowledge.blogspot.com/2009/10/production-order-what-is-backflushing.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-7639486253181154641</guid><pubDate>Fri, 09 Oct 2009 10:29:00 +0000</pubDate><atom:updated>2009-10-09T15:59:41.784+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP Production Order</category><title>Production Order How Costing takes place in Production Orders</title><description>&lt;p&gt;&lt;b&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;Can anyone please explain me the how the Costing takes place for the Production Orders.&lt;/span&gt;&lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;Actually, I am new to this package , In Other Package (RAMCO ERP) &lt;/span&gt;&lt;/b&gt;&lt;br /&gt;&lt;b&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;(The Process is like follows: &lt;/span&gt;&lt;/b&gt;&lt;br /&gt;&lt;b&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;a. Production Work-Order Resource Cost Posts to Finance directly &lt;/span&gt;&lt;/b&gt;&lt;br /&gt;&lt;b&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;b. Material Consumption postings happens from OSV(Order Settlement Variance) of MAC Module(Management Accounting).&lt;/span&gt;&lt;/b&gt;&lt;br /&gt;&lt;b&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;  &lt;/span&gt;&lt;/b&gt;&lt;br /&gt;&lt;b&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;Please somebody explain me as above in SAP.&lt;/span&gt;&lt;/b&gt;&lt;br /&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;The following are considered in costing,&lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt; &lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;1) cost of materials that you have issued for order &lt;/span&gt; &lt;/p&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;2) activity you have performed in terms of labour hours that you entered while confirming the order (the rates for the labour are defined in the activity planning tables of controlling module)..which is generally associated with a formula key and attached to a workcenter that is linked to a cost center also &lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt; &lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;3) overhead as applicable with respect to that cost center based on a predetermined cost center planning and its rate...&lt;/span&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;&lt;span style="color: rgb(153, 0, 0);"&gt;Anil&lt;/span&gt;&lt;/b&gt;&lt;br /&gt;&lt;/p&gt;&lt;p&gt;&lt;b&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;&lt;span style="font-size: 78%;"&gt;Costing updation in production order&lt;/span&gt;&lt;/span&gt;&lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;How is costing updated for production order? &lt;/span&gt;&lt;/b&gt;&lt;br /&gt;&lt;b&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;After goods issue, conformation &amp;amp; GR, we do TECO. &lt;/span&gt;&lt;/b&gt;&lt;br /&gt;&lt;b&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;Before closing the order, costing details should be updated. Is it not? &lt;/span&gt;&lt;/b&gt;&lt;br /&gt;&lt;b&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;Could you please guide me as to how this is done? &lt;/span&gt;&lt;/b&gt;&lt;br /&gt;&lt;b&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;Also, what is the transaction code to be used? &lt;/span&gt;&lt;/b&gt;&lt;br /&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;Planned cost is caculated if you click 'cost calculation' in production order. GI go production order will update actual material cost. Confirmation of production order will update actual activity cost. You can settle cost once production order has status TECO or DLV. From PP side, the transction is CO02&lt;/span&gt;&lt;br /&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;In IMG we can define that when we calcu. the planned cost. &lt;/span&gt; &lt;/p&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;There are 3 ways. &lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;- Determine planned costs when saving, &lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;- Do not determine planned costs when saving,&lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;- Determine planned costs when saving if released. &lt;/span&gt; &lt;/p&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;But the actual cost is posted when we draw the material, when we confirm the order......We can use co02 and click the calcu. cost to update the cost in the prd order. &lt;/span&gt;&lt;br /&gt;&lt;/p&gt;&lt;p&gt;&lt;b&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;&lt;span style="font-size: 78%;"&gt;Error in Cost Calculation&lt;/span&gt;&lt;/span&gt;&lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;I am using 4.7. When I was saving my production order, there was this error message that told me that there was an error in cost calculation. Do you have any suggestions what I couldn't have done? What can I do to fix this? &lt;/span&gt;&lt;/b&gt;&lt;br /&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;Check the log file in the Production Order -&gt; Goto -&gt; Logs -&gt; For costing &lt;/span&gt; &lt;/p&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;Then take it from here....&lt;/span&gt; &lt;/p&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;Check whether the material for which you have created a production order has a price define in material master like Moving average price or Std price.&lt;/span&gt;&lt;/p&gt;</description><link>http://sapsoftwareknowledge.blogspot.com/2009/10/production-order-how-costing-takes.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-2372361740152293327</guid><pubDate>Fri, 09 Oct 2009 10:28:00 +0000</pubDate><atom:updated>2009-10-09T15:59:07.908+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP Production Order</category><title>Production Order SAP flow for REWORK activity</title><description>&lt;p&gt;&lt;b&gt;What is the SAP flow for REWORK activity in PP-PI.&lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;Sample Scenerio:&lt;/b&gt;&lt;br /&gt;&lt;b&gt;1. Initial Process Order qty: 10pc&lt;/b&gt;&lt;br /&gt;&lt;b&gt;2. Confirmed QTY.: 9 PCS.&lt;/b&gt;&lt;br /&gt;&lt;b&gt;3. Rejection qty .: 1 pc.&lt;/b&gt;&lt;br /&gt;&lt;b&gt;4. Now that one pc. is to be reworked in operation no.0020.&lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;How is it possible to understand later that, it is in this particular process order, so much of rework is carried out, and thats the reason the process cost has increased.&lt;/b&gt; &lt;/p&gt;&lt;p&gt;Rework during production depends on the client's decision. Like some companies want a separate process order to process this rejected quantity and some clients want to use the same process order, some even want to identify this rejected by assigning a new batch number. &lt;/p&gt;&lt;p&gt;But in some company, they do rework rarely but not as frequently as you do. &lt;/p&gt;&lt;p&gt;What they do is by inserting the new operation/phase after the actual operation/phase, and the operation quantity/base&lt;br /&gt;quantity, queue times, etc will be according to the users decision. in u r example down 1 pc will be the operation/phase quantity. &lt;/p&gt;&lt;p&gt;and one more thing is that remember to PCNF the 9 pc if you want to identify the 1 pc with the new batch. &lt;/p&gt;&lt;p&gt;&lt;b&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;With Compliments by:&lt;/span&gt; &lt;span style="color: rgb(153, 0, 0);"&gt;Sandeep&lt;/span&gt;&lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;Additional comments::&lt;/span&gt; &lt;/p&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;You also need to remember the product costing aspect.&lt;/span&gt; &lt;/p&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;The primary costs of material should not be repeated while doing the rework. so, the generally accepted trend is that you create a separate order type for it and a common recipe with a rework operation and the materials you can assign while creating the process order.&lt;/span&gt; &lt;/p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;Doing it in the same process order will have a problem of treacability of cost.&lt;/span&gt;</description><link>http://sapsoftwareknowledge.blogspot.com/2009/10/production-order-sap-flow-for-rework.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-8941599982938937594</guid><pubDate>Fri, 09 Oct 2009 10:28:00 +0000</pubDate><atom:updated>2009-10-09T15:58:42.422+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP Production Order</category><title>Production Order Serial Number For Component</title><description>&lt;p&gt;&lt;b&gt;I have a FG (A/C) which has a serial number. This A/c has a compressor in its BOM.&lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;The client requirement is to link the compressor to A/c using serial number. So, I maintain serial number profile for the compressor also. But when I do mfbf (backflush) for the A/c, the system asks only for the serial no. profile only for the A/c &amp;amp; not for the compressor. How do I link the two?&lt;/b&gt; &lt;/p&gt;&lt;p&gt;You can assign componenets (with serial nos.) to assembly ( also with serial nos.) with COIB after goods receipt.( Menu path --Logistics -&gt; Plant maintenance -&gt; Management of technical objects -&gt; Installed base -&gt; Create (special) -&gt; With reference to production data.) &lt;/p&gt;&lt;p&gt;Example: Say assembly sr. no. is 1&lt;br /&gt;And components serial no. are- 1,5,10,20 and so on. &lt;/p&gt;&lt;p&gt;After assignment of components it can be viewed on right part of screen, You can have the assignment history--- ie for which assembly no. which components are assigned or vice versa. In production order i.e in descrete mfg. it can be directly done at the time of operation confirmation. &lt;/p&gt;&lt;p&gt;The following is the detail steps:&lt;br /&gt;1. T code--COIB&lt;br /&gt;2. Enter material code ( Assembly). You can select specific serial no. of assembly --- by putting sr. no. in serial no. field.&lt;br /&gt;3. Click on list tree- you will find all assembly with serial numbers.&lt;br /&gt;4. Click on explode-- it will show the BOM ( in bottom left corner of screen)&lt;br /&gt;5. Select the assembly numbers for which you want to assign the componets&lt;br /&gt;6. Clik on tranfer&lt;br /&gt;7. Select the component&lt;br /&gt;8. Also select the assembly no. on right side screen.&lt;br /&gt;9. Select the serial no. which you want to assign to an assembly&lt;br /&gt;10. Click on assign&lt;br /&gt;11. You will find all the components will get assigned to assembly with serial numbers.&lt;br /&gt;12. Now on right side screen there is "save" button. ( It will ask you create/ change as built in foreground or background?&lt;br /&gt;13. Select as foreground&lt;br /&gt;14. Save&lt;br /&gt;15. You will find a message at the borttom --- saved.&lt;br /&gt;16. Now you will find tick mark ( in front of assembly material) in right part of screen ( indication of assignment of components)&lt;/p&gt;</description><link>http://sapsoftwareknowledge.blogspot.com/2009/10/production-order-serial-number-for.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-6894637329458956478</guid><pubDate>Fri, 09 Oct 2009 10:27:00 +0000</pubDate><atom:updated>2009-10-09T15:58:11.815+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP Production Order</category><title>How To Delete Old PP Production Orders</title><description>&lt;p&gt;&lt;b&gt;How to delete old production orders ( CO78 )?&lt;/b&gt; &lt;/p&gt;&lt;p&gt;Note that CO78 is the start of the Archive process. We are not using Archiving yet but the initial process fits the bill for what we need to do as mentioned in the original note. &lt;/p&gt;&lt;p&gt;Decide the range of orders you want to delete. This range will be used in the program variant. Note that we will be running CO78 many times because of the number of orders involved. &lt;/p&gt;&lt;p&gt;Running CO78 calls program PPARCHP1 and this involves the use of a Variant where the parameters for selection etc. are set.  &lt;/p&gt;&lt;p&gt;First of all, create the variant via SE38 for PPARCHP1.  &lt;/p&gt;&lt;p&gt;Enter details for number range, order type, plant and set deletion flag. Flag Detailed log and set this to go to Spool when running. Save the variant. You can also force the job to run in background at this point (which I would recommend) via menu line Variant --&gt; Attributes. Also here you can flag order number, order type and plant to be required fields. &lt;/p&gt;&lt;p&gt;For e.g.&lt;br /&gt;&lt;img src="http://sap-img.com/production/archiving-pp-order.jpg" alt="Archiving of Old Production Order" width="585" height="387" /&gt; &lt;/p&gt;&lt;p&gt;Run CO78&lt;br /&gt;Press the first button - deletion flag/deletion indicator. &lt;/p&gt;&lt;p&gt;Choose the variant you have just created. Press "Maintain" to update the selection range on subsequent runs. Save changes and return to initial screen. &lt;/p&gt;&lt;p&gt;Press Start date to set date and time for job to run as per any background job. Icon will turn Green. &lt;/p&gt;&lt;p&gt;Press Spool Params to set save output in Spool Q rather than print immediately. Icon will also turn Green. &lt;/p&gt;&lt;p&gt;Press Execute and job can be tracked via SM37. &lt;/p&gt;&lt;p&gt;Details of deleted orders and errors will appear in the Spool. &lt;/p&gt;&lt;p&gt;Rerun as many times as you need with relevant order ranges till all required orders are deleted.&lt;/p&gt;</description><link>http://sapsoftwareknowledge.blogspot.com/2009/10/how-to-delete-old-pp-production-orders.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-4305184207976955121</guid><pubDate>Fri, 09 Oct 2009 10:26:00 +0000</pubDate><atom:updated>2009-10-09T15:57:14.245+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP Planned Order</category><title>SAP PP How to “permanently” delete new planned orders?</title><description>&lt;p&gt;&lt;b&gt;Your company insists on fixing planned orders, to try to keep a stable, six-month plan. But you still get new planned orders generated in-between the fixed ones. You thought that you would get exception messages to pull in all the fix planned orders before new ones are generated. You need to “permanently” delete the new planned orders and leave only the fixed ones. &lt;/b&gt; &lt;/p&gt;&lt;p&gt;Two ideas which you can they apply to the scenario: &lt;/p&gt;&lt;p&gt;1) In OPPQ, exclude firm planned orders from rescheduling. This will add a rescheduling exception to the planned orders, and you could filter/report that way. &lt;/p&gt;&lt;p&gt;For example, if you discovered that the rescheduling horizon was only 100 days, you can made it 999. Now the fixed planned orders are all being rescheduled and no new planned orders are created “in between” the fixed ones. &lt;/p&gt;&lt;p&gt;2) Convert planned orders into production orders. Then you can look at production orders as your fixed plan, and ignore planned orders. &lt;/p&gt;&lt;p&gt;Deleting planned orders will be a short joy, as soon as you run MRP (assuming you do...) they will be recreated.&lt;/p&gt;</description><link>http://sapsoftwareknowledge.blogspot.com/2009/10/sap-pp-how-to-permanently-delete-new.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-2105442567046868239</guid><pubDate>Fri, 09 Oct 2009 10:26:00 +0000</pubDate><atom:updated>2009-10-09T15:56:47.370+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP Planned Order</category><title>SAP PP Planned Order Assign Multiple Planned Order to a Purchase Requisition</title><description>In order to assign multiple planned order to a single purchase requisition number, you need to make used of the external purchase requisition number range.&lt;br /&gt;&lt;br /&gt;Define your external purchase requisition number range in &lt;b&gt;&lt;span style="color: rgb(204, 102, 0);"&gt;OMDN.&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;/b&gt;Assign the external purchase requisition group number range to used in &lt;b&gt;&lt;span style="color: rgb(204, 102, 0);"&gt;OMI3.&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;/b&gt;Once the IMG settings are completed, you can used &lt;b&gt;&lt;span style="color: rgb(204, 102, 0);"&gt;MD15&lt;/span&gt;&lt;/b&gt; to assign the multiple planned order into a single purchase requisition number.&lt;br /&gt;&lt;br /&gt;In &lt;b&gt;&lt;span style="color: rgb(204, 102, 0);"&gt;MD15&lt;/span&gt;&lt;/b&gt;, select the planned order you want to convert to a purchase requisition.&lt;br /&gt;&lt;br /&gt;Next, click the &lt;b&gt;&lt;span style="color: rgb(153, 0, 0);"&gt;Convert Online&lt;/span&gt;&lt;/b&gt; button.&lt;br /&gt;&lt;br /&gt;SAP will display the planned order in change mode.&lt;br /&gt;&lt;br /&gt;Now, look for the &lt;b&gt;&lt;span style="color: rgb(153, 0, 0);"&gt;Purchase Requisition&lt;/span&gt;&lt;/b&gt; fields and supply the &lt;b&gt;&lt;span style="color: rgb(153, 0, 0);"&gt;Purchase requisition&lt;/span&gt;&lt;/b&gt; number.&lt;br /&gt;&lt;br /&gt;For example, assuming that you assign the external number range 2000001.&lt;br /&gt;&lt;br /&gt;In the planned order, you type the first number range 2000001 and item number 10 subsequently, copy and paste the number range but input the item number manually.&lt;br /&gt;&lt;br /&gt;It would be like   2000001   10 and save&lt;br /&gt;                        2000001   20 and save.....&lt;br /&gt;&lt;br /&gt;The disadvantages is that the user have to track and enter the external number range manually.&lt;br /&gt;Therefore, there is a trade off, between&lt;br /&gt;&lt;br /&gt;1.  having a single planned order for a single purchase requisition number or&lt;br /&gt;&lt;br /&gt;2.  having multiple planned order to a single purchase requisition number.</description><link>http://sapsoftwareknowledge.blogspot.com/2009/10/sap-pp-planned-order-assign-multiple.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-4732159952464933218</guid><pubDate>Fri, 09 Oct 2009 10:25:00 +0000</pubDate><atom:updated>2009-10-09T15:56:11.849+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP Planned Order</category><title>SAP PP Planned Order Conversion to Process Orders</title><description>&lt;p&gt;&lt;b&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;We are facing problems when converting planned orders to process orders. During conversion when BOM is re-exploded it is not using the same production version as specified in the planned order instead it defaults to the first one it sees. &lt;/span&gt;&lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;I need to know if I am missing any settings anywhere..... &lt;/span&gt;&lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;First ensure that setting in the material master for BOM explosion is "Selection thru prod version".&lt;/span&gt; &lt;/p&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;Then Pls check the validity periods of the new production version.&lt;/span&gt; &lt;/p&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;e.g&lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;Prod Ver Val frm     val to     No lot size variation&lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;0001     01.01.2007  31.12.9999&lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;0002     01.01.2007  31.01.2007&lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;or&lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;0001     01.01.2007  31.12.9999&lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;0002     01.01.2007  31.12.2007&lt;/span&gt; &lt;/p&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;Then in both the cases system will always pick prod ver 0001 default (Longer validity period).  If not the case then &lt;/span&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;Check for lot size variation (if lot size dependent.)&lt;/span&gt; &lt;/p&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;Further if you are not able to select the req prod Ver then you can lock the earlier prod version(if it is not in use). &lt;/span&gt; &lt;/p&gt;&lt;p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;To avoid this prob in future.... always use "Valid to date" either in limits (31.12.2007) or without limit (31.12.9999) for all prod version of a material.&lt;/span&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;When we have to go for Planned order conversion to Process order, it is used in manufacturing industry or process industry, when exactly we use process orders?&lt;/span&gt;&lt;/b&gt; &lt;/p&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;It is used for process industries.&lt;/span&gt;</description><link>http://sapsoftwareknowledge.blogspot.com/2009/10/sap-pp-planned-order-conversion-to.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-2976779765634734450</guid><pubDate>Fri, 09 Oct 2009 10:24:00 +0000</pubDate><atom:updated>2009-10-09T15:55:18.411+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP MRP</category><title>PP MRP Why used Planning tools like APO or I2?</title><description>&lt;p&gt;APO and I2 are Finite PLANNING tools. When MRP runs with APO or I2 (or Red Pepper or Manugistics), it takes Capacity issues into consideration. MRP in SAP R/3 Core does not, it assumes infinite capacity available. (MRP only looks at material availablity.) &lt;/p&gt;&lt;p&gt;However, SAP R/3 DOES do finite SCHEDULING, which is where the system 'dispatches" operations on a production order until it fills up the capacity available, then moves to the next time period and dispatches until that period is filled up. In SAP speak, that is called capacity leveling. &lt;/p&gt;&lt;p&gt;I believe APO should only be used in very large companies (billions) because of the amount of master data that must be maintained, and that data better be ACURATE, or you've wasted a heck of a lot of time. By the way, APO stands for Advanced Planner and Optimizer tool, obviously a German sort of name!&lt;br /&gt;&lt;/p&gt;&lt;p&gt;&lt;b&gt;Differences between planning and scheduling, finite and infinite&lt;/b&gt; &lt;/p&gt;&lt;p&gt;R/3 does planning without consideration for capacity situations. So if MRP says you need 500 parts on 3/1/04, it schedules them all to be built at the same time, even though you can only do 100 at a time. Assume you have a fixed lot size of 100, you'll get 5 planned orders for 100 to start on the same day. This is "Infinite Planning". APO would recognize that constraint, and instead schedule out the 5 orders over time. The important part of that is that it also will schedule out the deliveries of the components for 5 different days. This is "Finite Planning". &lt;/p&gt;&lt;p&gt;Now, assume old fashion MRP. It schedules all 5 orders for the same day, and the buyers go out an get all of the components for the same day. Then the planner realizes he can't do all 5, and manually changes the schedule, and manually spreads out the 5 orders. The buyers will recieve rescheduling notifications, but not until the scheduler does the manual rescheduling. You could call this "Infinite Scheduling", but that only means the same thing as Infinite Planning. &lt;/p&gt;&lt;p&gt;But, SAP has "Capacity Leveling". What that means is you run another program after MRP (CM27 and CM28), which can be run in batch mode overnight. (There is a ton of configuration and thinking that will be required to do this!). The capacity leveling program will recognize the constrant at the work center level, and fill up the first day, then re-schedule the next order to the next available capacity, then the next order searches for available capacity, and so on. This is called "Finite Scheduling". The problem with this is the opposite of Infinite Planning, which is it doesn't take Material availablity into consideration! The system will re-schedule a production order without thinking about whether the materials will be available or not. &lt;/p&gt;&lt;p&gt;Finite Planning does Finite Sheduling at the same time. If there is no capacity available on the desired date, the system looks for when capacity IS available. Then it stops to see if Materials will also be available (usually based on the lead-time for those components). If there is a material problem, then the system figures out when the materials WILL be available, and then&lt;br /&gt;checks to see if capacity is available on THAT day, and if so, it blocks off capacity, and allocates the materials for that day.&lt;/p&gt;</description><link>http://sapsoftwareknowledge.blogspot.com/2009/10/pp-mrp-why-used-planning-tools-like-apo.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-9169889290947946616</guid><pubDate>Fri, 09 Oct 2009 10:24:00 +0000</pubDate><atom:updated>2009-10-09T15:54:47.012+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP MRP</category><title>PP MRP Difference between MRP vs MPS</title><description>&lt;p&gt;&lt;b&gt;Explain the difference between MRP &amp;amp; MPS. Though both components gives you the requirement list, what we gain out of MPS run rather than running MRP. What is the main idea behind this?&lt;/b&gt; &lt;/p&gt;&lt;p&gt;The following might help in explaining the difference between MPS and its counter part MRP. &lt;/p&gt;&lt;p&gt;&lt;b&gt;Master Production Schedule (MPS) : &lt;/b&gt;&lt;br /&gt;MPS operates within only one level of the BOM, While MRP can be utilized throughout all levels of a material’s BOM. If a MPS is run on a material, the necessary orders are planned at that level. Dependent requirements (if any) are placed on the next BOM level down, and then the process stops. &lt;/p&gt;&lt;p&gt;Main Idea : Master production scheduling (MPS) is a form of MRP that concentrates planning on the parts or products that have the great influence on company profits or which dominate the entire production process by taking critical resources. These items are marked as ‘A’ parts (MPS items) and are planned with extra attention. These items are selected for a separate MPS run that takes place before the MRP run. The MPS run is conducted without a BOM explosion so that the MRP controller can ensure that the Master schedule items (MSI) are correctly planned before the detailed MRP run takes place. &lt;/p&gt;&lt;p&gt;The master production schedule is a line on the master schedule grid that reflects the anticipated build schedule for those items assigned to the master scheduler. The master scheduler maintains this schedule, and in turn, it becomes a set of planning numbers that drives material requirements planning. It represents what the company plans to produce expressed in specific configurations, quantities, and dates. The master production schedule is not a sales item forecast that represents a statement of demand. The master production schedule must take into account the forecast, the production plan, and other important considerations such as backlog, availability of material, availability of capacity, and management policies and goals. Syn: master schedule. &lt;/p&gt;&lt;p&gt;&lt;b&gt;Material Requirements Planning (MRP) : &lt;/b&gt;&lt;br /&gt;A set of techniques that uses bill of material data, inventory data, and the master production schedule to calculate requirements for materials. It makes recommendations to release replenishment orders for material. Further, because it is time-phased, it makes recommendations to reschedule open orders when due dates and need dates are not in phase. Time-phased MRP begins with the items listed on the MPS and determines &lt;/p&gt;&lt;p&gt;(1) the quantity of all components and materials required to fabricate those items and  &lt;/p&gt;&lt;p&gt;(2) the date that the components and material are required. Time-phased MRP is accomplished by exploding the bill of material, adjusting for inventory quantities on hand or on order, and offsetting the net requirements by the appropriate lead times. &lt;/p&gt;&lt;p&gt;&lt;b&gt;MRP Interview Questions:&lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;What is the need of mrp list if stock requirement list is already there?&lt;/b&gt; &lt;/p&gt;&lt;p&gt;The MRP list displays the result of the last planning run. Changes that have occurred between planning runs are ignored in the MRP list. In contrast to this, the system displays all changes in stock, receipts and issues, which have currently occurred, in the stock/requirements list. &lt;/p&gt;&lt;p&gt;&lt;b&gt;Which tcode are used to run MRP?&lt;/b&gt; &lt;/p&gt;&lt;p&gt;- MD01 is generally used to run the MRP for all the materials in a plant normally just before go-live.&lt;br /&gt;- MD02 is used to run MRP for materials which have a BOM i.e multi-level.&lt;br /&gt;- MD03 is used to run MRP for materials which do not have a BOM i.e single level.&lt;/p&gt;</description><link>http://sapsoftwareknowledge.blogspot.com/2009/10/pp-mrp-difference-between-mrp-vs-mps.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-6596886713020026744</guid><pubDate>Fri, 09 Oct 2009 10:23:00 +0000</pubDate><atom:updated>2009-10-09T15:54:18.683+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP MRP</category><title>SAP PP MRP Factory Calendar</title><description>&lt;p&gt;Factory calendar contain company specific dates such as alternate working Saturdays, Plant shutdown etc. &lt;/p&gt;&lt;p&gt;You can create your company factory calendar via transaction code '&lt;b&gt;&lt;span style="color: rgb(204, 102, 0);"&gt;SCAL&lt;/span&gt;&lt;/b&gt;'. &lt;/p&gt;&lt;p&gt;Assignment of the factory calendar by plant is done in transaction code '&lt;b&gt;&lt;span style="color: rgb(204, 102, 0);"&gt;SM30&lt;/span&gt;&lt;/b&gt; - V_T001W'. &lt;/p&gt;&lt;p&gt;An example of a SAP application that uses the factory calendar is the SAP MRP modules. &lt;/p&gt;Assuming that you have a specified an alternate working Saturday, MRP will postponed the planned orders to the next working day if it happened to falls on a non-working Saturday.</description><link>http://sapsoftwareknowledge.blogspot.com/2009/10/sap-pp-mrp-factory-calendar.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-7869699372832262678</guid><pubDate>Fri, 09 Oct 2009 10:23:00 +0000</pubDate><atom:updated>2009-10-09T15:53:49.809+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP MRP</category><title>PP MRP GR processing time in PP and MM</title><description>&lt;p&gt;&lt;b&gt;I have one material number that is procured externally but also produced inhouse. Now I have one problem with the GR processing time. As far as I can see the parameter on the material master on MRP2 view and Purchasing view is the same (MARC-WEBAZ). But in my case the GR processing time should be only used for goods receipts in MM (from purchase oders). This GR processing time must not be added to my lead time scheduled in production (when producing the material). How to solve this conflict?&lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;We have a make to order enviroment, that means our production orders are created (and scheduled) directly from the sales order. The sales gets back a confirmed date and quantity from production order scheduling - and here this GR processing time is also added. Absolutely useless in this scenario, but MM needs this GR processing time for the external procurement of the material.&lt;/b&gt; &lt;/p&gt;&lt;p&gt;I'm hearing at least two problems here. Let me lumber through them as I see them.  &lt;/p&gt;&lt;p&gt;#1 - We have a make to order enviroment, that means our production orders are created (and scheduled) directly from the sales order. The sales gets back a confirmed date and quantity from production order scheduling - and here this GR processing time is also added. Absolutely useless in this scenario, but MM needs this GR processing time for the external procurement of the material. &lt;/p&gt;&lt;p&gt;The GR processing time is quite legitimate, and needful. It represents the time it takes once a material is 'delivered', before it is usable. If that is instantaneous for you, then this field is blank. In fact if it is less than one day, the field should be blank. (MARC-WEBAZ) If you DO have to do testing or documentation or even just 'checking' to be sure the proper certificates&lt;br /&gt;have arrived with this material, then it's nice to have a day here for this. --- I may have overlooked one thing, if you are ONLY thinking of the FERT that your customer ordered, then maybe this field seems trivial. However, if your process requires that the FERT be purchased from some other company (or even supplied from within YOUR company), then there IS a receiving process that has to happen . . . it does take time to back a truck up, get a fork truck to unload it, the&lt;br /&gt;identification process, and then relocating the item to where it can be shipped to your customer.  &lt;/p&gt;&lt;p&gt;Also, if you produce this item, then there are 'other' items that need to be 'built' into this item . . . THEY need the GR field, even if you produce the saleable item, it has to be 'received' from production into inventory for you to ship it out. &lt;/p&gt;&lt;p&gt;There is another field that should be considered. This is the procurement lead time. The time it takes for purchasing to "react" to the requirement. When the sales order is placed, the signal will come for 'purchasing' to occur (via MRP perhaps). Purchasing MAY take as long as a day to get that order to a vendor where the vendor can now react. This time is generally a 'standard' time for any given plant/purchasing org and is included using OMDT. &lt;/p&gt;&lt;p&gt;Thirdly, the vendor lead time has to be considered. This is what the field "Planned delivery time" (MARC-PLIFZ) is about. The vendor's turn around time - from the time they are notified of your intention (via a PO perhaps), until they can put it on your dock . . . that is what this field is about. And MRP knows the difference between this field and the others. Between the three fields mentioned, the 'purchased' item is properly planned for . . . except for the exceptions and the fact that this is all based on "norms" and averages which never seem to be exactly what is needed, but that's another discussion . &lt;/p&gt;&lt;p&gt;Next we think of the situation where the item requested is produced by us. In this case (as mentioned before), the GR is STILL legitimate - perhaps not needed if it takes less than a day for your company to receive material from production, inspect it, certify it, and load it up. &lt;/p&gt;&lt;p&gt;However, a "0" is a legitimate entry to this field.  &lt;/p&gt;&lt;p&gt;What is also needed is a place to locate the time for "producing" this item. That is where there are options. One option in MRP 2 is the field "in-house production" (MARC-DZEIT). This is sometimes useful, but dangerous. It assumes that no matter how large an order is or how much of a material is needed, it can always be produced in the same period (in 'days', of course). The number of days fits in this field. &lt;/p&gt;&lt;p&gt;If that doesn't 'do it' for you, you can go to the "Work Scheduling" view of the Material Master and include the details for the fields under the "in house production time in days" grouping (Setup time; Interoperation; Processing time; and base quantity). At LEAST this gives the system a 'shot' at planning longer times for greater quantities. If you fill both data points in (in&lt;br /&gt;house production time and " in days, the 'in days' will supercede the other).  &lt;/p&gt;&lt;p&gt;Now you've put in all the data that you HAVE to input to have the system plan the length of time needed for telling your customer when you will have their product ready for them. &lt;/p&gt;&lt;p&gt;In the case of your conflict where you produce OR source the item, then you MAY have a problem with GR - look at both scenarios and see what your entry should be. You CAN use the Total Replenishment Leadtime (MARC-WZEIT) field to be the TOTAL TIME when producing the material in-house, because the external replenishment does not look at this field. So MRP will run and depending on how you have it set, it will consider purchasing the material, or making the material, and the fields we've mentioned will impact the result as mentioned.&lt;/p&gt;</description><link>http://sapsoftwareknowledge.blogspot.com/2009/10/pp-mrp-gr-processing-time-in-pp-and-mm.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-249609095372945845</guid><pubDate>Tue, 29 Sep 2009 13:10:00 +0000</pubDate><atom:updated>2009-09-29T18:40:53.240+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP MRP</category><title>PP MRP Calculation to determine the delivery date and release date</title><description>&lt;p&gt;There have been three parameters that SAP will take it into calculation to determine the delivery date and release date during material requirement planning. They are - &lt;/p&gt;&lt;p&gt;1) Planned Delivery Time which is the vendor-dependent lead time being measured from the time PO is outputted (for sending to the vendor) till the time the shipment is delivered at the warehouse. &lt;/p&gt;&lt;p&gt;2) GR processing time represents the necessary period of time being required for receipting the shipment into the warehouse. This period is, usually, for quality and quantity inspection. &lt;/p&gt;&lt;p&gt;3) Purchasing Processing Time. This is the internal required time for processing the purchasing document (Purchase Requisition) till Purchase Order. You can set it up plant-wise via Transaction OMI8. &lt;/p&gt;&lt;p&gt;With these three parameters, it is possible that you can set it up correctly in your system to enable the appropriate planning of your material requirement.&lt;/p&gt;</description><link>http://sapsoftwareknowledge.blogspot.com/2009/09/pp-mrp-calculation-to-determine.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-4032507699468343199</guid><pubDate>Tue, 29 Sep 2009 13:10:00 +0000</pubDate><atom:updated>2009-09-29T18:40:27.919+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP MRP</category><title>PP MRP Purchasing processing Time - OPPQ</title><description>&lt;p&gt;&lt;b&gt;Please refer above subject and would like to do following. External Processing Time I have set in using OPPQ. My client want this time set differently for different Vendor. Is there any userexit or customization settings? &lt;/b&gt; &lt;/p&gt;&lt;p&gt;For MRP to take lead time by supplier, you need to have 3 settings:  &lt;/p&gt;&lt;p&gt;1) The config in OPPQ - External procurement at plant level (or OPPR at MRP grp - Scheduling/doc. type) should have the check box marked to read SchedAgreem/Inforecord leadtime (T399D-GTERM) &lt;/p&gt;&lt;p&gt;2) You should have a contract/schedule agreement, or a purchase info record maintained for that plant-material-vendor combination &lt;/p&gt;&lt;p&gt;3) You should maintain source list (ME01) for the contract/schedule agreement, or info record. This changes the default behavior of MRP to use leadtime by supplier, rather than material master leadtime. When both contract and info record exist, the contract will take precedence. &lt;/p&gt;&lt;p&gt;Please watchout for the case if you're already using contracts/info records in procurement, but not using them for planning. In this case your leadtime data in these documents may be incorrect, or may be left blank - this will be interpreted as zero if you make this change implementation, as mentioned in the steps above.&lt;/p&gt;</description><link>http://sapsoftwareknowledge.blogspot.com/2009/09/pp-mrp-purchasing-processing-time-oppq.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-1437726648537898558</guid><pubDate>Tue, 29 Sep 2009 13:09:00 +0000</pubDate><atom:updated>2009-09-29T18:40:02.459+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP MRP</category><title>PP MRP Define Safety Stock Availability</title><description>&lt;p&gt;The IMG can be set in &lt;b&gt;&lt;span style="color: rgb(204, 102, 0);"&gt;SM30&lt;/span&gt;&lt;/b&gt; - &lt;b&gt;&lt;span style="color: rgb(204, 51, 204);"&gt;V_438M_S&lt;/span&gt;&lt;/b&gt; &lt;/p&gt;&lt;p&gt;You define per plant and per MRP group the percentage of the safety stock that is to be available for planning. This helps to avoid a situation where order proposals are created unnecessarily by the system to cover small shortage quantities. &lt;/p&gt;&lt;p&gt;For example: &lt;/p&gt;&lt;p&gt;                                      Mat. 1         Mat. 2         Mat. 3  &lt;/p&gt;&lt;p&gt;Safety stock:                  100 pc         100 pc        100 pc&lt;br /&gt;&lt;/p&gt;&lt;p&gt;available for planning:       0%              50%           50%&lt;br /&gt;&lt;/p&gt;&lt;p&gt;Shortage quantity             1 pc             1 pc           51 pc  &lt;/p&gt;Order proposal quantity&lt;br /&gt;for lot-for-lot order qty    1 pc             0 pc           51 pc</description><link>http://sapsoftwareknowledge.blogspot.com/2009/09/pp-mrp-define-safety-stock-availability.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-6135978168106385548</guid><pubDate>Tue, 29 Sep 2009 13:09:00 +0000</pubDate><atom:updated>2009-09-29T18:39:34.978+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP MRP</category><title>PP MRP Questions on MRP Group and MRP Controller</title><description>&lt;p&gt;MRP groups are used when the plant division for planning is not enough for the division of the different materials MRP requirements. You assign different groups according to the requirements to run MRP (different Settings). These settings will be taken in account when you run MRP for single item or total planning. &lt;/p&gt;&lt;p&gt;MRP controller is the person in charge of the MRP run for the materials. It is still a further division on your MRP. This is work load related. You can have one MRP controller for materials with different MRP groups. &lt;/p&gt;&lt;p&gt;On your MRP group, you will define the parameters for the MRP run. These parameters are calculated in accordance with the settings on your material master MRP views. &lt;/p&gt;&lt;p&gt;Available stock =&lt;br /&gt;            Plant stock - safety stock +&lt;br /&gt;            receipts of (purchasing orders + purchasing agreements + production orders) - required quantity. &lt;/p&gt;&lt;p&gt;This means that all the requirements are calculated in the bases of your material master settings and your MRP group settings.&lt;br /&gt;&lt;/p&gt;&lt;p&gt;&lt;b&gt;What if nothing happens when you run MRP?&lt;/b&gt; &lt;/p&gt;&lt;p&gt;The reasons could be :-  &lt;/p&gt;&lt;p&gt;- You have purchase requisitions that are delayed but the delivery time has not been updated on the system. &lt;/p&gt;&lt;p&gt;- The settings on your material MRP screens are not correct, i.e. your material have not yet&lt;br /&gt;entered the re-order point level. &lt;/p&gt;&lt;p&gt;- Your requirements have not been taken in account when running MRP.&lt;br /&gt;&lt;/p&gt;&lt;p&gt;Assuming that everything is well and the requirement has been calculated, go to transaction code &lt;b&gt;&lt;span style="color: rgb(204, 102, 0);"&gt;MD04&lt;/span&gt;&lt;/b&gt; and verify that the different requirements are reflected in the MRP list and also if there is any purchase requisition scheduled by the system. Verify also if there is any other delivery schedule that will exceed the actual requirements. &lt;/p&gt;&lt;p&gt;If the purchasing requisition is there, the only thing that you have to troubleshoot is the message to tell you that the purchasing requirement was calculated. &lt;/p&gt;&lt;p&gt;If the requirement is not there, re-visit your material master and check your settings for the MRP group. &lt;/p&gt;&lt;p&gt;&lt;b&gt;What is the real meaning and usage of the followings configured in PP: &lt;/b&gt;&lt;br /&gt;&lt;b&gt;1. MRP Controller; &lt;/b&gt;&lt;br /&gt;&lt;b&gt;2. Schedule margin key; &lt;/b&gt;&lt;br /&gt;&lt;b&gt;3. MRP group; &lt;/b&gt;&lt;br /&gt;&lt;b&gt;4. MRP profile.&lt;/b&gt; &lt;/p&gt;&lt;p&gt;1. MRP Controller;&lt;br /&gt;This will help you to group the material for some controlling purpose.   You can run mrp by mrp controller.&lt;br /&gt;you can do evaluation by mrp controller. This will help us if have different people in one organisation involved in purchasing. &lt;/p&gt;&lt;p&gt;2. Schedule margin key;  &lt;/p&gt;&lt;p&gt;This will help you to determine the floats. In case if you have production order you can see the impact of floats  &lt;/p&gt;&lt;p&gt;3. MRP group;  &lt;/p&gt;&lt;p&gt;This will help you for the material to reac in tems of the settings made relavant to each group. To know more details on the group you can chek the tcode oppr. &lt;/p&gt;&lt;p&gt;4. MRP profile&lt;br /&gt;We can have some prefixed datas in the profile and and we can enter teh profile for diff material so the values will copied as defaulted in the profile.&lt;/p&gt;</description><link>http://sapsoftwareknowledge.blogspot.com/2009/09/pp-mrp-questions-on-mrp-group-and-mrp.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-1708637619188366165</guid><pubDate>Tue, 29 Sep 2009 13:08:00 +0000</pubDate><atom:updated>2009-09-29T18:39:09.643+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP MRP</category><title>PP MRP Planning separately via Storage Location or Vendor with MRP Area</title><description>Steps 1 :-&lt;br /&gt;&lt;br /&gt;You must convert the existing planning file (table MDVM) to the new planning file (table DBVM)&lt;br /&gt;in order to be able to use MRP areas in materials requirements planning. Transaction OM0F.&lt;br /&gt;&lt;br /&gt;1.  During the conversion, the system creates a plant MRP area for every plant.&lt;br /&gt;2.  The existing planning file entries are copied from the planning file used up to now into&lt;br /&gt; the new planning file.&lt;br /&gt;3.  The system deletes the planning file that had been used up to now after the conversion has&lt;br /&gt; taken place.&lt;br /&gt;4.  At client level, the indicator Planning file entries for MRP area converted is set in a&lt;br /&gt; system table. This indicator causes material requirements planning to be carried out using&lt;br /&gt; planning file entries at MRP area level from this point onwards.&lt;br /&gt;5.  The report also converts the individual customer planning file entries at plant level to&lt;br /&gt; individual customer planning file entries at MRP area level.&lt;br /&gt;&lt;br /&gt;Steps 2 :-&lt;br /&gt;&lt;br /&gt;Activate MRP Area in SM30 - T000MD.&lt;br /&gt;(Material requirements planning with MRP areas cannot be reversed once activated).&lt;br /&gt;&lt;br /&gt;Steps 3 :-&lt;br /&gt;&lt;br /&gt;During conversion in Steps 1, SAP will automatically create a MRP area for all your existing&lt;br /&gt;Plants.&lt;br /&gt;&lt;br /&gt;Now, you can start creating the MRP area for storage location or vendor to be planned&lt;br /&gt;separately.  That's is the whole purpose for using MRP area.&lt;br /&gt;&lt;br /&gt;Define MRP Area in SM30 - V_MDLV.&lt;br /&gt;Here you define whether the MRP area type :-&lt;br /&gt;01 - Plant&lt;br /&gt;02 - Storage Location&lt;br /&gt;03 - Vendor&lt;br /&gt;&lt;br /&gt;Steps 4 :-&lt;br /&gt;&lt;br /&gt;In Material Master MRP 1, the MPR area section will appear once you successfully complete&lt;br /&gt;the above Steps.&lt;br /&gt;&lt;br /&gt;Assign MRP Areas to Materials&lt;br /&gt;&lt;br /&gt;You assign the MRP areas to the materials by creating an MRP area segment for each MRP area&lt;br /&gt;in the material master. You can assign several MRP areas to one material.&lt;br /&gt;&lt;br /&gt;MRP with MRP areas for the material is not activated until an MRP area has been assigned to&lt;br /&gt;a material. If you have not assigned an MRP area to a material, that is, you have not created&lt;br /&gt;an MRP area segment in the material master, the material will continue to be planned in the&lt;br /&gt;plant MRP area only. If you have assigned an MRP area to the material, the system can plan it&lt;br /&gt;in the plant MRP area and in the assigned MRP area.&lt;br /&gt;&lt;br /&gt;You can display an overview for all materials in an MRP area. To do this, you go into&lt;br /&gt;Customizing for MRP and choose the IMG activity Define MRP areas. Call up an MRP area by&lt;br /&gt;double-clicking and choose  Material overview for MRP area.&lt;br /&gt;&lt;br /&gt;Steps 5 :-&lt;br /&gt;&lt;br /&gt;Check Storage Locations&lt;br /&gt;&lt;br /&gt;If you have already entered a storage location in the BOM (BOM item), in the work center&lt;br /&gt;(supply area) or in the production version, you should check whether this storage location&lt;br /&gt;is the storage location for the MRP area that you have assigned in the material master.&lt;br /&gt;&lt;br /&gt;The materials are assigned to an MRP area via the storage location that the system&lt;br /&gt;determines during the planning run. You should therefore check the storage locations that&lt;br /&gt;you have maintained in the material master. The storage location in the material master&lt;br /&gt;must be a storage location for the MRP area, for which you have created an MRP area segment&lt;br /&gt;in the material master. You can therefore ensure that material requirements planning will&lt;br /&gt;be carried out for the correct MRP area&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;The MRP area represents an organizational unit for which material requirements planning is&lt;br /&gt;carried out independently.&lt;br /&gt;&lt;br /&gt;Basically, there are three types of MRP area:&lt;br /&gt;&lt;br /&gt;Plant MRP Area&lt;br /&gt;The plant MRP area initially contains the plant together with all its storage locations and&lt;br /&gt;stock with subcontractors.&lt;br /&gt;&lt;br /&gt;When you have defined MRP areas for storage locations and for subcontractors and you have&lt;br /&gt;assigned the materials, the plant MRP area is reduced by exactly this number of subcontractors&lt;br /&gt;and storage locations. This is because they are now to be planned separately.&lt;br /&gt;&lt;br /&gt;MRP Areas for Storage Locations&lt;br /&gt;You can define an MRP area that consists of a particular storage location, by creating an MRP&lt;br /&gt;area and assigning the storage location to it. Material requirements for this storage location&lt;br /&gt;are then planned separately from the rest of the plant.&lt;br /&gt;&lt;br /&gt;You can also group several storage locations into one MRP area, by creating an MRP area and&lt;br /&gt;assigning the storage locations to it. These storage locations are then planned together.&lt;br /&gt;&lt;br /&gt;A storage location of a plant may be assigned to only one MRP area.&lt;br /&gt;&lt;br /&gt;MRP Areas for Subcontractors&lt;br /&gt;You can also define an MRP area for each subcontractor.&lt;br /&gt;&lt;br /&gt;A subcontractor may be assigned to only one MRP area.&lt;br /&gt;&lt;br /&gt;An MRP area of the subcontractor type may also only contain one subcontractor.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;MRP areas of the storage location or subcontractor type are only suitable for:&lt;br /&gt;&lt;br /&gt;1. components that are planned and produced for stock&lt;br /&gt;&lt;br /&gt;2. finished products that are planned and produced for stock.&lt;br /&gt;&lt;br /&gt;By assigning a storage location in a sales order or by entering an MRP area when creating&lt;br /&gt;the planned independent requirements, you can define whether a material is planned in the&lt;br /&gt;plant MRP area or in the MRP area of the storage location.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Material requirements planning for each MRP area allows you to have specific control over&lt;br /&gt;the staging and procurement of parts produced in-house and purchased parts for each shop&lt;br /&gt;floor and assembly area. If, for example, you define an MRP area for the production&lt;br /&gt;storage location of an assembly line, the system plans the material requirements for the&lt;br /&gt;assembly line separately from all other requirements.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Example: Subcontractor&lt;br /&gt;&lt;br /&gt;You can also carry out planning for components to be provided in subcontracting using an&lt;br /&gt;MRP area by defining an MRP area for every subcontractor and assigning the components to be&lt;br /&gt;provided to the MRP area of the subcontractor. You therefore plan the requirements to be&lt;br /&gt;provided for these components for one subcontractor separately from all other requirements.&lt;br /&gt;&lt;br /&gt;Depending on the requirements situation, the system creates either stock transfer reservations&lt;br /&gt;from the plant to the stock of material provided of the subcontractor or it creates purchase&lt;br /&gt;requisitions within subcontracting/third-party order processing, according to the special&lt;br /&gt;procurement key settings.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;The planning run takes into account the planning with MRP areas as follows:&lt;br /&gt;&lt;br /&gt;If you do not enter a separate scope of planning, the system plans the whole plant, that is,&lt;br /&gt;all MRP areas in the plant, during the total planning run. If you want to carry out a total&lt;br /&gt;planning run for a particular MRP area only, you must specify the required MRP area in the&lt;br /&gt;scope of planning.&lt;br /&gt;&lt;br /&gt;During single-item, multi-level planning, the system plans the selected material in the MRP&lt;br /&gt;area entered. In addition, the system takes into account planning file entries from other&lt;br /&gt;MRP areas, for example, if the material is to be procured using stock transfer.&lt;br /&gt;During single-item, single-level planning, the system plans the selected material in the&lt;br /&gt;MRP area entered only.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;You define the MRP areas in Customizing for MRP. You can thereby assign the following to&lt;br /&gt;an MRP area: one or more storage locations (example: you want to carry out planning for a&lt;br /&gt;particular assembly line and therefore assign a production storage location to the MRP area)&lt;br /&gt;a subcontractor.&lt;br /&gt;&lt;br /&gt;You assign the various MRP areas to the materials in the material master. For this, you&lt;br /&gt;create an MRP area segment for a material for every MRP area, in which it is used. In this&lt;br /&gt;MRP area segment, you can define MRP parameters such as, for example, the lot size or MRP&lt;br /&gt;type. This allows you to plan the material differently in the MRP area from how you plan it&lt;br /&gt;in the plant MRP area.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;MRP with MRP areas for the material is not activated until the material has been assigned&lt;br /&gt;to an MRP area. If you have not assigned a material to an MRP area, that is, you have&lt;br /&gt;not created an MRP area segment in the material master, the material will continue to&lt;br /&gt;be planned in the plant MRP area only. If you have assigned an MRP area to it, the system&lt;br /&gt;can plan it in the plant MRP area and in the assigned MRP area.</description><link>http://sapsoftwareknowledge.blogspot.com/2009/09/pp-mrp-planning-separately-via-storage.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-8839528812928472120</guid><pubDate>Tue, 29 Sep 2009 13:07:00 +0000</pubDate><atom:updated>2009-09-29T18:38:21.143+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP MRP</category><title>PP - The Common Planning Strategy used</title><description>The planning strategies are maintained in Customizing for Demand Management in &lt;b&gt;&lt;span style="color: rgb(204, 102, 0);"&gt;SM30 - V_T461S&lt;/span&gt;&lt;/b&gt;.&lt;br /&gt;&lt;br /&gt;Define the Planned Requirement Type and assign the requirement class in &lt;b&gt;&lt;span style="color: rgb(204, 102, 0);"&gt;OMP1&lt;/span&gt;&lt;/b&gt;.&lt;br /&gt;&lt;br /&gt;Define the requirement class in &lt;b&gt;&lt;span style="color: rgb(204, 102, 0);"&gt;OMPO&lt;/span&gt;&lt;/b&gt;.&lt;br /&gt;&lt;br /&gt;Check the independent requirement and consumption of requirement class in &lt;b&gt;&lt;span style="color: rgb(204, 102, 0);"&gt;OMPC&lt;/span&gt;&lt;/b&gt;.&lt;br /&gt;&lt;br /&gt;Maintain the message for invalid requirement type in &lt;b&gt;&lt;span style="color: rgb(204, 102, 0);"&gt;OMPJ&lt;/span&gt;&lt;/b&gt;.&lt;br /&gt;&lt;br /&gt;You define the strategy group in &lt;b&gt;&lt;span style="color: rgb(204, 102, 0);"&gt;SM30 - V_T461P&lt;/span&gt;&lt;/b&gt;.&lt;br /&gt;&lt;br /&gt;You define the Plant to MRP group in &lt;b&gt;&lt;span style="color: rgb(204, 102, 0);"&gt;SM30 - V_T438M_S&lt;/span&gt;&lt;/b&gt;.&lt;br /&gt;&lt;br /&gt;Maintain the consumption mode and period of adjustment in &lt;b&gt;&lt;span style="color: rgb(204, 102, 0);"&gt;SM30 - V_T438M_V&lt;/span&gt;&lt;/b&gt;.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Listed here are some common used planning strategies :-&lt;br /&gt;&lt;/b&gt; &lt;br /&gt;&lt;span style="color: rgb(0, 0, 0);"&gt;&lt;b&gt;Strategy 10 in summary :-&lt;br /&gt;&lt;br /&gt;&lt;/b&gt;1. Sales Order creation - no impact.&lt;br /&gt;&lt;br /&gt;2. Goods Receipt - reduce the planned independent requirement during MRP run&lt;br /&gt; For e.g. if PIR is 100, quantity remained as 100 in PIR, however during MRP run,&lt;br /&gt; 100 will not be included in the MRP planned as stock is available.&lt;br /&gt;&lt;br /&gt;3. Delivery - minus the quantity for the oldest planned independent in demand management.&lt;br /&gt; For e.g. if PIR is 100 and delivery 90, PIR becomes 10 (withdrawal 90).&lt;br /&gt;&lt;/span&gt;        &lt;br /&gt;&lt;br /&gt;10  LSF    Make-to-stock production               KSL   Sale from stock without independent&lt;br /&gt;                                                                                 requirement reduction&lt;br /&gt;&lt;br /&gt;Choose this strategy if you want production to be determined by a production plan (Demand Management) and if you do not want sales orders to influence production directly.&lt;br /&gt;&lt;br /&gt;You must maintain the following master data for the finished product:&lt;br /&gt;&lt;br /&gt;&lt;b&gt;&lt;span style="color: rgb(204, 51, 204);"&gt;Strategy group 10 on the MRP screen.&lt;br /&gt;Item category group (for example, NORM) on the Sales Organization screen.&lt;br /&gt;Availability check field in Customizing so that you perform an availability check&lt;br /&gt;without replenishment lead times (in the standard system, you must enter 02 here).&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;/b&gt;In net requirements planning according to strategy 10, the order does not create a requirement; the sales order is displayed, but does not generate planned orders.&lt;br /&gt;&lt;br /&gt;The planned independent requirement is reduced during processing of the goods issue.&lt;br /&gt;Old quantities can still be retrieved by using either&lt;br /&gt;Goto -&gt; Schedule line history in Demand Management, or by using the total requirements list&lt;br /&gt;(Evaluations -&gt; Display total requirements from the Demand Management menu).&lt;br /&gt;The quantities issued are displayed in the Withdrawal quantity field.&lt;br /&gt;&lt;br /&gt;The system always reduces the oldest planned independent requirements unless the consumption fields (Consumption mode, Fwd consumption per., Bwd consumption per.) are maintained in the material master or in the MRP group.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;11  BSF    Gross planned independent requirements  KSL Sale from stock without independent&lt;br /&gt;                                                                                       requirement reduction&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Strategy 11 in summary :-&lt;br /&gt;&lt;br /&gt;&lt;/b&gt;1. Sales Order creation - no impact.&lt;br /&gt;&lt;br /&gt;2. Goods Receipt - minus the quantity for the oldest planned independent in demand management.&lt;br /&gt; For e.g. if PIR is 100 and delivery 90, PIR becomes 10 (withdrawal 90).&lt;br /&gt;&lt;br /&gt;3. Delivery - no impact as delivery is issue from sales order.&lt;br /&gt;&lt;br /&gt;This strategy is particularly useful if you need to produce, regardless of whether you have stock or not. For instance, steel or cement producers might want to use this strategy because they cannot shut down production; a blast furnace or a cement factory must continue to produce, even if this means having to produce to stock.&lt;br /&gt;&lt;br /&gt;You need to maintain the following master data for the finished product:&lt;br /&gt;&lt;br /&gt;&lt;b&gt;&lt;span style="color: rgb(204, 51, 204);"&gt;Maintain strategy group 11 on the MRP screen.&lt;br /&gt;Set the Mixed MRP indicator to 2 on the MRP screen.&lt;br /&gt;Maintain the item category group (for example, NORM) on the Sales Organization screen.&lt;br /&gt;Maintain the Availability check field so that you perform an availability check without the replenishment lead time (checking group 02 in the standard system).&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;/b&gt;Strategy                                                        10                  11&lt;br /&gt;&lt;br /&gt;Stock is taken into account                           Yes                 No&lt;br /&gt;&lt;br /&gt;Reduction of planned independent&lt;br /&gt;requirements takes place during …   … goods issue for   ... goods receipt for a production&lt;br /&gt;the delivery order (discrete production),&lt;br /&gt;                                                                                    for a planned order (repetitive&lt;br /&gt;                                                                                    manufacturing), or for a purchase&lt;br /&gt;                                                                                    order (trading goods).</description><link>http://sapsoftwareknowledge.blogspot.com/2009/09/pp-common-planning-strategy-used.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-7211799741940114006</guid><pubDate>Tue, 29 Sep 2009 13:07:00 +0000</pubDate><atom:updated>2009-09-29T18:37:47.741+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP MRP</category><title>PP MRP Why Planning file entry still Exists?</title><description>&lt;p&gt;&lt;b&gt;Does anyone know why a planning file entry would exist for NETCH or NETPL when there has been NO activity on the material since the last planning run? No movements, no PO's created, no Orders taken, no activity whatsoever . . . and MRP ran, created a planned order, which was converted to a requisition and then a PO. This PO was converted for a date earlier than what MRP recommended. &lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;Now each time MRP runs, we get exception #15 - delay the order until later (gives date). We don't change it and the planning file entry doesn't go away, even after the run. &lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;Found a note that seemed to apply, but . . . I guess it doesn't really. &lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;"If the planning run terminates for a material with planning file entry on account of an error message, the planning file entry is not deleted if this is not explicitly set in customizing. In transaction OMDY, you can set for which errors (message number) you want the planning file entry being deleted." &lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;I thought this was my answer. However, after looking in OMDY - the message #015 = Dates incorrect (start date &gt; finish date). And message #15 = Enter value for version number increment (VersNumIncr.). &lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;Neither of these defines my MRP List exception message 15 = "Postpone process (28.06.2004/26.06.2004)" - on a current date of 03/06/2004. It's CLOSE, but not the first message. &lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;So if I set the field for the deletion of the planning file entry, it still wouldn't affect my real problem - trying to get this entry to 'go away' after doing what it was supposed to do. &lt;/b&gt; &lt;/p&gt;&lt;p&gt;Please Check CS15 - where used list. May be this material has been added to a BOM of a product/Assy, which has caused an entry in planning file. &lt;/p&gt;&lt;p&gt;Check MD04 for the source of reqt.  &lt;/p&gt;&lt;p&gt;Also check MD63, if a PIR exists.  &lt;/p&gt;&lt;p&gt;If not, delete from planning file. Try report RMMDVM10 - consistency check.&lt;/p&gt;</description><link>http://sapsoftwareknowledge.blogspot.com/2009/09/pp-mrp-why-planning-file-entry-still.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-3949114979781258042</guid><pubDate>Tue, 29 Sep 2009 13:06:00 +0000</pubDate><atom:updated>2009-09-29T18:37:22.293+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP MRP</category><title>PP MRP Planning Strategy Selection</title><description>&lt;p&gt;Selection priority for planning strategy is: &lt;/p&gt;&lt;p&gt;First material, second MRP group and last plant parameters. E.g. System first checks for material, if strategy is defined there, that is used, if it's not maintained there, then it checks if it's defined in MRP group. &lt;/p&gt;&lt;p&gt;That is the same for all MRP parameters, not only strategy. &lt;/p&gt;&lt;p&gt;If you wanna test how it works, try this: &lt;/p&gt;&lt;p&gt;1. create an mrp group, say 0001, and assign strategy group "40 - planning with final assembly" in the MRP group parameters. &lt;/p&gt;&lt;p&gt;2. create a material, say product1 and define planning strategy as "20 - make to order". And also enter the MRP group 0001 in material master. &lt;/p&gt;&lt;p&gt;3. Create a sales order and create an order item for product1. &lt;/p&gt;&lt;p&gt;4. In the sales order header, go to the Procurement tab. There, you will see the requirement type for product1, which is automatically selected by system according to the planning strategy it uses. That requirement type should be "KE" if strategy 20 is selected, or it should be "KSL" if strategy 40 is selected by system. &lt;/p&gt;&lt;p&gt;5. In my test, system selected KE requirement type, which indicates that system used strategy 20, and which I have entered in the material master. It didn't select KSL, which indicates that system uses strategy 40, which is entered in the mrp group. Finally, this test shows that system takes the planning strategy in material master (if it's entered), not the strategy in MRP group. &lt;/p&gt;&lt;p&gt;I think you can now make another test how system uses MRP group's planning strategy. (hint: Delete planing strategy from the material master and repeat the previous test steps. That would end up using strategy 40, which is selected using the MRP group parameters.) &lt;/p&gt;&lt;p&gt;&lt;b&gt;With Compliment: &lt;span style="color: rgb(153, 0, 0);"&gt;Osman Karslioglu&lt;/span&gt;&lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;&lt;span style="color: rgb(204, 0, 0);"&gt;&lt;span style="font-size: 85%;"&gt;When do we use planning without final assembly strategy?&lt;/span&gt;&lt;/span&gt;&lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;We have mainly MTS, MTO, planning with final assembly and planning without final assembly. Now when we are dealing with planning with final assembly, we would usually produce subassemblies (HALBs I guess) using make to stock, so do we use a planning strategy 70 for subassemblies and do a MRP run. To my knowledge I thought we run MRP only for final products (with final assembly) so in that case how would we plan for subassembly products.&lt;/b&gt; &lt;/p&gt;I get to understand you are using strategy planning with final assembly. So you are using strategy 40 for the finished product.&lt;br /&gt;&lt;br /&gt;Just to clarify certain things, MRP can be run for any material...be it finished or semi finished or raw material. Actually when you run a MRP for the finished product using MD02, you are doing a multilevel run.&lt;br /&gt;&lt;br /&gt;Secondly, when you are using 40 for the finished product you may or may not use any strategy for the semi finished goods. It depends on your business. If you are going to produce semi finished goods independent of the finished goods, you may have a make to stock strategy 10 (one of the many options) and produce them independent of the finished good requirement. Now when a requirement will be generated for the finished good and a MRP run will be taken, it will show that the Semi Finished is either in stock or a planned/production order exists and thus only the remaining quantity will be planned for (there is a better strategy existing for this type of a scenario.....&lt;br /&gt;&lt;br /&gt;However if you do not put any strategy for the Semi Finished, then planned orders will be created for the Semi Finished for the same quantity as the orders created for the Finished goods.</description><link>http://sapsoftwareknowledge.blogspot.com/2009/09/pp-mrp-planning-strategy-selection.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-542925238086454287.post-3493124197825164316</guid><pubDate>Tue, 29 Sep 2009 13:06:00 +0000</pubDate><atom:updated>2009-09-29T18:36:56.579+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP PP MRP</category><title>PP MRP Monthly lot size</title><description>&lt;p&gt;&lt;b&gt;Appreciated if some guide can be provided.  &lt;/b&gt;&lt;br /&gt;&lt;b&gt;MRP lot size has been set to MB (Monthly lot size) &lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;It is known that with this setting, material are always bring in on the first working day of the month. &lt;/b&gt;&lt;br /&gt;&lt;b&gt;Ex: Dep requirement 26-10-04 100 pcs &lt;/b&gt;&lt;br /&gt;&lt;b&gt;Dep requirement 30-10-04 190 pcs &lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;When MRP completion, the PR item shown 1-10-2004 290 pcs, is that any possible to bring in material just right before dependant requirement 26-10-04 say about 24 or 25 of the month. &lt;/b&gt;&lt;br /&gt;&lt;b&gt;Because. we dont tend to keep more stocks until actual requirement. &lt;/b&gt; &lt;/p&gt;&lt;p&gt;&lt;b&gt;Any comment are welcome. &lt;/b&gt; &lt;/p&gt;&lt;p&gt;In that case you might like to consider lot size key WB (weekly). It will bring in material at the first working day of the week. In your case it is Oct 25, 2004 &lt;/p&gt;&lt;p&gt;&lt;b&gt;But in this case, I will have increase administrative cost on monitoring the material lot weekly. &lt;/b&gt;&lt;br /&gt;&lt;b&gt;I want to have monthly lot size that group all the requirement, but bring in material as close as possible on the first requirement. &lt;/b&gt;&lt;br /&gt;&lt;b&gt;Any comment are welcome.. &lt;/b&gt; &lt;/p&gt;&lt;p&gt;How about manually change delivery date in PO item &lt;/p&gt;&lt;p&gt;&lt;b&gt;Check your config. in OMI4 - scheduling may by ''1'" for Lot size of MB. &lt;/b&gt;&lt;br /&gt;&lt;b&gt;Change to Blank. &lt;/b&gt; &lt;/p&gt;&lt;p&gt;Friend PPS is correct, Schedule the "REQUIREMENTS DATE = DELIVERY DATE" option in Customizing for Lot Size MB (use Blank instead of 1) &amp;amp; your reqt 'll be met... &lt;/p&gt;&lt;p&gt;&lt;b&gt;We have similar problem and when I applied your solution, the proposed requirement date is perfect.&lt;/b&gt;&lt;/p&gt;</description><link>http://sapsoftwareknowledge.blogspot.com/2009/09/pp-mrp-monthly-lot-size.html</link><thr:total>0</thr:total><author>prakashkdv509@gmail.com (Technical Data)</author></item></channel></rss>