Ansicht
Dokumentation
CRMV_IPM_RTREE - Assign Generic Tree Profile to Rights Maintenance Usage
CL_GUI_FRONTEND_SERVICES - Frontend Services BAL_S_LOG - Application Log: Log header dataThis documentation is copyright by SAP AG.
In this Customizing activity, you can change the way the generic tree is displayed for specific usages in IPM applications using a generic tree profile. A profile specifies the attributes to be displayed in the tree hierarchy. Customizing settings override the default profile. Profiles are maintained in the separate Customizing activity: Define Object Hierarchy and Object Attributes.
There are a number of changes you can make to the way a generic tree is displayed. These are listed below. Before making any changes, in all cases:
1.,,Either create a new profile or copy an existing one.
2.,,Assign the new profile to a usage
For more information, see the Customizing activity Define Object Hierarchy and Object Attributes.
- Change the presentation ID (default labels of nodes)
The delivered SAP tree profile has predefined presentations to display the attributes of business objects. You may wish to create new presentation to display a different set of attributes. For example, a delivered object may display a product ID and description only. You can add the date of the product in your new presentation.
- Change the way that the cells are displayed (HTML coding in method RENDER_CELL)
To deliver more complex user interface (UI) elements without the need to re-create the complete UI, you can use the RENDER cell. You can include bold text or include a dropdown list box.
- Add nodes based on the business object model
The nodes of the delivered profiles define the hierarchy of the data to display for a specific tree. You can add additional levels in the tree hierarchy based on the model of the business object.
- Trigger external functions when the cells are rendered
You can extend the functions of the tree through additional ABAP coding. This is similar to using the RENDER_CELL method or a Business Add-In.
- Change dynamically the content of the cells
You can change the content of a cell dynamically in the implementation class defined for a node.
- Change the column names / add more columns
In the Customizing activity for the object hierarchy, you can change column names or add more columns to a profile. The new columns are displayed in the presentation IDs.
You may want to change the behavior for a specific usage of the generic tree. For simple changes, you can change the way a specific tree appears in the user interface without additional coding. More complex changes may require additional coding.
The standard system does not contain any entries.
To change the assignment of a tree profile:
- Prepare the tree profile you want to use in Customizing activity Define Object Hierarchy and Object Attributes.
- Add a new entry (or change an existing one) for one specific usage of the application name and the usage ID.
- Assign a profile for this usage.
The system delivers all the standard usages for Customizing. To create your own usage and assign a profile to it, create an entry in database table CRMC_IPM_PRF_USG. The new entry is displayed in this Customizing node. The text table for the usage is CRMC_IPM_PRF_UST.
Note:
The generic tree display always depends on the business
object model. If you try to display nodes or attributes that do not exist, there may inconsistent behavior or it may cause a system dump.
Available usages where the generic tree display can be modified
You can change how the generic tree is displayed for the following usage profiles:
Contract management
Profile: ADVANCE (Advance group (IPMAdvGrp)
Default Profile: IPM_RTBASE
Location in UI: Create a sales contract; assign an IP; add an advance group
Profile: CUNORASSIGNEDCONTRACTS (Assigned Rights (IPMCollCheck))
Default Profile: IPM_RTCONS
Location in UI: 1) Create an IP using generation rule 0008.
2) Create an acquisition contract.
3) Assign an IP.
4) Create rights scope for one year. Dimensions:
Market - BOOK
Territory - CANADA
Language - ALL
Royalty dimension - ALL_PG
5) Load IP and generate rights from acquisition contract.
6) Create sales contract and sell more rights than owned.
7) Run collision check.
8) Expand the trees.
Profile: CUNORAVAILCONTRACTS (Available Rights (IPMCollCheck))
Default Profile: IPM_RTCONS
Location in UI: 1) Create an IP using generation rule 0008.
2) Create an acquisition contract.
3) Assign an IP.
4) Create rights scope for one year. Dimensions:
Market - BOOK
Territory - CANADA
Language - ALL
Royalty dimension - ALL_PG
5) Load IP and generate rights from acquisition contract.
6) Create sales contract and sell more rights than owned.
7) Run collision check.
8) Expand the trees.
Profile: CUNORMISSINGRIGHTS (Missing Rights (IPMCollCheck))
Default Profile: IPM_RTCMIS
Location in UI: 1) Create an IP using generation rule 0008.
2) Create an acquisition contract.
3) Assign an IP.
4) Create rights scope for one year. Dimensions:
Market - BOOK
Territory - CANADA
Language - ALL
Royalty dimension - ALL_PG
5) Load IP and generate rights from acquisition contract.
6) Create sales contract and sell more rights than owned.
7) Run collision check.
8) Expand the trees.
Profile: CUNOROPENRIGHTS (Open Rights (IPMCollCheck))
Default Profile: IPM_RTCONS
Location in UI: 1) Create an IP using generation rule 0008.
2) Create an acquisition contract.
3) Assign an IP.
4) Create rights scope for one year. Dimensions:
Market - BOOK
Territory - CANADA
Language - ALL
Royalty dimension - ALL_PG
5) Load IP and generate rights from acquisition contract.
6) Create sales contract and sell more rights than owned.
7) Run collision check.
8) Expand the trees.
Profile: HB_SCOPE (Holdback Scope)
Default Profile: IPM_RTHBC
Location in UI: Sales contract with holdbacks activated
Profile: RIGHTS (Pure rights scope)
Default Profile: IPM_RTBASE
Location in UI: Sales contract or acquisition contract
Profile: RIGHTS_ROYALTIES (Rights and royalties scope)
Default Profile: IPM_RTBASE
Location in UI: Sales contract
Profile: ROYALTIES (Pure royalties scope)
Default Profile: IPM_RTBASE
Location in UI: Sales contract or acquisition contract
Intellectual property (IP)
Profile: RIGHTS_SCOPE_EDIT (Rights scope edit)
Default Profile: IPM_RTGRP
Location in UI: Edit page for any of the rights types
Profile: RIGHTSOWNEDGREF (Rights owned granting reference)
Default Profile: IPM_RTFULL
Location in UI: IP overview page (condition: base category of IP includes rights)
Profile: RIGHTSOWNED (Rights owned)
Default Profile: IPM_RIGHTS
Location in UI: IP overview page (condition: base category of IP includes rights)
Profile: RELEASERESTRICTIONS (Rights release restrictions)
Default Profile: IPM_RTREST
Location in UI: IP overview page (condition: base category of IP includes rights)
Profile: RELEASEDATES (Rights release dates)
Default Profile: IPM_RTBASE
Location in UI: IP overview page (condition: base category of IP includes rights)
Rights availability analysis (RAA)
Profile: ACQUIRED_SOLD_RIGHTS (Acquired and sold rights)
Default Profile: IPM_RAARDE
Location in UI: Step 4 of RAA procedure (Availability overview)
Profile: ANSWERITEM (Another answer item)
Default Profile: IPM_RAAIPR
Location in UI: Step 4 of RAA procedure (Availability overview)
Profile: AVAIL_NOTOWNED_MISSING (Available, not owned and missing rights)
Default Profile: IPM_RAAVAI
Location in UI: Step 4 of RAA procedure (Availability overview)
Profile: HB_EDIT_GROUP (Holdback edit group profile for RAA)
Default Profile: IPM_RTHB
Location in UI: Step 2 of RAA procedure (Availability criteria),
license to third-party request (LTHP) scenario only, holdbacks activated
Profile: RIGHTS_HOLDBACK (Rights with holdback)
Default Profile: IPM_RTBASE
Location in UI: Step 2 of RAA procedure (Availability criteria),
license to third-party request (LTHP) scenario only, holdbacks activated
Profile: RTDIM_DISPLAY (Rights dimensions read-only profile)
Default Profile: IPM_RTDIM2
Location in UI: Step 3 of RAA procedure (IP selection)
Profile: RTDIM_EDIT (Rights dimensions editable)
Default Profile: IPM_RTDIM
Location in UI: Step 3 of RAA procedure (IP selection)
Profile: RTGRP_DISPLAY (Rights group read-only profile)
Default Profile: IPM_RTGRP2
Location in UI: Step 2 of RAA procedure (Availability criteria)
Profile: RTGRP_EDIT (Rights group editable profile)
Default Profile: IPM_RTGRP
Location in UI: Step 2 of RAA procedure (Availability criteria)
Profile: RTRESTRICTED (Restricted rights)
Default Profile: IPM_RTREST
Location in UI: Step 4 of RAA procedure (Availability overview)
Profile: RTRESTRICTED_ANSWITEMS (Restricted rights with answer items)
Default Profile: IPM_RAARES
Location in UI: Step 4 of RAA procedure (Availability overview)
Profile: RTUNRELEASED (Unreleased rights)
Default Profile: IPM_RTBASE
Location in UI: Step 4 of RAA procedure (Availability overview)
Profile: RTUNRELEASED_ANSWITEMS (Unreleased rights with answer items)
Default Profile: IPM_RAABAS
Location in UI: Step 4 of RAA procedure (Availability overview)
Fill RESBD Structure from EBP Component Structure CL_GUI_FRONTEND_SERVICES - Frontend Services
This documentation is copyright by SAP AG.
Length: 13306 Date: 20240523 Time: 170330 sap01-206 ( 142 ms )
