Skip to main content

Hi all,

We run IFS Cloud Web version: 24.2.9.20250806053050.0..

I get the following error while running MS - One Part and currently no clue how to fix this. I run the standard IFS functionality.

Where do we start to tackle this error?

 

Error ORA-01400: cannot insert NULL into ("IFSAPP"."MTR_ORDER_TAB"."ORD_REF4") occured while running LEVEL_1_PROJ_FORECAST_UTIL_API.Calculate_Ms_Receipt_for Site/PNG/PartNo/Ms Set 

 

 

Kind regards,

 

Evert

Hi ​@Evert 

You can follow the steps below to analyze this issue further:

  • Run the process for another part or MS set: If the issue doesn’t occur elsewhere, it’s likely data related (specific to the part, site, or forecast combination).
  • Compare with a working case: Identify a part/site combination where the process runs successfully and compare the related setup details.
  • Enable debug mode: Turn on debug logging from the application and review the server logs or error stack to trace where the NULL value is being passed.

If this is part of the standard flow without any customizations or custom events, you may raise a support case with the relevant details for further investigation.

Best Regards,

Sonali

Hi Sonali,

Thanks for the reply.

  1. I ran the process for another part and there is no error on my other parts. And this pointed me towards the data related part of your reply.
  2.  Setup is the same and this i had checked before posting here :)
  3. I will try this next time with one of our application administrators to tackle the error.

For now I found a misaligment in our customer orders. This was connected to another activity within the project, but on this activity we only send customer owned stock (part of our RMA-proces). The order was made with a part with setting company owned and not customer owned. This made IFS err, during this process. Why I do not know, but I managed to fix the problem and can run the process again.

 

Kind regards,


Evert

Hi Evert,

I’m back and again you have run into a new defect :-( I repeat myself from the previous chat we had :-)

You should report this as a defect. You need to create a support case Please make sure you are mentioning that this is about Project Master Scheduling. 

The good news is that the defect is easy to correct.

Around two years back in time we did a fix in PMRP and Material Transfer Requisitions to support by-products/co-products better. Unfortunately we see an unknown side effect of this correction in Project Master Scheduling.

(in between did u report the previous problem?)

Cheers,

Mats

Terms & ConditionsCookie settingsAccessibility statement