SAP CHANGEDOCU_FILLTABKEY254 Function Module for









CHANGEDOCU_FILLTABKEY254 is a standard changedocu filltabkey254 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 filltabkey254 FM, simply by entering the name CHANGEDOCU_FILLTABKEY254 into the relevant SAP transaction such as SE37 or SE38.

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



Function CHANGEDOCU_FILLTABKEY254 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_FILLTABKEY254'"
EXPORTING
* IS_CDHDR = "Internal Table CDHDR
IS_CDPOS = "Change document items
* IT_CDPOS_UID = "Internal Table CDPOS_UID
* IT_CDPOS_STR = "

IMPORTING
ES_EDITPOS = "Change Documents, Display Structure
EV_RC = "Return code

EXCEPTIONS
OBJECTCLAS_EMPTY = 1 STR_READ_ERROR = 10 OBJECTID_EMPTY = 2 CHANGENR_EMPTY = 3 UNICODE_CHECK_ERROR = 4 IS_KEY_INTRAW_ERROR = 5 KEY_ANY2CHAR_ERROR = 6 TABKEYLEN_GET_ERROR = 7 CDPOS_TABKEY_FOR_GUID_EMPTY = 8 GUID_READ_ERROR = 9
.



IMPORTING Parameters details for CHANGEDOCU_FILLTABKEY254

IS_CDHDR - Internal Table CDHDR

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

IS_CDPOS - Change document items

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

IT_CDPOS_UID - Internal Table CDPOS_UID

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

IT_CDPOS_STR -

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

EXPORTING Parameters details for CHANGEDOCU_FILLTABKEY254

ES_EDITPOS - Change Documents, Display Structure

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

EV_RC - Return code

Data type: SY-SUBRC
Optional: No
Call by Reference: Yes

EXCEPTIONS details

OBJECTCLAS_EMPTY -

Data type:
Optional: No
Call by Reference: Yes

STR_READ_ERROR -

Data type:
Optional: No
Call by Reference: Yes

OBJECTID_EMPTY -

Data type:
Optional: No
Call by Reference: Yes

CHANGENR_EMPTY -

Data type:
Optional: No
Call by Reference: Yes

UNICODE_CHECK_ERROR -

Data type:
Optional: No
Call by Reference: Yes

IS_KEY_INTRAW_ERROR -

Data type:
Optional: No
Call by Reference: Yes

KEY_ANY2CHAR_ERROR -

Data type:
Optional: No
Call by Reference: Yes

TABKEYLEN_GET_ERROR -

Data type:
Optional: No
Call by Reference: Yes

CDPOS_TABKEY_FOR_GUID_EMPTY -

Data type:
Optional: No
Call by Reference: Yes

GUID_READ_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CHANGEDOCU_FILLTABKEY254 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_is_cdhdr  TYPE CDHDR, "   
lv_es_editpos  TYPE CDRED, "   
lv_objectclas_empty  TYPE CDRED, "   
lv_str_read_error  TYPE CDRED, "   
lv_ev_rc  TYPE SY-SUBRC, "   
lv_is_cdpos  TYPE CDPOS, "   
lv_objectid_empty  TYPE CDPOS, "   
lv_it_cdpos_uid  TYPE CDPOS_UID_TAB, "   
lv_changenr_empty  TYPE CDPOS_UID_TAB, "   
lv_it_cdpos_str  TYPE CDPOS_STR_TAB, "   
lv_unicode_check_error  TYPE CDPOS_STR_TAB, "   
lv_is_key_intraw_error  TYPE CDPOS_STR_TAB, "   
lv_key_any2char_error  TYPE CDPOS_STR_TAB, "   
lv_tabkeylen_get_error  TYPE CDPOS_STR_TAB, "   
lv_cdpos_tabkey_for_guid_empty  TYPE CDPOS_STR_TAB, "   
lv_guid_read_error  TYPE CDPOS_STR_TAB. "   

  CALL FUNCTION 'CHANGEDOCU_FILLTABKEY254'  "
    EXPORTING
         IS_CDHDR = lv_is_cdhdr
         IS_CDPOS = lv_is_cdpos
         IT_CDPOS_UID = lv_it_cdpos_uid
         IT_CDPOS_STR = lv_it_cdpos_str
    IMPORTING
         ES_EDITPOS = lv_es_editpos
         EV_RC = lv_ev_rc
    EXCEPTIONS
        OBJECTCLAS_EMPTY = 1
        STR_READ_ERROR = 10
        OBJECTID_EMPTY = 2
        CHANGENR_EMPTY = 3
        UNICODE_CHECK_ERROR = 4
        IS_KEY_INTRAW_ERROR = 5
        KEY_ANY2CHAR_ERROR = 6
        TABKEYLEN_GET_ERROR = 7
        CDPOS_TABKEY_FOR_GUID_EMPTY = 8
        GUID_READ_ERROR = 9
. " CHANGEDOCU_FILLTABKEY254




ABAP code using 7.40 inline data declarations to call FM CHANGEDOCU_FILLTABKEY254

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 SUBRC FROM SY INTO @DATA(ld_ev_rc).
 
 
 
 
 
 
 
 
 
 
 
 


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!