1I143 - No more posting with DI to account &1 /&2 possible as of go-live date

Start a new search

SAP Error Message - Details

  • Message type: E = Error

  • Message class: 1I - BCA: General Ledger Integration

  • Message number: 143

  • Message text: No more posting with DI to account &1 /&2 possible as of go-live date

  • Show details Hide details
  • What causes this issue?

    Account &v2& in bank area &v1& has &v3& as go-live date. The item to be
    posted came from direct input and is to be posted on &v4&.
    This is not possible, as only legacy data can be transferred by means
    of direct input. As of the go-live date, postings can only be made
    using the BAPI interfaces or the user interface.

    System Response

    The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

    How to fix this error?


    Error message extract from SAP system. Copyright SAP SE.


AnswerBot

  • What is the cause and solution for SAP error message 1I143 - No more posting with DI to account &1 /&2 possible as of go-live date ?

    The SAP error message 1I143 indicates that no further postings can be made to a specific account due to the go-live date being reached. This typically occurs in the context of financial accounting and is related to the closing of periods or the restriction of postings to certain accounts after a specific date.

    Cause:

    1. Go-Live Date Reached: The error is triggered when the system has been configured to prevent postings to certain accounts after a defined go-live date. This is often part of the financial closing process to ensure that no changes are made to historical data.
    2. Account Configuration: The account in question may have been set up with restrictions that prevent postings after a certain date.
    3. Period Closing: The financial period may have been closed, which restricts any further postings to that period.

    Solution:

    1. Check Configuration: Review the configuration settings for the account in question. You may need to check the settings in the Financial Accounting (FI) module to see if there are restrictions on postings after the go-live date.
    2. Open Posting Periods: If necessary, you can open the posting periods for the relevant account. This can be done through the transaction code OB52 (Change View "Posting Periods": Overview) where you can adjust the allowed posting periods.
    3. Adjust Go-Live Date: If the go-live date was set incorrectly, you may need to adjust it, but this should be done with caution and typically requires administrative privileges.
    4. Consult with Finance Team: If you are unsure about making changes, consult with your finance team or SAP administrator to ensure that any adjustments align with your organization's financial policies.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as:
      • OB52: For managing posting periods.
      • FS00: For account master data maintenance.
    • Documentation: Review SAP documentation related to financial closing processes and posting period management.
    • User Roles: Ensure that you have the appropriate user roles and permissions to make changes to financial settings in SAP.

    Best Practices:

    • Always back up your configuration settings before making changes.
    • Document any changes made for future reference and compliance.
    • Communicate with relevant stakeholders before making adjustments to financial settings.

    If the issue persists after following these steps, it may be necessary to consult SAP support or your internal IT team for further assistance.

  • AnswerBot is an artificial intelligence solution provided by tomco.ai.
    Disclaimer

Related SAP Error Messages

Click the links below to see the following related messages:


SAP messages fall into 3 different categories: Error messages (message type = E), Warnings (W) or Informational (I) messages.

An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.

Click on this link to search all SAP messages.