Resolving restriction in Phase Model

Objectives

After completing this lesson, you will be able to:

  • Learn new features and functions

Resolving restriction in Phase Model

Standard solution until OP 2023 FPS0 including restriction

The phase model has been delivered via the scope items:

  • Reactive maintenance process (4HH) referring to notification type Y1 and order type YA01Proactive maintenance process (4HI) referring to notification type Y2 and order type YA02
  • Following the original solution, the calculation of the phase model was restricted within the boundary of each scope item. 
  • From a technical perspective, a maintenance planner could assign a proactive maintenance notification of type Y1 to a proactive maintenance order of type YA02
  • Combining a notification type of Y1 with an order type of YA02 merges the business objects of two different scope items, which was not supported with regards to the calculation of the subphases so that an incorrect subphase was shown

Both screenshots show the assignment of the overall status profile.

  • Reactive maintenance process is represented by overall status profile PMSP1 so that this profile is assigned to notification type Y1 and order type YA01
  • Proactive maintenance process is represented by overall status profile PMSP2 so that this profile is assigned to notification type Y2 and order type YA02

→ The subphase has been only calculated correctly if all business objects refer to the same overall status profile .

Standard solution from OP 2023 FPS1 

Maintenance notifications and orders referring to different scope items are compatible with regards to the calculation of the resulting subphases. 

SAP Note "3394726 – Phase Model – Allow separate Overall Status Profiles on Maintenance Order and assigned Maintenance Notification" is provided and can be only used for OP 2023 FPS0 and not on older versions.

Log in to track your progress & complete quizzes