SAP RPY_DYNPRO_READ_NATIVE Function Module for

Search SAP Function Modules

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

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

Function RPY_DYNPRO_READ_NATIVE 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_DYNPRO_READ_NATIVE'"
  EXPORTING
   PROGNAME =  "Program name of screen
   DYNNR =  "Screen number
*  SUPPRESS_EXIST_CHECKS = ' ' "
*  SUPPRESS_CORR_CHECKS = ' ' "

 IMPORTING
   HEADER =  "Screen header in internal format
   DYNPROTEXT =  "Screen description text in language LANGUAGE

TABLES
*  FIELDLIST =  "Screen field list in internal format
*  FLOWLOGIC =  "Screen flow logic
*  PARAMS =  "
*  FIELDTEXTS =  "Screen-specific field texts in language LANGUAGE

EXCEPTIONS
   CANCELLED = 1    NOT_FOUND = 2    PERMISSION_ERROR = 3 

.

IMPORTING Parameters details for RPY_DYNPRO_READ_NATIVE

PROGNAME - Program name of screen

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

DYNNR - Screen number

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

SUPPRESS_EXIST_CHECKS -

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

SUPPRESS_CORR_CHECKS -

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

EXPORTING Parameters details for RPY_DYNPRO_READ_NATIVE

HEADER - Screen header in internal format

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

DYNPROTEXT - Screen description text in language LANGUAGE

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

TABLES Parameters details for RPY_DYNPRO_READ_NATIVE

FIELDLIST - Screen field list in internal format

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

FLOWLOGIC - Screen flow logic

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

PARAMS -

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

FIELDTEXTS - Screen-specific field texts in language LANGUAGE

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

EXCEPTIONS details

CANCELLED - Canceled by user in correction dialog box

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

NOT_FOUND - Screen not found

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

PERMISSION_ERROR - No authorization to import (read)

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

Copy and paste ABAP code example for RPY_DYNPRO_READ_NATIVE 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_DYNPRO_READ_NATIVE

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