How To Fix GMCUSTOM009 - Full integration with CO mandatory. Check your entries.

GMCUSTOM009 - Overview

• Message type: E = Error

• Message class: GMCUSTOM - Customizable Messages for Grants Management

• Message number: 009

• Message text: Full integration with CO mandatory. Check your entries.

What causes this issue?

Grants Management (GM) is active for this company code. Grants
Management requires full integration with Controlling (CO); this means
that a general ledger (G/L) account or a cost element must be supplied
together with cost objects. The whole GM updating process and the
derivation of dimensions depend on this.

System Response

Processing stops.

How to fix this error?

In your posting line, specify either a G/L account or a cost element.
Alternatively, since this is a customizable message, you can change the
message control within GM. This would mean that you do not require
updating on grants or that your transaction simply does not take a cost
element or a GL account as a parameter.

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 GMCUSTOM009 - Full integration with CO mandatory. Check your entries. ?

  The SAP error message GMCUSTOM009: Full integration with CO mandatory. Check your entries typically occurs in the context of the integration between the General Ledger (GL) and Controlling (CO) modules in SAP. This error indicates that there is a configuration issue or missing settings that prevent the system from fully integrating financial data with controlling data.
  Causes:
  
  Missing Configuration: The integration settings between the Financial Accounting (FI) and Controlling (CO) modules may not be properly configured.
  Incorrect Account Assignment: The account assignment in the transaction may not be valid or may not correspond to the required CO settings.
  Missing CO Object: The transaction may require a CO object (like a cost center, internal order, etc.) that has not been specified or is not valid.
  Document Type Settings: The document type used in the transaction may not be set up for CO integration.
  Transaction Type: Certain transaction types may require specific CO integration settings that are not