Catalog OCI SRM 7.01 Professional shopping vs Simplified Shopping

[Former Member]

Hello Professionals,

We are upgrading to SRM 7.0 EHP1 and have an issue that the when punching out to the SRM-MDM catalog or an external catalog through the professional shopper role, all OCI information is returned correctly. However, when punching out to a catalog through the simplified shopping scenario, the catalog short text , supplier part number, etc. are all wrong.

Professional shopper - Short Text = 007, 24 Drawers/Bins, Cabinet - THIS IS CORRECT

Simplified Shopper - Short Text = 007,\x5cx2024\x5cx20Drawers\x5cx2fBins,\ - THIS IS WRONG

We are on SRM-MDM 3.0 Version 7.1 (7.1.08.254)

Any help would be appreciated.

Susan Bennett

[Former Member]

Hi Susan,

Can you pls share the screen shots of the issue that will help to understand the issue.

Thanks

Ravi

[Former Member]

Hi Ravi,

I don't have a screen print, but the short text values being returned to the shopping cart were different if starting with Shop Professional or Simplified shopping for the exact same item.

Professional shopper - Short Text = 007, 24 Drawers/Bins, Cabinet - THIS IS CORRECT

Simplified Shopper - Short Text = 007,\x5cx2024\x5cx20Drawers\x5cx2fBins,\ - THIS IS WRONG

We ultimately decided to stick with shop wizard and never implemented simplified shopping. We also found later on that we needed to add a codepage (UTF-8) to our external punchout catalog definitions in Web Services. Peter talks about this above.

Hope this helps you.

Susan

[FlamentP1]

Hi all,

maybe a little late but I just came accross this post as i was searching for this same issue -> fields from the OCI were strangely 'translated' when transferring from supplier catalog to SRM shopping cart. As described this happened only with a 'simplified shopper' and not with a 'wizard shopper'.

After some research and debugging i came accross the 'inbound handler' that is probably executed also in your case.

the inbound handler can be found in SICF / default_host / SAP / SAPSRM / inbound_hdlr

on clicktrhourgh to the details go to tab 'handler list' (3th tab)

there the handler is mentioned --> /SAPSRM/CL_CH_WD_INBOUND_HDLR

double click to go to the methods

if needed you can debug the method IF_HTTP_EXTENSION~HANDLE_REQUEST

the solution in my case was to add a codepage (UTF-8) to the catalog definition in spro

(there should be a field available for this right from the overview page).

and in the OCI-call-parameters make sure you have the inbound handler activated.

(not sure what it gives if inbound handler is deactivated all together - the docu says if it's the same codepage there is no need to activate the the inbound handler).

So adding the codepage to the catalog and setting the OCI parameter BYPASS_INB_HANDLER to blank solved my problem of strange 'translations'...

Regards

Peter.

[Former Member]

Hi Susan,

As Jason mentioned there is no difference in calling the catalog for  Professional shopping cart as well as Simplified Shopping cart.

Hope you can past here your catalog structure defined in "External Web service" to analyze.

Regards

Ashok

[jason_boggans]

Hi Susan,

If you use a HTTP Sniffer tool like HTTP watch or similar you could check the differences of the returned data from the professional SC versus the Simplified one, in truth, there should be no difference, both use the same parameters to call the catalog, i.e. through the catalog call structure, and both use the same HOOK_URL generation to formulate the return URL on the way back.

Maybe something is in place with this system that the simplified cart is using a different web dispatcher/portal/port etc to return and then maybe due to this the inbound handler is using/assigning some invalid or incorrect codepage to the simplified SC data. Try entering the parameter into the catalog call structure to bypass this handler and retest.

BYPASS_INB_HANDLER with value 'X'

Regards,

Jason

[Former Member]

Hi Susan,

Can you please refer  Note 1287412 - Prerequisites for OCI integration in SRM 7.0 that explain changes needed by Vendor for Punch out... Abstract from Note to consider;

4. Catalog providers

Catalog providers should comply with the specifications as defined in all OCI specifications while processing the following parameters:

           a. Return URL

           Variable name, default is HOOK_URL

           This URL is used to return to SRM from the catalog application. Set the value of this field to blank since it is automatically filled at runtime by the procurement application.

           The HOOK_URL can have a different name, but the type of this field must be set to Return URL. The HOOK_URL is encoded so that special characters such as ':' and '/' are represented by '%' and the hex digits for the ASCII code of the characters. The encoding method is standard URL encoding. The catalog application is responsible for decoding this string into a valid URL. Note that the catalog application must not make any assumptions about the HOOK_URL. For example, it cannot assume that a question mark is present to delineate the URL variables.

           The complete HOOK_URL sent from SRM must be used to return the data.

Please check the same.

Hope this helps.

Thank you

Ritesh

[Former Member]

Hi Ritesh,

Thank you for your response. We determined that we were having this problem because we need to upgrade to SRM-MDM 7.01 in order to implement Simplified Shopping. We are currently at SRM-MDM 3.0.

Susan