Hierarchy
MRSS_NW (Software Component) SAP Multiresource Scheduling for SAP Net⤷
PM-WOC-MO (Application Component) Maintenance Orders⤷
/MRSS/SGE (Package) Multiresource Planning: Scheduling Engine
IMG Activity
| ID | /MRSS/SGE_TEAM_CHECK | BAdI: Check Team Before Save |
| Transaction Code | /MRSS/92000222 | (empty) |
| Created on | 20090927 | |
| Customizing Attributes | /MRSS/SGE_TEAM_CHECK | BAdi: Check Team before save |
| Customizing Activity | /MRSS/SGE_TEAM_CHECK | BAdi: Check Team before save |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /MRSS/SGE_TEAM_CHECK |
Use
You use this BAdI to carry out additional checks before you save a team.
Requirements
Standard settings
The BAdI provides the following method:
CHECK_BEFORE_CHANGE: Additional checks can also be carried out here. This method accepts the old and new definitions of the team, and old and new team members as import parameters; failed statuses and messages can be exported.
Activities
When you call the IMG activity, a dialog box appears in which you can enter a name for the implementation.
If you have already defined other implementations for this BAdI, another dialog box appears in which the existing implementations are displayed. In this case, choose "Create", and proceed as follows:
1. In the dialog box, enter a name for the BAdI implementation in the "Implementation" field, and choose Create.
The screen for creating BAdI implementations appears.
2. Enter a short text for the implementation in the "Short Text for Implementation" field.
3. From the tab page index, choose "Interface".
The "Name of Implemented Class" field is already maintained on the tab page, since a class name was automatically assigned to the implementation when you named it.
4. Save your entries and assign the implementation to a development class.
5. Place the cursor on the method and double-click to access method processing.
6. Enter the code for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.
7. Save and implement your code. Return to the "Edit Implementation" screen.
8. Save the entries on the "Edit Implementation" screen.
Note: You can also create an implementation and activate it at a later time. In this case, end the processing stage at this point.
Example
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/SGE_TEAM_CHECK | 0 | HLB0009110 | Cross-Application Components |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20130207 |
| SAP Release Created in | 700 |
