How To Fix BOS01170 - Purchase requisition cannot be created; see log

SAP Error Message - Details

• Message type: E = Error

• Message class: BOS01 - Customer BOS Processing

• Message number: 170

• Message text: Purchase requisition cannot be created; see log

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 BOS01170 - Purchase requisition cannot be created; see log ?

  The SAP error message BOS01170 indicates that a purchase requisition cannot be created due to some underlying issues that need to be addressed. This error typically arises when there are problems with the configuration, data, or authorization related to the purchase requisition process.
  Possible Causes:
  
  Missing or Incorrect Data: Required fields in the purchase requisition may be missing or incorrectly filled out.
  Authorization Issues: The user may not have the necessary permissions to create a purchase requisition.
  Configuration Issues: There may be configuration settings in the SAP system that prevent the creation of purchase requisitions.
  Material Master Data: The material or service being requested may not be set up correctly in the system.
  Vendor Issues: The vendor may not be active or properly configured in the system.
  Document Type Issues: The document type for the purchase requisition may not be set up correctly.
  
  Solutions:
  
  Check the Log: The error message suggests checking the log for more details. Use transaction code SLG1 to view the application log and identify the specific issue.
  Review Data Entry: Ensure that all required fields are filled out correctly in the purchase requisition. Check for any mandatory fields that may be missing.
  Verify Authorizations: Check the user’s authorization roles to ensure they have the necessary permissions to create purchase requisitions.
  Check Configuration: Review the configuration settings for purchase requisitions in the SAP system. This may involve checking the document types, number ranges, and other related settings.
  Material and Vendor Master Data: Ensure that the material and vendor master data are correctly set up and active. You can check this using transaction codes MM03 for material and XK03 for vendor.
  Consult with IT or SAP Support: If the issue persists, it may be necessary to consult with your IT department or SAP support team for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME51N (Create Purchase Requisition), ME52N (Change Purchase Requisition), and ME53N (Display Purchase Requisition).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Review SAP documentation or user manuals related to purchase requisition processes for additional guidance.
  
  By following these steps, you should be able to identify and resolve the issue causing the BOS01170 error message in SAP.