Siebel Field Service Guide > Preventive Maintenance > Preventive Maintenance Engine >

Parameters for the Preventive Maintenance Engine


Siebel Business Process Designer or the client can invoke all engines. These engines require certain parameters to be passed. Table 132 describes the parameters for the Preventive Maintenance Engine.

Table 132. Preventive Maintenance Engine Parameters
Parameter
Values
Description

Mode

{SQL, Id, TempTbl}

This required parameter specifies how the engine locates the entities to process. Only SQL or ID should be specified in user requests. TempTbl is used by the client applications for submitting requests.

Sub-mode

{Assets, Plans, Assets&Plans, Agreements}

This required parameter identifies which entities are specified. A Sub-mode of Assets implies ALL PM Plans, and a Sub-mode of Plans implies ALL Assets.

End Date

YYYY-MM-DD format

This required parameter specifies the date furthest into the future for which the engine will generate PM Actions. Note that currently, only time-based triggers can fire for a future date.

Asset ID

Row ID of an asset

This parameter specifies a specific asset. It is required when the Mode is Id and the Sub-mode is either Assets or Assets&Plans.

Plan ID

Row ID of a PM Plan

This parameter specifies a specific PM Plan. It is required when the Mode is Id and the Sub-mode is either Plans or Assets&Plans.

Agreement ID

Row ID of an agreement

This parameter specifies a specific Agreement. It is required when the Mode is Id and the Sub-mode is Agreements.

Asset SQL

Where clause for the GET_SQL_ASSETS template. The where clause takes the following form:

[BusComp Field Name] = 'Value'

This parameter specifies a search specification for assets. It is required when the Mode is SQL and the Sub-mode is either Assets or Assets&Plans.

The SQL template for retrieving assets is as follows:

GET_SQL_ASSETS =
   SELECT asset.ROW_ID
   FROM   &Table_Owner.S_ASSET   asset
   WHERE   $SEARCH_SPEC$

The value supplied as the Asset SQL parameter is substituted for '$SEARCH_SPEC$.' Thus, any specification that completes this template with valid values is allowed for the parameter.

Plan SQL

Where clause for the GET_SQL_PM_PLANS template. The where clause takes the following form:

[BusComp Field Name] = 'Value'

This parameter specifies a search specification for PM plans. It is required when the Mode is SQL and the Sub-mode is either Plans or Assets&Plans.

The SQL template for retrieving PM Plans is as follows:

GET_SQL_PM_PLANS =
   SELECT pln.ROW_ID
   FROM   &Table_Owner.S_PM_PLNITM   pln
   WHERE   pln.ACTIVE_FLG = 'Y'
      AND $SEARCH_SPEC$

The value supplied as the Plan SQL parameter is substituted for '$SEARCH_SPEC$.' Thus, any specification that completes this template with valid values is allowed for the parameter.

Agreement SQL

Where clause for the GET_SQL_AGREEMENT_IDS template. The where clause takes the following form:

[BusComp Field Name] = 'Value'

This parameter specifies a search specification for agreements. It is required when the Mode is SQL and the Sub-mode is Agreements.

The SQL template for retrieving PM Agreements is as follows:

GET_SQL_AGREEMENT_IDS =
   SELECT agrmnt.ROW_ID
   FROM   &Table_Owner.S_DOC_AGREE   agrmt
   WHERE   agrmnt.VALID_FLG = 'Y'
      AND $SEARCH_SPEC$

The value supplied as the Agreement SQL parameter is substituted for '$SEARCH_SPEC$.' Thus, any specification that completes this template with valid values is allowed for the parameter.

Siebel Field Service Guide Copyright © 2007, Oracle. All rights reserved.