SAP EBPP_BD_MAP_TO_INVOICE Function Module for Map to the invoice

Search SAP Function Modules

EBPP_BD_MAP_TO_INVOICE is a standard ebpp bd map to invoice SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Map to the invoice 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 ebpp bd map to invoice FM, simply by entering the name EBPP_BD_MAP_TO_INVOICE into the relevant SAP transaction such as SE37 or SE38.

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

Function EBPP_BD_MAP_TO_INVOICE 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 'EBPP_BD_MAP_TO_INVOICE'"Map to the invoice
  EXPORTING
   I_CUST_PARAM =  "General parameter for customer related search
   I_INVOICE_PARAM =  "Invoice parameter
   I_DOCTYPE =  "Single-Character Flag
*  I_AUTO_DOC =  "Single-Character Flag
*  I_PAYMT_ID =  "Character field length 24
*  I_ODATA_PARAM =  "ODATA parameter

 IMPORTING
   E_TOTAL_NUM =  "Natural number
   E_RETURN =  "ABAP System Field: Return Code of ABAP Statements
   E_DEBUG_INFO =  "

TABLES
   T_ITEMS =  "Table of customer item
*  T_MESSAGES =  "Biller Direct: Messages

.

IMPORTING Parameters details for EBPP_BD_MAP_TO_INVOICE

I_CUST_PARAM - General parameter for customer related search

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

I_INVOICE_PARAM - Invoice parameter

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

I_DOCTYPE - Single-Character Flag

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

I_AUTO_DOC - Single-Character Flag

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

I_PAYMT_ID - Character field length 24

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

I_ODATA_PARAM - ODATA parameter

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

EXPORTING Parameters details for EBPP_BD_MAP_TO_INVOICE

E_TOTAL_NUM - Natural number

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

E_RETURN - ABAP System Field: Return Code of ABAP Statements

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

E_DEBUG_INFO -

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

TABLES Parameters details for EBPP_BD_MAP_TO_INVOICE

T_ITEMS - Table of customer item

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

T_MESSAGES - Biller Direct: Messages

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

Copy and paste ABAP code example for EBPP_BD_MAP_TO_INVOICE 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.

ABAP code using 7.40 inline data declarations to call FM EBPP_BD_MAP_TO_INVOICE

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