Do you have any question about this error?
Message type: E = Error
Message class: PRC_MIG_TRANSL_MSG - KONV migration translatable messages
Message number: 195
Message text: Not all rows in PRCD_ELEMENTS were processed. See long text.
Updating data in the field WAERK in table PRCD_ELEMENTS (formerly KONV)
was unsuccessful. After the SD Pricing data migration WAERK defaults to
a value of '2', this value is updated to the correct values found in the
SD document tables: VBAK, LIKP, VBRK, EKKO, EKBE, ESLH, RBKP and VFKP.
Not all rows in PRCD_ELEMENTS were updated. As a result, some rows of
PRCD_ELEMENTS don't have a corresponding row in a known SD document
table.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
If you have an additional type of SD document contained in a
non-standard table, or have added extra rows to KONV that don't
correspond to an SD document, you need to do the following:
1. Manually update field PRCD_ELEMENTS-WAERK where you see the value '2'
to correspond to the correct currency type found in your custom SD
document table.
2. If the currency type (WAERK) has anything other than 2 digits after
the decimal place, you need to update the field KAWRT.
If you do not use any non-standard tables and did not add any extra rows
to KONV, then something unexpected went wrong with the data migration
post-processing program. You will need to submit an SAP ticket with
short text that includes the keyword "PRC_MIG_POST" (Note: use the
component SD-BF-PR).
Error message extract from SAP system. Copyright SAP SE.
PRC_MIG_TRANSL_MSG195
- Not all rows in PRCD_ELEMENTS were processed. See long text. ?The SAP error message PRC_MIG_TRANSL_MSG195 indicates that not all rows in the table
PRCD_ELEMENTS
were processed during a migration or data transfer operation. This error typically occurs in the context of migrating pricing conditions or related data in SAP systems, particularly when using the SAP S/4HANA Migration Cockpit or similar tools.Cause:
- Data Inconsistencies: There may be inconsistencies or errors in the data within the
PRCD_ELEMENTS
table that prevent successful processing of all rows.- Missing Dependencies: Some rows may depend on other data that is missing or not properly configured, leading to incomplete processing.
- Configuration Issues: Incorrect configuration settings in the migration tool or the source system can lead to incomplete data processing.
- Data Format Issues: The data format or structure may not match the expected format required by the migration process.
Solution:
- Check Long Text: Review the long text associated with the error message for specific details about which rows were not processed and why.
- Data Validation: Validate the data in the
PRCD_ELEMENTS
table for any inconsistencies or errors. Look for missing or incorrect entries that could be causing the issue.- Review Dependencies: Ensure that all necessary dependencies for the rows in
PRCD_ELEMENTS
are present and correctly configured.- Log Analysis: Check the migration logs for detailed error messages or warnings that can provide insights into the specific rows that failed to process.
- Re-run Migration: After addressing any identified issues, re-run the migration process to see if the problem persists.
- Consult Documentation: Refer to SAP documentation or notes related to the migration process for any specific guidelines or troubleshooting steps.
- SAP Support: If the issue cannot be resolved, consider reaching out to SAP support for assistance, providing them with the error details and any relevant logs.
Related Information:
SE11
(Data Dictionary) to inspect the PRCD_ELEMENTS
table and SLG1
(Application Log) to check logs related to the migration.By following these steps, you should be able to identify the cause of the error and implement a solution to ensure all rows in the PRCD_ELEMENTS
table are processed successfully.
Get instant SAP help. Start your 7-day free trial now.
PRC_MIG_TRANSL_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...
PRC_MIG_TRANSL_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...
PRC_MIG_TRANSL_MSG197
There was an SQL error in joining table &1. See long text.
What causes this issue? An error occurred when updating values in the field WAERK in table PRCD_ELEMENTS (formerly KONV). WAERK defaults to a value o...
PRC_MIG_TRANSL_MSG198
Post-processing &1, total number of rows: &2
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.