RSMINFOHEAD SAP (Header Minfo) Structure details
Description: Header Minfo
Structure field list including key, data, relationships and ABAP select examples
RSMINFOHEAD 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 "Header Minfo" 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_RSMINFOHEAD TYPE RSMINFOHEAD.
The RSMINFOHEAD table consists of various fields, each holding specific information or linking keys about Header Minfo data available in SAP. These include DATAPAKID (Data packet number), ISOURCE (InfoSource), TYPE (Type of Requested Data - Also New DS Types), ISTYPE (InfoSource type).. 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 RSMINFOHEAD 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 |
REQUNR | Request number for the data transfer | RSREQUNR | CHAR | 30 | RSREQUNR | ||||
DATAPAKID | Data packet number | RSDATAPID | NUMC | 6 | NUM6 | ||||
ISOURCE | InfoSource | RSISOURCE | CHAR | 30 | RSISOURCE | RSS | |||
TYPE | Type of Requested Data - Also New DS Types | RSBWREQUTYPE | CHAR | 1 | RSBWREQUTYPE | ||||
ISTYPE | InfoSource type | RS_TYP | CHAR | 1 | CHAR1 | ||||
LOGSYS | Source system | RSSLOGSYS | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
OLTPSOURCE | InfoSource | RSISOURCE | CHAR | 30 | RSISOURCE | RSS | |||
SOURCE_SYSTEM | Prefix of logical system | 0 | |||||||
HIENM | Customer-Defined Hierarchy Name | RSHIECHAR | CHAR | 30 | CHAR30 | ||||
HIEVERS | Hierarchy version | RSVERSION | CHAR | 3 | RSVERSION | ||||
HIEDATETO | Valid-to date | RSDATETO | DATS | 8 | DATUM | ||||
HIECLASS | Not More Closely Defined Area, Possibly Used for Patchlevels | CHAR4 | CHAR | 4 | CHAR4 | ||||
REQDATE | Date | DATUM | DATS | 8 | DATUM | ||||
REQTIME | Time | UZEIT | TIMS | 6 | UZEIT | ||||
REQUSER | User Name | UNAME | CHAR | 12 | UNAME | ||||
SELDATEFROM | Date | DATUM | DATS | 8 | DATUM | ||||
SELDATETO | Date | DATUM | DATS | 8 | DATUM | ||||
WRITETOIDOC | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
WRITETOODS | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
WRITETOCUBES | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
WRITEPARALLEL | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
SIMULATION | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
CANCELLATION | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
REBUILDING | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
DISPLAY | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
CHANGE | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
UPDMODE | Mode of data update (Full, Delta, etc.) | RSUPDMODE | CHAR | 2 | RSUPDMODE | ||||
SELECT_SIM | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
BOOKMODE | Numeric 1-character | NUM1 | NUMC | 1 | NUM1 | ||||
DEBUGMODE | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
DEBUGMODE_TS | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
ASYNCMODE | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
SIMREQUNR | BW Generation tool: GUID in compressed form (CHAR25) | RSSGUID25 | CHAR | 25 | RSSGUID25 | ||||
CANCELLATIONREQUNR | Request number for the data transfer | RSREQUNR | CHAR | 30 | RSREQUNR | ||||
CHAVL_CHECK | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
CONTINUE_AT_ERR | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
REPORT_AT_ERR | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
NUMBER_AT_ERR | No. of records to be checked when handling incorrect data | RSNUMBER_AT_ERR | INT4 | 10 | INT4 | ||||
NOSISICO | No single SID commit with master data update | RSNOSISICO | CHAR | 1 | RSNOSISICO | ||||
UPDR_PROCESSED | Boolean | RS_BOOL | CHAR | 1 | RS_BOOL | ||||
DUPRECDEL | Flag: Handling of duplicate data records | RSDMDDUPRECDEL | CHAR | 1 | RS_BOOL | ||||
CRT_PACKAGE | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
RUNTIME_CHECK | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
RUNTIME_VARIANT | Runtime Analysis: Name of Variant for Restricting Measuremt | SE30VAR | CHAR | 30 | CHAR30 | SE30_VNAME | |||
DTP_OLD_TS | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
LOGDPID | Logical InfoPackage variant (ID) | RSLOGDPID | CHAR | 30 | RSLOGDPID | ||||
ONLY_TO_INDX | Only Store Data in Cluster Table for Data Flow Comparison | RS_ONLY_INDX | CHAR | 1 | RS_ONLY_INDX |
Key field | Non-key field |
How do I retrieve data from SAP structure RSMINFOHEAD using ABAP code?
As RSMINFOHEAD 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 RSMINFOHEAD as there is no data to select.How to access SAP table RSMINFOHEAD
Within an ECC or HANA version of SAP you can also view further information about RSMINFOHEAD 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