SAP BBP_CUF_GET_DATA_APPL Function Module for









BBP_CUF_GET_DATA_APPL is a standard bbp cuf get data appl 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 get data appl FM, simply by entering the name BBP_CUF_GET_DATA_APPL 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_GET_DATA_APPL 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_GET_DATA_APPL'"
EXPORTING
* IV_DOC_TYPE = "

IMPORTING
EV_OKCODE = "

CHANGING
* ES_HEADER = "
* ES_ITEM = "
* ES_ACC = "
* ES_HISTORY = "
* ES_BUT000 = "
* ES_PARTNER = "

TABLES
* IT_DOC_TYPES = "
* GT_MESSAGES = "
* ET_SEARCH_HEADER = "
* ET_SEARCH_ITEM = "
* CT_CUF_TABLE = "
* ET_HCF = "
* ET_ICF = "

EXCEPTIONS
PARAMETER_ERROR = 1
.



IMPORTING Parameters details for BBP_CUF_GET_DATA_APPL

IV_DOC_TYPE -

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

EXPORTING Parameters details for BBP_CUF_GET_DATA_APPL

EV_OKCODE -

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

CHANGING Parameters details for BBP_CUF_GET_DATA_APPL

ES_HEADER -

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

ES_ITEM -

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

ES_ACC -

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

ES_HISTORY -

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

ES_BUT000 -

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

ES_PARTNER -

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

TABLES Parameters details for BBP_CUF_GET_DATA_APPL

IT_DOC_TYPES -

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

GT_MESSAGES -

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

ET_SEARCH_HEADER -

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

ET_SEARCH_ITEM -

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

CT_CUF_TABLE -

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

ET_HCF -

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

ET_ICF -

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

EXCEPTIONS details

PARAMETER_ERROR -

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

Copy and paste ABAP code example for BBP_CUF_GET_DATA_APPL 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_HEADER, "   
lv_ev_okcode  TYPE SY-UCOMM, "   
lv_iv_doc_type  TYPE CRMD_ORDERADM_H-OBJECT_TYPE, "   
lt_it_doc_types  TYPE STANDARD TABLE OF BBP_PDS_OBJECT_TYPE, "   
lv_parameter_error  TYPE BBP_PDS_OBJECT_TYPE, "   
lv_es_item  TYPE BBP_PDS_ITEM, "   
lt_gt_messages  TYPE STANDARD TABLE OF BBP_PDS_MESSAGES, "   
lv_es_acc  TYPE BBP_PDS_ACC, "   
lt_et_search_header  TYPE STANDARD TABLE OF BBP_CUF_SEARCH_HEADER, "   
lv_es_history  TYPE BBP_PDS_HISTORY, "   
lt_et_search_item  TYPE STANDARD TABLE OF BBP_CUF_SEARCH_ITEM, "   
lv_es_but000  TYPE BUT000, "   
lt_ct_cuf_table  TYPE STANDARD TABLE OF TABLE, "   
lt_et_hcf  TYPE STANDARD TABLE OF TABLE, "   
lv_es_partner  TYPE BBP_PDS_PARTNER, "   
lt_et_icf  TYPE STANDARD TABLE OF TABLE. "   

  CALL FUNCTION 'BBP_CUF_GET_DATA_APPL'  "
    EXPORTING
         IV_DOC_TYPE = lv_iv_doc_type
    IMPORTING
         EV_OKCODE = lv_ev_okcode
    CHANGING
         ES_HEADER = lv_es_header
         ES_ITEM = lv_es_item
         ES_ACC = lv_es_acc
         ES_HISTORY = lv_es_history
         ES_BUT000 = lv_es_but000
         ES_PARTNER = lv_es_partner
    TABLES
         IT_DOC_TYPES = lt_it_doc_types
         GT_MESSAGES = lt_gt_messages
         ET_SEARCH_HEADER = lt_et_search_header
         ET_SEARCH_ITEM = lt_et_search_item
         CT_CUF_TABLE = lt_ct_cuf_table
         ET_HCF = lt_et_hcf
         ET_ICF = lt_et_icf
    EXCEPTIONS
        PARAMETER_ERROR = 1
. " BBP_CUF_GET_DATA_APPL




ABAP code using 7.40 inline data declarations to call FM BBP_CUF_GET_DATA_APPL

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 UCOMM FROM SY INTO @DATA(ld_ev_okcode).
 
"SELECT single OBJECT_TYPE FROM CRMD_ORDERADM_H INTO @DATA(ld_iv_doc_type).
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!