Hierarchy

⤷

⤷

⤷

IMG Activity
ID | OKCM_OKXR | Maintain report selection |
Transaction Code | S_ALR_87000192 | IMG Activity: OKCM_OKXR |
Created on | 19981222 | |
Customizing Attributes | OKCM_OKXR | Maintain report selection |
Customizing Activity | OKCM_OKXR | Maintain report selection |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | OKCM_OKXR |
For EC-EIS you have to maintain the report tree 'EIS'.
Here, you specify the name of the tree to be used for report selection in the application menu. SAP supplies one default tree per application, but customers can create their own trees and overwrite the SAP tree.
Under Extras -> Control, you can define whether the reports in the tree are to be displayed in a selection window or on a separate screen. To suppress the processing of report trees for the relevant application by choosing Inactive. When you call report selection in the application menu, the list selected in the report list is then displayed.
It is also possible to deactivate the report tree for any end-user in any application by setting the user parameter 'KBT' to 'X'.
Transporting the Tree Sructure
When you change a tree, it is included in a transport request (transport object R3TR SRTR). The following are then transported:
- The tree structure all the texts
- Node entries (the names of the reports and variants)
The following are not automatically transported:
- User-specific settings (initial position, sub.trees, visible entries)
- Saved lists
When you change a node, it is also included in a transport request. The following are then transported:
- Node entries (the names of the reports and variants)
Manual Transport (for Special Cases)
The tree structure is stored in the table SERPTREE. A tree structure can only be transported as a whole, and the transport request should contain the following entry:
- R3TR TABU SERPTREE and SERPT. Function R transports all trees from the source system and overwrites those in the target system.
- R3TR TABU SERPTREE und SERPT. Function K transports only those trees specified on the next screen. You must enter function R. You can only specify the tree ID; the node ID must be specified generically.
If you want to overwrite a tree structure in the target system, the node contents (table SREPOVARI, see below) and the user-specific views (table SERPENTR and SREPOUSER, see below) should also be transported, or at least deleted in the target system.
Transporting Node Contents
The contents of report tree nodes (reports and variants) are stored in the table SREPOVARI. In this case, you should make the following entry in the transport request:
- R3TR TABU SREPOVARI. Function R transports the contents of all nodes of all trees from the source system and overwrites those in the target system.
- R3TR TABU SREPOVARI. Function K transports only the node contents specified in the next screen. You enter function R here.
If you want to overwrite a node in the target system, the user-specific views (table SREPOUSER, see below) should also be transported, or at least deleted in the target system.
Transporting User-Specific Views
The views of the report tree are stored in the table SERPENTR. You must make the following entry in the transport request:
- R3TR TABU SERPENTR. Function R transports the views of all users of all trees from the source system and overwrites those in the target system.
- R3TR TABU SERPENTR. Function K transports only those views specified on the next screen. You enter function R here.
The views of the nodes are stored in the table SREPOUSER. You must make the following entry in the transport request:
- R3TR TABU SREPOUSER. Function R transports the view of all users of all nodes from the source system and overwrites those in the target system.
- R3TR TABU SREPOUSER. Function K transports only those views specified on the next screen. You enter function R here.
Example
Requirements
Standard settings
Recommendation
Activities
Further notes
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 | OKCM_OKXR | 0 | HLA0009493 | Interactive Drilldown Reporting |
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 |
OKXR | T - Individual transaction object | OKXR | EIS | Report tree |
History
Last changed by/on | SAP | 19981222 |
SAP Release Created in |