My Oracle Support Banner

Work Order Number greater than 30 characters causing issue with costing (Doc ID 2536976.1)

Last updated on MAY 03, 2019

Applies to:

Oracle Cost Management - Version 12.2.5 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.5 version, Work Execution

Work Order Number greater than 30 characters causes issue with costing

1. Created a work order with a work number of 30 characters, it estimated and costed with no issues.
2. Copied the work order so it was exactly the same. Added 2 characters to the work order number so it is now 32 characters. The estimator and cost manager error out.
3. Changed the work order number from 32 to 26 characters. It estimated and costed with no issues.


ERROR
-----------------------
Estimated the work order (with 32 characters) and it receive error that character buffer too small.

1. ORA-06502: PL/SQL: numeric or value error: character string bugger too small in Package CST_eamCost_PUB Procedure InsertUpdate_eamPerBal: Statement-300
2. insertupdate_eamperbal error in Package CST_EAMCOST_PUB Procedure COMPUTE_JOB_ESTIMATES(120):
3. Error:CST_EAMCOST_PUB.compute_job_estimate()in Package CSTPECEP Procedure ESTIMATE_WORKORDER(400):


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

1. Create Work Order with 32 characters
2. Run Estimate and Cost Work Order
3. Receiving Error -
   ORA-06502: PL/SQL: numeric or value error: character string bugger too small in Package CST_eamCost_PUB Procedure InsertUpdate_eamPerBal:
   Statement-300

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.