Considerations and Limitations

When centralizing your Trade Promotion Management (TPM) data into Data 360 , be aware of these considerations and limitations.

• Data 360 export reuses RTR export configurations and integration APIs for triggering exports, status checks, and aborting exports.
• Two usage types are supported: datacloudpromotionmeasuresmeta and datacloudaccountplanmeasuresmeta. Verify that these usage types exist as picklist values in the RTR Report Configuration object. If they don't, add them manually.
• The RTR configurations for both promotion and account plan exports include measure codes, a date from field, and an object.
• The date from value sets the promotion start date. The export includes promotions that start on or after this date.
• For Account Plans, the date from value applies to the business year or calendar year, based on the calendar configuration. The export uses the beginning of that year. For example, if the business year starts on December 28, 2023, and the configured date is January 1, 2024, the export uses December 28, 2023.
• The system doesn't validate whether the configured measure codes exist or are writeback measures. The export ignores measure codes without data.
• Exports run incrementally and maintain a watermark for exported records.
• You can't modify the RTR metadata section in the export configuration when it is running.
• If you change the configuration after the export completes, the export watermark resets to null. This reset triggers a full export, even for previously exported measures. Data 360 overwrites existing records with the latest versions based on the primary key (rowid) and lastmodified timestamp.
• The export includes the exact values from the processing service without additional rounding.
• The export is incremental and processes only records created after the previous export.
• The configuration is sales organization dependent.
• The limit for concurrent export jobs is 10. This limit is shared between RTR and Data 360 exports. You can have only one export configuration per sales organization and object.
• If you remove measure codes from the configuration, the export doesn't delete the corresponding records in Data 360. They remain in the Data Lake Object (DLO) until you remove them. For example, you export records for measure codes VOLU and PRIC. Then you update the configuration to replace those codes with MONE and TMON. The new export contains records only for MONE and TMON, but the previously exported records for VOLU and PRIC remain in Data 360.
• If a promotion spans multiple business or calendar years, the system splits the promotion into multiple records, one per year. If a single period spans years, the system splits the values based on the Week Day Share Profile. The system uses the Week Day Share Profile only for Volume, Money, and None KPI value types. For Price and Percentage, the system copies the values.
• Run the TPM Data Kit to make custom or standard objects available in Data 360 for mapping the TPM data export.