最新消息:雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客

XSD is not generating a correct XML (SAP) - Stack Overflow

programmeradmin2浏览0评论

I’m in the process of migrating an integration from SAP PI to SAP CPI. For this, I imported the existing EHF schema into CPI, re-did the mapping and ensured everything is now inside CPI. But there's an issue, the XML result generated by CPI is different from the one generated by PI.

Here’s an example of the XML result from CPI:

    <CustomizationID>urn:fdc:peppol.eu:poacc:trns:order_response:3:extended:urn:fdc:anskaffelser.no:2019:ehf:spec:3.0</CustomizationID>
    <ProfileID>urn:fdc:anskaffelser.no:2019:ehf:postaward:g3:09:1.0</ProfileID>

And here's the result from PI:

<ns0:OrderResponse xmlns:ns0="urn:oasis:names:specification:ubl:schema:xsd:OrderResponse-2">
    <ns1:CustomizationID xmlns:ns1="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">urn:fdc:peppol.eu:poacc:trns:order_response:3:extended:urn:fdc:anskaffelser.no:2019:ehf:spec:3.0</ns1:CustomizationID>
    <ns1:ProfileID xmlns:ns1="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">urn:fdc:anskaffelser.no:2019:ehf:postaward:g3:09:1.0</ns1:ProfileID>

In the PI XML, the namespace is included for each element, but in the CPI result, it’s missing.

The missing reference is causing the file to not be validated by the EHF validator.

Has anyone else encountered this issue before?

发布评论

评论列表(0)

  1. 暂无评论