Algorithms Used in C1-DisputeRequest
The following table lists the algorithms which are attached to the C1-DisputeRequest business object:
System Event | Algorithm | Algorithm Type | Description |
---|---|---|---|
Information | C1-DSPTRQINF | C1-DSPTRQINF | This algorithm generates the dispute request information
string which appears throughout the application. It concatenates the
following fields:
|
Validation | C1-DSPTVADN | C1-DSPTVADN | This algorithm validates following: Draft status validations:
|
The following table lists the algorithms which are used in the lifecycle of the C1-DisputeRequest business object:
Status | System Event | Algorithm | Algorithm Type | Description |
---|---|---|---|---|
Submitted | Enter | C1-DISPUTSUB | C1-DISPUTSUB | This algorithm checks the following:
|
Submitted | Enter | C1-DPTSTAUPY | C1-DPTSTAUPY | This algorithm is used to stop auto pay on bill. Parameter – Characteristic Type Characteristic Type is used to add the characteristic which is stamped on the bill to postpone overdue process |
Dispute | Monitor | F1-AT-RQJ | F1-GEN-BOMNJ | This algorithm type transitions business object current state to the input Next Status or to the status related to the input Next Transition Condition. Either one but not both soft parameters may be specified. If both soft parameters are not specified, the business object will be transitioned to the default next status specified on lifecycle. Algorithms of this algorithm type may be defined for any business object status as its monitor algorithm. |
Dispute | Enter | C1-DPTSTAUPY | C1-DPTSTAUPY | This algorithm is used to stop auto pay on bill. Parameter – Characteristic Type Characteristic Type is used to add the characteristic which is stamped on the bill to postpone overdue process |
Creating Adjustments | Monitor | F1-AT-RQJ | F1-GEN-BOMNJ | This algorithm type transitions business object current state to the input Next Status or to the status related to the input Next Transition Condition. Either one but not both soft parameters may be specified. If both soft parameters are not specified, the business object will be transitioned to the default next status specified on lifecycle. Algorithms of this algorithm type may be defined for any business object status as its monitor algorithm. |
Creating Adjustments | Enter | C1-ENTERADJS | C1-ENTERADJ | This algorithm is executed on submit or on approve of an
dispute request. It creates the adjustments which will be swapped
on the current or next bill. Adjustment are created with below logic Unpaid Bill logic
|
Status | System Event | Algorithm | Algorithm Type | Description |
---|---|---|---|---|
Paid Bill logic
Partial Bill Logic
There are four parameters for this algorithm.
Parameter 1 – Adjustment on Next Bill (Required)
Parameter 2 – Match Type Entity Flag (Required)
Parameter 3 – To Do Type
|
Status | System Event | Algorithm | Algorithm Type | Description |
---|---|---|---|---|
Parameter 4 – Characteristic Type
|
||||
Approval In Progress | Enter | C1-DSPTAPP | C1-DSPTAPP | This algorithm creates the following:
|
Approval In Progress | Exit | F1-TODOCOMPL | F1-TODOCOMPL | This algorithm type completes To Do entries that are linked to an object when the object exits a given state. The system finds all open To Do entries with drill keys for the current business object's primary key, and completes them, unless the To Do entry's type has been configured with an Exclude To Do Type Characteristic Type indicating that it should not be automatically completed. |
Approved | Enter | C1-DSPAPPRVD | C1-DSPAPPRVD | This algorithm is triggered when the approver clicks the Approve button. It checks whether the approval is required from users at the next level in the approval hierarchy. If the approval is required from the next level in the approval hierarchy, the status of the dispute request is changed to Approval In Progress and the algorithm attached to the Approval In Progress status is invoked. If further approval is not required, the status of the dispute request is changed to Creating Adjustment. |
Return to Submitter | Enter | C1-DSPTRESUB | C1-DSPTRESUB | This algorithm is invoked on Re-Submit button. It moves the status of Dispute Request into Draft. A To Do will be generated for the user as submitter whose To Do Type and To Do Role are fetched from Dispute Request Type. |
Rejected | Enter | C1-DSPTREJT | C1-DSPTREJT | This algorithm is executed when on reject.
Parameter
1 – To Do Type
Parameter 2 – Characteristic Type
|
Canceled | Enter | C1-DSPTREJT | C1-DSPTREJT | This algorithm is executed when on reject.
Parameter
1 – To Do Type
Parameter 2 – Characteristic Type
|