- SAP Community
- Products and Technology
- Enterprise Resource Planning
- ERP Q&A
- User exits in PM
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
User exits in PM
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 07-02-2008 1:04 PM
Hi guys,
Any one can tell me the detailed procedure for user exits which are using in PM module, i want ti have a clear idea of user exit with example. Plz mention the path of using user exits.
Regards,
Rajesh
- SAP Managed Tags:
- PLM Enterprise Asset Management (EAM)/Plant Maintenance (PM)
Accepted Solutions (0)
Answers (4)
Answers (4)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Develop Enhancements
The following standard enhancements are available for Plant Maintenance
and Customer Service:
Area: Equipment
o IEQM0001 Additional checks when installing equipment at functional
locations
o IEQM0002 Additional checks when defining equipment hierarchies
o IEQM0003 Additional checks before updating equipment
o IEQM0004 Object permitted for contract partner (Order -> Maintenance
contract)
o IEQM0005 Object permitted for SD contract (Maintenance contract ->
Maintenance contract)
o IEQM0006 Object permitted for SD contract (maintenance of
maintenance contract)
o IEQM0007 Check/change to manufacturer field for equipment status
o IHCL0001 Create equipment with material template:
Classes/Characteristics
o ILOM0002 Structural check and correction of location numbers
Area: Functional locations and reference functional locations
o ILOM0001 Additional checks before updating functional location
o ILOM0002 Structure check and correction of location numbers
Area: Technical Objects
o ITOB0001 Include subscreen for master data of technical objects
o ITOB0002 Field changes to copy template
Area: Fleet Management
o ITOB0003 Include subscreen for fleet data
o ITOB0004 Fleet object identification data - checks
Area: Installation
o IB020001 Filter components
o IBPP0001 Filter components when generating from PP data
Area: Measuring points/measurement documents
o IMRC0001 User-specific processing for update
o IMRC0002 Menu exit - measuring point
o IMRC0003 Menu exit - measurement document
o IMRC0004 Exit for standard checks for new measurement document
o IMRC0005 Exit in AUTHORITY_CHECK_IMPT for measuring point
Area: Serial numbers
o IQSM0001 Automatic serial number assignment
o IQSM0002 Check when copying object list
o IQSM0003 Customer exit for additional data
o IQSM0004 Customer exit after leaving serialization screen
o IQSM0005 Customer exit in update
o IQSM0007 Customer exit for goods movements
o IQSM0008 Character string check
Area: Maintenance planning
o IPRM0002 Determinination of planned date information for maintenance
plan
o IPRM0003 User fields: Maintenance plan
o IPRM0004 Maintenance plan/item: Customer check for "Save"
o IPRM0005 Determine offset for performance-based strategy plans
Area: Maintenance and service notifications
o IWOC0001 Creation of maintenance/service notification: Determination
of reference object
o IWOC0002 Maintenance/service notification: Check permission for
status change
o IWOC0003 Maintenance/service notification: Authorization check for
reference object and planner group
o IWOC0004 Change ALV settings for list editing of PM/QM/CS
o ICSV0002 Automatic task determination for service notifications
o ICSV0004 Check reference object and display object information
o QQMA0001 User subscreen for notification header
o QQMA0008 User subscreen for additional data for notification item
o QQMA0010 User subscreen for additional data for cause
o QQMA0011 User subscreen for additional data for task
o QQMA0012 User subscreen for additional data for activity
o QQMA0014 Checks before saving notification
o QQMA0015 Customer exit before calling up F4 Help for catalog
o QQMA0016 Function "User data" - menu "Goto -> Tasks"
o QQMA0017 Function "User data" - menu "Goto -> Activity"
o QQMA0018 Scheduling according to entry of priority
o QQMA0019 Default partner when adding notification
o QQMA0021 Function "User data" - menu "Goto"
o QQMA0022 Function "User data" - menu "Goto -> Cause"
o QQMA0023 Function "User data" - menu "Goto -> Item"
o QQMA0024 Deactivation of function codes in CUA menu
o QQMA0025 Default values when adding notification
o QQMA0026 Authorization check when entering notification transaction
o QQMA0027 Default values when adding task
Area: Maintenance and service orders
o IWO10001 Creation of maintenance sub-order
o IWO10002 Maintenance order: Customer check for order release
o IWO10004 Maintenance order: Customer check for order completion
o IWO10005 Maintenance order: Customer-specific determination of
profit center
o IWO10006 Maintenance order: Exclusion of function codes through
customer enhancements
o IWO10007 Maintenance order: Customer enhancement for permits in
order
o IWO10008 Maintenance order: Determination of tax jurisdiction code
o IWO10009 Maintenance order: Customer check for "Saving"
o IWO10010 Maintenance order: Determination of WBS element
o IWO10011 Maintenance order: Component selection
o IWO10012 Maintenance order: Priority treatment on central header
o IWO10015 Maintenance order: F4 Help for user fields on operation
o IWO10016 Maintenance order: Check of operation user fields
o IWO10017 Determination of external order number by customer logic
o IWO10018 Maintenance order: User fields on order header
o IWO10020 Maintenance order: Automatic inclusion of task list
o IWO10021 Automatic task list transfer for order creation for
notification
o IWO10022 Determine calendar from customer exit
o IWO10023 Service order: Changes to header data for advance shipment
o IWO10024 Service order: Changes to items for advance shipment
o IWO10025 Maintenance/service order: Determination of responsible
cost center
o IWO10026 User check when setting status "Do not perform"
o IWO10027 Generate user-specific settlement rule
o IWO10029 Inclusion of bill of material in maintenance/service order
o IWO10030 Pre-filling the fields for the result object
o IWO10031 Hiding the employee number in the maintenance-/service
order
o IWO10033 Customer-specific authorization check maintenance-/service
order (triggered by BAdI IWO1_ORDER_BADI)
o IWO10034 Operation status based on the status of the capacity
requirement
o COI20001 Change of persons determined
o COI20002 Alternative procurement of the employee availability data
o CYPP0001 Change of the sequential criteria and the sequential
planning
o IWO20001 Maintenance order: Task list transfer in order
o ICSV0004 Check maintenance object and display object information
o CNEX0013 Maintenance order: Proposal for item category for component
assignment
o CNEX0026 Maintenance order: General check for material
o CNEX0027 Maintenance order: Determination of plant or storage
location for component
o COZF0001 Maintenance order: Change purchase requisition for external
operation
o COZF0002 Maintenance order: Change purchase requisition for external
component
Area: Maintenance order confirmations
o CONF0001: Deactivation of functions
o CONFPM01: Determine customer-specific default values
o CONFPM02: Customer-specific entry checks 1
o CONFPM03: Customer-specific check by operation selection
o CONFPM04: Customer-specific entry checks 2
o CONFPM05: Customer-specific additions when saving
o CMFU0001: Determine customer-specific screen layout
o CMFU0002: Set parameters for time confirmation and goods movements
Area: CATS
o CATS0001: Structure of worklist
o CATS0002: Enhancement of data entered
o CATS0003: Verification of data entered
o CATS0004: Deactivate functions in the interface
o CATS0005: Customer field enhancements
o CATS0006: Verification of overall time sheet
o CATS0007: Subscreen on initial screen
o CATS0008: Determination of workflow recipients for permit
o CATS0009: Individual customer text fields on entry screen
Area: Warranties
o BG000001 Warranty check
o BG000002 Warranty check - dialog box
o BG000003 Change of warranty check result - subscreen
Area: Partners
o ICSV0001 Display of geographical location data
o ICSV0003 Partner selection
o ICSV0007 Partner transfer of serial numbers for goods issue and
returns
o ICSV0008 Verification of additional partner types
o IEQM0004 Object permitted for contract partner (Order -> Maintenance
contract)
o IEQM0005 Object permitted for SD contract (Maintenance contract ->
Maintenance contract)
o IEQM0006 Object permitted for SD contract (maintenance of
maintenance contract)
o IICRP0201 Search help CS_ORG_02: Authorization check
o IICRP0202 Search help CS_ORG_02: Self-programmed selection
o IICRP0203 Search help CS_ORG_02: Propose task
Area: Quotation creation and resource-related billing
o SIMG_OLPR_USERFAKTUR Enhancements for quotation creation and billing
o ICSV0005 Determination of reason for rejection for resource-related
billing
o KSDIEX01 Influence of creation of quantity structure for
resource-related billing before Release 4.5A
Area: Information Systems
o MCI10001 PMIS/QMIS update
Area: General
o IWMI0001 Customer exit for CS/PM-IDocs
o IMSMCOMM Customer exit for MSM communication
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Munny,
User/Customer exists provide the option of adding user defined functions to the standard SAP application.
These do not have any functions or built in code, infact we can include our own code depending upon the requirement ( user defined code)
Transaction : CMOD
Ex : Restricting Time entry field - Actual hrs in IW41 by 100 units
BAPI's are standard methods to access SAP objects. They are commonly used in intergrating with SAP - SAP and SAP -Non SAP systems.
Transaction : BAPI
Ex: Equipment will be created in SAP system from a business activity in Non SAP system (third party system)
Award if this was useful.
Thanks,
Harisha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello,
User eixt means Enhancing the standard functionality .
SAP has provided some includes in User exits which we can write our own code as per requirement with certain limits.
Ex: In the Work Order if you want to add some new field(like "MUNNY")it is possible through User exit.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Rajesh,
Unfortunately its not that straight forward..
There are user-exits, customer-exits, program-exits, BADIs, enhancement-spots, etc. Each has different TCodes e.g. SMOD, CMOD, SE18, SE19, SE38, etc.
There is also no easy way of finding all the user-exits for a given transaction e.g. IW31.
Have a [look|http://pjatkin.users.btopenworld.com/documents/PMCSUserExits.pdf] here for the most comprehensive list of PM/CS user-exits on the web.
PeteA
[www.pjas.com]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- SAP S/4HANA Cloud Public Edition 2402.2: Final What's New & Product Assistance available in Enterprise Resource Planning Blogs by SAP
- fpo4: additional fields for item list are required in Enterprise Resource Planning Q&A
- migration jobs in S/4HANA Cloud troubleshooting in Enterprise Resource Planning Q&A
- Data migration approach for Open PO and Contract in Public Cloud in Enterprise Resource Planning Q&A
- Total value of the sale order is not equal to the Sum of Total Item Net Value and Tax. in Enterprise Resource Planning Q&A
| User | Count |
|---|---|
| 100 | |
| 11 | |
| 11 | |
| 6 | |
| 6 | |
| 5 | |
| 4 | |
| 3 | |
| 3 | |
| 3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.