SAP CLAP_DDB_READ_BUFFER_UP Function Module for
CLAP_DDB_READ_BUFFER_UP is a standard clap ddb read buffer up 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 read buffer up FM, simply by entering the name CLAP_DDB_READ_BUFFER_UP 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_READ_BUFFER_UP 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_READ_BUFFER_UP'".
EXPORTING
* OBJECT = "Key of Object to be Classified
CLASSTYPE = "Class Type
PTABLE = "Name of Database Table for Object
* I_CLASS = "Class Number
* NO_DELETIONS = 'X' "
TABLES
T_ALLOCATIONS = "Update interface
EXCEPTIONS
NO_ALLOCATIONS_IN_BUFFER = 1 CLASS_NOT_IN_BUFFER = 2 ALLOCATION_NOT_IN_BUFFER = 3 MISSING_PARAMETER = 4
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_READ_BUFFER_UP
OBJECT - Key of Object to be Classified
Data type: KSSK-OBJEKOptional: Yes
Call by Reference: No ( called with pass by value option)
CLASSTYPE - Class Type
Data type: KSSK-KLARTOptional: No
Call by Reference: No ( called with pass by value option)
PTABLE - Name of Database Table for Object
Data type: TCLAO-OBTABOptional: No
Call by Reference: No ( called with pass by value option)
I_CLASS - Class Number
Data type: KLASSE_DOptional: Yes
Call by Reference: No ( called with pass by value option)
NO_DELETIONS -
Data type: FLAGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CLAP_DDB_READ_BUFFER_UP
T_ALLOCATIONS - Update interface
Data type: RMCLKSSKOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_ALLOCATIONS_IN_BUFFER -
Data type:Optional: No
Call by Reference: Yes
CLASS_NOT_IN_BUFFER -
Data type:Optional: No
Call by Reference: Yes
ALLOCATION_NOT_IN_BUFFER -
Data type:Optional: No
Call by Reference: Yes
MISSING_PARAMETER -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CLAP_DDB_READ_BUFFER_UP 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_object | TYPE KSSK-OBJEK, " | |||
| lt_t_allocations | TYPE STANDARD TABLE OF RMCLKSSK, " | |||
| lv_no_allocations_in_buffer | TYPE RMCLKSSK, " | |||
| lv_classtype | TYPE KSSK-KLART, " | |||
| lv_class_not_in_buffer | TYPE KSSK, " | |||
| lv_ptable | TYPE TCLAO-OBTAB, " | |||
| lv_allocation_not_in_buffer | TYPE TCLAO, " | |||
| lv_i_class | TYPE KLASSE_D, " | |||
| lv_missing_parameter | TYPE KLASSE_D, " | |||
| lv_no_deletions | TYPE FLAG. " 'X' |
|   CALL FUNCTION 'CLAP_DDB_READ_BUFFER_UP' " |
| EXPORTING | ||
| OBJECT | = lv_object | |
| CLASSTYPE | = lv_classtype | |
| PTABLE | = lv_ptable | |
| I_CLASS | = lv_i_class | |
| NO_DELETIONS | = lv_no_deletions | |
| TABLES | ||
| T_ALLOCATIONS | = lt_t_allocations | |
| EXCEPTIONS | ||
| NO_ALLOCATIONS_IN_BUFFER = 1 | ||
| CLASS_NOT_IN_BUFFER = 2 | ||
| ALLOCATION_NOT_IN_BUFFER = 3 | ||
| MISSING_PARAMETER = 4 | ||
| . " CLAP_DDB_READ_BUFFER_UP | ||
ABAP code using 7.40 inline data declarations to call FM CLAP_DDB_READ_BUFFER_UP
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 OBJEK FROM KSSK INTO @DATA(ld_object). | ||||
| "SELECT single KLART FROM KSSK INTO @DATA(ld_classtype). | ||||
| "SELECT single OBTAB FROM TCLAO INTO @DATA(ld_ptable). | ||||
| DATA(ld_no_deletions) | = 'X'. | |||
Search for further information about these or an SAP related objects