How To Fix /SCMTMS/TS_PROF304 - Depart. from time strm does not exist for exclded date &1, time &2 (UTC)

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TS_PROF -

• Message number: 304

• Message text: Depart. from time strm does not exist for exclded date &1, time &2 (UTC)

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/TS_PROF304 - Depart. from time strm does not exist for exclded date &1, time &2 (UTC) ?

  The SAP error message /SCMTMS/TS_PROF304 indicates that there is an issue with the transportation scheduling in the SAP Transportation Management System (TMS). Specifically, the error states that the departure time stream does not exist for the excluded date and time in UTC.
  Cause:
  This error typically occurs due to one of the following reasons:
  
  
  Missing Time Stream Configuration: The time stream for the specified date and time has not been configured in the system. This could happen if the time stream is not defined for the specific date or if the time stream is not active.
  
  
  Incorrect Date/Time Input: The date and time being referenced may not be valid or may not correspond to any defined time stream in the system.
  
  
  Exclusion of Dates: The date in question may have been excluded from the scheduling process, leading to the absence of a corresponding time stream.
  
  
  Time Zone Issues: There may be discrepancies in time zone settings, leading to confusion about the actual time being referenced.
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Time Stream Configuration:
  
  Navigate to the configuration settings for transportation scheduling in SAP TMS.
  Verify that the time stream is correctly defined for the date and time in question.
  Ensure that the time stream is active and includes the necessary time intervals.
  
  
  
  Review Date and Time Inputs:
  
  Double-check the date and time being used in the transaction or scheduling process.
  Ensure that the date and time are valid and correspond to the expected format.
  
  
  
  Adjust Exclusion Settings:
  
  If certain dates are excluded from scheduling, review the exclusion settings to determine if the date in question can be included.
  Modify the exclusion settings if necessary to allow for the required scheduling.
  
  
  
  Check Time Zone Settings:
  
  Ensure that the time zone settings in the system are correctly configured.
  Verify that the UTC time being referenced aligns with the local time settings.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for additional guidance on configuring time streams and handling scheduling errors.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like /SCMTMS/TS_PROF to access the time stream configuration settings.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide patches related to this error.
  User Forums: Engage with SAP community forums or user groups for insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the root cause of the error and implement the necessary solutions to resolve it.