How To Fix AD01506 - Sales document type &1 does not belong to sales doc. category 'Quotation'

SAP Error Message - Details

• Message type: E = Error

• Message class: AD01 - DI Processor (Expense-related Billing)

• Message number: 506

• Message text: Sales document type &1 does not belong to sales doc. category 'Quotation'

What causes this issue?

You have entered a sales document type in the DIP profile or on this
screen (Customer Quotation Calculation: Change Header Data) that does
not match the sales document category <LS>quotation</>.
However, the creation of a quotation for a service order is only
possible when you select sales document types from the <LS>quotation</>
category.

System Response

Processing cannot continue.

How to fix this error?

Enter a sales document type from the category <LS>quotation</> in the
DIP profile or on this screen (see above).

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message AD01506 - Sales document type &1 does not belong to sales doc. category 'Quotation' ?

  The SAP error message AD01506 indicates that there is a mismatch between the sales document type you are trying to use and the expected sales document category for quotations. This error typically occurs when you attempt to create or process a sales document that is not configured as a quotation in the system.
  
  Cause:
  
  Incorrect Sales Document Type: The sales document type you are using does not belong to the category of quotations. Each sales document type in SAP is associated with a specific category (e.g., quotation, order, contract).
  
  Configuration Issues: The sales document type may not be properly configured in the system to be recognized as a quotation.
  Custom Development: If there are custom developments or modifications in the system, they may have altered the expected behavior of sales document types.
  
  
  Solution:
  
  
  Check Sales Document Type Configuration:
  
  Go to the transaction code VOTXN (or SPRO -> Sales and Distribution -> Sales -> Sales Document -> Define