SXMB_ADM — Integration Engine Administration
SXMB_ADM is the administration transaction of the ABAP integration engine. It is used to configure how a business system sends and receives XI messages, for example ABAP proxy messages, including which integration server or endpoint receives them. When proxies move from SAP PI/PO to SAP Integration Suite, this configuration points the system to the new endpoint.
Configures the ABAP integration engine, including the role of the system and the integration server used for proxy communication.
Published 31 Oct 2026· 463 words
What SXMB_ADM is for
ABAP proxies exchange messages using the XI protocol through the local integration engine. The engine's configuration defines the role of the system, the corresponding integration server and other runtime parameters. Without correct settings, outbound proxy messages fail or go to the old middleware, so SXMB_ADM is central in migrations and system copies.
When it is used
It is used when setting up proxy communication, after system copies or refreshes, and during PI/PO to Integration Suite migrations when the destination for proxy messages changes. Support teams check it when proxy messages error in SXMB_MONI with connection problems.
How it is used in practice
Open the integration engine configuration, note the current values before any change, check the role of the business system and the corresponding integration server destination, and adjust specific configuration parameters only according to the agreed design. Test with a single proxy message and monitor it in SXMB_MONI. Document changes, because they affect every proxy interface of the system.
Fields and objects that matter
- Role of the business system in the integration engine
- Corresponding integration server or HTTP destination
- Specific configuration parameters for runtime behaviour
- Monitoring and archiving settings for messages
- RFC or HTTP destinations in SM59 referenced by the configuration
How to prove it in the data
After a change, send one outbound proxy message and check in SXMB_MONI that it was delivered to the intended endpoint, and in the middleware that it arrived with the same message ID. A message still going to the old PI system shows the configuration or destination was not updated.
ECC vs S/4HANA
Available in S/4HANA and other ABAP systems using ABAP proxies. With SAP Integration Suite, the XI adapter allows proxies to keep working while only the endpoint configuration changes.
Common pitfalls and how they show up
One setting here affects every proxy interface of the system.
- Changing the target in production before all interfaces are migrated
- System copies keeping production endpoints, sending test messages to live partners
- Adjusting runtime parameters without understanding their effect on every interface
- Deleting the old PO destination too early, leaving no fallback during hypercare
- No documentation of the configuration, making cutover rollback hard
- Testing only one interface after a change instead of a representative set
Whose problem this is
Owned by integration and Basis teams, with strict change control during migrations and system copies. The post-copy checklist should include this configuration, because a refreshed test system pointing at production middleware is a real risk.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Learn this properly
Lessons and topics
Source: ERPClimb — https://erpclimb.com/sap-tcodes/sxmb-admERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.