Customer Checkout to post Sales Invoices on B1 with mandatory VAT Allocation Date

[Former Member]

Greetings. I am trying to post receipts from Customer Checkout to SAP B1. The Italian localisation of B1 has the Vat Allocation Date VatDate on Sales Invoices as mandatory. I edited the vBIU.sap.CCO.CreateReceiptPre step in the extension package and added the VatDate which value should match the DocDate.

After that I create a receipt on CCO and in the monitor whenever I try to pass the receipt to SAP I get this message:

005 - B1 Error (0010000100):
Exception : DI Error: (-10) 256000511 - "VAT Allocation Date" is mandatory field. Enter a date.-The di call #1 did fail.

The error message in the B1 Integration Framework shows the VatDate field with the correct value in the xml file.

I am not sure where to start solving the issue. Can you please help?

Thanks

Luca

[JoergAldinger]

Hello Luca:

According to the DI Proxy log you are not sending the VatDate in the Payment, and that is what is being rejected.

Also, I can see that you are using the same extension step for several different extension points. Since the structure for each is different, you should create different extension steps for each.

In addition, remember to confirm the version of the CCO scenarios you are using, they may have been updated.

Best regards,

Joerg.

[Former Member]

Hi Joerg, thanks for your reply. I edited the additional scenarios sap.CCO.Extension V3.1.0, specifically the vBIU.sap.CCO.CreateReceiptPre that I associated with different steps as in the first screenshot. Attached is also the atom0.xsl I edited to make it work.

Also attached is the log from the DI Proxy folder. On it I don't see the field I intend to pass to B1. For comparison, attached also the error message from B1 integration framework.

Thanks!

Luca

atom0.txt

diproxy-1.txt

error-message-b1i.txt

[JoergAldinger]

Hello Luca:

You should not modify the predelivered scenarios (which version of the scenarios are you using?). Instead, create your own extension step and reference it according the the documentation.

Also, one thing that has helped me find errors in the scenarios before, is looking at the DI Proxy log. There you should find the final XML generated that throws the error.

Best regards,

Joerg.