How To Fix 1G355 - No postings generated

SAP Error Message - Details

• Message type: E = Error

• Message class: 1G - BKK: Konditionen

• Message number: 355

• Message text: No postings generated

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 1G355 - No postings generated ?

  The SAP error message 1G355: No postings generated typically occurs during the execution of a transaction or process that is expected to generate accounting entries or postings, but for some reason, no entries were created. This can happen in various contexts, such as during the execution of a financial transaction, a closing process, or a data upload.
  Causes:
  
  Missing Data: Required fields or data may be missing in the transaction or document being processed.
  Incorrect Configuration: The configuration settings for the relevant module (e.g., Financial Accounting, Controlling) may not be set up correctly.
  Posting Period Issues: The posting period may be closed or not open for the transaction type being processed.
  Document Type Issues: The document type used may not be configured to allow postings.
  Validation Errors: There may be validation rules that prevent the posting from being generated.
  Account Determination Issues: The system may not be able to determine the correct accounts for the transaction.
  Authorization Issues: The user may not have the necessary authorizations to perform the posting.
  
  Solutions:
  
  Check Required Fields: Ensure that all mandatory fields are filled in the transaction or document.
  Review Configuration: Verify the configuration settings in the relevant modules to ensure they are set up correctly.
  Check Posting Period: Confirm that the posting period is open for the transaction type you are trying to process.
  Review Document Type Settings: Ensure that the document type being used is configured to allow postings.
  Examine Validation Rules: Check for any validation rules that may be preventing the posting from being generated.
  Account Determination: Review the account determination settings to ensure that the system can find the correct accounts for the transaction.
  Authorization Check: Ensure that the user has the necessary authorizations to perform the posting.
  
  Related Information:
  
  Transaction Codes: Depending on the context, you may need to use specific transaction codes to check configurations or data (e.g., OB52 for posting periods, OBA7 for document types).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Debugging: If the issue persists, consider debugging the process to identify where the failure occurs.
  Consult Documentation: Review SAP documentation or help files related to the specific module you are working with for additional guidance.
  
  If the problem continues after checking these areas, it may be beneficial to consult with your SAP support team or a functional consultant who can provide more specific assistance based on your system's configuration and the context of the error.