Hi Monika Demla,

Have converted this JIRA from Support Activity to Bug as code fix will be required.

Following are the 3Cs:
Concern:
Billing Report is not producing records for TrustMark Products. Trust mark products are user defined.

Cause:
Billing report was being pulled for the month of November 2017.
Employee Deborah Pullen has Accident plan election, effective from 11/1/2017. When cost is defined on Rates, it has termination date set on it. But as this is user defined benefit type, the table(RateChanges_Log) in which cost data is stored has NULL termination date saved for this election. While executing the Billing report there is separate query to process data with future effective date. In that query, NULL termination date was getting treated as 1/1/1900 which is why this record was not appearing on the report.

Correction:
Have changed the query to process NULL termination date appropriately for elections with future effective date. Please note that this issue is not there for ongoing elections, as query to process ongoing elections is different.

Affected files:
OES_SP_GetBillingDetails

Impacted Areas:
Billing Section for elections with future effective date.

Unit tested scenario:
Election with future effective date having NULL termination date stored in cost table.

Please note that, currently fix is deployed on Charleys company only. Fix will be deployed on all Production companies as per process.

Please let us know if anything more is required.

Thank you!

cc: Gaurav Sodani, [~meghana joshi], Sachin Hingole

[~meghana joshi]

While doing issue fix, we have fixed following issue too related to election with future effective date:
#2
Concern:
When no rate is mapped to a plan, elections with future effective date are not appearing on Billing Report with 0 cost.

Cause:
While filtering the data, employee and plan filter was applied on data from cost table. In this scenario, as there is no rate mapped, no cost data is present against an election. Due to this records with 0 cost were not appearing on report.

Correction:
While applying filter for employee and plan, have referred Enrollment table instead of cost table

Affected files:
OES_SP_GetBillingDetails

Impacted Areas:
Billing Section for elections with future effective date with and without rate mapped.

Unit tested scenario:
Elections having no rate mapped

Thank you!

cc: Gaurav Sodani, [~meghana joshi], Sachin Hingole

Hi Prasanna Karlekar

I have verified this issue on LB

Verified with Partner and Employee Login

Verified with Company " City of Durham "

Its working fine

Biiling Test Report.xls

Hence, Marking it as ready For Stage

cc: Sachin Hingole Prasad Pise Rakesh Roy Hrishikesh Deshpande

Thank You !

Hello Prasanna Karlekar

I have verified this issue on Stage

Verified with Partner and Employee Login

Verified with Company " TIBCO For HSPL"

Its working fine
WT-11716.xls

Hence, Marking it as ready For Production

cc: Sachin Hingole Prasad Pise Rakesh Roy Hrishikesh Deshpande

Thank you !

Hi all,
Can we close this?

Hi Monika Demla,

We cannot close this JIRA as it not Production deployed.
Will check and provide an update related to Production deployment date for this ticket.

Thank you!

cc: Gaurav Sodani, [~parmeshwar.jumbade]

This is related to Billing Details report

Hi All,

Attaching the development approval email for your reference

Regards
Gaurav

Hi All,

This ticket has been approved for stage deployment on 12/21/17.

Regards
Gaurav

Hi Prasanna Karlekar,

It seems there is issue in November month billing report. When I pulled report from 11/01/2017 - 11/30/2017 I got only one record which is of Reported Employee "Deborah Pullen".

If I run Enrollment report effective from 11/01/2017 I got many records, If those enrollments not done in November then it some should adjusted in December Billing.

• Enrollment report has 167 record in Accident plan, Count on Decemnber Adjustment is 145, It should be 166.
• Enrollment report has 52 records in Universal Life Events plan, Count on Decemnber Adjustment is 50, it should be 52.

can you please check same?

Thanks,
Hrishikesh.

Hi All,

Attaching the production deployment approval email for reference

Regards
Gaurav

Hi Hrishikesh Deshpande,

Following are the updates:
#1: It seems there is issue in November month billing report. When I pulled report from
11/01/2017 - 11/30/2017 I got only one record which is of Reported Employee "Deborah Pullen".

• In the month of November, Deborah Pullen was the only election that had cost assigned. Hence, you got only 1 record on Billing report.

#2: Enrollment report has 167 record in Accident plan, Count on Decemnber Adjustment is 145, It should be 166.

• Ran Enrollment report for Nov 2017, it is showing 145 records. Executed Billing Report for Dec 2017, it has 146 adjustments(145 debits + 1 credit record) for month of Nov 2017. So record count on, Enrollment-Nov 2017 report and Billing Nov 2017 adjustments in Dec 2017 report matches correctly.

#3: Enrollment report has 52 records in Universal Life Events plan, Count on Decemnber Adjustment is 50, it should be 52.

• Ran Enrollment report for Nov 2017, it is showing 52 records. Executed Billing report for Dec 2017, it has 52 adjustments for month of Nov 2017. So record count on, Enrollment Nov 2017 report and Billing Nov 2017 adjustments in Dec 2017 report matches exactly.

Verified the data from front end as well as back end. In all above scenarios, Billing report is functioning as per implementation.
My apologies. Forgot to share following with you on Friday 29-Dec-2017, when we had discussion on this issue:
If no cost is assigned to an election, it will appear with 0 cost in Billing section as part of missing data. So Billing Report - Billing section's record count will match directly with Enrollment report's record count. But same is not the case with Adjustment section. Retro records which do not have cost assigned will not appear in adjustment section with 0 cost.
This can be the reason for discrepancy, when you compared Enrollment record count with Billing report's adjustment section record count.

Kindly reconfirm mentioned issues at your end once again.

Thank you!

cc: Gaurav Sodani

Hi Monika Demla,

This issue has been fixed and tested on Production.

Thanks,
Hrishikesh.