Hierarchy
MRSS_NW (Software Component) SAP Multiresource Scheduling for SAP Net⤷
PM-WOC (Application Component) Maintenance Processing⤷
/MRSS/DPR (Package) MRS Interface for Cprojects
IMG Activity
| ID | /MRSS/DPR_SUBSYSTEM | BAdI: Integration of MRS as a Subsystem of cProjects |
| Transaction Code | /MRSS/92000057 | (empty) |
| Created on | 20080325 | |
| Customizing Attributes | /MRSS/DPR_SUBSYSTEM | BAdI: Integration of MRS as a Subsystem of cProjects |
| Customizing Activity | /MRSS/DPR_SUBSYSTEM | BAdI: Integration of MRS as a Subsystem of cProjects |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /MRSS/DPR_SUBSYSTEM |
Use
You use this Business Add-In (BAdI) to integrate SAP Multiresource Scheduling as a subsystem of cProjects.
This BAdI provides the following methods:
- FREE
The system calls this method to clear the MRS buffers when a project is closed.
- HAS_CHANGES
The system calls this method before saving a project to check whether UI changes have been made.
- INITIALIZE_AFTER_SAVE
The system calls this method after a project has been saved to fill the MRS buffers.
- PREPARE_TO_SAVE
The system calls this method before a project is saved to perform validations.
- SAVE
The system calls this method on saving a project to save the data in MRS.
Requirements
An additional step is required to call this BAdI: A class in the customer namespace must be implemented, for example, ZCL_DPR_SUBSYSTEM MRS Cpro Intergration as Subsystem.
This class must implement the interfaces:
- IF_DPR_APPL_BOOTSTRAP_MEMBER
- IF_DPR_APPL_PLUG_IN_SUBSYSTEM
In interface IF_DPR_APPL_PLUG_IN_SUBSYSTEM, the corresponding BAdI methods are called in the respective methods.
For example:
METHOD if_dpr_appl_plug_in_subsystem~has_changes.
DATA: lref_badi TYPE REF TO /mrss/dpr_badi_subsystem.
GET BADI lref_badi.
CALL BADI lref_badi->has_changes
RECEIVING
rv_has_changes = rv_has_changes.
ENDMETHOD.
Or:
METHOD if_dpr_appl_plug_in_subsystem~save.
DATA: lref_badi TYPE REF TO /mrss/dpr_badi_subsystem.
GET BADI lref_badi.
CALL BADI lref_badi->save
RECEIVING
rv_rc = rv_rc.
ENDMETHOD.
In addition, the contructor in "get_instance" must return and (if necessary) generate the instance of the class.
Standard settings
SAP provides the following default implementation:
- /MRSS/DPR_SUBSYSTEM_ENH_IMPL
For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).
Activities
We recommend that you use the default implementation to benefit from automatic code updates and improvements.
However, if you had implemented a customer-specific logic in a previous SAP Multiresource Scheduling release and want to keep using your implementation, you can do so.
Example
See also
For more information about implementing BAdIs as part of the Enhancement Framework, see SAP Library for SAP NetWeaver Platform on SAPHelp Portal at http://help.sap.com/nw_platform. Choose a release and then Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development -> Enhancement Framework.
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 |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | /MRSS/DPR_SUBSYSTEM | 0 | HLB0009110 | Cross-Application Components |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20090903 |
| SAP Release Created in | 610 |
