Usage of Permits in SAP Plant Maintenance

灰太狼 2022-10-07 13:49 232阅读 0赞

**Purpose**

This process describes the use of permits during order processing. Before an order can be executed or technically completed, a planner ensures that:

*  All the necessary safety precautions have been taken

*  The required financial resources are available

*  The work has been approved at management level

**Prerequisites**

You define permit categories in the Customizing for Plant Maintenance and Customer Service by choosing Master Data in Plant Maintenance and

Customer Service – Basic Settings – Permits – Define Permit Categories.

These permits can be assigned to Technical Objects and / or Orders. Assignment of Permits to the PM Order can be done in 2 ways.

*  Manually – without referring any condition

*  Automatically – using the condition

**Permits Assignment in Technical Object:**

Permits can be assigned to Technical Objects viz., Equipment & Functional Location. These permits will be called in all the PM orders which are

created with reference to these Technical Objects with the condition of **Proposal **tick box selected in Permits Screen.

To assign the Permits to Technical Objects in Technical Objects, follow this path.

*  Transaction Code is IE02 / IL02

*  In the Technical Object, Go to è Permits.

Prerequisites: Permits should be created. Refer Transaction Code IPMD. Creation of Permits will be discussed at a later phase of this document.

![equipment\_\_\_permits\_163950.jpg][equipment_permits_163950.jpg]

This type of Permits assignment to the technical objects will be done whenever critical equipments are used & approval is required prior to all kinds of

maintenance.

**Permits Assignment to Order:**

Apart from assigning Permits to technical objects, Permits can be assigned directly in PM order. In some of the Technical Objects, Approval will not be

required always whenever maintenance is being done. So whenever approval required, permits can assigned in PM Order.

To facilitate this, Permits can be assigned to PM Order either manually or automatically.

**Manual Assignment of Permits in PM Orders:**

Menu Path: IW32 – Menu **Goto –**** Permits.**

**![order\_\_\_permit\_163951.jpg][order_permit_163951.jpg]**

**Automatic Assignment of Permits to PM Orders:**

Also Permits can be assigned to PM Order automatically based on Business Transactions.

1. Based on Cost

2. Based on Type of Activity

3. Based on Other Conditions

**Based on Cost:**

Here, approval will be asked from the manager or responsible person if the maintenance cost goes beyond certain limit. Here costs include Total

Planned Cost of Order, Total Estimated Costs of Order & Total Actual Costs of Order.

**Scenario: (Whenever Total Planned Costs is more than limit)**

Here, Permits should be created automatically whenever Total Planned Costs of Order goes beyond the limit. The following steps are to be followed.

1. Create Characteristics for the Parameters to be considered (T- Code is CT04)

a. Total Planned Costs of the Order (CSEVPERMIT – PKOSTEN)

b. If the approval is for specific type of Order (ex. Only for Preventive Maintenance), then add Order Type as another characteristic

(CSEVPERMIT – AUART)

![char1\_163952.jpg][char1_163952.jpg]

![char2\_163953.jpg][char2_163953.jpg]

![char3\_163954.jpg][char3_163954.jpg]

![char4\_163955.jpg][char4_163955.jpg]

2. Create Class by including all the created characteristics (T – Code is CL02)

Once all the required characteristics are created for the Permits configuration, Permit Class should be created.

***Pre-Requisites:*** Permit Class should be configured in OIPG. The class name in CL02 should be same as the class mentioned in OIPG.

![category\_163956.jpg][category_163956.jpg]

![class\_163958.jpg][class_163958.jpg]

![per1\_163959.jpg][per1_163959.jpg]

In the class of **Permit, **all the required characteristics should be assigned.

1. Creation of Permits

Once after creating Required Characteristics & Class, Permits can be configured using these details.

Transaction Code is IPMD

![per2\_163960.jpg][per2_163960.jpg]

As shown above, Permit Code, Permit description & Permit category should be given. After that, Approval stage should be mentioned with

requirement status of approval. Approval stages are Order Release & Order TECO. Requirement statuses are

1. Warning message if permit is not issued

2. Error message if permit is notissued

3. Permit is optional

Once after defining above mentioned details, click ***Classification ***button.

![per3\_163965.jpg][per3_163965.jpg]

Here the condition is that approval is required for the maintenance if the planned cost is  more than 1000 SAR & order type is ZM03.

**Usage of these Permits:**

With above configured Permit, the following usage will be derived.

Whenever order is created with order type ZM03 & total planned costs goes beyond the limit of 1000 SAR, this permit will be assigned automatically

in the order. By having proper authorisation, only authorised person can issue this permit. Without having the issue of permit, Order release can be

rectified.

![per4\_163966.jpg][per4_163966.jpg]

As per the required parameter to be considered for approval process, all the characteristics should be created & assigned the Permit class. All the

possible conditions can be referred from the table **CSEVPERMIT**.

**Some Additional Information:**

1. There are 3 different Order types (PM01, PM02 & PM03); but for all order types, approval is required if the total planned cost is more than 1000

SAR. Then there are 2 ways.

a. One, create 3 different approvals with the combination PM01 & 1000 SAR, PM02 & 1000 and PM03 & 1000.

b. Second, Create only one permit by assigning all 3 order types. Pre-Requisite to assign multiple values in Permit configuration is that ***Select***

***                    Multiple Values while creating Characteristics & giving appropriate no. of characters.***

2. Authorisation for Permits Issue can be controlled using Authorisation Object* **I\_SOGEN    PM: Permit   ***

![per5\_163977.jpg][per5_163977.jpg]

Multiple values can be mentioned while defining the permits.

![per6\_163978.jpg][per6_163978.jpg]

[equipment_permits_163950.jpg]: /images/20221005/18e2ff2fc3ed4d68bd9ad417d7486266.png
[order_permit_163951.jpg]: /images/20221005/49e1f6c68f1c484085746c14d956cacd.png
[char1_163952.jpg]: /images/20221005/d5a164dacc01457e92016650756ddb19.png
[char2_163953.jpg]: /images/20221005/747b8bb58ce34094b5217381ffe1a6df.png
[char3_163954.jpg]: /images/20221005/5b2c39abda00432eaf9e1109a10d64c6.png
[char4_163955.jpg]: /images/20221005/762692fd15664f9c97f4df82a95da351.png
[category_163956.jpg]: /images/20221005/7a28ddc4e33f41bc84f33a97aadfa7b4.png
[class_163958.jpg]: /images/20221005/4f9a34919bfe46f58568534110ea4538.png
[per1_163959.jpg]: /images/20221005/7b06dc60533d41fca56b78302fc26c3c.png
[per2_163960.jpg]: /images/20221005/c3f9c9b34d6642aaaaadfdd12d9ca1a8.png
[per3_163965.jpg]: /images/20221005/638b80f1fdbd4e1d84ca574a47fad4f5.png
[per4_163966.jpg]: /images/20221005/698753480d9f4e6f9e032730156c391b.png
[per5_163977.jpg]: /images/20221005/3fc116d919a9402bbbb3bf7af51cea75.png
[per6_163978.jpg]: /images/20221005/40abfcf92dc44fa2a4cf7580f686ac0a.png