cancel
Showing results for 
Search instead for 
Did you mean: 

BADI for managing "Allow Shadowing " in Shopping carts without using the access key to modify the component configurator /SAPSRM/POWL_CONFIG_SC of the webdynpro component POWL_UI_COMP

Former Member
0 Kudos
215

Hi,

For the error in the POWL , " Query Shopping carts is already opened in another session",

SAP has provided Conf data specific configurator 'Allow Shadowing" to allow the same query to be opened in more than one session.

This change needs to be done in the component configurator /SAPSRM/POWL_CONFIG_SC of the webdynpro component POWL_UI_COMP.

But when trying to do the changes as above it is prompting for the access key for the object R3TR WDCC /SAPSRM/POWL_CONFIG_SC to enter as it is  a standard component.But we dont want to modify the standard component.

Is there any other alternative(BADI'S or SAP NOTE)  to remove the error without modifying the standard webdynpro component.

Please help me out in resolving the above error without using the acess key in modifying the standard component.

Many Thanks.

Kind Regards,

Sindhu Ravuri

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Sindhu,

the problem with the error "Query Shopping carts is already opened in another session" is a never ending story ...

I had a long, long discussion and multiple OSS messages with the SAP support to correct this problem without activating the "Allow Shadowing" parameter.

The real drawback of activating this parameter is that the POWL links for Define new query and Personalize are both inactive where these links are clickable in the system when shadowing is not active. This is SAP standard and described in OSS note 1692542 - POWL Links Define new query and personalize are disabled.


After months of corrections and searching for the real cause of the error but without eleminating the error we decided to create an enhancement in the FORM 'Flush_package'. This coding is three statements long and ignores the lock entry if the locked object is 'EPOWL_QUERY_EDIT'.


Since this time we have no longer this stupid message and can use all links on POWL.


Best regards

Joe

Former Member
0 Kudos

Hi Joe,

Thanks for your reply.

Could you please provide us some more details(method name and  the class name )  in creation of the enhancement in the form Flush_package and share us the screenshot.

Many thanks in advance.

Regards,

Sindhu Ravuri

Former Member
0 Kudos

Hi Sindhu,

I made the enhancement at the end of the FORM routine Flush_package in the INCLUDE LSENAF01:

...

* call BAdis for DD_ENQU_LISTENER
* Note: The BADI call has to be defined in a separate function module
*       because of transport problems (see internal CSN 1917897 2006)
      if ( gv_kayak_active <> space and rc = 0 )
      or ( badi_perf_test <> 0 ).
        perform call_badi
          tables
            seqta_lis
          using
            opcode
            scope
            enqobj
            user_use
            usvb_use
            badi_perf_test.
      endif.


ENHANCEMENT ZSCOPESRM_EI_POWL_Q_UNLOCK.    "active version
* Ignore lock in POWL-Object ENQOBJ: EPOWL_QUERY_EDIT to avoid POWL 016 message
     
if enqobj = 'EPOWL_QUERY_EDIT' and rc = 2.
           rc
= 0.
     
endif.
ENDENHANCEMENT.


After this enhancement we got no longer this stupid message.

Of course you have to check if this solution is applicable at your system.


Best regards

Joe

Former Member
0 Kudos

Hi Joe,

Thanks for your reply.

I have implemented the above code.

Do you have an idea When this will code get triggered actually to check how it is working.

Can you please help us.

Many thanks in advance.

Regards,

Sindhu Ravuri

Former Member
0 Kudos

Hi Sindhu,

test is quite simple:

set a breakpoint at the end of the badi DD_ENQU_LISTENER. Copy the URL of your actual POWL session and create a new tab in your browser with this URL. Display the fields enqobj and rc.

You should not get the error message because the enhancement sets the rc to zero.

Regards

Joe

Former Member
0 Kudos

Hi Joe,

Many thanks for your help.

Regards,

Sindhu Ravuri

Answers (0)