How can I set SAP Business One document numbering series in Customer Checkout.

[piyushv]

Hi All,

I installed Customer Checkout which is linked with SAP Business One. I have separate document numbering series for AR Invoice in SAP Business One for Customer Checkout. How can I set it in customer checkout ?

Thanks.

[JoergAldinger]

Hello Fedias,

We actually went with the first option, not the second one. But the general logic for handling this in an extension step is:

1. Create a user-defined table in B1 (e.g. "@XXX_CCO_CONF") with columns or rows for your numbering values, por POS terminal, in general or whatever is suitable for you
2. Create an extension step for "PostInvoiceDocument" (see samples on PartnerEdge)
3. In the extension step:
   a) First run a SQL query to get the correct series value from the UDT created in step one,
   b) Add the "Series" node to the Documents header of the extension step output

The above works for invoices and credit notes. For payments defining the numbering in this way is unfortunately not possible because the extension step does not hand over information for whether the payment is incoming our outgoing. Please vote for this improvement request to make it possible: Payment Extension Step Improvement

Hope this helps.

Best regards,

Joerg.

[JoergAldinger]

Hello Piyush,

Unfortunately there is no default configuration for this requirement. We have needed this before, too, so I just submitted an improvement request. Kindly vote for it here: https://influence.sap.com/sap/ino/#/idea/242987

As for the workaround, here is what you can do:

1. Create a plugin, add the required configuration properties there, inject them into the outgoing B1i message, create an extension step in B1i and put the value into the Series field.
2. Or, you can create any required configuration table directly in B1 or B1i, and only create the extension step for each transaction so that the Series is set correctly.

To solve our requirement we have used both methods: 1. for invoices and credit notes, 2. for incoming/outgoing payments. I would suggest you go by way of #2, since it does not require any CCO plugin and is pretty straight forward. Had we thought of #2 we probably would not have implemented #1...

Hope this helps.

Best regards,

Joerg.

[Fedias]

Hi Joerg Aldinger,

Can you share your 2nd suggestion please?