BAPISHELFHD SAP (Header data for planogram) Structure details
Description: Header data for planogram
Structure field list including key, data, relationships and ABAP select examples
BAPISHELFHD 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 "Header data for planogram" 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_BAPISHELFHD TYPE BAPISHELFHD.
The BAPISHELFHD table consists of various fields, each holding specific information or linking keys about Header data for planogram data available in SAP. These include LAYMOD_DESC (Layout module description), CUSTOMER_SITE (Customer Number for Plant), PLANT (Plant), LANGU (Language Key).. 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 BAPISHELFHD 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 |
| LAYOUT_MOD | Layout Module | LAYGR | CHAR | 10 | TWML | LAYGR | WLM | LAYMODD | |
| LAYMOD_DESC | Layout module description | LAYMOD_DESC | CHAR | 40 | TEXT40 | ||||
| CUSTOMER_SITE | Customer Number for Plant | LOCNR | CHAR | 10 | KNA1 | ALPHA | KUNNR | KUN | |
| PLANT | Plant | WERKS_D | CHAR | 4 | T001W | WERKS | WRK | H_T001W_C | |
| LANGU | Language Key | SPRAS | LANG | 1 | T002 | ISOLA | SPRAS | SPR | H_T002 |
| LANGU_ISO | 2-Character SAP Language Code | LAISO | CHAR | 2 | LAISO | ||||
| SHELF_OPT_PROFILE | Space management profile | SSOPT_PRO | CHAR | 4 | TWSSO | SSOPT_PRO | |||
| PURCH_ORG | Purchasing Organization | EKORG | CHAR | 4 | T024E | EKORG | EKO | ||
| SALESORG | Sales Organization | VKORG | CHAR | 4 | TVKO | VKORG | VKO | C_VKORG | |
| DISTR_CHAN | Distribution Channel | VTWEG | CHAR | 2 | TVTW | VTWEG | VTW | C_VTWEG | |
| LAYOUT | Layout | LAYVAR | CHAR | 10 | TWGV | LAYVAR | |||
| LAY_DOC_PATH | Path for layout documents | LAYDOCPATH | CHAR | 140 | CHAR140 | ||||
| AREA | Layout area number | LAYPOSNR | NUMC | 10 | TWGLV | NUMC10 | |||
| PRICE_DATE | Key date for price determination | PRICE_DATE | DATS | 8 | DATUM | ||||
| PERIOD_NUM | Number of periods for reading business volume data | PERIOD_NUM | NUMC | 2 | NUMC02 | ||||
| PERIOD_TYPE | Period category for reading business volume data | PERIOD_TYPE | CHAR | 6 | CHAR6 | ||||
| LAYMOD_VER | Layout Module Version | LAYMOD_VER | NUMC | 4 | Assigned to domain | WLMV | LAYMOD_VER | WLMV | LAYMODVER |
| LM_DATE_FR | Validity start date of a layout module version | LM_DATE_FR | DATS | 8 | DATS | ||||
| LM_DATE_TO | Validity end date of a layout module version | LM_DATE_TO | DATS | 8 | DATS | ||||
| LMOD_STAT | Status of a layout module version | LMOD_STAT | CHAR | 2 | LMOD_STAT | ||||
| ASSORTMENT | Assortment | ASORT | CHAR | 10 | Assigned to domain | ALPHA | ASORT | WST | WSOR |
| LAYMOD_VAR | Variant for Layout Module Version | LAYMOD_VAR | CHAR | 4 | Assigned to domain | LAYMOD_VAR | WLVA | ||
| DOCUMENT_NUMBER | Document number | DOKNR | CHAR | 25 | Assigned to domain | ALPHA | DOKNR | CV1 |
| Key field | Non-key field |
How do I retrieve data from SAP structure BAPISHELFHD using ABAP code?
As BAPISHELFHD 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 BAPISHELFHD as there is no data to select.How to access SAP table BAPISHELFHD
Within an ECC or HANA version of SAP you can also view further information about BAPISHELFHD 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