SAP VBDBDM_DATA_MAINTAIN_RFC Function Module for Maintain Documentary Batches - RFC
VBDBDM_DATA_MAINTAIN_RFC is a standard vbdbdm data maintain rfc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Maintain Documentary Batches - RFC 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 vbdbdm data maintain rfc FM, simply by entering the name VBDBDM_DATA_MAINTAIN_RFC into the relevant SAP transaction such as SE37 or SE38.
Function Group: VBDOCUBATCH_DM
Program Name: SAPLVBDOCUBATCH_DM
Main Program: SAPLVBDOCUBATCH_DM
Appliation area:
Release date: 19-Jan-2009
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function VBDBDM_DATA_MAINTAIN_RFC 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 'VBDBDM_DATA_MAINTAIN_RFC'"Maintain Documentary Batches - RFC.
EXPORTING
I_MATNR = "Material Number
* I_EBELP = "Item Number of Purchasing Document
* I_AUFNR = "Order Number
* I_AUFPS = "Number of Order Item
* I_RSNUM = "Number of Reservation / Dependent Requirement
* I_RSPOS = "Item Number of Reservation/Dependent Requirement
* I_RSART = "Record Type
* I_VBELN = "Delivery
* I_POSNR = "Delivery Item
* IS_DOCUBATCH_COM = "Documentary Batch - Communication Structure
* I_LINE_ID = "Unique Identification of Document Line
I_WERKS = "Plant
* I_LGNUM = "Warehouse Number/Warehouse Complex
* I_TANUM = "Transfer Order Number
* I_TAPOS = "Transfer order item
I_QUANTITY = "Quantity in Unit of Entry
I_UOM = "Unit of Entry
* I_DOCUBATCH_CHARG = "Documentary Batch - Batch Number
* IT_DOCUBATCHES = "Documentary Batch - Table Screen Fields
* I_PROCESS_ID = "Definable Processes for Documentary Batches
* I_REPLACE_EXISTING_DATA = "Checkbox
* I_EBELN = "Purchasing Document Number
EXCEPTIONS
PARAMETER_ERROR = 1 PROCESS_NOT_ACTIVE = 2
IMPORTING Parameters details for VBDBDM_DATA_MAINTAIN_RFC
I_MATNR - Material Number
Data type: MATNROptional: No
Call by Reference: No ( called with pass by value option)
I_EBELP - Item Number of Purchasing Document
Data type: EBELPOptional: Yes
Call by Reference: No ( called with pass by value option)
I_AUFNR - Order Number
Data type: AUFNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_AUFPS - Number of Order Item
Data type: CO_POSNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_RSNUM - Number of Reservation / Dependent Requirement
Data type: RSNUMOptional: Yes
Call by Reference: No ( called with pass by value option)
I_RSPOS - Item Number of Reservation/Dependent Requirement
Data type: RSPOSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_RSART - Record Type
Data type: RSARTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_VBELN - Delivery
Data type: VBELN_VLOptional: Yes
Call by Reference: No ( called with pass by value option)
I_POSNR - Delivery Item
Data type: POSNR_VLOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_DOCUBATCH_COM - Documentary Batch - Communication Structure
Data type: DOCUBATCH_COMOptional: Yes
Call by Reference: No ( called with pass by value option)
I_LINE_ID - Unique Identification of Document Line
Data type: MB_LINE_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_WERKS - Plant
Data type: WERKS_DOptional: No
Call by Reference: No ( called with pass by value option)
I_LGNUM - Warehouse Number/Warehouse Complex
Data type: LGNUMOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TANUM - Transfer Order Number
Data type: TANUMOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TAPOS - Transfer order item
Data type: TAPOSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_QUANTITY - Quantity in Unit of Entry
Data type: ERFMGOptional: No
Call by Reference: No ( called with pass by value option)
I_UOM - Unit of Entry
Data type: ERFMEOptional: No
Call by Reference: No ( called with pass by value option)
I_DOCUBATCH_CHARG - Documentary Batch - Batch Number
Data type: DOCUBATCH_CHARGOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_DOCUBATCHES - Documentary Batch - Table Screen Fields
Data type: DOCUBATCH_SCREEN_FIELDS_TTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PROCESS_ID - Definable Processes for Documentary Batches
Data type: DOCUBATCH_PROCESS_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_REPLACE_EXISTING_DATA - Checkbox
Data type: DOCUBATCH_REPLACEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_EBELN - Purchasing Document Number
Data type: EBELNOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PARAMETER_ERROR - Transfer parameters containing errors
Data type:Optional: No
Call by Reference: Yes
PROCESS_NOT_ACTIVE - Process Not Active
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for VBDBDM_DATA_MAINTAIN_RFC 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_matnr | TYPE MATNR, " | |||
| lv_parameter_error | TYPE MATNR, " | |||
| lv_i_ebelp | TYPE EBELP, " | |||
| lv_i_aufnr | TYPE AUFNR, " | |||
| lv_i_aufps | TYPE CO_POSNR, " | |||
| lv_i_rsnum | TYPE RSNUM, " | |||
| lv_i_rspos | TYPE RSPOS, " | |||
| lv_i_rsart | TYPE RSART, " | |||
| lv_i_vbeln | TYPE VBELN_VL, " | |||
| lv_i_posnr | TYPE POSNR_VL, " | |||
| lv_is_docubatch_com | TYPE DOCUBATCH_COM, " | |||
| lv_i_line_id | TYPE MB_LINE_ID, " | |||
| lv_i_werks | TYPE WERKS_D, " | |||
| lv_process_not_active | TYPE WERKS_D, " | |||
| lv_i_lgnum | TYPE LGNUM, " | |||
| lv_i_tanum | TYPE TANUM, " | |||
| lv_i_tapos | TYPE TAPOS, " | |||
| lv_i_quantity | TYPE ERFMG, " | |||
| lv_i_uom | TYPE ERFME, " | |||
| lv_i_docubatch_charg | TYPE DOCUBATCH_CHARG, " | |||
| lv_it_docubatches | TYPE DOCUBATCH_SCREEN_FIELDS_TT, " | |||
| lv_i_process_id | TYPE DOCUBATCH_PROCESS_ID, " | |||
| lv_i_replace_existing_data | TYPE DOCUBATCH_REPLACE, " | |||
| lv_i_ebeln | TYPE EBELN. " |
|   CALL FUNCTION 'VBDBDM_DATA_MAINTAIN_RFC' "Maintain Documentary Batches - RFC |
| EXPORTING | ||
| I_MATNR | = lv_i_matnr | |
| I_EBELP | = lv_i_ebelp | |
| I_AUFNR | = lv_i_aufnr | |
| I_AUFPS | = lv_i_aufps | |
| I_RSNUM | = lv_i_rsnum | |
| I_RSPOS | = lv_i_rspos | |
| I_RSART | = lv_i_rsart | |
| I_VBELN | = lv_i_vbeln | |
| I_POSNR | = lv_i_posnr | |
| IS_DOCUBATCH_COM | = lv_is_docubatch_com | |
| I_LINE_ID | = lv_i_line_id | |
| I_WERKS | = lv_i_werks | |
| I_LGNUM | = lv_i_lgnum | |
| I_TANUM | = lv_i_tanum | |
| I_TAPOS | = lv_i_tapos | |
| I_QUANTITY | = lv_i_quantity | |
| I_UOM | = lv_i_uom | |
| I_DOCUBATCH_CHARG | = lv_i_docubatch_charg | |
| IT_DOCUBATCHES | = lv_it_docubatches | |
| I_PROCESS_ID | = lv_i_process_id | |
| I_REPLACE_EXISTING_DATA | = lv_i_replace_existing_data | |
| I_EBELN | = lv_i_ebeln | |
| EXCEPTIONS | ||
| PARAMETER_ERROR = 1 | ||
| PROCESS_NOT_ACTIVE = 2 | ||
| . " VBDBDM_DATA_MAINTAIN_RFC | ||
ABAP code using 7.40 inline data declarations to call FM VBDBDM_DATA_MAINTAIN_RFC
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