How To Fix >4836 - Short acct assgmt &1 &2 is not permitted for tfr pstg from clarif. wklist

SAP Error Message - Details

• Message type: E = Error

• Message class: >4 - SAP File Transfer Protocol

• Message number: 836

• Message text: Short acct assgmt &1 &2 is not permitted for tfr pstg from clarif. wklist

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 >4836 - Short acct assgmt &1 &2 is not permitted for tfr pstg from clarif. wklist ?

  The SAP error message "4836 Short acct assignment &1 &2 is not permitted for transfer posting from clarification worklist" typically occurs in the context of inventory management and transfer postings. This error indicates that there is an issue with the account assignment when trying to perform a transfer posting from the clarification worklist.
  Cause:
  
  
  Account Assignment Issues: The error suggests that the account assignment (e.g., cost center, internal order, etc.) is not valid for the type of transfer posting you are trying to execute. This could be due to:
  
  The account assignment being too short or not meeting the required length.
  The account assignment not being allowed for the specific transaction type.
  The account assignment being inactive or not properly configured in the system.
  
  
  
  Configuration Settings: There may be configuration settings in the SAP system that restrict certain account assignments for transfer postings.
  
  
  Data Integrity Issues: There could be inconsistencies or missing data in the master data (e.g., material master, vendor master) that are causing the error.
  
  
  Solution:
  
  
  Check Account Assignment: Verify the account assignment details (e.g., cost center, internal order) you are using for the transfer posting. Ensure that they are valid and meet the required criteria.
  
  
  Review Configuration: Check the configuration settings in the SAP system related to account assignments for transfer postings. This may involve reviewing the settings in the following areas:
  
  Transaction codes related to inventory management.
  Account assignment categories in the configuration.
  
  
  
  Correct Data: If there are any inconsistencies or missing data in the master data, correct them. Ensure that all relevant master data is properly maintained.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific details on the error message and related transaction codes.
  
  
  Contact Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as MB1B (Transfer Posting), MB1A (Goods Withdrawal), and others that may be involved in the process.
  SAP Notes: Search for SAP Notes related to error message 4836 in the SAP Support Portal for any known issues or patches.
  User Forums: Check SAP community forums or user groups for discussions related to this error, as other users may have encountered and resolved similar issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.