SAP BBP_CUF_DETERMINE_SOLUTION_KEY Function Module for









BBP_CUF_DETERMINE_SOLUTION_KEY is a standard bbp cuf determine solution key 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 cuf determine solution key FM, simply by entering the name BBP_CUF_DETERMINE_SOLUTION_KEY into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_CUF_DETERMINE_SOLUTION_KEY 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_CUF_DETERMINE_SOLUTION_KEY'"
  EXPORTING
*  IS_HEADER =  "

 IMPORTING
   ES_SOLUTION_KEY =  "

TABLES
*  I_ITEM =  "
*  I_PRIDOC =  "
*  I_HCF =  "
*  I_ICF =  "
*  I_TOL =  "
*  I_ACCOUNT =  "
*  I_PARTNER =  "
*  I_CONFIRM =  "
*  I_LONGTEXT =  "
*  I_LIMIT =  "
*  I_ORGDATA =  "
*  I_FREIGHT =  "
*  I_TAX =  "
.



IMPORTING Parameters details for BBP_CUF_DETERMINE_SOLUTION_KEY

IS_HEADER -

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

EXPORTING Parameters details for BBP_CUF_DETERMINE_SOLUTION_KEY

ES_SOLUTION_KEY -

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

TABLES Parameters details for BBP_CUF_DETERMINE_SOLUTION_KEY

I_ITEM -

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

I_PRIDOC -

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

I_HCF -

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

I_ICF -

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

I_TOL -

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

I_ACCOUNT -

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

I_PARTNER -

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

I_CONFIRM -

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

I_LONGTEXT -

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

I_LIMIT -

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

I_ORGDATA -

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

I_FREIGHT -

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

I_TAX -

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

Copy and paste ABAP code example for BBP_CUF_DETERMINE_SOLUTION_KEY 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_i_item  TYPE STANDARD TABLE OF TABLE, "   
lv_is_header  TYPE ANY, "   
lv_es_solution_key  TYPE BBPS_PD_SOLUTION_KEY, "   
lt_i_pridoc  TYPE STANDARD TABLE OF BBP_PDS_PRC, "   
lt_i_hcf  TYPE STANDARD TABLE OF BBP_PDS_HCF, "   
lt_i_icf  TYPE STANDARD TABLE OF BBP_PDS_ICF, "   
lt_i_tol  TYPE STANDARD TABLE OF BBP_PDS_TOL, "   
lt_i_account  TYPE STANDARD TABLE OF BBP_PDS_ACC, "   
lt_i_partner  TYPE STANDARD TABLE OF BBP_PDS_PARTNER, "   
lt_i_confirm  TYPE STANDARD TABLE OF BBP_PDS_CON, "   
lt_i_longtext  TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT, "   
lt_i_limit  TYPE STANDARD TABLE OF BBP_PDS_LIMIT, "   
lt_i_orgdata  TYPE STANDARD TABLE OF BBP_PDS_ORG, "   
lt_i_freight  TYPE STANDARD TABLE OF BBP_PDS_FREIGHT, "   
lt_i_tax  TYPE STANDARD TABLE OF BBP_PDS_TAX. "   

  CALL FUNCTION 'BBP_CUF_DETERMINE_SOLUTION_KEY'  "
    EXPORTING
         IS_HEADER = lv_is_header
    IMPORTING
         ES_SOLUTION_KEY = lv_es_solution_key
    TABLES
         I_ITEM = lt_i_item
         I_PRIDOC = lt_i_pridoc
         I_HCF = lt_i_hcf
         I_ICF = lt_i_icf
         I_TOL = lt_i_tol
         I_ACCOUNT = lt_i_account
         I_PARTNER = lt_i_partner
         I_CONFIRM = lt_i_confirm
         I_LONGTEXT = lt_i_longtext
         I_LIMIT = lt_i_limit
         I_ORGDATA = lt_i_orgdata
         I_FREIGHT = lt_i_freight
         I_TAX = lt_i_tax
. " BBP_CUF_DETERMINE_SOLUTION_KEY




ABAP code using 7.40 inline data declarations to call FM BBP_CUF_DETERMINE_SOLUTION_KEY

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



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!