How To Fix KE337 - ¡La carac. & se tuvo que cambiar de nombre! ¡Adapte la valoración!

SAP Error Message - Details

• Message type: E = Error

• Message class: KE -

• Message number: 337

• Message text: ¡La carac. & se tuvo que cambiar de nombre! ¡Adapte la valoración!

¿Qué causa este problema?

Characteristic &V1& had to be renamed due to a naming conflict in the
valuation tables. The new name is &V2&.
Characteristic &V1& is used in condition table A&V4& and access
sequence &V3& for valuation using conditions in CO-PA.

Respuesta del sistema

Valuation in CO-PA is no longer possible for this characteristic under
the former field name &V1&.

¿Cómo arreglar este error?

The valuation, i.e. the condition table A&V4& which uses this
characteristic, and access sequence &V3&, which accesses this condition
table, must be maintained for this characteristic under the field
name &V2&.

El sistema emite un mensaje de error y no le permitirá continuar con esta transacción hasta que se resuelva el error.

Do the following:
Create a new condition table for the characteristic in CO-PA
Customizing.
<DS:TRAN.KE4A>Proceed</>
Then use the ABAP Editor to create a program which reads the
condition records from the previous condition table A&V4& and enters
them in the new condition table.
<DS:TRAN.SE38>Proceed</>
Replace the old access sequence &V3& with a new access sequence
which accesses the new condition table.
<DS:TRAN.KE48>Proceed</>
Assign the new access sequence to the condition types which use
access sequence &V3&.
<DS:TRAN.KE47>Proceed</>
Carry out a test for the valuation.
Finally, delete the old condition table A&V4&.
Example:
You receive the message "Characteristic CUCLA needs to be renamed!
Adapt valuation accordingly!"
The long text tells you that condition table A610 and access sequence
ACUC need to be adapted, and that the new field name is RKE_CUCLA.
RESET N1
Proceed as follows:
Create condition table A610, which contains the characteristic CUCLA
(and perhaps others), again. Create a new condition table by
choosing the characteristic RKE_CUCLA (and any others used in A610)
from the field catalog. Generate the new condition table. The
system displays a message telling you that Table A687 has been
activated.
Next, copy the entries in Table A610 to the new Table A687. If you
look at the Tables A610 and A687 in the ABAP/4 Dictionary
(Transaction SE11), you should find the following structure, based
on our example:
Table A610 MANDT KAPPL KSCHL CUCLA DATBI DATAB KNUMH
Table A687 MANDT KAPPL KSCHL RKE_CUCLA DATBI DATAB KNUMH
A program for copying the entries might look like the following:
REPORT COPY_TAB.
TABLES: A610, A687.
SELECT * FROM A610 CLIENT SPECIFIED.
MOVE-CORRESPONDING A610 TO A687.
MOVE A610-CUCLA TO A687-RKE_CUCLA.
INSERT A687 CLIENT SPECIFIED.
ENDSELECT.
Access sequence ACUC used Table A610 up to now. Replace ACUC
with a new, equivalent access sequence ACU2, which accesses Table
A687.
Up to now the condition records were accessed using access sequence
ACUC for the conditions CT01 and CT02. Assign the new access
sequence ACU2 to conditions CT01 and CT02.
After carrying out these steps we can perform valuation again on the
basis of the characteristic CUCLA.

Extracto de mensaje de error del sistema SAP. Copyright SAP SE.