Phrase Enabled Characteristics

[Former Member]

Dear Experts,

I am facing issue of one standard class and it's characteristics are not being Phrase enabled.

Class is SAP_EHS_1018_015 and all it's characteristics

As per standard, process, I have performed the Master Data Matchup
(CGCZ) and ran

1) Activate Phrasing of Field
2) Activate Phrasing of Characteristics
3) Match up ValAss Type and Class

still no success.

I have reviewed characteristics and it has all below prerequisite of being phrase enabled
> Data Type: CHAR format
> Number of Chars: 30
> Function Module C14K_PHRASECHARACT_CHECK allocated

Also, checked in CGAB, there getting below error...

"No phrase-enabled characteristic is available for class
SAP_EHS_1018_015"

Technically speaking, As you must be knowing, when the Characteristics
become phrase enabled, the respective entry get maintained in table
TCG66 but the same is not happening at my end.

Can you please advise what steps I need to perform be make these
standard characteristics as phrase enabled?

Kindly Advice.

Thanking you,

Regards

Amol

[Former Member · Accepted solution]

Hi Amol,

Have you checked the class "SAP_EHS_1018_015" in CL02 for having the required characteristics assigned to it?

Thanks & Regards

Gourav Kumar

[Former Member · Accepted solution]

Hi Gourav,

Yes, perform the all the basic test already....

Regards

Amol

[Former Member · Accepted solution]

Hi Amol,

We also faced similar situation in one of our project, where we just implemented a new enhancement pack.

What you can do is sit with the developer and try to investigate what value it is passing while F4 help is being called to FM C14K_PHRASECHARACT_CHECK. there would be some mismatch in the passing value and the available table entries which creating the issue.

Thanks & Regards

Gourav Kumar

[christoph_bergemann · Accepted solution]

Dear Amol

this topic has been discussed very often in this FORUM:

http://scn.sap.com/thread/358074

http://scn.sap.com/thread/1668178

http://scn.sap.com/thread/851498

http://scn.sap.com/thread/3186551

http://scn.sap.com/thread/1602758

http://scn.sap.com/thread/1672797

http://scn.sap.com/thread/1472576

IN same case you need to "manipulate" TCG66 by using SAP tools to get the problem removed

C.B.

PS: this topic is not mentioned yet in my document:

http://scn.sap.com/docs/DOC-41109

My research has shown that this "issue" wasn't mentioned since some time here; and therefore I did no add it to the document. May be I will add it