06.01.2013 Views

SAP Production Planning Table

SAP Production Planning Table

SAP Production Planning Table

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Now the production order at lower level component also loose track and they were<br />

already released where as production orders at higher level were not released<br />

So now lower level production orders were tecoed with BDC program as there were 1200<br />

production orders to be tecoed at lower level .<br />

So once I deleted lower level, I saw that there were planned orders for same component<br />

and same sales order and item, this was because MRP was running at same time .<br />

So this MRP generated planned orders as the production orders at highrt level were still<br />

hanging there and to full fill those production orders lower level component planned<br />

orders were generated<br />

So now cleared the production orders in top level and ran MRP in display mode and<br />

found that there were no planned orders for lower level component.<br />

But still there were two more planned order created at higher level has I previously<br />

tecoed them and did zero confirmation due to some other reason, So I had to unteco them<br />

to delete these planned orders and also cancel confirmation to get the production order<br />

element on to MD04 screen. Once Iam done with that it show a message 26<br />

So It should be clear that if the exception message is 20 ie cancel process then that<br />

production order must be deleted as there is no requirement to consume this order. As all<br />

this context was made in MTO stock product.<br />

With Compliments from: Prashanth<br />

Fast Links:<br />

Batch Characteristics while Running MRP<br />

Can batch characteristics be considered while running a MRP? I have a finished<br />

good that has acid value as its batch characteristics. Based on this acid value I am<br />

trying to pick up a certain batch of raw material that is also batch managed and has<br />

its characteristics as acid value.<br />

While running MRP qty requirements are transferred and stock is reserved but the<br />

required batch qty (having the acid value required) of raw material is not picked.<br />

MRP does NOT use batch data.<br />

Because, while entering PIR, there's no field to enter batch number. When system creates<br />

planned order, also there's no field to enter batch number, both for the header material<br />

and planned order components.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!