Transaction detail feed layout overview

Overview

This section provides details on the Transaction Detail feed layout, including the use of the feed layout, how the data is reflected in the database, and how to use the data from RPI.

This section provides the following detailed information:

Feed layout intent

This feed allows business unit level Transaction Detail information to be loaded to the Redpoint CDP platform. The Transaction Detail feed is used to ingest transactional detail information from client source systems (i.e., point of sale, call center, order management systems, CRM, web platform, data warehouse, etc.). The Transaction Detail feed supports various transaction states for transactions (order placed, canceled, shipped, returned) and loads transaction detail into Redpoint CDP. The Transaction Detail needs to link to an existing Transaction Header record in order to load.

Transaction Detail records without an associated Transaction Header record based on source_transaction_id will not be loaded, and will be placed in the holding table until the header record is available.

Missing products will also cause the record to go to the holding table.

Extension table

This feed has an associated extension table.

For general information about extension tables, refer to: extension tables.

Feed layout areas of consideration

This section includes some additional information to consider when providing data for this feed layout.

There are various things that can be captured about transactions using the Transaction detail feed layout. This includes line item details like status of the line item, the product related to they line item, the various price information for the item, along with other details.

• You can keep track of the Transaction Detail status for each of the items independently.

• Currently the transaction_detail_status_code only holds the most recent status for a given item.

• Default transaction_detail_status_code values in the lookup table:

  • Sale

  • Demand

  • Cancel

  • Returned

  • Price Adjustment

• Feed layout required fields:

  • source_transaction_id

  • line_item_num

  • source_product_id

  • transaction_detail_status_code

  • global_net_sales_amount

Identity matching

Transaction Detail feed does not go through matching. The PII associated to the transaction is provided by including the source Party Profile in the Transaction Header feed layout. This will populate the Transaction Customer Map and Transaction Customer PII Detail tables.

Use in RPI

Transaction and related summary data can be used in RPI to either select based on amount fields, product level, transaction type, or other details of the transactions.

Use in aggregates

Summaries where the location is used:

1. Transaction_Detail_Summary
   This table is a flattened version of the transaction header and detail along with other information related to the transaction, like location and product information.

2. Individual_BU_Retail_Summary
   This table includes details about the individual and business unit, like the first and last purchase date of the individual for that business unit, for example.

3. Individual_BU_Product_Category_Summary
   This table includes information about the product category that an individual has made purchases from for a given business unit.