Condition Baserd maintenance

Dear Sir
      My client is having SAP ECC 6.0 They want to go for implementing  Condition based maintenance.
     I know this is available in PLM. How to implement in ECC. Please suggest any software up gradation for this PM-PCS interface or any other methodology to implement condition based maint.
  Your valuable suggestion is most welcome.
Regards

Hello,
If you want to transfer data for the counter through the interface then you can use the interface or you can enter the data manually through IK11.
For a bit description.
1. Create one maintenance strategy in IP11.
2. Give it a suitable key like C description Condition based
3. Assign packages to this strategy as I took in above example.
4. Create one measurement point as counter through IK01 for the particular equipment or FL.
5. Create one maintenance plan through IP01(If you have the task list then assign it to plan or you can create the task list from here also) by using that strategy and give the particular values for call horizon and offset.
6.Schedule the Plan through IP10 from current counter reading.
Now system will calculate a date from annual estimate and current reading.
You need to refresh the plan all the time when you enter a document for counter if not using deadline monitoring.
For more details on planning go through the below link:
[Maintenance Planning|http://help.sap.com/saphelp_47x200/helpdata/en/b0/df293581dc1f79e10000009b38f889/frameset.htm]
Thanks
Naveen

Similar Messages

  • Condition based maintenance

    Hi Gurus,
    As per my business needs
    Measuring document needs to be updated automatically from proleit (Another system) by IDOC-Pls let me know from our PM end what we have to do?
    Condition based maintenance (As per proleit system measuring document would be updated and determine the condition for automatic notification creation)-Pls suggest how to map the both scenario. if possible pls send the relative documents

    Hi,
         You will have to activate User exit IMRC001  -This gets triggered when measuring document is posted via IK11
    You will have to create a measureing point for the eqpt ..
    In the above user exit you can find sample code which would be helpful
    In config spro ->pm - basic settings -->measuring points & counters  ->Define Measuring point categories, here for a category mention the Tolerance period , if there is any ..
    regards
    giri

  • Condition Based Maintenance Plans

    Dear All,
    My client has the requirement of condition based maintenance plans without interfacing etc. An example is described below:
    Compressor bearing has temperature limits of 70 deg C and 90 deg C. If measurement document reading is recorded outside the range specified here a maintenance call / maintenance order should be triggered.
    Please give an example or process for the above dsicussed condition based maintenance plan upto two or three calls.
    Thanks and Regards,
    Saif Ali Momin

    Hi,
    As such there is no functionality directly. You can use the following user exits and can develop your on logic to trigger notification in case measured values are out of tolerance values.
    IMRC0003 Menu exit - measurement document
    As I remember there is sample code available for ythe same. You can check through SMOD transaction.

  • Condition based maintenance plan

    Dear Experts,
    Can anybody clarify me about the condition based maintenance plan?
    How the plan is created and measuring points and measuring documents are controlled?
    My requirement is as follow:
    I have one equipment, for that equipment I have created a measuring point (Temp) with counter. And the engineer enters the measuring document for that equipment.
    Here when the measuring reading reaches certain level, say Temp reaches more that 80 Degree C, i.e., a measuring document is entered for the measuring point with a reading of 82 Degree C, system should generate a maintenance order for that equipment?
    How the above scenario is addressed in SAP?
    Please help me out.
    Thanks in Advance,
    Regards.

    Hi all,
    Thanks for your replies.
    PS: Ramesh,
    The operator maintains the log sheet of the equipments out side SAP, since he doesn't have the access to the SAP system. All the details are entered by Maintenance Engineer or Supervisor. The same log sheet details are entered by them in the system.
    Will you please clarify me on thing:
    *need to specify the min & max level in your measurement point at which u want to get call*
    how can we specify the min & max levels in measuring point? Is it possible through customer exit only? Because I did not able to find those filed in the measuring point master data.
    Regards..

  • Selection condition in maintenance view

    I have one table with data related to 5 systems.
    MSF, RET, SER, BOB, SAV, LED.
    I need t o create views with related data for each system. But system BOB contains data related to MSF and RET, So instead of creating view for that i have to add MSF related data to MSF view and RET related data to RET view from BOB system. These all are from one table only.Can you please suggest me the selection condition for that in maintenance view.
    Thanks.

    thanks

  • Condition based Maintenance for crusher

    Hi Experts,
    Need a suggestion & help in one of the requirement I have in my hand. The scenario is more of a common but I have tried many of options but failed to gather the desired results. The requirement is as below.
    The Maintenance of crushers are based on Gaps
    The allowable gap is 6 to 14 Inch.
    When the gap reaches 14", a maintenance order should be generated. Maintenance will feed the gap as a measurement document in the system.
    And, after overhauling ; the counter will be reset to 6" & process of measurement continues till 14" when another call will be generated.
    Please help me in mapping the process.
    Best Regards,
    Srini

    And, I need to have an object called when my Counter Reading is 14". I can handle the Total Counter reading by Replace function & not concerned about the same. The catch here is when the Counter Reading (I.e : GAP) is greater than or equal to 14" ; I should be able to call an object.
    I tried using IK01, then create an initial reading (IK11) , then create single cycle plan with 14" as the cycle with TL in the Plan. Then when I am entering any value for 14" or more & then running IP30, still I am not getting any Orders generated. My scheduling parameters are as below.
    Hope, this gives a clear idea of my requirement.
    Appreciate your help.
    Regards,
    SP

  • Dates in the condition record maintenance for the condition type?

    Hi,
    Condition type has the following dates when maintaining the condition record,
    Valid from date:
    Valid on :
    Please ellaborate on the  above dates?
    Thanks

    Dear Rajiv
    Valid from date:-   The date from which the said condition type is applicable.  For example, in VK11, if you changed (let us assume PR00 changed to Rs.250 from 200) a condition with a date as  01-06-08 in the above field, only from 1st of June'08, whatever sale orders you generated, revised value of Rs.250 will flow in the respective sale orders.  Whatever created b4 1st June'08 will be having Rs.200.
    Valid on :-  As in the above case, if you input a date as 30-05-08 for the above condition type, system will populate Rs.200/- and if you input 01-06-08, it will propose Rs.250/-.
    Hope this explanation is suffice for you to understand the difference between the two fields.
    thanks
    G. Lakshmipathi

  • Condition Record maintenance Doubt

    Dear SD collegures,
        when i maintain a basic price condition record for example Pr00 i maintained material 'A' is costing 100. then Today i changed the value to 98 and 100 rupees validity is changed to yesterday. then i give new price 98 is valid from today. after saving when i go back and see the condition record it says no record found.
    Kindly throw some light
    regards,
    Sudhir

    Dear Sudhir,
    Try this,
    You first change the validity date of 100 rupees with yesterday date
    Now you go through VK11 transaction maintain new condition record for 98 rupees with validity from Taday's date.
    I hope this will help you,
    Regards,
    Murali.

  • Error during condition record maintenance EXEM

    Hello Guys,
    I am trying to maintain condition records for the condition type EXEM. I am getting an error during this process.
    When I get into VV11 and enter the condition type EXEM and hit enter, I get the list of key combinations. For any key combination I select and press enter, I get an error and the following log details. Please find the log details below. Any inputs to fix this error during condition maintenace would be appreciable. The config is maintained perfectly and does not indicate any error.
    Thanks
    Venkat
    Status      Note
    Information     882 Coding generator started                                                                               
    Information     851 Report RV13B998 saved                                                                               
    Information     883 Text pool for report RV13B998 written in language E                                                              
    Error           806 Report RV13B998 has a syntax error                                                                               
    Information     722 Text pool for program RV13B000 does not exist in language 0                                                      
    Information     883 Text pool for report RV13B998 written in language 0                                                              
    Information     883 Text pool for report RV13B998 written in language 1                                                              
    Information     722 Text pool for program RV13B000 does not exist in language 2                                                      
    Information     883 Text pool for report RV13B998 written in language 2                                                              
    Information     883 Text pool for report RV13B998 written in language 3                                                              
    Information     722 Text pool for program RV13B000 does not exist in language 4                                                      
    Information     883 Text pool for report RV13B998 written in language 4                                                              
    Information     722 Text pool for program RV13B000 does not exist in language 5                                                      
    Information     883 Text pool for report RV13B998 written in language 5                                                              
    Information     722 Text pool for program RV13B000 does not exist in language 6                                                      
    Information     883 Text pool for report RV13B998 written in language 6                                                              
    Information     722 Text pool for program RV13B000 does not exist in language 7                                                      
    Information     883 Text pool for report RV13B998 written in language 7                                                              
    Information     722 Text pool for program RV13B000 does not exist in language 8                                                      
    Information     883 Text pool for report RV13B998 written in language 8                                                              
    Information     722 Text pool for program RV13B000 does not exist in language 9                                                      
    Information     883 Text pool for report RV13B998 written in language 9                                                              
    Information     722 Text pool for program RV13B000 does not exist in language A                                                      
    Information     883 Text pool for report RV13B998 written in language A                                                              
    Information     722 Text pool for program RV13B000 does not exist in language B                                                      
    Information     883 Text pool for report RV13B998 written in language B                                                              
    Information     883 Text pool for report RV13B998 written in language C                                                              
    Information     883 Text pool for report RV13B998 written in language D                                                              
    Information     883 Text pool for report RV13B998 written in language E                                                              
    Information     883 Text pool for report RV13B998 written in language F                                                              
    Information     722 Text pool for program RV13B000 does not exist in language G                                                      
    Information     883 Text pool for report RV13B998 written in language G                                                              
    Information     883 Text pool for report RV13B998 written in language H                                                              
    Information     722 Text pool for program RV13B000 does not exist in language I                                                      
    Information     883 Text pool for report RV13B998 written in language I                                                              
    Information     883 Text pool for report RV13B998 written in language J                                                              
    Information     722 Text pool for program RV13B000 does not exist in language K                                                      
    Information     883 Text pool for report RV13B998 written in language K                                                              
    Information     883 Text pool for report RV13B998 written in language L                                                              
    Information     883 Text pool for report RV13B998 written in language M                                                              
    Information     883 Text pool for report RV13B998 written in language N                                                              
    Information     883 Text pool for report RV13B998 written in language O                                                              
    Information     883 Text pool for report RV13B998 written in language P                                                              
    Information     883 Text pool for report RV13B998 written in language Q                                                              
    Information     883 Text pool for report RV13B998 written in language R                                                              
    Information     883 Text pool for report RV13B998 written in language S                                                              
    Information     883 Text pool for report RV13B998 written in language T                                                              
    Information     722 Text pool for program RV13B000 does not exist in language U                                                      
    Information     883 Text pool for report RV13B998 written in language U                                                              
    Information     883 Text pool for report RV13B998 written in language V                                                              
    Information     722 Text pool for program RV13B000 does not exist in language W                                                      
    Information     883 Text pool for report RV13B998 written in language W                                                              
    Information     722 Text pool for program RV13B000 does not exist in language X                                                      
    Information     883 Text pool for report RV13B998 written in language X                                                              
    Information     722 Text pool for program RV13B000 does not exist in language Y                                                      
    Information     883 Text pool for report RV13B998 written in language Y                                                              
    Information     722 Text pool for program RV13B000 does not exist in language a                                                      
    Information     883 Text pool for report RV13B998 written in language a                                                              
    Information     722 Text pool for program RV13B000 does not exist in language b                                                      
    Information     883 Text pool for report RV13B998 written in language b                                                              
    Information     722 Text pool for program RV13B000 does not exist in language c                                                      
    Information     883 Text pool for report RV13B998 written in language c                                                              
    Information     722 Text pool for program RV13B000 does not exist in language d                                                      
    Information     883 Text pool for report RV13B998 written in language d                                                              
    Information     722 Text pool for program RV13B000 does not exist in language i                                                      
    Information     883 Text pool for report RV13B998 written in language i                                                              
    Status      Note
    Information     884 Screen generator started                                                                               
    Information     860 Screen SAPMV13B 1998 saved                                                                               
    Information     858 Screen SAPMV13B 1998 generated                                                                               
    Status      Note
    Information     890 Text field for field INSMK not found                                                                             
    Information     860 Screen SAPMV13B 2998 saved                                                                               
    Information     858 Screen SAPMV13B 2998 generated

    What part of the code would you like?
    It says there is an error in Report RV13B998. This is part of standard.
    Thanks
    Venkat.

  • Condition based mainten

    hi all ,
    i have two querries...
    1.It was given in help.sap. tht system can create notification automatically whenever measuring value of a measuring point exceeds the target value,but i could not find the setting... any idea on how this can be done.
    2.Can we maintain confirmation for PRT in PM MO confirmation?
    regards
    pushpa

    Hi,
    You can use following developments as per your requiremnts.
    IMRC0001                                MeasPoint/MeasDoc: Exit before update (after COMMIT WORK)
    IMRC0002                                MeasPoint: Menu exit for customer-specific function
    IMRC0003                                MeasDoc: Menu exit for customer-specific function
    IMRC0004                                Measure.doc.:Exit according to stndrd checks for new mes.doc
    IMRC0005                                Measure point: Exit in AUTHORITY_CHECK_IMPT
    Business Add-in
    IMRC_CHANGE_CHECK                       Additional Checks of Measurement Documents/Points
    IMRC_REF_POINT_BADI                     Activate Reference Measuring Point
    IMRC_STATUS_CHECK                       BAdI for Additional Status Checks for Measuring Documents
    Ramesh
    Edited by: RameshChandra  Soni on Jun 13, 2008 8:23 AM

  • Triggering of Preventive Maintenance based on Measuring Point

    Hi,
    I have set measuring point & defined upper range limit and lower range limit. Now I want to trigger preventive maintenance, based on reading enter against measuring point specifically if measuring point reading is above or below defined upper range limit or lower range limit.
    Letu2019s say example, If 10 and 5 is upper range limit and lower range limit, now in this case creation of notification / main order if user has enter measuring point value more than 10 or less than 5.
    Regards,
    Dipen Shroff

    Hi,
        You can do it via Condition Based Maintenance ..
    IMRC0001- U can use this User exit
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/a7/fa4c988f6611d29e8a0000e8323350/frameset.htm
    regards
    pushpa

  • Condition record exists, but has not been set

    Hi
    in the pricing analysis this is the explanation i got.
    the reasons could be an Condition record overflow  or the condition record wpuld have been created after the documnet is created.
    But i found the record has been mainatined earlier to the creation of document.
    this was for MWST condition type in IS Oil. where the tax rate manatined for this condition record is zero%
    Since this is a mandatory condition, the document could not be completed.
    Your help in this regard is highly appreciated.
    thanks
    C.Sivakumar

    Hi,
    Check the pricing procedure for the condition type MWST. Whether this condition is taken from any prevoius steps
    (check the from and to for the condition type MWST).
    If this condition is with reference to somw other condition, then check whether that condition is maintianed or not?
    Check the condition record maintenance in VK13, did you maintian the right access?
    Prase

  • Pricing ZCondition Types are not appearing in Condition Record Maintanence

    Hi All,
    We have a requirement in SAP CRM Opportunity Management where the pricing determination should happen. So, to facilitate the requirement we have done the following
    Downloaded the DNL_CUST_CNDALL and DNL_CUST_CND from ECC to CRM
    But the Problem is when I am trying to maintain the Condition record in T-Code "/SAPCND/GCM" 　our Z-Condition types are not appearing in the list, also in Product Master Condition Tab.
    Please suggest me how to resolve this issue.
    Regards,
    karthik J

    Hi Karthik,
    As a best practice -
    1. If you are downloading the condition type and pricing procedure from ECC, then it is advisable to use ECC as a master system for all your Z condition type/condition record maintenance.
    2. Similarly if you are using Pricing procedure as of ECC, then ensure that the downloaded pricing procedure in CRM is used for pricing procedure determination.
    3. The condition record in T-Code "/SAPCND/GCM" is advisable to use if you are mainly using CRM Pricing.
    By looking at your problem statement you are using ECC pricing procedure, condition types by downloading it to CRM.
    If you have any other comments to make, please give the exact problem statement or any appropriate problem screenshot for further analysis.
    Hope this will be useful
    Thanks and Regards
    DJ

  • Tax code linking with account mapped to condition type in vkoa

    Hi,
    I created two new discount condition types and mapped an account in vkoa as per client's requirements. There is no field for tax code in the condition record maintenance screen. However, on creation of billing document I am getting error 'No taxes on sales/purch. are allowed for account 416010 TCL, A4 is not allowed.' Message no. FS217. Is there any setting in FI linking the account with the tax code? Or should I check any SD settings?
    Thanks,
    Kasturi

    hi,
    according to the error message
      message e217(fs) with v_accrac-hkont
                            v_accrac-bukrs
                            v_accrac-acctax.
          MESSAGE e217(fs) WITH i_hkont i_bukrs i_mwskz
                  RAISING no_tax_code.
        MESSAGE e217(fs) WITH i_hkont i_bukrs i_mwskz
                RAISING no_tax_code.
    this are two programs which are affected with the respective TAX CODES.
    check FTXP for the same.
    please check and confirm
    balajia

  • Condition type MWST

    Hi Friends,
    We set up condition type MWST (output tax) for our European customers. The rate is 17.5%.
    Our issue is for some customers we won't charge 17.5% at all. (two scenarios could apply to one customer)
    My question is
    Is that possible that I am able to set up this condition type with a default of 17.5%, and be able to change it at ltem level to 0% whenever I needed?
    Thanks you for your help in advance.
    Linda

    Hi Linda,
    For the same scenario: same customer, same material, same country, the same rate should apply, so I think you can do this depending on the values you set in your master data.
    If this is not the case, create a new condition by copy of MWST, let's say ZWST, and on condition type maintenance (SPRO -> Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control -> Define Condition Types -> Maintain Condition Types) allow manual changes on field 'Manual Entries'.
    Assign it to your pricing procedure and you should be able to perform this change.
    Regards,
    Joã

Maybe you are looking for