How To Fix /SCMTMS/SFIR158 - No FSD type for PO type, material group, plant, purch. group combination

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/SFIR -

• Message number: 158

• Message text: No FSD type for PO type, material group, plant, purch. group combination

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/SFIR158 - No FSD type for PO type, material group, plant, purch. group combination ?

  The SAP error message /SCMTMS/SFIR158 No FSD type for PO type, material group, plant, purch. group combination typically occurs in the context of SAP Transportation Management (TM) when there is an issue with the configuration of Freight Settlement Document (FSD) types. This error indicates that the system cannot find a valid FSD type for the specified combination of Purchase Order (PO) type, material group, plant, and purchasing group.
  Cause:
  
  
  Missing Configuration: The most common cause of this error is that the necessary configuration for the Freight Settlement Document types has not been set up in the system. This could be due to missing entries in the customizing settings for the relevant combinations.
  
  
  Incorrect Combinations: The combination of PO type, material group, plant, and purchasing group being used does not have a corresponding FSD type defined in the system.
  
  
  Data Inconsistencies: There may be inconsistencies or missing data in the master data related to the materials, plants, or purchasing groups.
  
  
  Solution:
  
  
  Check Configuration:
  
  Go to the customizing settings in SAP (transaction code SPRO).
  Navigate to the relevant section for Transportation Management and check the configuration for Freight Settlement Document types.
  Ensure that there is an entry for the specific combination of PO type, material group, plant, and purchasing group.
  
  
  
  Create Missing Entries:
  
  If the required FSD type does not exist, you will need to create it. This involves defining the FSD type in the system and linking it to the appropriate combinations.
  
  
  
  Review Master Data:
  
  Check the master data for the materials, plants, and purchasing groups involved in the transaction. Ensure that they are correctly set up and that there are no discrepancies.
  
  
  
  Testing:
  
  After making the necessary changes, test the process again to ensure that the error no longer occurs.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for detailed steps on configuring Freight Settlement Document types.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like SPRO (for configuration), SE11 (for data dictionary), or SE16 (for table display) to investigate the issue further.
  Tables: Relevant tables may include those that store FSD types and their configurations, such as /SCMTMS/FSDTYP or similar.
  SAP Notes: Check for any SAP Notes related to this error message for additional guidance or patches that may address known issues.
  
  If the problem persists after following these steps, it may be beneficial to consult with an SAP expert or reach out to SAP support for further assistance.