How To Fix /SCMTMS/TOR854 - Pick-up time for carrier &1 with service level &2 could not be determined


SAP Error Message - Details

  • Message type: E = Error

  • Message class: /SCMTMS/TOR -

  • Message number: 854

  • Message text: Pick-up time for carrier &1 with service level &2 could not be determined

  • Show details Hide details


  • Self-Explanatory Message

    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.



    What else can you do?

    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.


Smart SAP Assistant

  • What is the cause and solution for SAP error message /SCMTMS/TOR854 - Pick-up time for carrier &1 with service level &2 could not be determined ?

    The SAP error message /SCMTMS/TOR854 indicates that the system is unable to determine the pick-up time for a specific carrier and service level combination. This error typically arises in the context of transportation management within SAP, particularly when dealing with transportation orders and planning.

    Causes:

    1. Missing Configuration: The carrier or service level may not be properly configured in the system. This includes missing or incorrect settings in the transportation management configuration.
    2. Data Inconsistencies: There may be inconsistencies in the master data related to the carrier, service level, or transportation lanes.
    3. Time Zone Issues: The system may be facing issues related to time zone settings, which can affect the calculation of pick-up times.
    4. Transportation Lane Not Defined: The transportation lane between the shipping point and the destination may not be defined or may not have valid parameters.
    5. Service Level Agreement (SLA) Issues: The service level agreement for the carrier may not be set up correctly or may be missing.

    Solutions:

    1. Check Carrier and Service Level Configuration:

      • Ensure that the carrier and service level are correctly defined in the system.
      • Verify that the necessary parameters for the carrier and service level are maintained in the configuration.
    2. Review Transportation Lane Settings:

      • Check if the transportation lane between the relevant locations is defined and active.
      • Ensure that the lane has valid parameters, including transit times and pick-up times.
    3. Validate Master Data:

      • Review the master data for the carrier, service level, and any related entities to ensure there are no inconsistencies or missing information.
    4. Check Time Zone Settings:

      • Verify the time zone settings in the system to ensure they are correctly configured for the locations involved.
    5. Consult Documentation:

      • Refer to SAP documentation or help resources for specific guidance on configuring transportation management and resolving related errors.
    6. Debugging:

      • If the issue persists, consider using debugging tools or transaction codes (like SLG1 for application logs) to trace the error and identify the root cause.

    Related Information:

    • Transaction Codes: You may find it useful to use transaction codes such as /SCMTMS/TOR for transportation orders or /SCMTMS/PL for planning to review the relevant data.
    • SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide updates and patches.
    • Community Forums: Engage with SAP community forums or support channels for additional insights and shared experiences from other users who may have encountered similar issues.

    By following these steps, you should be able to identify the cause of the error and implement the necessary solutions to resolve it.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant