E1BPILHEADO SAP (Communication Structure: Remuneration List Header Data) IDoc segment structure details
Dictionary Type: IDoc segment structure
Description: Communication Structure: Remuneration List Header Data
Description: Communication Structure: Remuneration List Header Data
IDoc segment structure field list including key, data, relationships and ABAP select examples
E1BPILHEADO is a standard SAP Structure which is used to define the field attributes of IDoc segment E1BPILHEADO. The segment is used within the below IDoc to send Communication Structure: Remuneration List Header Data information via the IDoc send process
REMUNREQUESTLIST_GETLIST01REMUNREQUESTLIST_GETLIST02
REMURQSLIST_CHANGE01
REMURQSLIST_CREATE_CBD01
REMURQSLIST_CREATE_CBD02
REMURQSLIST_CREATE_REMU01
REMURQSLIST_CREATE_REMU02
REMURQSLIST_CREATE_SETT01
REMURQSLIST_CREATE_SETT02
REMURQSLIST_GETDETAIL0101
REMURQSLIST_GETDETAIL0201
REMURQSLIST_GETDETAILA01
REMURQSLIST_GETDETAILA02
REMURQSLIST_GETDETAILB01
REMURQSLIST_GETDETAILC01
REMURQSLIST_GETDETAILD01
REMURQSLIST_GETDETAILG01
REMURQSLIST_GETDETAILH01
REMURQSLIST_GETDETAILK01
REMURQSLIST_GETDETAILK02
REMURQSLIST_GETDETAILL01
REMURQSLIST_RELEASE01
REMURQSLIST_RELEASE02
Below is the standard documentation available and a few details of the fields which make up this IDoc segment structure. To view further details checkout the IDoc links above or use relevant transactions such as WE30(IDoc development), WE31 (segment development)...Also check here for more IDoc related development help, or you can obviously also use standard dictionary object dev tcodes such as SE11, SE80 etc...
Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Cannot Be Enhanced
SAP E1BPILHEADO idoc segment 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 | 0 | ||||||||
| BILL_TYPE | 0 | ||||||||
| BILL_DATE | 0 | ||||||||
| DIFF_INV | 0 | ||||||||
| PURCH_ORG | 0 | ||||||||
| PUR_GROUP | 0 | ||||||||
| COMP_CODE | 0 | ||||||||
| ACCTSTATUS | 0 | ||||||||
| CURRENCY | 0 | ||||||||
| CURRENCY_ISO | 0 | ||||||||
| DOC_DATE | 0 | ||||||||
| REF_DOC_NO | 0 | ||||||||
| PAYMT_REF | 0 | ||||||||
| ALLOC_NMBR | 0 | ||||||||
| FINAL_AMNT | 0 | ||||||||
| EXCH_RATE | 0 | ||||||||
| EXCH_RATE_V | 0 | ||||||||
| EX_RATE_FX | 0 | ||||||||
| TRANS_DATE | 0 | ||||||||
| PMNTTRMS | 0 | ||||||||
| DSCNT1_TO | 0 | ||||||||
| DSCT_PCT1 | 0 | ||||||||
| DSCNT2_TO | 0 | ||||||||
| DSCT_PCT2 | 0 | ||||||||
| DSCNT3_TO | 0 | ||||||||
| ADD_VAL_DY | 0 | ||||||||
| FIX_VAL_DY | 0 | ||||||||
| BILL_TO | 0 | ||||||||
| SALESORG | 0 | ||||||||
| DISTR_CHAN | 0 | ||||||||
| DIVISION | 0 | ||||||||
| PMNTTRMS_DEB | 0 | ||||||||
| DSCNT1_TO_DEB | 0 | ||||||||
| DSCT_PCT1_DEB | 0 | ||||||||
| DSCNT2_TO_DEB | 0 | ||||||||
| DSCT_PCT2_DEB | 0 | ||||||||
| DSCNT3_TO_DEB | 0 | ||||||||
| PMNT_METH_DEB | 0 | ||||||||
| ADD_VAL_DY_DEB | 0 | ||||||||
| FIX_VAL_DY_DEB | 0 | ||||||||
| PYMT_METH | 0 | ||||||||
| REF_DOC_NO_LONG | 0 | ||||||||
| CANCELLED_DOC | 0 | ||||||||
| SETTLEMENT_TYPE | 0 | ||||||||
| BILL_CATEGORY | 0 | ||||||||
| INV_LIST_DATE | 0 | ||||||||
| BILL_REASON | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure E1BPILHEADO using ABAP code?
As E1BPILHEADO 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 E1BPILHEADO as there is no data to select.How to access SAP table E1BPILHEADO
Within an ECC or HANA version of SAP you can also view further information about E1BPILHEADO 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