SAP RPY_DATAELEMENT_UPDATE Function Module for

Search SAP Function Modules

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

Function Group: SIFD
Program Name: SAPLSIFD
Main Program: SAPLSIFD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RPY_DATAELEMENT_UPDATE 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 'RPY_DATAELEMENT_UPDATE'"
  EXPORTING
*  ACTIVATION_TYPE = 'M' "
   DATAELEMENT_NAME =  "
   DTEL_INF =  "
*  LANGUAGE = SY-LANGU "
*  WITH_DOCU = ' ' "
*  TRANSPORT_NUMBER = ' ' "
*  DOCUTYPE = 'T' "

TABLES
*  DOCU_TABLE_USER =  "
*  DOCU_TABLE_TECH =  "

EXCEPTIONS
   CANCELLED = 1    NOT_EXIST = 2    PERMISSION_ERROR = 3    ILLEGAL_TYPE = 4    OBJECT_INCONSISTENT = 5    DB_ACCESS_ERROR = 6 

.

IMPORTING Parameters details for RPY_DATAELEMENT_UPDATE

ACTIVATION_TYPE -

Data type: DD04L-AS4LOCAL
Default: 'M'
Optional: Yes
Call by Reference: No ( called with pass by value option)

DATAELEMENT_NAME -

Data type: RPY_DTEL-DTELNAME
Optional: No
Call by Reference: No ( called with pass by value option)

DTEL_INF -

Data type: RPY_DTEL
Optional: No
Call by Reference: No ( called with pass by value option)

LANGUAGE -

Data type: SY-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

WITH_DOCU -

Data type: RGLIF-WITH_DOCU
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

TRANSPORT_NUMBER -

Data type: RGLIF-TRKORR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

DOCUTYPE -

Data type: RGLIF-DOCUTYPE
Default: 'T'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for RPY_DATAELEMENT_UPDATE

DOCU_TABLE_USER -

Data type: RPY_OBJTAB
Optional: Yes
Call by Reference: No ( called with pass by value option)

DOCU_TABLE_TECH -

Data type: TLINE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

CANCELLED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NOT_EXIST - Data element does not exist

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PERMISSION_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ILLEGAL_TYPE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

OBJECT_INCONSISTENT -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

DB_ACCESS_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

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

ABAP code using 7.40 inline data declarations to call FM RPY_DATAELEMENT_UPDATE

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