/ASU/SSMTREES SAP (ASU Simple Schedule Manager: Internal Structure for ALV-Tree) Structure details
Description: ASU Simple Schedule Manager: Internal Structure for ALV-Tree
Related tables to /ASU/SSMTREES
Access table /ASU/SSMTREES
Structure field list including key, data, relationships and ABAP select examples
/ASU/SSMTREES 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 "ASU Simple Schedule Manager: Internal Structure for ALV-Tree" 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_/ASU/SSMTREES TYPE /ASU/SSMTREES.
The /ASU/SSMTREES table consists of various fields, each holding specific information or linking keys about ASU Simple Schedule Manager: Internal Structure for ALV-Tree data available in SAP. These include NODE_ID (Node ID), PARENT_ID (Node ID), NSIBLING_ID (Node ID), MANDT (Client).. 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 /ASU/SSMTREES 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 |
| NODE_ID | Node ID | SCMA_NODE | CHAR | 12 | SCMA_NODE | ||||
| PARENT_ID | Node ID | SCMA_NODE | CHAR | 12 | SCMA_NODE | ||||
| NSIBLING_ID | Node ID | SCMA_NODE | CHAR | 12 | SCMA_NODE | ||||
| MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| TASKLIST | Schedule Manager: Task List | PEPPROFILE | CHAR | 10 | /ASU/TSSM | PEPPROFILE | SCMAPROFILE | H_PEPPROFILE | |
| ID | ASU - General ID f.g. sequence number | /ASU/ID | CHAR | 12 | CHAR12 | ||||
| SCENARIO | ASU: Scenario | /ASU/SCENARIO | CHAR | 20 | TEXT20 | ||||
| VERSION | ASU: Content Version /Date+Time/ | /ASU/VERSION | CHAR | 14 | CHAR14 | ||||
| GUID | GUID in 'CHAR' Format in Uppercase | GUID_32 | CHAR | 32 | /ASU/CONTENT | SYSUUID_C | |||
| EXEC_VARIANT | Report Variant | SCMATASK_VAR | CHAR | 40 | SCMATASK_VAR | ||||
| UACC_STEP_NAME | Step Name | UACC_STEP_NAME | CHAR | 50 | UACC_STEP_NAME | UACC_STEP_NAME | |||
| UACC_USE_CASE | Use case of Check -- 'UPG', 'SPAM', 'ASU' etc.. | UACC_USE_CASE | CHAR | 30 | UACC_USE_CASE | UACC_USECASE | |||
| RELATIONKEY | GUID in 'CHAR' Format in Uppercase | GUID_32 | CHAR | 32 | SYSUUID_C | ||||
| TEXT | Text for a Task in the Schedule Manager | SCMATEXT | CHAR | 60 | TEXT60 | ||||
| SCMA_REPORT_ID | Job ID | BTCJOBCNT | CHAR | 8 | CHAR8 | ||||
| SCMA_REPORT_NAME | Background job name | BTCJOB | CHAR | 32 | CHAR32 | ||||
| LAST_RUN | Schedule Manager: Date and time of the last run | SCMALAST_RUN | CHAR | 17 | CHAR17 | ||||
| START_DATE | Task Start Date | SCMA_START_DATE | DATS | 8 | DATE | ||||
| TASK_ICON | Schedule Manager: Task type (report, flow) | SCMA_TASK_TYPE | CHAR | 4 | SCMA_TASK_TYPE | ||||
| RTA_NEXT_RUN | Schedule Manager: Next Expected Runtime | SCMA_RTA_NEXT | CHAR | 17 | CHAR17 | ||||
| RTA_CUST_RUN | Schedule Manager: Estimated Runtime (Customer) | SCMA_RTA_CUST | CHAR | 17 | CHAR17 | ||||
| RTA_AVE_RUN | Schedule Manager: Average Runtime | SCMA_RTA_AVE | CHAR | 17 | CHAR17 |
| Key field | Non-key field |
How do I retrieve data from SAP structure /ASU/SSMTREES using ABAP code?
As /ASU/SSMTREES 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 /ASU/SSMTREES as there is no data to select.How to access SAP table /ASU/SSMTREES
Within an ECC or HANA version of SAP you can also view further information about /ASU/SSMTREES 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