How To Fix COIS899 - Conversion of variants for PPIO_ENTRY: &1 successful, &2 with errors

COIS899 - Overview

• Message type: E = Error

• Message class: COIS - Messages for the Order Information System

• Message number: 899

• Message text: Conversion of variants for PPIO_ENTRY: &1 successful, &2 with errors

What causes this issue?

Selection screen variants have been converted for report PPIO_ENTRY:
&V1& variants converted successfully.
&V2& variants could not be converted since an error occurred during
conversion.
Conversion is not necessary for &V3& variants.
&V4& temporary variants deleted.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Reason for conversion
For release 4.70 a parameter on the selection screen for the PPIO_ENTRY
report has been changed so that all old variants for this selection
screen must be converted. This also affects the standard variants SAP
&COOIS, SAP&HVOM, SAP&RELEASE, SAP&PRINT and SAP &AVAILCHK, if they are
imported from release 4.6B or 4.6C. If these old variants are imported
and not converted, a program termination (dump) will occur when the
following transactions are called: COOIS, COHV, CO04N, CO05N and COMAC.

How to fix this error?

Errors during conversion do not have an influence on an upgrade
process.
Incorrect vairants can be converted at any time using the
PPIO_ENTRY_XPRA01 report. To do this, start the PPIO_ENTRY_XPRA01
conversion report again in the foreground and you will obtain an
extended error log.
The variants delivered (and created) for release 4.70 must not be
converted.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message COIS899 - Conversion of variants for PPIO_ENTRY: &1 successful, &2 with errors ?

  The SAP error message COIS899 indicates that there was an issue during the conversion of variants for a PPIO (Process Industry Order) entry. The message specifies that the conversion was successful for a certain number of entries, but there were errors for others. Here’s a breakdown of the cause, potential solutions, and related information:
  
  Cause:
  
  Data Inconsistency: The error often arises due to inconsistencies or missing data in the variants being processed. This could be due to incorrect or incomplete entries in the master data or transaction data.
  
  Configuration Issues: There may be issues with the configuration of the PPIO or the variants themselves, such as incorrect settings in the variant configuration profiles.
  Technical Errors: There could be technical issues, such as problems with the underlying database or issues in the ABAP code that processes the variants.
  
  
  Solution:
  
  Check the Error Log: Review the detailed error log to identify which specific entries failed during the conversion.