How To Fix G5852 - CORRECT STATUS (1) in T8JEV for Company Code &, Year &, Period &


SAP Error Message - Details

  • Message type: E = Error

  • Message class: G5 - IS-Oil /Joint Venture/ Material transfer pricing

  • Message number: 852

  • Message text: CORRECT STATUS (1) in T8JEV for Company Code &, Year &, Period &

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

    CORRECT STATUS (1) in T8JEV for Company Code &, Year &,
    Period &
    60000002
    *& There are several status when Cutback was run.
    *& 1 Complete
    *& 2 Incomplete
    *& 3 Failed
    *& Only if the status is 1 the billing transactions gj12,gj13
    should
    *& process the data from Ledger 4A, 4F and 4B, 4D.
    *& If using multiple company code and different status then there
    is
    *& no error message to stop the complete process but in the error
    pop up
    *& where you can see the company code which have status 2 or 3.
    *& If processing one company code which has an incorrect status
    the
    *& program will exit.
    60000003
    Please see Event Table T8JEV Process CBIM for company code, year,
    period. The cutback run correctly for this company code, the billing
    process can run.

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message G5852 - CORRECT STATUS (1) in T8JEV for Company Code &, Year &, Period & ?

    The SAP error message G5852 "CORRECT STATUS (1)" typically occurs in the context of financial postings, particularly when dealing with the closing of periods in the SAP system. This error is often related to the status of the company code, fiscal year, and posting period you are trying to work with.

    Cause:

    1. Incorrect Status: The error indicates that the status of the specified company code, fiscal year, and period is not set correctly for the operation you are trying to perform. This could mean that the period is closed or not open for posting.
    2. Period Locking: The posting period may be locked for the specified company code, preventing any further postings.
    3. Configuration Issues: There may be configuration issues in the financial settings that prevent the system from allowing postings in the specified period.

    Solution:

    1. Check Period Status:

      • Go to the transaction code OB52 (Change Posting Periods) and check the status of the posting period for the specified company code and fiscal year. Ensure that the period is open for posting.
      • If the period is closed, you may need to open it temporarily to allow the necessary postings.
    2. Review Company Code Settings:

      • Ensure that the company code settings are correctly configured to allow postings in the desired period. This includes checking the fiscal year variant and the associated periods.
    3. Consult with Finance Team:

      • If you are unsure about changing the status of the period, consult with your finance team or the person responsible for financial operations in your organization. They may have specific policies regarding period openings and closings.
    4. Transaction Codes:

      • Use transaction codes like T8JEV to check the status of the periods and make necessary adjustments.
      • You can also use OB52 to adjust the posting periods if needed.
    5. Error Logs:

      • Check the error logs for more detailed information about the error. This can provide additional context that may help in resolving the issue.

    Related Information:

    • Fiscal Year Variant: Understand the fiscal year variant assigned to the company code, as it defines the structure of the fiscal year and the posting periods.
    • Posting Periods: Familiarize yourself with how posting periods are managed in SAP, including the concept of open and closed periods.
    • SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on handling posting periods.

    If the issue persists after following these steps, it may be necessary to involve your SAP support team or consult SAP documentation for further troubleshooting.

    • 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's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker