My Oracle Support Banner

Result Line Sequence Number (Doc ID 2491829.1)

Last updated on MARCH 25, 2019

Applies to:

Oracle Health Insurance Enterprise Policy Administration - Version 3.18.3.0.0 and later
Information in this document applies to any platform.

Goal

In release 3.18.2 the field financialTransactionDetail.sequenceNumber was used to match to calculationResultLine.sequence (to find the result line for a specific financial transaction detail). In release 3.18.3 this does notwork any longer as in the object model always returns null for financialTransactionDetail.sequenceNumber. In the database, Financial Transaction Detail Sequence Number does have correct values. They just don't seem to be available through the object model (even though the sequenceNumber attribute is still present).

The release notes for 3.18.3 indicate a new attribute 'resultLineSequenceNumber' has been added to financialTransactionDetail. This does in fact have a value (both in the object model and the database).

In the implementation guide for 3.18.3 the financial transaction detail sequence number description is as follows:

The unique identifier of the financial transaction detail within the financial transaction. For types Premium and Premium Based Commission the value for this field is set to the corresponding calculation result line or commission result line sequence; for type Fee the value is set to 1.

This would imply it could be used. The implementation guide has provided a description for the new Referenced Sequence Number field but has no mention of the Result Line Sequence Number field. Likewise, in the release notes there is no mention of not being able to use financialTransactionDetail.sequenceNumber and needing to switch to the new 'resultLineSequenceNumber' field.

Is it necessary to now use resultLineSequenceNumber to match a transaction to the result line? If so, shouldn't this field be included in the implementation guide and be mentioned as a dynamic logic impact in the release notes?

Is the financialTransactionDetail.sequenceNumber field obsolete or not available in dynamic logic for another reason?

 

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
References


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