RJHAMOZ_PLUS_TMP_KEY SAP (IS-M/AM: Ad Spec Assignment (AD) with Temporary Number) Structure details
Description: IS-M/AM: Ad Spec Assignment (AD) with Temporary Number
Related tables to RJHAMOZ_PLUS_TMP_KEY
Access table RJHAMOZ_PLUS_TMP_KEY
Structure field list including key, data, relationships and ABAP select examples
RJHAMOZ_PLUS_TMP_KEY 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: Ad Spec Assignment (AD) with Temporary Number" 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_RJHAMOZ_PLUS_TMP_KEY TYPE RJHAMOZ_PLUS_TMP_KEY.
The RJHAMOZ_PLUS_TMP_KEY table consists of various fields, each holding specific information or linking keys about IS-M/AM: Ad Spec Assignment (AD) with Temporary Number data available in SAP. These include MANDT (Client), AVM_NR (IS-M/AM: Sales Document Number), POS_NR (IS-M: Order Item Number), UPOS_NR (IS-M: Order Sub-Item Number).. 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 RJHAMOZ_PLUS_TMP_KEY 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 |
| POS_NR | IS-M: Order Item Number | POS_NR | NUMC | 3 | JHAP | AVM_PNR | |||
| UPOS_NR | IS-M: Order Sub-Item Number | UPOS_NR | NUMC | 4 | JHAU | AVM_UPNR | |||
| EIN_NR | IS-M: Schedule Line | EIN_NR | NUMC | 6 | JHAEA | AVMENR | |||
| MOTIV | IS-M: Ad Spec Number (Ad) | MOTIV_NR | NUMC | 6 | JHAMOT | PAM_MOTIV | |||
| XAUSUPOS | IS-M: Ad Spec/AI was Assigned in the Sub-Item Indicator | XAUSUPOS | CHAR | 1 | XFELD | ||||
| XAUSEINT | IS-M: Ind.: Ad Spec/AI Was Assigned in the Schedule Line | XAUSEINT | CHAR | 1 | XFELD | ||||
| XMOZAUSTEC | IS-M: Ad spec was assigned in technical system indicator | XMOZAUSTEC | CHAR | 1 | XFELD | ||||
| XMOT_CHNGD | IS-M: Ad Spec/Ad Insert was Changed Without Post-Editing | XMOT_CHNGD | CHAR | 1 | XFELD | ||||
| TMP_UPOS_NR | IS-M: (Temporary) Sub-Item Number | ISM_TMP_UPOS_NR | CHAR | 4 | ALPHA | ISM_TMP_UPOS_NR | |||
| TMP_EIN_NR | IS-M: (Temporary) Schedule Line Number | ISM_TMP_EIN_NR | CHAR | 6 | ALPHA | ISM_TMP_EIN_NR |
| Key field | Non-key field |
How do I retrieve data from SAP structure RJHAMOZ_PLUS_TMP_KEY using ABAP code?
As RJHAMOZ_PLUS_TMP_KEY 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 RJHAMOZ_PLUS_TMP_KEY as there is no data to select.How to access SAP table RJHAMOZ_PLUS_TMP_KEY
Within an ECC or HANA version of SAP you can also view further information about RJHAMOZ_PLUS_TMP_KEY 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