Ad
More Related Content
What's hot (20)
Viewers also liked (20)
![Oracle Fusion applications 101 [2010 OAUG Collaborate]](https://cdn.slidesharecdn.com/ss_thumbnails/fusionapplications101-100423004647-phpapp01-thumbnail.jpg?width=560&fit=bounds)
Ad
Similar to Oracle ebs r12 eam module-upk (20)
Ad
More from jcvd12 (11)
Recently uploaded (20)
Oracle ebs r12 eam module-upk
- 1. Oracle EBS R12.1 eAM Entreprise Asset Management Setting Up EAM Cédric Beltrame, PMP - 2012 Oracle is a registered trademark of Oracle Corporation and/or its affiliates 1
- 2. Agenda • This module covers the required setup tasks to use Oracle Enterprise Asset Management. In addition, this module covers many of the core transactions and business processes you may perform while using Oracle Enterprise Asset Management. • Upon completion of this module, you will be able to: – Set up Oracle Enterprise Asset Management. – Perform other asset setup tasks. – Use the Activity Workbench. – Perform other EAM setup transactions. – Set up non-stock direct items. – Set up preventive maintenance. – Set up work order billing. – Use eAM work management. – Use eAM work order planning. – Perform preventive maintenance transactions. – Use eAM Planning and Scheduling. – Use eAM Cost Management. – Generate eAM cost variance reports. – Enable direct item procurement for eAM work orders. – Use eAM Contractor Services. – Use eAM Project Manufacturing. – Use self-service transactions. – Use the Maintenance User Workbench. – Perform Maintenance Super User transactions. – Use stores. 2
- 3. Setting Up EAM 3
- 4. Setting Up Organizations • A valid organization is required for the setup of Oracle Enterprise Asset Management (eAM). Decisions are made during implementation as to which organizations are enabled for Oracle Enterprise Asset Management. • In this topic, you will define an organization. 4
- 10. Setting Up Organizations 10
- 11. Setting Up Organizations 11
- 12. Setting Up Organizations 12
- 13. Setting Up Organizations 13
- 14. Setting Up Organizations 14
- 15. Setting Up Organizations 15
- 16. Setting Up Organizations 16
- 17. Setting Up Organizations 17
- 18. Setting Up Organizations 18
- 19. Setting Up Organizations 19
- 20. Setting Up Organizations 20
- 21. Setting Up Organizations 21
- 22. Setting Up Organizations 22
- 23. Enabling Organizations for Enterprise Asset Management You can create a new Enterprise Asset Management (eAM) enabled organization, or convert an existing organization to an eAM-enabled organization. Oracle recommends that you keep Enterprise Asset Management organizations separate from production organizations. Enterprise Asset Management parameters are on the Inventory Parameters tab, within the Organization Parameters window. Before you begin implementing eAM, decide which organizations are eAM-enabled. A valid organization must exist before you can enable the organization for Enterprise Asset Management. In this topic, you will enable an organization for eAM. 23
- 24. Enabling Organizations for Enterprise Asset Management 24
- 25. Enabling Organizations for Enterprise Asset Management 25
- 26. Enabling Organizations for Enterprise Asset Management 26
- 27. Enabling Organizations for Enterprise Asset Management 27
- 28. Defining eAM Parameters Once you have established an eAM-enabled organization, set up specific eAM parameters that determine the organization level defaults for individual transactions. Set up information such as asset number defaults, cost defaults, work request information, and work order defaults. Before creating eAM parameters, first create an asset subinventory in the current eAM-enabled organization using this navigation, Inventory > Setup > Organizations > Subinventories. In this topic, you will define eAM parameters. 28
- 29. Defining eAM Parameters 29
- 30. Defining eAM Parameters 30
- 31. Defining eAM Parameters 31
- 32. Defining eAM Parameters 32
- 33. Defining eAM Parameters 33
- 34. Defining eAM Parameters 34
- 35. Defining eAM Parameters 35
- 36. Defining eAM Parameters 36
- 37. Defining eAM Parameters 37
- 38. Defining eAM Parameters 38
- 39. Defining eAM Parameters 39
- 40. Defining eAM Parameters 40
- 41. Defining eAM Parameters 41
- 42. Defining eAM Parameters 42
- 43. Defining eAM Parameters 43
- 44. Defining eAM Parameters 44
- 45. Defining eAM Parameters 45
- 46. Defining eAM Parameters 46
- 47. Reviewing and Verifying Installed Base Parameters Oracle Enterprise Asset Management is integrated with Oracle Installed Base. Therefore, the Installed Base parameters must be set up to ensure that assets are created correctly in eAM. In this topic, you will review and verify the Oracle Installed Base parameters. 47
- 48. Reviewing and Verifying Installed Base Parameters 48
- 49. Reviewing and Verifying Installed Base Parameters 49
- 50. Reviewing and Verifying Installed Base Parameters 50
- 51. Reviewing and Verifying Installed Base Parameters 51
- 52. Reviewing and Verifying Installed Base Parameters 52
- 53. Reviewing and Verifying Installed Base Parameters 53
- 54. Reviewing and Verifying Installed Base Parameters 54
- 55. Reviewing and Verifying Installed Base Parameters 55
- 56. Reviewing and Verifying Installed Base Parameters 56
- 57. Reviewing and Verifying Installed Base Parameters 57
- 58. Reviewing and Verifying Installed Base Parameters 58
- 59. Reviewing Service Fulfillment Manager Parameters You have to set up the Service Fulfillment Manager (SFM) parameters for eAM. These parameters must be set up in order to process asset transfers accurately. In this topic, you will review the Service Fulfillment Manager parameters. 59
- 60. Reviewing Service Fulfillment Manager Parameters 60
- 61. Reviewing Service Fulfillment Manager Parameters 61
- 62. Reviewing Service Fulfillment Manager Parameters 62
- 63. Reviewing Service Fulfillment Manager Parameters 63
- 64. Reviewing Service Fulfillment Manager Parameters 64
- 65. Setting Up Areas Use areas to logically sort assets by the zones in which they reside. Areas divide the maintenance plant or facility into zones, which help to track and account for assets. Areas are later associated with assets. In this topic, you will define an area. 65
- 66. Setting Up Areas 66
- 67. Setting Up Areas 67
- 68. Setting Up Areas 68
- 69. Setting Up Areas 69
- 70. Setting Up Areas 70
- 71. Setting Up Areas 71
- 72. Defining Departments A department represents a crew within your organization. A crew may include people, machines, or suppliers. Departments are also used to collect costs, apply overhead, and compare load to capacity. Assign a department to each operation of a routing and assign resources that are available for that department. The department assigned to each operation of a routing also becomes the assigned department of the corresponding operation within the work order, assuming the work order is using the routing. Prerequisite You must define resources before you can define departments. For information on defining resources, refer to the 'Defining a Resource' section in the Oracle Bills of Material User's Guide. In this topic, you will define a department. 72
- 73. Defining Departments 73
- 74. Defining Departments 74
- 75. Defining Departments 75
- 76. Defining Departments 76
- 77. Defining Departments 77
- 78. Defining Departments 78
- 79. Defining Departments 79
- 80. Defining Departments 80
- 81. Defining Departments 81
- 82. Defining Departments 82
- 83. Defining Departments 83
- 84. Adding Resources to a Department Resources are defined before departments. For information on defining resources, Refer: 'Defining a Resource' section in the Oracle Bills of Material User's Guide. A resource represents a craft. You can enter multiple resources for each department. For each resource, you can specify the shifts that the resource is available. For each resource shift, you can specify capacity modifications that change the available hours per day, units per day, or workdays. In this topic, you will add a resource to a department. 84
- 85. Adding Resources to a Department 85
- 86. Adding Resources to a Department 86
- 87. Adding Resources to a Department 87
- 88. Adding Resources to a Department 88
- 89. Adding Resources to a Department 89
- 90. Adding Resources to a Department 90
- 91. Adding Resources to a Department 91
- 92. Adding Resources to a Department 92
- 93. Adding Resources to a Department 93
- 94. Adding Resources to a Department 94
- 95. Adding Resources to a Department 95
- 96. Adding Resources to a Department 96
- 97. Adding Resources to a Department 97
- 98. Adding Resources to a Department 98
- 99. Adding Resources to a Department 99
- 100. Adding Resources to a Department 100
- 101. Adding Resources to a Department 101
- 102. Adding Resources to a Department 102
- 103. Adding Resources to a Department 103
- 104. Adding Resources to a Department 104
- 105. Adding Resources to a Department 105
- 106. Adding Resources to a Department 106
- 107. Defining Department Approver With a responsibility assigned to the current asset's owning department, you can set up the department approvers so that work request notifications are sent to each approver, via Oracle Workflow (Refer: Defining Departments and Resources, Oracle Enterprise Asset Management User's Guide and Defining Asset Numbers, Oracle Enterprise Asset Management User's Guide, and Oracle Applications 12 Workflow). Approvers can view these notifications on the Enterprise Asset Management Self Service Maintenance Home Page (Refer: Home, Oracle Enterprise Asset Management User's Guide). Everyone who receives the notification can access the work request to change its status, or add additional information to the work request log. After one user approves the work request, the notification is removed from the users' notification lists, and the work request status transitions from Open to Awaiting Work Order. A work request can be rejected. If an approver rejects a work request, the notification is removed from that approver's notification list. You can re-assign a notification to another user for approval or additional information; for example, the originator might need to provide additional information on the work request. In this topic, you will define a department approver. 107
- 108. Defining Department Approver 108
- 109. Defining Department Approver 109
- 110. Defining Department Approver 110
- 111. Defining Department Approver 111
- 112. Defining Department Approver 112
- 113. Defining Department Approver 113
- 114. Defining Department Approver 114
- 115. Defining Department Approver 115
- 116. Defining Lookups Lookup codes must be decided upon and defined during the implementation process. Lookup codes fall within three categories: extensible, user defined, or system defined. If a lookup code is extensible, the existing lookup codes cannot be modified, but you can add new codes to the table. If lookup codes are user defined, all codes may be modified. If lookup codes are system defined, the existing codes cannot be modified, and new codes cannot be added to the table. You must define Asset Lookups, Work Request Lookups, and Work Order Lookups. Activity types are a type of lookup code. Activity types are used to describe the type of maintenance work that is performed on an asset, for example, Inspections, Lubrications, Overhauls, Calibration, and Repetitive work. Activity types are extensible. In this topic, you will define an activity type lookup code. 116
- 117. Defining Lookups 117
- 118. Defining Lookups 118
- 119. Defining Lookups 119
- 120. Defining Lookups 120
- 121. Defining Lookups 121
- 122. Defining Lookups 122
- 123. Defining Lookups 123
- 124. Defining Lookups 124
- 125. Defining Lookups 125
- 126. Defining Lookups 126
- 127. Defining Lookups 127
- 128. Defining Activity Types Activity types are used to describe the type of maintenance work that is performed on an asset. For example, Inspections, Lubrications, Overhauls, Calibration, and Repetitive work. Activity types are extensible. In this topic, you will define an activity type code. 128
- 129. Defining Activity Types 129
- 130. Defining Activity Types 130
- 131. Defining Activity Types 131
- 132. Defining Activity Types 132
- 133. Defining Activity Types 133
- 134. Defining Activity Types 134
- 135. Defining Activity Types 135
- 136. Defining Activity Types 136
- 137. Defining Activity Types 137
- 138. Defining Causes Activity cause codes are the reasons for an asset failure. For example, preventive, normal wear, rework, and breakdown. This information enables you to understand the dynamics that affect an asset's ability to perform. They establish critical data that is used for reporting and analysis of asset failure causes and the frequency of such conditions. Asset cause codes are referenced when setting up an activity. Activity cause codes are extensible. In this topic, you will define an activity cause code. 138
- 139. Defining Causes 139
- 140. Defining Causes 140
- 141. Defining Causes 141
- 142. Defining Causes 142
- 143. Defining Causes 143
- 144. Defining Causes 144
- 145. Defining Causes 145
- 146. Defining Causes 146
- 147. Defining Causes 147
- 148. Defining Activity Source Codes Activity source codes are the reasons that activities are executed. For example, warranty compliance, OSHA compliance, or military specification requirements. Activity source codes are referenced when setting up an activity. Activity source codes are extensible. In this topic, you will define an activity source code. 148
- 149. Defining Activity Source Codes 149
- 150. Defining Activity Source Codes 150
- 151. Defining Activity Source Codes 151
- 152. Defining Activity Source Codes 152
- 153. Defining Activity Source Codes 153
- 154. Defining Activity Source Codes 154
- 155. Defining Activity Source Codes 155
- 156. Defining Activity Source Codes 156
- 157. Defining Activity Source Codes 157
- 158. Defining Asset Activity Priorities Activity priority codes indicate asset activity priority levels, for example, Low, Medium, and High. Activity priority codes are extensible. In this topic, you will define an asset activity priority code. 158
- 159. Defining Asset Activity Priorities 159
- 160. Defining Asset Activity Priorities 160
- 161. Defining Asset Activity Priorities 161
- 162. Defining Asset Activity Priorities 162
- 163. Defining Asset Activity Priorities 163
- 164. Defining Asset Activity Priorities 164
- 165. Defining Asset Activity Priorities 165
- 166. Defining Asset Activity Priorities 166
- 167. Defining Asset Activity Priorities 167
- 168. Defining Asset Activity Priorities Complete the information as previously 168
- 169. Defining Asset Activity Priorities 169
- 170. Defining Criticality Codes Criticality codes suggest the importance of an asset to an organization, for example, High and Low. An asset that has a direct impact on production or that is difficult to replace may be considered a critical asset. Asset criticality codes help you to determine the urgency of the requested work. Asset criticality codes are referenced when defining an asset. Asset criticality codes are extensible. In this topic, you will define an asset criticality code. 170
- 171. Defining Criticality Codes 171
- 172. Defining Criticality Codes 172
- 173. Defining Criticality Codes 173
- 174. Defining Criticality Codes 174
- 175. Defining Criticality Codes 175
- 176. Defining Criticality Codes 176
- 177. Defining Criticality Codes 177
- 178. Defining Criticality Codes 178
- 179. Defining Criticality Codes 179
- 180. Defining Work Request Statuses The Work Request Approval process changes the work request status from Open to Awaiting Work Order. Maintenance work orders are linked to work requests with a status of Awaiting Work Order. When defining the Enterprise Asset Management parameters, if the Auto Approve check box is selected, work requests are automatically created with a status of Awaiting Work Order, for the organization. If the check box is not selected, then work requests are created with a status of Open. Work request approval statuses are extensible. In this topic, you will define a work request status. 180
- 181. Defining Work Request Statuses 181
- 182. Defining Work Request Statuses 182
- 183. Defining Work Request Statuses 183
- 184. Defining Work Request Statuses 184
- 185. Defining Work Request Statuses 185
- 186. Defining Work Request Statuses 186
- 187. Defining Work Request Statuses 187
- 188. Defining Work Request Types Work request types categorize work requests. For example, Manual, System, Routine, Ca pital, and Furniture. Work request types are extensible. In this topic, you will define a work request type. 188
- 189. Defining Work Request Types 189
- 190. Defining Work Request Types 190
- 191. Defining Work Request Types 191
- 192. Defining Work Request Types 192
- 193. Defining Work Request Types 193
- 194. Defining Work Request Types 194
- 195. Defining Work Request Types 195
- 196. Defining Work Request Types 196
- 197. Defining Work Request Priority Codes Work order (request) priority codes contribute to the organization and execution of work orders. For example, High, Medium, and Low, or 1, 2, and 3, respectively. Typically, a priority is assigned by the people entering work requests and work orders. The planner or supervisor compares this priority to the asset criticality. These codes are entered when creating activity associations, work orders, and work requests. Typically, a priority is assigned by the person that enters the work request and its related work order. The priority specified during the activity association becomes the work order priority when a work order is created, using the activity association. Work order priority codes are extensible. In this topic, you will define a work request priority code. 197
- 198. Defining Work Request Priority Codes 198
- 199. Defining Work Request Priority Codes 199
- 200. Defining Work Request Priority Codes 200
- 201. Defining Work Request Priority Codes 201
- 202. Defining Work Request Priority Codes 202
- 203. Defining Work Request Priority Codes 203
- 204. Defining Work Request Priority Codes 204
- 205. Defining Work Order Reconciliation Codes Reconciliation codes detail how work orders and operations were completed. These codes usually fall within two categories: Completed as Planned or Partial Completion. You can further define the condition within these two types of completion statuses. Reconciliation codes enable you to evaluate work orders by percentage completed or delayed, and if they were delayed, the reason for the delay. Reconciliation codes are extensible. In this topic, you will define a work order reconciliation code. 205
- 206. Defining Work Order Reconciliation Codes Follow the same steps to arrive in Manufacturing lookups 206
- 207. Defining Work Order Reconciliation Codes 207
- 208. Defining Work Order Reconciliation Codes 208
- 209. Defining Work Order Reconciliation Codes 209
- 210. Defining Work Order Reconciliation Codes 210
- 211. Defining Work Order Reconciliation Codes 211
- 212. Defining Work Order Types Work order types enable you to differentiate work orders. For example, Routine, and Rebuild. Maintenance management can use this information to sort and monitor work activity for reporting and budgeting. Work order types are referenced in the activity and work order. Work order types are created manually or automatically. For example, rebuildable work orders are created automatically or manually. Preventive maintenance work orders are created automatically, based on meter readings. Work order types are extensible. In this topic, you will define a work order type. 212
- 213. Defining Work Order Types Follow the same steps to arrive in Manufacturing lookups 213
- 214. Defining Work Order Types 214
- 215. Defining Work Order Types 215
- 216. Defining Work Order Types 216
- 217. Defining Work Order Types 217
- 218. Setting Up EAM 218