cancel
Showing results for 
Search instead for 
Did you mean: 

special characters are not getting converted sometimes while Outbound IDOC is triggered from S4 Sys

manemahesh
Participant
0 Kudos

Hi All,

IDOC(SUBMAS01) is being sent from EHS S4 system to SAP PO middleware and its being successfully processed E2E (SAP S4->PO->Downstream sys) for some of the EHS Specifications. But recently EHS is migrated from ECC to S4 and after data migration when some of the specifications are triggered from EHS IDOC is coming to middleware but special Characters are not getting converted to unicode  (e.g<DATAORIGIN>EH&S</DATAORIGIN> to <DATAORIGIN>EH&#38;S</DATAORIGIN>) and in xml if its not getting converted its failing in middleware since these characters((&,<= ) makes xml as non well formed xml.

Could you please let us know what could be reason that some specifications IDOC gets triggered with unicode conversion for special characters(&,<=) and for some specifications IDOC is not converting these special characters to unicode.

Regards

Mahesh

Sandra_Rossi
Active Contributor
0 Kudos
If you used the standard XML port, then it would be a bug. Did you check SAP Support? (search IDOCS_OUTPUT_IN_XML_FORMAT)
manemahesh
Participant
0 Kudos

Hi Sandra_Rossi,

Do you mean WE21 port ? There our SAP team has maintained Transaction_RFC port type under which they have RFC pointing to middleware system(SAP PO). Not File Port in WE21. Pls help further on this.

Sandra_Rossi
Active Contributor
0 Kudos
My 2 cents: if RFC is sent to SAP PO, XML is not implied in EHS, so it's not a bug in EHS but a bug in SAP PO. If you used the standard SAP PO features to generate the XML, did you check SAP notes or contact SAP Support?
manemahesh
Participant
0 Kudos

Hi Sandra,

In middleware we using Standard IDOC_AAE adapter and not having any settings for xml conversion explicitly also some specifications when triggered from EHS we receive the message with valid xml from ECC having Unicode converted values for special characters and message is processing successfully.This issue is causing for only some specifications for which data is migrated from EHS ECC to EHS S4 system. So looks like standard unicode conversion while IDOC is getting triggered from ECC to PO is not happening for select cases.

Regards

Mahesh

Sandra_Rossi
Active Contributor
0 Kudos
Then, did you check SAP notes or contact SAP Support?

Accepted Solutions (0)

Answers (0)