SAP BBP_CREATE_SUPP_MONI_ENTRIES Function Module for









BBP_CREATE_SUPP_MONI_ENTRIES is a standard bbp create supp moni entries SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 bbp create supp moni entries FM, simply by entering the name BBP_CREATE_SUPP_MONI_ENTRIES into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_CREATE_SUPP_MONI_ENTRIES 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 'BBP_CREATE_SUPP_MONI_ENTRIES'"
EXPORTING
IV_PARTNER = "
* IS_ADDRESS_O = "
* IV_COMMIT = 'X' "
* IV_NEW_BP = "
* IV_LOGSYS = "
* IV_EXT_ID = "
* IS_DATA_C = "
* IS_DATA_O = "
* IS_DATA_ORG_C = "
* IS_DATA_ORG_O = "
* IS_ADDRESS_C = "

TABLES
* IT_TEL_C = "
* IT_BANKS_O = "
* IT_TAXNUM_C = "
* IT_TAXNUM_O = "
* IT_TAXCLASS_C = "
* IT_TAXCLASS_O = "
* ET_RETURN = "
* IT_TEL_O = "
* IT_FAX_C = "
* IT_FAX_O = "
* IT_EMAIL_C = "
* IT_EMAIL_O = "
* IT_PURCH_DATA_C = "
* IT_PURCH_DATA_O = "
* IT_BANKS_C = "

EXCEPTIONS
ERROR_MESSAGE_PASSED = 1 NO_CHANGE_REQUIRED = 2 PARTNER_DATA_INVALID = 3 ERROR_READING_ADDRESS = 4
.



IMPORTING Parameters details for BBP_CREATE_SUPP_MONI_ENTRIES

IV_PARTNER -

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

IS_ADDRESS_O -

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

IV_COMMIT -

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_NEW_BP -

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

IV_LOGSYS -

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

IV_EXT_ID -

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

IS_DATA_C -

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

IS_DATA_O -

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

IS_DATA_ORG_C -

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

IS_DATA_ORG_O -

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

IS_ADDRESS_C -

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

TABLES Parameters details for BBP_CREATE_SUPP_MONI_ENTRIES

IT_TEL_C -

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

IT_BANKS_O -

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

IT_TAXNUM_C -

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

IT_TAXNUM_O -

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

IT_TAXCLASS_C -

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

IT_TAXCLASS_O -

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

ET_RETURN -

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

IT_TEL_O -

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

IT_FAX_C -

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

IT_FAX_O -

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

IT_EMAIL_C -

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

IT_EMAIL_O -

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

IT_PURCH_DATA_C -

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

IT_PURCH_DATA_O -

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

IT_BANKS_C -

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

EXCEPTIONS details

ERROR_MESSAGE_PASSED -

Data type:
Optional: No
Call by Reference: Yes

NO_CHANGE_REQUIRED -

Data type:
Optional: No
Call by Reference: Yes

PARTNER_DATA_INVALID -

Data type:
Optional: No
Call by Reference: Yes

ERROR_READING_ADDRESS -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BBP_CREATE_SUPP_MONI_ENTRIES 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_it_tel_c  TYPE STANDARD TABLE OF BAPIADTEL, "   
lv_iv_partner  TYPE BU_PARTNER, "   
lv_error_message_passed  TYPE BU_PARTNER, "   
lt_it_banks_o  TYPE STANDARD TABLE OF BAPIBUS1006_BANKDETAILS, "   
lv_is_address_o  TYPE BAPIBUS1006_ADDRESS, "   
lv_iv_commit  TYPE XFELD, "   'X'
lt_it_taxnum_c  TYPE STANDARD TABLE OF DFKKBPTAXNUM, "   
lt_it_taxnum_o  TYPE STANDARD TABLE OF DFKKBPTAXNUM, "   
lt_it_taxclass_c  TYPE STANDARD TABLE OF BAPIBUS1006_TAX_CLASS, "   
lt_it_taxclass_o  TYPE STANDARD TABLE OF BAPIBUS1006_TAX_CLASS, "   
lt_et_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lt_it_tel_o  TYPE STANDARD TABLE OF BAPIADTEL, "   
lv_iv_new_bp  TYPE XFELD, "   
lv_no_change_required  TYPE XFELD, "   
lt_it_fax_c  TYPE STANDARD TABLE OF BAPIADFAX, "   
lv_iv_logsys  TYPE LOGSYS, "   
lv_partner_data_invalid  TYPE LOGSYS, "   
lt_it_fax_o  TYPE STANDARD TABLE OF BAPIADFAX, "   
lv_iv_ext_id  TYPE BBPLIFNR, "   
lv_error_reading_address  TYPE BBPLIFNR, "   
lv_is_data_c  TYPE BAPIBUS1006_CENTRAL, "   
lt_it_email_c  TYPE STANDARD TABLE OF BAPIADSMTP, "   
lv_is_data_o  TYPE BAPIBUS1006_CENTRAL, "   
lt_it_email_o  TYPE STANDARD TABLE OF BAPIADSMTP, "   
lv_is_data_org_c  TYPE BAPIBUS1006_CENTRAL_ORGAN, "   
lt_it_purch_data_c  TYPE STANDARD TABLE OF BBPM_BUT_FRG0061, "   
lv_is_data_org_o  TYPE BAPIBUS1006_CENTRAL_ORGAN, "   
lt_it_purch_data_o  TYPE STANDARD TABLE OF BBPM_BUT_FRG0061, "   
lt_it_banks_c  TYPE STANDARD TABLE OF BAPIBUS1006_BANKDETAILS, "   
lv_is_address_c  TYPE BAPIBUS1006_ADDRESS. "   

  CALL FUNCTION 'BBP_CREATE_SUPP_MONI_ENTRIES'  "
    EXPORTING
         IV_PARTNER = lv_iv_partner
         IS_ADDRESS_O = lv_is_address_o
         IV_COMMIT = lv_iv_commit
         IV_NEW_BP = lv_iv_new_bp
         IV_LOGSYS = lv_iv_logsys
         IV_EXT_ID = lv_iv_ext_id
         IS_DATA_C = lv_is_data_c
         IS_DATA_O = lv_is_data_o
         IS_DATA_ORG_C = lv_is_data_org_c
         IS_DATA_ORG_O = lv_is_data_org_o
         IS_ADDRESS_C = lv_is_address_c
    TABLES
         IT_TEL_C = lt_it_tel_c
         IT_BANKS_O = lt_it_banks_o
         IT_TAXNUM_C = lt_it_taxnum_c
         IT_TAXNUM_O = lt_it_taxnum_o
         IT_TAXCLASS_C = lt_it_taxclass_c
         IT_TAXCLASS_O = lt_it_taxclass_o
         ET_RETURN = lt_et_return
         IT_TEL_O = lt_it_tel_o
         IT_FAX_C = lt_it_fax_c
         IT_FAX_O = lt_it_fax_o
         IT_EMAIL_C = lt_it_email_c
         IT_EMAIL_O = lt_it_email_o
         IT_PURCH_DATA_C = lt_it_purch_data_c
         IT_PURCH_DATA_O = lt_it_purch_data_o
         IT_BANKS_C = lt_it_banks_c
    EXCEPTIONS
        ERROR_MESSAGE_PASSED = 1
        NO_CHANGE_REQUIRED = 2
        PARTNER_DATA_INVALID = 3
        ERROR_READING_ADDRESS = 4
. " BBP_CREATE_SUPP_MONI_ENTRIES




ABAP code using 7.40 inline data declarations to call FM BBP_CREATE_SUPP_MONI_ENTRIES

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.

 
 
 
 
 
DATA(ld_iv_commit) = 'X'.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!