Ansicht
Dokumentation

SIMG_VC_EAM_PRIOZN - Define Prioritization Profiles

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Allows you to maintain prioritization profiles.

In this configuration step, you can maintain prioritization profile using the following steps:

1.,,Define a list of prioritization profiles. A profile can be compared to a container that has consequence category groups, notification types, and plants. When you create a maintenance request of type M1 for a technical object that is assigned to plant 1010, and assess priority, the system tries to locate the profile that matches this combination.

If you enter M1 as notification type, 1010 as maintenance plant, and CHEMICAL_PROF as profile, and assess priority, the system identifies CHEMICAL_PROF as the selected profile and refers to the Consequence to Priority mapping table. It fetches the priority for the selected combination of consequences and likelihood.

2.,,Assign prioritization profile to a notification type and a plant. You can assign a profile to many plants but a plant cannot have more than one profile assigned to it. Ensure that you maintain only one profile for each notification type and plant.

3.,,Assign consequence category group to a prioritization profile. You can assign a profile to only one group. But, you can assign the same group to one or more profiles.

4.,,Assign UI (user interface) position to a consequence category. Within a group, you can choose to arrange the consequence categories in a particular order. When you assess priority, you will see the consequence categories in this order.

5.,,Assign a priority to consequences. You can assign an appropriate priority to a combination of consequence categories, consequences, and likelihood. It is important that priorities are carefully assigned to the combinations as the priorities directly influence other factors of a maintenance request such as the final due date, required start date, and required end date.

ROGBILLS - Synchronize billing plans   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 2101 Date: 20240523 Time: 182917     sap01-206 ( 55 ms )