ESCom XML 2.0 version not supported

[ashish25bp]

Hello Experts,

I am trying to import ESCom xml file downloaded from CHESAR tool for Exposure scenario into SAP through T code CGESCIP. This T code is available only after activation of Business functions : LOG_EHS_PS_CI_5 and LOG_EHS_PS_CI_6. However while loading the CHSEAR ESCom xml file, I am getting an error " Selected file is not a valid ESCom file"

The CHESAR file has ESCom xml version 2.0.

When I generated xml file for eSDS from my system, it shows xml version as 1.5

I assume that the reason of error that I am facing could be because of in compatibility of the Escom xml versions. My SAP system has lower version where as CHESAR xml has higher version (2.0 vs 1.5)

I checked with SAP and understood that currently version 2.0 is not supported through SAP.

My question is has anyone encountered the same issue ? What is the other option available to upload the xml, generated from tool like CHESAR, into SAP?

Regards,

Ashish

[ashish25bp]

Thanks Christoph for your suggestions

Indeed I tried doing a workaround by changing the xml version to 1.5 in the beginning stream data of xml but it did not worked.

In fact I raised OSS to SAP and that is where I got the reply that ,

" The function "Inbound Processing of ESComXML" is valid only for ESComXML format 1.5"

" The function "Outbound Processing of ESComXML" is valid only for ESComXML format 1.5"

SAP has currently no plans to support ESComXML 2.0 or later.

It means that some other option needs to be explored for uploading xml files for Exposure scenario from CHESAR Tool

Regards,

Ashish

[Mark-Pfister]

ashish25bp - just write me a private message. I think you might need to connect to me in order to do that.

[Mark-Pfister]

Hi Ashish,

You already figured out and got confirmation from SAP that ESComXML 2.0 is not supported.

I just want to point out, that the format itself ESComXML - will no longer be developed separately but will become part of SDSComXML to my understanding.

If you need help importing the 2.0 Version into SAP you would need to develop some adjustment to the current SAP logic. Please reach out if you need help doing so.

Best

Mark

[ashish25bp]

Hi Mark,

Thanks for your comments,

yes I would like to understand about the development that can be made in SAP logic for importing 2.0 version of .xml. In fact it has become a challenge now for me about how to import large volume of exposure scenario data in SAP now.

Please let me know how can I reach out for this

Thanks

Ashish Pradhan

[christoph_bergemann]

Dear Mark

helpful input from you. Currently I have the feeling that SAP will not take care "always" regarding all aspects in EHS.

So i support your feeling that "SDSComXML" will get a standard but i have doubts that it will be supported by SAP in the futrue e.g. S/4 HANA Core (as they are currently "blocked" because of S/4 HANA development),. Therefore (refer to discussion regarding EU PoisonCenter in a parallel thread): may be a SAP Partner might then deploy later a solution (import export of SDS via XML).

Dear Ashish

you need to understand that you can not just" change" the XML data stream (and change the "1.5." to "2.0" to get an import. I assume that with version 2.0 new data elements are included. And to "parse" these (so that the data is imported to SAP HES): you need an extension of the existing functionality.

It is now your decision to go on. Simple decsiion could be. Use 1.5. implementation by SAP: Copy the implementation to "customer specifix" one and extend the coding so that 2.0 XML files can be imported/exported

C.B.

[ashish25bp]

Thanks Christoph for your suggestions

Indeed I tried doing a workaround by changing the xml version to 1.5 in the beginning stream data of xml but it did not worked.

In fact I raised OSS to SAP and that is where I got the reply that ,

" The function "Inbound Processing of ESComXML" is valid only for ESComXML format 1.5"

" The function "Outbound Processing of ESComXML" is valid only for ESComXML format 1.5"

SAP has currently no plans to support ESComXML 2.0 or later.

It means that some other option needs to be explored for uploading xml files for Exposure scenario from CHESAR Tool

Regards,

Ashish

[christoph_bergemann]

Dear Ashish

this finding by your is quite "strange" (I checked with SAP and understood that currently version 2.0 is not supported through SAP.)

So you have identified one OSS note in which SAP is really explaining that they support only versionb 1.5. ? Then why do we have this interface?

Anyhow. we are not using this. One need to be "expert" in XML. One would need now to compare version 1.5. with 2.0 (and what is the difference)

At the begin of the xml data strream there must be some information stored regaridngf version 1.5. May be just "change" that to 2.0 and try to reupload. IN the ideal world. If you look at SAP, Microsoft etc.: we have a kind of "downport" option. May be there is no "real" big idfference in 1.5 to 2.0... But I did not checked

Stareng any how I would restart the OSS and ask SAP: what is the next step to go on?

C.B.