IBIBCUST SAP (IB: Installed base Customizing settings) Structure details
Description: IB: Installed base Customizing settings
Structure field list including key, data, relationships and ABAP select examples
IBIBCUST 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 "IB: Installed base Customizing settings" 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_IBIBCUST TYPE IBIBCUST.
The IBIBCUST table consists of various fields, each holding specific information or linking keys about IB: Installed base Customizing settings data available in SAP. These include MANDT (Client), IBTYP (IB: Installed Base Category), STSMA (Status Profile), COMPIND (IB: Component Store Indicator (Not Currently Used)).. 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: Cannot Be Enhanced
SAP IBIBCUST structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| IBTYP | IB: Installed Base Category | IB_IBTYP | CHAR | 2 | Assigned to domain | IB_IBTYP | H_IB_IBTYP | ||
| STSMA | Status Profile | J_STSMA | CHAR | 8 | Assigned to domain | J_STSMA | |||
| COMPIND | IB: Component Store Indicator (Not Currently Used) | IB_COMPIND | CHAR | 1 | XFELD | ||||
| CONFIND | IB: Installed Base Used for Variant Configuration | IB_CONFIND | CHAR | 1 | XFELD | ||||
| FILID | IB: Identification for a Group of Physical Files | IB_FILID | CHAR | 2 | T371B | CHAR2 | |||
| VALTYP | IB: Validity type for the installed base | IB_VALTYP | NUMC | 1 | IB_VALTYP | ||||
| INTST | IB: Internal Status of the IBase | IB_INTSTATE | NUMC | 1 | IB_INTSTATE | ||||
| STTYP | IBase: Status Type | IB_STTYP | CHAR | 2 | T371ST | IB_STTYP | |||
| IBASEMAIN | IB: Installed Base Maintenance | IB_IBASE_MAINTENANCE | CHAR | 1 | IB_IBASE_MAINTENANCE | ||||
| CHGKZ | IBase: Flag Indicates Whether Chang Docs Active f.IBase Cat. | IB_CHGKZ | CHAR | 1 | XFELD | ||||
| CASEKZ | IBase: Flag for Usage of IBase in Case Management | IB_CASEKZ | CHAR | 1 | XFELD | ||||
| LANGU | Language Key | SPRAS | LANG | 1 | T002 | ISOLA | SPRAS | SPR | H_T002 |
| DESCR | IB: Description of installed base type | IB_IBTYPT | CHAR | 30 | TEXT30 |
| Key field | Non-key field |
How do I retrieve data from SAP structure IBIBCUST using ABAP code?
As IBIBCUST 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 IBIBCUST as there is no data to select.How to access SAP table IBIBCUST
Within an ECC or HANA version of SAP you can also view further information about IBIBCUST and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects