To Access Data from Multiple Operating Units from a Single Responsibility

Each user can access, process, and report on data only for the operating units assigned to the MO: Operating Unit or MO: Security Profile profile option

The MO: Operating Unit profile option only provides access to one operating unit.
The MO: Security Profile provides access to multiple operating units from a single responsibility

Note: If the MO: Security Profile is set, then the MO: Operating Unit profile is ignored.

Access to Operating Units:
Your responsibility determines which operating units you can access when you use Oracle Applications. If you want a responsibility to access only one operating unit, then
set the profile option called MO: Operating Unit. If you want a responsibility to access multiple operating units, then define a security profile with multiple operating units
assigned and assign it to the MO: Security Profile profile option. Additionally, if using the MO: Security Profile profile option, you can also set the MO: Default Operating Unit
profile option to specify a default operating unit that will default in transaction entry pages

It is correct to enable MO: Security Profile to have access to multiple operating units from a single responsibility

Possibility to link Preventive Maintenance (PM) Meter reading with Discrete Manufacturing Process in Oracle EAM (R12)

There isn't a synchronization between PM Schedule and duration time (or resource usage time) in finished Discrete Jobs

The PM Schedule is based on the entered meter readings (manually in Meter Readings form or by interface).  Usage rate (defined for meters) is used for PM Schedule calculations until the number of entered meter reading is less than "Number of Past Reading". After that, system calculates usage rate based only on entered meter readings

Difference Of Service Request And Work Request In Oracle EAM

You can probably implement your business flow using either way: Service and EAM Work Requests even there are differences between them. The main difference is that agents can view work orders created in Oracle Enterprise Asset Management related to the service request, but the life cycle of the work order is not in any way tied to the service request life cycle. Closing work orders tied to a service request does not close the service request and vice-versa. This is not the same when using work requests

Other differences: Normally, SRs are used when maintaining instances owned by customers while WRs are used when maintaining own asset numbers. we can use approval workflow for WRs and not for SRs. Using SRs you need to create a repair order then to generate work orders while using the WRs, the WOs are generated directly

Google Map in Oracle EAM (GIS Integration)

Geographic Information System (GIS) is an information system for storing, analyzing, managing and presenting digital data such as geographic features present on the Earth's surface using spatial references. Some of the GIS solutions available in the market are ESRI, Google Maps, Oracle Spatial, etc.

A Geocode (Geospatial Entity Object code) is a representation format of a geospatial coordinate measurement used to provide a standard representation of an exact geospatial point location on the earth. For example, the format (41°54'12"N, 87°37'35"W) indicates latitude, longitude of a unique location on earth.

Latitude gives the location of a place on earth north or south of the equator. Lines of Latitude are the horizontal lines shown running east-to-west on maps. Latitude is given as an angular measurement ranging from 0° at Equator to +90° at North Pole and -90° at South Pole. An example of a latitude in DMS (Degrees Minutes Seconds) format is 41°54'12"N

Longitude is the east-west geographic coordinate measurement. Longitude is given as an angular measurement ranging from 0° at the prime meridian to +180° eastward and −180° westward.
An example of a longitude in DMS (Degrees Minutes Seconds) format is 87°37'35"W

Release 12.1.1 enables GIS Integration using web based source map viewer of Google maps and provision is given to allow assets/ instances to be geocoded so that they can be spatially located on the map viewer. All item instances, i.e. EAM Assets and OAT instances are eligible to be geocoded and viewed in the Asset map viewer

Release 12.1.1 provides ability so that item instances can have a provision to capture their geocodes i.e. Latitude and Longitude. This can be done either manually through a mass data entry page or automatically through an API.

In Enterprise Assets Maintenance, users can search for any EAM assets using simple/ advanced search, enter geocodes for the assets using the 'Mass Geocode Entry' form, then locate the resulting asset on the map viewer by invoking the 'Map All' button. Alternatively, users can navigate to the Asset details page and locate the particular asset on the map viewer.

When a user selects any asset icon on the map viewer, details such as Asset Number, Description, Asset Group, Owning Department, Asset Location and Geocodes are displayed in a pop up. Also, hyperlinks are displayed for performing the following actions:
1. View asset details page
2. Create work request
3. Create work order
4. View open work requests
5. View open work orders
6. View Graphical Asset hierarchy.

When user selects any of the above actions, the page control is transferred to the appropriate tab in EAM responsibility with the context of the asset number selected. All other details corresponding to the selected asset number are defaulted when the page is rendered

Setup Steps

To enable the GIS Integration using Google Map feature, follow these instructions:

1. Set the following profile options:

• (R) System Administrator
• (N) Profile > Systems
• 'CSI: Mapviewer Name' = Google

Profile value can be set at any level.

• 'CSI: Google Registration key'

This profile hold the complete registration key (license key) for the Google Maps and can be set at any level

• 'CSI: Google Map Client ID'

This profile hold the client ID for the licensed copy of

"Asset Group" at inside the Oracle eAM

The word “Asset Group” trips out many people and remains a clearly un-answered question for range of Oracle users including technical consultants and business end users. explaining the Asset Group to different user groups is challenge, particularly when it comes to linear assets,For better clarity on the data model of the eAM Asset Group

Objective of this blog is to explain how an Asset Group relates to the key data objects within Oracle Enterprise Asset Management (eAM) module. These relationships are very important to consider while deciding on eAM Asset Groups for an organisation,Please take a look at following diagram that illustrates the direct and indirect links between eAM Asset Groups with other objects

1.  eAM Attribute Groups are assigned to a particular eAM Asset Group. ie, all eAM Assets belonging to that eAM Asset Group inherit the assigned attribute groups.
2. eAM Activities are assigned to a particular eAM Asset Group. ie, all eAM Assets belonging to that eAM Asset Group inherit the assigned activities.