9 Condition Based Alert

This chapter includes these topics:

9.1 Condition Based Alert Overview

This chapter provides detailed information about the business interfaces that are available for the Condition Based Alert business object.

This table lists all of the available interface components:

Interface Type Available Interfaces
Business Services The CapitalAssetManager published web service (JP130000) manages these methods:
  • J1300001 (createCapitalAssetConditionBasedAlert)

  • J1300002 (getCapitalAssetConditionBasedAlert)

Batch Import Programs Available batch import programs:
  • Inbound Condition-Based Alerts Processor program (R1310Z1I)

Orchestration (Release 9.1 Update) Add Condition-Based Maintenance Alert

For additional information about the Add Condition-Based Maintenance Alert orchestration, see Section 7.1.1, "Add Condition-Based Maintenance Alert".



Note:

You can find additional technical information about each type of business interface component. For additional descriptions of the information available, and instructions for finding this information, see Chapter 5, "Accessing Additional Information for Business Interface Components."

9.2 Condition Based Alert Business Services - CapitalAssetManager

The CapitalAssetManager web service (JP130000) manages the processing of capital asset-related web service operations. This table includes a description of the capital asset web service operations:

Operation Description
createCapitalAssetConditionBasedAlert Use this operation to add capital asset condition-based alerts within the JD Edwards EnterpriseOne Plant and Equipment Management system.
getCapitalAssetConditionBasedAlert Use this operation to query the JD Edwards EnterpriseOne database for existing capital asset condition-based alerts.

9.2.1 Accessing Javadoc for the Capital Asset Manager Web Service Operations

To access Javadoc for the Capital Asset Manager web service and its related operations, review these Javadoc packages:

  • JP130000 (CapitalAssetManager)

  • J1300001 (createCapitalAssetConditionBasedAlert)

  • J1300002 (getCapitalAssetConditionBasedAlert)

9.2.2 Prerequisites

Before using the Capital Asset Manager web service, or any of the related web service operations, you must install and configure the JD Edwards EnterpriseOne Capital Asset Management product including the JD Edwards EnterpriseOne Plant and Equipment Management and JD Edwards EnterpriseOne Condition-Based Maintenance systems.

See JD Edwards EnterpriseOne Applications Capital Asset Management Implementation Guide.

See JD Edwards EnterpriseOne Applications Condition-Based Maintenance Implementation Guide.

9.2.3 createCapitalAssetConditionBasedAlert

The createCapitalAssetConditionBasedAlert web service operation is an inbound transaction operation that enables consumers to process condition-based alert information within the JD Edwards EnterpriseOne system. The consumer can add capital asset condition-based alerts in the JD Edwards EnterpriseOne Plant and Equipment Management system.

If the operation is successful, the system creates condition-based alerts and commits the records.

If the operation fails, the system returns error messages to the consumer.

The createCapitalAssetConditionBasedAlert web service operation calls the XPIConditionBasedAlert master business function (N1301150) to process the capital asset record. When a condition-based alert is successfully created, a condition-based alert key is returned to the caller through the Alert ID. Exceptions are sent to the caller. The minimum required fields to create a condition-based alert in JD Edwards EnterpriseOne are equipmentNumber, alertLevel, eventDate, eventTime, description, and automatedResponseType.

9.2.3.1 Supported Functionality

This section discusses the functionality that the createCapitalAssetConditionBasedAlert operation supports.


Note:

If functionality is not explicitly documented as supported functionality, it is to be understood that the functionality is not supported by the integration solution.

The createCapitalAssetConditionBasedAlert operation supports adding capital asset condition-based alerts in the JD Edwards EnterpriseOne Plant and Equipment Management system.

The createCapitalAssetConditionBasedAlert operation does not support updating or deleting capital asset condition-based alerts.

9.2.3.2 Setup Considerations

Before you use this operation, you can set business service properties to specify how the system processes condition-based alert information. This table includes information about the business service properties that the createCapitalAssetConditionBasedAlert web service operation uses:

Group Key Description Default Value
J1300001 J1300001_CBA_MBF_VERSION Use this business service property to specify which version of the XPI Condition-Based Alerts program (P1301150) the operation uses. ZJDE0001
J1300001 J1300001_PREFIX_1 Use this business service property to specify the prefix value the operation uses for error messages. Capital Asset Send In

See JD Edwards EnterpriseOne Tools Business Services Development Methodology Guide.

9.2.3.3 Implementation Details

The following table includes information that can help determine whether the createCapitalAssetConditionBasedAlert operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, the system does not return an error message.

If the operation succeeds and returns records, the system returns non-zero values for these fields:

  • alertId

  • description

  • alertLevelCode

  • alertStatusCode

  • automatedResponseTypeCode

  • notificationRecipient

If I encounter errors while processing a transaction, do I need to reverse the transaction? This operation uses standard transaction processing. Therefore, if you encounter errors during processing, the system does not update any information in the JD Edwards EnterpriseOne system. No manual update is necessary.
Does this operation use record reservation? No. This operation does not reserve records.

9.2.4 Setting Processing Options for XPI Condition-Based Alerts (P1301150)

Processing options enable you to specify the default processing for programs and reports.

For programs, you can specify options such as the default values for specific transactions, whether fields appear on a form, and the version of the program that you want to run.

9.2.4.1 Process

1. Equipment Number Format

Specify how the system validates the equipment number. Values are:

1: Use the equipment number. This is the default value.

2: Use the unit number.

3: Use the serial number.

9.2.4.2 Versions

1. Condition-Based Alerts Revisions (P1311) Version

Specify the version that the system uses for the Condition-Based Alerts Revisions program (P1311). If you leave this processing option blank, the system uses the ZJDE0001 version.

2. Condition-Based Alerts Processor (R1312) Version

Specify which version of the Condition-Based Alerts Processor program (R1312) the system uses when processing the automated responses of condition-based alerts. If you leave this processing option blank, the system does not process the automated responses of condition-based alerts. Note: If you leave this processing option blank, you must run a version of the Condition-Based Alerts Processor program (R1312) in order to complete the automated response-type processing.

9.2.5 getCapitalAssetConditionBasedAlert

The getCapitalAssetConditionBasedAlert web service operation is a database query operation that enables consumers to query the JD Edwards EnterpriseOne Plant and Equipment Management system to retrieve existing capital asset data. The getCapitalAssetConditionBasedAlert operation invokes a database operation to retrieve capital asset information from the Condition-Based Alerts table (F1310) in JD Edwards EnterpriseOne based on the selection criteria specified in the value object.

The getCapitalAssetConditionBasedAlert web service operation allows an open query.


Note:

An open query of the JD Edwards EnterpriseOne database impacts system performance. It is strongly recommended that you set the Max Rows business service property to a value other than 0 (zero). If you leave this value set to 0, the system returns all matching records. Additionally, it is recommended that you specify selection criteria when you query the JD Edwards EnterpriseOne database.

If the operation is successful, the system returns zero to many records to the consumer. You can specify the maximum number of records to return during a query using the Max Rows business service property.

If the operation fails, the system returns an error message to the consumer.

The getCapitalAssetConditionBasedAlert web service operation queries the JD Edwards EnterpriseOne condition-based alert information in a real-time fashion. The web service operation, getCapitalAssetConditionBasedAlert, is called by the source system. This web service operation consumes a published interface, GetCapitalAssetConditionBasedAlert, which exposes the selection criteria for retrieving the condition-based alert information from the F1310 table in JD Edwards EnterpriseOne. The fields in GetCapitalAssetConditionBasedAlert are used to set the selection in the getCapitalAssetConditionBasedAlert integration. The web service operation returns results in the ShowCapitalAssetConditionBasedAlert published interface.


Note:

The system adjusts the date time stamp entered to Coordinated Universal Time (UTC), which the system determines using the time zone on your business service server, unless an offset is used. For example, if the business service server is GMT-7, entering 2007-01-18T00:00:00.000 results in an adjustment to this value of -7 hours, and the actual value that passes in to JD Edwards EnterpriseOne becomes 2007-01-17T17:00:00.000. An offset can be passed in with the original value so that these adjustments do not occur, such as 2007-01-18T00:00:00.000-7:00, which offsets by 7 hours from UTC, resulting in the date being passed into JD Edwards EnterpriseOne as 2007-01-18T00:00:00.000.

9.2.5.1 Supported Functionality

This section discusses the functionality that the getCapitalAssetConditionBasedAlert operation supports.


Note:

If functionality is not explicitly documented as supported functionality, it is to be understood that the functionality is not supported by the integration solution.

The getCapitalAssetConditionBasedAlert operation supports a database query operation that enables consumers to query the JD Edwards EnterpriseOne Plant and Equipment Management system to retrieve existing capital asset data.

The getCapitalAssetConditionBasedAlert operation does not support the wildcard (asterisk (*)) for search criteria.

9.2.5.2 Setup Considerations

Before you use this operation, you can set business service properties to specify how the system processes capital asset information. This table includes information about the business service properties that the getCapitalAssetConditionBasedAlert web service operation uses:

Group Key Description Default Value
J1300002 J1300002_F1310_MAX_GRID_ROWS_RETURNED Use this business service property to define the maximum number of rows that the operation returns when querying the JD Edwards EnterpriseOne database. 100


Note:

It is strongly recommended that you set this business service property to a value other than 0 (zero). If you leave this value set to 0, the system returns all matching records. Additionally, it is recommended that you specify selection criteria when you query the JD Edwards EnterpriseOne database.

See JD Edwards EnterpriseOne Tools Business Services Development Methodology Guide.

9.2.5.3 Implementation Details

The following table includes information that can help determine whether the getCapitalAssetConditionBasedAlert operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, the system does not return an error message.

If the operation completes successfully, the system returns records that match your search criteria. These records include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, if the query finds matching records, the system returns non-zero values for these fields:

  • alertId

  • description

  • alertLevelCode

  • alertStatuscode

  • automatedResponseTypeCode

  • dateRequested

  • timeRequested

  • eventTimeUTC

  • itemAsset

The operation may complete successfully without returning rows because the selection criteria did not match any records in the database or an open query was performed and there were no records. This is considered successful and provides valid information.

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions.

If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database.

Does this operation use record reservation? No. This operation does not reserve records that are returned in a query.

9.3 Condition Based ALert Batch Import Programs

You use batch import programs to import data from an external software system into the JD Edwards EnterpriseOne system, where it can then be processed by EnterpriseOne programs.

This table lists and describes the available batch import programs that are associated with the Condition Based Alerts business object:

Program and Program Type Description Available Documentation
Inbound Condition-Based Alerts Processor program (R1310Z1I)

This is an interoperability batch program.

Use this program to copy the information from the F1310Z1 table to the Condition-Based Alerts table (F1310). The program also performs these functions:
  • Processes the inbound condition-based alerts transactions.

  • Updates the F1310 table.

  • Initiates any required downstream processing that is based on the transaction information or the alert action rules by running a version of the Condition-Based Maintenance Alerts program (R1312).

See this topic for additional information: