SAP Knowledge Base Article - Preview

3358202 - Export tenant and Target fields are empty when you create a Transport from a Feature for on-Premise Changes

Symptom

  • Enabled Change and Deployment Management scenario in Cloud ALM
  • Want to create a Transport request with SAP Cloud ALM Feature to an ABAP system but the Export tenant and Target fields are empty, so no Transport can be created for On-premise changes
  • In the managed system:client where the use case Feature Deployment: Manage Transports per Client is activated, see errors in the job /SDF/CALM_CDM_TR_PROC_CL_DEP-client:

Step 001 started (program /SDF/CALM_CDM_TSK_PROCESS, variant &0000000006459, user ID XXX)
Program /SDF/CALM_CDM_TSK_PROCESS started with destination YYY
Call post request to URL: 'https://<domain>.alm.cloud.sap/api/featuresService/v1/ odata/v4/FeatureSer
Post request returned with status 403   --> correct value would be Post request returned with status 200   (403 Forbidden, 200 OK, 204 No Content) 
Post request failed with status 403        --> correct value would be Post request returned with status 200

  • Run report sa38 > /SDF/CALM_CDM_DIAGNOSTICS and see:

'https://<domain>.alm.cloud.sap/api/featuresService/v1/ odata/v4/FeatureService/handleABAPSystemDiagnostic
Post request returned with status 403    -> correct value would be Post request returned with status 204
Post request failed with status 403


Read more...

Environment

SAP Cloud ALM 1.0

Product

SAP Cloud ALM 1.0

Keywords

CDM, Deployment, export tenant, CALM, target, 403 , KBA , SV-CLM-IMP-FTR , Feature , SV-CLM-INF-CON , Connectivity of managed services/systems to SAP Cloud ALM , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.