JBIDBLE SAP (Control Fields for DB Access) Structure details

Search SAP tables

Structure field list including key, data, relationships and ABAP select examples

JBIDBLE is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Control Fields for DB Access" Information within sap ABAP programs.

This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.

i.e. DATA: wa_JBIDBLE TYPE JBIDBLE.

The JBIDBLE table consists of various fields, each holding specific information or linking keys about Control Fields for DB Access data available in SAP. These include SKOKO (Control Field for DB Accesses), SKOPO (Control Field for DB Accesses), SKKOW (Control Field for DB Accesses), SKUMS (Control Field for DB Accesses).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .

Delivery Class:
Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Not classified

SAP JBIDBLE structure fields - Full list of fields found in SAP data dictionary

Key field

Non-key field

How do I retrieve data from SAP structure JBIDBLE using ABAP code?

As JBIDBLE is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on JBIDBLE as there is no data to select.

How to access SAP table JBIDBLE

Within an ECC or HANA version of SAP you can also view further information about JBIDBLE and the data within it using relevant transactions such as

SE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).

Search for further information about these or an SAP related objects