APAYRA Having Performance Issues Due To Overdue Review Per Transaction Level Match Event
(Doc ID 2290661.1)
Last updated on MARCH 19, 2019
Applies to:Oracle Financial Services Revenue Management and Billing - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On : 18.104.22.168.0 version, BT - Batch
APAYRA is having performance issues due to Overdue review per transaction level Match Event .
Experiencing performance issues for APAYRA and other such processes that create/update match events due to the base match event/overdue review processing routine.
There is a base routine (CIPFMEVN) which sets the match event status. It reviews the account’s active overdue process (if any). This is triggered by various processes, including the match event service (CIPFMVTP), when a match event is added or changed. The level at which UHG does matching (i.e. transaction level) is causing the overdue review process to be triggered multiple times.
In the Production scenario where the performance issue was raised, a large payment was being processed through the APAYRA process and we saw that the overdue cancel criteria algorithm (which is triggered by the base review account overdue process) was triggered 300 times, for a single tender.
With the need to do transaction level matching for healthcare employer groups, we would like Product to reassess the current match event/overdue review processing and determine the best way forward. Our thought is to provide a way for implementation to disable this (e.g. through an installation option), so that it can be turned off if transaction level matching is being done.
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