cancel
Showing results for 
Search instead for 
Did you mean: 

OVS issue?

Former Member
0 Kudos

I have a screen which consists of 3 fields and for one of the field i assigned OVS.

While pressing on that input field i am getting the error like beow.......

Note

The following error text was processed in the system CGD : Access via 'NULL' object reference not possible.

The error occurred on the application server svr3_ABC_20 and in the work process 0 .

The termination type was: RABAX_STATE

The ABAP call stack was:

Method: IF_WDR_OVS_LISTENER~MODIFY_RESULT_VIEW of program CL_WDR_VALUE_HELP_HANDLER=====CP

Method: WDDOMODIFYVIEW of program /1BCWDY/9G598IOA1X2HFSB3X8F0==CP

Method: IF_WDR_VIEW_DELEGATE~WD_DO_MODIFY_VIEW of program /1BCWDY/9G598IOA1X2HFSB3X8F0==CP

Method: DO_MODIFY_VIEW of program CL_WDR_DELEGATING_VIEW========CP

Method: MODIFY_VIEW of program CL_WDR_VIEW===================CP

Method: DO_MODIFY_VIEW of program CL_WDR_CLIENT_COMPONENT=======CP

Method: DO_MODIFY_VIEW of program CL_WDR_WINDOW_PHASE_MODEL=====CP

Method: PROCESS_REQUEST of program CL_WDR_WINDOW_PHASE_MODEL=====CP

Method: PROCESS_REQUEST of program CL_WDR_WINDOW=================CP

Method: EXECUTE of program CL_WDR_MAIN_TASK==============CP

And some times it showing a another error in the pop-up as below....

Webdynpro error

What Happend?

Calling the webdynpro page was terminated due to an error

Error Type :sapPopupMainID_X1

And if put a break point in the ovs method it is working fine....

Please help me to sort out this...

Please help me to sort out this....

Regards

Ravi

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Ravi,

Better you maintain the values at domain level.

Take "DropDownByKEY" element and then bind the context attribute to "SelectedKey' in element property. It may work fine....

Former Member
0 Kudos

Hi All,

First time when i am developed this application it works fine.But after that i add small logic to get the portal login useid into my WDA application by using application parameters .i am getting that user id .But from that onwards only the OVS is not working properly...Is this may cause any Issue on OVS...

Please help me to sort out this...

Regards,

Ravi

abhimanyu_lagishetti7
Active Contributor
0 Kudos

Post the code u hv writte in OVS event.

Abhi

Former Member
0 Kudos

Hi Abhi,

This is the code which i had written on OVS event..

WHEN 'SERVICE_DEPT'.

CASE ovs_callback_object->phase_indicator.

WHEN 0.

    • //declare all text related to the selection dialog box

DATA : text3 TYPE string VALUE 'SERVICE Department SEARCH',

text4 TYPE string VALUE 'SERVICE Department VALUES'.

*

    • << assign appropriate values to these text strings >>

    • //Export all text to the OVS Component through the set_configuration()

**

CALL METHOD ovs_callback_object->set_configuration

EXPORTING

window_title = text3

group_header = text4

col_count = 1.

WHEN 1.

    • //Create corresponding object

*

TYPES: BEGIN OF ty_input1,

DEPTID TYPE ZPM_DD_DEPT,

END OF ty_input1.

WHEN 2.

    • //dereferencing the data contained in the query_parameters of callback object

*

FIELD-SYMBOLS: <lf_input_query1> TYPE ty_input1.

*

ASSIGN ovs_callback_object->query_parameters->* TO <lf_input_query1> CASTING.

*

    • << Use some Bapi for fetching data according to the values contained in the above field symbol and take the output in some table >> .

CALL FUNCTION 'ZPM_FM_GET_DEPARTMENTS'

EXPORTING

  • IV_RESTYPE =

iv_uname = sy-uname

IMPORTING

ET_DEPARTMENTS = lt_output1

tables

return = tt_return

.

sort lt_output1 by DEPTID.

    • //exporting data to be displayed as value help list to the OVS component

CALL METHOD ovs_callback_object->set_output_table

EXPORTING

output = lt_output1.

WHEN 3.

    • //dereferencing the data contained in the selection parameter of callback object.

FIELD-SYMBOLS: <fs_selection1> TYPE ty_output1.

ASSIGN ovs_callback_object->selection->* TO <fs_selection1> CASTING .

IF <fs_selection1> IS ASSIGNED.

lv_var3 = <fs_selection1>-DEPTID.

  • navigate from <CONTEXT> to <SERVICE_DEPT> via lead selection

lr_node = wd_context->get_child_node( wd_this->wdctx_service_dept ).

  • get element via lead selection

lr_element = lr_node->get_element( ).

lr_element->set_attribute( name = `SERVICE_DEPT`

value = lv_var3 ).

ENDIF.

*endif.

ENDCASE.

Regards,

Ravi...

Former Member
0 Kudos

Hi Abhi,

i tested the application with same code in OVS Event in different Scenarios...

!. If i directly test the Application through SE80 ,it is working fine....

2.if i create URL iview in the portal,And tested in portal,It is working Fine...

3.If i create a Webdynpro ABAP Iview,And tested it getting the dump like above on the second click of the OVS Binded element.

It is getting problem only when i executed in the portal through WDA iview....

Please help me to sort out this....

Regards,

Ravi

abhimanyu_lagishetti7
Active Contributor
0 Kudos

Hi

is the Portal user and r/3 system user mapped and having the same authorization?

Abhi

Former Member
0 Kudos

Hi Abhi,

We are not using the portal user ID any where in the OVS Event to get the values....We are using the R/3 User ID which havd full authorization to get the list of Departments....

Sry i didnt get u that in which these User id 's will effect to get the values.....

Some times it is working properly.....

In my case i have 3 input fields.if i give the input for antoher two and after that if i click on ovs binded input it is working fine....instead if we directly click on the ovs field ,for the second click it getting dump...

Regards,

Ravi

Former Member
0 Kudos

Hi All,

Please give me any inputs to resolve this....

Regards,

Ravi

bryan_cain
Contributor
0 Kudos

Did you log into the back end and look at the dump information in ST22? Posting that might help...

Former Member
0 Kudos

Hi Bryan Cain,

Error analysis

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not

caught in

procedure "IF_WDR_OVS_LISTENER~MODIFY_RESULT_VIEW" "(METHOD)", nor was it

propagated by a RAISING clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

You attempted to use a 'NULL' object reference (points to 'nothing')

access a component (variable: "ME->TABLE").

An object reference must point to an object (an instance of a class)

before it can be used to access components.

Either the reference was never set or it was set to 'NULL' using the

CLEAR statement.

Information on where terminated

Termination occurred in the ABAP program "CL_WDR_VALUE_HELP_HANDLER=====CP" -

in "IF_WDR_OVS_LISTENER~MODIFY_RESULT_VIEW".

The main program was "SAPMHTTP ".

In the source code you have the termination point in line 689

of the (Include) program "CL_WDR_VALUE_HELP_HANDLER=====CCIMP".

The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in

procedure "IF_WDR_OVS_LISTENER~MODIFY_RESULT_VIEW" "(METHOD)", but it was

neither handled locally nor declared

in the RAISING clause of its signature.

The procedure is in program "CL_WDR_VALUE_HELP_HANDLER=====CP "; its source

code begins in line

551 of the (Include program "CL_WDR_VALUE_HELP_HANDLER=====CCIMP ".

This is What we got in the ST22....

Regards,

Ravi

bryan_cain
Contributor
0 Kudos

I think it's saying the lookup table is not being set correctly, and the OVS is trying to reference it when it's Null.

Have you set the external debugger in the OVS to see what's happening?