How To Fix CU842 - Enter a BOM Application for the Sales Order (SET) scenario.

SAP Error Message - Details

• Message type: E = Error

• Message class: CU - Variants / configuration messages

• Message number: 842

• Message text: Enter a BOM Application for the Sales Order (SET) scenario.

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 CU842 - Enter a BOM Application for the Sales Order (SET) scenario. ?

  The SAP error message CU842, which states "Enter a BOM Application for the Sales Order (SET) scenario," typically occurs in the context of sales order processing when the system expects a Bill of Materials (BOM) application to be defined for a specific sales order scenario. This error is often related to the configuration of the BOM and the sales order management process.
  Cause:
  
  
  Missing BOM Application: The primary cause of this error is that the system does not have a BOM application defined for the sales order scenario you are trying to execute. This can happen if the BOM is not properly configured or if the relevant settings in the system are incomplete.
  
  
  Incorrect Configuration: The configuration settings for the BOM application in the sales order may not be set up correctly in the system.
  
  
  Sales Order Type: The sales order type being used may not be compatible with the BOM application that is expected.
  
  
  Solution:
  
  
  Define BOM Application:
  
  Go to the transaction code SPRO (SAP Reference IMG).
  Navigate to Logistics > Sales and Distribution > Sales > Sales Order > Define BOM Application for Sales Order.
  Ensure that a BOM application is defined for the sales order type you are using.
  
  
  
  Check BOM Configuration:
  
  Ensure that the BOM is created and active for the material in question.
  Use transaction code CS01 to create or CS02 to change the BOM and verify that it is correctly set up.
  
  
  
  Review Sales Order Type:
  
  Check the sales order type being used and ensure it is configured to allow BOM applications.
  You can check this in the configuration settings under Sales Order Types.
  
  
  
  Material Master Data:
  
  Ensure that the material master data is correctly set up, including the relevant views that pertain to BOMs.
  
  
  
  Testing:
  
  After making the necessary changes, try to create or process the sales order again to see if the error persists.
  
  
  
  Related Information:
  
  
  BOM (Bill of Materials): A BOM is a comprehensive list of materials, components, and assemblies required to manufacture a product. In SAP, BOMs are used in various processes, including production and sales.
  
  
  Sales Order Management: This involves the processes related to the creation, processing, and management of sales orders in SAP.
  
  
  Transaction Codes:
  
  CS01: Create BOM
  CS02: Change BOM
  CS03: Display BOM
  SPRO: Access the SAP Reference IMG for configuration.
  
  
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or refer to SAP Notes for any specific patches or updates related to this error.