Ansicht
Dokumentation

SIMG_MMPURSPRSNMAP - Define Mapping: Unconfirmed Demand Reason to Block Indicator Reason (Contr)

TXBHW - Original Tax Base Amount in Local Currency   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

In the following explanations, items of the type "Complex" are referred to as "project items" and items of the type "General" are referred to as "standard items", as these are the item classification names used in the standard delivery. The terms that appear on the UI may be different depending on which item classification names have been defined in the implementation activity "Define Item Types for Sourcing Projects".

When the bidding process is over and the most suitable supplier quotations have been awarded, the system starts the creation of follow-on documents, in this case a central purchase contract. During this process, the system checks whether items or demand lines of project items have been set to "Unconfirmed". This influences whether the distribution line for the respective plant is marked as "Blocked" in the central purchase contract. Demand lines will be aggregated into a single distribution line if they have the same values in fields relating to the procurement hub source system, procurement hub company code grouping ID, company code, purchasing organization, purchasing group, currency, payment terms, and plant.

The following logic applies:

• If a standard item is set to "Unconfirmed" in a sourcing project, the contract item and distribution line for the respective plant will be marked as "Blocked".

• If a standard item is set to "Confirmed", the contract item and distribution line for the respective plant will not be marked as "Blocked".

• If a project item is set to "Unconfirmed", the contract item will be marked as "Blocked".

• If a project item is set to "Confirmed" or "Partly Confirmed", the contract item will not be marked as "Blocked".

• For the demand lines of a project item, the following logic applies:

• If all demand lines that have the same values in the abovementioned fields are set to "Unconfirmed" in a sourcing project, the distribution line for the respective plant will be marked as "Blocked".

• If none or only some of the demand lines that have the same values in the abovementioned fields are set to "Unconfirmed" in a sourcing project, the distribution line for the respective plant will not be marked as "Blocked".

In the follow-on document, the reason codes for the blocked distribution lines will be derived from the reason codes for the unconfirmed demand of the items or demand lines according to the mapping defined in this implementation activity.

In this step you can do the following:

• Define new mapping between reason codes for unconfirmed demand and reason codes for blocked contract items and distribution lines

• Display existing mapping between reason codes for unconfirmed demand and reason codes for blocked contract items and distribution lines

• Delete existing mapping between reason codes for unconfirmed demand and reason codes for blocked contract items and distribution lines

You have to define reason codes for unconfirmed demand in the implementation activity "Define Reason Codes" first.

To define a new mapping between a reason code for unconfirmed demand and a reason code for a blocked distribution line, click on "New Entries" and maintain the following information:

• Reason code for unconfirmed demand

Select one of the existing reason codes for unconfirmed demand that you previously defined in the implementation activity "Define Reason Codes".

• Reason code for blocked distribution line

Select one of the existing reason codes for blocked distribution lines that you previously defined in the implementation activity "Maintain Reasons for Blocking Central Purchase Contract Items".

To delete a mapping between a reason for unconfirmed demand and a reason for a blocked distribution line, select one mapping line, click on "Delete", and save the changes.

BAL_S_LOG - Application Log: Log header data   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 4422 Date: 20240523 Time: 221256     sap01-206 ( 82 ms )