SAP BAPI_VENDORSETTL_GETDETAIL Function Module for Agency Business: BAPI Vendor Settlement Detailed Data









BAPI_VENDORSETTL_GETDETAIL is a standard bapi vendorsettl getdetail SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Agency Business: BAPI Vendor Settlement Detailed 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 bapi vendorsettl getdetail FM, simply by entering the name BAPI_VENDORSETTL_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.

Function Group: 2126_EA
Program Name: SAPL2126_EA
Main Program: SAPL2126_EA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BAPI_VENDORSETTL_GETDETAIL 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 'BAPI_VENDORSETTL_GETDETAIL'"Agency Business: BAPI Vendor Settlement Detailed Data
  EXPORTING
   PARAMETERS =  "Communication Structure: Parameter for GetDetail BAPIs

TABLES
   DOCUMENTS =  "Vendor billing document: key for table WBRK for mass access
*  PARTNEROUT =  "BAPI Structure of WBPA with English Field Names
*  ADDRESSOUT =  "Communication Structure: Address Data for BAPI
*  HEADDATAOUT_OD =  "Communication Structure: Payment Document Header Data
*  ITEMDATAOUT_OD =  "Communication Structure: Payment Document Item Data
*  CUSTOMERCONDOUT =  "Com. Structure: Conditions Agency Business Customer (KOMV)
*  CUSTOMERCONDPRINTOUT =  "Communication Structure: Conditions Agency Business Customer (KOMVD)
*  HEADDATAOUT =  "Communication Structure: Header Data - Vendor Settlement
*  ITEMDATAOUT =  "Communiation Structure: Item Data Vendor Settlement
*  RETURN =  "Return Parameter(s)
*  EXTENSIONOUT =  "Reference Structure for BAPI Parameters ExtensionIn/ExtensionOut
*  HEADTEXTOUT =  "Agency Business: Header Text For Change Case
*  ITEMTEXTOUT =  "Agency Business: Item Texts, Change Case
*  VENDORCONDOUT =  "Communication Structure: Conditions Agency Business (KOMV)
*  VENDORCONDPRINTOUT =  "Communication Structure: Conditions Agency Business (KOMVD)
.



IMPORTING Parameters details for BAPI_VENDORSETTL_GETDETAIL

PARAMETERS - Communication Structure: Parameter for GetDetail BAPIs

Data type: BAPILFDETPAR
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BAPI_VENDORSETTL_GETDETAIL

DOCUMENTS - Vendor billing document: key for table WBRK for mass access

Data type: WBRK_KEY
Optional: No
Call by Reference: Yes

PARTNEROUT - BAPI Structure of WBPA with English Field Names

Data type: BAPILFPART
Optional: Yes
Call by Reference: Yes

ADDRESSOUT - Communication Structure: Address Data for BAPI

Data type: BAPILFADDRESS
Optional: Yes
Call by Reference: Yes

HEADDATAOUT_OD - Communication Structure: Payment Document Header Data

Data type: BAPISRHEADO
Optional: Yes
Call by Reference: Yes

ITEMDATAOUT_OD - Communication Structure: Payment Document Item Data

Data type: BAPISRITEMO
Optional: Yes
Call by Reference: Yes

CUSTOMERCONDOUT - Com. Structure: Conditions Agency Business Customer (KOMV)

Data type: BAPILFCONDUO
Optional: Yes
Call by Reference: Yes

CUSTOMERCONDPRINTOUT - Communication Structure: Conditions Agency Business Customer (KOMVD)

Data type: BAPILFCONDUPRINT
Optional: Yes
Call by Reference: Yes

HEADDATAOUT - Communication Structure: Header Data - Vendor Settlement

Data type: BAPIVSHEADO
Optional: Yes
Call by Reference: Yes

ITEMDATAOUT - Communiation Structure: Item Data Vendor Settlement

Data type: BAPIVSITEMO
Optional: Yes
Call by Reference: Yes

RETURN - Return Parameter(s)

Data type: BAPIRET2
Optional: Yes
Call by Reference: Yes

EXTENSIONOUT - Reference Structure for BAPI Parameters ExtensionIn/ExtensionOut

Data type: BAPIPAREX
Optional: Yes
Call by Reference: Yes

HEADTEXTOUT - Agency Business: Header Text For Change Case

Data type: BAPIABHEADCTEXT
Optional: Yes
Call by Reference: Yes

ITEMTEXTOUT - Agency Business: Item Texts, Change Case

Data type: BAPIABITEMCTEXT
Optional: Yes
Call by Reference: Yes

VENDORCONDOUT - Communication Structure: Conditions Agency Business (KOMV)

Data type: BAPILFCONDO
Optional: Yes
Call by Reference: Yes

VENDORCONDPRINTOUT - Communication Structure: Conditions Agency Business (KOMVD)

Data type: BAPILFCONDPRINT
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for BAPI_VENDORSETTL_GETDETAIL 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_documents  TYPE STANDARD TABLE OF WBRK_KEY, "   
lv_parameters  TYPE BAPILFDETPAR, "   
lt_partnerout  TYPE STANDARD TABLE OF BAPILFPART, "   
lt_addressout  TYPE STANDARD TABLE OF BAPILFADDRESS, "   
lt_headdataout_od  TYPE STANDARD TABLE OF BAPISRHEADO, "   
lt_itemdataout_od  TYPE STANDARD TABLE OF BAPISRITEMO, "   
lt_customercondout  TYPE STANDARD TABLE OF BAPILFCONDUO, "   
lt_customercondprintout  TYPE STANDARD TABLE OF BAPILFCONDUPRINT, "   
lt_headdataout  TYPE STANDARD TABLE OF BAPIVSHEADO, "   
lt_itemdataout  TYPE STANDARD TABLE OF BAPIVSITEMO, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lt_extensionout  TYPE STANDARD TABLE OF BAPIPAREX, "   
lt_headtextout  TYPE STANDARD TABLE OF BAPIABHEADCTEXT, "   
lt_itemtextout  TYPE STANDARD TABLE OF BAPIABITEMCTEXT, "   
lt_vendorcondout  TYPE STANDARD TABLE OF BAPILFCONDO, "   
lt_vendorcondprintout  TYPE STANDARD TABLE OF BAPILFCONDPRINT. "   

  CALL FUNCTION 'BAPI_VENDORSETTL_GETDETAIL'  "Agency Business: BAPI Vendor Settlement Detailed Data
    EXPORTING
         PARAMETERS = lv_parameters
    TABLES
         DOCUMENTS = lt_documents
         PARTNEROUT = lt_partnerout
         ADDRESSOUT = lt_addressout
         HEADDATAOUT_OD = lt_headdataout_od
         ITEMDATAOUT_OD = lt_itemdataout_od
         CUSTOMERCONDOUT = lt_customercondout
         CUSTOMERCONDPRINTOUT = lt_customercondprintout
         HEADDATAOUT = lt_headdataout
         ITEMDATAOUT = lt_itemdataout
         RETURN = lt_return
         EXTENSIONOUT = lt_extensionout
         HEADTEXTOUT = lt_headtextout
         ITEMTEXTOUT = lt_itemtextout
         VENDORCONDOUT = lt_vendorcondout
         VENDORCONDPRINTOUT = lt_vendorcondprintout
. " BAPI_VENDORSETTL_GETDETAIL




ABAP code using 7.40 inline data declarations to call FM BAPI_VENDORSETTL_GETDETAIL

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!