SAP ABAP IMG Activity IPRM_MCP_UPD_CALLOBJ (BAdI: Adapt Plan/Basic Dates of Call Objects)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ IPRM (Package) Application Development R/3 Preventive Maintenance
IMG Activity
ID IPRM_MCP_UPD_CALLOBJ BAdI: Adapt Plan/Basic Dates of Call Objects  
Transaction Code S_P6B_12000048   (empty) 
Created on 20030603    
Customizing Attributes IPRM_MCP_UPD_CALLOBJ   BAdI: Adapt Plan/Basic Dates of Call Objects 
Customizing Activity IPRM_MCP_UPD_CALLOBJ   BAdI: Adapt Plan/Basic Dates of Call Objects 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name IPRM_MCP_UPD_CALLOBJ    

Use

This Business Add-In (BAdI) is used in the Maintenance Planning (PM-PRM-MP) component.

With this BAdI you can control the scheduling adjustments of dates that have already been released (status Called) for multiple counter plans.

Updating the schedule in the standard only leads to a check of the dates with the status Waiting. Dates with the status Called are not adjusted.

Requirements

Standard settings

If you use this BAdI, and implement it actively accordingly, the dates of a multiple counter plan are determined as follows:

  1. Dates with the status Waiting are deleted.
  2. Within the remaining dates, the scheduling determines a "fixed" starting point and checks the scheduled dates, beginning with the latest date.

    The following dates are assessed as a fixed starting point:

    Date with the status Completed or Ignored

    • Status Completed
      The completion date serves as starting point for the date adjustment.
    • Status Ignored:
      The planned date serves as starting point for the date adjustment.

      Date with scheduling type Restart or Start in Cycle

      • The start time serves as starting point for the date adjustment.

      Date whose call object does not allow any date adjustment

      This is the case if the corresponding call object is locked by a user at the time of a scheduling update or if a completion date is already specified in the maintenance plan.
      The status I0043 - Locked is also checked for the call object "Maintenance- or Service Object.
  3. Beginning at the determined starting point, the planned dates of the dates with the status Called are recalculated. The system recalculates the next planned date from the starting point, and uses this new planned date to calculate any subsequent dates.
  4. If the corresponding dates with the status Called are adjusted, then the last date with the status Called is used as the basis for calculating the subsequent date(s).
  5. The changed planned dates are not updated (either in the maintenance plan or in the corresponding call objects) until the maintenance plan is saved.

Note

  • Dates with the status Called and a planned date in the past are not adjusted.
  • Dates with several call objects are not adjusted if one call object is completed.

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:

  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 is now displayed.

  2. Enter a short text for the implementation in the Short text for implementation field.
  3. 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.

  4. Save your entries, and assign the implementation to a development class.
  5. Place the cursor on the method, and double-click to enter 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 then activate it at a later time. In such a case, end the processing stage at this point.

  9. 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_UPD_CALLOBJ 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