SAP Function Modules
BBP_CUF_GET_SOLUTION_KEY SAP Function module
BBP_CUF_GET_SOLUTION_KEY is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name BBP_CUF_GET_SOLUTION_KEY into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
BBP_PDH_CUF
Released Date:
Not Released
Processing type: Normal fucntion module
Pattern for FM BBP_CUF_GET_SOLUTION_KEY - BBP CUF GET SOLUTION KEY
CALL FUNCTION 'BBP_CUF_GET_SOLUTION_KEY' "
EXPORTING
* iv_doc_guid = " bbp_pds_header-guid
* iv_user_id = " baluser
iv_doc_type = " crmd_orderadm_h-object_type
* iv_sub_type = " bbp_pds_header-subtype
* is_header = " bbp_pds_header
* iv_param_per_guid = 'X' " xfeld
IMPORTING
es_solution_key = " bbps_pd_solution_key
TABLES
* it_partner = " bbp_pds_partner
* i_item = " bbp_pds_item
* i_account = " bbp_pds_acc
* i_orgdata = " bbp_pds_org
* i_longtext = " bbp_pds_longtext
* i_freight = " bbp_pds_freight
* i_tax = " bbp_pds_tax
et_filter = " bbps_cuf_filter
* et_return = " bapiret2
* it_partner_on_header = " bbp_pds_partner
. " BBP_CUF_GET_SOLUTION_KEY
ABAP code example for Function Module BBP_CUF_GET_SOLUTION_KEY
The ABAP code below is a full code listing to execute function module BBP_CUF_GET_SOLUTION_KEY including all data declarations. The code uses 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 original method of declaring data variables up front. 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).
| ld_es_solution_key | TYPE BBPS_PD_SOLUTION_KEY , |
| it_it_partner | TYPE STANDARD TABLE OF BBP_PDS_PARTNER,"TABLES PARAM |
| wa_it_partner | LIKE LINE OF it_it_partner , |
| it_i_item | TYPE STANDARD TABLE OF BBP_PDS_ITEM,"TABLES PARAM |
| wa_i_item | LIKE LINE OF it_i_item , |
| it_i_account | TYPE STANDARD TABLE OF BBP_PDS_ACC,"TABLES PARAM |
| wa_i_account | LIKE LINE OF it_i_account , |
| it_i_orgdata | TYPE STANDARD TABLE OF BBP_PDS_ORG,"TABLES PARAM |
| wa_i_orgdata | LIKE LINE OF it_i_orgdata , |
| it_i_longtext | TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT,"TABLES PARAM |
| wa_i_longtext | LIKE LINE OF it_i_longtext , |
| it_i_freight | TYPE STANDARD TABLE OF BBP_PDS_FREIGHT,"TABLES PARAM |
| wa_i_freight | LIKE LINE OF it_i_freight , |
| it_i_tax | TYPE STANDARD TABLE OF BBP_PDS_TAX,"TABLES PARAM |
| wa_i_tax | LIKE LINE OF it_i_tax , |
| it_et_filter | TYPE STANDARD TABLE OF BBPS_CUF_FILTER,"TABLES PARAM |
| wa_et_filter | LIKE LINE OF it_et_filter , |
| it_et_return | TYPE STANDARD TABLE OF BAPIRET2,"TABLES PARAM |
| wa_et_return | LIKE LINE OF it_et_return , |
| it_it_partner_on_header | TYPE STANDARD TABLE OF BBP_PDS_PARTNER,"TABLES PARAM |
| wa_it_partner_on_header | LIKE LINE OF it_it_partner_on_header . |
DATA(ld_iv_doc_guid) = Check type of data required
DATA(ld_iv_user_id) = 'Check type of data required'.
SELECT single OBJECT_TYPE
FROM CRMD_ORDERADM_H
INTO @DATA(ld_iv_doc_type).
DATA(ld_iv_sub_type) = some text here
DATA(ld_is_header) = 'Check type of data required'.
DATA(ld_iv_param_per_guid) = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_it_partner to it_it_partner.
"populate fields of struture and append to itab
append wa_i_item to it_i_item.
"populate fields of struture and append to itab
append wa_i_account to it_i_account.
"populate fields of struture and append to itab
append wa_i_orgdata to it_i_orgdata.
"populate fields of struture and append to itab
append wa_i_longtext to it_i_longtext.
"populate fields of struture and append to itab
append wa_i_freight to it_i_freight.
"populate fields of struture and append to itab
append wa_i_tax to it_i_tax.
"populate fields of struture and append to itab
append wa_et_filter to it_et_filter.
"populate fields of struture and append to itab
append wa_et_return to it_et_return.
"populate fields of struture and append to itab
append wa_it_partner_on_header to it_it_partner_on_header. . CALL FUNCTION 'BBP_CUF_GET_SOLUTION_KEY' EXPORTING * iv_doc_guid = ld_iv_doc_guid * iv_user_id = ld_iv_user_id iv_doc_type = ld_iv_doc_type * iv_sub_type = ld_iv_sub_type * is_header = ld_is_header * iv_param_per_guid = ld_iv_param_per_guid IMPORTING es_solution_key = ld_es_solution_key TABLES * it_partner = it_it_partner * i_item = it_i_item * i_account = it_i_account * i_orgdata = it_i_orgdata * i_longtext = it_i_longtext * i_freight = it_i_freight * i_tax = it_i_tax et_filter = it_et_filter * et_return = it_et_return * it_partner_on_header = it_it_partner_on_header . " BBP_CUF_GET_SOLUTION_KEY
IF SY-SUBRC EQ 0. "All OK ENDIF.
ABAP code to compare 7.40 inline data declaration with original syntax
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_es_solution_key | TYPE BBPS_PD_SOLUTION_KEY , |
| ld_iv_doc_guid | TYPE BBP_PDS_HEADER-GUID , |
| it_it_partner | TYPE STANDARD TABLE OF BBP_PDS_PARTNER , |
| wa_it_partner | LIKE LINE OF it_it_partner, |
| ld_iv_user_id | TYPE BALUSER , |
| it_i_item | TYPE STANDARD TABLE OF BBP_PDS_ITEM , |
| wa_i_item | LIKE LINE OF it_i_item, |
| ld_iv_doc_type | TYPE CRMD_ORDERADM_H-OBJECT_TYPE , |
| it_i_account | TYPE STANDARD TABLE OF BBP_PDS_ACC , |
| wa_i_account | LIKE LINE OF it_i_account, |
| ld_iv_sub_type | TYPE BBP_PDS_HEADER-SUBTYPE , |
| it_i_orgdata | TYPE STANDARD TABLE OF BBP_PDS_ORG , |
| wa_i_orgdata | LIKE LINE OF it_i_orgdata, |
| ld_is_header | TYPE BBP_PDS_HEADER , |
| it_i_longtext | TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT , |
| wa_i_longtext | LIKE LINE OF it_i_longtext, |
| ld_iv_param_per_guid | TYPE XFELD , |
| it_i_freight | TYPE STANDARD TABLE OF BBP_PDS_FREIGHT , |
| wa_i_freight | LIKE LINE OF it_i_freight, |
| it_i_tax | TYPE STANDARD TABLE OF BBP_PDS_TAX , |
| wa_i_tax | LIKE LINE OF it_i_tax, |
| it_et_filter | TYPE STANDARD TABLE OF BBPS_CUF_FILTER , |
| wa_et_filter | LIKE LINE OF it_et_filter, |
| it_et_return | TYPE STANDARD TABLE OF BAPIRET2 , |
| wa_et_return | LIKE LINE OF it_et_return, |
| it_it_partner_on_header | TYPE STANDARD TABLE OF BBP_PDS_PARTNER , |
| wa_it_partner_on_header | LIKE LINE OF it_it_partner_on_header. |
ld_iv_doc_guid = Check type of data required
"populate fields of struture and append to itab
append wa_it_partner to it_it_partner.
ld_iv_user_id = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_i_item to it_i_item.
SELECT single OBJECT_TYPE
FROM CRMD_ORDERADM_H
INTO ld_iv_doc_type.
"populate fields of struture and append to itab
append wa_i_account to it_i_account.
ld_iv_sub_type = some text here
"populate fields of struture and append to itab
append wa_i_orgdata to it_i_orgdata.
ld_is_header = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_i_longtext to it_i_longtext.
ld_iv_param_per_guid = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_i_freight to it_i_freight.
"populate fields of struture and append to itab
append wa_i_tax to it_i_tax.
"populate fields of struture and append to itab
append wa_et_filter to it_et_filter.
"populate fields of struture and append to itab
append wa_et_return to it_et_return.
"populate fields of struture and append to itab
append wa_it_partner_on_header to it_it_partner_on_header.
Contribute (Add Comments)
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name BBP_CUF_GET_SOLUTION_KEY or its description.