During the recent Oracle → HANA system conversion to S/4HANA 2023, we encountered an error in the Execution Phase where SUM stopped with an error at the step MAIN_NEWBAS/XPRAS_AIMMRG.

Overview

During the SUM execution, the process stopped in MAIN_NEWBAS/XPRAS_AIMMRG due to BW-related inconsistencies. The phase could not continue because certain BW InfoObjects were not fully activated before downtime.

Analysis

• While reviewing the error logs (XPRASUPG_NEW.ELG and related BW activation logs), we observed multiple failures related to InfoObject activation.
• The XPRAS engine failed to merge certain BW objects because the BW content was not in an active state before SUM was started.
• We validated client settings, checked multiple profiles, reviewed shadow logs, and compared BW content activation status before correlating this with the root cause.
• Only after detailed log review and cross-checking, it became clear that the system required specific BW preparation activities prior to downtime.

How to Identify

These indicators helped confirm the issue early:

1. XPRAS error in XPRASUPG_NEW.ELG with BW InfoObject activation entries.
2. Multiple failed entries referring to missing or inactive InfoObjects.
3. BW task list not executed before downtime (SAP_BW_SETUP_INITIAL_S4HANA).
4. Running STC01 or RSDG_IOBJ_ACTIVATE manually showed several inactive objects.
5. SUM repeating the same activation attempts and stopping again.

This combination confirmed that BW content activation was incomplete prior to the conversion.

Resolution

After confirming the root cause, we performed the below steps to fix the issue:

1. Implemented the required corrections in Client 000 using a non-DDIC user with SAP_ALL.
2. Activated the missing BW InfoObjects as per SAP Note 3315495.
3. Ensured the system was locked again and resumed the SUM execution.
4. SUM continued successfully without further XPRAS errors.

Workaround (for early detection )

To prevent the issue in the next conversion cycles (QA/DR/Production):

• Implement SAP Notes 3305016 and 3316148 before executing SUM.
  • Before downtime, run task list:
  STC01 → SAP_BW_SETUP_INITIAL_S4HANA
• Optionally run:
  Program RSDG_IOBJ_ACTIVATE to ensure all InfoObjects are active.
• Validate BW readiness in Sandbox during rehearsal runs.
  
  

These actions ensure the BW layer is fully consistent before SUM execution begins.

Regards,
Shubham Mishra

Hi Folks,

Greetings! I hope you are all doing well.

During a recent System Refresh activity, I encountered an issue where the Transport Route configuration could not be edited in the Quality system after restoring a backup from the Production system. Since this issue can occur frequently during refresh cycles, I am sharing the root cause, analysis, and step-by-step resolution.

Issue Summary: -

After performing a backup restore from Production to Quality, we executed the standard post-refresh activities—one of which includes clearing the existing TMS configuration in the target (Quality) system.

However, once the system came up and I launched STMS, the Edit / Change icon was disabled, preventing me from defining or modifying the transport routes.

Because the Quality system was refreshed from Production, the original routes and controller information were overwritten or removed—leading to a mismatch between the local TMS configuration and the domain controller.

Root Cause:-

During the system refresh:

• Transport Management System (TMS) data from Production overwrote the Quality system’s configuration.
• As part of cleanup, TMS routes were deleted or became inconsistent.
• The system lost its connection to the Domain Controller, causing the edit icon in STMS Transport Routes to become unavailable.

Essentially, the Quality system was no longer recognized as part of the transport domain.

Technical Explanation: -

After the refresh:

• The refreshed system contains production TMSADM keys, not matching the domain controller.
• Therefore, the system cannot authenticate with the domain controller.
• As a result, STMS → Transport Routes goes into read-only mode.

To synchronize the system again, we must update the local TMS config with the domain controller.

Solution – Restore TMS Route Using “Adjust with Controller: -

Perform the steps in the Quality system:

Step 1: Log in with DDIC user in client 000

This is mandatory because TMS configuration changes can only be done in:

• Client 000
• With DDIC or TMSADM authorized users

Step 2: Execute Transaction STMS

The system will try to connect to the domain controller.

STMS T-code

Step 3: Navigate to Transport Routes

Step 4: Adjust Configuration with Domain Controller

Go to: Configuration>Adjust with controller

You will notice the Edit icon is disabled.

Then click on configuration and get option is adjust with controller just see below snap.

Click Yes when prompted.

This action forces the Quality system to:

• Re-import TMS configuration from the Domain Controller
• Regenerate TMSADM RFC connection
• Restore the correct system role (Dev → QA → Prod)
• Load the existing route definitions

Step 5: Save the Transport Route

• After synchronization, the correct routes appear automatically.
• Click Save to activate the configuration.

Additional Technical Checks (Optional but Recommended)

1. Verify RFC connection of TMSADM

         SM59 → ABAP Connections → TMSADM_<SID>_XXX

         Status should be green.

1. Check Domain Controller system

         In Domain Controller (usually DEV system):
         STMS → Overview → Systems

          Ensure the refreshed system is visible and status is Active.

1. Check consistency

       Run:

       STMS → System Overview → Extras → Verify Configuration

Conclusion

After a system refresh, you may find the Edit option disabled in STMS due to mismatched TMS configuration. Using “Adjust with Controller” is the correct approach to synchronize the system with the transport domain controller and restore the predefined routes.

This process ensures that:

• Quality system aligns with the domain controller
• Routes are restored without manual reconstruction
• TMS remains consistent and operational

Thanks for Reading!

Please feel free to share your thoughts, improvements, or any similar experiences you’ve encountered during system refreshes.

Regards,

Nishant Garg

stop chasing digital hype – unlock real enterprise value by transforming tedious tasks into strategic advantages with AI

Are you looking to accelerate your development and simplify the maintenance of your SAP solutions?

Do you want to learn how to extend your SAP environments with minimal impact and maximum benefit?

These were the questions that our webinar participants had and that were answered throughout this clean core session. 

Hi Folks,

I would like to share a knowledge base article regarding the issues while performing Classical Migration using Export/Import method and SWPM tool.

Scenario:

We have an ABAP system for which we have taken export using SWPM on source server and here we are doing an SAP system installation while importing the exported data using SWPM tool (Installation + Migration), it throws below error while import.

Assertion failed: The installer is started with enabled database environment variables, which is not supported

Environment: Windows server 2019

Cause:

This issue occurred because there was already a System on target host with the same SID which was not properly uninstalled and cleaned up, so there were few Sybase database environment variables remained in the target host Registry Editor(regedit) in windows server which was not properly cleaned up during uninstallation.

Solution:

There are two ways in which this issue can be resolved.

1. The OS level user from which you are running SWPM, if it contains that environment variables and regedit (Registry) entries of old system SID, running SWPM with another user having same privileges fixes the issue.
2. Remove the environment variables and entries of Old SID from regedit and restart SWPM and try again.

Additional Information:

You might come across a situation where your target system is corrupted, or system failure happens and you may loss the important encrypted data which is copied from source.  

While importing the data, SWPM provides you key id and key value which you need to take a note of and keep it in a safer place.

The secure storage will be encrypted with the following key:

Make a backup of above Key ID and 58-character Key Value and keep it in a secure place for disaster recovery.

When you are in the process of system installation and want to use this system as source for a system copy or system rename, you must provide this backup to restore access to the encrypted data in the copied system.

Thanks & Regards,

Tanmay Gupta

SAP

Onboarding to SAP Build Work Zone, advanced edition involves several configuration steps across SAP BTP, Identity Authentication (IAS), and Identity Provisioning (IPS). This blog provides an end-to-end, practical walkthrough to help administrators set up SAP Build Work Zone for a BTP subaccount from scratch.

You will learn how to prepare your Identity Authentication tenant, create and assign the required Work Zone groups, run the SAP BTP booster, complete the post-booster configuration, and correctly connect IAS and IPS using the metadata and system parameters provided in the Site Manager. By following these steps, you will have a fully configured SAP Build Work Zone environment ready to authenticate users, provision groups, and launch the Work Zone site successfully.

Thanks to everyone who joined my session at SAP TechEd Sydney on how to efficiently operate SAP BTP applications.
We explored what good operations look like on BTP. From monitoring and alerting, to automation, cost optimisation, and DevOps best practices.

If you’d like to dive deeper into some of the topics discussed, here are a few great follow-up reads:

SAP Cloud Logging Service https://help.sap.com/docs/cloud-logging/cloud-logging/what-is-sap-cloud-logging?locale=en-AU

Cloud ALM Overview https://support.sap.com/en/alm/sap-cloud-alm.html

Introducing SAP Cloud ALM https://learning.sap.com/courses/introducing-sap-cloud-alm

OpenTelemetry https://support.sap.com/en/alm/sap-cloud-alm/operations/expert-portal/data-collection-infrastructure.html?anchorId=section_873338493

Custom Apps Integration https://github.com/SAP-samples/alm-demo-session

SAP BTP Terraform Provider https://registry.terraform.io/providers/SAP/btp/latest/docs

Getting started with Terraform provider for BTP https://learning.sap.com/courses/getting-started-with-terraform-on-sap-btp

DORA Metrics https://dora.dev/guides/dora-metrics-four-keys/

Application AutoScaler https://help.sap.com/docs/application-autoscaler/application-autoscaler/what-is-application-autoscaler?locale=en-AU

It was great connecting with so many of you. See you at the next TechEd or in the BTP community discussions!

Struggling with errors in SAP Cloud Integration (CPI) scenarios? Don’t waste time guessing the right component, get it right the first time. Our quick guide and video KBA (3663880) show you exactly which support component to choose for SuccessFactors integrations, from SFTP to OData and beyond. Bookmark this resource and resolve issues faster than ever!

If you’re an SAP partner, you’ve probably heard “AI agents” mentioned in every second customer conversation lately.  The thing is… most teams still aren’t sure how to use them in real projects.

That’s exactly what we’ll unpack in our upcoming webinar, “Increase business outcomes by unleashing the power of AI agents.”

We’ll start by demystifying SAP’s agentic landscape—what agents are, how they think and act, and when they’re the right tool.  Then we’ll roll up our sleeves and show how you can use Joule Studio’s low-code / no-code agent builder to design content-based agents that plug into SAP BTP, SAP Build, and your existing processes.

My favorite part? A real customer-style scenario: an AI-powered technical advisory/support system for professional services that quietly accelerates delivery without sacrificing quality.

If you know the basics of cloud-native, AI, and SAP BTP, you’re ready.  Register now and let’s turn the hype into outcomes your customers will feel.  https://partneredge.sap.com/en/library/education/psd/2025/jun/e_oe_te_w_PSD_WEB_00010558.html

#SAP #SAPBTP #SAPPartnerEcosystem #GenerativeAI #JouleStudio #SAPBuild #ProcessAutomation