RJHAMOTO SAP (IS-M/AM: Structure for Online Ad Spec) Structure details
Description: IS-M/AM: Structure for Online Ad Spec
Structure field list including key, data, relationships and ABAP select examples
RJHAMOTO 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/AM: Structure for Online Ad Spec" 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_RJHAMOTO TYPE RJHAMOTO.
The RJHAMOTO table consists of various fields, each holding specific information or linking keys about IS-M/AM: Structure for Online Ad Spec data available in SAP. These include MANDT (Client), AVM_NR (IS-M/AM: Sales Document Number), MOTIV (IS-M: Order ad spec number (online)), MOTIVSTAT (IS-M: Ad spec status).. 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 RJHAMOTO 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 | |||
AVM_NR | IS-M/AM: Sales Document Number | AVM_NR | CHAR | 10 | JHAK | ALPHA | AVM_NR | JHA | MJHA |
MOTIV | IS-M: Order ad spec number (online) | OLMOTIV_NR | NUMC | 6 | Assigned to domain | MAM_OL_MOT | |||
MOTIVSTAT | IS-M: Ad spec status | MOTIVSTAT | CHAR | 2 | PAM_STATUS | ||||
NOTIZ | IS-M: Note for Ad Spec Design | MOTIVNOTIZ | CHAR | 50 | TEXT50 | ||||
MOTIVID | IS-M: Assigned ad spec/ad spec file in technical system | MOTIVID | CHAR | 12 | MOTIVID | ||||
VORL_AVMNR | IS-M: Order Number of the Preceding Document | VORL_AVMNR | CHAR | 10 | JHAK | ALPHA | AVM_NR | ||
VORL_MOTNR | IS-M: Template ad spec (online) | VORL_MOTNR_OL | NUMC | 6 | JHAMOTO | MAM_OL_MOT | |||
VORL_TECID | IS-M: Ad spec template (description in technical system) | VORL_TECID | CHAR | 12 | MOTIVID | ||||
HOEHE_S | IS-M: Planned Height of the Ad Spec | HOEHE_S | QUAN | 7(3) | GROESSE | ||||
HOEHE_S_EH | IS-M/AM: Unit of Measurement for Height (Online) | ONL_HOEHE_SEH | UNIT | 3 | TJHOLHME | CUNIT | ONL_HOEHE_SEH | ||
BREITE_S | IS-M: Planned Ad Spec Width | BREITE_S | QUAN | 7(3) | GROESSE | ||||
BREITE_SEH | IS-M/AM: Unit of Measurement for Online Ad Size Field | ISPEINH_OL | UNIT | 3 | TJHOLBME | CUNIT | ISPEINH_OL | ||
STICHW | IS-M: Keyword | STICHW | CHAR | 40 | TEXT40 | ||||
PRODH | IS-M/AM: Product Hierarchy | J_PRODH | CHAR | 18 | JJT179 | J_PRODH | |||
FORMAT_ONL | IS-M/AM: Format Proposal (Online) | FORMAT_ONL | CHAR | 4 | TJHOLFMT | ALPHA | FORMAT_ONL | ||
LINK_URL | IS-M/AM: Target URL for a banner | LINK_URL | CHAR | 132 | TEXT132 | ||||
GROESSE | IS-M/AM: File Size for Online Ad Spec | GROESSE_KB | DEC | 10(3) | ISM_DEC10_3 | ||||
GROESSE_UNIT | IS-M/AM: Unit for Physical Ad Spec Size | GROESSE_UNIT | UNIT | 3 | T006 | CUNIT | MEINS | ||
CLICK_TEXT | IS-M/AM: Clicktext for an Online Ad Spec | CLICKTEXT | CHAR | 132 | TEXT132 | ||||
ALTERN_TEXT | IS-M/AM: Alternative Text for an Online Ad Spec | ALTERN_TEXT | CHAR | 132 | TEXT132 | ||||
DRVORL_NR | IS-M: Ad Spec Master | DRVORL_NR | NUMC | 6 | JHADRV | DRVORL_NR | |||
AENVERS_NR_OL | IS-M: Last Change Version for Technical System | AENVERS_NR | NUMC | 4 | AENVERS_NR | ||||
XMOTIVTEXT | IS-M/AM: Text Exists for the Ad Spec Indicator | XMOTIVTEXT | CHAR | 1 | XFELD | ||||
XSTORNIERT | IS-M: Canceled Order Object Indicator | XSTORNIERT | CHAR | 1 | XFELD | ||||
XUVMOT | IS-M: 'Ad spec data incomplete' indicator | XUVMOT | CHAR | 1 | XFELD | ||||
XPRNOTW | IS-M: Ad Spec Check Required But Not Performed | XPRNOTW | CHAR | 1 | XFELD | ||||
MERKMAL0 | IS-M: Characteristic 0 for Individual Use (Online Ad Spec) | MERK0_MOTO | CHAR | 1 | XFELD | ||||
MERKMAL1 | IS-M: Characteristic 1 for Individual Use (Online Ad Spec) | MERK1_MOTO | CHAR | 1 | XFELD | ||||
MERKMAL2 | IS-M: Characteristic 2 for Individual Use (Online Ad Spec) | MERK2_MOTO | CHAR | 1 | XFELD | ||||
MERKMAL3 | IS-M: Characteristic 3 for Individual Use (Online Ad Spec) | MERK3_MOTO | CHAR | 1 | XFELD | ||||
MERKMAL4 | IS-M: Characteristic 4 for Individual Use (Online Ad Spec) | MERK4_MOTO | CHAR | 1 | XFELD | ||||
MERKMAL5 | IS-M: Characteristic 5 for Individual Use (Online Ad Spec) | MERK5_MOTO | CHAR | 1 | XFELD | ||||
MERKMAL6 | IS-M: Characteristic 6 for Individual Use (Online Ad Spec) | MERK6_MOTO | CHAR | 1 | XFELD | ||||
MERKMAL7 | IS-M: Characteristic 7 for Individual Use (Online Ad Spec) | MERK7_MOTO | CHAR | 1 | XFELD | ||||
MERKMAL8 | IS-M: Characteristic 8 for Individual Use (Online Ad Spec) | MERK8_MOTO | CHAR | 1 | XFELD | ||||
MERKMAL9 | IS-M: Characteristic 9 for Individual Use (Online Ad Spec) | MERK9_MOTO | CHAR | 1 | XFELD | ||||
TMOT_KENNZ | IS-M/AM: Sub ad spec/linked ad specs indicator | TMOT_KENNZ | CHAR | 6 | TJH75 | TMOTIV_KE | |||
TMOT_NR | IS-M: Position of the Sub Ad Spec Within the Chain | TMOT_NR | NUMC | 2 | NUMC2 | ||||
TMOT_ANZ | IS-M: Number of sub ad specs in an ad spec chain | TMOT_ANZ | NUMC | 2 | NUM02 | ||||
TMOT_BEZUG | IS-M: Ref.to header ad spec in ad spec linking (online) | TMOT_BEZUG_OL | NUMC | 6 | JHAMOTO | MAM_OL_MOT | |||
TMOT_LAGE | IS-M: Position of Sub Ad Spec (Relative to Header Ad Spec) | TMOT_LAGE | CHAR | 4 | TJH77 | MOT_LAGE | |||
TMOT_KOMM | IS-M: Comment on location of sub ad spec | TMOT_KOMM | CHAR | 30 | TEXT30 | ||||
PRODH_TEXT | Description | BEZEI20 | CHAR | 20 | TEXT20 | ||||
FORMAT_TEXT | Text with 15 Characters | BEZEI15 | CHAR | 15 | CHAR15 |
Key field | Non-key field |
How do I retrieve data from SAP structure RJHAMOTO using ABAP code?
As RJHAMOTO 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 RJHAMOTO as there is no data to select.How to access SAP table RJHAMOTO
Within an ECC or HANA version of SAP you can also view further information about RJHAMOTO 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