The following examples explain the relevant feeds, lines, and columns. The examples may or may not include all required columns from the feeds.
Use case 1
Order placed on Day 0, one product is canceled on Day 1, one product is shipped on Day 2
You do not have to update the transaction feed since neither the customer nor the date of the initial transaction changed. However, the transaction item needs to reflect those changes. CDP represents these changes incrementally. CDP displays the new and updated lines. You can either provide the increment as displayed in each case or provide a full history every time. You must follow the same conventions.
Feed: TransactionItem
Day 0
SourceTransactionItemNumber | SourceTransactionNumber | Type | SubType | InvoiceDate | ShipDate | SaleRevenue | SourceProductNumber | Quantity | DateCreated |
---|---|---|---|---|---|---|---|---|---|
ABC1-Demand | ABC | Purchase | Demand | Day0 | 10 | P1 | 1 | Day0 | |
ABC2-Demand | ABC | Purchase | Demand | Day0 | 30 | P2 | 1 | Day0 |
Day 1
SourceTransactionItemNumber | SourceTransactionNumber | Type | SubType | InvoiceDate | ShipDate | SaleRevenue | SourceProductNumber | Quantity | DateCreated |
---|---|---|---|---|---|---|---|---|---|
ABC1-Canceled | ABC | Purchase | Canceled | Day0 | Day1 | -10 | P1 | -1 | Day1 |
Day 2
SourceTransactionItemNumber | SourceTransactionNumber | Type | SubType | InvoiceDate | ShipDate | SaleRevenue | SourceProductNumber | Quantity | DateCreated |
---|---|---|---|---|---|---|---|---|---|
ABC2-Shipped | ABC | Purchase | Shipped | Day0 | Day2 | 30 | P2 | 1 | Day2 |
Use case 2
Order placed on Day 0, all products are shipped on Day 1, one product has a discount of $10, the whole order has a $5 discount and one product is returned on Day2
You do not have to update the transaction feed since neither the customer nor the date of the initial transaction changed. However, the transaction item needs to reflect those changes. CDP represents these changes incrementally. CDP displays the new and updated lines. You can provide either the increment as displayed in each case or provide a full history every time. You must follow the same conventions.
The transaction-level discount is spread evenly between the two items in the transaction in this example, but you can spread them based on the relative price of each item, or other means.
Feed: TransactionItem
Day 0
SourceTransactionItemNumber | SourceTransactionNumber | Type | SubType | InvoiceDate | ShipDate | ListPrice | Discount | SaleRevenue | SourceProductNumber | Quantity | DateCreated |
---|---|---|---|---|---|---|---|---|---|---|---|
ABC1-Demand | ABC | Purchase | Demand | Day0 | 10 | 2.5 | 7.5 | P1 | 1 | Day0 | |
ABC2-Demand | ABC | Purchase | Demand | Day0 | 30 | 12.5 | 17.5 | P2 | 1 | Day0 |
Day 1
SourceTransactionItemNumber | SourceTransactionNumber | Type | SubType | InvoiceDate | ShipDate | ListPrice | Discount | SaleRevenue | SourceProductNumber | Quantity | DateCreated |
---|---|---|---|---|---|---|---|---|---|---|---|
ABC1-Shipped | ABC | Purchase | Shipped | Day0 | Day1 | 10 | 2.5 | 7.5 | P1 | 1 | Day1 |
ABC2-Shipped | ABC | Purchase | Shipped | Day0 | Day1 | 30 | 12.5 | 17.5 | P2 | 1 | Day1 |
Day 2
SourceTransactionItemNumber | SourceTransactionNumber | Type | SubType | InvoiceDate | ShipDate | ListPrice | Discount | SaleRevenue | SourceProductNumber | Quantity | DateCreated |
---|---|---|---|---|---|---|---|---|---|---|---|
ABC1-Returned | ABC | Purchase | Returned | Day0 | Day2 | -10 | -2.5 | -7.5 | P1 | -1 | Day2 |