How To Fix /SCWM/DELIVERY058 - Document type &1 not allowed for confirmation

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCWM/DELIVERY -

• Message number: 058

• Message text: Document type &1 not allowed for confirmation

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 /SCWM/DELIVERY058 - Document type &1 not allowed for confirmation ?

  The SAP error message /SCWM/DELIVERY058 Document type &1 not allowed for confirmation typically occurs in the context of the Extended Warehouse Management (EWM) module when you are trying to confirm a delivery document that is not permitted for confirmation based on its document type.
  Cause:
  
  Document Type Restrictions: The document type associated with the delivery (indicated by &1 in the error message) is not configured to allow confirmations in the system. This could be due to specific settings in the EWM configuration.
  Configuration Settings: The system may have been set up to restrict certain document types from being confirmed, possibly due to business rules or operational procedures.
  Incorrect Document Type: The document type being used may not be appropriate for the operation you are trying to perform.
  
  Solution:
  
  
  Check Document Type Configuration:
  
  Go to the EWM configuration settings and check the allowed document types for confirmations. This can typically be found in the Customizing settings under the EWM area.
  Ensure that the document type you are trying to confirm is included in the list of allowed types.
  
  
  
  Modify Document Type Settings:
  
  If the document type should allow confirmations, you may need to modify the configuration to include it. This may involve working with your SAP Basis or EWM configuration team to adjust the settings.
  
  
  
  Use Correct Document Type:
  
  If the document type is not meant to be confirmed, ensure that you are using the correct document type for the operation you are trying to perform. You may need to create a new document or use a different existing document type that is allowed for confirmation.
  
  
  
  Consult Documentation:
  
  Review the SAP documentation or help resources related to EWM and document types to understand the implications of the settings and how they affect confirmations.
  
  
  
  Check User Authorizations:
  
  Ensure that the user attempting to perform the confirmation has the necessary authorizations to confirm the document type in question.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like /SCWM/PRDI for processing deliveries or /SCWM/CONF for confirmations to check the status of the documents.
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional guidance on document type configurations.
  Support: If the issue persists after checking the configurations, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.