Administration

1. Access ASI admin settings.
2. In the workspace, select .
   A blank datasheet appears.
3. In the Master section, select the appropriate option from the Family ID drop-down menu.
4. In the Detail section, select the Child Definitions from the Child Family ID - Value(s) and Child Family Relationship ID - Value(s) drop-down menus.
5. Select .
   The Work Management Item Definition is created.

1. Access ASI admin settings.
2. Select Create for the WMI that you want to add to a mapping configuration.
   The datasheet associated with the configuration appears.
3. Modify the appropriate fields, and then select .
   The mapping configuration has been created and saved.

   Tip: To view the baseline mappings and associated mapping Policies, refer to Action Mappings and subsequent topics.

1. Access ASI admin settings.
2. Select the hyperlink associated with the setting that you want to modify.
   The datasheet associated with your selected configuration appears.
3. Make the necessary changes, and then select .
   Your configuration has been saved.

1. Access ASI admin settings.
2. Select Work Management Item Definitions.
3. In the Import Mapping column, select the WMI for which you want to enable copying.
4. Select the Is Copy Paste Allowed check box.
5. In the Fields to be ignored while copy paste box, enter a list of fields that must be ignored while copying. All the remaining fields will then be selected.
6. As needed, modify values in the remaining fields, and then select .
   You can now copy the WMI.

1. Navigate to Admin > Configuration Manager > Family Management.
2. Access the custom family.
3. Select Fields.
   A list of fields in the custom family appears.
4. Select the Status field, and then select Behaviour.
5. Add a new default behaviour.
6. Enter A in the left side constant field, and then select Save.
   The status field is added to any new records of the custom WMI family by default.
7. Select Rules and Policies.
8. Select Family Policy, and then select Save.
9. Add a before-update Policy to ensure that the status field is changed when the custom WMI record is updated.
   When a record of the custom WMI family changes, the updated status appears in the WMI tree.

1. Access ASI admin settings.
2. In the Work Management Item Definitions section, in the Name column, select the WMI Definition for which you want to configure the export settings.
3. Enter values in the following fields:
   • Lookup Fields for Data Loader and Export
   • Exclude Fields from Export
4. Select .
   The configuration for the Export ASI Package feature is saved.

1. Access ASI admin settings.
2. Select the Asset Strategy Implementation Preferences tab.
   The Asset Strategy Implementation Preferences workspace appears.
3. In the Query to Locate Implementation Package box, select Browse.
   The Select a query from the catalog window appears.
4. Select the appropriate query from the list.
   The query is highlighted.
5. Select Open.
   The Asset Strategy Implementation Preferences workspace reappears.
6. Select Save.
   Your preferences have been saved.

   Note: If you want to change your Paste Options, select either Yes or No from the Display Asset and Action Assignment Dialog... drop-down menu.

In the Asset Strategy Implementation Preferences workspace, you can customize the Import from SAP feature to utilize custom SAP Function Modules for Maintenance Plans, Maintenance Items, Task Lists, and Notifications.

1. Access ASI admin settings.
2. Select the Asset Strategy Implementation Preferences tab.

   The Asset Strategy Implementation Preferences workspace appears.

3. In the Import from SAP section, enter values for the custom RFC in the Maintenance Plan Detail Function Module, Maintenance Item Detail Function Module, Task List Detail Function Module, and Notification Function Detail Module boxes as needed.
   Note: Values should be entered in the following format: <Function Group> /<Function Module Name> (for example; MIAPM/GET_MAINT_ITEMS).
4. Select Custom SAP Table Configuration hyperlink to define the mappings between a custom SAP table and an APM family for each custom RFC.
5. In the RFC Name field, enter the custom RFC that needs to be called for Import.
6. In the Custom Family field, enter the custom APM family information. This will be the target family while importing from SAP.
7. In the Custom EAM Object field, enter the custom SAP table information. This will be the source table while Importing into APM.
8. In the Reference Mapping field, add the parent key and child keys as Json Key value parameters to identify relationships For instance, if you are linking custom family to Operation, you will need to have the Operation Key as the lookup field from SAP. The expected format is {parentField: childField, parentField: childField}. For example, {"MI_OPERTION_ID_C":"VORNR"} as VORNR is the operation number in SAP.

1. Access ASI admin settings.
2. Select Asset Strategy Implementation Preferences.
   The Asset Strategy Implementation Preferences workspace appears.
3. As needed, in the Export to SAP section, enter values for the custom RFC in the following fields:
   • Maintenance Plan Detail Function Module
   • Maintenance Item Detail Function Module
   • Task List Detail Function Module
   • Notification Function Module

   Enter values in the following format: <Function Group>/<Function Module Name> (for example, MIAPM/GET_MAINT_ITEMS)
4. To define the mappings between a custom SAP table and a APM family for each custom RFC:
   1. Select Custom SAP Table Configuration.
   2. Enter values in the following fields:

      Field	Description
      RFC Name	Enter the custom RFC that you want to export.
      Custom Family	Enter the custom APM family that you want to use as the target family while exporting to SAP.
      Custom EAM Object	Enter the custom SAP table information that you want to use as the target table when exporting to SAP.
      Reference Mapping	Add the parent key and child keys as JSON key-value parameters to identify the relationships. For example, if you want to link a custom family with Operation, you must use the Operation key as the lookup field from SAP. Use the following format: {"<parent field>";"<child field>", "<parent field>";"<child field>"} For example, to map Operation with the operation number VORNR in SAP, enter {"MI_OPERTION_ID_C":"VORNR"}

5. Select Save.

1. In the Maintenance Package UOM codes box, modify the value to specify the valid interval values for implemented actions associated with Asset Strategies.
   Only valid interval values of implemented actions are updated in the corresponding Maintenance Packages in SAP. The default value in this box is {"MONTHS":{"IntervalCode":"M","IntervalValues":[1,3,6]},"YEARS":{"IntervalCode":"Y","IntervalValues":[1]}}.
   Example: You can configure 2 months to be a valid interval value so that when you specify an interval of 2 months for an implemented action, the corresponding Maintenance Package in SAP is updated with the same value. To configure 2 months as a valid value, modify the value in this box as follows:

   {"MONTHS":{"IntervalCode":"M","IntervalValues":[1,2,3,6]},"YEARS":{"IntervalCode":"Y","IntervalValues":[1]}}

2. Select Save.

1. Access ASI admin settings.
2. Select Asset Strategy Implementation Preferences.
   The Asset Strategy Implementation Preferences workspace appears.
3. In the SAP Validation section, in the SAP Validation Parameter box, enter a value for the custom validation parameter (for example, I_TEST_RUN).
4. Select Save.

1. Access ASI Admin Settings.
2. Select the Asset Strategy Implementation Preferences tab.
   The Asset Strategy Implementation Preferences workspace appears.
3. Select Enable PRT check box.
4. In the PRT Report Builder Project Path box, enter the new rule path.
5. In the PRT Report Builder Class Name box, enter the class name.
6. Select Save.
   The settings to generate a customized PRT report are configured.

   For more information on how to customize a PRT report, refer to KBA 000036539.

1. Access ASI Admin Settings.
2. Select Field Lookup Configurations.
3. Select the hyperlink for each family field.
   The RFC Parameter Configuration datasheet appears.
4. As needed, modify values in the available fields, and then select .
   The Field Lookup parameters are configured.