Configuring Notification Catalog Types

Use parameters to configure the notification catalog types.

Context

Code groups that belong together in terms of content are grouped in catalogs. These catalogs are identified by the catalog type (a number or a letter). For example, in this way, you combine:

  • All code groups for particular problems for a catalog type

  • All code for causes for another catalog type and

  • All code groups for activities for a further catalog type

Use the CATALOGTYPE parameter group and the following parameters within the group to configure your catalog types for notifications in SAP Service and Asset Manager:

  • CatTypeActivities: Default is A

  • CatTypeCauses: Default is 5

  • CatTypeDefects: Default is C

  • CatTypeObjectParts: Default is B

  • CatTypeTasks: Default is 2

  • CatalogProfileOrder: Default is Equipment, Functional Location, Notification Type

The CATALOGTYPE parameters correspond to the rules found in the OData mobile data object SAM2210_CATALOG_CODES. You can add a new data filter rule to your customer namespace, or change the existing parameter-rule association to a new parameter-rule association.

Procedure

  1. Using the ConfigPanel, navigate to Start of the navigation pathMobile Application Configuration Next navigation step Parameters tabEnd of the navigation path. In the left column, Defined Mobile Applications, select your application.

    The Parameter List populates with a list of all parameters available for the application.

  2. The CatType[xxx] parameters are found in the CATALOGTYPE group. You can scroll down to find the parameter, or perform a search using the Search box. Highlight the parameter you want to configure and click the Change button.

  3. Make your desired parameter association changes, or change the value of a parameter to Z, a custom activity catalog type.
  4. Check the <Active> flag to ensure that the parameter is used by the mobile application. If desired, and if not already checked, check the <No Runtime Change> box to ensure that the value of the parameter is not overridden at runtime through synchronization processing.
  5. Save your changes.
  6. If you are creating a custom activity value type, navigate to Start of the navigation pathOData Mobile Data Object Configuration Next navigation step Data Filter Tab Next navigation step SAM2210_CATALOG_CODES Next navigation step Operation - READ Next navigation step Standard Filter Next navigation step CATALOG_TYPEEnd of the navigation path.
  7. Click the Change button. Add the new value. For information on working with rules, see Working with oData MDO Filter Rules.
  8. Save your changes.