In this talk we cover how TM is technically integrated with other systems such as SAP ERP or SAP GTS (A2A integration), resp. with business partners such as carriers (B2B integration) to exchange transactional data such as a transportation requirement or a transportation order.
Both, mediated integration via SAP PI as well as point-to-point integration using WSRM is discussed w.r.t. technical and application specific configuration of the messaging runtime, pros and cons, principal requirements.
For PI based integration, the PI architecture, PI pipeline steps, relevant PI configuration objects, and the role of SLD (system landscape directory) are explained. In addition, we discuss how shipped configuration templates, so called process integration scenarios, can be used to configure the PI runtime fot the TM specific A2A integration scenarios by using a wizard.
For P2P based integration, the recommended central configuration is explained and prerequisites such as service groups are described.
As round-up some basic trouble shooting check points are shortly summarized, and the necessary steps to enhance a standard interface by customer fields are listed.


List of some important transactions:

PI local integration engine configuration: SXMB_ADMIN -> Integration Engine Configuration

SLD Check: SLDCHECK

Integration Builder (Web UI for PI Tools Enterprise Services Repository, Integration Directory, SLD, Central Monitoring): SXMB_IFR
- Design Time (e.g. needed for Interface Enhancments): SXMB_IFR -> Enterprise Services Builder
- Configuration of PI runtime: SXMB_IFR -> Integration Builder

WSRM configuration: SOAMANAGER

Message monitoring:
- SXMB_MONI
- as of NW 7.31, separate transaction for WSRM based integration: SRT_MONI

Forward Error Handling: ECH_MONI

Ver todos los episodios