BAPISLHC SAP (Communication Structure: Settlement List Header Data) Structure details
Description: Communication Structure: Settlement List Header Data
Structure field list including key, data, relationships and ABAP select examples
BAPISLHC 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: Settlement 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_BAPISLHC TYPE BAPISLHC.
The BAPISLHC table consists of various fields, each holding specific information or linking keys about Communication Structure: Settlement List Header Data data available in SAP. These include CURRENCY (Currency of Agency Document), CURRENCY_ISO (ISO code currency), DOC_DATE (Document Date in Document), REF_DOC_NO (Reference Document Number).. 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 BAPISLHC 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 |
| BILL_DATE | Agency business: Posting date | WFDAT | DATS | 8 | DATUM | ||||
| 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 | Terms of Payment Key | DZTERM | CHAR | 4 | ZTERM | ||||
| DSCNT1_TO | Cash (Prompt Payment) Discount Days | DZBDET | DEC | 3 | ZBDXT | ||||
| DSCT_PCT1 | Cash Discount Percentage 1 | DZBD1P | DEC | 5(3) | PRZ23 | ||||
| DSCNT2_TO | Cash discount days 2 | DZBD2T | DEC | 3 | ZBDXT | ||||
| DSCT_PCT2 | Cash Discount Percentage 2 | DZBD2P | DEC | 5(3) | PRZ23 | ||||
| DSCNT3_TO | Net Payment Terms Period | DZBD3T | DEC | 3 | ZBDXT | ||||
| ADD_VAL_DY | Additional value days | VALTG | NUMC | 2 | TAGE2 | ||||
| FIX_VAL_DY | Fixed value date | VALDT | 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 | ||||
| BILL_REASON | Agency business: Reason for activity | WFGRU | CHAR | 3 | TMLFG | WFGRU | |||
| ALT_PAYEE | Account number of the alternative payee | LNRZB | CHAR | 10 | LFA1 | ALPHA | LIFNR | ||
| INCOMP_REASON | Incompleteness Reason | WLF_INCOMPLETENESS_REASON | CHAR | 4 | TWLF_IR | WLF_INCOMPLETENESS_REASON | |||
| APPL_STATUS | Agency business: Application status | WSTATE | CHAR | 4 | TMPA2 | WSTATE | |||
| 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 BAPISLHC using ABAP code?
As BAPISLHC 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 BAPISLHC as there is no data to select.How to access SAP table BAPISLHC
Within an ECC or HANA version of SAP you can also view further information about BAPISLHC 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