GV_SCR_SELECTED_CAT input too long - selecting product category SRM 5.5

[Former Member]

We have recently patched SRM 5.5 to SP17 with MDM 2.0 SP4 patched to 16 via EP7.0. When raising a text shopping cart (not using the catalogue) we have seen the error GV_CSR_SELECTED_CAT input too long as a windows pop-up message on occasion when attempting to access the category pick list. If a category is picked from the recently used list ..no problem however if the full pick list is accessed via "..." (three dots) then we sometimes see this message. If we click shop again to re-start the error is not reproduced. We are using classic scenario.

The problem is hard to replicate and does not happen all the time ..i have tried with that catalogue oprn in another window or closed, first time logged on for that day or not. unable to find a consistent pattern.

Has anyone observed this? and can point me in the right direction. Any help greatly received.

Add Internal Goods / Services

Enter the quantity and, if necessary, change the requested delivery date.

Description

Internal Note

Quantity/unit Each Days ...

Price/Currency British Pound ...

Category IPR/Patent Legal Ser IT Contractors IT Hardware IT Software Purchase Mob.Phones Employee ...

Required on

[jason_boggans]

Hi Debbie,

I think you might refer to the error GV_SCR_SELECTED_CAT not GV_CSR_SELECTED_CAT (where SCR = screen). It does not matter if the users are creating carts from catalog or free text, in either case, webservice id is analysed, so make sure none of the webservices contain any special characters like ü, $, &, - etc. If they do, remove them and retest.

Regards,

jason

[Former Member]

Hi Jason

We are also experiencing a similar issue as reported by Debbie. We are using SRM 5.5 SP15 Classic with ECC 6.0 SP 15 backend. Both are at kernel 700 patch 291 and are unicode.

We have recently moved our SRM server from Windows OS to Linux 2.6, OP release 2.6.18-194.el5 and this is when the error was first received. It has continued even after we migrated the ECC server to Linux also.

The error is only received when the user is shopping via transaction BBPSC02 and selecting Special Request. It is never received when shopping from catalogues. The user will input all details (description, sometimes an internal note but not always, Quantity/unit, UOM, Price/currency, Category) choose Add to Shopping Cart and the error is thrown. I believe they are not choosing a new product category from the search help but as we cannot replicate this can't be confirmed. They are not inserting any odd characters into any fields.

The issue only occurs for some users, and often if they log off and back on it does not re-occur.

We cannot replicate even though our QA system is a current copy of Production.

Any advice would be appreciated. In addition can you clarify what is meant by "in either case, webservice id is analysed", I understand webservice as a term only used in catalogue definitions.

Thanks

SD

[jason_boggans]

Hi Sally.

My statement means that even in the case of non catalog shopping, i.e. freetext item, the system still analyses the authorized webservices (catalogs) for the user and can throw an error if the webservice id is containing an invalid character, so check that all the catalog descriptions do not contain any such characters, even check in different languages as you may get a report from someone in lets say Mexico saying they are having problems, so they are probably logging on in Spanish, so you would have to check this webservice id in the backend while accessing the system in Spanish to verify what the catalog ID is.

Hope that makes some sense??

Regards.,

Jason

[Former Member]

Hi Jason

Thks for the quick response. We have no strange chars in the webservices and these haven't changed in a long time. Unless it is a coincidence I believe it is related to the OS change.

Any further suggestions greatly welcomed.

SD

[jason_boggans]

Hi Sally,

In all cases I have encountered, this was the root cause, if it is related to something else I am not aware of it.

Sorry.

Regards

Jason