TBS_PROTOCOL_BUSINESS_TRANS SAP (Treasury: Interface Posting Log : Business Operation) Structure details
Description: Treasury: Interface Posting Log : Business Operation
Related tables to TBS_PROTOCOL_BUSINESS_TRANS
Access table TBS_PROTOCOL_BUSINESS_TRANS
Structure field list including key, data, relationships and ABAP select examples
TBS_PROTOCOL_BUSINESS_TRANS 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 "Treasury: Interface Posting Log : Business Operation" 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_TBS_PROTOCOL_BUSINESS_TRANS TYPE TBS_PROTOCOL_BUSINESS_TRANS.
The TBS_PROTOCOL_BUSINESS_TRANS table consists of various fields, each holding specific information or linking keys about Treasury: Interface Posting Log : Business Operation data available in SAP. These include XNAME (Name), SBUSINESS_TRANS_CATEGORY (Treasury: Posting log: Business operation category), PRIMANOTA (Daybook no.), KEYDATE (Position value date).. 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 (Deep)
SAP TBS_PROTOCOL_BUSINESS_TRANS 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 |
| COMPANY_CODE | Company Code | BUKRS | CHAR | 4 | Assigned to domain | BUKRS | BUK | C_T001 | |
| XNAME | Name | XLBEZ | CHAR | 50 | XTEXT50 | ||||
| SBUSINESS_TRANS_CATEGORY | Treasury: Posting log: Business operation category | TB_BUSINESS_TRANS_CATEGORY | CHAR | 3 | TB_BUSINESS_TRANS_CATEGORY | ||||
| PRIMANOTA | Daybook no. | VVRPNNR | CHAR | 10 | VVRPNNR | ||||
| KEYDATE | Position value date | DBESTAND | DATS | 8 | DATUM | ||||
| SEC_CORPACTIONNUMBER | Corporate Action Number | KMNR | CHAR | 13 | Assigned to domain | ALPHA | VKMNR | KMA | |
| SEC_CORPACTIONTEXT | Short text/description of the object | KURZTEXT | CHAR | 40 | TEXT40 | ||||
| SEC_CORPACTIONTYPETEXT | Corporate action type text | XKMART | CHAR | 30 | TEXT30 | ||||
| SEC_RIGHTTYPETEXT | Text for rights category | TER_RIGHTTYPE_T | CHAR | 30 | CHAR30 | ||||
| TRANSACTION_ITEMS | 0 | ||||||||
| MESSAGES | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure TBS_PROTOCOL_BUSINESS_TRANS using ABAP code?
As TBS_PROTOCOL_BUSINESS_TRANS 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 TBS_PROTOCOL_BUSINESS_TRANS as there is no data to select.How to access SAP table TBS_PROTOCOL_BUSINESS_TRANS
Within an ECC or HANA version of SAP you can also view further information about TBS_PROTOCOL_BUSINESS_TRANS 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