Determination of Promotion IDs for a Single Promotion

In the SAP Supply Network Collaboration (SAP SNC) promotion collaboration process, a promotion is identified by an ID that is unique in SAP SNC. Upon receipt of a DemandInfluencingEventNotification XML message that contains one promotion, SAP SNC automatically determines the ID of the promotion that needs to be updated or created, based on the external and internal ID transmitted in the XML message.

The DemandInfluencingEventNotification message can transmit the following IDs:

InternalID
This tag represents the internal promotion ID.
BuyerID
This tag represents the external promotion ID.

Prerequisites

Before starting a promotion collaboration, the customer and the supplier come to a basic agreement about the promotion ID that the customer sends the supplier. For example, a customer can agree with a supplier that the customer only sends an external promotion ID by means of the XML message.

Based on the result of the agreement between customer and supplier, you make settings to determine which promotion IDs the supplier expects from the customer in Customizing for Supply Network Collaboration under Start of the navigation path Demand Next navigation step Promotion Define Settings for Inbound Processing of Promotion XML Messages End of the navigation path .

Features

SAP SNC uses different processes to determine the promotion ID based on which promotion ID the customer includes in the DemandInfluencingEventNotification XML message, internal promotion ID, external promotion ID, both internal and external promotion ID, or none at all.

Note Note

If the customer sends both internal and external promotion ID in the DemandInfluencingEventNotification XML message, the system determines the promotion ID based on the internal promotion ID.

End of the note.

Determining the Promotion ID Without Internal or External Promotion ID

If the XML message does not contain promotion IDs, the system creates a promotion ID by combining the three letter string “XML” and the message creation time stamp (MESSAGE_CREATION_DATETIME) of the XML message, for example XML20080407. This is done by the Business Add-In Maintain Settings for Promotion Planning (/SAPAPO/ICH_PROM_EXT).

Determining the Promotion ID with the External Promotion ID

If the XML message only contains the external promotion ID, the system checks if an existing promotion exists that already uses the external promotion ID. If the system finds a promotion with the same external promotion ID, the system updates the promotion. If no promotion exists with that external promotion ID, the system creates a new promotion ID using the external promotion ID.

Determining the Promotion ID with the Internal Promotion ID

The system can only determine promotion IDs with the internal promotion ID if you have made settings in Customizing. The settings in Customizing define if the supplier expects from the customer to send an internal promotion ID in the DemandInfluencingEventNotification XML message. SAP SNC reacts as follows depending on if you expect the internal promotion ID or not:

If you do not expect an internal promotion ID but the customer sends one in the DemandInfluencingEventNotification XML message, the system saves the promotion as a draft and issues an alert.
If you expect an internal promotion ID and the customer sends one in the DemandInfluencingEventNotification XML message, the system searches for an existing promotion. It performs this search to decide on how to determine the promotion:
- If no existing promotion exists with the same promotion ID as the internal promotion ID, the system creates a new promotion.
- If a promotion exists with the same promotion ID as the internal promotion ID, the system creates an update of the existing promotion.
- If a promotion exists with a partial match of the promotion IDs, for example the system finds a promotion that has the same internal promotion ID but an additional external promotion ID, the system saves the promotion as a draft and creates an alert.

Multiple Promotions

If the XML message contains more than one location product that do not share the same promotion parameter set, the system creates multiple promotion IDs. To distinguish between the promotion IDs, the system separates the promotion IDs by assigning a numeric suffix, such as _001, _002, and so on.