How To Fix G3573 - Subitem &4 is not recordable

G3573 - Overview

• Message type: E = Error

• Message class: G3 - Messages for SAP Consolidation: Integration

• Message number: 573

• Message text: Subitem &4 is not recordable

What causes this issue?

The current data record should have been posted to
<DS:GLOS.subitem>subitem</> <ZH>&V4&</> for
<DS:GLOS.financial_statement_item>FS item</> <ZH>&V2&</> in
<DS:GLOS.consolidation_chart_of_accounts>consolidation chart of
accounts</> <ZH>&V1&</>, however, this was not possible because the
indicator <ZH>Block posting and entry</> is set for this subitem.

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?

Find out whether it makes sense for you to deactivate the indicator for
subitem <ZH>&V4&</> in subitem category <ZH>&V3&</>, and if possible,
change this setting in Consolidation Customizing.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message G3573 - Subitem &4 is not recordable ?

  The SAP error message G3573, which states "Subitem &4 is not recordable," typically occurs in the context of financial transactions, particularly when dealing with subitems in accounting documents. This error indicates that the specific subitem you are trying to use is not allowed to be recorded in the system for the transaction you are attempting to process.
  Causes:
  
  Subitem Configuration: The subitem may not be configured correctly in the system. It might be set up in a way that it cannot be used for certain types of postings.
  Posting Rules: The posting rules for the specific account or transaction type may not allow the use of that subitem.
  Document Type Restrictions: Certain document types may have restrictions on which subitems can be used.
  Missing Master Data: The master data for the subitem may be incomplete or missing, leading to it being deemed non-recordable.
  Authorization Issues: The user may not have the necessary authorizations to use that