Do you have any question about this error?
Message type: E = Error
Message class: /SEHS/DG_DG -
Message number: 460
Message text: You have not specified any shipment legs
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
/SEHS/DG_DG460
- You have not specified any shipment legs ?The SAP error message
/SEHS/DG_DG460
indicating "You have not specified any shipment legs" typically occurs in the context of the SAP Transportation Management (TM) module. This error suggests that the system expects shipment legs to be defined for a transportation order or shipment, but none have been specified.Cause:
- Missing Shipment Legs: The most direct cause of this error is that the shipment legs have not been defined in the transportation order or shipment.
- Incorrect Configuration: There may be issues with the configuration of the transportation management settings that prevent the system from recognizing or creating shipment legs.
- Data Entry Error: Users may have missed entering the necessary details when creating the shipment or transportation order.
- Integration Issues: If the shipment legs are supposed to be generated from another system or module, there may be integration issues preventing this from happening.
Solution:
Define Shipment Legs:
- Go to the relevant transaction in SAP TM where you can define or edit shipment legs.
- Ensure that you have specified the necessary details for the shipment legs, including the start and end locations, transportation mode, and any other required parameters.
Check Configuration:
- Review the configuration settings in SAP TM to ensure that the system is set up correctly to handle shipment legs.
- Consult with your SAP Basis or TM configuration team if you suspect there are issues with the setup.
Review Data Entry:
- Double-check the data entry for the transportation order or shipment to ensure that all required fields are filled out correctly.
- Look for any mandatory fields that may have been overlooked.
Integration Check:
- If your system relies on data from other modules (like SAP ERP or external systems), verify that the integration is functioning correctly and that data is being passed as expected.
Consult Documentation:
- Refer to SAP documentation or help resources for specific guidance on how to create and manage shipment legs in your version of SAP TM.
Seek Support:
- If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with SAP experts who can provide more tailored assistance.
Related Information:
/SCMTMS/SHPMNT
for managing shipments.By following these steps, you should be able to resolve the error and successfully define shipment legs in your SAP system.
Get instant SAP help. Start your 7-day free trial now.
/SEHS/DG_DG459
User exit could not determine a selection date
What causes this issue? A function module is defined as a user exit to determine selection dates in the IMG activity <ZK>Specify date for deter...
/SEHS/DG_DG458
No mode of transport category entered
What causes this issue? No mode of transport category for the current country to be checked could be found in the SD document.System Response The ch...
/SEHS/DG_DG461
Dangerous goods check schema could not be read
What causes this issue? The <DS:GLOS.352A3008D3895CD5E10000009B38F974>dangerous goods check schema</> could not be read. This is due to a...
/SEHS/DG_DG462
Not all required data has been maintained
What causes this issue? One or more in the following list of data has not been maintained: Departure and destination countries along the leg or the c...
Click on this link to search all SAP messages.