Examples of Collecting Transactions and Credits
These two examples use a subset of transaction data to show the results when transactions are imported into the staging table and then collected into the transaction table under two different conditions.
-
Condition 1 starts with a transaction that was created in the source application.
-
Condition 2 starts with an adjusted version of the same source transaction.
Condition 1: New Transaction Created in a Source Application
This table shows a simplified transaction record created in the source application.
Source Order ID |
Source Transaction Line ID |
Source Order Date |
Source Transaction Amount |
Source Item ID |
---|---|---|---|---|
1001 |
301 |
01-01-2015 |
10,000 |
Sentinel Desktop |
The next two tables don't show the source order ID and date or source transaction amount and item ID but the transaction 1001-301 record would include them.
Condition 1: After Importing the Transaction into the Staging Table
This table shows what that simplified transaction record looks like in the staging table, after importing it from the source application.
Staging Order ID |
Staging Order Date |
Staging Transaction Amount |
Transaction Order ID |
Transaction Order Date |
Transaction Amount |
Transaction Object Status |
Changed Transaction |
---|---|---|---|---|---|---|---|
1001 |
01-01-2015 |
10,000 |
None |
None |
None |
None |
None |
Condition 1: After Collecting the Transaction into the Transaction Table
This table shows what that simplified transaction record looks like in the transaction table, after collecting it from the staging table.
Staging Order ID |
Staging Order Date |
Staging Transaction Amount |
Transaction Order ID |
Transaction Order Date |
Transaction Amount |
Transaction Object Status |
Changed Transaction |
---|---|---|---|---|---|---|---|
deleted |
deleted |
deleted |
1001 |
01-01-2015 |
10,000 |
New |
N |
Condition 2: After the Transaction is Modified in the Source Application
This table shows the same transaction in the source application, after the amount is modified from 10,000 to 12,000.
Source Order ID |
Source Transaction Line ID |
Source Order Date |
Source Transaction Amount |
Source Item ID |
---|---|---|---|---|
1001 |
301 |
01-01-2015 |
12,000 |
Sentinel Desktop |
While the remaining tables don't show the source order ID and date or source transaction amount and item ID from the previous scenario, the record for transaction 1001-301 would include them.
Condition 2: After Importing the the Modified Transaction into the the Staging Table
This table shows what the modified transaction looks like in the staging table, after importing it from the source application.
Staging Order ID |
Staging Order Date |
Staging Transaction Amount |
Transaction Order ID |
Transaction Order Date |
Transaction Amount |
Transaction Object Status |
Transaction Changed Transaction |
---|---|---|---|---|---|---|---|
1001 |
01-01-2015 |
12,000 |
None |
None |
None |
None |
None |
Condition 2: After Collecting the Modified Transaction into the Transaction Table
This table shows what the original and modified transactions look like in the transaction table, after collecting the modified transaction from the staging table.
Staging Order ID |
Staging Order Date |
Staging Transaction Amount |
Transaction Order ID |
Transaction Order Date |
Transaction Amount |
Transaction Object Status |
Transaction Changed Transaction |
---|---|---|---|---|---|---|---|
deleted |
deleted |
deleted |
1001 |
01-01-2015 |
12,000 |
New |
Y |
deleted |
deleted |
deleted |
1001 |
01-01-2015 |
10,000 |
Obsolete |
Y |
Condition 2: After Reversal Based on the Modified Transaction
This table shows what the modified transactions look like in the transaction table, after running the Revert Transactions process to address changes to source transactions collected earlier. The second transaction is a reversal to offset the difference between the original and adjusted source transaction amounts.
Staging Order ID |
Staging Order Date |
Staging Transaction Amount |
Transaction Order ID |
Transaction Order Date |
Transaction Amount |
Transaction Object Status |
Changed Transaction |
---|---|---|---|---|---|---|---|
deleted |
deleted |
deleted |
1001 |
01-01-2015 |
12,000 |
New |
Y |
deleted |
deleted |
deleted |
1001 |
01-01-2015 |
-10,000 |
New |
Y |
The Revert Transaction process also performs these actions:
-
Moves the original transaction to the history table
-
Deletes the original transaction from the transaction table