Portal Runtime when passing special character MDM to SRM

[Former Member]

Dear Experts,

When check out from MDM, we have portal runtime error for product with special character > and < in description. Currently we're using parameter BYPASS_INB_HDLR with value "X" to accomodate difference between external and internal host. We've changed the external host due to company rebranding. I do aware that this parameter is responsible for character conversion, but if we didn't set the parameter in call structure, the system keep asking for login to backend when checkout from the catalog.

I've tried set the codepage UTF-8 in webservice catalog, but it only solved product with character ">" in description. Some product with "<" still got portal runtime.

Any Idea?

Regards,

Desti.

[bhanupriya_sharma1]

Hello Desti,

For solving this issue, it is important to note that the Codepage of Front End should be the same as the one configured in the SPRO settings for the Webservice of the Catalog.

You have tried to set UTF-8 to resolve the issue, however still the error occurs.

Could you check with Txn SNLS, which is the "Codepage of Front End" then set the same in SPRO settings.

Also, please note regarding the issue you face when you don't set BYPASS_INB_HANDLER parameter in call structure:

Could you try to add the following parameter in the SPRO settings:

returntarget = _parent.

If issue still persists, share a screenshot of your SPRO settings and kindly confirm your external catalog supports OCI 4.0

Regards,

Bhanupriya

[anita_lipovics]

Hi Desti,

did you check the note

1970761 - Chars '<' and '>' returned by catalog results in portal dump

It seems to be relevant for you.

Best regards,
Anita

[Former Member]

Yes I've already checked the note. But it says the parameter BYPASS_INB_HANDLER has to be removed, while we need that parameter to accomodate difference between external and internal host. So we can't use this note.

Oh and I also retest the scenario, and turns out using the codepage UTF-8 is not help. All product ID with character > and < still giving portal runtime error.

Regards,

Desti.

[laurent_burtaire]

Hello Desti,

there are correction instructions for the note: apply it.

Then, test again without any modification for the Web Service call structure.

Regards.

Laurent.