SAP CHANGEDOCU_KEY_ANY2CHAR Function Module for
CHANGEDOCU_KEY_ANY2CHAR is a standard changedocu key any2char 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 changedocu key any2char FM, simply by entering the name CHANGEDOCU_KEY_ANY2CHAR into the relevant SAP transaction such as SE37 or SE38.
Function Group: SCD8
Program Name: SAPLSCD8
Main Program: SAPLSCD8
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CHANGEDOCU_KEY_ANY2CHAR 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 'CHANGEDOCU_KEY_ANY2CHAR'".
EXPORTING
IV_STRUCT_IN = "
IV_TABNAME = "
IMPORTING
EV_TABKEY = "
EXCEPTIONS
TABNAME_IS_EMPTY = 1 NAMETAB_ERROR = 2
IMPORTING Parameters details for CHANGEDOCU_KEY_ANY2CHAR
IV_STRUCT_IN -
Data type: ANYOptional: No
Call by Reference: No ( called with pass by value option)
IV_TABNAME -
Data type: CDPOS-TABNAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CHANGEDOCU_KEY_ANY2CHAR
EV_TABKEY -
Data type: CDPOS_UID-TABKEYOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
TABNAME_IS_EMPTY -
Data type:Optional: No
Call by Reference: Yes
NAMETAB_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CHANGEDOCU_KEY_ANY2CHAR 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_ev_tabkey | TYPE CDPOS_UID-TABKEY, " | |||
| lv_iv_struct_in | TYPE ANY, " | |||
| lv_tabname_is_empty | TYPE ANY, " | |||
| lv_iv_tabname | TYPE CDPOS-TABNAME, " | |||
| lv_nametab_error | TYPE CDPOS. " |
|   CALL FUNCTION 'CHANGEDOCU_KEY_ANY2CHAR' " |
| EXPORTING | ||
| IV_STRUCT_IN | = lv_iv_struct_in | |
| IV_TABNAME | = lv_iv_tabname | |
| IMPORTING | ||
| EV_TABKEY | = lv_ev_tabkey | |
| EXCEPTIONS | ||
| TABNAME_IS_EMPTY = 1 | ||
| NAMETAB_ERROR = 2 | ||
| . " CHANGEDOCU_KEY_ANY2CHAR | ||
ABAP code using 7.40 inline data declarations to call FM CHANGEDOCU_KEY_ANY2CHAR
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 TABKEY FROM CDPOS_UID INTO @DATA(ld_ev_tabkey). | ||||
| "SELECT single TABNAME FROM CDPOS INTO @DATA(ld_iv_tabname). | ||||
Search for further information about these or an SAP related objects