Bugseye catalog does not return a shopping cart occasionally

[Former Member]

Dear Experts,

We have a problem where Bugseye catalog items sometimes randomly do not return a shopping cart into the SRM portal side. This happens randomly for any Bugseye items after restarting the browser (IE8 and Firefox 3.6.13). Otherwise the Bugseye catalogs are running fine with an https connection.

After the browser restart, about 1/3 attempts to create a shopping cart from Bugseye catalogs return nothing. Instead the user is brought back to 'Shop in 4 steps' screen without a shopping cart. After the failed attempt a user lock is created (tcode SM12) and the shopping session left open. Once a shopping cart is successfully returned, it does not fail again unless the browser is restarted. The error happens randomly and we haven't been able to figure out any logic behind it. We have verified that the source codes in the Bugseye side, just before continuing to order items, are identical for a successful and non-successful tries. We have also placed breakpoints in function module BBP_WS_IMPORT_SC_DATA, to ensure no errors are issued for the items

Does anyone have any idea what could cause the problem?

We are running SRM7.0 Extended Classic Scenario ( SRM 7.00 SP11). Requisite Bugseye version 4.0.0.25.

Here is an example Standard Call Structure for the catalog:

10 https://orsrdd01.orion.fi:8001/requisite/BugsEye 0 URL

10 username xxxx 2 Fixed Value

20 password xxxx 2 Fixed Value

30 catalog Catalog2 2 Fixed Value

40 sap-locale SY-LANGU 1 SAP Field

50 datalanguage EN 2 Fixed Value

60 BYPASS_OUTB_HANDLER 2 Fixed Value

70 BYPASS_INB_HANDLER 2 Fixed Value

100 HOOK_URL 4 Return URL

Looking forward to your expert insights,

Matti Hokkanen

[Former Member · Accepted solution]

Hi,

Please also append this in the call structure,

5 ~OkCode ADDI 2 Fixed Value

6 ~target _top 2 Fixed Value

7 ~caller CTLG 2 Fixed Value

sometimes the browser cookie and session information will be conflicting with the punchout window. It is better to clear the cookie information and then try once on http.

Thanks,

Prashanth

[Former Member · Accepted solution]

Thank you Prashant for your input! I added the parameters you suggested and tested again with no changes to the behaviour. I also tried clearing all IE cookies, temp files and history. Also tested multiple times with both http and https catalog addresses. The same error comes up with all scenarios.

[Former Member · Accepted solution]

Matti is it same with the lower versions of IE too?

[Former Member · Accepted solution]

Unfortunately I'm not able to install any programs on to my workstation and haven't tested this with lower versions of IE. Do you have some clues that would lead to this working with older versions?

[Former Member · Accepted solution]

Yeah, there are known browser issues with IE 8. Few cases include, items not returned to SC, HTTP 500 Internal Server Error etc.. May be you can try with the lower versions and see if it works.

Thanks,

Prashanth

[Former Member · Accepted solution]

I tested this with IE8 compability mode (which I believe downgrades the browser into version 7) and the problem still persisted. I believe we are forced to look for an alternate solution to Bugseye catalogs.

[jason_boggans]

Hi All,

Please note that SAP no longer support Requisite/ClickCommerce products since December of 2006, see the same note [485884|https://service.sap.com/sap/support/notes/485884] for further details on Requisite BugsEye and eMerge delivery.

Regards,

Jason

[Former Member]

Hi,

It will be a network issue.

for my clarification. whether SRM 7.0 is works with Bugseye.

upto my knowledge for SRM 7.0 , SRM-MDM is mandatory.

you can raise a SAP OSS message and get the feedback

can you confirm whether your landscape is SRM 7.0 wiht Bugeye only

Regards

G.Ganesh Kumar

[Former Member]

Hello,

Thank you for the reply. We are currently using only Bugseye for manually updated catalogs. Besides that, we have multiple direct OCI-call catalogs. We do realize that SAP only supports MDM catalogs. However we think that the MDM environment is way too heavy for our use and we already have the catalogs available in Bugseye. Everything else works fine with Bugseye except for the described error. I have raised an OSS message regarding the issue but SAP is reluctant to investigate the error because Bugseye is involved.

Yours truly,

Matti Hokkanen