BAPI_PHYSINV_HEAD SAP (BAPI Communication Structure: Header Data of Phys. Inv. Doc.) Structure details
Description: BAPI Communication Structure: Header Data of Phys. Inv. Doc.
Related tables to BAPI_PHYSINV_HEAD
Access table BAPI_PHYSINV_HEAD
Structure field list including key, data, relationships and ABAP select examples
BAPI_PHYSINV_HEAD 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 "BAPI Communication Structure: Header Data of Phys. Inv. Doc." 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_BAPI_PHYSINV_HEAD TYPE BAPI_PHYSINV_HEAD.
The BAPI_PHYSINV_HEAD table consists of various fields, each holding specific information or linking keys about BAPI Communication Structure: Header Data of Phys. Inv. Doc. data available in SAP. These include FISCALYEAR (Fiscal Year), EVENT_TYPE (Transaction/Event Type), PLANT (Plant), STGE_LOC (Storage Location).. 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: Cannot Be Enhanced
SAP BAPI_PHYSINV_HEAD 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 |
PHYSINVENTORY | Physical Inventory Document | IBLNR | CHAR | 10 | ALPHA | BELNR | IBN | ||
FISCALYEAR | Fiscal Year | GJAHR | NUMC | 4 | GJAHR | GJAHR | GJR | ||
EVENT_TYPE | Transaction/Event Type | VGART | CHAR | 2 | T158V | VGART | |||
PLANT | Plant | WERKS_D | CHAR | 4 | T001W | WERKS | WRK | H_T001W_C | |
STGE_LOC | Storage Location | LGORT_D | CHAR | 4 | T001L | LGORT | LAG | ||
SPEC_STOCK | Special Stock Indicator | SOBKZ | CHAR | 1 | T148 | SOBKZ | |||
DOC_DATE | Document Date in Document | BLDAT | DATS | 8 | DATUM | ||||
PLAN_DATE | Planned date of inventory count | GIDAT | DATS | 8 | DATUM | ||||
COUNT_DATE | Date of last count | DZLDAT | DATS | 8 | DATUM | ||||
PSTNG_DATE | Posting Date in the Document | BUDAT | DATS | 8 | DATUM | ||||
FIS_PERIOD | Fiscal Period | MONAT | NUMC | 2 | MONAT | ||||
USERNAME | User name | USNAM | CHAR | 12 | USR02 | XUBNAME | USR | ||
POST_BLOCK | Posting block due to physical inventory | ISPER | CHAR | 1 | XFELD | ||||
COUNT_STATUS | Status of count | DZSTAT | CHAR | 1 | ZSTAT | ||||
ADJUST_STATUS | Status of adjustment posting (inventory differences) | DSTAT | CHAR | 1 | DSTAT | ||||
PHYS_INV_REF | Reference number for physical inventory | XBLNI | CHAR | 16 | XBLNR | ||||
DELETE_STATUS | Status of delete flag | LSTAT | CHAR | 1 | DSTAT | ||||
FREEZEBOOKINV | Freeze book inventory | XBUFI | CHAR | 1 | XFELD | ||||
GROUPING_TYPE | Type of grouping criterion | KEORD | CHAR | 2 | KEORD | ||||
GROUPING_CRIT | Grouping criterion of physical inventory document item | ORDNG | CHAR | 10 | CHAR10 | ||||
PHYS_INV_NO | Physical inventory number | INVNU | CHAR | 16 | XBLNR | ||||
PHYS_INV_NO_LONG | Physical Inventory Number (Dependencies see Long Text) | INVNU_LONG | CHAR | 35 | XBLNR_LONG | ||||
PHYS_INV_REF_LONG | Phys. Inv. Reference Number (Dependencies see Long Text) | XBLNI_LONG | CHAR | 35 | XBLNR_LONG |
Key field | Non-key field |
How do I retrieve data from SAP structure BAPI_PHYSINV_HEAD using ABAP code?
As BAPI_PHYSINV_HEAD 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 BAPI_PHYSINV_HEAD as there is no data to select.How to access SAP table BAPI_PHYSINV_HEAD
Within an ECC or HANA version of SAP you can also view further information about BAPI_PHYSINV_HEAD 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