How To Fix FSH_ARUN_MSG381 - Order &1 not allocated to &2 %, achieved &3 %

FSH_ARUN_MSG381 - Overview

• Message type: E = Error

• Message class: FSH_ARUN_MSG - ARUN Message Class

• Message number: 381

• Message text: Order &1 not allocated to &2 %, achieved &3 %

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 FSH_ARUN_MSG381 - Order &1 not allocated to &2 %, achieved &3 % ?

  The SAP error message FSH_ARUN_MSG381 typically relates to the allocation of an order in the context of SAP Fashion Management (FSH). This message indicates that a specific order (identified by &1) is not fully allocated to a particular location or distribution channel (identified by &2), and it shows the percentage of allocation achieved (indicated by &3).
  
  Cause:
  
  Insufficient Stock: The most common cause is that there is not enough stock available to fulfill the order requirements.
  Allocation Rules: There may be specific allocation rules or settings in the system that prevent the order from being fully allocated.
  
  Configuration Issues: There could be configuration issues in the allocation process or in the master data related to the order or the products.
  Order Status: The order might be in a status that does not allow for allocation.
  Data Inconsistencies: There may be inconsistencies in the data related to the order, such as incorrect product details or location settings.
  
  
  Solution:
  
  Check