SAP CONVERT_TO_SAP_CODE Function Module for
CONVERT_TO_SAP_CODE is a standard convert to sap code SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 convert to sap code FM, simply by entering the name CONVERT_TO_SAP_CODE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FITP_CODES
Program Name: SAPLFITP_CODES
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CONVERT_TO_SAP_CODE 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 'CONVERT_TO_SAP_CODE'".
EXPORTING
CODE_ID = "
GDS = "
GDS_CODE = "
IMPORTING
CODE = "
IMPORTING Parameters details for CONVERT_TO_SAP_CODE
CODE_ID -
Data type: TA20GDS_CODES-CODE_IDOptional: No
Call by Reference: No ( called with pass by value option)
GDS -
Data type: TA20GDS_CODES-GDSOptional: No
Call by Reference: No ( called with pass by value option)
GDS_CODE -
Data type: TA20GDS_CODES-GDS_CODEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CONVERT_TO_SAP_CODE
CODE -
Data type: TA20GDS_CODES-CODEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CONVERT_TO_SAP_CODE 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_code | TYPE TA20GDS_CODES-CODE, " | |||
| lv_code_id | TYPE TA20GDS_CODES-CODE_ID, " | |||
| lv_gds | TYPE TA20GDS_CODES-GDS, " | |||
| lv_gds_code | TYPE TA20GDS_CODES-GDS_CODE. " |
|   CALL FUNCTION 'CONVERT_TO_SAP_CODE' " |
| EXPORTING | ||
| CODE_ID | = lv_code_id | |
| GDS | = lv_gds | |
| GDS_CODE | = lv_gds_code | |
| IMPORTING | ||
| CODE | = lv_code | |
| . " CONVERT_TO_SAP_CODE | ||
ABAP code using 7.40 inline data declarations to call FM CONVERT_TO_SAP_CODE
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.| "SELECT single CODE FROM TA20GDS_CODES INTO @DATA(ld_code). | ||||
| "SELECT single CODE_ID FROM TA20GDS_CODES INTO @DATA(ld_code_id). | ||||
| "SELECT single GDS FROM TA20GDS_CODES INTO @DATA(ld_gds). | ||||
| "SELECT single GDS_CODE FROM TA20GDS_CODES INTO @DATA(ld_gds_code). | ||||
Search for further information about these or an SAP related objects