My Oracle Support Banner

Hard Coded LOCATION_ID Value Of 22546 In ASAP.PKG_ADDRESS_UPDATE_IMPACT (Doc ID 2114458.1)

Last updated on MARCH 14, 2019

Applies to:

Oracle Communications MetaSolv Solution - Version 6.2.1 and later
Information in this document applies to any platform.

Symptoms

MetaSolv Solution version 6.2.1

Actual Behavior 

There are 4 UPDATE statements in the ASAP.PKG_ADDRESS_UPDATE_IMPACT object that have a hard coded LOCATION_ID value of 22546 in the WHERE clause of its subquery. 2 are in the SP_PROCESS_CLR_UPDATE procedure and 2 are in the SP_PROCESS_DLR_UPDATE procedure. The example below was taken from SP_PROCESS_CLR_UPDATE procedure.



Expected Behavior

Code should NOT have a hard coded LOCATION_ID value.


Steps

N/A


Business Impact

Due to this issue, the code will never update rows because of the nearly impossible probability of encountering the hard coded "CIR.location_id" value.

 

Changes

 

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
Changes
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.