oracle ebs r12 eam module-upk

218
Oracle EBS R12.1 eAM Entreprise Asset Management Cédric Beltrame, PMP - 2012 1 Oracle is a registered trademark of Oracle Corporation and/or its affiliates Setting Up EAM

Upload: jcvd12

Post on 15-Nov-2014

6.225 views

Category:

Technology


67 download

DESCRIPTION

Oracle eAM UPK screenshots, part 1 : Setting Up EAM

TRANSCRIPT

Page 1: Oracle ebs r12 eam module-upk

1

Oracle EBS R12.1 eAMEntreprise Asset Management

Cédric Beltrame, PMP - 2012

Oracle is a registered trademark of Oracle Corporation and/or its affiliates

Setting Up EAM

Page 2: Oracle ebs r12 eam module-upk

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.

Page 3: Oracle ebs r12 eam module-upk

3

Setting Up EAM

Page 4: Oracle ebs r12 eam module-upk

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.

Page 5: Oracle ebs r12 eam module-upk

5

Setting Up Organizations

Page 6: Oracle ebs r12 eam module-upk

6

Setting Up Organizations

Page 7: Oracle ebs r12 eam module-upk

7

Setting Up Organizations

Page 8: Oracle ebs r12 eam module-upk

8

Setting Up Organizations

Page 9: Oracle ebs r12 eam module-upk

9

Setting Up Organizations

Page 10: Oracle ebs r12 eam module-upk

10

Setting Up Organizations

Page 11: Oracle ebs r12 eam module-upk

11

Setting Up Organizations

Page 12: Oracle ebs r12 eam module-upk

12

Setting Up Organizations

Page 13: Oracle ebs r12 eam module-upk

13

Setting Up Organizations

Page 14: Oracle ebs r12 eam module-upk

14

Setting Up Organizations

Page 15: Oracle ebs r12 eam module-upk

15

Setting Up Organizations

Page 16: Oracle ebs r12 eam module-upk

16

Setting Up Organizations

Page 17: Oracle ebs r12 eam module-upk

17

Setting Up Organizations

Page 18: Oracle ebs r12 eam module-upk

18

Setting Up Organizations

Page 19: Oracle ebs r12 eam module-upk

19

Setting Up Organizations

Page 20: Oracle ebs r12 eam module-upk

20

Setting Up Organizations

Page 21: Oracle ebs r12 eam module-upk

21

Setting Up Organizations

Page 22: Oracle ebs r12 eam module-upk

22

Setting Up Organizations

Page 23: Oracle ebs r12 eam module-upk

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.

Page 24: Oracle ebs r12 eam module-upk

24

Enabling Organizations for Enterprise Asset Management

Page 25: Oracle ebs r12 eam module-upk

25

Enabling Organizations for Enterprise Asset Management

Page 26: Oracle ebs r12 eam module-upk

26

Enabling Organizations for Enterprise Asset Management

Page 27: Oracle ebs r12 eam module-upk

27

Enabling Organizations for Enterprise Asset Management

Page 28: Oracle ebs r12 eam module-upk

28

Defining eAM ParametersOnce 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.

Page 29: Oracle ebs r12 eam module-upk

29

Defining eAM Parameters

Page 30: Oracle ebs r12 eam module-upk

30

Defining eAM Parameters

Page 31: Oracle ebs r12 eam module-upk

31

Defining eAM Parameters

Page 32: Oracle ebs r12 eam module-upk

32

Defining eAM Parameters

Page 33: Oracle ebs r12 eam module-upk

33

Defining eAM Parameters

Page 34: Oracle ebs r12 eam module-upk

34

Defining eAM Parameters

Page 35: Oracle ebs r12 eam module-upk

35

Defining eAM Parameters

Page 36: Oracle ebs r12 eam module-upk

36

Defining eAM Parameters

Page 37: Oracle ebs r12 eam module-upk

37

Defining eAM Parameters

Page 38: Oracle ebs r12 eam module-upk

38

Defining eAM Parameters

Page 39: Oracle ebs r12 eam module-upk

39

Defining eAM Parameters

Page 40: Oracle ebs r12 eam module-upk

40

Defining eAM Parameters

Page 41: Oracle ebs r12 eam module-upk

41

Defining eAM Parameters

Page 42: Oracle ebs r12 eam module-upk

42

Defining eAM Parameters

Page 43: Oracle ebs r12 eam module-upk

43

Defining eAM Parameters

Page 44: Oracle ebs r12 eam module-upk

44

Defining eAM Parameters

Page 45: Oracle ebs r12 eam module-upk

45

Defining eAM Parameters

Page 46: Oracle ebs r12 eam module-upk

46

Defining eAM Parameters

Page 47: Oracle ebs r12 eam module-upk

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.

Page 48: Oracle ebs r12 eam module-upk

48

Reviewing and Verifying Installed Base Parameters

Page 49: Oracle ebs r12 eam module-upk

49

Reviewing and Verifying Installed Base Parameters

Page 50: Oracle ebs r12 eam module-upk

50

Reviewing and Verifying Installed Base Parameters

Page 51: Oracle ebs r12 eam module-upk

51

Reviewing and Verifying Installed Base Parameters

Page 52: Oracle ebs r12 eam module-upk

52

Reviewing and Verifying Installed Base Parameters

Page 53: Oracle ebs r12 eam module-upk

53

Reviewing and Verifying Installed Base Parameters

Page 54: Oracle ebs r12 eam module-upk

54

Reviewing and Verifying Installed Base Parameters

Page 55: Oracle ebs r12 eam module-upk

55

Reviewing and Verifying Installed Base Parameters

Page 56: Oracle ebs r12 eam module-upk

56

Reviewing and Verifying Installed Base Parameters

Page 57: Oracle ebs r12 eam module-upk

57

Reviewing and Verifying Installed Base Parameters

Page 58: Oracle ebs r12 eam module-upk

58

Reviewing and Verifying Installed Base Parameters

Page 59: Oracle ebs r12 eam module-upk

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.

Page 60: Oracle ebs r12 eam module-upk

60

Reviewing Service Fulfillment Manager Parameters

Page 61: Oracle ebs r12 eam module-upk

61

Reviewing Service Fulfillment Manager Parameters

Page 62: Oracle ebs r12 eam module-upk

62

Reviewing Service Fulfillment Manager Parameters

Page 63: Oracle ebs r12 eam module-upk

63

Reviewing Service Fulfillment Manager Parameters

Page 64: Oracle ebs r12 eam module-upk

64

Reviewing Service Fulfillment Manager Parameters

Page 65: Oracle ebs r12 eam module-upk

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.

Page 66: Oracle ebs r12 eam module-upk

66

Setting Up Areas

Page 67: Oracle ebs r12 eam module-upk

67

Setting Up Areas

Page 68: Oracle ebs r12 eam module-upk

68

Setting Up Areas

Page 69: Oracle ebs r12 eam module-upk

69

Setting Up Areas

Page 70: Oracle ebs r12 eam module-upk

70

Setting Up Areas

Page 71: Oracle ebs r12 eam module-upk

71

Setting Up Areas

Page 72: Oracle ebs r12 eam module-upk

72

Defining DepartmentsA 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.

Page 73: Oracle ebs r12 eam module-upk

73

Defining Departments

Page 74: Oracle ebs r12 eam module-upk

74

Defining Departments

Page 75: Oracle ebs r12 eam module-upk

75

Defining Departments

Page 76: Oracle ebs r12 eam module-upk

76

Defining Departments

Page 77: Oracle ebs r12 eam module-upk

77

Defining Departments

Page 78: Oracle ebs r12 eam module-upk

78

Defining Departments

Page 79: Oracle ebs r12 eam module-upk

79

Defining Departments

Page 80: Oracle ebs r12 eam module-upk

80

Defining Departments

Page 81: Oracle ebs r12 eam module-upk

81

Defining Departments

Page 82: Oracle ebs r12 eam module-upk

82

Defining Departments

Page 83: Oracle ebs r12 eam module-upk

83

Defining Departments

Page 84: Oracle ebs r12 eam module-upk

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.

Page 85: Oracle ebs r12 eam module-upk

85

Adding Resources to a Department

Page 86: Oracle ebs r12 eam module-upk

86

Adding Resources to a Department

Page 87: Oracle ebs r12 eam module-upk

87

Adding Resources to a Department

Page 88: Oracle ebs r12 eam module-upk

88

Adding Resources to a Department

Page 89: Oracle ebs r12 eam module-upk

89

Adding Resources to a Department

Page 90: Oracle ebs r12 eam module-upk

90

Adding Resources to a Department

Page 91: Oracle ebs r12 eam module-upk

91

Adding Resources to a Department

Page 92: Oracle ebs r12 eam module-upk

92

Adding Resources to a Department

Page 93: Oracle ebs r12 eam module-upk

93

Adding Resources to a Department

Page 94: Oracle ebs r12 eam module-upk

94

Adding Resources to a Department

Page 95: Oracle ebs r12 eam module-upk

95

Adding Resources to a Department

Page 96: Oracle ebs r12 eam module-upk

96

Adding Resources to a Department

Page 97: Oracle ebs r12 eam module-upk

97

Adding Resources to a Department

Page 98: Oracle ebs r12 eam module-upk

98

Adding Resources to a Department

Page 99: Oracle ebs r12 eam module-upk

99

Adding Resources to a Department

Page 100: Oracle ebs r12 eam module-upk

100

Adding Resources to a Department

Page 101: Oracle ebs r12 eam module-upk

101

Adding Resources to a Department

Page 102: Oracle ebs r12 eam module-upk

102

Adding Resources to a Department

Page 103: Oracle ebs r12 eam module-upk

103

Adding Resources to a Department

Page 104: Oracle ebs r12 eam module-upk

104

Adding Resources to a Department

Page 105: Oracle ebs r12 eam module-upk

105

Adding Resources to a Department

Page 106: Oracle ebs r12 eam module-upk

106

Adding Resources to a Department

Page 107: Oracle ebs r12 eam module-upk

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.

Page 108: Oracle ebs r12 eam module-upk

108

Defining Department Approver

Page 109: Oracle ebs r12 eam module-upk

109

Defining Department Approver

Page 110: Oracle ebs r12 eam module-upk

110

Defining Department Approver

Page 111: Oracle ebs r12 eam module-upk

111

Defining Department Approver

Page 112: Oracle ebs r12 eam module-upk

112

Defining Department Approver

Page 113: Oracle ebs r12 eam module-upk

113

Defining Department Approver

Page 114: Oracle ebs r12 eam module-upk

114

Defining Department Approver

Page 115: Oracle ebs r12 eam module-upk

115

Defining Department Approver

Page 116: Oracle ebs r12 eam module-upk

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.

Page 117: Oracle ebs r12 eam module-upk

117

Defining Lookups

Page 118: Oracle ebs r12 eam module-upk

118

Defining Lookups

Page 119: Oracle ebs r12 eam module-upk

119

Defining Lookups

Page 120: Oracle ebs r12 eam module-upk

120

Defining Lookups

Page 121: Oracle ebs r12 eam module-upk

121

Defining Lookups

Page 122: Oracle ebs r12 eam module-upk

122

Defining Lookups

Page 123: Oracle ebs r12 eam module-upk

123

Defining Lookups

Page 124: Oracle ebs r12 eam module-upk

124

Defining Lookups

Page 125: Oracle ebs r12 eam module-upk

125

Defining Lookups

Page 126: Oracle ebs r12 eam module-upk

126

Defining Lookups

Page 127: Oracle ebs r12 eam module-upk

127

Defining Lookups

Page 128: Oracle ebs r12 eam module-upk

128

Defining Activity TypesActivity 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.

Page 129: Oracle ebs r12 eam module-upk

129

Defining Activity Types

Page 130: Oracle ebs r12 eam module-upk

130

Defining Activity Types

Page 131: Oracle ebs r12 eam module-upk

131

Defining Activity Types

Page 132: Oracle ebs r12 eam module-upk

132

Defining Activity Types

Page 133: Oracle ebs r12 eam module-upk

133

Defining Activity Types

Page 134: Oracle ebs r12 eam module-upk

134

Defining Activity Types

Page 135: Oracle ebs r12 eam module-upk

135

Defining Activity Types

Page 136: Oracle ebs r12 eam module-upk

136

Defining Activity Types

Page 137: Oracle ebs r12 eam module-upk

137

Defining Activity Types

Page 138: Oracle ebs r12 eam module-upk

138

Defining CausesActivity 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.

Page 139: Oracle ebs r12 eam module-upk

139

Defining Causes

Page 140: Oracle ebs r12 eam module-upk

140

Defining Causes

Page 141: Oracle ebs r12 eam module-upk

141

Defining Causes

Page 142: Oracle ebs r12 eam module-upk

142

Defining Causes

Page 143: Oracle ebs r12 eam module-upk

143

Defining Causes

Page 144: Oracle ebs r12 eam module-upk

144

Defining Causes

Page 145: Oracle ebs r12 eam module-upk

145

Defining Causes

Page 146: Oracle ebs r12 eam module-upk

146

Defining Causes

Page 147: Oracle ebs r12 eam module-upk

147

Defining Causes

Page 148: Oracle ebs r12 eam module-upk

148

Defining Activity Source CodesActivity 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.

Page 149: Oracle ebs r12 eam module-upk

149

Defining Activity Source Codes

Page 150: Oracle ebs r12 eam module-upk

150

Defining Activity Source Codes

Page 151: Oracle ebs r12 eam module-upk

151

Defining Activity Source Codes

Page 152: Oracle ebs r12 eam module-upk

152

Defining Activity Source Codes

Page 153: Oracle ebs r12 eam module-upk

153

Defining Activity Source Codes

Page 154: Oracle ebs r12 eam module-upk

154

Defining Activity Source Codes

Page 155: Oracle ebs r12 eam module-upk

155

Defining Activity Source Codes

Page 156: Oracle ebs r12 eam module-upk

156

Defining Activity Source Codes

Page 157: Oracle ebs r12 eam module-upk

157

Defining Activity Source Codes

Page 158: Oracle ebs r12 eam module-upk

158

Defining Asset Activity PrioritiesActivity 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.

Page 159: Oracle ebs r12 eam module-upk

159

Defining Asset Activity Priorities

Page 160: Oracle ebs r12 eam module-upk

160

Defining Asset Activity Priorities

Page 161: Oracle ebs r12 eam module-upk

161

Defining Asset Activity Priorities

Page 162: Oracle ebs r12 eam module-upk

162

Defining Asset Activity Priorities

Page 163: Oracle ebs r12 eam module-upk

163

Defining Asset Activity Priorities

Page 164: Oracle ebs r12 eam module-upk

164

Defining Asset Activity Priorities

Page 165: Oracle ebs r12 eam module-upk

165

Defining Asset Activity Priorities

Page 166: Oracle ebs r12 eam module-upk

166

Defining Asset Activity Priorities

Page 167: Oracle ebs r12 eam module-upk

167

Defining Asset Activity Priorities

Page 168: Oracle ebs r12 eam module-upk

168

Defining Asset Activity Priorities

Complete the information as previously

Page 169: Oracle ebs r12 eam module-upk

169

Defining Asset Activity Priorities

Page 170: Oracle ebs r12 eam module-upk

170

Defining Criticality CodesCriticality 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.

Page 171: Oracle ebs r12 eam module-upk

171

Defining Criticality Codes

Page 172: Oracle ebs r12 eam module-upk

172

Defining Criticality Codes

Page 173: Oracle ebs r12 eam module-upk

173

Defining Criticality Codes

Page 174: Oracle ebs r12 eam module-upk

174

Defining Criticality Codes

Page 175: Oracle ebs r12 eam module-upk

175

Defining Criticality Codes

Page 176: Oracle ebs r12 eam module-upk

176

Defining Criticality Codes

Page 177: Oracle ebs r12 eam module-upk

177

Defining Criticality Codes

Page 178: Oracle ebs r12 eam module-upk

178

Defining Criticality Codes

Page 179: Oracle ebs r12 eam module-upk

179

Defining Criticality Codes

Page 180: Oracle ebs r12 eam module-upk

180

Defining Work Request StatusesThe 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.

Page 181: Oracle ebs r12 eam module-upk

181

Defining Work Request Statuses

Page 182: Oracle ebs r12 eam module-upk

182

Defining Work Request Statuses

Page 183: Oracle ebs r12 eam module-upk

183

Defining Work Request Statuses

Page 184: Oracle ebs r12 eam module-upk

184

Defining Work Request Statuses

Page 185: Oracle ebs r12 eam module-upk

185

Defining Work Request Statuses

Page 186: Oracle ebs r12 eam module-upk

186

Defining Work Request Statuses

Page 187: Oracle ebs r12 eam module-upk

187

Defining Work Request Statuses

Page 188: Oracle ebs r12 eam module-upk

188

Defining Work Request TypesWork request types categorize work requests. For example, Manual, System, Routine, Capital, and Furniture. Work request types are extensible. In this topic, you will define a work request type.

Page 189: Oracle ebs r12 eam module-upk

189

Defining Work Request Types

Page 190: Oracle ebs r12 eam module-upk

190

Defining Work Request Types

Page 191: Oracle ebs r12 eam module-upk

191

Defining Work Request Types

Page 192: Oracle ebs r12 eam module-upk

192

Defining Work Request Types

Page 193: Oracle ebs r12 eam module-upk

193

Defining Work Request Types

Page 194: Oracle ebs r12 eam module-upk

194

Defining Work Request Types

Page 195: Oracle ebs r12 eam module-upk

195

Defining Work Request Types

Page 196: Oracle ebs r12 eam module-upk

196

Defining Work Request Types

Page 197: Oracle ebs r12 eam module-upk

197

Defining Work Request Priority CodesWork 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.

Page 198: Oracle ebs r12 eam module-upk

198

Defining Work Request Priority Codes

Page 199: Oracle ebs r12 eam module-upk

199

Defining Work Request Priority Codes

Page 200: Oracle ebs r12 eam module-upk

200

Defining Work Request Priority Codes

Page 201: Oracle ebs r12 eam module-upk

201

Defining Work Request Priority Codes

Page 202: Oracle ebs r12 eam module-upk

202

Defining Work Request Priority Codes

Page 203: Oracle ebs r12 eam module-upk

203

Defining Work Request Priority Codes

Page 204: Oracle ebs r12 eam module-upk

204

Defining Work Request Priority Codes

Page 205: Oracle ebs r12 eam module-upk

205

Defining Work Order Reconciliation CodesReconciliation 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.

Page 206: Oracle ebs r12 eam module-upk

206

Defining Work Order Reconciliation CodesFollow the same steps to arrive in Manufacturing lookups

Page 207: Oracle ebs r12 eam module-upk

207

Defining Work Order Reconciliation Codes

Page 208: Oracle ebs r12 eam module-upk

208

Defining Work Order Reconciliation Codes

Page 209: Oracle ebs r12 eam module-upk

209

Defining Work Order Reconciliation Codes

Page 210: Oracle ebs r12 eam module-upk

210

Defining Work Order Reconciliation Codes

Page 211: Oracle ebs r12 eam module-upk

211

Defining Work Order Reconciliation Codes

Page 212: Oracle ebs r12 eam module-upk

212

Defining Work Order TypesWork 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.

Page 213: Oracle ebs r12 eam module-upk

213

Defining Work Order TypesFollow the same steps to arrive in Manufacturing lookups

Page 214: Oracle ebs r12 eam module-upk

214

Defining Work Order Types

Page 215: Oracle ebs r12 eam module-upk

215

Defining Work Order Types

Page 216: Oracle ebs r12 eam module-upk

216

Defining Work Order Types

Page 217: Oracle ebs r12 eam module-upk

217

Defining Work Order Types

Page 218: Oracle ebs r12 eam module-upk

218

Setting Up EAM