This chapter covers the following topics:
The table below indicates if you can view or update the profile option and which System Administrator levels the profile options can be updated: Site, Application, Responsibility, and User. Use the Personal Profile Options window to view or set your profile options at the user level. View the Oracle Applications System Administrator's Guide for a list of profile options common to all Oracle applications.
A Required profile option requires a value. An Optional profile option provides a default value; provide a value only if you want to change this value.
Profile Option | User | System Admin: USER |
System Admin: RESP |
System Admin: APP |
System Admin: SITE |
Required? | Default |
---|---|---|---|---|---|---|---|
EAM: Activity API Debug File Directory | View Update |
View Update |
View Update |
View Update |
View Update |
N | - |
EAM: Activity API Debug File Name | View Update |
View Update |
View Update |
View Update |
View Update |
N | EAM_ABO_debug.log |
EAM: Activity API Debug Option | View Update |
View Update |
View Update |
View Update |
View Update |
N | No |
EAM: Asset Actions Lookup Name | View Update |
View Update |
View Update |
View Update |
View Update |
View Update |
Blank |
EAM: Asset hierarchy description length | View Update |
View Update |
View Update |
View Update |
View Update |
View Update |
Yes |
EAM: Debug Profile Option | View Update |
View Update |
View Update |
View Update |
View Update |
N | - |
EAM: Debug PM Scheduling | View Update |
View Update |
View Update |
View Update |
View Update |
N | Yes |
EAM: Default failure codes for PM work orders | View Update |
View Update |
View Update |
View Update |
View Update |
View Update |
Yes |
EAM: Enable Cross Reference and Manufacturer Search on Material | View Update |
View Update |
View Update |
View Update |
View Update |
N | Yes |
EAM: Endeca Work Order Data Load Start Date (mm/dd/yyyy) | View Update |
View Update |
View Update |
View Update |
View Update |
View Update |
N |
EAM: Endeca Work Request Data Load Start Date (mm/dd/yyyy) | View Update |
View Update |
View Update |
View Update |
View Update |
View Update |
N |
EAM: FA Book Type Code | - | - | - | - | Yes | N | Blank |
EAM: Google Map Registration key | No | No | No | No | Yes | N | Blank |
EAM: Google Map Client ID | No | No | No | No | Yes | N | Blank |
EAM: Maintenance Supervisor | View Update |
View Update |
View Update |
View Update |
View Update |
N | No |
EAM: Maintenance Work Request Options | View | View | View Update |
View | View | N | - |
EAM: Map Viewer name | No | No | No | No | Yes | N | Blank |
EAM: Mass Complete work orders at system date | View Update |
View Update |
View Update |
View Update |
View Update |
View Update |
Mass Complete through Maintenance Workbench |
EAM: Mobile Configuration | View Update |
View Update |
View Update |
View Update |
View Update |
View Update |
N |
EAM: Mobile Include Departments Work | View Update |
View Update |
View Update |
View Update |
View Update |
View Update |
N |
EAM: Mobile Update Hook Enabled | View Update |
View Update |
View Update |
View Update |
View Update |
View Update |
N |
EAM: MSU-RESP | View Update |
View Update |
View Update |
View Update |
View Update |
View Update |
N |
EAM: Object Instantiation API Log File Directory | View Update |
View Update |
View Update |
View Update |
View Update |
N | - |
EAM: Object Instantiation API Log File Name | View Update |
View Update |
View Update |
View Update |
View Update |
N | EAM_MOI.log |
EAM: Object Instantiation API Log Option | View Update |
View Update |
View Update |
View Update |
View Update |
N | No |
EAM: Trigger requisition for cancelled/rejected quantity | View Update |
View Update |
View Update |
View Update |
View Update |
View Update |
N |
EAM: Use Work Order Org For EAM Endeca Security | View Update |
View Update |
View Update |
View Update |
View Update |
View Update |
N |
eAM's profile options are listed below:
EAM: Activity API Debug File Directory
The activity API is called in eAM when a new activity is created from either a work order or activity. This profile option indicates the debug file directory that the debug log will reside, if debugging is enabled for the activity API. For example, If the profile option, EAM: activity API Debug Option, is set to Yes, the log of the activity process is saved in the directory determined by the path designated in the current profile option. This profile option is visible and changeable at the User level; it is visible and changeable at System Administrator's User, Responsibility, Application, and Site levels.
EAM: Activity API Debug File Name
The Activity API is called in eAM when a new activity is created from either a work order or activity. This profile option indicates the debug file name that resides in the debug file directory, if debugging is enabled for the Activity API. For example, If the profile option, EAM: Activity API Debug Option, is set to Yes, the log of the activity process is saved in the directory determined by the path designated by the EAM: Activity API Debug File Directory profile option. The name of the file that includes the activity process log is determined by the current profile option. This profile option is visible and changeable at the User level; it is visible and changeable at System Administrator's User, Responsibility, Application, and Site levels.
EAM: Activity API Debug Option
The Activity API is called in eAM when a new activity is created from either a work order or activity. This profile option indicates whether debugging is enabled for the Activity API. This profile option is visible and changeable at the User level; it is visible and changeable at System Administrator's User, Responsibility, Application, and Site levels.
EAM: Asset Actions Lookup Name
This profile option determines which lookup is shown as options in asset search table actions of Create Work Request or Asset Hierarchy.
EAM: Asset Hierarchy Description Length
This profile option is used to set the length of asset hierarchy description. You can then view the assets with their descriptions in the Asset Hierarchy page.
This profile option indicates whether debug mode is enabled for Preventive Maintenance Scheduling processes. The profile option is visible and changeable at the User level; it is visible and changeable at System Administrator's User, Responsibility, Application, and Site levels. The debug mode enables a tracing feature and causes additional messages to be printed to a log file. The default value is Yes. The internal name of the profile option is EAM_DEBUG_PM_SCHED. Available values are as follows:
Yes - System is operating in debug mode
No - System is operating in normal mode
Blank (no value) - Equivalent to No
This profile option is used by multiple eAM processes. If this profile is enabled, the log of these processes is collected. These processes include the following:
Asset Number Import Program - the log is visible in the Concurrent Program log
Asset Downtime Process - the log is visible in the Concurrent Program log
Asset Genealogy Import Process - the log is visible in the Concurrent Program log
Work Order Business Object API
This profile option is visible and updateable at the User level; it is visible and updateable at System Administrator's User, Responsibility, Application, and Site levels.
EAM: Default Failure Codes for PM Work Orders
This profile option displays the default value of "Failure Code Required" associated with the generated PM work order according to Failure Set/Asset Group association setup. The default value is Yes.
EAM: Enable Cross Reference and Manufacturer Search on Material
This profile option provides the ability to search for items by Manufacturers Part Number or item cross reference for work order materials in the Create/Update Work Order page and the Stores - One-Step Material Issue page. The Manufacturers Part Number can be added to the inventory item using the Item Master form. Because the Manufacturers Part Number is readily available (etched on parts), this identifier can be used to find the inventory item in the application.
EAM: Endeca Work Order Data Load Start Date (mm/dd/yyyy)
This profile option loads all work orders created on and after the specified date to the Endeca Data Store.
Note: For more information, see Oracle Enterprise Asset Management Extensions for Oracle Endeca Configuration notes, My Oracle Support Note 1470176.1.
EAM: Endeca Work Request Data Load Start Date (mm/dd/yyyy)
This profile option loads all work requests created on and after the specified date to the Endeca Data Store.
Note: For more information, see Oracle Enterprise Asset Management Extensions for Oracle Endeca Configuration notes, My Oracle Support Note 1470176.1.
EAM: Include Non-Nettable Quantity
If this profile is set to NO, Material Requirements within the Material Requirements, Operations, Work Orders, and the Maintenance Workbench windows display on-hand quantity as the quantity available in Nettable Subinventories. If this profile is set to YES, Material Requirements within these windows display the on-hand quantity as the quantity available in all Subinventories (Nettable and Non-nettable). Within the Maintenance Super User responsibility's Work Orders tab, the Material Requirements page displays he on-hand quantity as the quantity available in Nettable Subinventories if this profile is set to NO. The Material Requirements page displays on-hand quantity as the quantity available in all Subinventories (Nettable and Non-nettable), if the profile is set to YES.
Set this profile option to indicate if the self service Maintenance Supervisor Workbench is enabled.
Yes: The Maintenance Supervisor Workbench is enabled.
No: The Maintenance Supervisor Workbench is not enabled.
EAM: Maintenance Work Request Options
This profile options controls the view and update of a Work Request. It determines whether you can see only your own work requests or also others' work requests.
EAM: Mass Complete work orders at system date
Set this profile option to indicate the preferred dates for work orders to mass complete from the Maintenance Workbench. This profile option has 4 values for setup:
No: This is the default value of the profile. Use this option if you do not want to perform mass completes using the system date as a default.
Yes - for future date work orders: The System Date is the default completion date for work orders with scheduled dates in the future during the Mass Complete process using the Maintenance Workbench.
Yes - for past date work orders: The System Date is the default completion date for work orders with scheduled dates in the past during the Mass Complete process using the Maintenance Workbench.
Yes - for all work orders: The System Date is the default completion date for all work orders including past and future scheduled dates in the future during the Mass Complete process using the Maintenance Workbench.
The following table outlines the behavior of the Mass Complete process relative to the completion dates for each profile value:
Completion Date | No | Yes - for future date work orders | Yes - for past date work orders | Yes - for all work orders |
---|---|---|---|---|
For work orders with scheduled dates in past | Scheduled Completion Date | Scheduled Completion Date | System Date | System Date |
For work orders with scheduled dates in future | Scheduled Completion Date* | System Date | Scheduled Completion Date* | System Date |
*The system will not include future-dated work orders that have not been set up with the System Date as the completion date.
This profile option is used to display Express and Debrief work orders in the EAM Mobile Maintenance application. Set value as follows:
Value: {"access":{"expressWorkOrder":"Y"}}
Profile can be set at Site, Responsibility and User levels.
Note: For more information, see Oracle Mobile Maintenance for Oracle E-Business Suite Release Notes on My Oracle Support, Note 1923702.1.
EAM: Mobile Include Departments Work
This profile option enables users to view work assigned to a login user or a login user and department. If the option is set to No, the user will be able to view only the work assigned to login user. If the option is set to Yes, the user will be able to view work assigned to the login user and work assigned to the department.
Note: For more information, see Oracle Mobile Maintenance for Oracle E-Business Suite Release Notes on My Oracle Support, Note 1923702.1.
EAM: Mobile Update Hook Enabled
This profile option is used to refresh mobile disconnected data immediately after changes are made in EAM.
Note: For more information, see Oracle Mobile Maintenance for Oracle E-Business Suite Release Notes on My Oracle Support, Note 1923702.1.
This profile option is used to set the default EAM Self-Service responsibility where there are multiple responsibilities assigned for the user.
EAM: Object Instantiation API Log File Directory
The Object Instantiation API is called when a new asset number is created via the Asset Number window or if the Instantiate button is chosen within the Rebuildable Serial Number window. This profile option indicates the debug file directory that the debug log will reside, if debugging is enabled for the Object Instantiation API. For example, If the profile option, EAM: Object Instantiation API Log Option, is set to Yes, the log of the activity process is saved in the directory determined by the path designated in the current profile option. This profile option is visible and changeable at the User level; it is visible and changeable at System Administrator's User, Responsibility, Application, and Site levels.
EAM: Object Instantiation API Log File Name
The Object Instantiation API is called when a new asset number is created via the Asset Number window or if the Instantiate button is chosen within the Rebuildable Serial Number window. This profile option indicates the debug file name that resides in the debug file directory, if debugging is enabled for the Object Instantiation API. For example, If the profile option, EAM: Object Instantiation API Log Option, is set to Yes, the log of the activity process is saved in the directory determined by the path designated by the EAM: Object Instantiation API Log File Directory profile option. The name of the file that includes the activity process log is determined by the current profile option. This profile option is visible and changeable at the User level; it is visible and changeable at System Administrator's User, Responsibility, Application, and Site levels.
EAM: Object Instantiation API Log Option
The Object Instantiation API is called when a new asset number is created via the Asset Number window or if the Instantiate button is chosen within the Rebuildable Serial Number window. This profile option indicates whether debugging is enabled for the activity API. This profile option is visible and changeable at the User level; it is visible and changeable at System Administrator's User, Responsibility, Application, and Site levels.
EAM: PM Debug File (including complete file path)
This profile option indicates the directory location where debug files will be created if debug mode is enabled. The profile option is visible and changeable at the User level; it is visible and changeable at System Administrator's User, Responsibility, Application, and Site levels. The internal name of the profile option is EAM_DEBUG_FILE. The default value is a file path inserted by the auto-configuration utility, executed during the installation of the application, and appended by the file name, viz.eampmeng.log.
EAM: Trigger requisition for canceled/rejected quantity
This profile option specifies whether a requisition must be created when the status of a work order with a direct item is changed, such as put on hold, released or quantity is updated.
EAM: Use Work Order Org for EAM Endeca Security
This profile option is used in Endeca security. If set to Y or null, the work order organization is used for Endeca security. If it is set to N, the asset organization is used for Endeca security.
Profiles that help the eAM integration with other Oracle Applications are listed below. If you are implementing other Oracle Applications, you will need to set up additional profile options as appropriate. Please refer to the applications' respective user's guides or implementation manuals for more details.
Profile Option | User | System Admin: USER |
System Admin: RESP |
System Admin: APP |
System Admin: SITE |
Required? | Default |
---|---|---|---|---|---|---|---|
INV: Default Primary Unit of Measure | View Update |
View Update |
View Update |
View Update |
View Update |
Y | - |
INV: Item Default Status | View Update |
View Update |
View Update |
View Update |
View Update |
Y | - |
PO: Enable Direct Delivery To Shop Floor | View Update |
View Update |
View Update |
View Update |
View Update |
N | - |
Relevant profile options in other applications are listed below:
INV: Default Primary Unit of Measure
You can specify any user-defined or seeded value for this profile.
INV: Item Default Status
You can specify any user-defined or seeded value for this profile.
PO: Enable Direct Delivery To Shop Floor
This profile option is a prerequisite for an eAM User to create Purchase Requisitions for Direct Items via Oracle Purchasing and iProcurement. This profile option must be set to Yes if you need to create Purchase Requisitions using Oracle Purchasing and iProcurement applications.
Related Topics
Personal Profile Values Window, Oracle Applications User's Guide
Overview of Setting User Profiles, Oracle Applications System Administrator's Guide
Common User Profile Options, Oracle Applications User's Guide