SAP Note

2574435 - FAQ for TM embedded in S/4 Hana

Component: TM-INT-LI (Transportation Management (no software transports) > Integration > Logistics
Integration - General), Version: 14, Released On: 13.02.2023

Symptom
This note contains a list of questions that may arise when using TM embedded in S/4 Hana.

Other Terms
FU = Freight unit, FUBR = freight unit building rule

Reason and Prerequisites

Questions
1. Why are FUs not created / updated directly when creating an order / delivery ?
2. Why doesn't a condition deliver the desired result if it is using order or delivery related data ?
3. Why is the propagation of texts from an order or delivery to the TM execution documents not working ?
4. Why does the creation of a location based on a plant or a shipping point fail ?
5. How can I adapt the data which are a result of the internal mapping between the SAP ERP documents and the SAP TM
documents with customer specific logic ?
6. Why has a FU got an empty location ?
7. Why is there no delivery split / update although the planning result of the execution documents should trigger such a split /
update ?
8. Why is there no FU or FU item for a respective order or delivery item ?
9. Why are TM documents, such as the FU, not updated when the delivery is updated and relevant for EWM ?
10. Why does the delivery creation out of TM fails for batch-managed materials when using ASR ?

Solution
1. Question:
Why are FUs are not created / updated directly when creating an order / delivery ?

Answer:
In case of the creation of new addresses / one-time-locations / locations or if FUs are locked in TM the TM specific processing
is scheduled in a BGRFC queue and processed later. The queue can be monitored via the standard BGRFC transactions like
for instance SBGRFCMON (bgRFC Monitor). The name of the queue (Inbound destination) relevant for TM is
TM_BGRFC_INBOUND.
For more details concerning TM and BGRFC refer to the note 2526415 (Updated trigger concept using bgRFC processing).

Remark: Initially you have to execute the report /SCMTMS/TRIGGER_SETUP_BGRFC once in order to create the inbound
destination.

2. Question:
Why doesn't a condition deliver the desired result if it is using order or delivery related data ?
Answer:
Internally a data container is present containing the data of the order / delivery used by the TM specific logic.
In order to make use of the data of this container you have to use the determination class
/SCMTMS/CL_COND_TRQ_CT_EXTR in the respective data access definition of the condition. In addition to this class you
have to use /SCMTMS/TRQ as business object, the respective node - ROOT and ITEM are supported - and the respective field
you would like to use.
Remark: The data crawler cannot be used in this context because there is no instance of the BO /SCMTMS/TRQ. This means
if the requirements cannot be fulfilled with the class mentioned above a customer specific determination class has to be
introduced retrieving the desired data respectively.

3. Question:
Why is the propagation of texts from an order or delivery to the TM execution documents not working ?
Answer:
In general the propagation of texts has to be set up as described in the KBA 2370187 also for SAP TM embedded in S/4 Hana.
The difference is that in the text schema you have to use an access sequence containing an access with the determination class
/SCMTMS/CL_TEXT_ACCESS_ERP and the access type 'External Source'.
In addition the customlzing 'Assign SD/MM Text Types to TM Text Types for SO/PO' and 'Assign Logistics Execution Text
Types to TM Text Types for Deliveries' is relevant in this context.

4. Question:
Why does the creation of a location based on a plant or a shipping point fail ?
Answer:
A locations requires an address and therefore it has to be ensured that for the plant or the shipping point an address is
present.

5. Question:
How can I change the data which are a result of the internal mapping between the SAP ERP documents and
the SAP TM documents ?
Answer:
There is the BAdI /SCMTMS/BADI_LOGINT_CHG_TTRQ allowing the manipulation of the SAP TM related data.

6. Question:
Why has a FU got an empty location ?
Answer:
In case you are using document addresses an one-time-location is being created based on the respective address number. For
the creation of such an one-time-location a number range interval for the number range /SCMTMS/OT has to be present.

7. Question:
Why is there no delivery split / update although the planning result of the execution documents should
trigger such a split / update ?
Answer:
1. The delivery split / update is triggered asynchronously via bgRFC and therefore the bgRFC has to be configured
properly. For details to the required configuration of the bgRFC refer to question 1 describing that in another context.
 2. The delivery split is using the split profile 0003 meaning this split profile has to be present and in addition the respective
delivery type has to be assigned to this split profile.
The activity to add the delivery type to the split profile can be found via the following path in IMG:
Logistics Execution -> Shipping -> Deliveries -> Subsequent Delivery Split

8. Question:
Why is there FU or FU item for a respective order or delivery item ?
Answer:
There are many reasons why an order / delivery item is not reflected as FU item. In order to make it easier to analyze such an
issue the program /SCMTMS/CHK_DOC_INT_TM_INTEGR has been introduced with the note 2779484 identifying missing
customizing or other inconsistencies.

9. Question:
Why are TM documents, such as the FU, not updated when the delivery is updated and relevant for EWM ?
Answer:
When using the direct TM - EWM integration, changes of the delivery are not propagated anymore to the respective
FU. Changes in this context are done via the loading appointment service triggered out of EWM which is based on the EWM
TU updating the respective FO. This means in context with the direct TM - EWM integration, EWM is leading for performing
the changes.
If you don't intend to use the direct TM - EWM integration you have to switch it off explicitly via the BAdI
/SCMTMS/BADI_LOGINT_CHG_TTRQ. In method CHANGE_TTRQ_LE, you need to set the value of the field
DIRECT_EWM_ACTIVE of the root of the transient TRQ to 'G'.

As of S4HANA 2020 the fields WM_WH_NUMBER and WM_LOGSYS has to be cleared as well.

10. Question:
Why does the inbound delivery creation out of TM fails for batch-managed materials when using ASR ?
Answer:
You are using the ASR (Advanced Shipping & Receiving) process and the freight units based on the order already contain
package items which should be transferred to the inbound delivery. The delivery creation fails because batch creation is
required for the inbound delivery for batch-managed materials.
In order to activate the automatic batch creation you have to use the following the IMG activity by setting the flag "Automatic
Batch Creation" for the respective item categories:
Logistics Execution -> Shipping -> Deliveries -> Define Delivery Item Categories

This document refers to

SAP Note/KBA Component Title

2769186 TM-CF System Transformation SAP TM to TM in SAP S/4HANA

This document is referenced by

SAP Component Title
Note/KBA

2860697 S/4 HANA Embedded TM BAdIs

2649823 TM-PLN-FU Empty Requested/Acceptable Dates at Incoterm Locations for OTR/DTR based FUs in TM
2874379 TM-INT-LI- One-time Location behavior in FU when using a Purchase or Stock Transfer Order with a deviating
MM info in Delivery Address tab.

2370187 TM-PLN-FU How to Configure Correct Propagation of Notes (Text) in SAP Transportation Management