DDIC ACTIVATION ERRORS and RETURN CODE in SAPA731ESI.TRD

[Former Member]

Hi

We're busy with SPDD phase during EHP8 Upgrade, but cannot resolve Matchcode ID & Matchcode Object issues below.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

DDIC ACTIVATION ERRORS and RETURN CODE in SAPA731ESI.GTQ

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1EEDO519X"Matchcode ID" "ZCTPC" could not be activated

1EEDO519 "Matchcode Object" "ZCTP" could not be activated

1 ETP111 exit code           : "8"

When we try to edit these objects in SE11 (image 3 & 2 below), we get error message "Matchodes not supported in Unicode systems" (image 1 below).

So now it is not possible to fix these old Matchcodes that we don't even need, but it is halting the Upgrade with exit code "8"...

Has anyone resolved this?

Thank you and best regards,

Adrian Bruwer

p.s. All I can think of that I haven't tried yet is to temporarily set the sap profile parameter "abap/unicode_check" 3 values to "off"; then try to fix the Matchcode ID and Matchcode Objects. Afterwards set the parameter values back to "on". But I'll need to ask Basis to do that if it is a possible solution?

[Former Member]

Hi

We're busy with SPDD phase during EHP8 Upgrade, but cannot resolve Matchcode ID & Matchcode Object issues below.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

DDIC ACTIVATION ERRORS and RETURN CODE in SAPA731ESI.GTQ

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1EEDO519X"Matchcode ID" "ZCTPC" could not be activated

1EEDO519 "Matchcode Object" "ZCTP" could not be activated

1 ETP111 exit code           : "8"

When we try to edit these objects in SE11 (image 3 & 2 below), we get error message "Matchodes not supported in Unicode systems" (image 1 below).

So now it is not possible to fix these old Matchcodes that we don't even need, but it is halting the Upgrade with exit code "8"...

Has anyone resolved this?

Thank you and best regards,

Adrian Bruwer

p.s. All I can think of that I haven't tried yet is to temporarily set the sap profile parameter "abap/unicode_check" 3 values to "off"; then try to fix the Matchcode ID and Matchcode Objects. Afterwards set the parameter values back to "on". But I'll need to ask Basis to do that if it is a possible solution?

[RaymondGiuseppi]

You were supposed to delete those Matchcodes before the Upgrade (ref: 24860 - Replacement of a matchcode ID by a search help function) SAP only managed conversion of its own matchcode (AFAIK)

• From which version are you upgrading, was it already Unicode?
• Does the delete option work?

Regards,

Raymond

[Former Member]

Thanks Raymond

We did an Upgrade 4 years ago and the Matchcodes didn't pop up on SPDD or SPAU at the time. We've been on Unicode for a year now and the Matchcodes also didn't pop up on UCCHECK.

So I understand it's a good idea to delete these 20 year old Matchcodes, but I didn't even know about them until now... it's a catch 22. Will let you know when we resolve it.

Adrian