DRC - Italy - Official document numbering (ODN)

[akaserer]

Hi everybody,

In Italy we got the requirement to maintain gap less document numbering within the Italian company code.

SAP offers the Official document numbering (ODN) in Italy - see

Official document numbering (ODN) in SAP S/4HANA Cloud

Do you use the ODN-functionality in Italy for your customers or projects?

We got some clients already, who managed to work without ODN-customizing. They use these rules:

• There is a validation so that they cannot set back the posting date in incoming invoices
• Make sure that no parked incoming invoices are deleted (permissions)

Do we need to setup ODN up if we use Document and Compliance Reporting, or is it supported when sending and receiving invoices via Document and Compliance Reporting / eDcoument Cockpit?

Thanks

A.

[beier-rehau2021]

Hi, we are using SAP-standard ODN functionality (filled within VBRK-XBLNR field) together with SAP DRC. If it is obligatory for SAP DRC mapping I couldn't 100% confirm, but I know that ODN Number is part of the XML content.

It is realy important to avoid gaps, therefore we implemented also rules within billing types to avoid cancellations for billing documents with existing accounting documents via VF11. Debit and Credit Notes should be created also without reference, to avoid double usage of the same ODN.

For the incoming invoice part we have a Z-solution, so I couldn't answer your question regarding posting date.

Daniela Beier
REHAU Industries

[JDG_R1]

Dear Collegues,

I am having some issue fulfilling a requirements from my business team. From their understanding of the regulation, all invoices must have <FatturaElettronicaBody><DatiGenerali><DatiGeneraliDocumento><Numero> sequential.

However, it did happen that when a wrong posting is performed the eDocument generated is rejected to SDI without any solution to correct it and resend. In this case, the document number is not transmitted to the SDI and this results in a 'gap' of the numbering. (Reversing it without sending the reversal invoice generates an additional numbering gap).

I don't see any workaround (or at least non that do not involve some specific coding) to this probem and I would be curious to know how some of you have dealt with this issue.

For a better understanding of the current system configuration :
For source type FI_INVOICE - tag <Numero> gets it's value from field BKPF-BELNR
For source type SD_INVOICES - tag <Numero> gets it's value from field VBRK-VBELN
The business ask that a different numbering record be used for the tag - that would increment only invoices that have been correctly correctly receieved by SDI...

[akaserer]

Hi Daniela,

Thank you for sharing your insights on the use of ODN in Italy and your experiences with SAP DRC.

I wanted to bring to your attention the feedback we received from our SAP finance experts regarding the use of ODN. They mentioned that in previous projects, attempts to use ODN resulted in more issues than solutions. Consequently, their advice is not to use ODN for Italy. The did SAP validations instead, to ensure gapless numbers.

Specifically, they mentioned using BELNR as ODN.

Given this advice, we're now exploring how to map BELNR to the XML content. I wanted to seek your expertise on this matter. Do you have any recommendations or insights on how we can effectively map BELNR to the XML content, considering your experience with ODN and SAP DRC?

Your guidance on this would be highly valuable, and we appreciate your time and expertise.

Thanks,

Andreas

[JDG_R1]

Hello Andreas,

[JDG_R1]

Hello Andreas, I was wondering if you were able to solve this issue of maintain gap less document numbering within the Italian company code without ODN.

[JDG_R1]

Hello Andreas, I was wondering if you were able to solve this issue of maintain gap less document numbering within the Italian company code without implementing ODN ? I am having an issue understanding how ODN can solve this issue altogethe ; we have mapped BKPF-BELNR and VBRK-VBELN to tag <FatturaElettronicaBody><DatiGenerali><DatiGeneraliDocumento><Numero> so we already have a gapless eDocument list. Our issue however is when an eDocument is rejected or when a wrong posting is made, in this case we get a gap in the numbering transmitted to the SDI.

[martinlitalin]

Hi Andreas,

there may also be adiditonal information on the DRC Italy WorkZone site. If you like please email gsworkzone@sap.com for access.

Best regards,

Martin

[JDG_R1]

Hello Andreas and martinlitalin, I was wondering if you were able to solve this issue of maintain gap less document numbering within the Italian company code without implementing ODN ? I am having an issue understanding how ODN can solve this issue altogethe ; we have mapped BKPF-BELNR and VBRK-VBELN to tag <FatturaElettronicaBody><DatiGenerali><DatiGeneraliDocumento><Numero> so we already have a gapless eDocument list. Our issue however is when an eDocument is rejected or when a wrong posting is made, in this case we get a gap in the numbering transmitted to the SDI. Are you in a similar situation ?