BAPI_IFLOT SAP (BAPI Structure for table IFLOT) Structure details
Description: BAPI Structure for table IFLOT
Structure field list including key, data, relationships and ABAP select examples
BAPI_IFLOT 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 "BAPI Structure for table IFLOT" 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_BAPI_IFLOT TYPE BAPI_IFLOT.
The BAPI_IFLOT table consists of various fields, each holding specific information or linking keys about BAPI Structure for table IFLOT data available in SAP. These include FUNCT_LOC (Functional Location), LANGU_ISO (2-Character SAP Language Code), STRIND (Functional location structure indicator), CATEGORY (Functional location category).. 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 BAPI_IFLOT 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 |
OPERATION | Function | MSGFN | CHAR | 3 | MSGFN | ||||
FUNCT_LOC | Functional Location | TPLNR | CHAR | 30 | Assigned to domain | TPLNR | TPLNR | IFL | IFLM |
LANGU_ISO | 2-Character SAP Language Code | LAISO | CHAR | 2 | LAISO | ||||
STRIND | Functional location structure indicator | TPLKZ | CHAR | 5 | Assigned to domain | TPLKZ | ISR | ||
CATEGORY | Functional location category | FLTYP | CHAR | 1 | Assigned to domain | FLTYP | IFT | ||
SUPFLOC | Superior functional location | TPLMA | CHAR | 30 | Assigned to domain | TPLNR | TPLNR | IFLM | |
ERDAT | Date on which the object was created | ICRDT | DATS | 8 | DATUM | ||||
ERNAM | Name of User Who Created the Object | ICRNA | CHAR | 12 | USNAM | ||||
AEDAT | Date on which the object was last changed | IUPDT | DATS | 8 | DATUM | ||||
AENAM | Name of the user who last changed the object | IUPNA | CHAR | 12 | USNAM | ||||
START_FROM | Start-up Date of the Technical Object | ILOM_DATAB | DATS | 8 | DATUM | ||||
AUTHGRP | Technical object authorization group | IAUTG | CHAR | 4 | Assigned to domain | IAUTG | |||
TRPNR | Reference functional location | TRPNR | CHAR | 30 | Assigned to domain | TRPNR | IRL | IRLM | |
PSTAE | SAP Development reserve: Format CHAR, length 4 | RESERVE_CHAR_004 | CHAR | 4 | CHAR4 | ||||
STNAM | SAP Development Reserve: Format CHAR, Length 12 | RESERVE_CHAR_012 | CHAR | 12 | CHAR12 | ||||
LVORM | SAP Development Reserve: Format CHAR, Length 1 | RESERVE_CHAR_001 | CHAR | 1 | CHAR1 | ||||
CONSTTYPE | Construction type material of the object | SUBMT | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | |
SUBMTI | Data origin for construction type field | INH_SUBMTI | CHAR | 1 | INHER | ||||
MANPARNO | Manufacturer part number | MAPAR | CHAR | 30 | MAPAR | ||||
MAPARI | SAP Development Reserve: Format CHAR, Length 1 | RESERVE_CHAR_001 | CHAR | 1 | CHAR1 | ||||
EQINSTALL | Installation of equipment allowed at the functional location | IEQUI | CHAR | 1 | X | ||||
IEQUII | Data origin for equip. inst. allowed field | INH_IEQUII | CHAR | 1 | INHER | ||||
EQSINGLE | Single equipment installation at functional location | EINZL | CHAR | 1 | XFELD | ||||
EINZLI | Data origin for authorization group field | INH_BEGRUI | CHAR | 1 | INHER | ||||
PLANPLANT | Maintenance Planning Plant | IWERK | CHAR | 4 | Assigned to domain | WERKS | IWK | ||
IWERKI | Data origin for planning plant field | INH_IWERKI | CHAR | 1 | INHER | ||||
PLANGROUP | Planner Group for Customer Service and Plant Maintenance | INGRP | CHAR | 3 | Assigned to domain | INGRP | IHG | ||
INGRPI | Data origin for maintenance planner group field | INH_INGRPI | CHAR | 1 | INHER | ||||
PM_OBJTY | Object Type of CIM Resources for Work Center | PM_OBJTY | CHAR | 2 | CR_OBJTY | ||||
WORK_CTR | Object ID of the Work Center | LGWID | NUMC | 8 | Assigned to domain | CR_OBJID | |||
LGWIDI | Data Origin for the Field 'Work Center' | INH_LGWIDI | CHAR | 1 | INHER | ||||
CATPROFILE | Catalog Profile | RBNR | CHAR | 9 | Assigned to domain | RBNR | |||
RBNR_I | Data origin for maintenance catalog field | INH_RBNR_I | CHAR | 1 | INHER | ||||
ILOAN | Location and account assignment for technical object | ILOAN | CHAR | 12 | Assigned to domain | ILOAN | |||
OBJECT_NO | Object number | J_OBJNR | CHAR | 22 | Assigned to domain | J_OBJNR | ONR | ||
POSNR | Position in superior technical object | ILOM_POSNR | CHAR | 4 | CHAR4 | ||||
ISTYP | Object category for Industry Solutions (IS) | ILOM_ISTYP | CHAR | 1 | ILOM_ISTYP | ||||
PREMS | Premise | ILOM_PREMS | CHAR | 10 | CHAR10 | ||||
EQUITYPE | Type of Technical Object | EQART | CHAR | 10 | Assigned to domain | EQART | |||
INVENTORY | Inventory number | INVNR | CHAR | 25 | INVNR_ANLA | ||||
OBJ_SIZE | Size/dimension | GROSS | CHAR | 18 | GROES | ||||
ISOCODE_UNIT | ISO code for unit of measurement | ISOCD_UNIT | CHAR | 3 | Assigned to domain | ISOCD_UNIT | |||
UNIT_OF_WT | Weight Unit | GEWEI | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
GROSS_WT | Gross Weight | BRGEW | QUAN | 13(3) | MENG13 | ||||
CURRISO | ISO currency code | ISOCD | CHAR | 3 | ISOCD | ||||
CURRVALUE | Acquisition Value | ANSWT | CURR | 13(2) | WERT | ||||
CURRENCY | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
ACQDATE | Acquisition date | ANDTI | DATS | 8 | DATUM | ||||
MANFACTURE | Manufacturer of asset | HERST | CHAR | 30 | TEXT30 | ||||
COUNTRYISO | Country ISO code | INTCA | CHAR | 2 | INTCA | F4_INTCA | |||
CONSTYEAR | Year of construction | BAUJJ | CHAR | 4 | GJAHR | CJAHR | |||
CONSTMONTH | Month of construction | BAUMM | CHAR | 2 | BAUMM | ||||
MANMODEL | Manufacturer model number | TYPBZ | CHAR | 20 | TYPBZ | ||||
MPN | Material Number Corresponding to Manufacturer Part Number | EMATN | CHAR | 18 | Assigned to domain | MATN1 | MATNR | HTN | |
MANSERNO | Manufacturer serial number | SERGE | CHAR | 30 | CHAR30 | ||||
HANDLE | SAP Development Reserve: Integration of Date Segment (Key) | ITOBTMP_TSEGGUID | CHAR | 22 | SYSUUID_22 | ||||
TSEGTP | SAP Development Reserve: Integration Date Segment (Tempate) | ITOBTMP_TSEGTEMPLA | CHAR | 10 | Assigned to domain | TMPLA | TSEGTEMPLA | ||
IFLOT_SRTYPE | Shift Report Type for Object | ILOM_SR_SRTYPE | CHAR | 10 | |||||
IFLOT_SNTYPE | Notification Type for Shift Note for Object | ILOM_SN_SNTYPE | CHAR | 2 | Assigned to domain | QMART | |||
FUNCLOC | Functional Location Label | ILOM_STRNO | CHAR | 40 | ILOM_STRNO | ||||
FUNCLOC_SUP | Functional Location Label | ILOM_STRNO | CHAR | 40 | ILOM_STRNO |
Key field | Non-key field |
How do I retrieve data from SAP structure BAPI_IFLOT using ABAP code?
As BAPI_IFLOT 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 BAPI_IFLOT as there is no data to select.How to access SAP table BAPI_IFLOT
Within an ECC or HANA version of SAP you can also view further information about BAPI_IFLOT 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