JBIUBSW SAP (Structure for Position Value Updates) Structure details
Description: Structure for Position Value Updates
Structure field list including key, data, relationships and ABAP select examples
JBIUBSW 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 "Structure for Position Value Updates" 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_JBIUBSW TYPE JBIUBSW.
The JBIUBSW table consists of various fields, each holding specific information or linking keys about Structure for Position Value Updates data available in SAP. These include MANDT (Client), OBJNR (Object number for financial transactions), DBSTND (Position Date), ABMENG (Position - Number of Units).. 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: Not classified
SAP JBIUBSW 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 |
| MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| OBJNR | Object number for financial transactions | JBOBJNR | CHAR | 22 | JBDOBJ1 | J_OBJNR | |||
| DBSTND | Position Date | JBDBSTND | DATS | 8 | DATUM | ||||
| ABMENG | Position - Number of Units | JBABMENG | QUAN | 13(3) | MENGE | ||||
| ABMENGV | Position - No. of Units (by Value Date) | JBABMENGV | QUAN | 13(3) | MENGE | ||||
| ABKNTK | Position - Number of Contracts | JBABKNTK | NUMC | 6 | NUMC6 | ||||
| ABKNTKV | Position - Number of Contracts | JBABKNTK | NUMC | 6 | NUMC6 | ||||
| BBBETR | Position - Nominal Amount | JBBBBETR | CURR | 17(2) | WERTV9 | ||||
| BBBETRV | Position - Nominal Amount (Value Date) | JBBBBETRV | CURR | 17(2) | WERTV9 | ||||
| BPGLDKU | Floating Average Price - Securities Price | JBBPGLDKU | DEC | 15(6) | VVPKTKUR | ||||
| KGLDKU | Floating Average Exchange Rate | JBKGLDKU | DEC | 9(5) | EXCRT | KURSF | |||
| NGLDKU | Floating Average - Index | JBNGLDKU | DEC | 8(3) | DEC5_3 | ||||
| BGLDKU | Floating Average Price - Amount | JBBGLDKU | CURR | 17(2) | WERTV9 | ||||
| EGLDKU | Floating Average - Effective Interest Rate | JBEGLDKU | DEC | 10(5) | JBIZINSS | ||||
| BBWHR | Acquisition Value in Position Currency | JBANSCHBW | CURR | 17(2) | WERTV9 | ||||
| BHWHR | SAP Banking: Aquisition Value in Local Currency | JBANSCHHW | CURR | 17(2) | WERTV9 | ||||
| BPWKURS | Floating Average Price - Securities Price | JBBPGLDKU | DEC | 15(6) | VVPKTKUR | ||||
| DEVKURS | Floating Average Exchange Rate | JBKGLDKU | DEC | 9(5) | EXCRT | KURSF | |||
| MODE | Mode of Data Flow | JBSMODE | CHAR | 1 | JBSMODE |
| Key field | Non-key field |
How do I retrieve data from SAP structure JBIUBSW using ABAP code?
As JBIUBSW 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 JBIUBSW as there is no data to select.How to access SAP table JBIUBSW
Within an ECC or HANA version of SAP you can also view further information about JBIUBSW 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