Entity corrections require information unique to the particular instance that is typically not provided by the interface, for example, the reason for the correction. Some types of entity corrections require even more specific details in order to produce the mass action. For example, the mass suppression entity correction type requires a suppression reason and suppressed entity to be defined. The product supports two different entity correction lifecycles based on whether or not the additional information is needed prior to the validation of the entities.
For use cases where the addition information is not required for validation of the entities, the business object C1-EntityCorrectionControl (Entity Correction) is provided.
A record is created from an external source and can be validated without any input from a user.
Once the record is validated, it is set to Approval in Progress at which time a user group is alerted via a To Do entry.
If a given business use case does not require any additional information besides a correction reason and comments, this business object may be used as the transaction BO. The mass tax form cancellation and mass payment cancellation use cases use this business object. If a given business use case requires additional data where the user can provide the data when approving the record (i.e. it's not needed for validation) then this business object may be extended. The base business object C1-MassSuppressionForTaxpayers (Mass Suppression for Taxpayers) extends this business object.
For use cases where the additional information is required for validation of the entities, the business object C1-EntityCorrectionExtraInfo (Entity Correction - Detail Validated) is provided. Once the additional data is provided the user transitions the record to pending to be picked up for validation. Once the record is validated, it is set to Approval in Progress at which time a user / group of users can be alerted via a To Do entry.
This business object is not expected to be used for any business use cases because by definition, additional data is expected from a user prior to validating. As such the expectation is that this BO is only used as a lifecycle BO for other business objects.
For a business use case that requires additional data prior to validation, this business object is extended. The business objects C1-OverdueCorrectionControl (Overdue Correction) and C1–MassSuppressionRelease (Mass Suppression Release) extend this business object.
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]