Do you have any question about this error?
Message type: E = Error
Message class: CNV_20100 - Messageclass for chart of account conversion
Message number: 436
Message text: Copy scenario: Indicator for reports (target CoA) is set
If the <ZK>Copy Rows</> indicator is set, the source chart of accounts
remains unchanged in the system, while the target chart of accounts is
created and changed as specified.
To accomplish this, all tables that have the chart of accounts as well
as sets in their keys (SETHEADER, SETHEADERT, SETLEAF, SETLINET, SETNODE
RWSHEADER, RWSLINE) must be copied (and entries for the target chart of
accounts must be changed).
These sets can be used in
Reporting (Report Painter, Report Writer)
Allocations (assessment, distribution, ...)
Due to the complexity of reports and allocations, it is not possible to
re-create them automatically using the copied sets.
The indicator for reports (target chart of accounts) was set.
Because this indicator was set, all tables in which sets are used will
be converted anyway.
&ADDITIONAL_HINTS&
Note that you can no longer use the reports that are based on the old
chart of accounts data.
Error message extract from SAP system. Copyright SAP SE.
CNV_20100436
- Copy scenario: Indicator for reports (target CoA) is set ?The SAP error message CNV_20100436 typically occurs during the data migration process, particularly when using the SAP S/4HANA Migration Cockpit or similar tools. This error indicates that there is an issue with the configuration of the target Chart of Accounts (CoA) in relation to the copy scenario being executed.
Cause:
The error message "Indicator for reports (target CoA) is set" suggests that the target Chart of Accounts has been configured to be used for reporting purposes, which may not be compatible with the current copy scenario. This can happen if:
- The target CoA is set as a "reporting" CoA, which may have specific restrictions or requirements.
- The source and target CoAs are not aligned in terms of their configuration or structure.
- There are inconsistencies in the mapping of accounts between the source and target CoAs.
Solution:
To resolve this error, you can take the following steps:
Check CoA Configuration: Review the configuration of the target Chart of Accounts in the SAP system. Ensure that it is set up correctly and that the reporting indicator is appropriate for the migration scenario you are executing.
Adjust Copy Scenario: If the target CoA is intended for reporting, consider using a different copy scenario that is compatible with reporting CoAs. Alternatively, you may need to adjust the settings of the target CoA to remove the reporting indicator if it is not necessary.
Mapping Validation: Ensure that the mapping between the source and target CoAs is correct. Check that all accounts in the source CoA have corresponding accounts in the target CoA.
Consult Documentation: Refer to the SAP documentation related to the migration process and the specific error message. This may provide additional insights or steps specific to your version of SAP.
SAP Support: If the issue persists, consider reaching out to SAP support for assistance. They can provide guidance based on the specific details of your system and migration scenario.
Related Information:
By following these steps, you should be able to address the CNV_20100436 error and proceed with your data migration successfully.
Get instant SAP help. Start your 7-day free trial now.
CNV_20100435
No priority was defined for target chart of accounts &2 (&1 -> &2)
What causes this issue? You would like to merge several charts of accounts into target chart of accounts &V2&. Some tables have only the char...
CNV_20100434
More than one country-specific CoA for CoA &1; old acct &2 not converted
What causes this issue? Chart of accounts &V1& is the operative chart of accounts for multiple company codes to which different country-speci...
CNV_20100437
Copy scenario: Indicator for reports (source CoA) is set
What causes this issue? If the <ZK>Copy Rows</> indicator is set, the source chart of accounts remains unchanged in the system, while the...
CNV_20100438
Validity period of &1 differs from &2 in controlling area &3 (CSKB-DATBI)
What causes this issue? According to the mapping table, you want to merge cost element &V1& and cost element &V2& in controlling area...
Click on this link to search all SAP messages.