Migration job for Purchase Order lines : no revision found

Hi ​@mduchaff 

please check the part revision for your part and contract
First of all, a part revision must be available
If so please check if the part revision has the same valid date as your purchase order date
 

BR
Martina​​​​​​​

You’re right Makede : that was a problem of dates. Some of the in-progress purchase orders were planned before the revision dates entered for the inventory parts.

Hi ​@mduchaff 

Ok, I have an idea.

When you create a new master part and then the inventory part manually or using a migration job then a record for the part revision (view name: inventory_part_revision) will be automatically created.

Sounds good but when you have a look into the part revision then you will find the creation date/system date as phase in date when the inventory part was created which is not good.

Example of the inventory part 303406 which I created today (04.06.2025 / DD.MM.YYYY):

I assume that the part revision record exists for your inventory part in your environment or am I wrong?

If if doesn’t exist then you have to create/migrate it.

If it exists then please have a look to the phase in date and also to the phase out date. In this record you will also find the revision no.

Back to your purchase_order_line_part issue.

The issue is related to the mapped value of the field planned_receipt_date if I’m not wrong.

When the planned_receipt_date is older than then phase in date of inventory_part_revision then you’ll get the error.

So I think you have to change the phase in date in your inventory_part_revision record.

You can map the field eng_chg_level with the function Inventory_Part_Revision_API.Get_Eng_Chg_Level(contract, part_no, planned_receipt_date) in the default value column of your migration job (source column must be empty) and then the revision no will be fetched if it exists and if it’s valid.

/Jens

Jens,

Good analysis !

As the products were loaded with a migration job, the revision record was not filled-in. So I’m going to add a new migration job to fulfill this part revision table with a date like 1/1/2024 so every purchase order will find a “nice” revision record and this will solve that issue.

Thank you