Troubleshooting
Problem
This document shows you a list of Must Gather materials needed to assist you and Technical Support in finding a solution to your SAP R/3 problems.
Resolving The Problem
The following list of information is needed to assist you and Technical Support in finding a solution to your SAP R/3 problems. This information is applicable for both BAPI and ALE adapters.
- Enable and gather the BAPI or ALE adapter trace by adding the -TV+ on the command or rule that is encountering a problem.
- Gathering component specific info:
RFC Trace:
For Inbound issues: This file is activated when enabling the BAPI or ALE adapter trace through the -TV+ switch. By default this file is created under the map folder; to change the location set the environment variable to RFC_TRACE_DIR=folder.
For Outbound issues: Run sm59 in SAP GUI to enable the trace and it's destination directory.
For Importer issues: Gather the .ido file - Enable and gather the map audit log and trace on the map that is encountering the problem. This can be activated through the Map Settings.
- Gather Event Server or Launcher log from the logs directory if Event Server or Launcher is involved.
- Gather your ITX Version.
- Confirm your SAP Pack version including any previously supplied patches.
- Gather your SAP Server version by going into the SAP GUI, and selecting System, Status, Component Version, and taking a screenshot of the Component Information.
- Gather your SAP Server kernel information by going into the SAP GUI, and selecting the bottom left icon to obtain a screenshot of the SAP kernel information.
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSPVY6A","label":"IBM Sterling Transformation Extender Pack for SAP Applications"},"ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
03 May 2025
UID
swg21285530