2023-01-26 1588450
1588450 - FAQ for ERP - TM Logistics integration
Version 20 Type SAP Note
Language English Master Language English
Priority Recommendations / Additional Info Category FAQ
Release Status Released for Customer Released On 28.11.2022
Component TM-INT-LI ( Logistics Integration - General )
Please find the original document at [Link] 1588450
Symptom
This note contains a list of questions that may arise with regard to service-
based order integration from SAP ERP and SAP TM on TM side.
Please refer to the FAQ note 1530240 concerning questions on the SAP ERP side.
General system settings for the integration of SAP ERP in SAP TM get explained
in the following scenario guide:
Basic Settings and Integration for SAP ERP and S/4 HANA
When using TM in S4HANA in a side-by-side scenario the following blogs might be
helpful describing the setup for master data replication:
[Link]
[Link]
partners/
[Link]
sap-tm/
[Link]
in-sap-tm/
[Link]
sap-s-4hana/
Other Terms
TransportationRequestSUITERequest, XI Monitor, SXMB_MONI, SRT_MONI, message
monitor, business partner, delivery proposals, order integration, delivery
integration, OTR, DTR, IntracompanyTransportationRequestRequest_In
Reason and Prerequisites
Questions
1. What causes the error message 'Error during proxy processing An exception
with the type CX_SY_OPEN_SQL_DB occurred, but was neither handled locally,
nor declared in a RAISING clause The system tried to insert a data record,
even though a data record with the same primary key already exists' when
importing a message in TM ?
2. Why does the error message 'Business partner internal ID & does not
exist' occur although the business partner exists in SAP TM master data ?
3. Why it is not possible to restart a failed message in the XI Monitor of
SAP TM with status 'Transfer to External Application' ?
4. Why do I get one of the following errors when creating delivery
proposals? Time stream (& &) cannot be loaded Generation error in & ?
5. Why does an order get the consumption status 'Consumed Completely' and
© 2023 SAP SE or an SAP affiliate company. All rights reserved 1 of 8
2023-01-26 1588450
the lifecycle status 'Completed' although there are no deliveries for that
order ?
6. Why do I get the warning message 'FUs are unsuitable for delivery
proposal; removed from scope' when creating delivery proposals ?
7. Why does the error message 'Incoterm transfer location does not exist in
Customizing' occur when trying to import a transportation request message ?
8. A message with a location with an address has been imported in SAP TM.
Why was a new location created although a location with the same address
already exists ?
9. Why does the import of a message fail when a location with an address is
present in that message ?
10. The import of a message in SAP TM failed because of a locking error. How
can I repeat the processing of such a message?
11. Why are carriers transferred via CIF from SAP ERP to SAP TM not visible
in SAP TM as locations?
12. Why is the shipment creation message (TransportationOrderSCMRequest_In)
successfully processed but the freight order is not present in SAP TM or the
error messages 'Business system group is initial'(Message class /SAPAPO/LOM,
message number 004) or 'Logical system is initial' (Message class
/SAPAPO/LOM, message number 005) occur when trying to import shipment
creation message (TransportationOrderSCMRequest_In)?
13. Why does the import of a message to create an OTR fails in SAP TM with
the error 'Product 10 has no quantity information' although there is a
quantity?
14. How can the performance of the processing of messages of type
OutboundDeliveryBulkConfirmation_In can be improved in SAP TM?
Solution
1. Question:
What causes the error message "Error during proxy processing An exception with the type
CX_SY_OPEN_SQL_DB occurred, but was neither handled locally, nor declared in a RAISING clause
The system tried to insert a data record, even though a data record with the same primary key already
exists" when importing a message in SAP TM ?
Answer:
This problem is a result of missing SLD (system landscape directory) data. You
can maintain these data in IMG via the following path:
TM8.0 and TM8.1:
SAP Transportation Management -> Transportation Management -> Basic Functions ->
Define SLD Data of Business Systems
As of TM9.0:
SAP Transportation Management -> Transportation Management -> Integration ->
Define SLD Data of Business Systems
You have to insert the system information of the SAP ERP system from which the
message was sent.
Remark: The name of the Business System reflects the content of the fields
© 2023 SAP SE or an SAP affiliate company. All rights reserved 2 of 8
2023-01-26 1588450
SenderBusinessSystemID of the XML message.
2. Question:
Why does the error message 'Business partner internal ID & does not exist' occur although the
business partner exists in SAP TM master data ?
Answer:
As prerequisite master has to be transferred from SAP ERP to SAP TM via CIF. For
the SAP ERP master data vendor, customer, plant and shipping point an
appropriate location and a business partner have to be available in SAP TM.
If the business partner is available but you get the error message mentioned
above this can have the following reasons:
• Wrong SLD data (IMG activity: SAP Transportation Management ->
Transportation Management -> Integration -> Define SLD Data of Business
Systems).
The logical system present in the identification of the business partner has
to match the logical system assigned to the sender business system of the
message.
• Missing authorization of the remote user to display business partners. You
can use for instance the transaction SU53 to find such a missing
authorization.
3. Question:
Why it is not possible to restart a failed message in the XI Monitor of SAP TM with status 'Transfer to
External Application' ?
Answer:
The import of the message failed and the responsibility of this message was
handed over to an external application in this case the forward error handling
(FEH).
You can find such failed messages in the Postprocessing Desktop via transaction
/SAPPO/PPO2 with the appropriate error messages. Within this transaction you can
repeat or discard the processing of such a failed message.
4. Question:
Why do I get one of the following errors when creating delivery proposals? Time stream (& &) cannot
be loaded Generation error in &
Answer:
When delivery proposals should be sent from SAP TM to SAP ERP, it might be
necessary to recalculate the material availability date in case of a sales order
or a stock transport order. This is done by evaluating the time stream and the
pick pack duration. This evaluation needs to read data out of SAP ERP if the
data in SAP TM are out of date. This reading of data is done via remote function
call and this call fails with one of the error messages mentioned above if the
remote connection is not set up correctly or if the connection is broken.
In order to solve the problem the remote connection has to be setup and checked
for instance via transaction SM59.
Description of the check:
Enter transaction SM59 and open node 'ABAP Connections' and doubleclick the line
of the relevant logical RFC destination. First press button 'Connection Test'
© 2023 SAP SE or an SAP affiliate company. All rights reserved 3 of 8
2023-01-26 1588450
and if successful press button 'Remote Logon'. This remote logon should work
automatically, i.e. a ABAP modus of the requested remote system should appear. A
frequent error is that no remote user exists or that no password is assigned to
the remote user. In these cases a logon screen for the remote system will appear
during this test. But in the real application (sending of delivery proposals to
ERP) the error message 'Generation error in /SCMTMS/TSTR_GENERATE_REMOTE' will
appear.
5. Question:
Why does an order get the consumption status 'Consumed Completely' and the lifecycle status
'Completed' although there are no deliveries for that order ?
Answer:
• An order may contain only requested quantities for instance in case of
a purchase order. If the relevant OTR type is configured that confirmed
quantities are planning relevant there are no open planning relevant
quantities and as consequence the status is set as mentioned.
• No items are goods movement relevant. One reason could be that the
material is not stock relevant for the appropriate plant. This can be
changed in IMG in SAP ERP via the following path:
Logistics - General -> Material Master -> Basic Settings -> Material
Types -> Define Attributes of Material Types
6. Question:
Why do I get the warning message 'FUs are unsuitable for delivery proposal; removed from scope'
when creating delivery proposals ?
Answer:
This message occurs if your enter the delivery proposals screen and the selected
objects are not relevant for delivery creation or delivery proposals have
already been created for these objects.
The same message occurs after sending delivery proposals out of the delivery
proposals screen. This happens because the screen is built up completely new and
it is the same behavior as if you would enter the delivery proposal screen with
the same objects again.
7. Question:
Why does the error message 'Incoterm transfer location does not exist in Customizing' occur when
trying to import a transportation request message ?
Answer:
You are using an incoterm in the order or the delivery in SAP ERP that requires
an incoterm location (Incoterm Part 2). Such an incoterm location is a free text
in SAP ERP and needs to be mapped to a valid master data location in SAP TM. An
appropriate entry is needed in SAP Menu in a mapping table that can be found via
the following path:
Transportation Management -> Master Data -> Transportation Network -> Assign
Location to Incoterm Location
8. Question:
A message with a location with an address has been imported in SAP TM. Why was a new location
created although a location with the same address already exists ?
© 2023 SAP SE or an SAP affiliate company. All rights reserved 4 of 8
2023-01-26 1588450
Answer:
By default always a new location will be created if an address is part of the
message. If this is not desired you have to switch on the address search that
tries to find a location with the appropriate address for reuse. If the address
search is switched on a new location will only be created if the address search
fails.
The address search can be switched on in IMG via the following path:
SAP Transportation Management -> Transportation Management -> Basic Functions ->
Define General Settings for SAP TM
9. Question:
Why does the import of a message fail when a location with an address is present in that message ?
Answer:
When a location with an address is part of a message a new location based on
this address might be created (Refer to question 8 for details). For the
creation of such a new one-time-location a number range has to be defined.
This number range has to be created in IMG via the following path:
SAP Transportation Management -> Transportation Management -> Master Data ->
General Settings -> Define Number Range Intervals for One-time Locations
10. Question:
The import of a message in SAP TM failed because of a locking error. How can I repeat the
processing of such a message?
Answer:
• Option 1 (Without usage of forward error handling)
• Option 1a (When using communication via PI)
• You can repeat the processing of the failed message via the
transaction SXI_MONITOR. Within this transaction you select the
respective entry and restart the queue manually.
• Automatically you can repeat the processing of such failed
messages via report RSXMB_RESTART_MESSAGES.
• Option 1b (When using point-to-point communication via WSRM)
• You can repeat the processing of the the failed message via the
transaction SRT_MONI. Within this transaction you select the
respective entry and restart the queue manually.
• Automatically you can repeat the processing of such failed
messages via report SRT_UTIL_RESTART.
• Option 2 (With usage of forward error handling = FEH)
Prerequisite is that you activated the forward error handling. This can be
done in IMG via the followiong path:
Cross-Application Components -> Processes and Tools for Enterprise
Applications -> Enterprise Services -> Activate Error and Conflict Handler.
• The import of such a failed message can be repeated either manually via
Postprocessing Desktop (transaction /SAPPO/PPO2 or ECH_MONI_SEL) or
automatically via Retry Postprocessing Orders (transaction
/SAPPO/RESUBMIT).
• As of netweaver release 731 (Basis for TM9.0) it is possible to
configure a retry of failed messages before they are written into the
FEH.
© 2023 SAP SE or an SAP affiliate company. All rights reserved 5 of 8
2023-01-26 1588450
This can be done via the following customizing:
Cross-Application Components -> Processes and Tools for Enterprise
Applications -> Enterprise Services -> Error and Conflict Handler ->
Define Resolution Strategy
Attached the screenshot 'Sample_resolution_strategy' with an example
setting.
The locking issue may occur SAP TM if multiple deliveries for one order are
created in SAP ERP. If the respective delivery messages arrive in SAP TM at the
same time they are trying to change the same OTR and this may cause a locking
problem.
In order to avoid the parallel processing of these messages you could put the
delivery messages into the same queue in SAP ERP as supplementary configuration
to the options described above. The note 1926879 provides an example
implementation for the respective BAdI in SAP ERP for that purpose.
11. Question:
Why are carriers transferred via CIF from SAP ERP to SAP TM not visible in SAP TM as locations?
Answer:
By default locations of type carrier (1020) are not visible in SAP TM. They have
to be activated by modification in the following way:
This requires effort in the SCMB (for example note 1721601). TM specific
location types are switched and covered by the domains /SCMB/C_LOCTYPE_TM1 and
/SCMB/TM_LOCTYPE_TM1, where the new location type must be added. In addition to
make the values appear in the search help, help view /SAPAPO/V_TLOCNO must be
enhanced under selection conditions.
Note that as long as no specific logic is implemented based on this location
type, no further adjustments should be required. Also, any new location type
kind of interfers with the ERP integration as the CIF inbound does not cover
additional types.
12. Question:
Why is the shipment creation message (TransportationOrderSCMRequest_In) successfully processed
but the freight order is not present in SAP TM or the error messages 'Business system group is
initial'(Message class /SAPAPO/LOM, message number 004) or 'Logical system is initial' (Message
class /SAPAPO/LOM, message number 005) occur when trying to import shipment creation message
(TransportationOrderSCMRequest_In)?
Answer:
One of the following customizing settings is missing in SAP TM:
• The Business System Group of the SAP TM system has to added to the following
customizing:
SAP Transportation Management -> Transportation Management -> SCM Basis ->
Integration -> Basic Settings for Creating the System Landscape -> Maintain
Business System Group
• The Business System Group of the SAP TM system has to be added to the
following customizing:
SAP Transportation Management -> Transportation Management -> SCM Basis ->
Integration -> Basic Settings for Creating the System Landscape -> Assign
Logical System and Queue Type
13. Question:
© 2023 SAP SE or an SAP affiliate company. All rights reserved 6 of 8
2023-01-26 1588450
Why does the import of a message to create an OTR fails in SAP TM with the error 'Product 10 has no
quantity information' although there is a quantity?
Answer:
In SAP TM only unit of measures based on the dimensions mass, volume and 'no
dimensions' are supported and therefore UoMs like for instance meter (M) cannot
be used.
In order to get rid of the issue you have the following options:
1. Define weight and / or volume in the material master of the respective
material in SAP ERP. As consequence this weight and volume will be
transferred to SAP TM and can be used for freight unit building.
Remark: The non-supported UoM will only be visible in the OTR / DTR but will
not be propagated to the successor documents like freight units.
2. Define a customer specific UoM like in this example for meter with dimension
'no dimensions' and use it instead of the standard UoM.
a. For the usage of this new UoM for the message processing you have to
add the respective standard ISO code to the new UoM and remove this ISO
code from the standard UoM. As result the new UoM can be used in SAP TM
like any other UoM with dimension 'no dimensions'.
Attention: This solution is just working without side effects if the
respective ISO code is not used in another context for the for external
communcation to other systems. If this is the case option b. might be
taken into account.
b. Implement the BAdI /SCMTMS/TRQ_SE_REQREQ by filling the quantity pieces
on item level with the new created unit of measure.
14. Question:
How can the performance of the processing of messages of type
OutboundDeliveryBulkConfirmation_In can be improved in SAP TM?
Answer:
Activate the index DLV of the database table /SCMTMS/D_TORROT.
This document is referenced by
SAP Note/KBA Title
2837744 More information on 'Technical error during resubmission of order &1' in /SAPPO/RESUBMIT
2637346 LDAP message has errors in queue /SCMTMS/TOR_INT 156 / 157
2602248 /SCMTMS/PLN_DLV007 FU removed from scope; schedule line sequence or quantity incorrect
3266115 Integration of TM in SAP S/4HANA with SAP ERP or SAP S/4HANA
© 2023 SAP SE or an SAP affiliate company. All rights reserved 7 of 8
2023-01-26 1588450
Attachments
File Name File Size Mime Type
Sample_resolution_strategy.zip 46 application/x-zip-compressed
Terms of use | Copyright | Trademark | Legal Disclosure | Privacy
© 2023 SAP SE or an SAP affiliate company. All rights reserved 8 of 8