How To Fix APPL_MM_PUR_PO087 - Purchase order type &1 is not supported.

SAP Error Message - Details

• Message type: E = Error

• Message class: APPL_MM_PUR_PO - Message Class for Purchase Order

• Message number: 087

• Message text: Purchase order type &1 is not supported.

What causes this issue?

You have entered a purchase order type that is not supported by the
system.

System Response

When you create a new purchase order, the system inserts the purchase
order type 'NB' by default.

How to fix this error?

You can change the default entry and use any customer-defined purchase
order type (Z*) that has been copied with all dependent entries from
purchase order type 'NB'. Please use such a purchase order type.
Once the purchase order has been saved, the purchase order type is
read-only.

Procedure for System Administrators

For more information, how to create customer-defined document types for
purchase orders, see the configuration help for the following
configuration step (required role: configuration expert - business
process): Manage Your Solution -> Configure Your Solution -> Application
Area: Sourcing and Procurement -> Sub Application Area: Operational
Procurement -> Purchase Order Processing -> Define Document Types.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message APPL_MM_PUR_PO087 - Purchase order type &1 is not supported. ?

  The SAP error message "APPL_MM_PUR_PO087 Purchase order type &1 is not supported" typically occurs when you are trying to create or process a purchase order (PO) of a type that is not configured or supported in the system. This can happen for various reasons, including configuration issues or missing settings in the system.
  Cause:
  
  Unsupported Purchase Order Type: The purchase order type you are trying to use (indicated by &1 in the error message) is not defined in the system or is not allowed for the transaction you are attempting.
  Configuration Issues: The purchase order type may not be properly configured in the system settings, or it may have been deactivated.
  Authorization Issues: The user may not have the necessary authorizations to create or process that specific type of purchase order.
  System Settings: The system may be set up to restrict certain purchase order types based on specific criteria (e.g., company code, purchasing organization).
  
  Solution:
  
  
  Check Purchase Order Type Configuration:
  
  Go to the configuration settings in SAP (Transaction code SPRO).
  Navigate to Materials Management > Purchasing > Purchase Order > Define Purchase Order Types.
  Verify if the purchase order type you are trying to use is defined and active.
  
  
  
  Review User Authorizations:
  
  Ensure that the user has the necessary authorizations to create or process the specific purchase order type.
  Check the user's role assignments and authorization objects related to purchasing.
  
  
  
  Consult with SAP Basis or Functional Team:
  
  If you are unsure about the configuration or if changes are needed, consult with your SAP Basis or functional team to review the settings and make necessary adjustments.
  
  
  
  Check for Customizations:
  
  If your organization has custom developments or enhancements, check if any custom logic is affecting the purchase order type processing.
  
  
  
  Review Documentation:
  
  Check any internal documentation or guidelines that may specify which purchase order types are supported for your specific business processes.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  ME21N (Create Purchase Order)
  ME22N (Change Purchase Order)
  ME23N (Display Purchase Order)
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to purchase order types.
  User Manuals: Refer to user manuals or training materials that may provide insights into the correct usage of purchase order types in your organization.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.