Page 1 of 7

"> R12.1.1 GIS Integration: Assets on Google Map Feature Guide [ID 779351.1] Modified 13-OCT-2011 In this Document Purpose Scope and Application R12.1.1 GIS Integration: Assets on Google Map Feature Guide Overview Feature Details Process Flows Functional Steps Technical Details Example FAQs Type BULLETIN Status PUBLISHED

Applies to:
Oracle Enterprise Asset Management Oracle Asset Tracking - Version: 12.1.1 and later [Release: 12.1 and later] Information in this document applies to any platform.

Purpose
***Checked for relevance on 02-Mar-2011*** This document describes details on the new integration between web based source map viewer of Google Maps and Oracle Asset Lifecycle Management (ALM) products in R12.1.1. Using this feature, assets can be geocoded and displayed in the Google map viewer based on user entered search criteria. After locating an asset on a map, user can perform various actions depending upon the type of asset such as create work request, create work order, view open WR, view open WO, Graphical Asset hierarchy, etc. This note specifically covers the following areas: * Overview * Feature Details * Process Flows * Functional Steps * Technical Details * Example * FAQs

Scope and Application

This document is informational and intended for any user.

R12.1.1 GIS Integration: Assets on Google Map Feature Guide Overview

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 (4154'12"N, 8737'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 4154'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 8737'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.

Feature Details
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

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=BULLETI...

12/3/2011

Page 2 of 7
asset number selected. All other details corresponding to the selected asset number are defaulted when the page is rendered. In Oracle Asset Tracking, users can search for Item instances using simple/ advanced search, enter geocodes for the asset using the 'Mass Geocode Enter' form, then locate the resulting asset on the map viewer by invoking the 'Map All' button. When the user selects any OAT/IB instance icon on the map viewer, details such as Instance Number, Description, Item, Instance Location and Geocodes will be displayed in a pop up. Also, hyperlinks are displayed for performing the following actions: 1. View instance details page 2. View Graphical Asset hierarchy Alternatively, when a user selects any EAM instance icon on the map viewer, details such as Instance Number, Description, Item, Instance Location and Geocodes will be displayed in a pop up. Also, hyperlinks are displayed for performing the following actions: 1. View instance details page 2. View open work requests 3. View open work orders 4. View Graphical Asset hierarchy

Process Flows
Following is a the process flow for the new GIS Integration feature :

Functional Steps
To enable the GIS Integration using Google Map feature, follow these instructions: 1. Set the following profile options correctly:
l l

(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 Google Maps and can be set at any level 2. Associate the function 'Map All' to the responsibility meant for accessing Maintenance user's menu.
l l

(R) System Administrator (N) Application > Menu Query for "EAM_MAINTENANCE_UNIT_SEARCH" menu. Add the function 'Map All'

Associating the 'Map All' function to the responsibility will enable 'Map All' button and 'Map' button to EAM/ OAT responsibilities. 3. Enter geocodes for assets/instances manually using the 'Mass Geocode Entry' form:
l l

(R) Maintenance Super User responsibility or Asset Tracking Super User responsibility (N) Assets > Mass Geocode Entry Query for an Asset Number Enter geaocodes for the Asset Save.

4. View the EAM Assets on Google Map:

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=BULLETI...

12/3/2011

Page 3 of 7
l l

(R) Maintenance Super User (N) Assets > Capital Query for an Asset Number Click 'Map All' button to locate the asset in the Google Map Viewer.

OR
l l

(R) Asset Tracking Super User (N) Assets > Item instance Query for an item instance. Click 'Map All' button to locate the asset in the Google Map Viewer.

Clicking on Map All button will render all the assets/instances fetched by the search criteria in the Google Map Viewer.

Technical Details
Geocodes can be entered for assets/instances using CSI_GIS_INSTANCE_LOC_PUB. IMPORT_INSTANCE_GEO_LOCATION Import API. This will enable mass entries for goecodes and save time. This Import API has been included in csipgilb.pls & csipgils.pls and meant to populate the CSI_II_GEOLOC_INTERFACE interface table name which has the following structure:
NAME INSTANCE_NUMBER GEOCODE_FORMAT INST_LATITUDE INST_LONGITUDE PROCESS_FLAG ERROR_MESSAGE PROCESS_DATE NULL ? NOT NULL NOT NULL NOT NULL NOT NULL TYPE VARCHAR2 (30) VARCHAR2 (3) VARCHAR2 (50) VARCHAR2 (50) VARCHAR2 (1) VARCHAR2(4000) DATE

COLUMN DETAILS: INSTANCE_NUMBER: This is Instance Number or Asset Number depending on whether the application is OAT or EAM respectively. This is a mandatory column. GEOCODE_FORMAT: Valid geocode formats are 'DMS','DM', and 'DD'. If nothing is entered 'DMS' is taken as the default geocode format. INST_LATITUDE & INST_LONGITUDE: The valid values for the 3 formats (DMS, DM, DD) are illustrated below. Both these columns are mandatory. DMS Format: <Degree Value>D<Minutes Value>M<Seconds Value>S<Direction> D-Degrees, M-Minutes, S-Seconds, Direction can be N, S, E, W as in North, South, East, West respectively. Eg. 25D36M14S N or 25d36m14s n
l l l l l

Spaces between any two elements will be ignored. Eg 25D 36M 14S N is also a valid value. Minutes and seconds must be in the range of 0 to 59. Degrees and Minutes cannot have decimal value. Eg 25.456 D36M49S N is an invalid value All the three values for D, M, S must be present for DMS format

DM Format: <Degree Value>D<Minutes Value>M<Direction> D-Degrees, M-Minutes Direction can be N, S, E, W as in North, South, East, West respectively Eg: 25D36.567M N or 25d36.567m n
l l l l l

Spaces between any two elements will be ignored. Eg 25D 36M N is also a valid value. Minutes must be in the range of 0 to 59. Degrees cannot have decimal value. Eg 25.456 D36M49S N is an invalid value Both the values for D, M must be present for DM format

Validations common for both DMS and DM Formats:

l l l l l l l

Latitude must be in the range of 90 to + 90. Longitude must be in the range of 180 to +180. Latitude directions can be only N, S Longitude directions can be only E, W Latitude direction N cannot have a negative value. Longitude direction E cannot have a negative value. If no direction is given, it is decided by taking sign into account. Positive values are considered to be N or E for latitude or longitude respectively. Negative values are considered S or W for latitude or longitude respectively.

DD Format: DD value can be anything between 90 to +90 for latitude and 180 to +180 for longitude including decimal numbers. Direction should not be entered for DD format. Eg: 25.6677
l l l

Direction for DD format will be inferred based on the sign of the value and whether it is latitude or longitude. Positive values are considered to be N or E for latitude or longitude respectively. Negative values are considered S or W for latitude or longitude respectively.

Conversion of DM and DD value to DMS value: 1. Conversion of DD value to DMS value:

l l l l l

The Degrees are simply the numbers to the left of the decimal (using 42.36824 the degrees would be 42) To determine the Minutes, multiply the number to the right of the decimal point by 60 (example: .36824 x 60 = 22.0944) The Minutes are the numbers to the left of the decimal point (in this example, 22) To determine the Seconds, multiply the number to the right of the decimal point by 60 (example: .0944 x 60 = 5.664) The Seconds are rounded up to two decimal places. (In this example .66)

2. Conversion of DM value to DMS value:

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=BULLETI...

12/3/2011

Page 4 of 7
For this conversion first you need to convert DM to DD value and then DD to DMS value as mentioned above. Conversion of DM to DD value DD = D + M / 60. Where D is degree and M is Minute. Once we have the DD value we can use the above-mentioned steps to convert the DD value to DMS value. PROCESS_FLAG: Process flag indicates the status of the record. Possible values are 'R','E', and 'P'. R Indicates that record is ready to be processed E Indicates that record is processed but it has erred out. P Indicates that the record is processed successfully. Only the records with PROCESS_FLAG set to R are considered for processing ERROR_MESSAGE: This column contains the error message when a record has errors out. PROCESS_DATE: Indicates the date on which the record was last processed.

Example
This example will show how to import Bulk Geocode data in DMS format for an Asset Number. This is used to save user time instead of entering geocodes for each assets using "Mass Gecocode Entry" form. This can be done either by inserting the geocodes entries directly to the interface table or using INSERT statements or through SQL Loader. Inserting Bulk data to Interface table using INSERT statements: Insert geocode details into the CSI_II_GEOLOC_INTERFACE table using the following INSERT:
INSERT into CSI_II_GEOLOC_INTERFACE values (AN-008, DMS, 45D40M14S N, 69D40M14S W, R, NULL, NULL); COMMIT;

This query will insert Geocode values for asset number AN-008. The geocode values given here are: Latitude values: Degree: 45 Minutes: 40 Seconds: 14 Direction: N (North) Longitude values: Degree: 69 Minutes: 40 Seconds: 14 Direction: W (West) So the interface table should have the above information stored in the table once the above INSERT statement is executed. Similar INSERT statements can be used for each Asset/Instance with their relevant geocode entries. Inserting Bulk data to Interface table using SQL Loader: Alternatively, you can user SQL Loader to insert geocode details into the CSI_II_GEOLOC_INTERFACE table as the following: 1. Open an Excel Worksheet. 2. Enter the data, which are needed to be imported into the interface table. E.g.

KAK-AN1 39309 39310 39311 39312 39313

DMS DMS DMS DMS DMS DMS

40D59M12S N 40D59M12S N 40D59M12S N 40D59M12S N 40D59M12S N 40D59M12S N

79D59M12S W 79D59M12S W 79D59M12S W 79D59M12S W 79D59M12S W 79D59M12S W

R R R R R R

4. Save the above data as csv file. The Extension of the file should be csv (eg: GIS.csv) 5 . Note down the full path for this csv file (e.g. "D:\GIS.csv") 6. Open a notepad and create a control file (e.g. "loader.ctl"). 7. Contents of this control file should be as the following:
load data infile 'D:\GIS.csv'

infile command accept the full path for the the csv file which includes all asset geocodes.

into table CSI_II_GEOLOC_INTERFACE

into table accepts the interface table name that the data will be imported to.

fields terminated by "," optionally enclosed by '"'

The column names of the CSI_II_GEOLOC_INTERFACE interface table should be mentioned in order.

(INSTANCE_NUMBER,GEOCODE_FORMAT,INST_LATITUDE,INST_LONGITUDE,PROCESS_FLAG)

8. So, the final loader.ctl file should contain only the following information:
load data infile 'D:\GIS.csv' into table CSI_II_GEOLOC_INTERFACE fields terminated by "," optionally enclosed by '"' (INSTANCE_NUMBER,GEOCODE_FORMAT,INST_LATITUDE,INST_LONGITUDE,PROCESS_FLAG)

9. Open a Command Prompt and change the directory to d: (by simply typing d:) 10. Execute the following command sqlldr apps/<password>@<SID> control=loader.ctl 11. You will get an output saying that "Commit point reached logical record count 6".

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=BULLETI...

12/3/2011

Page 5 of 7

Logical record count is 6 since there are 6 records in the csv file. 12. Connect to sqlplus and verify that the data has been inserted into the interface table.
SELECT * FROM CSI_II_GEOLOC_INTERFACE;

Importing Bulk data from interface table to Main tables: Run the following SQL block to import all details from interface table to Main tables:
Declare l_return_status Varchar2(1); l_msg_count Number; l_msg_data Varchar2(4000); Begin CSI_GIS_INSTANCE_LOC_PUB.IMPORT_INSTANCE_GEO_LOCATION (p_api_version =>1.0, p_commit=>FND_API.G_TRUE, x_return_status => l_return_status, x_msg_count => l_msg_count, x_msg_data=>l_msg_data); dbms_output.put_line('Process Status'||l_return_status); dbms_output.put_line('Erred Records'||l_msg_count); End;

SQL Block should import the details to main tables from the interface table. Ensure that the process_flag is 'P' which means 'Processed'. Viewing geocodes values imported for Assets:
l l

(R) Maintenance Super User, Vision Operations (N) Assets > Mass Geocode Entry Query for 'KAK-AN1' in the Asset Number Field. Click Go You should be able to see the Geocode values for the Asset Number 'KAK-AN1' which has been loaded through SQL.

Viewing Assets with associated geocodes into Google Map:

l l

(R) Maintenance Super User (N) Assets > Capital Query for 'KAK-AN1' in the Asset Number Field. Click 'Map All' button to locate the asset in the Google Map Viewer. Click the asset icon of 'KAK-AN1' A pop up window should appear having the details of 'KAK-AN1'. Check for the following: n Asset Number n Description n Asset Group n Asset Location n Owning Department n Geocodes Check other links for Create Work Request / Create Work Order / View Open Work Request / View Open Work Order / Graphical Hierarchy.

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=BULLETI...

12/3/2011

Page 6 of 7

FAQs
Q. Can I have another Map Viewer other than Google Map Viewer? A. In R12.1.1, GIS integration with web based source map viewer supports Google maps only. Q. What values can be set for 'CSI: Mapviewer Name' profile option? A. In R12.1.1, 'Google' and 'Custom' are the seeded values for 'CSI: Mapviewer Name' profile option. However, more look up values might be added in future releases based on other supported map viewers. If no value is set for this profile, then it is assumed that GIS integration is not intended. If it is set to 'Google', then GIS Integration with Google map is activated. If it is set to 'Custom', then GIS Integration with custom map viewer is activated. Custom source maps usually show details to a greater extent compared to the default images provided. Custom source maps can be either made by a tool if geocodes are available or a satellite imagery can be taken. Each source map viewer supports few specific formats of the custom source maps like Oracle Spatial supports 1 or 2 ESRI formats. Custom source maps in case of Utility industry can be entire stretch of utilities with associated information. Q. How can I get Map Registration Key and Map Client ID? A. Contact Google to obtain Map Registration Key and Map Client ID. Q. Why 'Map All' button is not shown in Asset/Items Instance search results page? A. Function 'Map All' need to be associated to the responsibility meant for accessing Maintenance user's menu. By default, this function is not associated to any Maintenance responsibility. Q. Can geocodes be captured for all item instances ? A. Geocode information capture can be allowed of all item instances, both customer and enterprise owned. except for Non-serial Rebuildables, Asset Routes and Systems. Q. Why assets icon is showing into the Google Map but got a blank no map? A. Reduce map zooming using the left panel on the Google Map.

Attachments Flow.png (8.73 KB) Map.png (682.58 KB) Related Products

l l

Oracle E-Business Suite > Asset Lifecycle Management > Asset Lifecycle Management > Oracle Enterprise Asset Management Oracle E-Business Suite > Asset Lifecycle Management > Asset Lifecycle Management > Oracle Asset Tracking

Keywords API; ASSET ITEM; ASSET NUMBER; EAM; GEOCODE; GOOGLE MAPS; UPGRADE TO 12.1.1; DYNAMIC ADV FEATURES

Back to top

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=BULLETI...

12/3/2011

Page 7 of 7
Copyright (c) 2007, 2010, Oracle. All rights reserved. Legal Notices and Terms of Use | Privacy Statement

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=BULLETI...

12/3/2011