How To Fix FI_E336 - Starting at &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FI_E - Message Class for FM English Developers

• Message number: 336

• Message text: Starting at &1

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 FI_E336 - Starting at &1 ?

  The SAP error message FI_E336, which states "Starting at &1," typically relates to issues in the Financial Accounting (FI) module, particularly concerning document processing or posting. This error can occur due to various reasons, including configuration issues, missing data, or incorrect settings in the financial documents.
  Possible Causes:
  
  Missing or Incorrect Configuration: The error may arise if the configuration for the financial document types or posting periods is not set up correctly.
  Document Type Issues: The document type being used may not be allowed for the transaction you are trying to perform.
  Posting Periods: The posting period may be closed or not open for the transaction date.
  Missing Master Data: Required master data (like vendor or customer accounts) may be missing or incorrectly set up.
  Authorization Issues: The user may not have the necessary authorizations to perform the transaction.
  
  Solutions:
  
  Check Configuration: Review the configuration settings for the relevant document types and ensure they are correctly set up in the system.
  Open Posting Periods: Verify that the posting period for the transaction date is open. You can do this by checking the transaction code OB52.
  Review Document Type: Ensure that the document type you are using is appropriate for the transaction and is allowed for the posting.
  Validate Master Data: Check if all required master data is available and correctly configured. This includes vendor, customer, and general ledger accounts.
  User Authorizations: Ensure that the user has the necessary authorizations to perform the transaction. This can be checked in the user roles and profiles.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like OB52 (for posting periods), OBA7 (for document types), and SU01 (for user authorizations) to investigate and resolve the issue.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Logs and Traces: Review system logs and traces for more detailed error messages that can provide further insights into the issue.
  
  If the problem persists after checking these areas, it may be beneficial to consult with your SAP support team or refer to SAP documentation for more specific guidance related to your system configuration.