Limit Parameter Imported in Claims Shows a Different Start Date than the Start Date Defined in Product Definition (Doc ID 2068761.1)

Last updated on OCTOBER 16, 2016

Applies to:

Oracle Health Insurance Claims Adjudication - Version 2.14.2 and later
Information in this document applies to any platform.

Symptoms

On: Claims 2.14.2.0.14 version

When Start Date 01/01/0114 of a limit parameter is imported in Claims, it shows in the User Interface as a day later 01/02/0114.

A.
In Product Definition a cost sharing option has a wrong start date with value 01/01/0114. This is a user error.
The XML file generated from Product Definition shows for the limitCode startDate="0114-01-01".
When this file is imported into Claims, the product shows a limit parameter with start date 01/02/0114 in the UI.
Table rcl_prod_ben_spec_limits also shows this start date (01/02/0114). This is not expected since this does not match the start date in the XML file.
B.
When Configuration Migration functionality is used to export the product from the Claims environment, the XML file contains for the ProductBenefitSpecificationLimit startDate 0114-01-01.
When this file is imported in other Claims environments the product shows a limit parameter with start date 01/01/0114 in the UI.

In Product Definition and Claims there are products in the system with wrong dates. These need to be corrected.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.
In Product Definition:
a)
Create a product in Product Definition.
Make sure that under the parameter alias (NAV Configuration / Products / Parameters / Parameter Aliases), a limit is defined which you can use in Cost Sharing options in your product.
Make sure the date is not a valid date, for instance 01/01/0114.
b)
NAV Operations / Data Exchanges / Product Export Sets.
Create an export set for your product.
c)
NAV Operations / Data Exchanges / Outbound Data Sets.
Create the XML file and check that this productBenefitSpecRequest shows for the limitCode startDate="0114-01-01".
2.
In Claims environment 1:
a)
NAV Operations / Data Exchanges / Inbound Data Sets
Import the file from 1c)
b)
NAV Reference Data / Products / Product Benefit Specifications
Query the product involved and check that the UI shows limit parameter with start date 01/02/0114. This date is not expected.
c)
Run the following query to check the date in the table:
select * from rcl_prod_ben_spec_limits
order by creation_date desc
Here the start date matches with the start date seen in the UI (01/02/0114).
d)
NAV Operations / Data Exchanges / Configuration Migration Sets (CMT2)
Create a new Configuration Migration Set for the product involved.
e)
NAV Operations / Data Exchanges / Outbound Data Sets.
Create the export file.
File shows limitCode with startDate="0114-01-01".
3.
In Claims environment 2:
a)
NAV Operations / Data Exchanges / Inbound Data Sets
Import the file from 2e)
b)
NAV Reference Data / Products / Product Benefit Specifications
Query the product involved and check that the UI shows limit parameter with start date 01/01/0114.
So that does not match with Claims environment 1.




Cause

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