RJVTMCP_STRUCTURE SAP (IS-M: TMCP Structures for TMCP Products (CRoutes/GUnits)) Structure details
Description: IS-M: TMCP Structures for TMCP Products (CRoutes/GUnits)
Related tables to RJVTMCP_STRUCTURE
Access table RJVTMCP_STRUCTURE
Structure field list including key, data, relationships and ABAP select examples
RJVTMCP_STRUCTURE 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 "IS-M: TMCP Structures for TMCP Products (CRoutes/GUnits)" 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_RJVTMCP_STRUCTURE TYPE RJVTMCP_STRUCTURE.
The RJVTMCP_STRUCTURE table consists of various fields, each holding specific information or linking keys about IS-M: TMCP Structures for TMCP Products (CRoutes/GUnits) data available in SAP. These include MANDT (Client), PUBLICATION (Publication), EDITION (Edition), PUBLDATE (Publication Date).. 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 RJVTMCP_STRUCTURE 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 | |||
| PUBLICATION | Publication | DRERZ | CHAR | 8 | JDTDRER | ALPHA | DRERZ | JD1 | MJD1 |
| EDITION | Edition | PVA | CHAR | 8 | JDTPVA | ALPHA | PVA | JD2 | |
| PUBLDATE | Publication Date | ERSCHDAT | DATS | 8 | DATUM | JD9 | |||
| BEZIRK | Carrier Route | BEZIRK | CHAR | 10 | Assigned to domain | ALPHA | BEZIRK | BEZ | MJVC |
| GEOEIN | Number of Geographical Unit | GEOEIN | CHAR | 10 | Assigned to domain | ALPHA | GEOEIN | GEO | |
| XNO_HHADR_FOUND | Indicator: No Households Found for Carrier Route/Geo. Unit | TMCP_XNO_HH | CHAR | 1 | XFELD | ||||
| XFINISHED | Indicator: Market Coverage Completed | TMCP_XFINISHED | CHAR | 1 | XFELD | ||||
| XMANUALLY_CLOSED | Indicator: Market Coverage Closed Manually | TMCP_XMANUALLY_CLOSED | CHAR | 1 | XFELD | ||||
| EXCL_TYPE | Type of Market Coverage Exclusion | TMCP_EXCLUDE_TYPE | NUMC | 2 | TMCP_EXCLUDE_TYPE | ||||
| XORDER_GENERATED | Market Coverage: Shipping Orders Generated | XORDER_GENERATED | CHAR | 1 | XFELD | ||||
| SHIPORDNBR | Address-Based Shipping Order Number | SHIPORDNBR | CHAR | 10 | Assigned to domain | ALPHA | SHIPORDNBR | JVSON | MJVSOA |
| XTMCP | Indicator: Total Market Coverage | TMCP_XTMC | CHAR | 1 | XFELD | ||||
| XSATURATION | Indicator: Market Saturation | TMCP_XSATURATION | CHAR | 1 | XFELD | ||||
| SEQ_NR_LAST | Last Sequence Number for Market Coverage Execution | TMCP_SEQUENCE_NUMBER_LAST | NUMC | 3 | NUM3 | ||||
| ERFUSER | Created By | ERFUSER | CHAR | 12 | USNAM | ||||
| ERFDATE | Created On | ERFDATE | DATS | 8 | DATUM | ||||
| ERFTIME | Time Created | ERFTIME | TIMS | 6 | UZEIT | ||||
| AENUSER | Last Changed By | AENUSER | CHAR | 12 | USNAM | ||||
| AENDATE | Date of Last Change | AENDATE | DATS | 8 | DATUM | ||||
| AENTIME | Time of Last Change | AENTIME | TIMS | 6 | UZEIT | ||||
| TASK_ID | Task ID | TMCP_TASK_ID | CHAR | 32 | CHAR0032 | ||||
| TASK_SYSTEM | RFC System ID | TMCP_TASK_RFCDEST | CHAR | 32 | Assigned to domain | RFCDEST | |||
| TASK_START_DATE | Task Start Date | TMCP_TASK_STARTDATE | DATS | 8 | DATS | ||||
| TASK_END_DATE | Task End Date | TMCP_TASK_ENDDATE | DATS | 8 | DATS | ||||
| TASK_START_TIME | Task Start Time | TMCP_TASK_START_TIME | TIMS | 6 | TIMS | ||||
| TASK_END_TIME | Task End Time | TMCP_TASK_END_TIME | TIMS | 6 | TIMS | ||||
| TASK_ERROR | Number of Message Type | ERROR | CHAR | 2 | Assigned to domain | ERROR | |||
| ERROR_MESSAGE | Message Row | MSG | CHAR | 83 | CHAR83 |
| Key field | Non-key field |
How do I retrieve data from SAP structure RJVTMCP_STRUCTURE using ABAP code?
As RJVTMCP_STRUCTURE 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 RJVTMCP_STRUCTURE as there is no data to select.How to access SAP table RJVTMCP_STRUCTURE
Within an ECC or HANA version of SAP you can also view further information about RJVTMCP_STRUCTURE 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