My Oracle Support Banner

Transaction Manager Errors With Negative balances not allowed|ORA-06502: PL/SQL: numeric or value error: character string buffer too small in Package CST_Utility_Pub Procedure getTxnCategoryId (Doc ID 2513487.1)

Last updated on FEBRUARY 23, 2021

Applies to:

Oracle Inventory Management - Version 12.2.7 and later
Information in this document applies to any platform.

Symptoms

On :  12.2.7 version, Inventory Transactions

ACTUAL BEHAVIOR  
---------------
When creating transactions using Transaction Open Interface (Say Project Transfer),

although input is having project id and task id , the transaction is created without task id and cost group is not cost group of project.

This is happening because the previous 5 transactions errored with "Negative Balances not allowed" in the following stacked messages order.

1) Negative balances not allowed
2) |Negative balances not allowed|Transaction processor error Negative balances not allowed
3) |Negative balances not allowed|Transaction processor error |Negative balances not allowed|Transaction processor error Negative balances not allowed
4) |Negative balances not allowed|Transaction processor error |Negative balances not allowed|Transaction processor error |Negative balances not allowed|T
5) |Negative balances not allowed|ORA-06502: PL/SQL: numeric or value error: character string buffer too small in Package CST_Utility_Pub Procedure getTx
6) The 6th transaction is successful but with wrong data of blank task_id and wrong cost_group_id.

But the issue does not happen if TRANSACTION_BATCH_ID is populated with NULL value.

EXPECTED BEHAVIOR
-----------------------
When creating transactions open interface, if there are errors - the errors
should be individual and should not be appended for the next records - thus
avoiding ORA-6502 error and in turn not corrupting the data in the same batch.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1) Load 6+ records in MTL_TRANSACTIONS_INTERFACE with Transaction_batch_id populated.
2) Make sure that all these 6 records gets into error (by making onhand not available)
3) Check the error message stack - you observe the error messages got appeneded by previous error message.


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!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.