The GEOCODE Field Is Being Reset To NULL Upon Editing Contact Info
Last updated on AUGUST 17, 2015
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.5.0]
Information in this document applies to any platform.
The GEOCODE field is being reset to NULL upon editing/saving contact info from Customer Center. In addition TAXPKG_TYPE is being set to 0. This issue is consistently happening for all accounts.
SQL for account before edit:
INNER JOIN ACCOUNT_NAMEINFO_T ANIT ON ACCOUNT_T.POID_ID0 = ANIT.OBJ_ID0
ACCOUNT_T.POID_ID0 = 1929340;
1929340 Pittsburgh PA 15212 390033040 3
After changing the city to Wexford PA and the zip to 15090 the results are:
1929340 Wexford PA 15090 0
GEOCODE field should not get reset to NULL, instead it should remain the existing value e.g 390033040 in the above scenario.
The issue can be reproduced at will with the following steps:
1) Verify that GEOCODE on ACCOUNT_NAMEINFO_T has some value
2) Edit contact info of an account through Customer Center
3) Notice that contact info is updated correctly but GEOCODE getting reset to NULL, in addition TAXPKG_TYPE is being reset to 0( from original value 3)
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms