SAP CND_MAP_VAKEY_AND_VADAT Function Module for NOTRANSL: Map variable Key

Search SAP Function Modules

CND_MAP_VAKEY_AND_VADAT is a standard cnd map vakey and vadat SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Map variable Key processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for cnd map vakey and vadat FM, simply by entering the name CND_MAP_VAKEY_AND_VADAT into the relevant SAP transaction such as SE37 or SE38.

Function Group: CND_GENERAL_INBOUND
Program Name: SAPLCND_GENERAL_INBOUND
Main Program: SAPLCND_GENERAL_INBOUND
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CND_MAP_VAKEY_AND_VADAT pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'CND_MAP_VAKEY_AND_VADAT'"NOTRANSL: Map variable Key
  EXPORTING
   I_KVEWE =  "Usage of the Condition Table
   I_KOTABNR =  "Condition Table
   I_VAKEY =  "Character 100
   I_VADAT =  "Variable Data Part

 IMPORTING
   E_VAKEY =  "Variable key 100 bytes
   E_VADAT =  "Variable Data Part

EXCEPTIONS
   TABLE_NOT_VALID = 1    TABLE_INCONSISTENT = 2    MAPPING_IMPOSSIBLE = 3    NO_MAPPING_NECESSARY = 4 

.

IMPORTING Parameters details for CND_MAP_VAKEY_AND_VADAT

I_KVEWE - Usage of the Condition Table

Data type: KVEWE
Optional: No
Call by Reference: Yes

I_KOTABNR - Condition Table

Data type: KOTABNR
Optional: No
Call by Reference: Yes

I_VAKEY - Character 100

Data type: VAKEY
Optional: No
Call by Reference: Yes

I_VADAT - Variable Data Part

Data type: BAPICONDCT-VADAT
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for CND_MAP_VAKEY_AND_VADAT

E_VAKEY - Variable key 100 bytes

Data type: VAKEY
Optional: No
Call by Reference: Yes

E_VADAT - Variable Data Part

Data type: BAPICONDCT-VADAT
Optional: No
Call by Reference: Yes

EXCEPTIONS details

TABLE_NOT_VALID - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

TABLE_INCONSISTENT - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

MAPPING_IMPOSSIBLE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

NO_MAPPING_NECESSARY - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CND_MAP_VAKEY_AND_VADAT Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM CND_MAP_VAKEY_AND_VADAT

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects