My Oracle Support Banner

Special Characters From PricingXMLs are Loading Junk Characters in BRM/PDC DB and ECE Cache (Doc ID 2793064.1)

Last updated on JUNE 22, 2022

Applies to:

Oracle Communications Pricing Design Center - Version and later
Information in this document applies to any platform.


Customer have multiple pricing Extensible Markup Language (XMLs) having special characters to support specific country Locale requirement. post loading from PDC, it is getting loaded properly in Billing and Revenue Management/Pricing Design Center(BRM/PDC) Database(DB) and Elastic Charging Engine(ECE) Cache in ON PREMISES setup. But, the same set of files tried to load in Cloud native setup. it is loaded the pricing setup with JUNK characters and also synced with junk characters to all BRM/ECE as well.

PDC DB content:
F��retag 20GB-1744
F��retag Alltid-1620
F��retag L-1620
F��retag M-1620
F��retag S-1620
F��retag XL-1620

BRM DB Content:
F??retag 20GB-1744
F??retag S-1620
F??retag Alltid-1620
F??retag L-1620
F??retag M-1620
F??retag XL-1620

ECE Cache content:
CohQL> select value().get().name from ChargeOffering where value().get().name like ' F%';
" F??retag L-1620"
" F??retag S-1620"
" F??retag XL-1620"
" F??retag Alltid-1620"
" F??retag M-1620"
" F??retag 20GB-1744"

PDC XML Content where the special Characters setup correctly with UTF8 encoding.
__Foretag_Alltid-1620_pricing.xml: Företag Alltid-1620.monthly_3
__Foretag_Alltid-1620_pricing.xml: Mobilt Företag Alltid SEK
__Foretag_Alltid-1620_pricing.xml: Företag Alltid-1620.monthly_1


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

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