Hierarchy

⤷

⤷

IMG Activity
ID | /RPM/EX_PORTFOLIO_BA | BAdI: Definition for Portfolio Enhancement |
Transaction Code | /RPM/47000047 | (empty) |
Created on | 20060724 | |
Customizing Attributes | /RPM/EX_PORTFOLIO_BA | BAdI: Definition for Portfolio Enhancement |
Customizing Activity | /RPM/EX_PORTFOLIO_BA | BAdI: Definition for Portfolio Enhancement |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | /RPM/EX_PORTFOLIO_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 portfolio business object. The BAdI methods provide the opportunity for content validations, enhancements to customer field content, and meeting other customer specific data requirements. The methods are integrated at various points in the object interaction model, providing the capability to enhance initial object content, enhance the retreived or saved content , and perform functions during or after the object save processing.
Requirements
Standard settings
In the standard system, the BAdI is designed so that the active implementation is called and executed.
In the standard system, the BAdI implementation 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 dependant 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 ON_SAVE_REQUESTED method by allowing user entry 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
Methods
Interface
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 | 20060724 |
SAP Release Created in | 400 |