Official Document Numbering(ODN) Configuration SDMMFI for GST
Dashboard
ERP Supply Chain Management
Localization India
Skip to end of banner
Go to start of banner
Official Document Numbering(ODN) Configuration SD/MM/FI for GST
Skip to end of metadata
Created by Former Member, last modified on Jul 25, 2017
Go to start of metadata
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
2472623 - GST India: Official Document Numbering
2489866 - GST India: Official Document Numbering ----> VALID ONLY FOR SAP_APPL: 606 SP (17,18 and 19)
2490434 - GST India: Corrections to Official Document Numbering Solution
2487781 - GST IN: Invoice and ODN numbers are skipped while saving billing document in transaction VF01
2496105 - GST India: ODN Corrections to note 2490434
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-
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”
Maintain document class in V_DOCCLS via SM30
Assign document types to document class in view J_1IG_V_T003_I via SM30
Ensure the same document type that is linked to billing type in VOFA is linked here-
Maintain number group in J_1IG_V_NUMGRP via SM30
Assign Number range group to Company Code, BUPLA and other fields in J_1IG_V_OFNUM via SM30
Maintain number range for the object J_1IG_ODN, ensure that all the settings are set as below-
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
2. Assign document types to document class in view J_1IG_V_T003_I via SM30
3. Maintain number group in J_1IG_V_NUMGRP via SM30
For Direct FI Postings-
1. Maintain docclass in V_DOCCLS via SM30
2. Assign document types to document class in view J_1IG_V_T003_I via SM30
3. Maintain number group in J_1IG_V_NUMGRP via SM30
Rest all the steps remain same as mentioned for Billing
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
The same can be viewed in FB03 -
Related SAP Notes/KBAs
2487589 - GST India: Data Dictionary Activities for Official Document Numbering
2472623 - GST India: Official Document Numbering
2489866 - GST India: Official Document Numbering ----> VALID ONLY FOR SAP_APPL: 606 SP (17,18 and 19)
2490434 - GST India: Corrections to Official Document Numbering Solution
2487781 - GST IN: Invoice and ODN numbers are skipped while saving billing document in transaction VF01
2496105 - GST India: ODN Corrections to note 2490434
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)
Do you have any idea about it ?
Thanks
Rahul
Jul 13, 2017
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.
Jul 23, 2017
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.
Thanks. Thanks for clarifying our earlier query.
Jul 26, 2017
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.
Please suggest how to correct it
Regards,
Mihir Patel
Jul 26, 2017
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)
Jul 26, 2017
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
Jul 26, 2017
Ashish Mohapatra
The ODN generation has no links to RCM condition types. It is generated only when
Vendor Classification is '0' unregistered vendor
Vendor Classification is '2' SEZ vendor
Country of the vendor is not 'IN' , import vendor
If any of this three condition is satisfied ODN will be generated irrespective of the transaction (MIRO or FB60).
In the FM J_1IG_CHECK_BEFORE_ODN it is coded as
IF ( lv_ven_class EQ '0' OR " Unregistered Vendor
lv_ven_class EQ '2' ) OR " GST SEZ Vendor
lv_ven_land1 NE 'IN'. " Import Vendor
Jul 26, 2017
Achuthan Nair
HI Ashish,
you are right, but problem is still there. I think FM is not validating vendor classification properly
Regards,
Mihir Patel
Jul 26, 2017
Former Member
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
This flag is to be set only for purchase and not sales.
And even for purchase only when required based on certain checks you should set the flag.
So check in your system without any criteria if you have set the flag to "X" in the BADI.
Regards,
Brinda
Jul 27, 2017
Former Member
Hi ,
we are currently implementing ODN.
All mentioned notes have been implemented successfully.
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?
Thanks and regards
Vivien
As per Attachment, with Pack.
In the Transaction, the entry field is missing
Jul 31, 2017
Ashvin Masih
Hi Brinda,
Really helpful document.
But as mentioned earlier in case of DZ document type it should be updated when we are receiving advance F-29.
But it is updating in the normal payment too that is via F-28.
Any solutions??
Regards,
Ashvin.
Aug 10, 2017
Former Member
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>>>>
You can write your enhancement in BADi and handle this-
##2496588 - GST India: Customer exit to enable ODN for payment vouchers and other relevant transactions
Regards,
Brinda
Aug 31, 2017
Azhar Iqbal
Nice presentation, Thanks for sharing.
I have one question for Cancellation of Invoices with ODN number.
Can you explain how it will work for canceled invoices and can we have different ODN for cancel invoices ?
Oct 24, 2017
Former Member
Hi Azhar,
New ODN is not required for cancelation as per GST rules.
Same ODN from original invoice will get copied.
regards,
brinda
...
