BAPIPLHC SAP (Communication Structure: Change Posting List Header Data) Structure details
Description: Communication Structure: Change Posting List Header Data
Structure field list including key, data, relationships and ABAP select examples
BAPIPLHC 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: Change Posting List 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_BAPIPLHC TYPE BAPIPLHC.
The BAPIPLHC table consists of various fields, each holding specific information or linking keys about Communication Structure: Change Posting List Header Data data available in SAP. These include BILL_DATE (Agency business: Posting date), DOC_DATE (Document Date in Document), REF_DOC_NO (Reference Document Number), PAYMT_REF (Payment Reference).. 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 BAPIPLHC 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 | Settlement request: Posting list | WBELN_RB | CHAR | 10 | Assigned to domain | ALPHA | WBELN | WBL | |
| BILL_DATE | Agency business: Posting date | WFDAT | DATS | 8 | DATUM | ||||
| 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 | ||||
| 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 | ||||
| PMNT_METH_DEB | Customer payment method | SCHZW_BSEGD | CHAR | 1 | Assigned to domain | ZLSCH | |||
| ADD_VAL_DY_DEB | Additional Value Days (Customer) | WVALTD | NUMC | 2 | TAGE2 | ||||
| FIX_VAL_DY_DEB | Fixed Value Date (Customer) | WVALDD | DATS | 8 | DATUM | ||||
| TESTRUN | Switch to Simulation Session for Write BAPIs | TESTRUN | CHAR | 1 | BAPIFLAG | ||||
| REF_DOC_NO_LONG | Reference Document Number (for Dependencies see Long Text) | XBLNR_LONG | CHAR | 35 | XBLNR_LONG | ||||
| PAYER | Payer | KUNRG | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
| BILL_REASON | Agency business: Reason for activity | WFGRU | CHAR | 3 | TMLFG | WFGRU |
| Key field | Non-key field |
How do I retrieve data from SAP structure BAPIPLHC using ABAP code?
As BAPIPLHC 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 BAPIPLHC as there is no data to select.How to access SAP table BAPIPLHC
Within an ECC or HANA version of SAP you can also view further information about BAPIPLHC 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