COO_LSTAR SAP (CO obj. planning: structure master data info table, act. typ) Structure details
Description: CO obj. planning: structure master data info table, act. typ
Structure field list including key, data, relationships and ABAP select examples
COO_LSTAR 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 "CO obj. planning: structure master data info table, act. typ" 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_COO_LSTAR TYPE COO_LSTAR.
The COO_LSTAR table consists of various fields, each holding specific information or linking keys about CO obj. planning: structure master data info table, act. typ data available in SAP. These include LSTAR (Activity Type), DATBI (Valid To Date), BUPER (Posting period), GJAHR (Fiscal Year).. 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 COO_LSTAR 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 |
| LSTAR | Activity Type | LSTAR | CHAR | 6 | Assigned to domain | LSTAR | LAR | LART_EMPTY | |
| DATBI | Valid To Date | DATBI | DATS | 8 | DATUM | ||||
| BUPER | Posting period | POPER | NUMC | 3 | POPER | POPR | |||
| GJAHR | Fiscal Year | GJAHR | NUMC | 4 | GJAHR | GJAHR | GJR | ||
| DATAB | Valid-From Date | DATAB | DATS | 8 | DATUM | ||||
| LEINH | Activity Unit | LEINH | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| KSTTY | Valid Cost Center Categories | KSTTY | CHAR | 8 | KSTTY | ||||
| VKSTA | Allocation Cost Element | VKSTA | CHAR | 10 | Assigned to domain | ALPHA | KSTAR | ||
| LATYP | Activity Type Category | LATYP | CHAR | 1 | LATYP | ||||
| AUSFK | Output factor | AUSFK | DEC | 5(2) | AUSFK | ||||
| AUSEH | Output Unit | AUSEH | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| TARKZ | Price Indicator: Calculate Allocation Price | TARKZ | CHAR | 3 | Assigned to domain | ALPHA | TARKZ | ||
| YRATE | Price Calculation with Period-Based Average Prices | CO_YRATE | CHAR | 1 | XFELD | ||||
| TARKZ_I | Indicator: Actual Allocation Price | CO_TARKZ_I | CHAR | 3 | Assigned to domain | ALPHA | TARKZ | ||
| LATYPI | Variant Activity Type Category for Actual Postings | LATYPI | CHAR | 1 | LATYPI |
| Key field | Non-key field |
How do I retrieve data from SAP structure COO_LSTAR using ABAP code?
As COO_LSTAR 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 COO_LSTAR as there is no data to select.How to access SAP table COO_LSTAR
Within an ECC or HANA version of SAP you can also view further information about COO_LSTAR 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