How To Fix /PLMI/DIR_BRW_BO035 - Document type is missing

SAP Error Message - Details

• Message type: E = Error

• Message class: /PLMI/DIR_BRW_BO -

• Message number: 035

• Message text: Document type is missing

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 /PLMI/DIR_BRW_BO035 - Document type is missing ?

  The SAP error message /PLMI/DIR_BRW_BO035 Document type is missing typically occurs in the context of SAP's Document Management System (DMS) or when working with document-related transactions. This error indicates that the system is unable to find a valid document type for the operation you are trying to perform.
  Cause:
  
  Missing Configuration: The document type you are trying to use has not been defined in the system.
  Authorization Issues: The user may not have the necessary authorizations to access the document type.
  Incorrect Input: The document type may not have been entered correctly in the transaction or program.
  System Customization: Custom developments or modifications may have inadvertently removed or altered the document type settings.
  
  Solution:
  
  
  Check Document Type Configuration:
  
  Go to the configuration settings for document types in SAP. This can usually be found in the customizing transaction (SPRO).
  Navigate to the relevant section for Document Management System and ensure that the required document type is defined and active.
  
  
  
  Verify User Authorizations:
  
  Check if the user has the necessary authorizations to access the document type. This can be done through transaction SU53 or by consulting with your security team.
  
  
  
  Input Validation:
  
  Ensure that the document type is correctly entered in the transaction. Double-check for any typos or incorrect values.
  
  
  
  Consult Documentation:
  
  Review any related documentation or notes from SAP that might provide additional context or updates regarding the document type.
  
  
  
  Check for Custom Developments:
  
  If there have been any recent changes or custom developments in the system, review those to ensure they have not affected the document type settings.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. They may provide patches or additional insights based on the specific version of your SAP system.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OAC2 (for document types) and OAC3 (for document management).
  SAP Notes: Search for SAP Notes related to document types and the specific error message for any known issues or fixes.
  User Forums: Check SAP community forums or other user groups for similar issues and solutions shared by other users.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.