SAP LXYRD_SCHDL_DISPLAY Function Module for Display scheduling activity
LXYRD_SCHDL_DISPLAY is a standard lxyrd schdl display SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display scheduling activity processing and below is the pattern details for this FM, 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 lxyrd schdl display FM, simply by entering the name LXYRD_SCHDL_DISPLAY into the relevant SAP transaction such as SE37 or SE38.
Function Group: LXYRD_ACTV
Program Name: SAPLLXYRD_ACTV
Main Program: SAPLLXYRD_ACTV
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LXYRD_SCHDL_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 'LXYRD_SCHDL_DISPLAY'"Display scheduling activity.
EXPORTING
IV_YARD = "Yard
IV_VENUM = "Internal Handling Unit Number
IMPORTING Parameters details for LXYRD_SCHDL_DISPLAY
IV_YARD - Yard
Data type: LXYRD_YARDOptional: No
Call by Reference: No ( called with pass by value option)
IV_VENUM - Internal Handling Unit Number
Data type: LEINT_YHU_HEADER-VENUMOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for LXYRD_SCHDL_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_iv_yard | TYPE LXYRD_YARD, " | |||
| lv_iv_venum | TYPE LEINT_YHU_HEADER-VENUM. " |
|   CALL FUNCTION 'LXYRD_SCHDL_DISPLAY' "Display scheduling activity |
| EXPORTING | ||
| IV_YARD | = lv_iv_yard | |
| IV_VENUM | = lv_iv_venum | |
| . " LXYRD_SCHDL_DISPLAY | ||
ABAP code using 7.40 inline data declarations to call FM LXYRD_SCHDL_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 VENUM FROM LEINT_YHU_HEADER INTO @DATA(ld_iv_venum). | ||||
Search for further information about these or an SAP related objects