Template fields

The following fields are included with the SAP Work Notification integration and are defaulted in this order

Note: Work Order Request fields are imported to the List Manager’s Response List, under the root node "SAP Response Lists," during Data Transformation.

QMEL-QMART – Work Notification Type field. This list, Types M1 through MX is mandatory for SAP Work Notifications and the list presented to the user may be limited based on the integration setup. This field might be setup as Required or with a default value as needed.

QMEL-QMNUM – Work Notification number field. This is a number automatically assigned by SAP, thus it will not appear in a new WOR screen during creation. Once the new WOR has been sent to SAP, it will be assigned a Notification Number. When the existing Notifications are updated within the database the newly created notification will be updated with the proper number. It is recommended that this field be set to "Read Only" and Not Required.

TJ02T-TXT30 – System Status field. This is a code automatically assigned by SAP, thus it will not appear in a new WOR screen during creation. Once the new WOR has been sent to SAP, it will be assigned a System Status which can change due to user update of the Work Notification in SAP. When the existing Notifications are updated within the database the newly created notification will be updated with the proper number. It is recommended that this field be set to "Read Only" and Not Required.

QMEL-PRIOK – This field is used for setting a priority on the work that needs to be done. A list of priority codes with descriptions will be displayed for selection. Generally, this will be a pre-defined list transferred from the SAP database.

ILOA-KOSTL – This field is used to indicate the cost center. This field is generally set by SAP and corresponds to the Functional Location associated with this Notification. Once the new WOR is transferred to the SAP database, it is automatically assigned a cost center. It is recommended that this field be set to "Read Only" and Not Required. Generally, this will also be a ‘Hidden’ field. (See Template columns for more information regarding the ‘Hidden’ field option.)

ILOA-TPLNR – This field is the Functional Location as configured in the SAP Database. This field is mandatory for the creation of SAP Notifications and so it is recommended that this field be set to "Required". This field will be automatically filled in by AVEVA Mobile Operator if this Notification is triggered by an action on a task by setting the Default Value Smart Tag to "%asset%". This field may also be filled out by the scanning of a RFID/NFC tag if the "Tag Name" section of the Template is configured with the appropriate RFID/NFC Tag Field name. (See Template columns for more information regarding Smart Tags and the ‘Hidden’ field option.)

QMIH-MSAUS – Breakdown Indicator flag. This flag is required for many customer implementations of SAP. The setting of this flag is also used to drive the requirements of QMIH-AUSVN, QMIH-AUZTV below

QMEL-QMTXT – This field requires the user to enter a short description for the work that needs to be done. The user will be allowed to either enter free text or to select from the Default Notes list to complete this field. This field can be configured to be automatically populated with data from the procedure task action by setting the default value within the Template to use the Smart Tag "%condition%". (See Template columns for more information regarding Smart Tags.)

RSTXT-TXLINE – This option is similar to the Short Text field. It is used to enter a detailed description of the work that needs to be done. This field can be configured to be automatically populated with data from the procedure task notes by setting the default value within the Template to use the Smart Tag "%note%". (See Template columns for more information regarding Smart Tags.)

"a" (QMFE-OTGRP / QMFE-OTEIL) Object Part – The Object Part Group Code (QMFE- OTGRP) is tied to the Object Part Code (QMFE- OTEIL) so that the choice of a Object Part Group Code will then filter choices for the Object Part Code.

• If the Object Part Group Code is required then by default the Object Part Code will be required.

• If the Object Part Group Code is visible then by default the Object Part Code will be visible.

• The "Catalog Profile" property on the Functional Location is used to filter the Object Part Group Code. If blank, this selection is unfiltered.

  "b" (QMFE-FEGRP / QMFE-FECOD) Problem – The Problem Group Code (QMFE-FEGRP) is tied to the Problem Code (QMFE-FECOD) so that the choice of a Problem Group Code will then filter choices for the Problem Code.

• If the Problem Group Code is required then by default the Problem Code will be required.

• If the Problem Group Code is visible then by default the Problem Code will be visible.

• The "Catalog Profile" property on the Functional Location is used to filter the Problem Group Code. If blank, this selection is unfiltered.

QMFE-FETXT – Problem Text is not filtered by the Problem Group Code. This field is provided to allow additional data entry related to the Problem.

"c" (QMUR-URGRP /QMUR-URCOD) Cause – The Cause Group Code (QMUR-URGRP) is tied to the Cause Code (QMUR-URCOD) so that the choice of a Cause Group Code will then filter choices for the Cause Code.

• If the Cause Group Code is required then by default the Cause Code will be required.

• If the Cause Group Code is visible then by default the Cause Code will be visible.

• The "Catalog Profile" property on the Functional Location is used to filter the Cause Group Code. If blank, this selection is unfiltered.

QMUR-URTXT – Cause Text is not filtered by the Cause Group Code. This field is provided to allow additional data entry related to the Cause.

QMEL-ERDAT - This field is used to enter the date that the WOR was entered. The current date can be automatically selected as the default date by entering the Smart Tag "%date%" within the Template. (See Template columns for more information regarding Smart Tags.)

QMEL-MZEIT – This field is used to enter the time that the Notification was entered.

"d" (QMIH-AUSVN / QMIH-AUZTV) Malfunction Date & Time – These fields are used to record the malfunction date and time to SAP as this may be different from the reported date and time.

• These fields are visible if the "Breakdown" field (QMIH-MSAUS) is visible

• These fields are required if Breakdown is set to "Yes" on the mobile device.

• These fields are not required if Breakdown is set to "No" on the mobile device.

QMEL-STRMN – This field is used to enter a requested start date for the work that needs to be done. A calendar will automatically populate this screen. The current date is automatically selected as the default date. The user can select another date or the user can proceed to the next screen with no selection which will automatically select the default date.

QMEL-STRUR – Requested Start Time for repair

QMEL-LTRMN – This field is used to enter a requested completion date for the work that needs to be done. A calendar will automatically populate this screen. The current date is automatically selected as the default date. The user can select another date or the user can proceed to the next screen with no selection which will automatically select the default date.

QMEL-STRUR – Requested Completion Time for repair

QMEL-QMNAM – This field is used to identify who is requesting the work. This field can be configured to be automatically populated with the login information for the user that is creating the Work Notification by setting the default value within the Template to use the Smart Tag "%name%". (See Template columns for more information regarding Smart Tags.)

QMEL-ARBPL – This field identifies the group, or department, that is typically responsible for performing the work requested in the notification. This field may be required to complete the SAP work notification.

QMEL-ZZCONSC – This optional datum identifies the consequence category. Possible options are: A - Asset Damage / Deferment; E - Environment; P - People; and R - Reputation.

QMEL-ZZCONSS – This optional datum indicates the consequence severity. Possible options are: 1 - Slight Impact; 2 - Minor Impact; 3 - Moderate Impact; 4 - Major Impact; and 5 - Massive Impact.

QMEL-ZZLIKEHD – This optional datum identifies the likelihood of the consequence’s occurrence. Possible options are: A - Unlikely to occur within 12 months; B - Likely to occur between three months and 12 months; C - Likely to occur between two weeks and three months; D - Likely to occur between two days and two weeks; and E - Likely to occur within one or two days or is occurring now.