SAP BBP_CF_ASSIGNMENT_BACKEND Function Module for









BBP_CF_ASSIGNMENT_BACKEND is a standard bbp cf assignment backend 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 cf assignment backend FM, simply by entering the name BBP_CF_ASSIGNMENT_BACKEND into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_CF_ASSIGNMENT_BACKEND 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_CF_ASSIGNMENT_BACKEND'"
  EXPORTING
   IV_SUBTYPE =  "
*  IV_BYPASS_BUFFER = ' ' "

 IMPORTING
   ES_HEADER =  "

TABLES
   IT_SELECTION =  "
*  ET_ITEM =  "
*  ET_ACCOUNT =  "
*  ET_PARTNER =  "
*  ET_LIMIT =  "
*  ET_ORGDATA =  "
*  ET_TAX =  "
*  ET_ACTUAL_VALUES =  "
*  ET_MESSAGES =  "
.



IMPORTING Parameters details for BBP_CF_ASSIGNMENT_BACKEND

IV_SUBTYPE -

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

IV_BYPASS_BUFFER -

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

EXPORTING Parameters details for BBP_CF_ASSIGNMENT_BACKEND

ES_HEADER -

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

TABLES Parameters details for BBP_CF_ASSIGNMENT_BACKEND

IT_SELECTION -

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

ET_ITEM -

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

ET_ACCOUNT -

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

ET_PARTNER -

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

ET_LIMIT -

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

ET_ORGDATA -

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

ET_TAX -

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

ET_ACTUAL_VALUES -

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

ET_MESSAGES -

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

Copy and paste ABAP code example for BBP_CF_ASSIGNMENT_BACKEND 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_es_header  TYPE BBP_PDS_CONF_HEADER_D, "   
lv_iv_subtype  TYPE BBP_PDS_HEADER-SUBTYPE, "   
lt_it_selection  TYPE STANDARD TABLE OF BBPS_OBJECT_KEY, "   
lt_et_item  TYPE STANDARD TABLE OF BBP_PDS_CONF_ITEM_D, "   
lv_iv_bypass_buffer  TYPE XFELD, "   ' '
lt_et_account  TYPE STANDARD TABLE OF BBP_PDS_ACC, "   
lt_et_partner  TYPE STANDARD TABLE OF BBP_PDS_PARTNER, "   
lt_et_limit  TYPE STANDARD TABLE OF BBP_PDS_LIMIT, "   
lt_et_orgdata  TYPE STANDARD TABLE OF BBP_PDS_ORG, "   
lt_et_tax  TYPE STANDARD TABLE OF BBP_PDS_TAX, "   
lt_et_actual_values  TYPE STANDARD TABLE OF BBP_PDS_ACTVAL, "   
lt_et_messages  TYPE STANDARD TABLE OF BBP_PDS_MESSAGES. "   

  CALL FUNCTION 'BBP_CF_ASSIGNMENT_BACKEND'  "
    EXPORTING
         IV_SUBTYPE = lv_iv_subtype
         IV_BYPASS_BUFFER = lv_iv_bypass_buffer
    IMPORTING
         ES_HEADER = lv_es_header
    TABLES
         IT_SELECTION = lt_it_selection
         ET_ITEM = lt_et_item
         ET_ACCOUNT = lt_et_account
         ET_PARTNER = lt_et_partner
         ET_LIMIT = lt_et_limit
         ET_ORGDATA = lt_et_orgdata
         ET_TAX = lt_et_tax
         ET_ACTUAL_VALUES = lt_et_actual_values
         ET_MESSAGES = lt_et_messages
. " BBP_CF_ASSIGNMENT_BACKEND




ABAP code using 7.40 inline data declarations to call FM BBP_CF_ASSIGNMENT_BACKEND

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 SUBTYPE FROM BBP_PDS_HEADER INTO @DATA(ld_iv_subtype).
 
 
 
DATA(ld_iv_bypass_buffer) = ' '.
 
 
 
 
 
 
 
 


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!