SAP SO_DYNP_DOCUMENT_DISPLAY Function Module for
SO_DYNP_DOCUMENT_DISPLAY is a standard so dynp document display 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 so dynp document display FM, simply by entering the name SO_DYNP_DOCUMENT_DISPLAY into the relevant SAP transaction such as SE37 or SE38.
Function Group: SO10
Program Name: SAPLSO10
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function SO_DYNP_DOCUMENT_DISPLAY 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 'SO_DYNP_DOCUMENT_DISPLAY'".
EXPORTING
OBJECTS = "
* OBJECT_FL_DISPLAY = "
* OWNER = "
* OK_CODE = DISP "
IMPORTING Parameters details for SO_DYNP_DOCUMENT_DISPLAY
OBJECTS -
Data type: SOOD4Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_FL_DISPLAY -
Data type: SOFM2Optional: Yes
Call by Reference: No ( called with pass by value option)
OWNER -
Data type: SOUD-USRNAMOptional: Yes
Call by Reference: No ( called with pass by value option)
OK_CODE -
Data type: SY-UCOMMDefault: DISP
Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SO_DYNP_DOCUMENT_DISPLAY 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_objects | TYPE SOOD4, " | |||
lv_object_fl_display | TYPE SOFM2, " | |||
lv_owner | TYPE SOUD-USRNAM, " | |||
lv_ok_code | TYPE SY-UCOMM. " DISP |
  CALL FUNCTION 'SO_DYNP_DOCUMENT_DISPLAY' " |
EXPORTING | ||
OBJECTS | = lv_objects | |
OBJECT_FL_DISPLAY | = lv_object_fl_display | |
OWNER | = lv_owner | |
OK_CODE | = lv_ok_code | |
. " SO_DYNP_DOCUMENT_DISPLAY |
ABAP code using 7.40 inline data declarations to call FM SO_DYNP_DOCUMENT_DISPLAY
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 USRNAM FROM SOUD INTO @DATA(ld_owner). | ||||
"SELECT single UCOMM FROM SY INTO @DATA(ld_ok_code). | ||||
DATA(ld_ok_code) | = DISP. | |||
Search for further information about these or an SAP related objects