How To Fix /PRA/ACCOUNTING274 - Document type is not maintained in Customizing

SAP Error Message - Details

• Message type: E = Error

• Message class: /PRA/ACCOUNTING -

• Message number: 274

• Message text: Document type is not maintained in Customizing

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 /PRA/ACCOUNTING274 - Document type is not maintained in Customizing ?

  The SAP error message /PRA/ACCOUNTING274 Document type is not maintained in Customizing typically occurs in the context of the SAP system when dealing with document types in the context of accounting or financial transactions. This error indicates that the document type you are trying to use has not been properly configured in the system's Customizing settings.
  Cause:
  
  Missing Document Type Configuration: The document type you are trying to use has not been defined in the Customizing settings for the relevant application area (e.g., Financial Accounting, Controlling, etc.).
  Incorrect Document Type: The document type may be incorrectly specified in the transaction or process you are executing.
  Transport Issues: If the configuration was recently transported from another system, it may not have been included or may not have been activated properly.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Document Type Configuration:
  
  Go to the SAP Customizing Implementation Guide (IMG) by using transaction code SPRO.
  Navigate to the relevant section for document types. For example, for Financial Accounting, you would go to:
  Financial Accounting (New) -> Financial Accounting Global Settings (New) -> Document -> Document Types -> Define Document Types
  
  Verify if the document type in question is listed. If it is not, you will need to create it.
  
  
  
  Create or Maintain Document Type:
  
  If the document type is missing, you can create it by clicking on "New Entries" and filling in the required fields (like Document Type, Description, etc.).
  Ensure that the document type is assigned to the correct company code and is configured according to your business requirements.
  
  
  
  Check for Transport Issues:
  
  If the configuration was recently transported, check the transport logs to ensure that the document type was included and activated in the target system.
  
  
  
  Review User Authorizations:
  
  Ensure that the user executing the transaction has the necessary authorizations to use the specified document type.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific details related to the document type and its configuration.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like OBY6 (for document types) or OBD2 (for document type assignment) to access relevant settings.
  SAP Notes: Check SAP Notes for any known issues or additional guidance related to this error message.
  Testing: After making changes, test the transaction again to ensure that the error is resolved.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or functional team for further investigation.