Class Implicit Enhancements not getting active

[Mithun_Kr]

I see a peculiar issue in the S/4HANA 1909 system.

I needed to enhance a standard class CL_MM_PUR_WF_OBJECT_PR_ITEM, to use with the flexible workflow. Thus I added a class enhancement implementation, and add an attribute, a method and few Events. Then I activated the enhancement.

However, none of these things show as 'Active' in the properties, (one screenshot here)

Subsequently, this attribute and the events I added, none of them can be seen in the workflow, as I try to add new pre-conditions, activities etc. Even when I create a new task with this class, I don't get the methods I added, when trying to add the terminating events.

Any idea, if this is some bug in SAP, or is there something I'm missing as a step to make sure the enhancement is 'Active' properly?

[Sandra_Rossi]

NB: in class enhancements, I recommend to prefix all custom components with ZZ (or the customer namespace) to avoid risks with future enhancements, like ZZ prefix is recommended for custom columns added to standard database tables.

[Sandra_Rossi]

It has always been like that, workflow doesn't support class enhancements -> see other discussion and note 1642132 (https://answers.sap.com/questions/635899/attributes-events-methods-of-enhanced-class-are-no.html + 1642132 - Workflow builder/ task: Error WF_CONT 151)

Indexing the error messages for people searching:

• OO003 &1 &2 does not exist (Event &2 does not exist) (OO 003)
• WF_CONT151 "Method &-& does not exist" (WF_CONT 151)

[Mithun_Kr]

Thanks sandra.rossi, for the clarifications.

I expected this old 'limitation' would've been overcome with the new ABAP and new Flexible workflow frameworks... Sad to see it still exists.

Why does SAP make it so difficult for any enhancements on the flexible workflows?

[Mithun_Kr]

In this old OSS note 1642132, the solution mentioned is to derive a custom class from the standard class instead of enhancing it. But in our case the class CL_MM_PUR_WF_OBJECT_PR_ITEM is also "Final". So can't do that as well...

Moreover, in the flexible workflow, it's not allowed to modify and replace the class name, as those fields are all read-only. 😞