How To Fix /ACCGO/CAS_FLLW_MSG390 - Sales document type &1 does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/CAS_FLLW_MSG -

• Message number: 390

• Message text: Sales document type &1 does not exist

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 /ACCGO/CAS_FLLW_MSG390 - Sales document type &1 does not exist ?

  The SAP error message /ACCGO/CAS_FLLW_MSG390 Sales document type &1 does not exist typically indicates that the system is trying to process a sales document type that has not been defined or is not recognized in the system. This can occur in various scenarios, such as during the creation of a sales order, invoice, or when processing a follow-up document.
  Cause:
  
  Missing Configuration: The sales document type specified in the error message (&1) has not been configured in the system.
  Incorrect Document Type: The document type may have been incorrectly entered or referenced in the transaction.
  Transport Issues: If the configuration was recently transported from another system, it may not have been properly imported or activated.
  Authorization Issues: The user may not have the necessary authorizations to access the specified sales document type.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the transaction code VOTXN or VOT2 to check the configuration of sales document types.
  Ensure that the sales document type exists and is properly configured.
  
  
  
  Create or Modify Document Type:
  
  If the document type does not exist, you may need to create it using transaction VOTXN.
  If it exists but is not configured correctly, make the necessary adjustments.
  
  
  
  Verify Input:
  
  Double-check the input in the transaction where the error occurred to ensure that the correct sales document type is being used.
  
  
  
  Check Transport Requests:
  
  If the issue arose after a transport, verify that the transport request was successful and that all necessary objects were included.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary authorizations to access the sales document type. This can be checked with the help of your SAP security team.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific sales document type and its configuration.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  VOTXN: Configuration of Sales Document Types
  VOT2: Display Sales Document Types
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting the SAP Community for further assistance.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.