SAP CTE_FND_CODE_MAPPING Function Module for Concur Integration Code Mapping









CTE_FND_CODE_MAPPING is a standard cte fnd code mapping SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Concur Integration Code Mapping 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 cte fnd code mapping FM, simply by entering the name CTE_FND_CODE_MAPPING into the relevant SAP transaction such as SE37 or SE38.

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



Function CTE_FND_CODE_MAPPING 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 'CTE_FND_CODE_MAPPING'"Concur Integration Code Mapping
EXPORTING
IV_SYSTEM_KEY = "System Key Number
IV_FEATURE_NAME = "Concur Feature Name
IV_FORM_TYPE = "Concur Form Type
IV_CONCUR_FIELD_ID = "Concur Field ID
.



IMPORTING Parameters details for CTE_FND_CODE_MAPPING

IV_SYSTEM_KEY - System Key Number

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

IV_FEATURE_NAME - Concur Feature Name

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

IV_FORM_TYPE - Concur Form Type

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

IV_CONCUR_FIELD_ID - Concur Field ID

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

Copy and paste ABAP code example for CTE_FND_CODE_MAPPING 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.

DATA:
lv_iv_system_key  TYPE CTE_SYSTEM_KEY_NUMBER, "   
lv_iv_feature_name  TYPE CTE_CONCUR_FEATURE_NAME, "   
lv_iv_form_type  TYPE CTE_CONCUR_FORM_TYPE, "   
lv_iv_concur_field_id  TYPE CTE_CONCUR_FIELD_ID. "   

  CALL FUNCTION 'CTE_FND_CODE_MAPPING'  "Concur Integration Code Mapping
    EXPORTING
         IV_SYSTEM_KEY = lv_iv_system_key
         IV_FEATURE_NAME = lv_iv_feature_name
         IV_FORM_TYPE = lv_iv_form_type
         IV_CONCUR_FIELD_ID = lv_iv_concur_field_id
. " CTE_FND_CODE_MAPPING




ABAP code using 7.40 inline data declarations to call FM CTE_FND_CODE_MAPPING

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!