SAP PI Tcodes ‘post list the main important Transaction Codes in SAP Process Integration.
It includes specific tcodes for SAP PI and some usefull cross-tcodes like for Queue and IDoc.
Read also SAP PI Tables (Process Integration Tables) – SAP XI tables
Table of Contents
Let’s start by listing the General SAP Process Integration ( PI, XI is the old name ) Transaction codes.
The Most important SAP PI (Process Integration or XI) Transaction Code are
Tcode | SAP PI Tcodes : General |
---|---|
SXMB_IFR | Start Integration Builder |
SXI_CACHE | XI Runtime (from IB) cache |
SXI_SUPPORT | Test all the Repository and Directory Objects |
SXDA_TOOLS | Post files to AL11 folders |
In order to Monitor the SAP Process Integration Message and system, consider the following SAP PI Monitoring Transaction Codes:
Tocde | SAP PI Monitoring Tcodes |
---|---|
SMICM | ICM Monitor |
SXMB_MONI | Integration Engine – Monitoring |
SXI_MONITOR | XI: Message Monitoring |
SXMB_MONI_BPE | Process Engine – Monitoring |
SMGW | Gateway Monitor |
ST06 | Operating System Monitor. cpu memory filesystem machine status |
SM37 | Job Monitoring |
ST03 | workload. |
SM21 | System logs |
SXMS_SAMON | Monitor for Sync/Async Communication messages |
SMMS | Message Server Monitor |
Message Packaging can be managed by the following SAP PI Tcodes :
PI Tcodes | Message Packaging Tcoes in SAP PI |
---|---|
SXMS_BCM | define Configuration types |
SXMS_BCONF | Global Package Configuration |
XMSPKSTATCNF | Package Statistics Configuration |
XMSPKSTATMON | Package Statistics Monitoring |
When it comes to SAP XI Administation, you can use the following SAP PI Administration Tcodes:
Tcode | SAP XI Tcodes for Administration |
---|---|
SXMB_ADM | Integration Engine – Administration |
SXMS_MONI_DB | Persistence Layer Analysis |
SXMB_ADMIN | Integration Engine Administration and Monitoring & Integration Engine parameters |
SWELS | BPM trace |
SXMS_MONI_JOB | Job Overview |
AL08 | list logged in users |
AL11 | SAP Direcories |
PFCG | Roles |
SCC4 | Client Administration |
SU01 | User Maintenance |
SU10 | User Maintenance – Mass Changes |
AL08 | Show logged on users |
To manage Alerts in SAP PI, you can use one of the following SAP PI Alerts Tcodes:
Alerts Tcodes in PI | Description |
---|---|
ALRTCATDEF | Alerts Configuration |
ALRTDISP | Display of Alerts Created |
ALRTINBOX | BSP alert inbox |
ALRTPROC | Process Alerts |
The Transaction Codes for CCMS in SAP Process Integration are:
CCMS Tcodes | Description |
---|---|
RZ21 | Monitoring : Prperties & Methods |
RZ20 | CCMS Monitor Sets |
GRMG | Generic Request and Message Generator |
Coming to Configuration SAP PI, check the following SAP Transaction Codes
Configuration Tcodes | Description |
---|---|
SLDAPICUST | SLD API Customizing |
RZ10 | edit system profile |
Check also Most Useful SAP EDI Transactions (SAP Idocs Tcodes) & SAP EDI Tables
For more information on EDI in SAP check the following articles:
Actually Idoc can be used in exchange process very easy and have SAP standard business Object behind.
Let’s remind some useful general SAP IDoc Configuration Tcodes:
Tcode | SAP Idoc Configuration Tocdes |
---|---|
WE20 | Partner Profiles |
WE21 | port definition |
BD82 | Maintain partner profile automatically |
BD54 | Logical System Creation |
BD64 | Maintain distribution model |
BD71 | Distibute customer model |
SALE | Create Logical System |
WE31 | Segment Creation at Transaction |
WE30 | Create IDOC (Basic IDoc Creation) |
If you want to use SAP PI (Process Integration) with Idocs, it is useful to have the SAP IDoc Adapter Transaction Codes:
Tcode | SAP PI Tcodes for IDoc Adapter |
---|---|
IDX1 | Idoc adapter |
IDX2 | idoc metadata |
IDX5 | monitor idoc adapter |
The main SAP EDI Monitoring Tcodes are:
Tcode | SAP PI Tcodes for EDI Monitoring |
---|---|
WE02 | Idoc display |
WE05 | Idoc list |
WE07 | Idoc statistics |
SM58 | QRFC (SOMETIMES idocs coluld not leave the SAP sending system) |
SM50 | Processes (are there enough in case of masss load) |
SMQ2 | Inbound Queues |
For ALE Administration check the following Tcodes:
SALE | Define ALE logical system |
---|---|
WE20 | Partner Profile |
WE21 | IDoc port |
WEDI | Mainatain menu for EDI related activities |
BALE | Main menu for ALE related activities |
The following List is not exclusively for SAP PI, but it is more for SAP Idoc :
WE31 | Segment editor |
---|---|
WE30 | Idoc editor to create and extend Idoc type |
BD53 | Reduce Idoc types for master data |
WE60 | Idoc documenataion (structure and segment definition) |
WE61 | Idoc documentation (control & data and status records) |
One the SAP IDoc Process is done, the next step is to test the SAP IDoc Processing.
Use the following SAP IDoc Testing Transaction Codes:
WE19 | Test tool for IDOC |
---|---|
WE12 | Create an inbound into an outbound |
WE16 | Process an incoming Idoc file |
WE17 | Process an incoming status file |
In order to reprocess a SAP IDocs, you can either one of the following Transaction Codes:
BD87 | Outbound |
---|---|
BD88 | Inbound |
IDXPW | to activate the IDOC message package |
---|---|
IDXP | to monitor the message packages |
If you want to search an Idoc from a value of field segment of the IDoc, you may consider the following Tcoes for Search IDoc:
WE09 | Search for IDocs by Content |
---|
Check the following article for the Most Useful SAP EDI Transactions (SAP Idocs Tcodes) & SAP EDI Tables.
If the mesasge or the Idoc is not fullfilled or lost you may check the Queues (inbound or OutBound Queue) to check the issue.
The main Transacion Codes for Queues in SAP (PI included) are:
SMQ1 | qRFC monitor – outbound message queue |
---|---|
SMQ2 | qRFC monitor – inbound message queue |
SMQ3 | save queue entry for qRFC monitor |
SMQS | to register the destination in QOUT scheduler |
SMQR | to register the queue |
The main Transaction code for RFC (Remote Function Call) in SAP are:
SM58 | Asynchronous RFC Error Log |
---|---|
SM59 | RFC Destinations |
Sometimes, to troubleshoot a PI (Process integration Issue), you may check the following SAP Tcodes :
SLDCHECK | Test SLD Connection |
---|---|
ST22 | ABAP dump analysis |
SM21 | Online System Log Analysis |
SM50 | Work process overview |
ST11 | Error Log Files |
SM20 | Analysis of Sequrity Audit Log |
AL11 | Directory listing |
---|---|
SE09/SE10 | Change Request(Transport Organiser) |
SE11 | Data dictionary |
SE37 | mantain funcion modules |
SICF | http server configuration |
table TSTC | sap transactions codes |
table TSTCT | transaction descriptions |
STMS | transports management |
SPAM | apply ABAP support packages |
SPAU | manage objects after apply support packages |
SE01 | manage change requests |
SM12 | Table locks |
SE38 | ABAP Editor |
SE11 | ABAP Dictionary |
SPROXY | ABAP Proxy Generation |
SE80 | Object Navigator |
ABAPDOCU | ABAP Documentation and Examples |
SE24 | Class Builder |
RZ70 | SLD Data Supplier |
SE16 | Data Browser |
SE93 | Maintain Transaction Codes |
SM30 | Call View Maintenance |
SM02 | System Messages |
SWF_XI_PBUILDER | for Detail BPM Process |
SWF_XI_CUSTOMIZING | transaction to check prerequisites for integration processes. |
WEOUTQUEUE | to start the queue processing |
SWF_XI_ADM_BPE | Start or Stop BPE |
SWF_XI_ADM_BPE_DISP | Display BPE Status |
SXI_MAPPING_Test | Test ABAP Mapping |
Source: XI Transaction Codes
If you want to go deeper into SAP Process Integration ( XI for the Old name and PO for Process Orchestration for the New one), chec the following SAP Books:
SAP ISU Tables for Technical master data, for Billing Master Data, Billing and invoicing Tables?…
SAP Fiori 3 UX and Design of SAP Fiori Apps for SAP S/4HANA, SAP TechEd…
Dunning is the business practice of informing a customer of past due payment. Dunning letters…
SAP AP Tcodes & SAP AR Tcodes: House Banks Tcodes, Advance Payments or Down Payments,…
What are the main SAP Payment Terms Tables ? What are the related Tables in…
Work center consists of master data related to routing of products. It contains data related…