Transaction Rollback

In the transaction aggregation process, an error occurs when:

  • Transaction validation fails.

  • Transaction does not satisfy any rule invoked through the rule type.

  • Effective pricing is not available for one or more price items to which a transaction is mapped.

  • SQIs are not defined for the price item - division combination.

  • Transaction aggregation rule is not defined for the SQI.

  • Exchange rate is not available during currency conversion.

  • There is no contract available with the specified contract type on the transaction date or when the contract is inactive.

  • There are multiple effective contracts of the same contract type (available on the transaction date) in Active, Pending Stop, or Stop status.

  • The Price Assignment Search algorithm is not defined for the division.

  • The parameter values are either not defined or invalid in the Price Assignment Search algorithm on the processing date.

  • The period in which the transaction date falls is not defined in the aggregation schedule.

  • Price Item parameters specified in the output parameters are not effective for the price item on the processing date.

  • Mandatory price item parameter which is effective on the processing date is not specified in the output parameter.

  • Parameter value is not specified for all mandatory price item parameters which are effective on the processing date.

In such cases, the status of the transaction is changed to Error. You can configure the required setup and then execute the following batches once again in the specified order:

  1. Flush All Caches (F1-FLUSH)

  2. Refresh Pricing (C1-TXNRP)

  3. Header Validation (C1-TXNHV)

  4. Validate Transaction and Derive Price Item (C1-TXNIP)

  5. Populate CI_​TXN_​DTL_​PRITM_​SUMMARY Table (C1-TXNPS)

    Note: You must execute the Populate CI_​TXN_​DTL_​PRITM_​SUMMARY Table (C1-TXNPS) batch when the Use C1-TXNPS During Transaction Aggregation option type in the C1_​FM feature configuration is set to true.

  6. Price Item Pricing Verification (C1-TXNVP)

  7. Update Status (C1-TXNEX)

  8. Service Quantity Calculation (C1-TXNSQ)

  9. Mark Completion (C1-TXNCM)

  10. Clean Up (C1-TXNCU)

But, before you execute these batches, you need to rollback the transaction status to Uploaded (UPLD). The system allows you to rollback transactions which are in the Ignored (IGNR) and Error (EROR) status. When you rollback a transaction, the corresponding transaction legs are deleted and the status of the transaction is changed to Uploaded (UPLD). On rolling back a transaction leg whose effective pricing has the Ignore Transaction field set to Yes and the Rating Criteria field set to Rate Transactions (RITX), the corresponding calculation lines are also deleted along with the transaction leg. If you rollback a partially disaggregated transaction which is in the Error (EROR) status, the transaction legs which are in the Error (EROR) status are only deleted and the status of the transaction is changed to Uploaded (UPLD).

You need to execute the Rollback (C1-TXNRB) batch to rollback transactions which are in the Ignored (IGNR) and Error (EROR) status. You can specify the following parameters while executing this batch:

Parameter Name Description Mandatory (Yes or No)
Transaction Status Used to indicate whether you want to rollback transactions which are in the Ignored or Error status. The valid values are:

  • IGNR

  • EROR

 Yes
Transaction Header ID Used when you want to rollback transactions which are received in a particular transaction feed. No
Transaction Source Used when you want to rollback transactions which are received from a particular transaction source. No
Division Used when you want to rollback transactions belonging to a particular division. No
Rollback From Date Used when you want to rollback transactions which were performed from a particular date onwards.
Note:

You must specify the date in the YYYY-MM-DD format.

The rollback from date cannot be later than the rollback to date.

 No
Rollback To Date Used when you want to rollback transactions which were performed till a particular date.
Note:

You must specify the date in the YYYY-MM-DD format.

The rollback to date cannot be earlier than the rollback from date.

 No
Chunk Size Used to specify the number of transactions you want to execute in each work unit. Yes
Maximum Batch Count Used to specify the maximum number of transactions after which the data must be transferred to the database. Yes
Thread Pool Name Used to specify the thread pool on which you want to execute the batch. No
Note:

If you want to undertake some preprocessing activities (such as cleaning data in any custom tables) during the rollback process, you need to attach a preprocessing algorithm on the Transaction Feed Management Rollback Preprocessing algorithm entity in the Algorithms tab of the Division screen. This algorithm is triggered when you execute the Rollback (C1-TXNRB) batch. Note that the system invokes the algorithm which is attached on the division to which the transaction belongs.

A sample preprocessing algorithm type named C1_​ROBK_​PRPC is shipped with the product. It does not have any business logic. If you want to undertake some preprocessing activities during the rollback process, you need to create custom algorithm type and attach the respective algorithm on the TFM - Rollback Pre-Processing algorithm spot of the respective division. You can refer to the C1_​ROBK_​PRPC algorithm type to understand the input parameters that must be passed to the custom algorithm type.

Related Topics

For more information on... See...
Transaction Leg Status Transition Transaction Leg Status Transition