Example of an Export to Data 360

When you modify the set of measure codes in the export configuration, the watermark resets and re-exports all data from the start date. This update ensures that the export includes the changes. This example shows this use case.

• Initial Configuration:
  • You set up the RTR Real-Time Reporting (RTR) metadata for the Data 360 Promotion writeback KPI export with the following parameters:
    • dateFrom = 2023-01-01
    • measures = ["VOLU", "PRIC"]
  • You are exporting data starting from January 1, 2023, and you are interested in two measure codes: "VOLU" (Volume) and "PRIC" (Price).
• First Export:
  • You run the export process, and the system exports the data for the measure codes "VOLU" and "PRIC" to the Data 360.
  • After the export, the system sets a watermark to keep track of the latest processed timestamp. For example, the watermark is set to 2025-11-01T00:00:00. This indicates that data with a last modified timestamp up to November 1, 2025, has been exported.
• Configuration Change:
  • You decide to add a new measure code to the RTR configuration:
    • measures = ["VOLU", "PRIC", "MONE"]
  • Now, you are interested in exporting three measure codes: "VOLU", "PRIC", and "MONE".
• Impact of Configuration Change:
  • Because you have changed the set of measure codes by adding "MONE", the system resets the export watermark to null. This means the system no longer remembers the last processed timestamp.
• Next Export Run:
  • During the next export run, the system starts exporting data for all three measure codes ("VOLU", "PRIC", and "MONE") from the beginning, 2023-01-01.
  • This happens even though "VOLU" and "PRIC" were already exported up to November 1, 2025. The system treats the change in measure codes as a new configuration and starts the export process from scratch for all specified measure codes. The system updates the record if the rowid values match. Otherwise, the system creates a record.