## Processing Interoperability for Condition-Based Maintenance

This chapter discusses how to:

- Process inbound interoperability for Condition-Based Maintenance.

- Review and revise interoperability transactions for Condition-Based Maintenance.

- Purge interoperability transactions for Condition-Based Maintenance.

### Processing Inbound Interoperability for Condition-Based Maintenance

This section provides an overview of inbound interoperability for Condition-Based Maintenance, lists prerequisites, and discusses how to:

- Set processing options for Inbound Condition-Based Alerts Processor (R1310Z1I).

- Process inbound condition-based alerts.

#### Understanding Inbound Interoperability for Condition-Based Maintenance

You run the Inbound Flat File Conversion program (R47002C) to copy the data from an external text file into the Unedited Condition-Based Alerts table (F1310Z1). The Inbound Flat File Conversion program validates the text file against the F1310Z1 table and the data dictionary specifications for the table. If the text file passes this validation, the system adds the data to the F1310Z1 table.

You can use the Unedited Condition-Based Alert Revisions program (P1310Z1) to add, update, and review the transactions in the F1310Z1 table.

You run the Inbound Condition-Based Alerts Processor program (R1310Z1I) to copy the information from the F1310Z1 table to the Condition-Based Alerts table (F1310).

The Inbound Condition-Based Alerts Processor program (R1310Z1I) 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).

The report displays the transaction information, including whether the transaction was successful; user ID; batch number; transaction number; equipment number; description; alert level; event date; event time; and time zone. After the alert has been successfully processed, you can use the Condition-Based Alerts program (P1310) to review and process the alert.

The Inbound Condition-Based Alerts Processor program (R1310Z1I) requires that the F1310Z1 interface table have data in these fields:

- Asset Number (NUMB), Unit Number (APID), or Serial Number (ASID).

- Product Model (PRODM).

- Automated Response Type (TYRP).

- Description (DL01).

- Event Date (EVTDT).

- Event Time (EVTTM).

  You can enter the event date and time using the Coordinated Universal Time (UTC) or the local date and time with time zone.

- Alert Level (PDFL).

These fields are frequently used, but are optional:

- Measurement Location (MELC).

- Time Zone (TIMEZONES).

- Daylight Savings Rule Name (DSAVNAME).

- Send Notification Message (SNDN).

- Notification Recipient (NOTR).

- Notification Structure Type (NSTT).

- Investigation Recipient (INVR).

- Investigation Structure Type (ISTT).

- Model Work Order (DOCO).

- Service Type (SRVT).

You can use a number of setup applications within the Condition-Based Maintenance system to define rules based on the equipment coding in order to supply default values for some of the optional fields if they are not populated by the import process. These setup applications include:

- Condition-Based Maintenance Message Sequences (P1315).

- Condition-Based Maintenance Message Rules (P1316).

- Condition-Based Maintenance Alert Action Sequences (P1317).

- Condition-Based Maintenance Alert Action Rules (P1318).

#### Prerequisites

Before you complete the tasks in this section:

- Set up flat file cross-references.

  See Setting Up the Flat File Cross-Reference.

  Note. The system provides transaction type CBMALERT for condition-based maintenance alert transactions.

- Run the Inbound Flat File Conversion program (R47002C).

  See Running the Inbound Flat File Conversion Program (R47002C).

#### Setting Processing Options for Inbound Condition-Based Alerts Processor (R1310Z1I)

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

Process

1. Work Center or Report | Specify where the system writes errors. Values are: Blank: Write errors to the Work Center. 1: Write errors on the report.
2. Job Status Message Recipient | Specify the address book number of the recipient of job status messages that result from the Inbound Condition-Based Alerts Processing program (R1310Z1I). If you leave this processing option blank, the system uses the address book number of the current user.
3. Equipment Number Format | Specify how the Inbound Condition-Based Alerts Processing program (R1310Z1I) validates and displays the equipment number. Values are: 1: Use the equipment number 2: Use the unit number 3: Use the serial number

Versions

1. Condition-Based Alerts Revisions (P1311) Version | Specify the version of the Condition-Based Alerts Revisions program (P1311) that the system uses. If you leave this processing option blank, the system uses ZJDE0001.
2. Condition-Based Alerts Processor (R1312) Version | Specify the version of the Condition-Based Alerts Processor program (R1312) that the system uses. If you leave this processing option blank, the system uses XJDE0001.

#### Processing Inbound Condition-Based Alerts

Select Condition-Based Maintenance Interoperability (G13CBM311), Inbound Condition-Based Alerts.

### Reviewing and Revising Interoperability Transactions for Condition-Based Maintenance

This section provides an overview of reviewing and revising interoperability transactions for Condition-Based Maintenance, lists the form used to review and revise interoperability transactions for Condition-Based Maintenance, and discusses how to set processing options for Unedited Condition-Based Alerts Revisions (P1310Z1).

#### Understanding Reviewing and Revising Interoperability Transactions for Condition-Based Maintenance

Running a transaction process, such as Inbound Condition-Based Alerts Processor (R1310Z1I), often identifies one or more inbound transactions that contain invalid transactions. The Inbound Condition-Based Alerts Processor program identifies the invalid transaction and sends an error message to the Work Center (P012501). The error message indicates the transaction number for the transaction in error.

You can use the Inbound Condition-Based Alerts Inquiry program (P1310Z1) to review and revise inbound transactions. You can add, change, or delete transactions containing errors. Then run the transaction process again. Continue to make corrections and rerun the transaction process until the program runs without errors.

#### Form Used to Review and Revise Interoperability Transactions for Condition-Based Maintenance

Form Name | FormID | Navigation | Usage
Unedited Condition-Based Alerts Revisions | W1310Z1B | Condition-Based Alerts Interoperability (G13CBM311), Inbound Condition-Based Alerts Inquiry On Work With Unedited Condition-Based Alerts, from the View menu, select Direction and then select Inbound. | Review inbound condition-based alerts. Note. You can used the options on the View menu to review records that processed successfully (Processed) and those that failed to process (Errors). Correct the data for any errors before rerunning the Inbound Condition-Based Alerts Processor program (R1310Z1I).

#### Setting Processing Options for Inbound Condition-Based Alerts Inquiry (P1310Z1)

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

Display

1. Default View Mode | Use this processing option to enter the default view mode. Values are: 1: View unprocessed transactions only. 2: View transactions that processed successfully. 3: View transactions that processed unsuccessfully.
2. Direction Indicator | Specify whether transactions are inbound or outbound. Values are: 1: Inbound 2: Outbound

Defaults

1. Transaction Type | Enter the transaction type for new condition-based alerts transactions. If you leave this processing option blank, the system uses CBMALERT.

Process

1. Inbound Subsystem UBE Name | Specify the name of the inbound subsystem program that the system uses to process inbound transactions. If you leave this processing option blank, the system uses R1310Z1I (Inbound Condition-Based Alerts Processing program).
2. Inbound UBE Version | Specify the version of the Inbound Condition-Based Alerts Processing program (R1310Z1I) that the system uses. If you leave this processing option blank, the system uses XJDE0001.

### Purging Interoperability Transactions for Condition-Based Maintenance

This section provides an overview of purging interoperability transactions and discusses how to purge interoperability transactions.

#### Understanding Purging Interoperability Transactions

When data becomes obsolete or when you need more disk space, you can use the Inbound Condition-Based Alerts Purge program (R1310Z1P) to remove data from the Unedited Condition-Based Alerts table (F1310Z1).

For records in the Processing Log table (F0046) that are marked as processed, the program purges the associated transactions in the F1310Z1 table, as well as the records in the F0046 table. If the records in the F0046 table are not marked as processed, the program does not purge any records.

See JD Edwards EnterpriseOne Tools 8.98 Interoperability Guide.

#### Purging Interoperability Transactions

Select Condition-Based Maintenance Interoperability (G13CBM311), Inbound Condition-Based Alerts Purge.