SAP SD_VBUP_READ_FROM_DOC Function Module for Read VBUP related data from Document (VBAP, LIPS)
SD_VBUP_READ_FROM_DOC is a standard sd vbup read from doc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read VBUP related data from Document (VBAP, LIPS) 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 sd vbup read from doc FM, simply by entering the name SD_VBUP_READ_FROM_DOC into the relevant SAP transaction such as SE37 or SE38.
Function Group: V45I
Program Name: SAPLV45I
Main Program: SAPLV45I
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SD_VBUP_READ_FROM_DOC 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 'SD_VBUP_READ_FROM_DOC'"Read VBUP related data from Document (VBAP, LIPS).
EXPORTING
I_VBELN = "Sales document number
* I_POSNR = "Position number of sales document
* I_VBTYP = "Sales document type
* I_VBOBJ = "Sales document object type
IMPORTING
ET_VBUP = "Table Type VBUP
ES_VBUP = "Sales Document: Item Status
ET_VBUPVB = "Table Type for XVBUP/YVBUP
ES_VBUPVB = "Structure for XVBUP/YVBUP
EXCEPTIONS
VBELN_NOT_FOUND = 1 VBTYP_NOT_SUPPORTED = 2 VBOBJ_NOT_SUPPORTED = 3
IMPORTING Parameters details for SD_VBUP_READ_FROM_DOC
I_VBELN - Sales document number
Data type: VBELNOptional: No
Call by Reference: Yes
I_POSNR - Position number of sales document
Data type: POSNROptional: Yes
Call by Reference: Yes
I_VBTYP - Sales document type
Data type: VBTYPLOptional: Yes
Call by Reference: Yes
I_VBOBJ - Sales document object type
Data type: VBOBJOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for SD_VBUP_READ_FROM_DOC
ET_VBUP - Table Type VBUP
Data type: VBUP_TOptional: No
Call by Reference: Yes
ES_VBUP - Sales Document: Item Status
Data type: VBUPOptional: No
Call by Reference: Yes
ET_VBUPVB - Table Type for XVBUP/YVBUP
Data type: TAB_XYVBUPOptional: No
Call by Reference: Yes
ES_VBUPVB - Structure for XVBUP/YVBUP
Data type: VBUPVBOptional: No
Call by Reference: Yes
EXCEPTIONS details
VBELN_NOT_FOUND - VBELN not found
Data type:Optional: No
Call by Reference: Yes
VBTYP_NOT_SUPPORTED - VBTYP not supported
Data type:Optional: No
Call by Reference: Yes
VBOBJ_NOT_SUPPORTED - VBOBJ not supported
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SD_VBUP_READ_FROM_DOC 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_et_vbup | TYPE VBUP_T, " | |||
| lv_i_vbeln | TYPE VBELN, " | |||
| lv_vbeln_not_found | TYPE VBELN, " | |||
| lv_es_vbup | TYPE VBUP, " | |||
| lv_i_posnr | TYPE POSNR, " | |||
| lv_vbtyp_not_supported | TYPE POSNR, " | |||
| lv_i_vbtyp | TYPE VBTYPL, " | |||
| lv_et_vbupvb | TYPE TAB_XYVBUP, " | |||
| lv_vbobj_not_supported | TYPE TAB_XYVBUP, " | |||
| lv_i_vbobj | TYPE VBOBJ, " | |||
| lv_es_vbupvb | TYPE VBUPVB. " |
|   CALL FUNCTION 'SD_VBUP_READ_FROM_DOC' "Read VBUP related data from Document (VBAP, LIPS) |
| EXPORTING | ||
| I_VBELN | = lv_i_vbeln | |
| I_POSNR | = lv_i_posnr | |
| I_VBTYP | = lv_i_vbtyp | |
| I_VBOBJ | = lv_i_vbobj | |
| IMPORTING | ||
| ET_VBUP | = lv_et_vbup | |
| ES_VBUP | = lv_es_vbup | |
| ET_VBUPVB | = lv_et_vbupvb | |
| ES_VBUPVB | = lv_es_vbupvb | |
| EXCEPTIONS | ||
| VBELN_NOT_FOUND = 1 | ||
| VBTYP_NOT_SUPPORTED = 2 | ||
| VBOBJ_NOT_SUPPORTED = 3 | ||
| . " SD_VBUP_READ_FROM_DOC | ||
ABAP code using 7.40 inline data declarations to call FM SD_VBUP_READ_FROM_DOC
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