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

G5852 - Overview

• 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 &

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:
  
  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.
  Period Locking: The posting period may be locked for the specified company code, preventing any further postings.
  
  Configuration Issues: There may be configuration issues in the financial settings that prevent the system from allowing postings in the specified period.
  
  
  Solution:
  
  
  Check Period Status:
  
  Go to the transaction code OB52 (Change Posting Periods) and check the status of the posting period for the specified