SAP TABLEFRAME_BCOT Function Module for Extended Table Maintenance: Upper Level

Search SAP Function Modules

TABLEFRAME_BCOT is a standard tableframe bcot SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Extended Table Maintenance: Upper Level processing and below is the pattern details for this FM, 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 tableframe bcot FM, simply by entering the name TABLEFRAME_BCOT into the relevant SAP transaction such as SE37 or SE38.

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

Function TABLEFRAME_BCOT 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 'TABLEFRAME_BCOT'"Extended Table Maintenance: Upper Level
  EXPORTING
*  VIEW_ACTION = 'S' "Activity w. table: dis./chan./transp. (S/U/T)
   VIEW_NAME =  "Table Name
*  CORR_NUMBER = ' ' "Correction Number for Changes Made

TABLES
   DBA_SELLIST =  "Database Access Selection Conditions
   DPL_SELLIST =  "Display Selection Conditions
   EXCL_CUA_FUNCT =  "Table with dynam. CUA funct. to be deactivated
   X_HEADER =  "Control block table for the table
   X_NAMTAB =  "Control block table for the table fields

EXCEPTIONS
   MISSING_CORR_NUMBER = 1 

.

IMPORTING Parameters details for TABLEFRAME_BCOT

VIEW_ACTION - Activity w. table: dis./chan./transp. (S/U/T)

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

VIEW_NAME - Table Name

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

CORR_NUMBER - Correction Number for Changes Made

Data type: E070-TRKORR
Default: ' '
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for TABLEFRAME_BCOT

DBA_SELLIST - Database Access Selection Conditions

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

DPL_SELLIST - Display Selection Conditions

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

EXCL_CUA_FUNCT - Table with dynam. CUA funct. to be deactivated

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

X_HEADER - Control block table for the table

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

X_NAMTAB - Control block table for the table fields

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

EXCEPTIONS details

MISSING_CORR_NUMBER - Correction Number Missing

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

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

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