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

Last updated on FEBRUARY 22, 2017

Applies to:

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


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.

-- Non Ordered Circuits

SET CLR_PRI_NL_ADDR_LN1 = i_ref_addr_data_record.addr_ln1,
CLR_PRI_NL_ADDR_LN2 = i_ref_addr_data_record.addr_ln2,
CLR_PRI_NL_ADDR_LN3 = i_ref_addr_data_record.addr_ln3,
CLR_PRI_NL_ADDR_LN4 = i_ref_addr_data_record.addr_ln4,
CLR_PRI_NL_GA_INSTANCE_ID_CITY = i_ref_addr_data_record.ga_instance_id_city,
CLR_PRI_NL_GA_INSTANCE_ID_STAT = i_ref_addr_data_record.ga_instance_id_state_cd,
CLR_PRI_NL_GA_INSTANCE_ID_COUN = i_ref_addr_data_record.ga_instance_id_country,
CLR_PRI_NL_POSTAL_CODE = i_ref_addr_data_record.postal_cd
                             FROM asap.circuit CIR ,
                                  asap.serv_item SI
                             WHERE CIR.location_id = 22546 and                   <--- HARD CODDED LOCATION_ID
                             CIR.circuit_design_id = SI.circuit_design_id and
                             SI.cust_acct_id is NULL and
                             not exists( select 1
                                         from asap.srsi_sr_loc SSL
                                         where SI.serv_item_id = SSL.serv_item_id and
                                         SSL.serv_loc_use = 'PRILOC' ) and
                                         not exists( select 1
                                                     from asap.si_loc SL
                                                     where SI.serv_item_id = SL.serv_item_id and
                                                     SL.serv_loc_use = 'PRILOC' ));

Expected Behavior

Code should NOT have a hard coded LOCATION_ID value.



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.



Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms