EBilling Account Creation Fails Due To Table Column Length Constraints
Last updated on FEBRUARY 28, 2018
Applies to:Oracle Self Service E-Billing Business Edition - Version 6.2 and later
Information in this document applies to any platform.
On: 6.2 version, E-Billing B2B
eBilling account creation fails due to table column length constraints
The customer has integrated eBilling product with siebel CRM to sync customer account information. Table definition in siebel is in characters whereas ebilling table definition is in bytes.
The customer has one scenario where their client account name has 100 characters (which includes french characters) created in siebel but while creating same account in eBilling it is failing as data is having more number of bytes than allowed size of table column in ebilling. Allowed size in ebilling in 100 bytes.
Since the client is having french characters in his name, while converting characters to bytes it will not the same. Due to this issue the customer couldn't load invoice data into ebilling and whole invoice batch is getting rejected due to single issue with this client.
The issue has the following business impact:
This problem becomes more worst during month ends as we do have huge volume of month end data during those days. This is highly impacting our business and we have no why to fix this issue.
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