Add Component Effectivity Date Year 2050 On Engineering Change Orders (ECO) Form (ENGFDECN.fmb) Incorrectly Fails With Form Error FRM-40212: Invalid Value For Field OLD_OPERATION_SEQ_NUM
(Doc ID 2959722.1)
Last updated on JANUARY 29, 2024
Applies to:
Oracle Engineering - Version 12.1.3 and later Information in this document applies to any platform.
ENGFDECN.fmb: Engineering Change Orders Form
Error Code: BOM_INVALID_OLD_OP_SEQ, Error Text: FRM-40212: Invalid value for field OLD_OPERATION_SEQ_NUM.
Symptoms
The change order (ECO) form (ENGFDECN.fmb) raises an error while trying to add components for effectivity dates in year 2050 and beyond.
WORKAROUND
Use dates less than (<) 2050 like 2049 and works fine. Try with 2051/2052 as effectivity date and got same error.
ERROR
FRM-40212: Invalid value for field OLD_OPERATION_SEQ_NUM.
The error appears on the form as a pop-up or in the status bar.
The internal error code that maps to this message is the code "BOM_INVALID_OLD_OP_SEQ" that one might see in a trace file.
STEPS
1. Navigate to engineering > change orders > create change order with a date in year 2050 like January 1, 2050. 2. Enter revised item. 3. Enter component to disable. 4. Receive error.
WHY Using 2050? (BUSINESS IMPACT)
Business sets change orders with a far off future effectivity date as a holding location. The users return to the change order when it is ready to complete and put a valid, current date that could be a few months or a few years away. The users could enter 2049 as a workaround as this is still years in the future, however, they were trained to use 2050 and this is now not working. There are also many existing change orders with the 2050 date used.
Cause
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!