How To Fix FAGL_MIG223 - Project must be used for production company codes

SAP Error Message - Details

• Message type: E = Error

• Message class: FAGL_MIG - Migration to New General Ledger Accounting

• Message number: 223

• Message text: Project must be used for production company codes

What causes this issue?

You are assigning a new ledger to a production company code without
using a project for the subsequent implementation of a ledger.

System Response

The assignment is not made.

How to fix this error?

To ensure data consistency in a company code that is already in use, you
first need to perform the complete maintenance of a project. This
contains the following steps:
Create a project for the introduction of an accounting principle. Follow
the steps in the Customizing activity <DS:SIMG.FINSVC_SIL_PROJ>Create
Project for Implementing Accounting Principle</>
As part of the project definition, define the new ledger (target
ledger).
Assign the relevant company codes and the source ledger to the project
and target ledger.
Since the company code to which the ledger is assigned is already in
productive use, you need to use the project to transfer the data of
source ledgers. Otherwise, a consistent dataset cannot be guaranteed in
the new ledger.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FAGL_MIG223 - Project must be used for production company codes ?

  The SAP error message FAGL_MIG223 indicates that a project must be used for production company codes during the migration process to the new General Ledger (G/L) accounting. This error typically arises when you are trying to execute a migration or a related process without having the necessary project settings in place for the company codes that are designated for production.
  Cause:
  
  Missing Project Assignment: The company code you are working with is not assigned to a project that is set up for production use.
  Incorrect Configuration: The configuration settings for the migration project may not be correctly set up to include the relevant company codes.
  Development vs. Production Environment: You might be trying to run a migration in a development environment instead of a production environment.
  
  Solution:
  
  
  Check Project Assignment:
  
  Go to the transaction code SCC4 to check the client settings and ensure that the company code is assigned to the correct project.
  Ensure that the project is marked for production use.
  
  
  
  Review Migration Project Settings:
  
  Use transaction FAGL_MIG to review the settings of your migration project.
  Ensure that the company codes you are working with are included in the project and that the project is activated.
  
  
  
  Adjust Configuration:
  
  If the project is not set up correctly, you may need to create or adjust the project settings to include the necessary company codes.
  Ensure that all required parameters and settings are correctly configured for the migration.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the migration process to ensure that all prerequisites are met.
  
  
  
  Testing in Development:
  
  If you are in a development environment, ensure that you are testing the migration in a way that reflects the production environment settings.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FAGL_MIG for migration and SCC4 for client settings.
  SAP Notes: Check for any SAP Notes related to FAGL_MIG223 for additional insights or patches that may address the issue.
  Migration Process: Understand the overall migration process to the new G/L, including prerequisites and steps involved.
  
  By following these steps, you should be able to resolve the FAGL_MIG223 error and successfully proceed with your migration activities.