SAP LOAD_VDORDER Function Module for Load Order Data
LOAD_VDORDER is a standard load vdorder SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Load Order Data 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 load vdorder FM, simply by entering the name LOAD_VDORDER into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVVD
Program Name: SAPLFVVD
Main Program: SAPLFVVD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LOAD_VDORDER 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 'LOAD_VDORDER'"Load Order Data.
EXPORTING
I_BUKRS = "
I_RANL = "
TABLES
YVDORDER = "
EXCEPTIONS
NO_ORDER = 1
IMPORTING Parameters details for LOAD_VDORDER
I_BUKRS -
Data type: T001-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_RANL -
Data type: VDORDER-RANLOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for LOAD_VDORDER
YVDORDER -
Data type: VDORDEROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_ORDER -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for LOAD_VDORDER 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_i_bukrs | TYPE T001-BUKRS, " | |||
| lv_no_order | TYPE T001, " | |||
| lt_yvdorder | TYPE STANDARD TABLE OF VDORDER, " | |||
| lv_i_ranl | TYPE VDORDER-RANL. " |
|   CALL FUNCTION 'LOAD_VDORDER' "Load Order Data |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| I_RANL | = lv_i_ranl | |
| TABLES | ||
| YVDORDER | = lt_yvdorder | |
| EXCEPTIONS | ||
| NO_ORDER = 1 | ||
| . " LOAD_VDORDER | ||
ABAP code using 7.40 inline data declarations to call FM LOAD_VDORDER
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 BUKRS FROM T001 INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single RANL FROM VDORDER INTO @DATA(ld_i_ranl). | ||||
Search for further information about these or an SAP related objects