Issue with LookUp File in Enhancement Processor NPL (Doc ID 2229153.1)

Last updated on APRIL 25, 2024

Applies to:

Goal

On : 6.0.0.3.0 version,

Clarification needed for the following related to Lookup File:

The Country Prefix vs Country Code mapping information is cached for lookup during enrichment to identify the correct country description for a B NUMBER Enhancement Processor NPL.
The country prefix can vary from 2 digit to 8 digit number.

Example

91=IND
1720=USA
39=ITA
26297637=MYT

The issue is that country description is retrieved only when B Number is exact match of country prefix.For example if b_number passed is 91

b_number="91";
out.descr = Java.lookup(tablename,substr(in.b_number));

Here out.descr value comes as IND.

Now if b_number is 919000119001(91*) than country description is retried as Null.

Is there a way to handle this type of scenarios? Since we are caching huge entries into lookup file with various length and combination passing exact value is not possible.

Can we use lookup file to cache entries in CDR format?

For example:

CUST_ORG_ID| CUST_NO|CONTACT_INFO|CALLEDNUMBER| ARTICLE_NO|CHARGING_ID| CHARGING_ID_2| EVENT_ID|VALID_FROM|VALID_TO| ACC_EVENT_DESCR
 

Solution

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