Do you have any question about this error?
Message type: E = Error
Message class: MIGRATE_PRICING_MSG - Pricing Migration Messages
Message number: 095
Message text: Cannot rename column KONV-MANDT. See long text.
The column KONV-MANDT cannot be renamed to KONV-CLIENT, since it is part
of a partition specification for table KONV, which is not supported by
your HANA database system version. This operation is supported starting
on HANA version 1.00.112.03.
As part of the KONV migration to PRCD_ELEMENTS, KONV-MANDT needs to be
renamed to KONV-CLIENT. As this cannot be performed in the current
system, this step is skipped. As a result, PRCD_ELEMENTS will end up
with a column named MANDT instead of a column named CLIENT.
After the migration, the column PRCD_ELEMENTS-MANDT needs to be renamed
to PRCD_ELEMENTS-CLIENT. For that, you need to re-partition
PRCD_ELEMENTS in a way that its partition specification doesn't involve
column MANDT. Then, you can rename column MANDT to CLIENT.
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.
MIGRATE_PRICING_MSG095
- Cannot rename column KONV-MANDT. See long text. ?The SAP error message MIGRATE_PRICING_MSG095 indicates that there is an issue with renaming the column
KONV-MANDT
during a migration or upgrade process. This typically occurs when there are constraints or dependencies that prevent the renaming of the column in the database.Cause:
- Database Constraints: The column
KONV-MANDT
may have constraints such as foreign key relationships, indexes, or other dependencies that prevent it from being renamed.- Data Consistency: The system may be enforcing data consistency rules that require the column to remain unchanged.
- Migration Process: The migration process may be attempting to rename columns as part of a data model change, but the existing structure does not allow for this change.
Solution:
- Check Dependencies: Review the database schema to identify any dependencies related to the
KONV-MANDT
column. This includes checking for foreign keys, indexes, and any other database objects that reference this column.- Remove Constraints: If possible, temporarily remove any constraints or dependencies that are preventing the rename operation. Be cautious with this approach, as it may affect data integrity.
- Consult Documentation: Refer to the SAP documentation or notes related to the migration process you are performing. There may be specific instructions or prerequisites that need to be followed.
- Use Transaction Codes: Utilize transaction codes like SE11 (Data Dictionary) to analyze the structure of the
KONV
table and understand its relationships.- Contact SAP Support: If the issue persists, consider reaching out to SAP support for assistance. They may provide specific guidance based on the version of SAP you are using and the context of the migration.
Related Information:
Always ensure that you have a backup of your data and a rollback plan before making any changes to the database schema or constraints.
Get instant SAP help. Start your 7-day free trial now.
MIGRATE_PRICING_MSG094
Data in custom field KONV-&1 no longer exists in PRCD_ELEMENTS
What causes this issue? Data has been found in the custom field KONV-&V1& but the field does not exist in PRCD_ELEMENTS.System Response Data...
MIGRATE_PRICING_MSG093
Data in deprecated field KONV-&1 no longer exists in PRCD_ELEMENTS
What causes this issue? Data has been found in the deprecated field KONV-&V1& but the field does not exist in PRCD_ELEMENTS.System Response ...
MIGRATE_PRICING_MSG100
Exiting as all rows of PRCD_ELEMENTS have already been processed
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MIGRATE_PRICING_MSG103
List of log messages from the last execution
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.