BAPISDHEAD SAP (Communication Fields: Sales and Distribution Document Header) Structure details
Description: Communication Fields: Sales and Distribution Document Header
Structure field list including key, data, relationships and ABAP select examples
BAPISDHEAD 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 "Communication Fields: Sales and Distribution Document Header" 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_BAPISDHEAD TYPE BAPISDHEAD.
The BAPISDHEAD table consists of various fields, each holding specific information or linking keys about Communication Fields: Sales and Distribution Document Header data available in SAP. These include DOC_TYPE (Sales Document Type), COLLECT_NO (Collective Number), SALES_ORG (Sales Organization), DISTR_CHAN (Distribution Channel).. 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 BAPISDHEAD 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 |
DOC_NUMBER | Sales Document | VBELN_VA | CHAR | 10 | VBUK | ALPHA | VBELN | AUN | |
DOC_TYPE | Sales Document Type | AUART | CHAR | 4 | TVAK | AUART | AUART | AAT | |
COLLECT_NO | Collective Number | SUBMI | CHAR | 10 | CHAR10 | ||||
SALES_ORG | Sales Organization | VKORG | CHAR | 4 | TVKO | VKORG | VKO | C_VKORG | |
DISTR_CHAN | Distribution Channel | VTWEG | CHAR | 2 | TVKOV | VTWEG | VTW | C_VTWEG | |
DIVISION | Division | SPART | CHAR | 2 | TVTA | SPART | SPA | C_SPART | |
SALES_GRP | Sales Group | VKGRP | CHAR | 3 | TVBVK | VKGRP | VKG | ||
SALES_OFF | Sales Office | VKBUR | CHAR | 4 | TVKBZ | VKBUR | VKB | ||
REQ_DATE_H | Requested delivery date | EDATU_VBAK | DATS | 8 | DATUM | ||||
DATE_TYPE | Proposed date type | PRGRS_VBAK | CHAR | 1 | PRGRS | ||||
PURCH_NO | Customer purchase order number | BSTNK | CHAR | 20 | BSTNK | ||||
PURCH_DATE | Customer purchase order date | BSTDK | DATS | 8 | DATUM | ||||
PO_METHOD | Customer purchase order type | BSARK | CHAR | 4 | T176 | BSARK | |||
PO_SUPPLEM | Purchase order number supplement | BSTZD | CHAR | 4 | BSTZD | ||||
REF_1 | Your Reference | IHREZ | CHAR | 12 | TEXT12 | ||||
NAME | Branching Name | BNAME | CHAR | 30 | CHAR30 | ||||
TELEPHONE | Telephone Number | TELF1_VP | CHAR | 16 | TELF1 | ||||
PRICE_GRP | Price group (customer) | KONDA | CHAR | 2 | T188 | KONDA | VKA | ||
CUST_GROUP | Customer group | KDGRP | CHAR | 2 | T151 | KDGRP | VKD | ||
SALES_DIST | Sales district | BZIRK | CHAR | 6 | T171 | BZIRK | BZI | ||
PRICE_LIST | Price list type | PLTYP | CHAR | 2 | T189 | PLTYP | VPL | ||
INCOTERMS1 | Incoterms (Part 1) | INCO1 | CHAR | 3 | TINC | INCO1 | |||
INCOTERMS2 | Incoterms (Part 2) | INCO2 | CHAR | 28 | INCO2 | ||||
PMNTTRMS | Terms of Payment Key | DZTERM | CHAR | 4 | ZTERM | ||||
DLV_BLOCK | Delivery block (document header) | LIFSK | CHAR | 2 | TVLS | LIFSP | |||
BILL_BLOCK | Billing block in SD document | FAKSK | CHAR | 2 | TVFS | FAKSP | |||
ORD_REASON | Order reason (reason for the business transaction) | AUGRU | CHAR | 3 | TVAU | AUGRU | |||
COMPL_DLV | Complete delivery defined for each sales order? | AUTLF | CHAR | 1 | XFELD | ||||
PRICE_DATE | Date for pricing and exchange rate | PRSDT | DATS | 8 | DATUM | ||||
QT_VALID_F | Quotation/Inquiry is valid from | ANGDT_V | DATS | 8 | DATUM | ||||
QT_VALID_T | Date until which bid/quotation is binding (valid-to date) | BNDDT | DATS | 8 | DATUM | ||||
CT_VALID_F | Valid-from date (outline agreements, product proposals) | GUEBG | DATS | 8 | DATUM | ||||
CT_VALID_T | Valid-to date (outline agreements, product proposals) | GUEEN | DATS | 8 | DATUM | ||||
CUST_GRP1 | Customer group 1 | KVGR1 | CHAR | 3 | TVV1 | KVGR1 | |||
CUST_GRP2 | Customer group 2 | KVGR2 | CHAR | 3 | TVV2 | KVGR2 | |||
CUST_GRP3 | Customer group 3 | KVGR3 | CHAR | 3 | TVV3 | KVGR3 | |||
CUST_GRP4 | Customer group 4 | KVGR4 | CHAR | 3 | TVV4 | KVGR4 | |||
CUST_GRP5 | Customer group 5 | KVGR5 | CHAR | 3 | TVV5 | KVGR5 | |||
PURCH_NO_C | Customer purchase order number | BSTKD | CHAR | 35 | BSTKD | ||||
PURCH_NO_S | Ship-to Party's Purchase Order Number | BSTKD_E | CHAR | 35 | BSTKD | ||||
PO_DAT_S | Ship-to party's PO date | BSTDK_E | DATS | 8 | DATUM | ||||
PO_METH_S | Ship-to party purchase order type | BSARK_E | CHAR | 4 | T176 | BSARK | |||
REF_1_S | Ship-to party character | IHREZ_E | CHAR | 12 | TEXT12 | ||||
SD_DOC_CAT | SD document category | VBTYP | CHAR | 1 | VBTYP | ||||
SHIP_COND | Shipping Conditions | VSBED | CHAR | 2 | TVSB | VSBED | |||
CURRENCY | SD Document Currency | WAERK | CUKY | 5 | TCURC | WAERS | FWS | ||
CURRENCY_ISO | ISO code currency | WAERS_ISO | CHAR | 3 | ISOCD | ||||
DLV_TIME | Agreed delivery time | DELCO | CHAR | 3 | DELCO | ||||
CD_TYPE1 | Condition type | KSCHA | CHAR | 4 | T685 | KSCHL | VKS | ||
CD_VALUE1 | Condition rate | BAPIKBETR | DEC | 23(4) | BAPICURR | ||||
CD_P_UNT1 | Condition pricing unit | KPEINC | NUMC | 5 | NUMC5 | ||||
CD_D_UNT1 | Condition unit in the document | KVMEI | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
CD_D_UISO1 | Condition unit of measure in UoM | KVMEI_ISO | CHAR | 3 | T006I | ISOCD_UNIT | |||
CD_CURR1 | Currency Key | WAERS | CUKY | 5 | TCURC | WAERS | FWS | ||
CD_CU_ISO1 | ISO code currency | WAERS_ISO | CHAR | 3 | ISOCD | ||||
CD_TYPE2 | Condition type | KSCHA | CHAR | 4 | T685 | KSCHL | VKS | ||
CD_VALUE2 | Condition rate | BAPIKBETR | DEC | 23(4) | BAPICURR | ||||
CD_P_UNT2 | Condition pricing unit | KPEINC | NUMC | 5 | NUMC5 | ||||
CD_D_UNT2 | Condition unit in the document | KVMEI | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
CD_D_UISO2 | Condition unit of measure in UoM | KVMEI_ISO | CHAR | 3 | T006I | ISOCD_UNIT | |||
CD_CURR2 | Currency Key | WAERS | CUKY | 5 | TCURC | WAERS | FWS | ||
CD_CU_ISO2 | ISO code currency | WAERS_ISO | CHAR | 3 | ISOCD | ||||
CD_TYPE3 | Condition type | KSCHA | CHAR | 4 | T685 | KSCHL | VKS | ||
CD_VALUE3 | Condition rate | BAPIKBETR | DEC | 23(4) | BAPICURR | ||||
CD_P_UNT3 | Condition pricing unit | KPEINC | NUMC | 5 | NUMC5 | ||||
CD_D_UNT3 | Condition unit in the document | KVMEI | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
CD_D_UISO3 | Condition unit of measure in UoM | KVMEI_ISO | CHAR | 3 | T006I | ISOCD_UNIT | |||
CD_CURR3 | Currency Key | WAERS | CUKY | 5 | TCURC | WAERS | FWS | ||
CD_CU_ISO3 | ISO code currency | WAERS_ISO | CHAR | 3 | ISOCD | ||||
CD_TYPE4 | Condition type | KSCHA | CHAR | 4 | T685 | KSCHL | VKS | ||
CD_VALUE4 | Condition rate | BAPIKBETR | DEC | 23(4) | BAPICURR | ||||
CD_P_UNT4 | Condition pricing unit | KPEINC | NUMC | 5 | NUMC5 | ||||
CD_D_UNT4 | Condition unit in the document | KVMEI | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
CD_D_UISO4 | Condition unit of measure in UoM | KVMEI_ISO | CHAR | 3 | T006I | ISOCD_UNIT | |||
CD_CURR4 | Currency Key | WAERS | CUKY | 5 | TCURC | WAERS | FWS | ||
CD_CU_ISO4 | ISO code currency | WAERS_ISO | CHAR | 3 | ISOCD | ||||
FKK_CONACCT | Character Field of Length 12 | CHAR12 | CHAR | 12 | CHAR12 | ||||
REF_DOC | Document number of the reference document | VGBEL | CHAR | 10 | Assigned to domain | ALPHA | VBELN | ||
REF_DOC_CA | Document category of preceding SD document | VBTYP_V | CHAR | 1 | VBTYP | ||||
SEPA_MANDATE_ID | Unique Referene to Mandate per Payment Recipient | SEPA_MNDID | CHAR | 35 | ID035 |
Key field | Non-key field |
How do I retrieve data from SAP structure BAPISDHEAD using ABAP code?
As BAPISDHEAD 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 BAPISDHEAD as there is no data to select.How to access SAP table BAPISDHEAD
Within an ECC or HANA version of SAP you can also view further information about BAPISDHEAD 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