How To Fix ACEPS068 - No documents created in Accounting


SAP Error Message - Details

  • Message type: E = Error

  • Message class: ACEPS - Fehlermeldungen Abgrenzungsbuchungen

  • Message number: 068

  • Message text: No documents created in Accounting

  • Show details Hide details


  • 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 ACEPS068 - No documents created in Accounting ?

    The SAP error message ACEPS068 ("No documents created in Accounting") typically occurs during the posting process in the SAP system, particularly when dealing with financial transactions. This error indicates that the system did not generate any accounting documents for the transaction you attempted to post. Here are some common causes, solutions, and related information for this error:

    Causes:

    1. Missing Configuration: The accounting configuration for the specific transaction type may not be set up correctly in the system.
    2. Posting Period Issues: The posting period may be closed, preventing any new accounting entries from being created.
    3. Document Type Issues: The document type used for the transaction may not be configured to create accounting documents.
    4. Transaction Type Not Supported: The specific transaction type may not be supported for accounting document creation.
    5. Error in Master Data: Issues with master data (e.g., vendor, customer, or material master) can lead to the failure of document creation.
    6. Missing Account Assignment: If the transaction lacks the necessary account assignment (e.g., cost center, internal order), it may not create an accounting document.
    7. Authorization Issues: The user may not have the necessary authorizations to create accounting documents.

    Solutions:

    1. Check Configuration: Review the configuration settings for the relevant transaction type in the Financial Accounting (FI) module. Ensure that the necessary settings are in place to allow for document creation.
    2. Verify Posting Period: Check the posting period settings in the system. If the period is closed, you may need to open it or post the transaction in an open period.
    3. Review Document Type Settings: Ensure that the document type used for the transaction is configured to create accounting documents.
    4. Validate Transaction Type: Confirm that the transaction type you are using is supported for accounting document creation.
    5. Check Master Data: Review the relevant master data for any inconsistencies or missing information that could prevent document creation.
    6. Ensure Account Assignment: Make sure that all necessary account assignments are provided in the transaction.
    7. Authorization Check: Verify that the user has the appropriate authorizations to perform the transaction and create accounting documents.

    Related Information:

    • Transaction Codes: You may want to use transaction codes like FB03 (Display Document) or FB02 (Change Document) to check existing documents and their statuses.
    • Error Logs: Check the application log (transaction code SLG1) for more detailed error messages that can provide additional context for the issue.
    • SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to this error message.
    • Consult Documentation: Review SAP documentation or help files related to the specific module you are working with for additional guidance.

    If the issue persists after checking these areas, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in the relevant module.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant