Hierarchy
CPRXRPM (Software Component) SAP Portfolio and Project Management 6.0⤷
PPM-PFM (Application Component) Portfolio Management⤷
/RPM/CONFIGURATION (Package) xRPM Configuration
IMG Activity
| ID | /RPM/EX_CAP_PLAN | BAdI: Definition for Capacity Enhancement |
| Transaction Code | /RPM/47000072 | (empty) |
| Created on | 20060802 | |
| Customizing Attributes | /RPM/EX_CAP_PLAN | BAdI: Definition for Capacity Enhancement |
| Customizing Activity | /RPM/EX_CAP_PLAN | BAdI: Definition for Capacity Enhancement |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /RPM/EX_CAP_PLAN_BADI |
Use
This Business Add-In (BAdI) is used in the Portfolio Management (PPM-PFM) component.
You can use this BAdI to enhance and extend the what-if scenario business object. The BAdI methods provide the opportunity for content validations, enhancements to customer field content, and to meet other customer-specific data requirements. The methods are integrated at various points of the object interaction model, providing the capability to enhance initial object content, enhance the retrieved or saved content, and perform functions during or after the object save process.
In order to make the views read-only or editable, you can implement an implicit enhancement spot in method IS_VIEW_READ_ONLY of class /RPM/CL_FIN_CAP_PLANNING_API. You cannot use the MODIFY_CAP_CONFIG BAdI method to change the Modify or Display properties of a group if the input capacity data is blank or is not maintained by the user.
To improve system performance, financial data from the Capacity Planning screen is not passed to the back-end code in the following cases:
- If you have not created new data
- If you have modified existing data by changing the input from the CT_CAP_PLAN method to the MODIFY_CAP_CONFIG method to blank.
Requirements
Standard settings
The BAdI is designed so that the active implementation is called and executed.
In the standard system, the BAdI is not filter-dependent.
Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
Example
An installation needs a 'read-only' field EXTERNAL_ID to be filled according to a number range object: you can perform this functionality within the CREATE_OBJECT method.
Customer fields should be calculated prior to their display, depending on the data of related fields: you can perform this calculation within the GET_ATTRIBUTES method.
Data content in certain fields should not be changed once initially populated, or the content of certain fields not displayed is derived when the user input is processed: you can perform this functionality in the SET_ATTRIBUTES method.
When data is saved, validation of user authorizations and data consistency should be performed such as the existence of referential data: You can perform this validation within the ON_SAVE_REQUESTED method by allowing a user to enter of corrected data prior to saving.
Once created, mail notifications must be generated informing adminstrators that a business object has been created and subsequent action may be necessary: You can perform this functionality within the ON_CHANGES_COMMITTED method.
See also
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20060802 |
| SAP Release Created in | 400 |
