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:

  • Dispute Request Type Description

  • Dispute Request Status Description

  • Dispute Request ID
Validation C1-DSPTVADN C1-DSPTVADN This algorithm validates following:

Draft status validations:

  • At-least one entity should be selected to submit a dispute. Dispute Request with at-least one Bill or Bill Line Item should be added for submission

  • Dispute amount cannot be zero or null

  • If a bill is already present in dispute request and request is not in final status then user should not be allowed to add same bill in another dispute request

  • Disputed Amount should be equal to bill outstanding amount if bill Line item contain multiple contracts

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:

  • Whether the approval is required for the dispute request. If the approval is required for a dispute request, the status of the dispute request is changed to Approval In Progress. However, if the approval is not required for a dispute request, the status of the dispute request is changed to Creating Adjustment.

  • At least one entity, such as payment event, payment, or credit bill line item (such as credit bill segment or adjustment) is selected in the dispute request.

  • Whether the approval profile attached to the Dispute Request Typehas the credit hierarchy and To Do Type defined.
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

  • If stop auto pay switch is No and auto pay exist then create adjustment on next bill

  • If stop auto pay switch is Yes then perform below step

    • If bill cannot be reopen or adjustment need to be created on next bill then create adjustment on next bill

    • If approval is configured then create to do for manual creation of auto pay (Auto Pay is stopped while submitting the request)

    • Else

      • create adjustment on current bill

        • if approval is configured then

          • Bill reopen and complete (Auto Pay is stopped while submitting the request)

          • Delete overdue char from bill
Status System Event Algorithm Algorithm Type Description

  • Else

    • Stop auto pay

    • Reopen and complete

Paid Bill logic

  • Adjustment will be created on next bill

Partial Bill Logic

  • Adjustment will be created to balance current bill and another adjustment will be created for remaining amount and it will be stamped on next bill.

  • If dispute adjustment will increase the debit or credit balance then adjustment will be stamped on next bill.

There are four parameters for this algorithm.

Parameter 1 - Adjustment on Next Bill (Required)

  • Adjustments should be swapped on the current or next bill. It is used only for unpaid bill.

Parameter 2 - Match Type Entity Flag (Required)

  • Valid values for this parameter are BILL, BSEG and SA. This parameter defines the open item at which the match events are to be created. For bills which are not paid yet, new match events will be created based on the value of this parameter.

  • Based on the flag defined Match Events are created as follows,

    • If the Match Type Flag is BILL, then all FTs on a bill have the same Match Event.

    • If the Match Type Flag is BSEG, then each line item (bill segment or adjustment) on the bill will have a unique match event.

    • If the Match Type Flag is SA, then line items belonging to the same contract within a bill will have the same match event.

Parameter 3 - To Do Type

  • To Do will be sent to the user if bill can't be reopen and auto pay has been stopped.
Status System Event Algorithm Algorithm Type Description
Parameter 4 - Characteristic Type

  • Characteristic Type is used to remove the characteristic which is stamped on the bill to postpone overdue process
Approval In Progress Enter C1-DSPTAPP C1-DSPTAPP This algorithm creates the following:

  • A To Do using the To Do type specified in the approval profile which is attached to the dispute request type. The To Do is sent to the appropriate users in the approval hierarchy depending on whether hierarchical approval is required or not.

  • A log entry is added when a To Do is created using the To Do type.
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

  • To Do will be sent to the user if bill can't be reopen and auto pay has been stopped.

Parameter 2 - Characteristic Type

  • Characteristic Type is used to remove the characteristic which is stamped on the bill to postpone overdue process
Canceled Enter C1-DSPTREJT C1-DSPTREJT This algorithm is executed when on reject.
Parameter 1 - To Do Type

  • To Do will be sent to the user if bill can't be reopen and auto pay has been stopped.

Parameter 2 - Characteristic Type

  • Characteristic Type is used to remove the characteristic which is stamped on the bill to postpone overdue process