Skip to main content

Hi,

 

We get this error in the mrp for one of our sites, error is recieved during the MRP snapshot summary :

Error ORA-20110: DeliveryRoute.ROUTEDATEPICK: Retrieving next work day from 02-FEB-53 using route has failed. The date is outside the interval of the calendar XXX. occurred while running Snapshot_Summary for Contract XXX.

 

We do not want to extend the calendar this far ahead and would like to find what is causing this issue. We suspect user error inputting some data but are not able to find what is causing it.

Checked parts with extremely long leadtimes, Demand far ahead, Supply chain matrix settings, Transport leadtimes

We are running IFS Apps 10

 

Any tips would be greatful

/Anna

Hi ​@atvanst,

I suggest to have a look to the MRP background job journal, where you can see the progress of the job until the error appeared. Just before the error you can see which kind of objects the MRP was handling, to narrow down your search. I would also check wanted delivery dates in customer order lines and receipt dates in purchase order lines.

Hope this helps!

Regards,

Pilar

Hi,

We already did and it’s when mrp takes the snapshop that the error occurs.

Dates on po lines and co line are checked

We even extended the calendar in another non-production environment run the mrp and error is gone. Then checked all dates again including ipap date required but could not find

It’s a mystery!

Hi ​@atvanst,

Sorry that my suggestion didn’t help...

If that’s the case, then you can create a support case so this can be debugged and investigated in your environment (better if it’s replicated in a non-PROD environment).

Regards,

Pilar

Hi Anna and Pilar,

I suspect this message comes when system tries to create a dummy date event in an MRP working table that is used to generate supply for safety stock. If there is no real net requirement for the part, but Qty Onhand is lower than safety stock, system will generate a PO/SO Req to replenish up to Safety Stock level. When creating this event system uses “Purchase Order Date logic” to look forward for first possible supply date for the purchased part.
I think it goes wrong here for “1” of your let say 50 000 purchased parts.

Really good input for us. Of course we should try to capture the PART NO in the error message.

Create a support case :-)

Cheers,

Mats

Hi,

We finally managed to find a part with extremely long leadtime that caused this error and issue is now solved.

Part no information in these types of  errors would be great to have. Would save us a lot of time :-)

/Anna

Hi,

We finally managed to find a part with extremely long leadtime that caused this error and issue is now solved.

Part no information in these types of  errors would be great to have. Would save us a lot of time :-)

/Anna

Hi ​@atvanst ,

This is, indeed, could be a good improvement for the process. Please, create a new Idea in IFS Community so R&D can review this and consider to implement in future releases.

Regards,

Pilar

Idea added

 Site and part no should be included in all mrp errors | IFS Community

Reply


Terms & ConditionsCookie settings