SAP Learnings

 

 

REFERENCE DOCUMENTS FOR SAP

ORGANIZATION STRUCTURE (SPRO) Step - 1 Company - Company Code - (FICO) Plant - Plant Code - (FICO) Planning Plant -  (FICO) a. Centralized Plant - ( Have dedicated Planning Plant ) ex: for 3 Plant have 1 Single Planning Plant b. De-Centralized Plant - ( Plant it self Planning ) ex: Each plant planning for it Self c. Partially Centralized Plant - ( It has some actions from Centralized & Some from It Self) Work Center MASTERDATA -  WORK CENTER/FLOC/EQUPMENT/BOM/CLASS/CHAR/CATALOGUE/CODE GROUP/CODES/MEASURING POINTS/MEASURING DOC/TASK LIST/MAINTENANCE STRATAGIES/MAINTENANCE PLANS/PERMITS TRASACTIONAL DATA - BUSINESS PROCESS -  CORRECTIVE BREAKDOWN PREVENTIVE QUALITY REFERBUSHMENT INVESTMENT PREDECTIVE SHUTDOWN PLANS/WORK ORDERS/NOTIFICATIONS. REPORTS - ASAP/LSMW/FS PREPARATIONS

The Business Object Functional Location is an Organizational Unit with in the Logistics , the structures the maintenance Objects of a Company according to the Functional Location, Process - related or spatial Area Functional Location represents the place at which a maintenance tasks is to be performed . A Functional location represents the system area at which an object can be installed. Objects that can be installed at functional locations are called piece of equipment in SAP System.  Ex: assembly line, painting area, rolling section, workshops, furnace area, boiler section etc. A  functional   location  represents the area at which a piece of equipment can be installed.   Functional   location  represents a place in which a maintenance task has to be performed. Structuring the maintenance hierarchy of assets  is  very much necessary for the organization.  Functional   location s are created in hierarchical structures and thus allow a  functional  or process-oriented structuring of

Mean Time Between Failure (MTBF)   is a reliability term used to provide the amount of failures per million hours for a product. This is the most common inquiry about a product’s life span, and is important in the decision-making process of the end user. MTBF is more important for industries and integrators than for consumers. Most consumers are price driven and will not take MTBF into consideration, nor is the data often readily available. On the other hand, when equipment such as media converters or switches must be installed into mission critical applications, MTBF becomes very important. In addition, MTBF may be an expected line item in an RFQ (Request For Quote). Without the proper data, a manufacturer’s piece of equipment would be immediately disqualified. Mean Time To Repair (MTTR)   is the time needed to repair a failed hardware module. In an operational system, repair generally means replacing a failed hardware part. Thus, hardware MTTR could be viewed as mean time to replace

NOTIFICATION TYPES M1 - Maintenance request M2 - Malfunction report M3 - Activity report GO - General notification ORDER TYPES PM01 - Corrective Maintenance Order PM02 - Breakdown Maintenance Order PM03 - Preventive Maintenance Order PM04 - Refurbishment Order PM05 -  Calibration order PM06 -  Investment order PM07 -  Shutdown Order Note: The PM01,PM02,PM03 will be vary according to the business requirements. for Ex: Some Org's are maintain the PM02 Is preventive, Some are maintain as PM01 is Preventive ORDER CATOGERY 10 - Production Order 20 -  30 - Maintenance Order CONTROL KEYES PM01 - Internal Processing PM02 - External Processing PM03 - Refurbishment of Repairable Spares

       S.NO CORRECTIVE MAINTENANCE 1 NOTIFICATION IW21 2 ORDER IW32 3 CALCULATE THE COST 4 SCHEDULING 5 COMPLETE THE NOTIFICATION 6 CONFIRMATION OF ORDER IW41 7 OVERHEAD CALCULATION KGI2 8 TECHNICAL COMPLETION 9 SETTLEMENT OF ORDER KO88 10 BUSINESS CLOSURE OF ORDER

It's an ordinary corrective maintenance cycle but it differs in the following: Mark the breakdown check box  Make sure that the technical object start-up date field is not empty At the completion of the order fill in the malfunction end date and time fields Create malfunction report ( technician in field) The process flow is as follows Release malfunction report (by engineering department) Create breakdown maintenance order (pm01) or whatever the order type set is customized Confirm operations And goods movements Technically complete the order  Settle the order  Complete the business closure Monitor the breakdown analysis - MTTR(Mean Time To Repair)/MTBR(Mean Time Between Replacement) MCI7 - Breakdown Analysis by Equ/Floc/Object Class/Period  MCJB - through Equipment MCJC - through Functional location  T-CODES Before monitoring make sure that the s070 info structure is updated by the period you want And make sure that the object information is customized for only  1 completed orde

  After releasing the maintenance order in SAP PM planned cost is not showing in the cost overview      Activity price is maintained KP26, costing and valuation variants are maintained in configuration, Check control key entered in operations allows costing, Check whether valuation categories are maintained in configuration. For the estimated cost you can directly enter the cost in the maintenance

First create the Material BOM by using T-Code of CS01 Select BOM Usage as " 4" on the initial screen. It Indicates that the Material BOM will be used in the Plant maintenance Module, If select the some other BOM Usage then the list of material will not be available in the maintenance Order Go to the main header screen of Material BOM. Here you can Maintain the entries of Material numbers With respect to the Each material we can maintain the quantity and Item Category. Item Category indicates whether material will be issued from warehouse or it will be purchased from external vendor. It Item category is "L"   then material will be issued from ware house with reference to the reservation. How ever, If item category is "N" then material will be purchased through a purchase requestion from from external vendor SAVE Material BOM Note down the material BOM header ID Now go to the equipment master main header screen by T-code IE01/02 Click on the Structure TAB Th

Introduction Data on problems, malfunctions, damages, causes and problem solutions or malfunction corrections is recorded in the system or reported to the planner  responsible in the form of technical findings after a visual check, after the object has been inspected or checked, or the problem has been determined. This data forms part of the service or maintenance notification and is entered in the maintenance history. Catalog profile will group different characteristics of the notification which will cater the needs of management to analyses the company assets & to ascertain the decisions accordingly. Catalog profiles have sub class of code groups which will group the codes as per their feature. All the codes (Damage, Cause, Task & Activities) illustrate why an asset failed during production, what is the cause for that failure, tasks to be performed & activities done for that failure. The use of codes in a SAP system ensures a consistent way of documenting the key aspects