How To Fix FAGL_REORGANIZATION804 - Reorganization period is already open for company code &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FAGL_REORGANIZATION - Reorganization

• Message number: 804

• Message text: Reorganization period is already open for company code &1

What causes this issue?

You want to create a new <DS:DE.FAGL_R_PLAN>reorganization plan</> or
make changes to the general or specific restrictions. However,
reorganization period &V2&/&V3& is already open for company code &V1&.
Note:
In the case of a posting period that always needs to be open, there must
be a minimum entry (account type <ZH>+</>) in the <LS>Financial
Accounting Global Settings</> under <LS>Open and Close Posting Periods
</>. This minimum entry was found for company code &V1& in period &V2&/
&V3&.
Example:
A reorganization plan has the reorganization date 06/01/2009.
Internal order O1 uses profit center PCB. Postings have already been
made to this internal order in period 6.
Profit center PCB is now added to the reorganization plan: In the
assignment table, a new line is entered with old profit center PCB and
new profit center PCC. As a result, internal order O1 becomes relevant
for the reorganization.
New postings to O1 in period 6 are made automatically to target profit
center PCC.
However, internal order O1 already has postings that were assigned for
profit center PCB.

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?

Procedure for System Administrators

INCLUDE FAGL_MESSAGE_CONTROL OBJECT DOKU ID TX

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FAGL_REORGANIZATION804 - Reorganization period is already open for company code &1 ?

  The SAP error message FAGL_REORGANIZATION804 indicates that a reorganization period is already open for the specified company code. This error typically occurs when you attempt to perform a reorganization process in the General Ledger (G/L) accounting module, but the system detects that there is already an active reorganization period for that company code.
  Cause:
  
  Open Reorganization Period: The primary cause of this error is that the reorganization period for the specified company code is already open. This means that the system is preventing you from opening another reorganization period until the current one is closed.
  Configuration Issues: There may be configuration settings in the SAP system that allow multiple reorganization periods to be opened, which can lead to conflicts.
  User Error: The user may have inadvertently attempted to start a new reorganization process without closing the previous one.
  
  Solution:
  
  Check Open Periods: Verify the current open reorganization periods for the company code in question. You can do this by navigating to the relevant transaction in SAP (e.g., transaction code OB52 for period control) and checking the status of the reorganization periods.
  Close Existing Period: If there is an open reorganization period that is no longer needed, you can close it. This typically involves using the appropriate transaction to close the period.
  Consult Documentation: Review the SAP documentation or help files related to the reorganization process to ensure that you are following the correct procedures.
  Contact SAP Support: If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting SAP Notes for any known issues or patches related to this error message.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FAGL_REORGANIZE for reorganization processes and OB52 for managing periods.
  SAP Notes: Check SAP Notes for any updates or specific instructions related to the FAGL_REORGANIZATION804 error.
  User Roles and Permissions: Ensure that the user attempting to perform the reorganization has the necessary permissions to open or close periods.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.