Skip to Content
Jan 05, 2012 at 03:52 PM

Workflow container op. dump when sap coding uses ixml instead of xslt



we have some SAP-systems with a self-designed workflow based on classes (not BOR).

On most systems all works fine, but on one system finalizing a work item via coding fails with a dump "deep inside" SAP:

While saving workflow container data the method cl_abap_typedescr=>describe_by_data_ref crashes due to a null-reference.

Through debugging I could localize the difference between the good and the bad system:

Bad system:

Method cl_swf_cnt_container->to_xml calls first the methode cl_swf_cnt_container_service=>container_get_default_use_xslt and this method sets the Parameter use_xslt to "space".

Afterwards coding runs through cl_swf_cnt_container_service=>to_xml_ixml.

Good system:

Parameter use_xslt gets the value "X", the system runs through cl_swf_cnt_container_service=>to_xml_xslt and all works fine.

So, my question: Where can I tell the system to use the correct Parameter for the "use_xslt"-service?

Comparing the workflow customizing etc. seems to be absolutly identical.



Corrected minor spelling error

Edited by: Rob Burbank on Jan 5, 2012 11:02 AM