The product provides two ways to create a refund control and link overpayments to the refund control
A user may manually create a refund control and define criteria such as tax type, overpayment process type and maximum amount. (Note that the exact criteria is determined by the business object). The refund control is then "validated" where an algorithm uses the criteria to select overpayment processes and then becomes eligible for approval.
A refund control and its overpayments are created via a web service. This mechanism is used if an implementation chooses to do some analysis in a separate analysis tool and selects a list of overpayments to refund in the external tool. The expectation in this case is that analysis tool produces a file and that an appropriate mechanism like Oracle Service Bus transforms the file and interfaces the information via a web service call.
The refund control type includes configuration to indicate whether criteria is provided or whether the explicit list of IDs are provided. Note that the product does not provide any user interface mechanism for defining overpayment IDs manually. The IDs Provided option is meant for the case where a web service call creates the refund control and its list of IDs.
Regardless of the mechanism for creating refund controls, the record is created in the Pending status. The base product attaches a deferred monitor to the pending state so that the validation / selection of the IDs occurs in batch allowing for large volumes. Depending on an implementation's business practice, this deferred monitor may be one to run often during the day.
Once the record is validated, it is routed for approval. Refer to Refund Control Approval for more information.
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]