SAP ABAP Data Element REBATE_MAP_FUNCTIONS (Functions for Mapping Access Fields)

Hierarchy

☛ BBPCRM (Software Component) BBPCRM
   ⤷ AP-PRC-PR (Application Component) Pricing
     ⤷ VKON (Package) Application development R/3 conditions

Basic Data

Data Element	REBATE_MAP_FUNCTIONS
Short Description	Functions for Mapping Access Fields

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	REBATE_MAP_FUNCTIONS
Data Type	CHAR	Character String
Length	1
Decimal Places	0
Output Length	1
Value Table

Further Characteristics

Search Help: Name
Search Help: Parameters
Parameter ID
Default Component name
Change document	☐
No Input History	☐
Basic direction is set to LTR	☐
No BIDI Filtering	☐

Field Label

	Length	Field Label
Short	10	Map Fnct.
Medium	16	Mapping Function
Long	40	Functions for Mapping Access Fields
Heading	0

Documentation

Definition

The fields in communication structures KOMK and KOMP in an access sequence for the rebate are filled during pricing preparation. The rebate-relevant billing documents are determined using these fields. A number of procedures are used to determine the values for these fields. In the simplest case, the field in the communication structure is filled with the value from one of the fields in the billing document. For some fields in the communication structure, different fields in the billing document can define which value is entered.

To determine the appropriate billing documents for a rebate condition, you have to determine the origin of the field in the communication structure. The mapping functions are available to map the different procedures involved in value determination.

Use

You can use the following mapping functions to define the origin of a field in a communication structure:

• Function "Normal Field": The value of the field in the communication structure is determined using a document field.
• Function "1 Mapping Using Two Reference Fields": The value of the field in the communication structure is determined using two possible reference fields. The second document field is used if the value of the first field is initial.
• Function "2 Field to Ignore": This field is not used to determine the relevant billing documents. An example for this function is the campaign ID. If the campaign is created after the billing document, the "Campaign ID" field canot be used to determine billing documents. The billing documents are determined using other access fields only.
• Function "3 Nonpersistent Field": The field value is not saved in the document but is determined during runtime. This field is not used to determine the relevant billing documents. The billing documents are determined using other access fields only. An additional pricing preparation step takes place before the billing documents are processed in order to determine the field value and restrict the billing documents. The additional processing logic requires more runtime and should therefore be avoided if possible.
• Function "4 Hierarchy Partner Field": The value of the field in the communication structure is determined using the level number within the hierarchy (HISTUNR).
• Function "5 Product Hierarchy Field": The value of the field in the communication structure is determined using the product hierarchy.
• Function "6 Field with Additional Condition": The value of the field in the communication structure is determined using a document table with an additional condition. An example for this function is the table "SD Document: Partner" VBPA with additional determination of partner role.
• Function: "7 Complex Logic (BAdI)": The value of the field in the communication structure is determined using a complex logic that cannot be mapped with the other functions. For this function, you can use your own customer-specific implementations in addition to the standard SAP implementations.

Dependencies

Example

For more examples, see Standard Mapping.

History

Last changed by/on	SAP	20130529
SAP Release Created in	616