SAP CLAP_DDB_ALLOCATION_FR_BUFFER Function Module for

Search SAP Function Modules

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

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

Function CLAP_DDB_ALLOCATION_FR_BUFFER 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_ALLOCATION_FR_BUFFER'"
  EXPORTING
*  OBJECT =  "Object key
   CLASSTYPE =  "Class type
   PTABLE =  "Physical classification table
*  OBJECT_EQ_CLASS = ' ' "Class or object
*  I_CLASS =  "Class Number

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_ALLOCATION_FR_BUFFER

OBJECT - Object key

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

CLASSTYPE - Class type

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

PTABLE - Physical classification table

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

OBJECT_EQ_CLASS - Class or object

Data type: RMCLF-KREUZ
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_CLASS - Class Number

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

TABLES Parameters details for CLAP_DDB_ALLOCATION_FR_BUFFER

T_ALLOCATIONS - Update interface

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

EXCEPTIONS details

NO_ALLOCATIONS_IN_BUFFER - 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_ALLOCATION_FR_BUFFER 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_ALLOCATION_FR_BUFFER

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