The following topics highlight functionality common to all entity correction use cases.
Entity corrections are created via an interface. The expectation is that analysis is performed using an appropriate reporting or analysis tool to determine the records that require a special action to be performed. The appropriate records for the use case in question are selected in that tool and interfaced to the system.
The types of records (referred to as Entities here) linked to the entity correction depend on the type of entity correction. For example, an entity correction for mass cancellation of tax forms expects tax forms to be linked to the entity correction. An entity correction for mass suppressions of taxpayers expects person IDs to be linked.
Some types of records have an external reference. For example, a tax form has a DLN; a person has an ID number. If the algorithms for the particular use case support it, the external ID may be provided when creating the entity correction.
The Link Status refers to the status of a particular entity to a particular entity correction. The following points highlight the status values.
When an entity is initially linked it has a link status of Active. Only entities linked as active are considered eligible for the mass action once the entity correction is approved.
An entity's link status may change to Skipped by the validation if the algorithm detects that some condition related to the entity is not appropriate for the mass action. For example, if the action is to cancel a record but it is already canceled, the record will be skipped. Each type of entity correction would have different rules for what causes the link status to change to Skipped. When setting the link status to Skipped the algorithms should also indicate an appropriate Skipped Reason so that it is clear when reviewing the results why the records were skipped. Also note that the algorithm that attempts to perform the mass action should recheck for conditions that may change in the time between running the validation algorithm and the correction algorithm. For example, a tax form to be canceled may be in the Suspended state when running the validation algorithm but before running the correct entity algorithm someone may cancel the record. In this scenario, the correct entity algorithm will not do any action and will indicate that the record is skipped at that point.
An entity's link status may change to Invalid by the validation if appropriate record cannot be found in the system. This may occur if internal IDs are provided or if external IDs are provided by the interface.
An entity's link status may change to Duplicate if it is found that the record is listed twice in the list for a given entity correction.
Once the entity correction and its list of entities are validated, the system transitions the record to Approval in Progress and a To Do entry is created to alert the appropriate user(s). At this point, the reviewing user may Approve or Reject the record.
Once a user approves an entity correction, a batch process processes the linked entities to perform the mass action. The action performed depends on the business use case.
The expectation is that this process is part of the nightly batch cycle. As such there may be a delay from the time that an entity correction is approved to the time its related entities are impacted by the action that is performed.
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]