Ansicht
Dokumentation

CRMV_CND_FLD_CSS - Define Customer-Specific Mapping of Condition Fields

CRMV_CND_FLD_CSS - Define Customer-Specific Mapping of Condition Fields

TXBHW - Original Tax Base Amount in Local Currency   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, you can control the filling of condition field values. The Customizing activity Display System Default Mapping of Condition Fields contains standard mapping entries for a basic set of condition fields. If you require additional condition fields or need to fill the fields defined in the standard table differently, you have to make corresponding entries in this table.

You define the following for each condition field:

  • The object changes to which the system must react to fill the condition field
  • Where the system reads the value for the condition field from
  • How the system fills the condition field

Note that the entries in this activity take priority over the entries in the activity Display System Default Mapping of Condition Fields.

You have defined the relevant condition fields in the field catalog (Customizing activity Maintain Field Catalog).

The following table explains the settings necessary to define the business transaction field for the system to transfer to the condition technique field in the field catalog:

Field Direct Mapping
Application CRM (SAP CRM is the only valid application)
Usage PR (To specify the mapping for pricing fields)
Field Name ZZFIELD (as defined in the field catalog for condition techniques)
Object Name CUSTOMER_H
Attribute Not needed
Logical Key Not needed
Field Name ZZFIELD (Field of transaction (the field refers to the object))
BAdI Filter Value Not needed
Source BAdI Filter Not needed
Target BAdI Filter Not needed

The following table explains the settings necessary to map individual fields of the partner object for bill-to parties:

Field Specific Mapping for Event Handler
Application CRM (SAP CRM is the only valid application)
Usage PR (To specify the mapping for pricing fields)
Field Name ZZPARTNER_FIELD (as defined in the field catalog for condition techniques)
Object Name PARTNER
Attribute 0003 (referring to partner function category for bill-to party)
Logical Key 0003 (referring to partner function category for bill-to party)
Field Name ZZPARTNER (Field of transaction (the field refers to the object))
BAdI Filter Value Not needed
Source BAdI Filter Not needed (optional: specify HEADER if partner is read from trans. header only)
Target BAdI Filter Not needed

You can use the implementation of the BAdI: Filling of Condition Fields to define the target group (for example, the target group defined for marketing) the sold-to party belongs to. The following table explains the settings necessary in this Customizing activity:






PERFORM Short Reference   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 6249 Date: 20240523 Time: 164806     sap01-206 ( 70 ms )
Field Filling with BADI
Application CRM (SAP CRM is the only valid application)
Usage PR (To specify the mapping for pricing fields)
Field Name ZZTARGETGROUP (as defined in the field catalog for condition techniques)
Object Name PARTNER
Attribute 0001 (referring to partner function category for sold-to party)
Logical Key 0001 (referring to partner function category for sold-to party)
Field Name BP_PARTNER_GUID (Field of trans. (the field refers to the object))
BAdI Filter Value ZZ_TARGETGROUP
Source BAdI Filter Not needed (optional: specify HEADER if partner is read from trans. header only)
Target BAdI Filter Not needed