Error Bill Segments Don't Persist In Database On Bill Segment Generation Through Bill API

(Doc ID 2287505.1)

Last updated on JULY 24, 2017

Applies to:

Oracle Financial Services Revenue Management and Billing - Version to [Release 2]
Information in this document applies to any platform.


On : ORMB version, BI - Billing

Error Bill segments don't persist in database on bill segment generation through Bill API

Observed a weird behavior when I use Bill API to generate Bill Segments on Pending Bill in 2.5. This used to work in 2.4 versions.

When the bill segments are created without any error, everything works properly, but when Bill segments goes into error, BILLAPI creates the bill segment
with status 20 but it commits only the last bill segment id on DB, all other bill segments do not persist.

For ex: If there are 10 bill segments in error, it will return all 10 bill segments in code but when batch completes, only the last bill segment persists in database for that bill.

When using Bill API to generate Bill Segments, if Bill segments goes into error, BILLAPI should commit all the Bill Segment ID in error not just the last bill segment id on DB.

The issue can be reproduced at will with the following steps:
1. Generate Bill Segments using Bill API.

The issue has the following business impact:
If one of the bill segments is in error, no other correct segments will get persisted, but they have to , and hence bill will be incorrect


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