How To Fix FINS_REV_REC_CUST100 - G/L account &1 (&2) is not assigned to an expense type

FINS_REV_REC_CUST100 - Overview

• Message type: E = Error

• Message class: FINS_REV_REC_CUST - Event-Based Rev. Rec.: Customizing

• Message number: 100

• Message text: G/L account &1 (&2) is not assigned to an expense type

What causes this issue?

You are posting to a CPM customer project, but the G/L expense account
is not assigned to an expense type of the CPM application.

System Response

The posting is prohibited by the system to avoid issues in subsequent
processes, especially plan/actual comparison and determination of the
POC (percentage of completion).
With a fixed price contract, the POC is the basis for revenue
recognition. If the G/L expense account is not assigned to an expense
type, the event-based revenue recognition posting fails.

How to fix this error?

Assign account &V1& in chart of accounts &V2& to an expense ID or use a
different account for the posting.
To maintain the assignment, use the app 'Maintain Your Solution' and
choose 'Configure Your Solution'. The configuration item is 'Customer
and Internal Project Management'.
Proceed as described in the configuration help for configuration step
'Define Resources'.

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.

FINS_REV_REC_CUST100 - Details

• The SAP error message FINS_REV_REC_CUST100 indicates that a General Ledger (G/L) account is not assigned to an expense type in the system. This error typically arises during the processing of revenue recognition or when trying to post transactions that require a specific configuration of G/L accounts.
  
  Cause:
  
  Missing Configuration: The G/L account specified in the error message is not linked to an expense type in the system configuration. This can happen if the account was newly created or if there were changes in the account settings.
  Incorrect Account Usage: The G/L account may not be intended for the type of transaction being processed, leading to the system not recognizing it as valid for the operation.
  Customizing Settings: The settings in the Financial Accounting (FI) module may not be properly configured to recognize the G/L account for the intended purpose.
  
  
  Solution:
  
  
  Check G/L Account Configuration:
  
  Go to the transaction code OBYC (Automatic Postings) in SAP.
  Look for the relevant