Hierarchy
⤷ PPM-PFM (Application Component) Portfolio Management
⤷ RPM_IMG (Package) RPM IMG Objects
IMG Activity
ID | 0RPM_USEREXITS | Portfolio Management User Exits Overview |
Transaction Code | S_XSD_23000115 | (empty) |
Created on | 20030210 | |
Customizing Attributes | 0RPM_USEREXITS | Portfolio Management User Exits Overview |
Customizing Activity |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SAP XRPM USER EXITS |
Use
User exits enable you to add specific data fields for the objects as per project requirement. The customer includes are added in the structures to add the customer-specific additional attributes for this object.
To add your own fields, click the CI_* include and a new structure is created with CI_*. Add the fields to the structure. Note: The "data type string" fields are not supported.
The fields that are added to the CI_I* structures are then automatically included in the relavant iViews available in SAP Portfolio and Project Management.
There are two different types of CI_* includes:
- Fields that are added to the database (you can then fill the fields by maintaining entry fields on the corresponding iViews)
- Derived fields that you fill by implementing ABAP coding (implementations of Business Add-Ins (BADIs). These fields are display only on the relevant iViews.
Note: The enhancement category for the CI_* include structures must have the enhancement category "Can not be enhanced".
Since all customer fields are part of database tables (direct or indirect), you need to carefully decided whether to add or delete a field to/from the CI_* structures.
To implement coding to fill the fields of the
To implement customer-specific processing that utilizes BADIs, you need to use transaction SE19 by defining implementations of SAP Portfolio and Project Management BADIs.
Activate any new implementations before adding code to the implementation methods.
Business Attributes
ASAP Roadmap ID | 201 | Make global settings |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type |
History
Last changed by/on | SAP | 20090217 |
SAP Release Created in |