SAP CLAP_DDB_GET_BUFFER_PARAMS Function Module for

Search SAP Function Modules

CLAP_DDB_GET_BUFFER_PARAMS is a standard clap ddb get buffer params 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 clap ddb get buffer params FM, simply by entering the name CLAP_DDB_GET_BUFFER_PARAMS into the relevant SAP transaction such as SE37 or SE38.

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

Function CLAP_DDB_GET_BUFFER_PARAMS 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 'CLAP_DDB_GET_BUFFER_PARAMS'"
  EXPORTING
*  OBJECT =  "
*  CLASSTYPE =  "
*  OBTAB =  "
*  OBJ_EQ_CLASS = ' ' "

 IMPORTING
   E_OBJ_IN_BUFFER =  "
   E_CHANGE_OBJ =  "
   E_CHANGE_ANY =  "
   E_CHANGENO_USED =  "
   E_DATE_USED =  "

TABLES
*  E_KSSK_TAB =  "
*  E_AUSP_TAB =  "
*  E_DELCL_TAB =  "
*  E_DELOB_TAB =  "

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLCLFM_001 Influences Class and Value Assignment
EXIT_SAPLCLFM_002 Customer Exit for Changing Classification Data Before Saving
EXIT_SAPLCLFM_003 Customer Exit After Check on Assigned Characteristic Values

IMPORTING Parameters details for CLAP_DDB_GET_BUFFER_PARAMS

OBJECT -

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

CLASSTYPE -

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

OBTAB -

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

OBJ_EQ_CLASS -

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

EXPORTING Parameters details for CLAP_DDB_GET_BUFFER_PARAMS

E_OBJ_IN_BUFFER -

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

E_CHANGE_OBJ -

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

E_CHANGE_ANY -

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

E_CHANGENO_USED -

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

E_DATE_USED -

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

TABLES Parameters details for CLAP_DDB_GET_BUFFER_PARAMS

E_KSSK_TAB -

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

E_AUSP_TAB -

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

E_DELCL_TAB -

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

E_DELOB_TAB -

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

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

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