How can I influence planned deadlines individually?

IPRM0002

You can use this customer exit to specify the next planned dates for performance-based and time-based maintenance plans . This exit consists of several function modules.

BAdI: IPRM_MCP_SCHE_CHANGE

You can use this BAdI to individually adjust the scheduling of a multiple counter plan.

You can implement scenarios or functions such as the following:

How can I determine a desired date for a planned counter reading, for example, if the date should always occur on a working day?

How can I use self-defined forecast models or seasonal models for scheduling?

IPRM0002

Function module: EXIT_SAPLIPM5_001

You can use this customer exit function module to determine the date on which the next planned counter reading should be reached for performance-based maintenance plans .

For more information, see Example Customer Exit IPRM0002 (1) .

How can I determine desired dates, for example, if an inspection should always be due on the first Monday in the month?

IPRM0002

Function module: EXIT_SAPLIPM5_002

You can use this customer exit function module to individually adjust planned dates for time-based maintenance plans to meet your company's requirements.

For more information, see Example Customer Exit IPRM0002 (2) .

How can I show seasonal counter deviations in the system, for example, for ice-cream manufacture or in agriculture?

IPRM0002

Function module: EXIT_SAPLIPM5_002

You can use this customer exit function module to change the estimated annual performance for the counter used in the maintenance plan for performance-based maintenance plans . The new counter reading will only be used in scheduling to schedule seasonally varying dates. The annual performance saved in the system is not changed.

For more information, see Example Customer Exit IPRM0002 (3) .

How can I dynamically change the estimated annual performance?

MEASURE_POINT_UPD_PYEAR

You can use this function module to change the estimated annual performance for the counter used in the maintenance plan for performance-based maintenance plans .

For more information, see Example Function Module MEASUREM_POINT_UPD_PYEAR .

How can I use my own rules to determine which maintenance package should be due next?

How can I skip maintenance packages that are not required because they no longer need to be performed based on the current counter reading?

IPRM0005

You can influence the dates for performance-based strategy plans using this customer exit.

You can determine which maintenance packages are due next, and, for example, which can be skipped on the basis of the counter reading entered using your own rules.

For more information, see Example Customer Exit IPRM0002 .

How can I prevent a database update in the scheduling?

BAdI: IPRM_CHECK_UPD_SCHED

You can use this BAdI to decide for multiple counter plans whether the database should be updated from the scheduling of a maintenance plan.

How can I set the reference date for the scheduling?

BAdI: DI_WPS_PLAN_EXT_DATE

With this BAdI you can use functions such as the following for multiple counter plans :

How can I define whether a plan date in the past is permissible?

BAdI: IPRM_MCP_DATE_I_PAST

You can use this BAdI to determine for multiple counter plans whether the scheduled dates calculated in the past should also appear with the date in the past in the scheduling list.

How can I adjust the planned/basic dates of maintenance call objects?

BAdI: IPRM_MCP_UPD_CALLOBJ

You can use this BAdI to control for multiple counter plans the schedule adjustments of scheduled dates that have already been put into process (status Called Up ).