RIMAK SAP (Include-structure for approp. request with change indicator) Structure details
Description: Include-structure for approp. request with change indicator
Structure field list including key, data, relationships and ABAP select examples
RIMAK 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 "Include-structure for approp. request with change indicator" 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_RIMAK TYPE RIMAK.
The RIMAK table consists of various fields, each holding specific information or linking keys about Include-structure for approp. request with change indicator data available in SAP. These include MANDT (Client), POSNR (Internal number for appropriation request), IVART (Appropriation request type), POSID (Appropriation Request Number (Formatted for Coding Mask)).. 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 or numeric)
SAP RIMAK 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 | |||
POSNR | Internal number for appropriation request | IMA_POSNR | CHAR | 12 | Assigned to domain | REQNR | IMA_POSNR | IAF | IIMA |
IVART | Appropriation request type | IMA_IVART | CHAR | 2 | TAIF1 | ALPHA | IMA_IVART | IAA | |
POSID | Appropriation Request Number (Formatted for Coding Mask) | IMA_POSID | CHAR | 24 | REQID | IMA_POSID | IAG | IIMA | |
OBJNR | Object number | J_OBJNR | CHAR | 22 | ONR00 | J_OBJNR | ONR | ||
WAERS | Object currency of the appropriation request | IMA_WAERS | CUKY | 5 | TCURC | WAERS | |||
ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
ERDAT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
AENAM | Name of Person Who Changed Object | AENAM | CHAR | 12 | USNAM | ||||
AEDAT | Date on which object was last changed | UPDAT | DATS | 8 | DATUM | ||||
VKOKRS | Responsible controlling area | IMA_VKOKRS | CHAR | 4 | TKA01 | CACCD | CAC | ||
ABUKRS | Requesting company code | IMA_ABUKRS | CHAR | 4 | T001 | BUKRS | BUK | ||
VBUKRS | Responsible company code | IMA_VBUKRS | CHAR | 4 | T001 | BUKRS | BUK | ||
ARCOMP | Requesting company | IMA_ARCOMP | CHAR | 6 | T880 | ALPHA | RCOMP | GCC | |
VRCOMP | Responsible company | IMA_VRCOMP | CHAR | 6 | T880 | ALPHA | RCOMP | GCC | |
FKBER | Functional Area | FKBER | CHAR | 16 | TFKB | FKBER | FBE | ||
TPLNR | Functional Location | TPLNR | CHAR | 30 | IFLOT | TPLNR | TPLNR | IFL | IFLM |
WERKS | Plant | WERKS_D | CHAR | 4 | T001W | WERKS | WRK | H_T001W_C | |
SIZECL | Scale of investment objects | IM_SIZECL | CHAR | 2 | TAIF5 | ALPHA | SIZECL | ||
WDATU | Desired date for start of implementation | IMA_WDATU | DATS | 8 | DATUM | ||||
PRIORI | Priority of the appropriation request | IMA_PRIOR | CHAR | 1 | TCN07 | NW_PRIO | |||
VKOSTL | Responsible cost center | IMA_VKOSTL | CHAR | 10 | CSKS | ALPHA | KOSTL | KOS | |
VPRCTR | Responsible profit center | IMA_VPRCTR | CHAR | 10 | CEPC | ALPHA | PRCTR | PRC | |
VGSBER | Responsible business area | IMA_VGSBER | CHAR | 4 | TGSB | GSBER | GSB | ||
XEXTRN | Required by external authorities | IMA_XEXTRN | CHAR | 1 | XFELD | ||||
AUART | Order Type | AUFART | CHAR | 4 | T003O | AUFART | AAT | ||
PROFIDPROJ | Project Profile | PROFIDPROJ | CHAR | 7 | TCJ41 | PROFIDPROJ | PWS | ||
XEINZL | Flag for individual app. request belonging to coll.app.reqst | IMA_XEINZL | CHAR | 1 | XFELD | ||||
VBUND | Trading partner number for app.requests within group | IMA_VBUND | CHAR | 6 | T880 | ALPHA | RCOMP | ||
PSPNR | Internal sequence number of project for approp. request | IMA_PSPNR | NUMC | 8 | PROJ | KONPD | PS_PSPNR | ||
GDATU | Planned approval date for appropriation request | IMA_GDATU | DATS | 8 | DATUM | ||||
GJAHR | Approval year for appropriation request | IMA_GJAHR | NUMC | 4 | GJAHR | GJAHR | |||
STORT | Planned location of appropriation request | IMA_STORT | CHAR | 10 | T499S | AP_STAND | |||
PRART | Program type | IM_PRART | CHAR | 4 | TAI05 | IM_PRART | |||
LOGSYSTEM | Logical System | LOGSYSTEM | CHAR | 10 | TBDLS | ALPHA | LOGSYS | ||
LAND1 | Country for Which Approp. Request Is Planned | IMA_LAND1 | CHAR | 3 | T005 | LAND1 | |||
XWFLOW | Indicator: Workflow was started | IMA_XWFLOW | CHAR | 1 | XFELD | ||||
SCOPE | Object Class | SCOPE_CV | CHAR | 2 | SCOPE | SCOPE_CV | PCO | ||
USR00 | User Field 01 (20 characters) | IMA_USR00 | CHAR | 20 | USRCHAR20 | ||||
USR01 | User field 2 (20 characters) | IMA_USR01 | CHAR | 20 | USRCHAR20 | ||||
USR02 | User field 3 (10 characters) | IMA_USR02 | CHAR | 10 | TAIF9 | IMA_USRCHAR10 | |||
USR03 | User field 4 (10 characters) | IMA_USR03 | CHAR | 10 | TAIF9 | IMA_USRCHAR10 | STAIF9_2 | ||
USR04 | User field 5 for quantity - IM | IMA_USR04 | QUAN | 13(3) | USRQUAN13 | ||||
USE04 | User field 5 for unit for quantity field 5 - IM | IMA_USE04 | UNIT | 3 | T006 | CUNIT | MEINS | ||
USR05 | User field 6 for quantity - IM | IMA_USR05 | QUAN | 13(3) | USRQUAN13 | ||||
USE05 | User field 6 for unit of quantity field 6 -IM- | IMA_USE05 | UNIT | 3 | T006 | CUNIT | MEINS | ||
USR06 | User field 7 for values - IM | IMA_USR06 | CURR | 13(3) | USRCURR13 | ||||
USE06 | User field 7 for currency for user field 7 | IMA_USE06 | CUKY | 5 | TCURC | WAERS | |||
USR07 | User field 8 for values - IM | IMA_USR07 | CURR | 13(3) | USRCURR13 | ||||
USE07 | User field 8 for currency for user field 8 | IMA_USE07 | CUKY | 5 | TCURC | WAERS | |||
USR08 | WB milestone date for IM | IMA_USR08 | DATS | 8 | USRDATE | ||||
USR09 | User field 10 as date for IM | IMA_USR09 | DATS | 8 | USRDATE | ||||
USR10 | So far so Good indicator for IM reports | IMA_USR10 | CHAR | 1 | XFELD | ||||
USR11 | User field 12 as indicator for IM reports | IMA_USR11 | CHAR | 1 | XFELD | ||||
USR12 | User field 13 for period and fiscal year | IMA_USR12 | ACCP | 6 | USRPER | ||||
USR13 | User field 14 for period and fiscal year | IMA_USR13 | ACCP | 6 | USRPER | ||||
STRATFLG | Strategic Appropriation Request | IM_STRATFLG | CHAR | 1 | XFELD | ||||
KZ | Change Type (U, I, S, D) | CDCHNGIND | CHAR | 1 | CDCHNGIND |
Key field | Non-key field |
How do I retrieve data from SAP structure RIMAK using ABAP code?
As RIMAK 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 RIMAK as there is no data to select.How to access SAP table RIMAK
Within an ECC or HANA version of SAP you can also view further information about RIMAK 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