Message type: E = Error
Message class: CFD_REGISTRY_CHECK - Custom Fields: Messages for Registry Check
Message number: 274
Message text: Migrated Draft 2.0 View &1 must keep association to Draft Include View &2
CDS View <(>&<)>1 was draft 1.0 extensibility enabled before and was
migrated to draft 2.0. The special situation is that two or more
business contexts exists which shared the same draft 1.0 extension
include view to access the draft persistency. But the business contexts
had their own extension include view for the active persistency. So, the
draft extension include view contained all extension fields of both
business contexts but the active extension include views contained only
the extension fields belonging to their business context.
In standard cases the draft extension association must be defined in the
same way as the active extension association for the draft 2.0
migration. This keeps the already generated CDS extensions for the
extended view syntax stable. In this case that is not possible because
neither of the active extension include view contains all fields.
The solution is to keep the draft association <(>&<)>3 with the draft
extension include view <(>&<)>2 as target as it was defined before the
migration, even if draft data is not read from there anymore.
Please make sure the formerly draft 1.0 association <(>&<)>3 to draft
extension include view <(>&<)>2 is still defined in your CDS View
<(>&<)>1.
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.
CFD_REGISTRY_CHECK274
- Migrated Draft 2.0 View &1 must keep association to Draft Include View &2 ?The SAP error message CFD_REGISTRY_CHECK274 typically occurs in the context of SAP Fiori or SAP S/4HANA applications when there is an issue with the association between a migrated draft view and its corresponding draft include view. This error indicates that the system expects a specific relationship between these views, which has not been maintained correctly during the migration process.
Cause: Migration Issues: The error often arises during the migration of draft views from an older version to a newer version (e.g., from Draft 1.0 to Draft 2.0). If the association between the draft view and the draft include view is not properly established, this error will occur. Configuration Errors: There may be configuration issues in the application that prevent the correct association from being recognized. Inconsistent Metadata: The metadata definitions for the draft views may be inconsistent or incomplete, leading to the system being unable to validate the relationship.
Solution: Check Associations: Verify the associations between
Get instant SAP help. Sign up for our Free Essentials Plan.
CFD_REGISTRY_CHECK273
Business Object Type &1 and Node Type &2 can only be entered once
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CFD_REGISTRY_CHECK272
Business Object Node Type &1 does not exist for Business Object Type &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CFD_REGISTRY_CHECK275
Chosen View Type does not support to add fields automatically
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CFD_REGISTRY_CHECK276
Functionality "Add Field automatically" is not allowed for Roles
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.