How To Fix 8N1104 - Journal has already been printed for posting date &


SAP Error Message - Details

  • Message type: E = Error

  • Message class: 8N1 - Messages for Accounting (Greek Localization)

  • Message number: 104

  • Message text: Journal has already been printed for posting date &

  • 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 8N1104 - Journal has already been printed for posting date & ?

    The SAP error message 8N1104 indicates that a journal entry has already been printed for a specific posting date. This typically occurs in the context of financial accounting or controlling when trying to print a journal that has already been processed.

    Cause:

    1. Duplicate Print Attempt: The most common cause is that the journal entry has already been printed, and the system prevents a second print to avoid duplication.
    2. Posting Date Conflict: The error may also arise if there is an attempt to print a journal for a posting date that has already been finalized or closed.
    3. System Configuration: There may be specific configurations in the SAP system that restrict printing of journals once they have been printed.

    Solution:

    1. Check Print Status: Verify if the journal has indeed been printed. You can do this by checking the print logs or the journal entry history.
    2. Reprint Option: If you need to reprint the journal, you may need to reverse the print status or use a specific transaction code that allows reprinting. This often requires appropriate authorizations.
    3. Consult Documentation: Review the SAP documentation or help files related to journal printing to understand the specific steps for your version of SAP.
    4. Contact Support: If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting with an SAP expert who can provide guidance based on your system configuration.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as FB03 (Display Document) or SPL1 (Display Print Log) to check the status of the journal.
    • User Authorizations: Ensure that you have the necessary authorizations to print or reprint journal entries.
    • System Settings: Review the configuration settings in the SAP system related to journal printing to understand any restrictions that may be in place.

    By following these steps, you should be able to address the error message and proceed with your journal printing tasks.

    • 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