Skip to main content
Question

IFS Cloud - 24R1 SU20 Issue

  • February 26, 2026
  • 2 replies
  • 67 views

Forum|alt.badge.img+7

Hello our wonderful IFS Community :)


We’re running IFS Cloud 24R1, applying SU20 to a pilot instance for evaluation (going from SU9). We’ve encountered an issue when receiving goods off of a Shop Order, complaining that an Expiration Date is mandatory. I’ve limited things down to something that appears correct in the SU9 version of the API INVENTORY_PART_IN_STOCK_API and a variable check_mandatory_expire_date_ that is referenced in the Check_Insert__ / Check_Common__ procedures.

Here’s a sample of the check_mandatory_expire_date_ being set (as opposed to the DEFAULT value for the parameter taking place. Anyone encounter an issue like this when going to SU20?

 

Error message:

ORA-20124: Error.NULLVALUE: Field [EXPIRATION_DATE] is mandatory for Inventory Part In Stock and requires a value.

INVENTORY_PART_IN_STOCK_API package body snippet:

-- Bug SCZ-27258, Start
   check_mandatory_expire_date_   BOOLEAN := TRUE;
   -- Bug SCZ-27258, End

Many thanks, and feel free to let me know if you’d like additional context or not :)

Regards,

Randy

2 replies

Forum|alt.badge.img+5
  • Sidekick (Customer)
  • October 2, 2026

Hello! Do you have any updates on this issue? We encountered the same problem in May this year while on 25.1.9, but found a workaround: we counted out a quantity of 1, which allowed us to unreceive the shop order quantity. We then counted in a quantity of 1 and unreceived it. After upgrading to 25.1.12, we encountered the issue again today. The part lot batch and stock record both include the expiration date, so we’re unsure why the system is reporting that a mandatory expiration date is required.


Forum|alt.badge.img+7
  • Author
  • Sidekick (Partner)
  • October 2, 2026

Hi ​@ghlsunayanav - sorry, unfortunately I do not. It ended up being some sort of data configuration that likely was root cause, but I can’t exactly recall…

I think the column Mandatory Expiration Date on the Inventory Part record had something to do with it, but again, not exactly sure what the root cause was.