SAP VENDOR_MAINTAIN_VB Function Module for NOTRANSL: Verbuchung Kreditor anstossen
VENDOR_MAINTAIN_VB is a standard vendor maintain vb SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Verbuchung Kreditor anstossen 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 vendor maintain vb FM, simply by entering the name VENDOR_MAINTAIN_VB into the relevant SAP transaction such as SE37 or SE38.
Function Group: WR11
Program Name: SAPLWR11
Main Program: SAPLWR11
Appliation area: W
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function VENDOR_MAINTAIN_VB 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 'VENDOR_MAINTAIN_VB'"NOTRANSL: Verbuchung Kreditor anstossen.
EXPORTING
* I_T001W = "
IMPORTING
A_LFA1 = "
TABLES
* PI_T_FIELDTAB = "
IMPORTING Parameters details for VENDOR_MAINTAIN_VB
I_T001W -
Data type: T001WOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for VENDOR_MAINTAIN_VB
A_LFA1 -
Data type: LFA1Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for VENDOR_MAINTAIN_VB
PI_T_FIELDTAB -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for VENDOR_MAINTAIN_VB 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_a_lfa1 | TYPE LFA1, " | |||
lv_i_t001w | TYPE T001W, " | |||
lt_pi_t_fieldtab | TYPE STANDARD TABLE OF T001W. " |
  CALL FUNCTION 'VENDOR_MAINTAIN_VB' "NOTRANSL: Verbuchung Kreditor anstossen |
EXPORTING | ||
I_T001W | = lv_i_t001w | |
IMPORTING | ||
A_LFA1 | = lv_a_lfa1 | |
TABLES | ||
PI_T_FIELDTAB | = lt_pi_t_fieldtab | |
. " VENDOR_MAINTAIN_VB |
ABAP code using 7.40 inline data declarations to call FM VENDOR_MAINTAIN_VB
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