SAP CHANGEDOCU_FIELDS_ANY2CHAR Function Module for









CHANGEDOCU_FIELDS_ANY2CHAR is a standard changedocu fields 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 fields any2char FM, simply by entering the name CHANGEDOCU_FIELDS_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_FIELDS_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_FIELDS_ANY2CHAR'"
  EXPORTING
   IV_TABNAME =  "Table Name
   IV_FIELDNAME =  "Field Name
*  IV_VALUE_OLD_ANY =  "
*  IV_VALUE_NEW_ANY =  "

 IMPORTING
   EV_VALUE_OLD_CHAR =  "
   EV_VALUE_NEW_CHAR =  "
   EV_STRING_OLD =  "
   EV_STRING_NEW =  "
   EV_RAWSTRING_OLD =  "
   EV_RAWSTRING_NEW =  "
   EV_SSTRING_OLD =  "
   EV_SSTRING_NEW =  "

EXCEPTIONS
   TABNAME_IS_EMPTY = 1    FIELDNAME_IS_EMPTY = 2    FIELDNAME_NOT_IN_TABLE = 3    NAMETAB_ERROR = 4
.



IMPORTING Parameters details for CHANGEDOCU_FIELDS_ANY2CHAR

IV_TABNAME - Table Name

Data type: CDPOS-TABNAME
Optional: No
Call by Reference: Yes

IV_FIELDNAME - Field Name

Data type: CDPOS-FNAME
Optional: No
Call by Reference: Yes

IV_VALUE_OLD_ANY -

Data type: ANY
Optional: Yes
Call by Reference: Yes

IV_VALUE_NEW_ANY -

Data type: ANY
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for CHANGEDOCU_FIELDS_ANY2CHAR

EV_VALUE_OLD_CHAR -

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

EV_VALUE_NEW_CHAR -

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

EV_STRING_OLD -

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

EV_STRING_NEW -

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

EV_RAWSTRING_OLD -

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

EV_RAWSTRING_NEW -

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

EV_SSTRING_OLD -

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

EV_SSTRING_NEW -

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

EXCEPTIONS details

TABNAME_IS_EMPTY -

Data type:
Optional: No
Call by Reference: Yes

FIELDNAME_IS_EMPTY - Field name is empty

Data type:
Optional: No
Call by Reference: Yes

FIELDNAME_NOT_IN_TABLE -

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_FIELDS_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_iv_tabname  TYPE CDPOS-TABNAME, "   
lv_tabname_is_empty  TYPE CDPOS, "   
lv_ev_value_old_char  TYPE C, "   
lv_iv_fieldname  TYPE CDPOS-FNAME, "   
lv_ev_value_new_char  TYPE C, "   
lv_fieldname_is_empty  TYPE C, "   
lv_ev_string_old  TYPE CDSTRINGVALO, "   
lv_iv_value_old_any  TYPE ANY, "   
lv_fieldname_not_in_table  TYPE ANY, "   
lv_ev_string_new  TYPE CDSTRINGVALN, "   
lv_nametab_error  TYPE CDSTRINGVALN, "   
lv_iv_value_new_any  TYPE ANY, "   
lv_ev_rawstring_old  TYPE CDRAWSTRINGO, "   
lv_ev_rawstring_new  TYPE CDRAWSTRINGN, "   
lv_ev_sstring_old  TYPE CDSHORTSTRINGO, "   
lv_ev_sstring_new  TYPE CDSHORTSTRINGN. "   

  CALL FUNCTION 'CHANGEDOCU_FIELDS_ANY2CHAR'  "
    EXPORTING
         IV_TABNAME = lv_iv_tabname
         IV_FIELDNAME = lv_iv_fieldname
         IV_VALUE_OLD_ANY = lv_iv_value_old_any
         IV_VALUE_NEW_ANY = lv_iv_value_new_any
    IMPORTING
         EV_VALUE_OLD_CHAR = lv_ev_value_old_char
         EV_VALUE_NEW_CHAR = lv_ev_value_new_char
         EV_STRING_OLD = lv_ev_string_old
         EV_STRING_NEW = lv_ev_string_new
         EV_RAWSTRING_OLD = lv_ev_rawstring_old
         EV_RAWSTRING_NEW = lv_ev_rawstring_new
         EV_SSTRING_OLD = lv_ev_sstring_old
         EV_SSTRING_NEW = lv_ev_sstring_new
    EXCEPTIONS
        TABNAME_IS_EMPTY = 1
        FIELDNAME_IS_EMPTY = 2
        FIELDNAME_NOT_IN_TABLE = 3
        NAMETAB_ERROR = 4
. " CHANGEDOCU_FIELDS_ANY2CHAR




ABAP code using 7.40 inline data declarations to call FM CHANGEDOCU_FIELDS_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 TABNAME FROM CDPOS INTO @DATA(ld_iv_tabname).
 
 
 
"SELECT single FNAME FROM CDPOS INTO @DATA(ld_iv_fieldname).
 
 
 
 
 
 
 
 
 
 
 
 
 


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!