My Oracle Support Banner

Sequencer Does Not Check Missing Sequence in the System First Usage, Wrong Sequence Number (Doc ID 1292896.1)

Last updated on DECEMBER 05, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.4.0.0.0 [Release 7.4.0]
Information in this document applies to any platform.

Goal

According the Roaming Specification, each time a Public Land Mobile Network (PLMN) send a file with a jump in the sequence number, it needs to generate a Returned Account Procedure (RAP) (missing file) for this PLMN to claim the missing sequences files.

We processed the Transferred Account Procedures (TAP) File with Sequence 00002 [i.e.., CDARGTMARGTP00002] and CDARGTMARGTP00411. Since this wasn't the TAP file with Sequence 0001 [i.e.., CDARGTMARGTP00001], the system should generate a RAP File with sequence 00001 with a claim to the tap file CDARGTMARGTP00001, but this RAP wasn't generated. Instead, a RAP file RCARGTPARGTM00002 was generated. Sequencer does not check missing sequence in the first usage. As a result, wrong sequence number is generated

Registry Entries
==========

Solution

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
Goal
Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.