JHIAP SAP (IS-M/AM: Include for Pure Item Attributes) Structure details
Description: IS-M/AM: Include for Pure Item Attributes
Structure field list including key, data, relationships and ABAP select examples
JHIAP 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: Include for Pure Item Attributes" 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_JHIAP TYPE JHIAP.
The JHIAP table consists of various fields, each holding specific information or linking keys about IS-M/AM: Include for Pure Item Attributes data available in SAP. These include PSTYV (IS-M: Item Category for Sales Document), VBTYP (IS-M/AM: Sales Document Category), WERBK_TYP (IS-M: Combination Sale Type), WERBK_KNZ (IS-M: Combination Sale Indicator).. 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 JHIAP 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 |
| POS_ART | IS-M: Order-Publishing-Media - Item Type | AVMPOS_ART | CHAR | 2 | TJH17 | AVMPOS_ART | |||
| PSTYV | IS-M: Item Category for Sales Document | PSTYV_PAM | CHAR | 4 | TJHAP | PSTYV_PAM | |||
| VBTYP | IS-M/AM: Sales Document Category | ISPVBTYP | CHAR | 1 | ISPVBTYP | ||||
| WERBK_TYP | IS-M: Combination Sale Type | WKOMBI_TYP | CHAR | 2 | TJH91 | WKOMBI_TYP | MJHWKOMBI_TYP | ||
| WERBK_KNZ | IS-M: Combination Sale Indicator | WERBK_KNZ | NUMC | 4 | WERBEKKNZ | ||||
| XAGENAUFTR | IS-M: Agency order indicator | XAGENAUFTR | CHAR | 1 | XFELD | ||||
| XEINTEILG | IS-M: Indicator for modification at subordinate ord. level | XEINTEILG | CHAR | 1 | XFELD | ||||
| BRAN_PAM | IS-M/AM: Current Industry Sector Associated With Order Item | BRAN_POS | CHAR | 10 | TBRC | BRACO | |||
| STATUSK | IS-M: Status | STATUSK | CHAR | 2 | PAM_STATUS | ||||
| VERMITTLER | IS-M: Sales Agent with ID Code for Screen | VERMK | CHAR | 10 | Assigned to domain | VERMK | JJMVERM | JGP | MJG0N |
| VNR | IS-M: Media Sales Agent Contract Number | JVMVVNR | CHAR | 10 | JJTVV | ALPHA | JVMVVNR | JJA | MJJV |
| BEDNR | IS-M: Number of Media Sales Agent Contract Requirement | VM_BEDNR | NUMC | 6 | JJTVB | VM_BEDNR | |||
| PROSL | IS-M/AM: Commission Key for Media Sales Agent | JPROVSCHL | CHAR | 5 | TJH23 | PRSCHL | |||
| KAMPAGNE | IS-M: Campaign (customer) | KAMPAGNE | CHAR | 6 | TJJKAMP | KAMPAGNE | |||
| WERBK_POS | IS-M: Combination Sale Grouping Item Number | WERBK_POS | NUMC | 3 | JHAP | AVM_PNR | |||
| WERBK_UPOS | IS-M: Combination Sale Grouping Sub-Item | WERBK_UPOS | NUMC | 4 | AVM_UPNR | ||||
| WERBK_EINT | IS-M: Combination Sale Grouping for Schedule Line Number | WERBK_EINT | NUMC | 6 | JHAE | AVMENR | |||
| REF_AVM_NR | IS-M: Reference Order Number of Preceding Order | REF_AVM_NR | CHAR | 10 | JHAK | ALPHA | AVM_NR | ||
| REF_POS_NR | IS-M: Reference Item Number of Preceding Item | REF_POS_NR | NUMC | 3 | JHAP | AVM_PNR | |||
| SUC_AVM_NR | IS-M: Order Number of Subsequent Document | SUC_AVM_NR | CHAR | 10 | JHAK | ALPHA | AVM_NR | ||
| SUC_POS_NR | IS-M: Item Number of Subsequent Item | SUC_POS_NR | NUMC | 3 | JHAP | AVM_PNR | |||
| VORL_AVMNR | IS-M: Order Number of the Preceding Document | VORL_AVMNR | CHAR | 10 | JHAK | ALPHA | AVM_NR | ||
| VORL_POSNR | IS-M: Item number of the Preceding Item | VORL_POSNR | NUMC | 3 | JHAP | AVM_PNR | |||
| CAMPAIGN | IS-M: Marketing Campaign | ISM_MARKETING_CAMPAIGN | RAW | 16 | MCAMP | ISM_MARKETING_CAMPAIGN | PRPM_CGPL_K |
| Key field | Non-key field |
How do I retrieve data from SAP structure JHIAP using ABAP code?
As JHIAP 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 JHIAP as there is no data to select.How to access SAP table JHIAP
Within an ECC or HANA version of SAP you can also view further information about JHIAP 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