System

Type of CMMS system with which APM exchanges information, for example, Maximo, Oracle eAM, or SAP Plant Maintenance.

System version

The version of Oracle eAM E-Business Suite.

Line length

The length of separate lines sent to SAP for long text descriptions.

Break long descriptions into separate lines

If this option is selected, long text descriptions (for assets, tasks, jobs, and so on) are broken into separate lines when they are sent to SAP.

Asset type

The asset type in the CMMS system. The suffix will be added to APM asset numbers for assets of this type.

Append a suffix to the asset number

If you are integrating two or more asset types from the CMMS to APM, you can define a suffix for each type of asset. The suffix is appended to the CMMS number when the asset number is created.

Suffix

The characters to append to asset numbers.

Asset type

The asset type in the CMMS system. The suffix will be added to APM asset numbers for assets of this type.

Append a suffix to the asset number

If you are integrating two or more asset types from the CMMS to APM, you can define a suffix for each type of asset. The suffix is appended to the CMMS number when the asset number is created.

Suffix

The characters to append to asset numbers.

Asset hierarchy 1 synchronization to the CMMS hierarchy

Select one of the following options for synchronizing asset hierarchy 1. You can choose: • Always synchronized. All changes to the CMMS hierarchy are made to the APM hierarchy. APM assets created from a CMMS asset use the CMMS parent to create the APM hierarchy. When this option is selected, you cannot change an asset’s parent. This is the most commonly used option. • New assets only. Only additions to the CMMS hierarchy are synchronized to the APM hierarchy. Hierarchy changes to existing assets are not reflected in the APM hierarchy. This option is selected in cases where your implementation team has decided that the CMMS hierarchy provides a good initial definition for APM, but changes are required. You can manually change an asset’s parent in APM. • Not synchronized. The CMMS and APM hierarchies are not synchronized. This option is selected in cases where your implementation team has decided that the CMMS hierarchy is not appropriate for the purposes of APM. The APM hierarchy is defined within APM itself. • Custom. A customized integration is used, so changes in the CMMS hierarchy are not made to the APM hierarchy.

	See Also

Alternate hierarchy to synchronize to the CMMS hierarchy

To synchronize another hierarchy instead of or in addition to hierarchy 1, select the appropriate option. Choose: • Always synchronized. All changes to the CMMS hierarchy are made to the APM hierarchy. APM assets created from a CMMS asset use the CMMS parent to create the APM hierarchy. When this option is selected, you cannot change an asset’s parent using the Parent Assets tab. • New assets only. Changes to the CMMS hierarchy are made to the APM hierarchy. APM assets created from a CMMS asset use the CMMS parent to create the APM hierarchy. You can manually change an asset’s parent in APM. • Not synchronized. Changes in the CMMS hierarchy are not made to the APM hierarchy. You can maintain the asset hierarchy manually in APM. • Custom. A customized integration is used, so changes in the CMMS hierarchy are not made to the APM hierarchy. Select the hierarchy to synchronize from the list.

Hierarchy to synchronize

Select the hierarchy to synchronize with the CMMS.

Hierarchy to use

Assets that are maintained exclusively in APM must have default CMMS information so that they can be referenced on work orders (for example) that are sent to the CMMS. APM retrieves this information from the asset’s first ancestor in the selected hierarchy with a CMMS identification number.

Check that the job’s tasks have been successfully integrated when the job is marked as ready to send

A standard job typically contains a list of standard job tasks. To integrate the list of tasks along with the standard job, the tasks must be sent to the CMMS before the job is sent. Select this option to have APM check whether the standard job’s tasks exist in the CMMS before the standard job can be marked as “Ready to Send”. If your integration includes synchronizing job tasks, you must leave this option selected. Clearing this option results in errors in the integration if the referenced job task objects do not exist in the CMMS when the job is sent. However, if you do not wish to send standard job tasks to the CMMS, you can clear this option. In this case, you can send standard jobs alone. Note: Clearing this option does not remove the standard job tasks from the APM interface classes or XML documents. The interface mapping must also be modified to exclude the job’s tasks.

Standard job numbers

Use these options to control how standard job numbers are constructed. Choose from: • Use APM number – the APM number is used as entered for standard jobs created in APM. Note: For jobs that originate from an Oracle eAM activity, the PM schedule number is used. • Use APM number plus site ID – the site’s ID is appended to the standard job number.

Task status

You can enter a task status to indicate that all standard tasks on a job are available for use in the CMMS. Enter the appropriate CMMS task status in the box. Note: This status is specific to your CMMS and does not relate to any status used in APM. As well, if a work order is based on a standard task, the standard task’s CMMS task number is included in the outbound message if the standard task has the specified status.

Standard task numbers

Use these options to control how standard task numbers are constructed. Choose from: • Use APM number – the APM number is used as entered for standard tasks created in APM. Note: For tasks that originate from an Oracle eAM activity, the activity number is used. • Use APM number plus site ID – the site’s ID is appended to the standard task number. Note: For Oracle eAM integration, it is recommended that this option be selected because activity numbers are not unique by organization.

Notification type

Enter the notification type that will identify notifications created from APM work orders.

Use the assigned Maximo work order #

You can specify that work order numbers assigned by Oracle eAM also be used in APM. However, you must designate a field in Oracle eAM where the APM number can be stored when the work order is sent from APM. The Oracle eAM number is then returned to APM, where the work order is renumbered. To activate this option: • Select Use the assigned Maximo work order #. • In the box below this option, enter the Oracle eAM field where the APM number is to be stored.

Maximo attribute where the EXP work order number is stored

You can specify that work order numbers assigned by Oracle eAM also be used in APM. However, you must designate a field in Oracle eAM where the APM number can be stored when the work order is sent from APM. The Oracle eAM number is then returned to APM, where the work order is renumbered. To activate this option: • Select Use the assigned Maximo work order #. • In this box, enter the Oracle eAM field where the APM number is to be stored.

Default asset type

If the Oracle eAM asset has not been assigned to an asset category, this asset type is assigned to the asset when it is imported into APM.

Work request type

The work request type assigned to all Oracle eAM work requests created from APM work requests. This must be a valid work request type in Oracle eAM.

Task multiplier

The task multiplier (for example, “10”) is used to convert work order task numbers to operation numbers suitable for Oracle eAM.

Base triggering interval

The default triggering interval, in days, for all standard jobs with a “rule based” schedule type.

Base triggering interval

The number of days used to calculate the initial trigger date for all standard jobs with a “list dates” schedule type.