Professional Documents
Culture Documents
Community WIKI SAP Community Welcome, Guest Login Register Search the Community
Purpose
The purpose of this page is to clarify on the required settings for ODN to work correctly SD/MM/FI postings.
Overview
Below notes should be implemented fully and correctly-
2487589 - GST India: Data Dictionary Activities for Official Document Numbering
2489866 - GST India: Official Document Numbering ----> VALID ONLY FOR SAP_APPL: 606 SP (17,18 and 19)
2487781 - GST IN: Invoice and ODN numbers are skipped while saving billing document in transaction VF01
2496588 - GST India: Customer exit to enable ODN for payment vouchers and other relevant transactions
2497855 - GST India: ODN Corrections to populate fiscal year for billing documents
2497727 - GST India: ODN Corrections to enable BAPI_ACC_DOCUMENT_POST and additional functionality
ODN Configuration
For SD
Billing-
1. Ensure that document type is assigned to Billing type in below path(VOFA)-
SPRO > Sales & Distribution > Billing > Billing documents > Define billing type > Here assign the document type.
Here transaction group will be “7”
https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=467544373 1/11
12/20/2017 Official Document Numbering(ODN) Configuration SD/MM/FI for GST - ERP SCM - SCN Wiki
2. Maintain document class in V_DOCCLS via SM30
https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=467544373 2/11
12/20/2017 Official Document Numbering(ODN) Configuration SD/MM/FI for GST - ERP SCM - SCN Wiki
4. Maintain number group in J_1IG_V_NUMGRP via SM30
5. Assign Number range group to Company Code, BUPLA and other fields in J_1IG_V_OFNUM via SM30
6. Maintain number range for the object J_1IG_ODN, ensure that all the settings are set as below-
https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=467544373 3/11
12/20/2017 Official Document Numbering(ODN) Configuration SD/MM/FI for GST - ERP SCM - SCN Wiki
Proforma-
For Proforma, document type is not required to be assigned to billing type(VOFA)-
SPRO > Sales & Distribution > Billing > Billing documents > Define billing type > Here document type will be blank
But here transaction group should be “8”.
Rest all the steps will be same as what is mentioned for Billing.
For MM-
1. Maintain docclass in V_DOCCLS via SM30
https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=467544373 4/11
12/20/2017 Official Document Numbering(ODN) Configuration SD/MM/FI for GST - ERP SCM - SCN Wiki
https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=467544373 5/11
12/20/2017 Official Document Numbering(ODN) Configuration SD/MM/FI for GST - ERP SCM - SCN Wiki
https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=467544373 6/11
12/20/2017 Official Document Numbering(ODN) Configuration SD/MM/FI for GST - ERP SCM - SCN Wiki
ODN-
For SD- The generated Official Document Number will be updated against VBRK-XBLNR.
For MM- ODN is only required for UNREGISTERED Vendors with RCM conditions.
BKPF-XBLNR will get updated with the value that you will enter manually in reference field.
BKPF-XBLNR_ALT will get updated with ODN
For Customer/output FI - The generated Official Document Number will be updated against BKPF-XBLNR.
For Vendor/input FI - BKPF-XBLNR will get updated with the value that you will enter manually in reference field.
BKPF-XBLNR_ALT will get updated with ODN
https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=467544373 7/11
12/20/2017 Official Document Numbering(ODN) Configuration SD/MM/FI for GST - ERP SCM - SCN Wiki
2489866 - GST India: Official Document Numbering ----> VALID ONLY FOR SAP_APPL: 606 SP (17,18 and 19)
2487781 - GST IN: Invoice and ODN numbers are skipped while saving billing document in transaction VF01
2496588 - GST India: Customer exit to enable ODN for payment vouchers and other relevant transactions
2497855 - GST India: ODN Corrections to populate fiscal year for billing documents
2497727 - GST India: ODN Corrections to enable BAPI_ACC_DOCUMENT_POST and additional functionality
odn official document numbering gst india j_1ig_odn xblnr
19 Comments
Rahul Kulkarni
Thanks Brinda. Really helpful document.
ODN should be updated in the tax relevant transactions. For example in case of DZ document type it should be updated when we are receiving advance (F-29). But in our case it is updating
in the normal payment also (F-28)
Thanks
Rahul
Ashish Mohapatra
Thanks Brinda for the blog. Please refer the following statements of your blog
"For MM- ODN is only required for UNREGISTERED Vendors with RCM conditions.
BKPF-XBLNR will get updated with the value that you will enter manually in reference field.
BKPF-XBLNR_ALT will get updated with ODN
For FI - The generated Official Document Number will be updated against BKPF-XBLNR."
Since some of the entries relevant for RCM will be processed through MM and some through FI, it will create confusion since in BSEG table ODN will be in different fields for different
documents, even for the same vendor.
Ashish Mohapatra
Hello Brinda,
Since the table-field BKPF-XBLNR_ALT is not visible in FB03 transaction, how do user (without authorization for SE16/SE16N or similar t-codes) confirm that the field has been populated by
ODN.
https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=467544373 8/11
12/20/2017 Official Document Numbering(ODN) Configuration SD/MM/FI for GST - ERP SCM - SCN Wiki
Achuthan Nair
Hi Brinda,
After implementing above SNOTE of ODN, ODN is getting generated for all the MIRO transaction. it doesn't check either vendor is registered / RCM conditions are there or not.
Regards,
Mihir Patel
Ashish Mohapatra
The ODN is generated based on the FM J_1IG_CHECK_BEFORE_ODN. In this FM it is hard-coded that when the Vendor Classification is 0 or 2 or the country is not 'IN' ODN will be
generated for reverse charge. This hard-coding is bound to create problems. (For Mr Mihir Patel - You can check this FM and your problem can be due to the master data maintained in
vendor master)
Achuthan Nair
HI Ashish,
I checked the vendor classification in vendor master data and it's blank. Further, I also run the transaction FB60, it's still generating ODN number.
There is no RCM conditions during posting document using MIRO & FB60
Regards,
Mihir Patel
Ashish Mohapatra
The ODN generation has no links to RCM condition types. It is generated only when
If any of this three condition is satisfied ODN will be generated irrespective of the transaction (MIRO or FB60).
Achuthan Nair
HI Ashish,
you are right, but problem is still there. I think FM is not validating vendor classification properly
Regards,
Mihir Patel
Brinda R
Hi,
The issue could be because you have set the flag to "X" for all scenarios in BADI. CALL BADI lv_exit->change_odn_checks
Regards,
Brinda
https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=467544373 9/11
12/20/2017 Official Document Numbering(ODN) Configuration SD/MM/FI for GST - ERP SCM - SCN Wiki
Vivien Meier
Hi ,
We have one Problem when trying to create the object J_1IG_ODN as per note 2487589, Attachment "Number-Range-Object.pdf"
In the Transaction SNRO we should enter the Package J1I_GST_LO. We have the Problem because the entry field in the Transaction is not shown as
described in the attachment document. So we can not enter the package. When we enter all the other required data and try to go to another Tab or save, we got error message saying the
object does not exisit and should be created via SNRO (which we are just doing). We checked that required entries (Package, Domain etc.) have been creted. Also all the Tasks related to the
other two attachments of the note have been performed. We had the idea that it might be the authorisation, but su53 was fineWe had the idea that it might be the authorisation, but su53 was
fine.
Has anyone any Idea what is wrong here? .How have You processed this step?
Vivien
Ashvin Masih
Hi Brinda,
But as mentioned earlier in case of DZ document type it should be updated when we are receiving advance F-29.
Any solutions??
Regards,
Ashvin.
Brinda R
Hi Ashvin,
If the document type is configured in J_1IG_T003_I table then system will try to generate ODN.
If you do not want ODN to be generated for a particular tcode then copy the document type and create a new one for which there is no entry maintained in J_1IG_T003_I table. <<<<OR>>>>
Regards,
Brinda
Azhar Iqbal
Nice presentation, Thanks for sharing.
Can you explain how it will work for canceled invoices and can we have different ODN for cancel invoices ?
https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=467544373 10/11
12/20/2017 Official Document Numbering(ODN) Configuration SD/MM/FI for GST - ERP SCM - SCN Wiki
Brinda R
Hi Azhar,
regards,
brinda
Azhar Iqbal
Thanks,
What in case if i want a running series For Example: If invoice is KA100001 and canceled invoice should have KA100002.
Is it possible to do so ?
Regards
Azhar Iqbal
varun yadav
As per design, ODN number will copy only for document category N & S (check in vofa further about document category vbrk-vbtyp for example M-invoice).
If you want new ODN number for cancellation billing document type then document category should not be N or S. But it should be one of M,P, O, 5 or 6.
Azhar Iqbal
Hey Varun,
if i change the document category then it will not serve as cancel invoice. M,P,O,5 or 6 are like credit memo that will not make Sales order status as opened for billing
it again.
Regards
Azhar
varun yadav
Hello Azhar,
So to overcome Sales Order status issue you can write two small enhancement (1. Start of FM where you can temporarily change document category
relevant for new ODN & store original in temp. Variable and 2. End of FM to reset it again from temp variable). This way it will not impact standard related to
status but will generate new ODN.
Regards,
Varun
Achuthan Nair
Hello all,
While doing Payment run via F110, ODN number is not getting generated. I have implemented BADI J_1IG_CHANGE_ODN_CHECK , which generates ODN number for all other FI
transactions, only facing problem with F110. Can anyone help ?
Regards
Kriti Agarwal
https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=467544373 11/11