SAP BBP_ACC_PUT_PBO Function Module for









BBP_ACC_PUT_PBO is a standard bbp acc put pbo 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 acc put pbo FM, simply by entering the name BBP_ACC_PUT_PBO into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_ACC_PUT_PBO 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_ACC_PUT_PBO'"
EXPORTING
I_COMACC = "
I_EDIT = "
* I_NO_ADD_ACC = "
* I_CHECK = "
* IV_USER_NAME = ' ' "
* IV_BACK_TEXT = "
* IV_BACK_OKCODE = 'ACC_BACK' "
* I_NO_CHANGE_TYPE = "
* IV_TAKE_AS_DEF = "

IMPORTING
E_PROGNAME = "
E_SCREEN = "

TABLES
I_ACCOUNT = "
E_MESSAGES = "
.



IMPORTING Parameters details for BBP_ACC_PUT_PBO

I_COMACC -

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

I_EDIT -

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

I_NO_ADD_ACC -

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

I_CHECK -

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

IV_USER_NAME -

Data type: SYUNAME
Default: SPACE
Optional: Yes
Call by Reference: Yes

IV_BACK_TEXT -

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

IV_BACK_OKCODE -

Data type: FCODE
Default: 'ACC_BACK'
Optional: Yes
Call by Reference: Yes

I_NO_CHANGE_TYPE -

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

IV_TAKE_AS_DEF -

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

EXPORTING Parameters details for BBP_ACC_PUT_PBO

E_PROGNAME -

Data type: SY-REPID
Optional: No
Call by Reference: Yes

E_SCREEN -

Data type: SY-DYNNR
Optional: No
Call by Reference: Yes

TABLES Parameters details for BBP_ACC_PUT_PBO

I_ACCOUNT -

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

E_MESSAGES -

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

Copy and paste ABAP code example for BBP_ACC_PUT_PBO 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_comacc  TYPE BBP_PDS_COMACC, "   
lt_i_account  TYPE STANDARD TABLE OF BBP_PDS_ACC, "   
lv_e_progname  TYPE SY-REPID, "   
lv_i_edit  TYPE XFELD, "   
lv_e_screen  TYPE SY-DYNNR, "   
lt_e_messages  TYPE STANDARD TABLE OF BBP_PDS_MESSAGES, "   
lv_i_no_add_acc  TYPE XFELD, "   
lv_i_check  TYPE XFELD, "   
lv_iv_user_name  TYPE SYUNAME, "   SPACE
lv_iv_back_text  TYPE CHAR50, "   
lv_iv_back_okcode  TYPE FCODE, "   'ACC_BACK'
lv_i_no_change_type  TYPE XFELD, "   
lv_iv_take_as_def  TYPE XFELD. "   

  CALL FUNCTION 'BBP_ACC_PUT_PBO'  "
    EXPORTING
         I_COMACC = lv_i_comacc
         I_EDIT = lv_i_edit
         I_NO_ADD_ACC = lv_i_no_add_acc
         I_CHECK = lv_i_check
         IV_USER_NAME = lv_iv_user_name
         IV_BACK_TEXT = lv_iv_back_text
         IV_BACK_OKCODE = lv_iv_back_okcode
         I_NO_CHANGE_TYPE = lv_i_no_change_type
         IV_TAKE_AS_DEF = lv_iv_take_as_def
    IMPORTING
         E_PROGNAME = lv_e_progname
         E_SCREEN = lv_e_screen
    TABLES
         I_ACCOUNT = lt_i_account
         E_MESSAGES = lt_e_messages
. " BBP_ACC_PUT_PBO




ABAP code using 7.40 inline data declarations to call FM BBP_ACC_PUT_PBO

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 REPID FROM SY INTO @DATA(ld_e_progname).
 
 
"SELECT single DYNNR FROM SY INTO @DATA(ld_e_screen).
 
 
 
 
DATA(ld_iv_user_name) = ' '.
 
 
DATA(ld_iv_back_okcode) = 'ACC_BACK'.
 
 
 


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!