COO_LSTARK SAP (CO Object Planning: Master Data Info - Acty Type Key) Structure details
Description: CO Object Planning: Master Data Info - Acty Type Key
Structure field list including key, data, relationships and ABAP select examples
COO_LSTARK 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 Object Planning: Master Data Info - Acty Type Key" 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_LSTARK TYPE COO_LSTARK.
The COO_LSTARK table consists of various fields, each holding specific information or linking keys about CO Object Planning: Master Data Info - Acty Type Key data available in SAP. These include DATBI (Valid To Date), BUPER (Posting period), GJAHR (Fiscal Year), DATAB (Valid-From 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: Not classified
SAP COO_LSTARK 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 |
| Key field | Non-key field |
How do I retrieve data from SAP structure COO_LSTARK using ABAP code?
As COO_LSTARK 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_LSTARK as there is no data to select.How to access SAP table COO_LSTARK
Within an ECC or HANA version of SAP you can also view further information about COO_LSTARK 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