SAP SD_SALES_DOCUMENT_UPDATE_MULTI Function Module for
SD_SALES_DOCUMENT_UPDATE_MULTI is a standard sd sales document update multi 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 sd sales document update multi FM, simply by entering the name SD_SALES_DOCUMENT_UPDATE_MULTI into the relevant SAP transaction such as SE37 or SE38.
Function Group: V45_EXTERNAL_UPDATE
Program Name: SAPLV45_EXTERNAL_UPDATE
Main Program: SAPLV45_EXTERNAL_UPDATE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SD_SALES_DOCUMENT_UPDATE_MULTI 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_SALES_DOCUMENT_UPDATE_MULTI'".
TABLES
FIT_XVBREVC = "Revenue Recognition: Worklist of Changed Sales Documents
TABLES Parameters details for SD_SALES_DOCUMENT_UPDATE_MULTI
FIT_XVBREVC - Revenue Recognition: Worklist of Changed Sales Documents
Data type: VBREVCOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for SD_SALES_DOCUMENT_UPDATE_MULTI 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: | ||||
| lt_fit_xvbrevc | TYPE STANDARD TABLE OF VBREVC. " |
|   CALL FUNCTION 'SD_SALES_DOCUMENT_UPDATE_MULTI' " |
| TABLES | ||
| FIT_XVBREVC | = lt_fit_xvbrevc | |
| . " SD_SALES_DOCUMENT_UPDATE_MULTI | ||
ABAP code using 7.40 inline data declarations to call FM SD_SALES_DOCUMENT_UPDATE_MULTI
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