Skip to content

solutions-for-errors-in-the-managed-system-setup-check-93ae080.md

Latest commit

 

History

History
1663 lines (1037 loc) · 31.1 KB

solutions-for-errors-in-the-managed-system-setup-check-93ae080.md

File metadata and controls

1663 lines (1037 loc) · 31.1 KB

Solutions for Errors in the Managed System Setup Check

Managed System Setup Check Report

To perform the Managed System Setup Check, run transaction /SDF/ALM_DIAGNOSTIC in client 000 in all the systems included in the transport track and working client that you want to connect to SAP Cloud ALM.

The following sections explain the checks and messages that can appear in the managed system during the Managed System Setup Check. This includes confirmation information and error messages.

General System Information Check

This shows in which system and client the check has been performed.

Message

Message Explanation

The check is running in &1/&2 for destination &3

Confirmation message. No action is needed.

Monitor ABAP Application Log and ABAP Job Log

We recommend monitoring the ABAP Application Log and ABAP Job Log. This helps you to detect communication issues.

  1. You've configured the push data provider for Operations and activated the use case task Integration Monitoring. For more information, see SAP NetWeaver Application Server for ABAP(7.40 or higher).

  2. Register all systems configured for Change and Deployment Management via the ST-PI setup and enable Change and Deployment Management and Exception Monitoring.

  3. Check if the system is registered in Landscape Management.

  4. Open the Integration & Exception Monitoring app.

  5. Select a scope by choosing your systems.

  6. Select Configuration.

    Note:

    Make sure that the configuration is active for your systems.

  7. Enter the individual system configuration.

  8. Set the ABAP Application Log and ABAP Job Log to active.

  9. Enter the filter configuration menu.

  10. For the ABAP Application Log, enter the following filters:

    • object: /SDF/CALM
    • subobject: BUILD_CDM

  11. For the ABAP Job Log, enter a Batch-User filter with the user you used for configuring the batch job.

  12. You can also specify the filters in more detail if needed.

  13. Ensure that the monitoring entry Active and overall system entry Data Collection switches are set ON.

For more general information about monitoring and creating alerts, see Monitoring Configuration.

Active Tasks Check

This check displays which tasks are active in which systems and when they last ran. You can also see whether a system has an export/import route or not.

Message

Message Explanation

Task "&1" is active in client &2 and last ran &3

Confirmation message. No action is needed.

System has an export route

Confirmation message. No action is needed.

System has no export route

Confirmation message. No action is needed.

Export Task is active in client &1

Confirmation message. No action is needed.

Export Task is inactive in client &1

If you want transports in this client to be managed by SAP Cloud ALM activate task Transports: Create & Export (client-specific).

System has an import route

Confirmation message. No action is needed.

System has no import route

Confirmation message. No action is needed.

Import Task is active in client &1 and valid for all clients

Confirmation message. No action is needed.

Import Task is inactive in client &1 and no imports will be processed

If you want imports in this system to be managed by SAP Cloud ALM activate the taskTransports: Import.

Timezone Check

This checks if your timezone settings are correct.

Message

Message Explanation

Timezone settings ok. Current time: &1

Confirmation message. No action is needed.

System &2: multiple system time zones found in different clients (&1)

Check your timezone settings. For more information, see SAP Note 481835.

System &2: system time zone for client &1 not specified (table TTZCU)

System &3: no definition for time zone &2 in client &1 (table TTZZ)

System &3: definition for time zone &2 in client &1 inactive (table TTZZ)

System &2: system time zone or UTC time not correct (client &1)

System &3: user time zone or UTC time incorrect (client &1, user &2)

System &1: UTC timer is not correct (difference = &2 s)

No timezone check could be performed due to RFC failures

No issue detected for time zone and UTC timer in any managed system

Confirmation message. No action is needed.

Analyze Application Log

The Analyze Application Log is an extended system log which shows you more details about use case tasks and jobs. For example, you can check if a job has already been scheduled.

To open the Analyze Application Log, run transaction SLG1 in the system where you activated the use case task you want to check. SLG1 is client independent.

In the Object field, enter /SDF/CALM. In the Subobject field, enter Build_CDM.

The following table shows you which External IDs you can use for filtering:

External ID

Task

Description

READ

Transports: Read

Read of all transport in system

READ LANDSCAPE

Transports: Read Landscape

Read transport landscape in domain controller

IMPORT

Transports: Import

Perform import

IMPORT FEEDBACK

Process import result

CLIENT DEPENDENT

Transports: Create & Export (client-specific)

Perform client dependent tasks

CREATE

Create transport request

RELEASE

Release transport request

EXPORT FEEDBACK

Process release result

TOC

Create transport of copies

TR CHECK

Transports: Check

Perform transport checks

RETRO

Transports: Retrofit

Perform retrofit

RETRO_CATE

Transports: Retrofit

Perform retrofit categorization

RETRO_AUTO

Transports: Retrofit

Perform automatic retrofit

Batch Job Check

The batch job check, checks if a job for the program /SDF/CALM_SCHEDULER is scheduled.

The /SDF/CALM_SCHEDULER program is the central scheduling mechanism for all active use cases. The frequency of the scheduling determines the overall interval between the use-case executions.

The batch job check, checks if a job for the program /SDF/CALM_CDM_DIAGNOSTICS is scheduled and did run today.

  • This program informs SAP Cloud ALM about the capabilities of the system according to the installed ST-PI service level and certain notes (For example: Transport creation, release, ToC, and so on).
  • It runs once after the use-case activation and then once daily. Check transaction /SDF/ALM_SETUP that at least one transport-related use-case is active.

Batch Job Check

Message

Message Explanation

Job &1 is scheduled. Next run: &2 &3

Confirmation message. No action is needed.

Job &1 isn't scheduled

Procedure: Check transaction /SDF/ALM_SETUP whether the background user is configured, and the system is registered.

If this isn't the case, select Register again.

Error in configuration: &1&2&3&4

No immediate solution is available. Search for similar issues with the SAP4Me help search or open a ticket at SAP For Me.

Job /SDF/CALM_CDM_DIAGNOSTICS did run today

Confirmation message. No action is needed.

Job /SDF/CALM_CDM_DIAGNOSTICS hasn't (yet) run today
  • Check that no obsolete jobs for this program exist in SM37 (for example, after suspending all jobs).
  • Check transaction /SDF/ALM_SETUP that at least one transport-related use-case is active.

For more information about the basic setup and use cases refer to the following documentation:

SAP S/4HANA Cloud Private Edition and On-Premise Systems.

Background Work Processes (BTC) Workers

Free batch processes are necessary to start use-case processing. If all worker processes are blocked by other tasks no information from Cloud ALM is transferred and no Cloud ALM tasks processed.

Background Work Processes (BTC) Workers

Error Message

Message Explanation

There are currently no free batch processes

Follow the instructions in 39412.

There's only one free batch process

Follow the instructions in 39412.

There are currently &1 free batch processes

Confirmation message. No action is needed.

Error reading batch process data: &1

No immediate solution is available. Search for similar issues with the SAP4Me help search or open a ticket at SAP For Me.

Certificate Check

For the connection to SAP Cloud ALM, the certificates must be installed on the system. See Setup S-Trust.

Certificate Check

Error Message

Message Explanation

Certificate exists: &1

Confirmation message. No action is needed.

Certificate missing: &1

Follow the instructions in Setup STRUST.

Certificate recommended: &1

Follow the instructions in Setup STRUST.

Connection Check

In case of connection issues check if you followed all the steps from the SAP S/4HANA Cloud Private Edition and On-Premise Systems guide.

Common connection problems that occur are for example HTTP Code 403:

  • Cloud API Key or Binding wasn't set up with the necessary scopes. For more information, see Token Scopes Check
  • Necessary certificates are missing. For more information, see Certificate Check.

Connection Check

Error Message

Message Explanation

Connection successful

Confirmation message. No action is needed.

Connection failed: &1

See common connection problems above the table.

Lock Check (SM12)

Some locks might prevent use-case processing. For example, a lock is still present even though use-case execution is paused.

For more information, see SAP Note 43614.

Lock Check (SM12)

Error Message

Message Explanation

No locks are blocking use-case execution

Confirmation message. No action is needed.

At least one SM12 lock found for /SDF/CALM_SCHED

For more information, see 43614.

At least one SM12 lock for /SDF/CALM_SCHED older than 10 minutes found

For more information, see 43614.

Error during lock retrieval: &1&2&3&4

No immediate solution is available. Search for similar issues with the SAP4Me help search or open a ticket at SAP For Me.

Note Implementation

Check if the latest version of the SAP Cloud ALM CDM master note 3425282 is implemented.

Note Implementation

Error Message

Message Explanation

Error during note download: &1&2&3&4

No immediate solution is available. Search for similar issues with the SAP4Me help search or open a ticket at SAP For Me.

The latest version of SAP Note 3322679 is implemented

Confirmation message. No action is needed.

An older note version is implemented: &1

It's recommended to update the master note and/or ST-PI regularly to receive new functions and bugfixes.

Error during note check: &1&2&3&4

No immediate solution is available. Search for similar issues with the SAP4Me help search or open a ticket at SAP For Me.

Token Scopes Check

The Cloud API Key or binding wasn't set up with the necessary scopes. If you're unsure about if you performed these steps correctly, create a new dedicated API instance according to the documentation you can find in Enabling SAP Cloud ALM API.

After you've performed the setup correctly, repeat the setup with the new API key.

Token Scopes Check

Error Message

Message Explanation

Token Connection failed: &1&2&3&4

No immediate solution is available. Search for similar issues with the SAP4Me help search or open a ticket at SAP For Me.

Token scope imp-cdm-feature-display-ui missing

Check if you followed the steps in Enabling SAP Cloud ALM API.

Token scope imp-cdm-feature-manage-ui missing

Check if you followed the steps in Enabling SAP Cloud ALM API.

Token scopes valid

Confirmation message. No action is needed.

Solution Tools Plug-In (ST-PI)

We recommend to regularly install a recent version of the ST-PI plugin instead of various master page notes. See also SAP Note 539977. Also, see the following guide Technical Prerequisites.

Solution Tools Plug-In (ST-PI)

Error Message

Message Explanation

A recent version of ST-PI is implemented: &1

Confirmation message. No action is needed.

An older version of ST-PI is implemented: &1

Upgrade your ST-PI version to a more recent version.

The installed version of ST-PI is outdated: &1

It's highly recommended to update the ST-PI version.

Error during component check: &1&2&3&4

No immediate solution is available. Search for similar issues with the SAP4Me help search or open a ticket at SAP For Me.

Web Dynpro Check

This checks whether the new S_START check is active for the CTS_ORGANIZER Web Dynpro app.

To display transports S_TRANSPRT display authorization must be assigned to the users.

Web Dynpro Check

Error Message

Message Explanation

S_START check is active for CTS_ORGANIZER

Information message. For background information, see SAP Note 1413011.

S_START authorization is assigned to current user

Information message. For background information, see SAP Note 1413011 .

S_START authorization missing for CTS_ORGANIZER for current user

Ensure that every user who wants to navigate from CALM to a transport request has the necessary authorization in the respective client of the managed system. Usually, this is not necessary for client 000, as it is not recommended to create transports in this client.

For more information, see SAP Note 1413011.

S_START check is inactive for CTS_ORGANIZER

Information message. For background information, see SAP Note 1413011.

S_TRANSPRT display authorization is assigned to current user

Confirmation message. No action is needed.

S_TRANSPRT display authorization missing for current user

Follow the information in Authorizations for Transport Organizer Web UI (CTS_ORGANIZER) to resolve the issue.

Change and Transport System (CTS) Check

SAP Cloud ALM checks the Change and Transport System for basic functionality.

Note:

Make sure that you've setup CTC=1. For more information, see Configuring your Transport Management System (TMS) on the Managed Systems.

For more information, see Transport Management System (BC-CTS-TMS)

Change and Transport System (CTS) System Check

Error Message

Message Explanation

&1: CTC is enabled

Confirmation message. No action is needed.

&1: CTC is disabled

It's recommended to enable CTC. Follow the instructions in Extended Transport Control.

&1: &2&3

No immediate solution is available. Search for similar issues with the SAP4Me help search or open a ticket at SAP For Me.

&1: System Profile couldn't be read

No immediate solution is available. Search for similar issues with the SAP4Me help search or open a ticket at SAP For Me.

RFC configuration in view &1 has been validated successfully

Confirmation message. All configured RFC work fine. No action is needed.

RFC configuration is missing in view &1 for transport checks

Configured RFC isn't working properly, see Setting up Transport Checks for Import Checks to solve the error.

The configured RFC &1 in the table view &2 has no user assigned

The configured RFC &1 in the table view &2 doesn't work

The configured RFC &1 in the table view &2 doesn't exist

Not authorized to logon with configured RFC &1

Trusted RFC &1 isn't allowed

Retrofit Configuration Checks

The following table shows error messages that can occur during the retrofit configuration and how to resolve them:

Error Message

Message Explanation

Production system information isn't configured for retrofit in table /SDF/CDM_PARAM

See 6. Maintain Production Systems for Retrofit in Setting up Retrofit on how to configure the production systems for retrofit.

Retrofit production system configuration in table /SDF/CDM_PARAMhas been validated

Confirmation message. No action is needed.

Invalid production system is configured for Retrofit in table /SDF/CDM_PARAM

See 6. Maintain Production Systems for Retrofit in Setting up Retrofit on how to configure the production systems for retrofit.

RFC configuration is missing in view /SDF/CMO_TARGET for retrofit

See 3. Create RFC Destination and 4. Maintain RFC Destination in Customizing Table for Retrofit in Setting up Retrofit on how to configure the RFC destination.

RFC destination is missing in view /SDF/CMO_TARGET for target &1

See 3. Create RFC Destination and 4. Maintain RFC Destination in Customizing Table for Retrofit in Setting up Retrofit on how to configure the RFC destination.

The configured RFC &1 in the table view /SDF/CMO_TARGET has no user assigned.

See 2. Create RFC User for Retrofit and 3. Create RFC Destination in Setting up Retrofit on how to configure the RFC destination.

Trusted RFC &1 isn't allowed

See 3. Create RFC Destination in Setting up Retrofit on how to configure the RFC destination.

On the tab Logon and Security, navigate to Logon Procedure. In the field Trust Relationship, set No for Trust Relationship of RFC &1.

The configured RFC &1 in the table view /SDF/CMO_TARGET doesn’t exist.

See 3. Create RFC Destination and 4. Maintain RFC Destination in Customizing Table for Retrofit in Setting up Retrofit on how to configure the RFC destination.

Other errors returned from RFC_READ_R3_DESTINATION that we can't predict

No immediate solution is available. Search for similar issues with the SAP4Me help search or open a ticket at SAP For Me

with component SV-CLM-IMP-FTR.

  • Not authorized to call TMW_ADJUST_ORIGINAL_SYSTEM with configured RFC &1

  • Not authorized to call TMW_COPY_TO_TARGET_REQUEST with configured RFC &1

  • Not authorized to call /SDF/CALM_CDM_RETRO_DELTOC with configured RFC &1

  • Not authorized to call /SDF/CALM_CDM_CSOL_FOR_RETRO with configured RFC &1

  • Not authorized to call /SDF/CALM_CDM_RETRO_GETLAYER with configured RFC &1

  • Not authorized to call SDF/CALM_CDM_RETRO_SETTRATTR with configured RFC &1

  • Not authorized to call TMW_IMPORT_REQUESTS with configured RFC &1

The authorization for retrofit is missing, or function code for retrofit is not ready.

Check the Prerequisites and 1. Upload PFCG Roles on Your Development System and Client of Your Implementation Track in Setting up Retrofit.

Retrofit RFC configuration in view &1 has been validated successfully.

Confirmation message. No action is needed.

Prerequisites Check for Export Checks

The system performs a check of the prerequisites of the activated use case tasks and provides information in case of errors.

Error Message

Message Explanation

SAP_BASIS Version is lower than the minimum version ST740 SP13.

SAP Basis version of the system does not meet the required version. For more information, Prerequisites for Export Checks.

SAP_BASIS Version check failed.

No immediate solution is available. Please search for similar issues with the SAP4Me help search or open a ticket at SAP For Me with component SV-CLM-IMP-FTR.

ATC SAP Note 3569187 is not implemented in this system

SAP Note for export check is not implemented in the system. See Prerequisites for Export Checks for the required SAP Notes.

Read ATC check flag failed. ATC is switched off.

ATC functionality does not exist in the system. For more information, Quality Checking with the ABAP Test Cockpit (ATC).

SAP_BASIS version successfully checked.

Confirmation message. No action needed.