Transaction validation
Catch errors earlier and prevent invalid data from propagating further through your organizational workflow by validating transactions.
What if your transactional data has issues preventing it from being used in Incentives?
Catch errors earlier by validating transactions. Prevent invalid data from propagating further through your organizational workflow. This saves workers from cost-intensive manual reviews later.
In this pipe, we aim to validate transactions before submitting them for processing, by catching currency mismatches, and missing dates. The required (starting) data set for this blueprint is Transactions (Data), data set that you want to validate.
This use case walks through how to fix the three following issues before you can use it in Incentives:
Inconsistent data
Missing values
Currency mismatches
Transactions (Data) consists of raw transactional data, which we are bringing into Varicent ELT to validate and clean.
The Error Handling (Case) tool identifies which transactions fail in at least one of three cases. In this example, we are looking for currencies that do not align with "Canada" and missing BookDate values.
The Valid Transactions (Filter) and Invalid Transactions (Filter) are filter tools that split our data into two data sets; the valid and invalid sets. This will allow us to easily manipulate, review and export the invalid data, before joining it back to the valid transactions.
The first invalid case we deal with is currency mismatches. The data in the invalid branch has either "CAN" listed as the country with a non-CAD currency, or has CAD currency with the country listed as other than "CAN". Error Correction (Formula) tool handles both these situations. In the first case, it replaces the ApprovedAmount value by multiplying it by a USD:CAD exchange rate to convert it to CAD. For your own scenario, you could instead import a table with the exchange rate of multiple currencies, and even multiple dates! Using a Join tool, you could add the correct exchange rate to each record.
The Error Correction (Formula) tool also handles the missing BookedDates. Instead, we will replace the null values with the existing ApplicationDate.
After, the Drop Original Columns (Drop) Rename Columns (Rename) tools do some column cleanup to allow us to join the data back together with the Union tool.
The valid combinations are then exported back for ingestion into Incentives, ready to be processed as valid transactions and orders. Export To Incentives (Export).
Finally, since the invalid transactions may warrant further investigation, or you may not have been able to handle all the errors you found, Investigate Invalid Transactions (Export) exports only the transactions that failed the original error validation. This allows us to further track these records, and follow up on the errors.