Ansicht
Dokumentation

M_CNDN_PRPS_ASSG - Assign Condition Purposes to Condition Types (Purchasing)

M_CNDN_PRPS_ASSG - Assign Condition Purposes to Condition Types (Purchasing)

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   CPI1466 during Backup  
This documentation is copyright by SAP AG.
SAP E-Book

Allows you to assign previously defined condition purposes to condition types.

You use this implementation activity to assign predefined condition purposes to condition types within pricing procedures, also called calculation schemas.

The system searches through these condition purposes for specific condition types within a pricing procedure to determine the values. These values are calculated depending on the user entries.

Each time a price calculation takes place, exactly one pricing procedure is used. This pricing procedure is determined per document.

Each condition purpose is represented on the user interface as a separate field. For supplier quotations for sourcing projects, depending on the settings that you define in this implementation activity, the system fills the relevant fields on the UI with values.

The following options are available:

  • Dependent on pricing procedure
You can define condition purposes to be valid for a combination of pricing procedure and condition type. To do so, you select the desired condition purpose ID and define the pricing procedure and the condition type. The system searches for the condition type only within the selected pricing procedure.
  • Independent from pricing procedure
You can define condition purposes to be valid for all available pricing procedures. To do so, you select the desired condition purpose ID and define a condition type. You leave the Procedure column empty. The system searches for the defined condition type when no specific pricing procedure dependent entry can be found.
  • You can define both pricing procedure dependent and independent condition purposes to provide an alternative logic if one of the options is not valid.
To do so, you can define multiple table entries for the same condition purpose ID. For each entry you select the condition purpose ID and define a pricing procedure and/or condition type. The system searches first for the defined condition type within the defined pricing procedures. If no condition type could be found, the system searches for the defined condition type without an entry in the Procedure column.

For supplier quotations for sourcing projects the values will be shown on the user interface of the app Manage Supplier Quotations (Sourcing Projects) in the Basic Data facet on the item level as values in the fields Price Reference 1 (MEASURE_1), Price Reference 2 (MEASURE_2) and Price Reference 3 (MEASURE_3).

Each supplier quotation has only one pricing procedure.

You have defined a condition purpose in the implementation activity Define Condition Purpose.

SAP provides three condition purposes (MEASURE_1, MEASURE_2, MEASURE_3). You can assign multiple pricing procedures and condition purposes by adding several entries.

Here are some examples for supplier quotations for sourcing projects.

  • Dependent on pricing procedure
In the Condition Purpose ID column you select the condition purpose MEASURE_1. In the Procedure column you enter RM0000. In the Condition Type column you select PBXX. When pricing procedure RM00000 is used in a supplier quotation and the condition PBXX can be found in that pricing procedure, then the value of condition PBXX is transferred to the field Price Reference 1 on the user interface of the app Manage Supplier Quotations (Sourcing Projects).
  • Independent from pricing procedure
In the Condition Purpose ID column you select condition purpose MEASURE_1. You leave the Procedure column empty. In the Condition Type column you select PBXX. If no procedure-specific entry was found, the system searches for a value that is independent from which pricing procedure is used in the document. In this case, the system searches for condition PBXX. If condition PBXX can be found in the pricing procedure that is used in a supplier quotation, then the value of condition PBXX is transferred to the field Price Reference 1 on the user interface of the app Manage Supplier Quotations (Sourcing Projects).





Fill RESBD Structure from EBP Component Structure   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 5332 Date: 20240523 Time: 190651     sap01-206 ( 105 ms )