SAP ABAP IMG Activity DI_WPS_PLAN_EXT_DATE (BAdU: Set Reference Date for Scheduling Multiple Counter Plan)
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 DI_WPS_PLAN_EXT_DATE BAdU: Set Reference Date for Scheduling Multiple Counter Plan  
Transaction Code S_P6B_12000044   (empty) 
Created on 20030603    
Customizing Attributes DI_WPS_PLAN_EXT_DATE   BAdU: Set Reference Date for Scheduling Multiple Counter Plan 
Customizing Activity DI_WPS_PLAN_EXT_DATE   BAdU: Set Reference Date for Scheduling Multiple Counter Plan 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name DI_WPS_PLAN_EXT_DATE    

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

You can use this BAdI to externally influence the scheduling of a mulitple counter plan.

  • You can use the method GET_EXT_DATE to determine the reference times for subsequent dates (see example).
  • You can use the methods GET_EXTT_EXT_TIMESTAMP_START to pre-fill the start time of a multiple counter plan.

Example

Determine proposal for start date and start time individually for the start

You want to determine the default values for the start date and start time for a start of a multiple counter plan yourself. The system proposes the current date and the current time respectively.

End - Start relationship for subsequent dates

The calculation of a planned date in the scheduling of the multiple counter plan (apart from the first planned date) is based on the preceding date. On the basis of the preceding dates, the counter readings are determined (in so far as performance-based cycles are used in the plan) and the cycle lengths are added.

Deviating from this standard, many industries need to be able to determine the basis for the subsequent dates externally. If, for example, a notification generated from a maintenance plan is integrated in a revision, then the end date of the revision should be taken into account for calculating the subsequent date, instead of the original planned date of the notification.

For a multiple counter plan with a cycle of one month, without using this Business Add-In, you get the following date sequence:

Call number    Planned date    Call date    Date type/Status

1    15.08.2001    15.08.2001    Restart, waiting

2    14.09.2001    14.09.2001    Scheduled, waiting

3    14.10.2001    14.10.2001    Scheduled, waiting

4    13.11.2001    13.11.2001    Scheduled, waiting

5    13.12.2001    13.12.2001    Scheduled, waiting

For a called-up date (status Called), this enhancement gives you the option of externally determining the "reference date" for calculating the next date.

If the date with the call number 1, for example, on the 15.08.2001 generates a maintenance call object (such as an order), this gets the status Called. The actual maintenance activity, however, lasts several days and will probably not be completed until the 25.08.2001. This date is also in the order as the basic end date.

The Business Add-In gives you the option of determining this end date and use it as reference date for calculating the second date. Finally, this "postponement" affects the entire scheduling and can produce the following schedule:

Call number    Planned date    Call date    Date type/status

1    15.08.2001        Restart, called up (End date call object 25.08.2001)

2    24.09.2001    24.09.2001    Scheduled, waiting

3    24.10.2001    24.10.2001    Scheduled, waiting

4    23.11.2001    23.11.2001    Scheduled, waiting

Requirements

Standard settings

Recommendation

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.

Further notes

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