ERS invoice failing in SNC - InvoiceRequest_In

[Former Member]

Hi all,

We are having an ERS scenario wherein the invoice posted via MRRL is failing in SNC with following error:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>  - <!-- 

<SAP:Code area="INTERNAL">INCORRECT_PAYLOAD_DATA</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>Error while processing message payload An error occurred when deserializing in the simple transformation program /1SAI/SASE2256E884A7DC72914B5 The value '' is not in the value range of the XML schema type 'decimal' or it does not meet the specified limitations</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Any suggestion to help resolve would be appreciated.

thanks,

mahesh.

[Muniyappan]

Hi

can you please post this in http://scn.sap.com/community/pi-and-soa-middleware space.

Regards,

Muniyappan.

[Former Member]

Issue resolved. The issue was the field VEPREI is not getting generated in Idoc but is a mandatory field in XML.

[Muniyappan]

Hi,

how are you handling this issue?

are you changing the sender idoc structure or sending constant to VEPREI in PI?

Regards,

Muniyappan.

[JaySchwendemann]

We have the same issue. VPREI is not filled in incoming IDoc which results in Proxy error on SNC side (Invoice_In Service Interface)

Any resolution for this yet?

Thanks

Jens

[JaySchwendemann]

There seems to be a node for switching of more strict schema validation of ABAP stack (in case of proxy communication). See here http://service.sap.com/sap/support/notes/1651794

Anyways, I believe that this is either a fault of ERP side (not filling the VPREI field of the IDoc) or the PI/SNC side (mapping an empty field).

We'll open an incident for this. Will post solution here

Cheers

[JaySchwendemann]

🙂 SAP already came up with an adjusted mapping. See here http://service.sap.com/sap/support/notes/1579791

HTH

Cheers

Jens