Handling Duplicate Requests

A request that affects the same retroactive benefit/deduction information as a previous request is considered a duplicate request.

The duplicate resolution process differs, depending upon the types of request that are involved (individual or mass) and the status of the initial request.

Individual Requests

When the system encounters duplicate individual requests with different effective dates, it attempts to use the earlier date for processing.

When a duplicate individual request is triggered and the initial individual request is not processed, the system compares the effective dates of the two requests, keeps the request with the earlier effective date, and deletes the request with the later effective date.

If the initial request is calculated, the system compares the effective dates of the two requests, marks the previously calculated request Not OK to Process, sets the status to Invalidated, sets the Duplicate Flag to Y (yes), and gives the new request the earlier of the two effective dates.

Mass Requests

For duplicate mass requests, the system checks the status of the initial request. If it is Not Processed or Calculated, the system marks both requests Not OK To Process. You will have to examine both requests and decide which one to run.

This process is also followed when one of the duplicate requests (either the original or the duplicate) is an individual request, while the other is a mass request.