Do you have any question about this error?
Message type: E = Error
Message class: FZ - Payment Transactions
Message number: 336
Message text: Posting key & with account type & is not permitted for comapny code clrgs
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.
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.
FZ336
- Posting key & with account type & is not permitted for comapny code clrgs ?The SAP error message FZ336 indicates that there is an issue with the posting key and account type combination for a specific company code during a financial transaction. This error typically arises when the system detects that the combination of the posting key and the account type is not allowed for the specified company code.
Cause:
- Invalid Posting Key: The posting key being used is not valid for the account type specified in the transaction.
- Account Type Restrictions: The account type associated with the posting key may not be permitted for the company code in question.
- Configuration Issues: There may be configuration settings in the Financial Accounting (FI) module that restrict the use of certain posting keys with specific account types for the company code.
- Transaction Type: The type of transaction being processed may not align with the allowed posting keys for the account type.
Solution:
Check Posting Key Configuration:
- Go to the transaction code OB13 to review the posting key configuration.
- Ensure that the posting key you are using is correctly configured for the account type you are trying to post to.
Verify Account Type:
- Check the account type associated with the account you are trying to post to. Ensure that it is compatible with the posting key being used.
Review Company Code Settings:
- Use transaction code OBY6 to check the settings for the company code. Ensure that the account type and posting key combinations are allowed.
Consult Documentation:
- Review SAP documentation or consult with your SAP FI consultant to understand the specific restrictions for the posting key and account type in your system.
Test with Different Combinations:
- If possible, try using a different posting key or account type to see if the transaction can be processed successfully.
Check User Authorizations:
- Ensure that the user performing the transaction has the necessary authorizations to use the specified posting key and account type.
Related Information:
If the issue persists after checking the above points, it may be necessary to involve your SAP support team or a consultant for further investigation.
Get instant SAP help. Start your 7-day free trial now.
FZ335
Vendor & & is already contained in proposal & &
What causes this issue? The specified payment proposal already contains customer/vendor items. To avoid overlaps, items from this account cannot be t...
FZ334
Customer & & is already contained in proposal & &
What causes this issue? The specified payment proposal already contains customer/vendor items. To avoid overlaps, items from this account cannot be t...
FZ337
Job was not scheduled with the transaction defined for it
What causes this issue? The job for the payment proposal or the payment run was not scheduled with the transaction for automatic payments, but rather...
FZ338
Exchange rate from & to & not maintained at posting date
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.