BAPICDHEADO SAP (Communication Structure: Customer Settlement Header Data) Structure details
Dictionary Type: Structure
Description: Communication Structure: Customer Settlement Header Data
Description: Communication Structure: Customer Settlement Header Data
Structure field list including key, data, relationships and ABAP select examples
BAPICDHEADO 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 Structure: Customer Settlement Header Data" 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_BAPICDHEADO TYPE BAPICDHEADO.
The BAPICDHEADO table consists of various fields, each holding specific information or linking keys about Communication Structure: Customer Settlement Header Data data available in SAP. These include PAYTYPE (Agency business: Payment type), BILL_TYPE (Agency business: Billing document type), BILL_DATE (Agency business: Posting date), BILL_TO (Bill-to party).. 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 BAPICDHEADO 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 |
| DOCUMENT_NUMBER | Agency Business: Customer Settlement | WBELN_CU | CHAR | 10 | WBRK | ALPHA | WBELN | WLF | |
| PAYTYPE | Agency business: Payment type | WRART | CHAR | 4 | TMZR | WRART | WRA | ||
| BILL_TYPE | Agency business: Billing document type | WFART | CHAR | 4 | TMFK | WFART | WFA | ||
| BILL_DATE | Agency business: Posting date | WFDAT | DATS | 8 | DATUM | ||||
| BILL_TO | Bill-to party | KUNRE | CHAR | 10 | KNA1 | ALPHA | KUNNR | KUN | |
| PAYER | Payer | KUNRG | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
| SALESORG | Sales Organization | VKORG | CHAR | 4 | TVKO | VKORG | VKO | C_VKORG | |
| DISTR_CHAN | Distribution Channel | VTWEG | CHAR | 2 | TVTW | VTWEG | VTW | C_VTWEG | |
| DIVISION | Division | SPART | CHAR | 2 | TSPA | SPART | SPA | C_SPART | |
| SALES_OFF | Sales Office | VKBUR | CHAR | 4 | TVBUR | VKBUR | VKB | ||
| SALES_GRP | Sales Group | VKGRP | CHAR | 3 | TVKGR | VKGRP | VKG | ||
| COMP_CODE | Company Code | BUKRS | CHAR | 4 | T001 | BUKRS | BUK | C_T001 | |
| ACCTSTATUS | Status for transfer to accounting | WFBSK | CHAR | 1 | WFBSK | ||||
| CURRENCY | Currency of Agency Document | WAERL | CUKY | 5 | TCURC | WAERS | FWS | ||
| CURRENCY_ISO | ISO code currency | WAERS_ISO | CHAR | 3 | ISOCD | ||||
| DOC_DATE | Document Date in Document | BLDAT | DATS | 8 | DATUM | ||||
| REF_DOC_NO | Reference Document Number | XBLNR | CHAR | 16 | XBLNR | ||||
| PAYMT_REF | Payment Reference | KIDNO | CHAR | 30 | CHAR30 | ||||
| ALLOC_NMBR | Assignment Number | DZUONR | CHAR | 18 | ZUONR | ||||
| GROSS_AMNT | Agency business: Total invoice amount | WBRTWB | DEC | 23(4) | BAPICURR | ||||
| EXCH_RATE | Direct Quoted Exchange Rate | UKURSP | DEC | 9(5) | PKURS | ||||
| EXCH_RATE_V | Indirect Quoted Exchange Rate | UKURSM | DEC | 9(5) | PKURS | ||||
| EX_RATE_FX | Indicator: Fixing of exchange rate | WKUFIX | CHAR | 1 | XFELD | ||||
| TRANS_DATE | Translation Date | WWERT_D | DATS | 8 | DATUM | ||||
| PMNTTRMS_DEB | Terms of Payment Key for Customer | WZTERMD | CHAR | 4 | ZTERM | ||||
| DSCNT1_TO_DEB | Cash Discount Period for Customer | WZBD1TD | DEC | 3 | ZBDXT | ||||
| DSCT_PCT1_DEB | Cash discount percentage 1 customer | WZBD1PD | DEC | 5(3) | PRZ23 | ||||
| DSCNT2_TO_DEB | Cash discount period 2 customer | WZBD2TD | DEC | 3 | ZBDXT | ||||
| DSCT_PCT2_DEB | Cash Discount Percentage 2 Customer | WZBD2PD | DEC | 5(3) | PRZ23 | ||||
| DSCNT3_TO_DEB | Deadline for Customer Net Condition | WZBD3TD | DEC | 3 | ZBDXT | ||||
| ADD_VAL_DY_DEB | Additional Value Days (Customer) | WVALTD | NUMC | 2 | TAGE2 | ||||
| FIX_VAL_DY_DEB | Fixed Value Date (Customer) | WVALDD | DATS | 8 | DATUM | ||||
| LOGSYSTEM | Logical System | LOGSYSTEM | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
| REF_DOC_NO_LONG | Reference Document Number (for Dependencies see Long Text) | XBLNR_LONG | CHAR | 35 | XBLNR_LONG | ||||
| PMNT_METH_DEB | Customer payment method | SCHZW_BSEGD | CHAR | 1 | Assigned to domain | ZLSCH | |||
| INV_LIST_DATE | Agency Business: Posting Date for the Remuneration List | WFDAT_RL | DATS | 8 | DATUM | ||||
| BILL_REASON | Agency business: Reason for activity | WFGRU | CHAR | 3 | Assigned to domain | WFGRU | |||
| SETTLEMENT_TYPE | Settlement Type | NAFKT | CHAR | 1 | NAFKT | ||||
| CANCELLED_DOC | Agency business: cancelled (reversed) document | LFAKS | CHAR | 10 | Assigned to domain | ALPHA | WBELN | ||
| BILL_CATEGORY | Agency business: Billing category | WFTYP | CHAR | 2 | WFTYP | ||||
| IDO_TYPE_CUST | AB: Identification Object Type Customer | WLF_IDOBJ_TYPE_CUSTOMER | CHAR | 4 | Assigned to domain | WLF_IDOBJ_TYPE_CUSTOMER | |||
| ID_OBJECT_CUST | AB: Identification Object Customer | WLF_IDOBJ_CUSTOMER | CHAR | 30 | WLF_IDOBJ | ||||
| VAT_REG_NO_V | Vendor VAT registration number | LIEFRUINR | CHAR | 20 | STCEG | ||||
| VAT_REG_NO_C | Customer VAT registration number | KUNDEUINR | CHAR | 20 | STCEG | ||||
| TAX_DEPART_CTY | Tax departure country | LANDTX | CHAR | 3 | Assigned to domain | LAND1 | LND | ||
| TAX_DEST_CTY | Tax Destination Country | LAND1TX | CHAR | 3 | Assigned to domain | LAND1 | LND | ||
| INCOTERMS1 | Incoterms (Part 1) | INCO1 | CHAR | 3 | Assigned to domain | INCO1 | |||
| INCOTERMS2 | Incoterms (Part 2) | INCO2 | CHAR | 28 | INCO2 |
| Key field | Non-key field |
How do I retrieve data from SAP structure BAPICDHEADO using ABAP code?
As BAPICDHEADO 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 BAPICDHEADO as there is no data to select.How to access SAP table BAPICDHEADO
Within an ECC or HANA version of SAP you can also view further information about BAPICDHEADO 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