SAP BBP_CUF_EXIST Function Module for

Search SAP Function Modules

BBP_CUF_EXIST is a standard bbp cuf exist 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 exist FM, simply by entering the name BBP_CUF_EXIST 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_EXIST 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_EXIST'"
  EXPORTING
*  IS_HEADER =  "
*  IS_ITEM =  "
*  IS_ACC =  "
*  IV_DOC_TYPE =  "
*  IV_DYNATTR =  "
*  IS_HISTORY =  "
*  IS_BUT000 =  "
*  IS_PARTNER =  "

 IMPORTING
   EV_CUF_EXIST =  "

TABLES
*  ET_MESSAGES =  "
*  ET_CUF_FIELDS =  "

EXCEPTIONS
   PARAMETER_ERROR = 1    UNKNOWN_DOCUMENT = 2 

.

IMPORTING Parameters details for BBP_CUF_EXIST

IS_HEADER -

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

IS_ITEM -

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

IS_ACC -

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

IV_DOC_TYPE -

Data type: CRMD_ORDERADM_H-OBJECT_TYPE
Optional: Yes
Call by Reference: Yes

IV_DYNATTR -

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

IS_HISTORY -

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

IS_BUT000 -

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

IS_PARTNER -

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

EXPORTING Parameters details for BBP_CUF_EXIST

EV_CUF_EXIST -

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

TABLES Parameters details for BBP_CUF_EXIST

ET_MESSAGES -

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

ET_CUF_FIELDS -

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

EXCEPTIONS details

PARAMETER_ERROR -

Data type:
Optional: No
Call by Reference: Yes

UNKNOWN_DOCUMENT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BBP_CUF_EXIST 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.

ABAP code using 7.40 inline data declarations to call FM BBP_CUF_EXIST

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