Transaction Leg Status Transition
This section explains how a transaction leg moves from one status to another during the following sub-processes:
-
Transaction Aggregation
Note: This is the aggregation process for transactions that are recently uploaded or reaggregated after being fully disaggregated. -
Transaction Rollback
-
Transaction Cancellation
-
Transaction Disaggregation
-
Transaction Reaggregation
Note: This is the aggregation process for transactions that are reaggregated after being partially disaggregated.
Transaction Aggregation
The following table indicates how a transaction leg moves from one status to another during the aggregation process:
Sr. No. | Batch | Event | Pre Event Transaction Status | Pre Event Transaction Leg Status | Post Event Transaction Status | Post Event Transaction Leg Status |
---|---|---|---|---|---|---|
1 | C1-TXNIP | Transaction validation fails due to incomplete transaction data | UPLOADED | Not applicable as the transaction legs are not yet created | INVALID | Not applicable as the transaction legs are not yet created |
2 | C1-TXNIP | Transaction validation fails due to invalid or incorrect transaction data | UPLOADED | Not applicable as the transaction legs are not yet created | ERROR | Not applicable as the transaction legs are not yet created |
3 | C1-TXNIP | Transaction validation is successful but no product is derived | UPLOADED | Not applicable as the transaction legs are not yet created | ERROR | Not applicable as the transaction legs are not yet created |
4 | C1-TXNIP | Transaction validation is successful and product is derived | UPLOADED | Not applicable as the transaction legs are not yet created | INITIAL PRODUCT DETERMINED | INITIAL PRODUCT DETERMINED |
5 | C1-TXNIP | Transaction validation is successful and the transaction is ignored by the rule based on the transaction attributes | UPLOADED | Not applicable as the transaction legs are not yet created | IGNORED | Not applicable as the transaction legs are not yet created |
6 | C1-TXNVP and C1-TXNEX | Effective pricing is not found for any of the transaction legs | INITIAL PRODUCT DETERMINED | INITIAL PRODUCT DETERMINED | ERROR | ERROR |
7 | C1-TXNVP and C1-TXNEX | Ignore Transaction flag is set to Y in the effective pricing for one or more transaction legs but not for all transaction legs | INITIAL PRODUCT DETERMINED | INITIAL PRODUCT DETERMINED | INITIAL PRODUCT DETERMINED | IGNORED (when Ignore Transaction flag is set to Y in the effective pricing) INITIAL PRODUCT DETERMINED (when Ignore Transaction flag is set to N in the effective pricing) |
8 | C1-TXNVP and C1-TXNEX | Ignore Transaction flag is set to Y in the effective pricing for all transaction legs | INITIAL PRODUCT DETERMINED | INITIAL PRODUCT DETERMINED | IGNORED | IGNORED |
9 | C1-TXNVP and C1-TXNEX | Ignore Transaction flag is set to N in the effective pricing for all transaction legs | INITIAL PRODUCT DETERMINED | INITIAL PRODUCT DETERMINED | INITIAL PRODUCT DETERMINED | INITIAL PRODUCT DETERMINED |
10 | C1-TXNSQ and C1-TXNCM | SQIs are not defined for the product — division combination, Transaction aggregation rule is not defined for the SQI, or Exchange rate is not available during currency conversion | INITIAL PRODUCT DETERMINED | INITIAL PRODUCT DETERMINED | ERROR | ERROR |
11 | C1-TXNSQ and C1-TXNCM | Billable charges are created successfully for all transaction legs | INITIAL PRODUCT DETERMINED | INITIAL PRODUCT DETERMINED | COMPLETED | COMPLETED |
Transaction Rollback
The following table indicates how a transaction leg moves from one status to another during the rollback process:
Sr. No. | Batch | Event | Pre Event Transaction Status | Pre Event Transaction Leg Status | Post Event Transaction Status | Post Event Transaction Leg Status |
---|---|---|---|---|---|---|
1 | C1-TXNRB | Transactions with the Error (EROR) status are rolled back | ERROR | ERROR | UPLOADED | Not applicable as the transaction legs are not yet created |
2 | C1-TXNRB | Transactions with the Ignored (IGNR) status are rolled back | IGNORED | IGNORED | UPLOADED | Not applicable as the transaction legs are not yet created |
Transaction Cancellation
The following table indicates how a transaction leg moves from one status to another during the cancellation process:
Sr. No. | Batch | Event | Pre Event Transaction Status | Pre Event Transaction Leg Status | Post Event Transaction Status | Post Event Transaction Leg Status |
---|---|---|---|---|---|---|
1 | C1-TXCNC | Transactions in any status are cancelled | UPLOADED, INITIAL PRODUCT DETERMINED, ERROR, COMPLETED, INVALID, or IGNORED | INITIAL PRODUCT DETERMINED, ERROR, IGNORED, or COMPLETED | CANCELLED | CANCELLED |
Transaction Disaggregation
The following table indicates how a transaction leg moves from one status to another during the disaggregation process:
Sr. No. | Batch | Event | Pre Event Transaction Status | Pre Event Transaction Leg Status | Post Event Transaction Status | Post Event Transaction Leg Status |
---|---|---|---|---|---|---|
1 | C1-DISTG | Transactions in the COMPLETED, ERROR, or IGNORED status are disaggregated. | COMPLETED, ERROR, or IGNORED Note: The transactions in the
ERROR or IGNORED status must have legs for disaggregation.
|
COMPLETED, ERROR, or IGNORED | No change in the status | No change in the status |
2 | C1-DISTG | Transactions in the INVALID or CANCELLED status cannot be disaggregated. In addition, the newly uploaded transactions and fully disaggregated transactions which are in the UPLOADED status cannot be disaggregated. | CANCELLED, INVALID, or UPLOADED | Not applicable as the transactions will not have any legs in these statuses | No change in the status | Not applicable as the transactions will not have any legs in these statuses |
3 | C1-IDENT | Transactions in the COMPLETED, ERROR, or IGNORED status are disaggregated. | COMPLETED, ERROR, or IGNORED Note: The transactions in the
ERROR or IGNORED status must have legs for disaggregation.
|
COMPLETED, ERROR, or IGNORED | No change in the status | No change in the status |
4 | C1-IDENT | Transaction has already been disaggregated and is in the UPLOADED status. The transaction legs which were not affected are moved in the staging table and the transaction legs which were affected are deleted. Now, if the effective pricing is changed for the account to which the transaction leg in the staging table is mapped, then that transaction leg must be disaggregated. Thus, disaggregation is done even though the transaction is in the UPLOADED status. | UPLOADED | UPLOADED | No change in the status | No change in the status |
5 | C1-PDTXN | Transactions in the COMPLETED, ERROR, or IGNORED status are disaggregated. | COMPLETED, ERROR, or IGNORED Note: The transactions in the
ERROR or IGNORED status must have legs for disaggregation.
|
COMPLETED, ERROR, or IGNORED | UPLOADED | Transaction legs which are affected during disaggregation are deleted and the other legs which are not affected are moved to the staging table. |
Transaction Reaggregation
The following table indicates how a transaction leg moves from one status to another during the reaggregation process:
Sr. No. | Batch | Event | Transaction Status Before Disaggregation | Transaction Leg Status Before Disaggregation | Transaction Status After Reaggregation | Transaction Leg Status After Reaggregation |
---|---|---|---|---|---|---|
1 | C1-TXNIP | Transaction in the COMPLETED status was disaggregated. It had four transaction legs – two in the COMPLETED status and other two in the IGNORED status. A transaction leg in the COMPLETED status was disaggregated due to change in the business rule (i.e. IGNORE_SW is set to Y). | COMPLETED | COMPLETED, IGNORED | COMPLETED | Derived Leg: IGNORED Existing Legs: COMPLETED and IGNORED |
2 | C1-TXNIP | Transaction in the COMPLETED status was disaggregated. It had one transaction leg in the COMPLETED status and all other transaction legs in the IGNORED status. The leg in the COMPLETED status was disaggregated due to change in the business rule (i.e. IGNORE_SW is set to Y). | COMPLETED | COMPLETED, IGNORED | IGNORED | Derived Leg: IGNORED Existing Legs: IGNORED |
3 | C1-TXNIP | Transaction in the COMPLETED status was disaggregated. All the transaction legs were in the COMPLETED status. One of the transaction legs in the COMPLETED status was disaggregated. During reaggregation, no product was derived for this transaction leg. | COMPLETED | COMPLETED | ERROR | Derived Leg: No new transaction leg was created Existing Legs: COMPLETED |
4 | C1-TXNIP | Transaction in the ERROR status was disaggregated. It had no transaction legs. During reaggregation, no product was derived for the transaction. | ERROR | No Transaction Legs Exist | ERROR | Derived Leg: No new transaction leg was created Existing Legs: None |
5 | C1-TXNIP | Transaction in the ERROR status was disaggregated. It had no transaction legs. During reaggregation, a product was derived for the transaction. | ERROR | No Transaction Legs Exist | INITIAL PRODUCT DETERMINED | Derived Leg: INITIAL PRODUCT DETERMINED Existing Legs: None |
6 | C1-TXNVP and C1-TXNEX | Transaction in the COMPLETED status was disaggregated. It had four transaction legs – two in the COMPLETED status and other two in the IGNORED status. A transaction leg in the COMPLETED status was disaggregated. During reaggregation, the effective pricing was not found for the transaction leg. | COMPLETED | COMPLETED, IGNORED | ERROR | Derived Leg: ERROR Existing Legs: COMPLETED and IGNORED |
7 | C1-TXNVP and C1-TXNEX | Transaction in the ERROR status was disaggregated. It had no transaction legs. During reaggregation, the effective pricing is found for the transaction legs. | ERROR | No Transaction Legs Exist | INITIAL PRODUCT DETERMINED | Derived Legs: INITIAL PRODUCT DETERMINED Existing Legs: None |
8 | C1-TXNVP and C1-TXNEX | Transaction in the COMPLETED status was disaggregated. It had four transaction legs – two in the COMPLETED status and other two in the IGNORED status. A transaction leg in the COMPLETED status was disaggregated due to change in the effective pricing (i.e. Ignore Transaction flag is set to Y). | COMPLETED | COMPLETED, IGNORED | COMPLETED | Derived Leg: IGNORED Existing Legs: COMPLETED and IGNORED |
9 | C1-TXNVP and C1-TXNEX | Transaction in the COMPLETED status was disaggregated. It had one transaction leg in the COMPLETED status and all other transaction legs in the IGNORED status. The leg in the COMPLETED status was disaggregated due to change in the effective pricing (i.e. Ignore Transaction flag is set to Y). | COMPLETED | COMPLETED, IGNORED | IGNORED | Derived Leg: IGNORED Existing Legs: IGNORED |
10 | C1-TXNSQ and C1-TXNCM | While reaggregating transaction legs, SQIs are not defined for the product — division combination, Transaction aggregation rule is not defined for the SQI, or Exchange rate is not available during currency conversion. | COMPLETED, ERROR, IGNORED Note: There must be no legs for
the transaction in the IGNORED status.
|
COMPLETED, ERROR | ERROR | Derived Legs: ERROR Existing Legs: No change in the status |
11 | C1-TXNSQ and C1-TXNCM | Billable charges are created successfully for all transaction legs which were earlier disaggregated and now reaggregated. | COMPLETED, ERROR, IGNORED Note: There must be no legs for
the transaction in the IGNORED status.
|
COMPLETED, ERROR | COMPLETED | Derived Leg: COMPLETED Existing Legs: No change in the status |