How To Fix REEXFI222 - Cost collector is closed to posting

SAP Error Message - Details

• Message type: E = Error

• Message class: REEXFI - Messages for Interface to FI

• Message number: 222

• Message text: Cost collector is closed to posting

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 REEXFI222 - Cost collector is closed to posting ?

  The SAP error message REEXFI222 indicates that a cost collector is closed to posting. This typically occurs in the context of controlling (CO) and project systems (PS) when you attempt to post costs to a cost collector that has been closed for further postings. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Cost Collector Status: The cost collector has been set to a status that prevents further postings. This can happen if the cost collector has been closed at the end of a period or project.
  Period Closing: The posting period may have been closed in the controlling area, preventing any further postings to cost collectors associated with that period.
  Project Closure: If the cost collector is linked to a project that has been closed, it will also prevent any further postings.
  
  Solutions:
  
  
  Check Cost Collector Status:
  
  Navigate to the cost collector in SAP and check its status. If it is closed, you may need to reopen it if appropriate.
  Use transaction codes like CJI3 (Project Actual Line Items) or COSS (Cost Totals for Internal Orders) to review the status.
  
  
  
  Open Posting Period:
  
  If the posting period is closed, you can open it again if your organization’s policies allow it. This can be done through transaction code OB52 (Change View "Periods": Overview).
  Ensure that the period you are trying to post to is open for the relevant company code and controlling area.
  
  
  
  Reopen Project:
  
  If the cost collector is linked to a project that has been closed, you may need to reopen the project if it is necessary to post additional costs. This can be done through transaction code CJ20N (Project Builder).
  
  
  
  Consult with Finance Team:
  
  If you are unsure about the implications of reopening a cost collector or period, consult with your finance or controlling team to ensure compliance with accounting policies.
  
  
  
  Use Alternative Cost Collectors:
  
  If the cost collector cannot be reopened, consider using an alternative cost collector that is open for postings.
  
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  CJI3: Display Project Actual Line Items
  COSS: Display Cost Totals for Internal Orders
  CJ20N: Project Builder
  OB52: Change View "Periods": Overview
  
  
  
  Documentation: Review SAP documentation or help files related to cost accounting and project systems for more detailed procedures on managing cost collectors and posting periods.
  
  
  User Roles: Ensure that you have the necessary authorizations to make changes to cost collectors, posting periods, or project statuses.
  
  
  By following these steps, you should be able to address the REEXFI222 error and understand the underlying issues related to cost collector postings in SAP.