Hallo,

we use Baan IV c4 ags2 and need to differentiate an item's demand for different revisions. This is especially important when phasing in a new version. At that time we still have stocks of e.g. revsion 1 but a customer would like to order the first few samples of revision 2 (using call offs in automotive). Unfortunately, Baan does not distinguish between different revision during the MRP calculation.

Is there anybody having similar problems and how did you solve it?

regards
Frank

I stumbled upon the same problem when we implemented EDM, unfortunately haven't found a solution (apart from customizing the complex MRP functionality).
We 'solved' it simply with a report that lists SO lines with the revision code, planners/purchasers amend the suggested PO's if necessary. If you find something better then please let me know.

regards,
Robert

Hi Frank if you are using tdpsc contracts expire the contract using the old reveision and make effective the new one. also MRP does check the BOM for effective items/routing so if you have PBOM history it can make/order both based on dates but order intervals make confuse the process some.

Hi Timothy,

that would work if one revision replaces another at a given time. Unfortunately, we have to sell and continue to produce older versions for up to 7 years (spare parts). Hence, customers will order various revisions parallel. Some do create new items for it others don't (and we would actually prefer not to create new items for every revision).