Usage of Permits in SAP Plant Maintenance

4/6/2019 Usage of Permits in SAP Plant Maintenance | SAP Blogs
Products
Products Industries
Industries Services Support
Services and Support Training
Training Community
Community Developer
Developer
Partner
Partner About
About
 
Ask a Question Write a Blog Post Login
Former Member
December 7, 2012 5 minute read
Usage of Permits in SAP Plant Maintenance

Follow RSS feed Like
33 Likes 27,664 Views 34 Comments
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
https://blogs.sap.com/2012/12/07/usage-of-permits-in-sap-plant-maintenance/ 1/25
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.
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.
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)
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.
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
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 Classiﬁcation button.
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.
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
Multiple values can be mentioned while defining the permits.
Alert Moderator
Assigned tags
PLM Enterprise Asset Management (EAM)/Plant Maintenance (PM) | Enterprise Asset

Management | in | orders | permits |
View more...
Related Blog Posts
Permits (Part1)
By Eslam Hosny , Sep 03, 2015
Organization structure of SAP PM/EAM
By Amol Khaimar , Apr 13, 2016
FAQ: PM/CS Tables
By Peter Atkin , Jul 26, 2013
Related Questions
Service Procurement in centralized maintenance planning

By Kiran Ambi , Mar 13, 2018
Process ow for Cross Plant Maintenance in Di . Company Code
By Former Member , Dec 23, 2016
Production in Power Plant
By MAHENDRAN PARAMASIVAN , Jun 29, 2018
34 Comments
You must be Logged on to comment or reply to a post.
Former Member
December 12, 2012 at 5:17 am

Excellent Stu , Great work
Like (0)
Former Member

thanks for sharing
Like (0)
Former Member

Maheswaran KD
Good Document to learn cost permit functionality.
Like (0)
Former Member
January 7, 2013 at 8:14 am

Superb document..
Like (0)
Former Member
January 22, 2013 at 12:47 pm

Thanks for Sharing ! Very good document.
Like (0)
Former Member
January 22, 2013 at 3:58 pm

good work. thanks for knowledge sharing!
Like (0)
Andrew Barnard
March 7, 2013 at 1:54 am

3 extra points to augment the excellent document above:
Costs and Currencies
When you create a currency relevant characteristic, such as total planned costs (PKOSTEN), the characteristic
maintenance transaction will require a currency. The values assigned to the characteristic are interpreted
always in this currency.
If the order contains costs in another currency, the system converts the costs from the order cost currency to
the characteristic currency before the comparison is made. The costs are converted using the exchange rate
type ‘M’ as at the current date. For those curious, see subroutine LIMSPF00_COMWWA_CREATE in Function
Group IMSP.
Characteristics form AND conditions
The characteristics of the class are always interpreted as AND conditions – meaning that any permit classi ed
using the permit class must ful l ALL conditions.
Permits can only be classi ed using the (one) permit class de ned in Tx OIPG. Given characteristics form AND
conditions, you must design your class classi cation very carefully if you work with multiple characteristics.
Table T357G_GR – PM: Permit Groups
This table maps the assignment of the class to a permit group. You should note that the table key supports
multiple permit groups – each with a possibly distinct class assignment. You might wonder what happens if
multiple entries were maintained.
The function module PERMIT_PROPOSAL_BY_CLASS just gets the rst entry with a class assigned. In short –
multiple permit groups are not supported. So don’t even try it.
* determine permit class

* (permit class is defined in permit group;
* ONLY one permit group can be defined)
SELECT SINGLE CLASS INTO L_CLASS FROM T357G_GR “#EC *
WHERE ( PERGR NE SPACE ).
Like (0)
Former Member
April 3, 2013 at 6:08 am

Thanks for sharing the informative stu in easily understandable way..
BR
Kalicharan.
Like (0)
Former Member
May 6, 2013 at 7:32 am

Thanks for sharing!
Like (0)
Jogeswara Rao K
June 8, 2013 at 9:46 am

Thanks for sharing
Like (0)
Katigiri Linganna
November 7, 2013 at 11:28 am

Good Document. thanks for sharing this .
Like (0)
Former Member
November 21, 2013 at 9:37 pm

Thanks for making this summary of permits functionality
Like (0)
Former Member | Post author
November 22, 2013 at 8:12 am

Thanks for the comments..
Like (0)
Former Member
February 12, 2014 at 10:37 am

Thank you….. its really Helpful… I tried it worked
Like (0)
Former Member
April 1, 2014 at 12:26 pm

Very useful document for learning permit concept
Like (0)
Shareeq Hussain K M
April 6, 2014 at 7:15 am

Very helpful document. Thanks for sharing.
Like (0)
Andre Luiz Vieira
September 1, 2014 at 2:09 pm

Thanks for sharing!
Very helpful document!
Like (0)
Former Member
September 15, 2014 at 5:04 pm

Thanks for sharing! Very helpful document!
Like (0)
Former Member
December 4, 2014 at 6:10 pm

Good document to understand the concept
Like (0)
Former Member
December 29, 2014 at 8:43 pm

Thanks for sharing
Like (0)
Former Member

Very good document. Thanks a lot, very useful.
Like (0)
Former Member
March 11, 2015 at 12:08 pm

1. During my assignment of value I’m getting error as currency INR not found in IPMD- classi cation.
2. Also I’m unable to nd order type for the same. Can you pls help me out on the same.
Like (0)
Shareeq Hussain K M
March 11, 2015 at 1:40 pm

@Ashish Rao
Kindly check the characteristics .
Regards,
Shareeq
Like (0)
Former Member
March 20, 2015 at 4:53 pm

nice documents,,
Like (0)
Nikhil Bengeri
April 6, 2015 at 7:13 am

Good one.. Really helpful in simple terms..
Like (0)
Former Member
April 8, 2015 at 11:39 am

thanks Maheswaran KD
it’s Avery useful document thanks for sharing your knowledge
best regards Sadin
Like (0)
Rohit Krish
August 17, 2015 at 10:37 am

Other than ABAB development and restriction based on User status, is there any option available to restrict
user to reserve material post release? Without which i hope there is no much use to I_SOGEN.
Like (0)
Former Member

Thanks for sharing
Like (0)
PS R
May 10, 2016 at 6:41 am

Hello Maheswaran,
Excellent document, really it’s very useful.
Thanks,
PS R
Like (0)
Former Member
June 12, 2016 at 6:41 pm

Hi,
I am implementing the same functionality in my project but I am getting an error during creation of permit
class
Please help me out of this.
Thanks!
Ashish
Like (0)
Former Member
October 20, 2016 at 7:56 am

Hi Former Member,
I was getting same error so I changed ‘PERMIT Group’ and than follow all step mention by Former Member, it’s
working ne.
Regards,
Faizan
Like (0)
Former Member
Guys,
Is it possible create more than one permit class? Or due to the AND conditions I must adapt my needings to
only one class with multiple characteristics? I’m quite confused.
Because when I change the permit class at tcode OIPG, all permits listed at IPMD change to this permit class.
Everything works good to me for the class permit I’ve created. (using the ILART eld issue permits for
electrical work for example)
But I really would like to create another permit to control costs, just like it is shown above. And this one has no
connection with the rst permit.
What to do?
Thanks in advance,
Julio
Like (0)
Harikrishna Anumandla

Thanks Former Member for sharing such a great document. The only question i have is what if the order has
to undergo multiple approval process?
Lets say like 1000 $ approval 1
2000 $ approval 2
3000 $ approval 3.
In such case, once the order is released for approval 1, it is released and we don’t have any additional
checkpoint over the order further cost.
Other situations would be, if they have only one cost approval process instead of multiple…..Once the permits
are issued..there would be situations to add additional costs to the existing order…so how to handle such
situations if the management wants to get noti ed for additional costs?
Like (0)
Former Member

Hi Former Member,
Is there any eld we can add Permit Number before we issue a permit?
Thanks in advance.
SP
Like (0)
Share & Follow
Privacy Terms of Use
Legal Disclosure Copyright
Trademark Cookie Preferences
Sitemap Newsletter

Usage of Permits in SAP Plant Maintenance - SAP Blogs PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Usage of Permits in SAP Plant Maintenance - SAP Blogs PDF

Uploaded by

Copyright:

Available Formats

4/6/2019 Usage of Permits in SAP Plant Maintenance | SAP Blogs

33 Likes 27,664 Views 34 Comments

All the necessary safety precautions have been taken

The required financial resources are available

The work has been approved at management level

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

Manually – without referring any condition

Automatically – using the condition

Permits Assignment in Technical Object:

Transaction Code is IE02 / IL02

In the Technical Object, Go to è Permits.

Permits Assignment to 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.

Automatic Assignment of Permits to PM Orders:

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

2. Based on Type of Activity

3. Based on Other Conditions

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

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

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

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

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

Transaction Code is IPMD

1. Warning message if permit is not issued

2. Error message if permit is notissued

Once after defining above mentioned details, click Classiﬁcation button.

Usage of these Permits:

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

possible conditions can be referred from the table CSEVPERMIT.

Some Additional Information:

SAR. Then there are 2 ways.

Multiple values can be mentioned while defining the permits.

PLM Enterprise Asset Management (EAM)/Plant Maintenance (PM) | Enterprise Asset

Related Blog Posts

Service Procurement in centralized maintenance planning

You must be Logged on to comment or reply to a post.

December 12, 2012 at 5:17 am

December 12, 2012 at 5:23 am

December 12, 2012 at 9:48 am

Good Document to learn cost permit functionality.

January 7, 2013 at 8:14 am

January 22, 2013 at 12:47 pm

January 22, 2013 at 3:58 pm

March 7, 2013 at 1:54 am

Costs and Currencies

Characteristics form AND conditions

Table T357G_GR – PM: Permit Groups

* determine permit class

April 3, 2013 at 6:08 am

May 6, 2013 at 7:32 am

June 8, 2013 at 9:46 am

November 7, 2013 at 11:28 am

November 21, 2013 at 9:37 pm

Former Member | Post author

November 22, 2013 at 8:12 am

February 12, 2014 at 10:37 am

April 1, 2014 at 12:26 pm

April 6, 2014 at 7:15 am

Andre Luiz Vieira

September 1, 2014 at 2:09 pm