My Oracle Support Banner

File Request Type Based Entity(invoice Account) Creation Resulted In Data Inconsistency. (Doc ID 2812021.1)

Last updated on OCTOBER 25, 2021

Applies to:

Oracle Financial Services Revenue Management and Billing Cloud Service - Version NA and later
Information in this document applies to any platform.


On : NA version, MICC Transfer to TSC

File request type based entity(invoice account) creation resulted in data inconsistency.

Customer solution is having a FRT based interface to create invoice account based on transacting account copy. Input transacting account meta data from input feed is used to replicate invoice account. Address lines from transaction accounts are also copied to bind with invoice account as per requirement. We are using the COPY function with zone based business service to read transaction account address lines and map it with invoice account route definition data area. If address line has an consecutive empty space, these lines are annotated with CDATA indicator during FRT COPY function. Such annotated address lines are missing from invoice account route definition.

Not sure why the Hold Request monitor cancelling the Overdue Process for an account that has a end date in the past. How is the business user suppose to remove the account from the Hold Request?

Suppose addressline1 value is TESADDRESSLINE1 & <>
What will be the addressline1 value after the COPY function call? The input address line length is 34.
We expect to retain the address line length of 34 even after the CDATA handling.


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.