sukesh75
22nd April 2006, 14:17
Hi Guys,
We are a metal based furniture co. and we use Customized Items a lot in our manufacturing process. Recently though, after we started off with MRP, we ran into problems when generating Planned PRP Orders. As you all are aware that MRP requires Nettable warehouses, therefore we had to convert certain warehouses to nettable by setting the nettable option to Yes in the warehouse table. Listed below is the series of events that led to the problem..
Item A(Order Policy: To Order) had stock in Warehouse A (Nettable) but its default Warehouse B was nonettable and had no stock.
This item A was used in Sales Order 1 with Warehouse B.
When Generate Planned PRP Orders was run after Generate Project Structure for Sales Order, we found out to our surprise that Baan had created a Planned PRP Warehouse Order (Warehouse to Project: Warehouse A to Warehouse B) and a Planned PRP Production Order for the remainder of the required quantity that wasnt satisfied by the Warehouse to Project Transfer.
Tests done later concluded that if the required quantity was present in Warehouse A then the Planned PRP Production Order would not have been created at all.
1) Why would Baan do this?
2) Item A was customized and therefore shouldnt have anything to do with the stock of Standard Item it was customized from. So how can this warehouse transfer be justifiable?
3) Are we missing any parameter setting somewhere?
4) Is it anything to do with Nettable warehouses? If so does it mean that we cant have stock in a nettable warehouse for any "To Order" Item?
I would appreciate it very much if anyone can throw some light onto this.
We use Baan4c4 with SP 17 on Sql 7
Sk
P.S: If this sort of issue was mentioned earlier in any thread, kindly point me to it..
We are a metal based furniture co. and we use Customized Items a lot in our manufacturing process. Recently though, after we started off with MRP, we ran into problems when generating Planned PRP Orders. As you all are aware that MRP requires Nettable warehouses, therefore we had to convert certain warehouses to nettable by setting the nettable option to Yes in the warehouse table. Listed below is the series of events that led to the problem..
Item A(Order Policy: To Order) had stock in Warehouse A (Nettable) but its default Warehouse B was nonettable and had no stock.
This item A was used in Sales Order 1 with Warehouse B.
When Generate Planned PRP Orders was run after Generate Project Structure for Sales Order, we found out to our surprise that Baan had created a Planned PRP Warehouse Order (Warehouse to Project: Warehouse A to Warehouse B) and a Planned PRP Production Order for the remainder of the required quantity that wasnt satisfied by the Warehouse to Project Transfer.
Tests done later concluded that if the required quantity was present in Warehouse A then the Planned PRP Production Order would not have been created at all.
1) Why would Baan do this?
2) Item A was customized and therefore shouldnt have anything to do with the stock of Standard Item it was customized from. So how can this warehouse transfer be justifiable?
3) Are we missing any parameter setting somewhere?
4) Is it anything to do with Nettable warehouses? If so does it mean that we cant have stock in a nettable warehouse for any "To Order" Item?
I would appreciate it very much if anyone can throw some light onto this.
We use Baan4c4 with SP 17 on Sql 7
Sk
P.S: If this sort of issue was mentioned earlier in any thread, kindly point me to it..