Transaction Cancellation

There might be situations when incorrect transaction data file is uploaded in the system. In such cases, the system provides you with an ability to cancel the whole transaction feed. You can cancel a transaction feed either before the transaction aggregation process starts (that is, before executing the Validate Transaction and Derive Price Item (C1-TXNIP) batch) or after the transaction aggregation process ends (that is, after executing the Clean Up (C1-TXNCU) batch). In other words, you cannot cancel a transaction feed during the transaction aggregation process. Once the transaction feed is cancelled, the status of the feed and all transactions in the feed is changed to Cancelled (CNCL).

The following table explains how the system behaves:

To cancel a transaction feed, you need to execute the following batches in the specified order:

1. Pending Bill Deletion (C1-DELBL) - This batch deletes the bills (with the Pending status) and their corresponding bill segments. You can specify either of the following parameters while executing this batch:

   Parameter Name	Description	Mandatory (Yes or No)
   Transaction Header ID	Used when you want to delete bills which include charges for transactions which are received in a particular transaction feed.	Yes
   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

2. Clean Up (C1-TXNCU) - This batch deletes non-aggregated and aggregated billable charges. An aggregated billable charge is deleted when it includes legs of transactions from the feed that you want to cancel. If an aggregated billable charge includes legs of transactions from multiple feeds, the SQIs and calculation lines (if any) are recalculated in the aggregated billable charge. The corresponding calculation lines are deleted whenever an aggregated billable charge, which includes transaction legs whose rating criteria is set to Aggregate transactions and then rate aggregated SQs (AGTR), is cancelled or deleted during the cancellation process. Note that while executing this batch, the Request Type parameter must be set to CNCL. For more information about the parameters that you can specify while executing this batch, refer to Clean Up.

3. Cancellation (C1-TXCNC) - This batch deletes the transaction legs. The corresponding calculation lines are deleted whenever an aggregated billable charge, which includes transaction legs whose rating criteria is set to Rate individual transactions and aggregate calc lines across transactions (RITA) or Rate Transactions (RITX), is cancelled or deleted during the cancellation process. Finally, this batch changes the status of the feed and all transactions in the feed to Cancelled (CNCL). You can specify either of the following parameters while executing this batch:

   Parameter Name	Description	Mandatory (Yes or No)
   Transaction Header ID	Used when you want to cancel a particular transaction feed.	Yes
   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 cancellation process, you need to attach a preprocessing algorithm on the TFM - Cancellation Pre-Processing algorithm entity in the Algorithms tab of the Division screen. This algorithm is triggered when you execute the Cancellation (C1-TXCNC) batch. Note that the system invokes the algorithm which is attached on the derived account's division and not on the division to which the transaction belongs.

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

Related Topics