GLID Constraint Error When Using SyncPDC
Last updated on MAY 19, 2016
Applies to:Oracle Communications Pricing Design Center - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 11.1.0]
Information in this document applies to any platform.
The user is developing the GL solution which needs to create 4 GL segments, each one represent a geographical location. As required by BRM, each GL Segments contains the GLID they need to use. The same GLID has been used within multiple segments, and in each segment, the internal configuration of the GLID is different as required by BRM.
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