SAP Order Management foundation

Available Monitoring Content

The following monitoring content is available for SAP Order Management foundation

CategoryTypeDescription
SAP Order Management foundation MessagesMessagesMonitors messages for incoming orders and order dispatches in SAP Order Management foundation

Setup Steps in SAP Order Management foundation

Enable Monitoring Data PUSH to SAP Cloud ALM

Perform the following steps to enable SAP Order Management foundation to send monitoring data to SAP Cloud ALM.

Prerequisites:

  • You need access to SAP BTC cockpit for the SAP Order Management foundation sub-account
  • You need to obtain the service key for your SAP Order Management foundation instance
  • You need to obtain the SAP Cloud ALM Service Key to connect to the SAP Cloud ALM system
    • Endpoint: The host part of the parameter "Api", e.g. eu10.alm.cloud.sap
    • OAuth URL: Service Key parameter "url" + /oauth/token, e.g. calm-tenant.authentication.eu10.hana.ondemand.com/oauth/token
    • Client ID: Service key parameter "clientid"
    • Client secret: Service key parameter "clientsecret"

PUSH Monitoring Registration

Please follow the documentation provided here to perform the PUSH monitoring registration.

After performing the registration the SAP Order Management foundation cloud service will appear in the landscape management of SAP Cloud ALM with the ID CO_<environment>_<tenant ID>.

The registration will activate the PUSH data collection and automatically send monitoring data to SAP Cloud ALM.

PUSH Monitoring Deregistration

To stop the monitoring data collection, please follow the 'Offboarding' section here

Setup Steps in SAP Cloud ALM

Activate Monitoring (Standard)

For managed services using PUSH data collection the standard monitoring content is automatically activated during the setup of the PUSH monitoring in the managed service. No further setup steps are necessary. You can check the successful activation in the Integration & Exception Monitoring application.

  1. Open the Integration & Exception Monitoring application from the launchpad
  2. Open the scope selection via the target icon in the upper right corner
  3. Select your cloud service in the scope
  4. Click the rack-wheel icon in the upper right corner to access the configuration
  5. Expand the Configuration panel
  6. The activation status for your SAP Order Management foundation service should already be set to ON

Adjust Monitoring and Alerting (Expert)

You can change which parts of the standard content are activated for each cloud service, activate and deactivate alerts or create own alerts with specific filters. 

  1. In the configuration panel, click on the name of the cloud service
  2. The "Configuration of Services" screen opens
  3. In the "Configuration for Services" screen, click the > button at the end of the line for the cloud service you want to change

Adjust Monitoring Categories

  1. Use the toggle button in the column Active to turn a monitoring category ON or OFF

Adjust Alerting

  1. Use the toggle button in the column Active to turn a standard alert ON or OFF
  2. Press the > button at the end of the line to access the detail setup for an existing alert or use the + button to create a new alert
  3. Adjust the display name if desired
  4. Expand the Filter Configuration tray
  5. Enter a filter name
  6. Select the filter category
  7. Maintain the available filter fields (see details below)

Available Alerts for SAP Order Management foundation

  • Erroneous SAP Central Order Message Detected(Single): Creates an alert for each failed message in the category SAP Order Management foundation Messages
  • Erroneous SAP Central Order Messages Detected(Grouped): Creates an alert if one or more failed messages in the category SAP Order Management foundation Messages were detected since the last data collection

Available Filter Fields for SAP Order Management foundation

The following filter fields are available for SAP Order Management foundation messages.

SAP Order Management foundation Messages

  • Component: Component name, e.g. Order (See Application Data)
  • Direction: INBOUND or OUTBOUND
  • Status: Message status (See Header Data)
  • Status Group: Successful, Warning, Error, In Process, Canceled, Others (See Header Data)
  • Status Text: Message status text (See Header Data)
  • Message Older Than N Minutes: Only consider messages older than X minutes