My Oracle Support Banner

Facing Error While Loading Pin_glid File After Adding New GLID (Doc ID 2678946.1)

Last updated on JUNE 11, 2020

Applies to:

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


Immediately after Pricing Design Center (PDC) migration, errors encountered while loading pin_glid file after adding a new General Ledger ID (GLID).

Below are the highlights:
1. Billing and Revenue Management (BRM) 7.5 system upgraded to 12 PatchSet (PS) 2.
2. PDC 12 and PDC-BRM Integration Pack PS2 installed.
3. Migration was successful.

As part of testing, the user tried to add the new GLID in the custom GLID file and loaded it successfully.
But, syncPDC failed with error as below.

>syncpdc $ grep SEVE syncPDC-20200420_074102_783.log
SEVERE: The description for GLID "1000066" has changed from "1000066_Late Fee" to "Late Fee" in BRM. But the name "Late Fee" is already used by an existing GLID in the PDC system. please use another name.
SEVERE: Exception executing SyncPDC job
SEVERE: Error while running SyncPDC!
SEVERE: SyncPDC Exception: Data migration Errors: One or more errors were encountered during data migration




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.