Hierarchy
EA-PS (Software Component) SAP Enterprise Extension Public Services⤷
PSM-FM-MD (Application Component) Master Data⤷
FMCC (Package) FIFM: Cash budget management customizing
IMG Activity
| ID | SIMG_ISPSDEOFRA | Create/Change Report Selection |
| Transaction Code | S_KI4_55000055 | IMG Activity: SIMG_ISPSDEOFRA |
| Created on | 19991215 | |
| Customizing Attributes | SIMG_ISPSDEOFRA | Create/Change Report Selection |
| Customizing Activity | SIMG_ISPSDEOFRA | Create/Change Report Selection |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_ISPSDEOFRA |
In the following work steps you define,
- if you use the reporting trees delivered by SAP or one of your own
- how every individual reporting tree is structured
- which reports are contained in a reporting tree
The reporting tree serves to to collect all reports for an application centrally and to structure them hierarchically.
Standard settings
Reporting trees are supplied by SAP for the following areas:
Reporting tree name area
FMCA standard reports
FMKO report selection (local authorities)
Recommendation
For a better overview, SAP recommends that you create your own nodes for every application area in the reporting tree. The more nodes and hierarchies exist, the better the overview of the report selection for the user.
Activities
- Check the reporting tree contained in the SAP standard delivery.
- If required extend the supplied reporting trees.
- If required define additional reporting trees.
Transporting the tree structure
When changing a tree the tree is included in an order (Transport obbject R3TR SRTR). This transports:
- Tree structure with texts
- Node entries (Name of the program and variants)
Those not automatically transported include:
- User-specific settings (initial screens, partial trees, visible entries)
- saved lists
When changing a node the node is included in an order. This transports:
- node entries (name of the program and variants)
Manual transport (for exceptional situations)
The tree structure is stored in the table SERPTREE. A tree structure can only be transported completely. The following entry has to be made in the transport order:
- R3TR TABU SERPTREE and SERPT, Function R transports all trees from the source system and overwrites them in the target system.
- R3TR TABU SERPTREE und SERPT, Funktion K transpors exactly the trees, for which the ID is specified in the following screen. Here you again specify R as the function. You can only specify the tree ID, the node ID must be specified generically.
If a tree structure is to be overwritten in the target system then the node contents (table SREPOVARI, see below) and the user-specific views (tables SERPENTR and SREPOUSER, see below) should also be transported or at least deleted in the target system.
Transport of the node contents
The node contents (programs and variants) are stored in the table
SREPOVARI. The following entry has to be carried out in the transport order:
- R3TR TABU SREPOVARI, Function R transports the contents of all nodes of all trees from the source system and overwrites them in the target system.
- R3TR TABU SREPOVARI, Function K transports exactly the node contents which are specified in the following screen. Here you specify R as the function.
If a node is to be overwritten in the target system then the user- specific views of this node (table SREPOUSER, see below) should likewise be transported or at least deleted in the target system.
Transport of the user-specific views
The views to the Reporting tree are stored in the table SERPENTR. The following entry has to be carried out in the transport order:
- R3TR TABU SERPENTR, Function R transports the viewschten aller Benutzer auf alle Bäume aus dem Quellsystem und überschreibt die im Zielsystem.
- R3TR TABU SERPENTR, Funktion K transportiert genau die Sichten, die im Folgebild spezifiziert sind. Hier ist als Funktion wieder R anzugeben.
Die Sichten auf die Knoten sind in der Tabelle SREPOUSER gespeichert. Folgender Eintrag ist im Transportauftrag vorzunehmen:
- R3TR TABU SREPOUSER, Funktion R transportiert die Sichten aller Benutzer auf alle Knoten aus dem Quellsystem und überschreibt die im Zielsystem.
- R3TR TABU SREPOUSER, Funktion K transportiert genau die Sichten, die im Folgebild spezifiziert sind. Hier ist als Funktion wieder R anzugeben.
Weitere Informationen zum Berichtsbaum finden Sie beim Aufruf der Berichtsauswahl über Hilfsmittel -> Online Handbuch.
Business Attributes
| ASAP Roadmap ID | 207 | Establish Reporting |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_ISPSDEOFRA | 0 | I150004908 | Information system |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| OFRA | T - Individual transaction object | OFRA | ISPSDEBBST | Report Tree | ||
| OFRK | T - Individual transaction object | OFRK | ISPSDEBBKO | Local authorities Report Tree |
History
| Last changed by/on | SAP | 19991215 |
| SAP Release Created in |
