cancel
Showing results for 
Search instead for 
Did you mean: 

Conversion in IF_HTTP_EXTENSION~HANDLE_REQUEST

former_member185171
Participant
0 Kudos

Hello,

in SRM we use the implementation of IF_HTTP_EXTENSION~HANDLE_REQUEST in /SAPSRM/CL_CH_WD_INBOUND_HDLR. Within this handler some data seem to be changed.

When entering the handler data are formed this way:

12 postArray.push(); 13 postArray.push();

14 postArray.push(); 15 postArray.push();*

After exiting we see this:

11 NEW_ITEM-EXT_PRODUCT_ID 00000001 1004374336643#

...

15 NEW_ITEM-MANUFACTMAT 00000001 1004374336643#

...

21 NEW_ITEM-VENDORMAT 00000001 1004374336643#

These are the last statements of the handler:

*

* finalize the HTML rendering

  CONCATENATE lv_html '</body></html>' INTO lv_html.        "#EC NOTEXT

  server->response->append_cdata( lv_html ).

  server->response->set_content_type( 'text/html' ).

  server->response->set_status( code = '200' reason = 'OK' ).

The content of LV_HTML is correct before the server->reponse calls.

Has anybody any suggestions what might cause the problem?

Thanks a lot.

Kris

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member114630
Active Participant
0 Kudos

We are encountering the same issue. We may have also found a fix. Can you let me know what call structure you are using?

Monique

former_member185171
Participant
0 Kudos

I'm rather new in this area, so I'm not sure my answer is ok:

Is it this you mean?

lt_target_fields TYPE tihttpnvp, " parameters sent as query string of the target URL

lt_post_body TYPE TABLE OF string. " the post body array for absolute navigation.

The interface uses IF_HTTP_SERVER as parameter.

Kris

former_member114630
Active Participant
0 Kudos

Actually, I'm talking about the call structure you are using for the catalogs. This can be found in the IMG under SRM Server --> Master Data --> Content Management --> Define External Web Services. Click on the catalog and then standard call structure.

former_member185171
Participant
0 Kudos

Thank You, this is what I find there.

10 https://b2bpreview.dell.com:443/invoke/B2BDirect.Entry/processDocument?rn=emea 0 URL

20 Username B2B_KU_Leuven 2 Vaste waarde

30 Password Leuvent3st 2 Vaste waarde

40 operation_type create 2 Vaste waarde

60 ~OKCode ADDI 2 Vaste waarde

70 ~Target _top 2 Vaste waarde

80 ~caller CTLG 2 Vaste waarde

Former Member
0 Kudos

Hi Kris,

try to check the OSS Note: Note 1599711 - OCI value with character '\' not correctly transferred

Kind regards

Juraj