SAP ABAP IMG Activity IPRM_MCP_DATE_I_PAST (BAdI: Check Whether Plan Date May Be in the Past)
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_DATE_I_PAST BAdI: Check Whether Plan Date May Be in the Past  
Transaction Code S_P6B_12000046   (empty) 
Created on 20030603    
Customizing Attributes IPRM_MCP_DATE_I_PAST   BAdI: Check Whether Plan Date May Be in the Past 
Customizing Activity IPRM_MCP_DATE_I_PAST   BAdI: Check Whether Plan Date May Be in the Past 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name IPRM_MCP_DATE_I_PAST    

Use

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

With this BAdI, you can determine whether the schedules of a multiple counter plan calculated in the past, should also appear in the schedule list with the past date.

Schedules of a multiple counter plan, whose planeed date was calculated in the past, are displayed in the schedule list with the current system date as standard.

Note the scheduling algorithm for performance-based schedules in the past. You can find more information on scheduling for multiple counter plans in the SAP library under Plant Maintenance.

Using this BAdI may mean that, depending on the status of the counter, several schedules are in the past and the scheduling is reliant on prompt measurement recording.

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:

  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_DATE_I_PAST 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