Absolutely, you can combine sapshcut.exe (for login) with win32com (to control the session) to solve your problem. The key difference from the saplogon.exe approach is that you don't need to open a new connection—instead, you'll attach to the existing session that sapshcut.exe starts.

Step-by-Step Solution Code #

Here's a merged script that handles login via sapshcut and then grabs the active SAP session for automation:

import win32com.client
import sys
import subprocess
import time

def sap_login_and_get_session():
    session = None
    try:
        # Step 1: Use sapshcut to log into your PROD system
        sapshcut_path = r"C:\Program Files (x86)\SAP\FrontEnd\SAPgui\sapshcut.exe"
        # Adjust parameters to match your system/client/user/password
        subprocess.call([
            sapshcut_path,
            '-system=PRD',
            '-client=010',
            '-user=XXXXXX',
            '-pw=XXXXXX'
        ])
        
        # Wait for the SAP session to fully load (adjust sleep time if needed)
        time.sleep(15)
        
        # Step 2: Attach to the existing SAP GUI session
        SapGuiAuto = win32com.client.GetObject('SAPGUI')
        if not isinstance(SapGuiAuto, win32com.client.CDispatch):
            print("Could not get SAPGUI object")
            return None
        
        application = SapGuiAuto.GetScriptingEngine
        if not isinstance(application, win32com.client.CDispatch):
            print("Could not get Scripting Engine")
            return None
        
        # Find the connection corresponding to your system (PRD)
        connection = None
        for conn in application.Connections:
            # Check if the connection's description matches your system
            if conn.Description == "PRD":
                connection = conn
                break
        
        if not connection:
            print("Could not find PRD connection")
            return None
        
        # Get the first session of the connection
        session = connection.Children(0)
        if not isinstance(session, win32com.client.CDispatch):
            print("Could not get SAP session")
            return None
        
        # Example: Verify the session is working by navigating to a transaction
        session.findById("wnd[0]/tbar[0]/okcd").text = "SE16N"
        session.findById("wnd[0]").sendVKey(0)
        
        print("Successfully connected to SAP session!")
        return session
        
    except Exception as e:
        print(f"Error occurred: {str(e)}")
        return None
    finally:
        # Clean up references (optional but good practice)
        if session:
            # Don't close the session here unless you want to log out
            pass
        connection = None
        application = None
        SapGuiAuto = None

# Run the function
sap_session = sap_login_and_get_session()

Key Details to Note #

• Why This Works

  • sapshcut.exe handles the login process via your Sap Logon Pad setup, which is exactly what you need since saplogon.exe isn't available.
  • Instead of using application.OpenConnection() (which is for saplogon.exe), we iterate through application.Connections to find the already-running session started by sapshcut.

• SAP GUI Scripting Must Be Enabled

  • If you get errors accessing the Scripting Engine, you need to enable scripting in SAP GUI:
    • Open SAP Logon Pad → Go to Options → Accessibility and Scripting → Scripting
    • Check "Enable scripting" and "Notify when a script attaches to SAP GUI" (optional but helpful for debugging)
    • Restart SAP GUI after changing these settings.

• Adjust Sleep Time

  • The time.sleep(15) gives SAP enough time to load the session. If your system is slower, increase this value (e.g., 20 or 30 seconds).

• Identify the Correct Connection

  • The conn.Description check uses the system name you specified in -system=PRD. If your Sap Logon Pad uses a different display name for the system, replace "PRD" with that exact name.

内容的提问来源于stack exchange，提问作者Marek Ševela