BNK_BTC_ITEM_UI SAP (Batch Payment Item (for UI)) Structure details
Dictionary Type: Structure
Description: Batch Payment Item (for UI)
Description: Batch Payment Item (for UI)
ABAP Code to SELECT data from BNK_BTC_ITEM_UI
Related tables to BNK_BTC_ITEM_UI
Access table BNK_BTC_ITEM_UI
Related tables to BNK_BTC_ITEM_UI
Access table BNK_BTC_ITEM_UI
Structure field list including key, data, relationships and ABAP select examples
BNK_BTC_ITEM_UI 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 "Batch Payment Item (for UI)" 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_BNK_BTC_ITEM_UI TYPE BNK_BTC_ITEM_UI.
The BNK_BTC_ITEM_UI table consists of various fields, each holding specific information or linking keys about Batch Payment Item (for UI) data available in SAP. These include BATCH_NO (Batch Identification Number), LAUFD_O (Date on Which the Program Is to Be Run), LAUFI_O (Additional Identification), STATUS_ID (Status ID).. 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 BNK_BTC_ITEM_UI 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 |
| ITEM_NO | Item Count Number | BNK_COM_BTCH_CNT | NUMC | 5 | BNK_COM_CTR | ||||
| BATCH_NO | Batch Identification Number | BNK_COM_BTCH_NO | NUMC | 10 | BNK_COM_BATCH_NO | ||||
| LAUFD_O | Date on Which the Program Is to Be Run | LAUFD | DATS | 8 | DATUM | ||||
| LAUFI_O | Additional Identification | LAUFI | CHAR | 6 | LAUFI | ||||
| STATUS_ID | Status ID | BNK_COM_STATUS_ID | CHAR | 5 | TEXT5 | ||||
| STATUS_TXT | Object status | J_TXT30 | CHAR | 30 | TEXT30 | ||||
| ZBUKR | Paying company code | DZBUKR | CHAR | 4 | Assigned to domain | BUKRS | |||
| BUTXT | Name of Company Code or Company | BUTXT | CHAR | 25 | TEXT25 | ||||
| LIFNR | Account Number of Vendor or Creditor | LIFNR | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LIF | KRED_C |
| KUNNR | Customer Numbers | KUNNR | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | KUN | C_KUNNR |
| EMPFG | Payee code | EMPFG | CHAR | 16 | EMPFG | ||||
| VBLNR | Document Number of the Payment Document | VBLNR | CHAR | 10 | ALPHA | BELNR | |||
| GJAHR | Fiscal Year | GJAHR | NUMC | 4 | GJAHR | GJAHR | GJR | ||
| ZALDT | Posting date of the payment document | DZALDT_ZHL | DATS | 8 | DATUM | ||||
| LAUFD_M | Merge Date | BNK_COM_BTCH_MRGE_DAT | DATS | 8 | DATUM | ||||
| LAUFI_M | Merge Id | BNK_COM_BTCH_MRGE_ID | CHAR | 6 | LAUFI | ||||
| DORIGIN | Grouping Origin | FIBL_DORIGIN | CHAR | 8 | Assigned to domain | FIBL_ORIGIN | |||
| PAYGR | Grouping Field for Automatic Payments | PAYGR | CHAR | 20 | CHAR20 | ||||
| AUSFD | Due date of the paid items | AUSFD | DATS | 8 | DATUM | ||||
| RZAWE | Payment Method for This Payment | RZAWE | CHAR | 1 | Assigned to domain | ZLSCH | |||
| ZNME1 | Name of the payee | DZNME1 | CHAR | 35 | TEXT35 | ||||
| ZBNKS | Country Key | DZBNKS | CHAR | 3 | Assigned to domain | LAND1 | LND | ||
| ZBNKN | Bank Account Number of the Payee | DZBNKN35 | CHAR | 35 | BANKN35 | ||||
| ZBNKL | Bank number of the payee's bank | DZBNKL | CHAR | 15 | BANKL | ||||
| ZSWIF | SWIFT/BIC for International Payments | SWIFT | CHAR | 11 | SWIFT | ||||
| ZIBAN | IBAN of the Payee | DZIBAN | CHAR | 34 | IBAN | ||||
| HKTID | ID for account details | HKTID | CHAR | 5 | Assigned to domain | HKTID | |||
| HBKID | Short Key for a House Bank | HBKID | CHAR | 5 | Assigned to domain | HBKID | |||
| UBNKS | Bank country key | BANKS | CHAR | 3 | Assigned to domain | LAND1 | BKL | ||
| UBNKL | Bank number of our bank | UBNKL | CHAR | 15 | BANKL | ||||
| RWBTR | Amount to be paid | BNK_COM_RWBTR | CURR | 13(2) | WRTV7 | ||||
| WAERS | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
| RBETR | Amount to be paid in local currency | BNK_COM_RBETR | CURR | 13(2) | WRTV7 | ||||
| HWAER | Local Currency | HWAER | CUKY | 5 | Assigned to domain | WAERS | |||
| AMT_RULECU | Payment amount in rule currency | BNK_COM_PYMNTAMT_IN_RULCU | CURR | 13(2) | WRTV7 | ||||
| RULE_CURR | Rule Currency | BNK_COM_RULE_CURR | CUKY | 5 | Assigned to domain | WAERS | |||
| URGENT | Urgent Payment | DTURG | CHAR | 1 | XFELD | ||||
| DTKVS | Cost Allocation Key | BNK_COM_COSTALLOC | CHAR | 2 | CHAR2 | ||||
| DTAWS | Instruction key for data medium exchange | DTAWS | CHAR | 2 | Assigned to domain | DTAWS | |||
| OLD_BTCNO | Previous Batch Identification Number | BNK_COM_OLD_BTCNO | NUMC | 10 | BNK_COM_BATCH_NO | ||||
| WDATE | Bill of Exchange Issue Date | WDATE | DATS | 8 | DATUM | ||||
| WEFAE | Bill of Exchange Due Date | WEFAE | DATS | 8 | DATUM |
| Key field | Non-key field |
How do I retrieve data from SAP structure BNK_BTC_ITEM_UI using ABAP code?
As BNK_BTC_ITEM_UI 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 BNK_BTC_ITEM_UI as there is no data to select.How to access SAP table BNK_BTC_ITEM_UI
Within an ECC or HANA version of SAP you can also view further information about BNK_BTC_ITEM_UI 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