OCI XML ESAPO 3.5 fail when more than one product item

[Former Member]

We are testing SRM 7 with OCI-XML ESAPO 3.5. It is successful to return one item with the XML file like this:

<?xml version="1.0"?>

<CatalogItems>

<CatalogItem>

<Quantity><Value>10</Value><UoM>EA</UoM></Quantity>

<Price><Value>12.3400</Value><Currency>HKD</Currency>

<PriceBasisQuantity>1</PriceBasisQuantity></Price>

<LeadTime>P10D</LeadTime><Product><Identifier></Identifier>

<Description>First ESAPO 3.5 Product Test</Description>

</Product><Category><CategoryID>80501</CategoryID></Category>

<Text><Content>Note of First ESAPO 3.5 Product</Content>

<Language>EN</Language></Text>

</CatalogItem>

</CatalogItems>

However, it is fail if I try to include 2 items in the XML document:

<?xml version="1.0"?>

<CatalogItems>

<CatalogItem>

<Quantity><Value>10</Value><UoM>EA</UoM></Quantity>

<Price><Value>12.3400</Value><Currency>HKD</Currency>

<PriceBasisQuantity>1</PriceBasisQuantity></Price>

<LeadTime>P10D</LeadTime><Product><Identifier></Identifier>

<Description>First ESAPO 3.5 Product Test</Description>

</Product><Category><CategoryID>80501</CategoryID></Category>

<Text><Content>Note of First ESAPO 3.5 Product</Content>

<Language>EN</Language></Text>

</CatalogItem>

<CatalogItem>

<Quantity><Value>5</Value><UoM>EA</UoM></Quantity>

<Price><Value>10.0000</Value><Currency>HKD</Currency>

<PriceBasisQuantity>1</PriceBasisQuantity></Price>

<LeadTime>P10D</LeadTime><Product><Identifier></Identifier>

<Description>Second ESAPO 3.5 Product Test</Description>

</Product><Category><CategoryID>80501</CategoryID></Category>

<Text><Content>Note of Second ESAPO 3.5 Product</Content>

<Language>EN</Language></Text>

</CatalogItem>

</CatalogItems>

Is there something wrong with the XML document? Please help. Thanks.

Regards,

Donald

[Former Member]

The problem was solved by OSS note 1463457.

[Former Member]

Additional information:

After debug BBP_WS_DISPATCH_XML_MAPPING, I found that it only read in the first 768 characters of XML document and which cause the error of incomplete catalog.

[Former Member]

Please store the XML in a file format and then send the file as parameter to the SAP encode base 64 function.

This will solve the issue.

Thanks,

-Devi Swain

[Former Member]

Hi Devi Swain,

Thanks for your reply. For OCI-XML, we are always store the XML in a file and pass the file as parameter to the SAP encode base 64 function since we are using BBP 2.0 with OCI-XML ESAPO 3.0.

When testing SRM 7 with OCI-XML ESAPO 3.5, it is okay if XML file length is <= 768 chars., when length > 768 system response error: Error during XML processing; contact system administration / Incomplete items in catalog. Only complete items were transferred

When debug in FM BBP_WS_DISPATCH_XML_MAPPING, field iv_xml_document arrived to this FM was cstring(768).

Regards,

Donald