Presentation on theme: "Refurbishment Management"— Presentation transcript:
1Refurbishment Management SAP Best Practices for Chemicals
2Purpose, Benefits, and Key Process Steps Faulty repairable spares is maintained to re-use in company, the spare part will have different valuation type to represent different valuesBenefitsA high value spare part or critical part, will be managed with serial number. It will help to manage each piece of this spare partRefurbishment process will help to reduce the spare parts inventory costThe refurbishment of high value faulty repairable spares is of considerable economic importance for the companies . It is much more cost-effective than a brand new purchase.Key process flows coveredCreation of Maintenance OrderRemoving Defective EquipmentReturning Defective material to warehouseGoods Issue for Maintenance OrderActivate EquipmentCreating the Refurbishment Order for the Defective materialGoods Issue for Refurbishment OrderOrder ConfirmationGoods Received for Refurbishment OrderCompleting, Settling, and Closing the Refurbishment Order
3Required SAP Applications and Company Roles SAP ECC 6.00 enhancement package 5Company RolesWarehouse clerkMaintenance Employee
4Detailed Process Description Refurbishment ManagementIn this scenario, a spare part will be procured and installed in the function location as an equipment. Serial nos. can also be assigned to the procured material. These repairable spare parts can be identified with different valuation types like New(C1), Repaired(C2) and Damaged(C3) with corresponding cost assignments.When there is a malfunction of the installed equipment, it will be dismantled from the functional location and a spare part / equipment can be withdrawn and installed at the functional location. The defective equipment will be returned as damaged item to the warehouse(Valuation type C3). The stock in the warehouse will be automatically updated(with valuation types) and with corresponding cost.The maintenance planner will create a refurbishment order. The defective repairable spare(Valuation class C3) will be withdrawn from the warehouse and will be repaired. When the refurbishment is finished, the equipment will be returned to warehouse as repaired material (Valuation type C2) and the cost will be updated accordingly in the material master. After the settlement of the refurbishment order, the maintenance expense will be settled to the specific material, then the moving average price of this spare will be updated in the material master. So the moving average price of this spare will vary during the different phases of refurbishment.After the settlement of the refurbishment order, the maintenance expense is settled to the specific material. The moving average price of this spare is updated in the material master. The moving average price of this spare varies during the different phases of refurbishment.
5Refurbishment Management Process Flow DiagramRefurbishment ManagementEventMalfunction of EquipmentChemicals: Maintenance SpecialistCreate Standard Maintenance OrderActivating Equipment View for New Pump and InstallCreate Refurb Order for Defective PumpGoods Receipt of Refurbished MaterialChecking Material StockTechnically Complete the OrderRemove Defective PumpTime ConfirmationSettle the OrderClose the Order (Optional)Warehouse ClerkReturn Defective Pump to WarehouseGoods Issue with New Pump with Serial NumberMaterial Withdrawal for RefurbishmentDisplay Material
6Legend Symbol Description Usage Comments Symbol Description Band: Identifies a user role, such as Accounts Payable Clerk or Sales Representative. This band can also identify an organization unit or group, rather than a specific role.The other process flow symbols in this table go into these rows. You have as many rows as required to cover all of the roles in the scenario.Role band contains tasks common to that role.External Events: Contains events that start or end the scenario, or influence the course of events in the scenario.Flow line (solid): Line indicates the normal sequence of steps and direction of flow in the scenario. Flow line (dashed): Line indicates flow to infrequently-used or conditional tasks in a scenario. Line can also lead to documents involved in the process flow.Connects two tasks in a scenario process or a non-step eventBusiness Activity / Event: Identifies an action that either leads into or out of the scenario, or an outside Process that happens during the scenarioDoes not correspond to a task step in the documentUnit Process: Identifies a task that is covered in a step-by-step manner in the scenarioCorresponds to a task step in the documentProcess Reference: If the scenario references another scenario in total, put the scenario number and name here.Sub-Process Reference: If the scenario references another scenario in part, put the scenario number, name, and the step numbers from that scenario hereProcess Decision: Identifies a decision / branching point, signifying a choice to be made by the end user. Lines represent different choices emerging from different parts of the diamond.Does not usually correspond to a task step in the document; Reflects a choice to be made after step executionSymbolDescriptionUsage CommentsTo next / From last Diagram: Leads to the next / previous page of the DiagramFlow chart continues on the next / previous pageHardcopy / Document: Identifies a printed document, report, or formDoes not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow linesFinancial Actuals: Indicates a financial posting documentBudget Planning: Indicates a budget planning documentManual Process: Covers a task that is manually doneDoes not generally correspond to a task step in a document; instead, it is used to reflect a task that is manually performed, such as unloading a truck in the warehouse, which affects the process flow.Existing Version / Data: This block covers data that feeds in from an external processDoes not generally correspond to a task step in a document; instead, this shape reflects data coming from an external source; this step does not have any incoming flow linesSystem Pass / Fail Decision: This block covers an automatic decision made by the softwareDoes not generally correspond to a task step in the document; instead it is used to reflect an automatic decision by the system that is made after a step has been executed.Diagram Connection<Function>Hardcopy / DocumentExternal to SAPFinancial ActualsBudget PlanningBusiness Activity / EventUnit ProcessManual ProcessProcess ReferenceExisting Version / DataSub-Process ReferenceSystem Pass/Fail DecisionProcess Decision