This content has been marked as final. Show 8 replies
Pl post details of OS, database and EBS versions. How did you update the table ? Directly updating base tables using SQL is not supported - hopefully you used an API. This error is typically caused when there are leading/trailing spaces in the data. Check by comparing the LENGTH function of the column with the LENGTH function of the column after LTRIM and RTRIM
You can also see this threads:
(On the block, set the property value of "DML Returning Value" to "Yes")
--(Check if you have any custom database triggers on MTL_SYSTEM_ITEMS_B)--
Edited by: stefan nebesnak on Feb 2, 2013 6:14 AM
Pl post the update statement used. Have you checked the LENGTH of the columns for those 8 updated rows ?
See the troubleshooting steps in these MOS Docs (assuming leading/trailing spaces is the issue)
How To Troubleshoot FRM-40654 Errors On Purchasing Documents? [ID 1203796.1]
How to Find and Fix FRM-40654 errors in MTL_CATEGORIES_B? [ID 1243085.1]
One way to recover would be to restore the database from a previous good backup
Thank you all for the continuous reply,
Please see query the was used. Thanks
update mtl_system_items_b set
SECONDARY_DEFAULT_IND = 'D'
TRACKING_QUANTITY_IND = 'PS',
DUAL_UOM_DEVIATION_LOW = 100,
DUAL_UOM_DEVIATION_HIGH = 100,
SECONDARY_UOM_CODE = 'PCS',
where segment1 = 'K5000078'
Ouch - I would recommend you open an SR with Oracle.
Maybe an FRD trace may help
R12: Forms Runtime Diagnostics (FRD), Tracing And Logging For Forms In Oracle Applications [ID 438652.1]
Steps To Take FRD Trace in 11.5.10 & R12 [ID 867943.1]
How To Collect And Use Forms Trace (FRD) in Oracle Applications Release 12 [ID 373548.1]