• /
  • EnglishEspañolFrançais日本語한국어Português
  • ログイン今すぐ開始

New Relic Note 1231

October 18, 2025

Transport details

SAP transport SD1K901231 delivered in two files:

  • K901231.SD1 (co-file)
  • R901231.SD1 (data)

Enhancements

NR_CALM_LANDSCAPE event

The NR_CALM_LANDSCAPE event is enhanced to include the client endpoints (if any) configured in the system. This does not apply for SAP PaaS/SaaS based services. Example: If your SAP instance has 3 clients - 100, 200, 300... then a separate LMSID would be generated for each one of them.

Required action: Change the monitoring component for this DP from CALM to LANDSCAPE in the DP Registry transaction.

NR.CALM.HM event

The NR.CALM.HM event is enhanced to send the relevant metrics based on the org_name to respective NR accounts of the org unit. This enhancement will be applicable only for serviceType = SAP_CPI and for metrics (CPI.JMS.Queue.Active, CPI.JMS.Queue.Status, CPI.JMS.Queue.Message.Number)

New attribute - ORG_NAME: org_name used as filter for metric names. Add this field to the template table (/NEWR/DP_SELOPTIN) using SM30.

Screenshot displaying data provider name

NR_CALM_IS_MPL data provider

The NR_CALM_IS_MPL data provider now requires a new parameter_id SERVICE_TYPE to differentiate between the IS CPI and MACO instances. Add this field to the template table (/NEWR/DP_SELOPTIN) using SM30.

Screenshot displaying NR_CALM_IS_MPL

Program updates

The /NEWR/SYS_GENERATE_DELIVERY program is enhanced to exclude the monitoring component CALM related data provider from generation of Call ID configuration. Instead use the program /NEWR/GEN_DP_CALLID for monitoring component CALM.

The /NEWR/GEN_DP_CALLID program is enhanced to update the new attributes added to the Registry Configuration table.

Fixes

Issue: The NR_CALM_LANDSCAPE data provider does not transmit all systems configured in the Cloud ALM tenant.

Resolution:

  • /NEWR/ABAP_COLLECTION_MANAGERN (program) - When data providers are submitted for parallel processing and if there is a resource constraint of WP, then that particular DP is skipped for data collection. Now we have enabled the retry mechanism.

  • /NEWR/REGISTRY (Tcode) - When we generate the Call ID for a new monitored system, the previously suspended data provider is re-activated again.

Copyright © 2026 New Relic株式会社。

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.