How To Fix /MOC/CONFIG117 - Document type &1 does not exist

/MOC/CONFIG117 - Overview

• Message type: E = Error

• Message class: /MOC/CONFIG -

• Message number: 117

• Message text: 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 /MOC/CONFIG117 - Document type &1 does not exist ?

  The SAP error message /MOC/CONFIG117 Document type &1 does not exist typically indicates that the system is trying to reference a document type that has not been defined or configured in the system. This error is often encountered in the context of SAP's Material Management (MM) or other modules that utilize document types for various transactions.
  
  Cause:
  
  Missing Document Type: The document type specified in the error message (&1) has not been created or is not active in the system.
  Incorrect Configuration: The document type may have been incorrectly configured or deleted.
  Authorization Issues: The user may not have the necessary authorizations to access the document type.
  Transport Issues: If the configuration was transported from another system, the transport may not have included the document type.
  
  
  Solution:
  
  
  Check Document Type Configuration:
  
  Go to the relevant configuration transaction (e.g., SPRO) and navigate to the section where document types are defined.
  Verify if the document type exists and is correctly configured.
  If