SAP APAR_EBPP_PUT_DISPUTE Function Module for EBPP: Anlegen von Klärungsfällen zu Rechnungen









APAR_EBPP_PUT_DISPUTE is a standard apar ebpp put dispute SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for EBPP: Anlegen von Klärungsfällen zu Rechnungen 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 apar ebpp put dispute FM, simply by entering the name APAR_EBPP_PUT_DISPUTE into the relevant SAP transaction such as SE37 or SE38.

Function Group: APAR_EBPP
Program Name: SAPLAPAR_EBPP
Main Program: SAPLAPAR_EBPP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function APAR_EBPP_PUT_DISPUTE 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 'APAR_EBPP_PUT_DISPUTE'"EBPP: Anlegen von Klärungsfällen zu Rechnungen
EXPORTING
I_PARTNER = "EBPP: Partnerdaten
* I_ADDSEL = "EBPP: Zusätzliche Selektionsangaben

IMPORTING
E_RETURNCODE = "Rückgabewert, Rückgabewert nach ABAP-Anweisungen
RETURN = "Returnparameter

TABLES
* T_DISPUTES_NEW = "Biller Direct: Daten für neue Klärungsfälle
* T_NOTES = "Biller Direct: Notizen für Klärungsfälle
* T_FILECONTENT = "Biller Direct: Attachments für Klärungsfälle Binärer Inhalt
* T_INVOICES_DISPDATA = "Biller Direct: Zuordnung anzulegende Fälle / Rechnungen
* T_ITEMS = "Biller Direct: Positionsdaten
* T_ALLOCATION = "EBPP: Zuordnung Positionsdaten / Rechnungsdaten
* T_MESSAGES = "EBPP: Meldungen
.



IMPORTING Parameters details for APAR_EBPP_PUT_DISPUTE

I_PARTNER - EBPP: Partnerdaten

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

I_ADDSEL - EBPP: Zusätzliche Selektionsangaben

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

EXPORTING Parameters details for APAR_EBPP_PUT_DISPUTE

E_RETURNCODE - Rückgabewert, Rückgabewert nach ABAP-Anweisungen

Data type: SY-SUBRC
Optional: No
Call by Reference: No ( called with pass by value option)

RETURN - Returnparameter

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

TABLES Parameters details for APAR_EBPP_PUT_DISPUTE

T_DISPUTES_NEW - Biller Direct: Daten für neue Klärungsfälle

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

T_NOTES - Biller Direct: Notizen für Klärungsfälle

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

T_FILECONTENT - Biller Direct: Attachments für Klärungsfälle Binärer Inhalt

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

T_INVOICES_DISPDATA - Biller Direct: Zuordnung anzulegende Fälle / Rechnungen

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

T_ITEMS - Biller Direct: Positionsdaten

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

T_ALLOCATION - EBPP: Zuordnung Positionsdaten / Rechnungsdaten

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

T_MESSAGES - EBPP: Meldungen

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

Copy and paste ABAP code example for APAR_EBPP_PUT_DISPUTE 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_partner  TYPE EBPP_PARTNER, "   
lv_e_returncode  TYPE SY-SUBRC, "   
lt_t_disputes_new  TYPE STANDARD TABLE OF FDM_EBPP_DMDISPUTES_NEW, "   
lv_return  TYPE BAPIRET1, "   
lt_t_notes  TYPE STANDARD TABLE OF FDM_EBPP_DMNOTES, "   
lv_i_addsel  TYPE EBPP_ADDSEL, "   
lt_t_filecontent  TYPE STANDARD TABLE OF FDM_EBPP_DMFILECONTENT, "   
lt_t_invoices_dispdata  TYPE STANDARD TABLE OF FDM_EBPP_DMINVOICES_DISPDATA, "   
lt_t_items  TYPE STANDARD TABLE OF EBPP_ITEM, "   
lt_t_allocation  TYPE STANDARD TABLE OF EBPP_ALLOCATION, "   
lt_t_messages  TYPE STANDARD TABLE OF EBPP_MESSAGES. "   

  CALL FUNCTION 'APAR_EBPP_PUT_DISPUTE'  "EBPP: Anlegen von Klärungsfällen zu Rechnungen
    EXPORTING
         I_PARTNER = lv_i_partner
         I_ADDSEL = lv_i_addsel
    IMPORTING
         E_RETURNCODE = lv_e_returncode
         RETURN = lv_return
    TABLES
         T_DISPUTES_NEW = lt_t_disputes_new
         T_NOTES = lt_t_notes
         T_FILECONTENT = lt_t_filecontent
         T_INVOICES_DISPDATA = lt_t_invoices_dispdata
         T_ITEMS = lt_t_items
         T_ALLOCATION = lt_t_allocation
         T_MESSAGES = lt_t_messages
. " APAR_EBPP_PUT_DISPUTE




ABAP code using 7.40 inline data declarations to call FM APAR_EBPP_PUT_DISPUTE

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.

 
"SELECT single SUBRC FROM SY INTO @DATA(ld_e_returncode).
 
 
 
 
 
 
 
 
 
 


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!