RIHIHSG SAP (Output structure: permits for PM object) Structure details
Description: Output structure: permits for PM object
Structure field list including key, data, relationships and ABAP select examples
RIHIHSG 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 "Output structure: permits for PM object" 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_RIHIHSG TYPE RIHIHSG.
The RIHIHSG table consists of various fields, each holding specific information or linking keys about Output structure: permits for PM object data available in SAP. These include MANDT (Client), OBJNR (Object number), COUNTER (Counter for differentiation 6-digit), ERDAT (Date on Which Record Was Created).. 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 (character-type)
SAP RIHIHSG 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 | |||
| OBJNR | Object number | J_OBJNR | CHAR | 22 | ONR00 | J_OBJNR | ONR | ||
| COUNTER | Counter for differentiation 6-digit | I_COUNT | NUMC | 6 | NUM6 | ||||
| ERDAT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
| ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
| AEDAT | Changed On | AEDAT | DATS | 8 | DATUM | ||||
| AENAM | Name of Person Who Changed Object | AENAM | CHAR | 12 | USNAM | ||||
| PMSOG | Permit Key | PMSOG | CHAR | 10 | T357G | PMSOG | |||
| K_AF | Indicator: Valid for Order Release | K_AF | CHAR | 1 | G_ERROR | ||||
| K_AA | Indicator: Valid for Order Completion | K_AA | CHAR | 1 | G_ERROR | ||||
| K_DRUCK | Printout of Permit Papers | K_DRUCK | CHAR | 1 | X | ||||
| K_PRO | Indicator: Permit Proposed During Processing | K_PRO | CHAR | 1 | X | ||||
| KZLTX | Long Text for Permit | KZLTG | CHAR | 1 | XFELD | ||||
| EQUNR | Equipment Number | EQUNR | CHAR | 18 | Assigned to domain | ALPHA | EQUNR | EQN | EQUI |
| TPLNR | Functional Location | TPLNR | CHAR | 30 | Assigned to domain | TPLNR | TPLNR | IFL | IFLM |
| AUFNR | Order Number | AUFNR | CHAR | 12 | Assigned to domain | ALPHA | AUFNR | ANR | |
| VORNR | Operation/Activity Number | VORNR | CHAR | 4 | NUMCV | VORNR | VGN | ||
| K_OBJEKT | Indicator: For Which Object the Permit Was Created | K_OBJEKT | CHAR | 1 | G_OBJECT | ||||
| IHASP | Language in Which the Piece of Equipment was Entered | EQASP | LANG | 1 | T002 | ISOLA | SPRAS | ||
| K_NODEL | Changeability of Permits | K_NODEL | CHAR | 1 | X | ||||
| K_SKIP | Relevance of Permit | K_SKIP | CHAR | 1 | X | ||||
| K_ORIGIN | Indicator: Permit Origin in Order | K_ORIGIN | CHAR | 1 | G_ORIGIN | ||||
| CLASS | Class number | KLASSE_D | CHAR | 18 | KLASSE | KLA | |||
| LVORM | Deletion Indicator | LVORM | CHAR | 1 | XFELD | ||||
| PLNTY | Task List Type | PLNTY | CHAR | 1 | Assigned to domain | PLNTY | PTY | H_TCA01 | |
| PLNNR | Key for Task List Group | PLNNR | CHAR | 8 | ALPHA | PLNNR | PLN | PLKS | |
| PLNAL | Group Counter | PLNAL | CHAR | 2 | ALPHA | ALTNR | PAL | ||
| GNTXT | Permit Text | GNTXT | CHAR | 30 | TEXT30 | ||||
| SPRAS | Language Key | SPRAS | LANG | 1 | T002 | ISOLA | SPRAS | SPR | H_T002 |
| Key field | Non-key field |
How do I retrieve data from SAP structure RIHIHSG using ABAP code?
As RIHIHSG 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 RIHIHSG as there is no data to select.How to access SAP table RIHIHSG
Within an ECC or HANA version of SAP you can also view further information about RIHIHSG 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