Considerations for Promotion Transfer

A few points to keep in mind during the transfer of a promotion from Trade Promotion Management (TPM) to Retail Execution (RE).

• A promotion is transferred, when 
  • The anchor customer of the TPM promotion is mapped to an RE customer. The anchor TPM customer and RE customer have the same transfer record identifier and are unique within a sales organization. You can update the transfer record identifier in the Customer Extensions object.
  • The target (RE) tactic template is configured for the TPM promotion.
  • At least one tactic in the TPM promotion is marked as transfer-relevant.
• As part of the promotion transfer, you can choose: 
  • The type of TPM promotions to be transferred and mark the TPM promotions as transfer-relevant.
  • The tactic type (from the list of TPM tactics) to be transferred and mark the tactic as transfer-relevant.
  • A time frame during which the TPM promotions are transferred (using the lead time and followup time) to ensure that older promotions aren’t transferred.
  • To transfer promotions in specific phases.
• When the promotion transfer fails, a notification is shown to the user who is updating the TPM promotion through the UI or to the admin user during the batch process. If the admin user isn't configured in the Sales Organization object, then an error message is shown in the batch run status.
• Transfer of TPM promotions with subaccounts isn’t supported. TPM promotions don't support customer sets and the transfer of promotions with customer sets to RE. ​​TPM KPIs (that are stored in Hyperforce or part of the promotion and tactic header) are also not supported as part of this transfer process.
• In the transferred RE promotion, editing of these prepopulated transfer relevant fields on the UI or through the apex layer changes leads to inconsistent results:
  • Source Promotion
  • Source Tactic
  • Promotion Template
  • Tactic Template
  • Is transferred (in the tactic product)
• For a transferred promotion with a tactic (1), post-transfer if you make the transferred tactic (t1) as non-transfer relevant in TPM and another tactic from the same TPM promotion (t2) as transfer relevant, the promotion gets transferred with the tactic (t1) and the user is notified.
• When multiple tactics in a promotion are marked as included and transfer relevant, then the oldest tactic (order by the In store Date field or creation date) is considered for transfer.
• For a promotion (with multiple tactics marked as included and transfer relevant), if the transferred tactic is updated as non-included, then the second oldest tactic that is marked as Included and transfer relevant is considered for transfer.
• When you create the Allow_Multi_Template_Transfer setting, the system transfers a promotion to Retail Execution regardless of whether its transfer-relevant tactics come from a single tactic template or multiple tactic templates. The system selects the oldest tactic by In-Store Date From and then Created Date.
• When you don’t create the Allow_Multi_Template_Transfer setting or set its value to false, the system doesn't transfer promotions with transfer-relevant tactics from multiple tactic templates.
• When you create the Skip_Transfer_Prodt_Resol_<salesOrg> setting for the source promotion’s sales org, the system skips product resolution during transfer for promotions from that sales org. The promotion transfers without any tactic products.
• Promotion transfer doesn't happen when none of the tactics are marked or updated as non-included.