BAPIBUS1600_S_POS_YEAR SAP (BAPI: Planning in New General Ledger, Item Data) Structure details
Description: BAPI: Planning in New General Ledger, Item Data
Related tables to BAPIBUS1600_S_POS_YEAR
Access table BAPIBUS1600_S_POS_YEAR
Structure field list including key, data, relationships and ABAP select examples
BAPIBUS1600_S_POS_YEAR 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 "BAPI: Planning in New General Ledger, Item 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_BAPIBUS1600_S_POS_YEAR TYPE BAPIBUS1600_S_POS_YEAR.
The BAPIBUS1600_S_POS_YEAR table consists of various fields, each holding specific information or linking keys about BAPI: Planning in New General Ledger, Item Data data available in SAP. These include CSPRED (Distribution key for currency amounts), HSLSUM (Total of transactions of the period in local currency), BASE_UOM_ISO (ISO code for unit of measurement), BASE_UOM (Base Unit of Measure).. 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 BAPIBUS1600_S_POS_YEAR 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 |
| GL_ACCOUNT | Account Number | RACCT | CHAR | 10 | Assigned to domain | ALPHA | SAKNR | ACC | |
| CSPRED | Distribution key for currency amounts | CSPRED | CHAR | 4 | Assigned to domain | SPRED | GSP | ||
| HSLSUM | Total of transactions of the period in local currency | HSLXX12 | CURR | 23(2) | WERTV12 | ||||
| BASE_UOM_ISO | ISO code for unit of measurement | ISOCD_UNIT | CHAR | 3 | Assigned to domain | ISOCD_UNIT | |||
| BASE_UOM | Base Unit of Measure | MEINS | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| QSPRED | Distribution key for quantities | QSPRED | CHAR | 4 | Assigned to domain | SPRED | GSP | ||
| MSLSUM | Total of the transactions of period in units of measure | MSLXX | QUAN | 15(3) | MENGV8 | ||||
| COSTCENTER | Cost Center | KOSTL | CHAR | 10 | Assigned to domain | ALPHA | KOSTL | KOS | |
| PROFIT_CTR | Profit Center | PRCTR | CHAR | 10 | Assigned to domain | ALPHA | PRCTR | PRC | PRCTR_EMPTY |
| FUNC_AREA | Functional Area | FKBER | CHAR | 16 | Assigned to domain | FKBER | FBE | ||
| BUS_AREA | Business Area | GSBER | CHAR | 4 | Assigned to domain | GSBER | GSB | ||
| CO_AREA | Controlling Area | KOKRS | CHAR | 4 | Assigned to domain | CACCD | CAC | ||
| SEND_CCTR | Sender cost center | SKOST | CHAR | 10 | Assigned to domain | ALPHA | KOSTL | KSK | |
| PART_PRCTR | Partner Profit Center | PPRCTR | CHAR | 10 | Assigned to domain | ALPHA | PRCTR | PPC | |
| PARTNER_FUNC_AREA | Partner Functional Area | SFKBER | CHAR | 16 | Assigned to domain | FKBER | |||
| TR_PART_BA | Trading partner's business area | PARGB | CHAR | 4 | Assigned to domain | GSBER | GSB | ||
| TRADE_ID | Company ID of trading partner | RASSC | CHAR | 6 | Assigned to domain | ALPHA | RCOMP | PGS | |
| CS_TRANS_T | Transaction Type | RMVCT | CHAR | 3 | Assigned to domain | RMVCT | |||
| SEGMENT | Segment for Segmental Reporting | FB_SEGMENT | CHAR | 10 | Assigned to domain | ALPHA | FB_SEGMENT | ||
| PARTNER_SEGMENT | Partner Segment for Segmental Reporting | FB_PSEGMENT | CHAR | 10 | Assigned to domain | ALPHA | FB_SEGMENT |
| Key field | Non-key field |
How do I retrieve data from SAP structure BAPIBUS1600_S_POS_YEAR using ABAP code?
As BAPIBUS1600_S_POS_YEAR 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 BAPIBUS1600_S_POS_YEAR as there is no data to select.How to access SAP table BAPIBUS1600_S_POS_YEAR
Within an ECC or HANA version of SAP you can also view further information about BAPIBUS1600_S_POS_YEAR 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