Hierarchy

⤷

⤷

⤷

IMG Activity
ID | IPRM_MCP_SCHE_CHANGE | BAdI: Multiple Counter Plan: Adjust Dates During Scheduling |
Transaction Code | S_P6B_12000047 | (empty) |
Created on | 20030603 | |
Customizing Attributes | IPRM_MCP_SCHE_CHANGE | BAdI: Multiple Counter Plan: Adjust Dates During Scheduling |
Customizing Activity | IPRM_MCP_SCHE_CHANGE | BAdI: Multiple Counter Plan: Adjust Dates During Scheduling |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | IPRM_MCP_SCHE_CHANGE |
Use
This Business Add-In (BAdI) is used in the Maintenance Planning (PM-PRM-MP) component.
With this BAdI you can individually adjust the scheduling of a multiple counter plan.
You can, for example, implement the following scenarios or functions:
- Implementation of shift factors (see single cycle plan)
This can be used to take a premature or delayed confirmation of a preceding date into account for the successor.
The shift factors can be stored in a customer-specific table for a maintenance plan and taken into account within the corresponding methods. - Setting of particular counter readings for the further scheduling, for example, to bridge the maintenance time of the reference object.
- Calculation of planned counter reading (performance-based) and planned date (time-based) by user-defined logic
- Setting of a particular, fixed planned date, both for time-based and performance-based cycles.
- Overwriting of default values of 100% for positive and negative shift factors when creating multiple counter plans and cycle sets
- Controlling for each multiple counter plan whether the system reads or ignores the existing actual shift when calculating the next planned date or planned counter reading during scheduling
For more information, see the documentation of the individual methods.
Requirements
Standard settings
Activities
After calling up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.
If you have already made 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:
- In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.
The screen for creating BAdI implementations is now displayed.
- Enter a short text for the implementation in the Short text for implementation field.
- From the tab index, choose Interface.
The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.
- Save your entries, and assign the implementation to a development class.
- Place the cursor on the method, and double-click to enter method processing.
- Enter the code for the implementation between the statements
method <Interface name> ~ <Name of method>
andendmethod
. - Save and implement your code. Return to the Edit Implementation screen.
- Save the entries on the Edit Implementation screen.
Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.
- Choose Activate
The code you stored in the method will be run when the application program is executed.
Example
Business Attributes
ASAP Roadmap ID | 153 | Design enhancements |
Mandatory / Optional | 3 | Nonrequired 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 | IPRM_MCP_SCHE_CHANGE | 0 | HLA0006645 | Maintenance Plans |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20030603 |
SAP Release Created in | 470 |