Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 8644

dump ASSERTION_FAILED in Adobe form after EHP6 upgrade

$
0
0

Hi Experts,

 

Our client is using custom Adobe forms to create master data: Cost center, Vendor, Customer, Material.

 

And we are doing EHP6 upgrade on ECC system, 2 forms - Cost center and Material are getting this dump when hit Approve/Reject button, and the other 2 are working fine.

 

Our Adobe form is built with ZCI layout, embeded within custom Webdynpros.

 

And here is the dump details:

 

Runtime error: ASSERTION FAILED

Program; CL_WDR_IFBA_SERVICES==========CP

 

The dump happened before calling the custom Webdynpro, it dumps at CLASS lcl_ifba_diff, method diff, and here is the method description in the code comments: 

 

*********************************************************************************************************************

* This class implements a performance optimized XML diff algorithm for  the form data exchanged between the Web Dynpro ABAP runtime and the  Adobe Reader (ADS). The XML documents created for the Adobe Reader (ADS) will be build  according to the following schema (see CL_WD_ADOBE_SERVICES-> GET_WD_CONTEXT_AS_XML for the implementation:

1. For the Context node bound to the property "dataSource" of the interactiveForm UI element, a XML tag with the name of the Context node will be created:

1.1. If the corresponding form template (SFP) has an inbound handler defined, a XML tag "form" with namespace http://www.sap.com/FP  will be created: FORM_TEMPLATE_NAME

2. For a Context node of cardinality 0..n or 1..n: Create a XML tag "DATA" for each Context element and process the Context element

(3.)For a Context node of cardinality 0..1 or 1..1: Process the Context element (3.)

  2.1. The "dataSource" Context node won't be considered to be multiple. Instead, the lead selection will be choosen.

3. For a Context element: For all child nodes: Create a XML tag with the name of the Context node and process the Context node (2.) For all Attributes: Create a XML tag with the name of the attribute and create the value of the Attribute as text:  Hello, World!

4. The Adobe Reader wraps the form data with an additional tag "data"  with namespace "http://www.xfa.org/schema/xfa-data/1.0/", which can be ignored: *    ...* * It's possible (via JavaScript in the Adobe Reader) to create/delete subforms in the form which results in a modified structure of the XML documents: There might be more (or less) DATA nodes in the XML document from the Adobe Reader than the corresponding XML document from  the Web Dynpro Context (for multiple Context nodes) and there might be nodes in the XML document from the Adobe Reader which is not in the XML document from the Context (or vice versa): This might happen for optional Context nodes (i.e. nodes of cardinality "0..1|n").

-> The diff algorithm makes use of the knowledge of this specific structure of the XML documents.  -> XML string readers will be used instead of XSLT transformations/XML parsers to avoid the creation of the DOM (which is performance critical too)  -> Context information will be used instead of random access to the  XML document (random access = create DOM)

****************************************************************************************************************************

 

I am not able to attach image file, here is the ABAP calls at runtime:

 

12  METHOD       CL_WDR_IFBA_SERVICES==========CP    CL_WDR_IFBA_SERVICES==========CCIMP

     LCL_IFBA_DIFF=>DIFF  

11  METHOD       CL_WDR_IFBA_SERVICES==========CP    CL_WDR_IFBA_SERVICES==========CM004           CL_WDR_IFBA_SERVICES=>DIFF_XFA_DATA   

10 METHOD       /1WDA/CADOBE==================CP    /1WDA/CADOBE==================CCIMP     CL_INTERACTIVE_FORM_ZCI=>IF_NW7_VIEW_ELEMENT_ADAPTER~HANDLE_EVENT    

9  METHOD       CL_NW7_VIEW_ELEMENT_ADAPTER===CP    CL_NW7_VIEW_ELEMENT_ADAPTER===CM004       CL_NW7_VIEW_ELEMENT_ADAPTER=>DISPATCH_NW7_EVENT   

8  METHOD       CL_WDR_CLIENT_SSR_LS==========CP   CL_WDR_CLIENT_SSR_LS==========CM00J  

CL_WDR_CLIENT_SSR_LS=>IF_WDR_CLIENT~GET_CLIENT_UPDATES    

7  METHOD       CL_WDR_MAIN_TASK==============CP    CL_WDR_MAIN_TASK==============CM00I        CL_WDR_MAIN_TASK=>EXECUTE   

6 METHOD       CL_WDR_MAIN_TASK==============CP    CL_WDR_MAIN_TASK==============CM00U   

   CL_WDR_MAIN_TASK=>IF_WDR_RUNTIME~EXECUTE   

5 METHOD       CL_WDR_CLIENT_ABSTRACT_HTTP===CP   CL_WDR_CLIENT_ABSTRACT_HTTP===CM01A 

CL_WDR_CLIENT_ABSTRACT_HTTP=>HANDLE_REQUEST    

4 METHOD       CL_WDR_MAIN_TASK==============CP    CL_WDR_MAIN_TASK==============CM00J          CL_WDR_MAIN_TASK=>IF_HTTP_EXTENSION~HANDLE_REQUEST    

3 METHOD       CL_HTTP_SERVER================CP    CL_HTTP_SERVER================CM00D      CL_HTTP_SERVER=>EXECUTE_REQUEST    

2 FUNCTION     SAPLHTTP_RUNTIME                    LHTTP_RUNTIMEU02                   

      HTTP_DISPATCH_REQUEST    

1 MODULE (PBO) SAPMHTTP                            SAPMHTTP                           

%_HTTP_START

 

 

Our system SAP_BASIS is SAPKB73108. Our production system doesn't have EHP6 changes yet, and it's not dumping there. 

Could you please help me out on this? Any point is helpful here.

 

Thanks a lot.

 

 

Regards,

Vicky


Viewing all articles
Browse latest Browse all 8644

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>