MIPACKAGE_HEAD_SEARCH SAP (Package generation header with device name field) Structure details
Description: Package generation header with device name field
Related tables to MIPACKAGE_HEAD_SEARCH
Access table MIPACKAGE_HEAD_SEARCH
Structure field list including key, data, relationships and ABAP select examples
MIPACKAGE_HEAD_SEARCH 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 "Package generation header with device name field" 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_MIPACKAGE_HEAD_SEARCH TYPE MIPACKAGE_HEAD_SEARCH.
The MIPACKAGE_HEAD_SEARCH table consists of various fields, each holding specific information or linking keys about Package generation header with device name field data available in SAP. These include PACKAGENAME (Name of an package), PACKAGETYPE (Type of template property), DEVICEID (Unique ID of Synchronization Container), MIUSER (User Name).. 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: Can Be Enhanced (Deep)
SAP MIPACKAGE_HEAD_SEARCH 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 | Assigned to domain | MANDT | |||
| PACKAGENAME | Name of an package | MI_PACKAGE_NAME | CHAR | 70 | |||||
| PACKAGETYPE | Type of template property | MI_PACKAGE_TYPE | CHAR | 1 | MI_PACKAGE_TYPE | ||||
| DEVICEID | Unique ID of Synchronization Container | MECONTGUID | CHAR | 36 | MEGUID | ||||
| MIUSER | User Name | UNAME | CHAR | 12 | UNAME | ||||
| MIGROUP | Mobile Group | MI_GROUP | CHAR | 35 | |||||
| MULTI_DEVINST | Sign for multi device installation | MI_MULTIDEVINST | CHAR | 1 | MI_MULTI_DEVINST | ||||
| STATUS | Current status of package generation | MI_PACKAGE_STATUS | CHAR | 1 | MI_PACKAGE_STAT | ||||
| MI_STARTDATE | Start date of an task | MI_START_DATE | DATS | 8 | DATS | ||||
| MI_STARTTIME | Start time of an task | MI_START_TIME | TIMS | 6 | TIME | ||||
| MI_ENDDATE | Date when the process ends | MI_END_DATE | DATS | 8 | DATS | ||||
| MI_ENDTIME | Time when the process finished | MI_END_TIME | TIMS | 6 | TIME | ||||
| CREATED_BY | User Name | UNAME | CHAR | 12 | UNAME | ||||
| DEVICENAME | Define text for device ID | MEMGMT_DEVID_TXT | CHAR | 128 | MEMGMT_DEVID_TXT |
| Key field | Non-key field |
How do I retrieve data from SAP structure MIPACKAGE_HEAD_SEARCH using ABAP code?
As MIPACKAGE_HEAD_SEARCH 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 MIPACKAGE_HEAD_SEARCH as there is no data to select.How to access SAP table MIPACKAGE_HEAD_SEARCH
Within an ECC or HANA version of SAP you can also view further information about MIPACKAGE_HEAD_SEARCH 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