The SAP TM Collaboration Portal is an web based component allowing collaboration between TM and the carriers. It covers freight procurement, tendering, execution and finally invoicing/dispute management. So a lot to talk about.
The trigger concept is used to handle locking situations, allow asynchronous updates and separation of concerns.
This concept and the report to process this triggers are explained in this episode.
The consulting notes mentioned are:
1. For trigger concept mentioned in the podcast is 1747234
2. TM Super Authorization: 1909959
The Application Operations Guide can be found here (for 9.0):
The question “Where can I get TM information and documentation?” is something we hear a lot and we try to answer this in this episode.
We try to be complete on the different types of documentation, who is the target audience, how can they be found, what are the available languages etc.
TM-Podcast episode 17 gives an overview of the Transportation Management trainings that are currently offered. We talk about the individual content of each training and the prerequisites that are required to successfully take part in this courses. Besides that we shortly talk about certification and the dependencies between the courses.
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
– as of NW 7.31, separate transaction for WSRM based integration: SRT_MONI