on 03-13-2014 11:25 AM
Dear All,
Appreicate your help and advice to handle this requirement.
We have implemented the indonsian ODN functionality for issuing ( Domestic -Tax invoices -VAT serial no ).
Currently it works as below when an invoice cancellation process takes place.
for ex:
VF01- Invoice creation - 915069944 - VAT /ODN # -> 0109001455609098
VF11-Invoice cancellation-940003647 - VAT /ODN #-> 0109001455609098 ( cancellation will not consume new ODN - will be same as original invoice).
VF01 - Invoice creation - 915069945 - VAT/ODN # -> 0109001455609099 ( Revision invoice).
The problem is when a revision invoice is created, then ODN number is consuming a new ODN # for a revision invoice (55609099).
The requirement is when a revision invoice is created, we would need the same ( original ) ODN number (55609098) to be consumed and not to consume new ODN (55609099). Additionally, we also need to notify that this is a revision invoice by changing the ( STATUS CODE) to 1 from 0.
That is for the (Revision) invoice 915069945 - the expected VAT/ODN no should be assigned as - 0119001455609098.
I was checking over several notes 1033737 / 1578519 /1856053/1839112. This one 1033737 says that we may not be able to change the status code at all from 0 to 1 .
Two things:
1. How could we stop system consuming a new # (ODN) ,when a revision invoice ->( further to cancellation invoice) is created.
2. If option # 1 is possible, then how could we change the status code from 0 to 1.
Is there a standard functionality in which we could acheive this by any chance, since i couldnt find more details on this topic any where.
Else, Will it be feasible if going for an enahcement for acheiving this without disturbing any of the other ODN's. ex(Italy).
How best we could handle if we go for enhacement. We are using same SD (Invoice) and FI(Accouting) numbers as same sequence no's.
Thanks,
Best Regards,
Kumar.
Since you already put efforts by going through the couple of OSS notes (I appreciate this), I feel, you have to go with USEREXIT_NUMBER_RANGE in the program RV60AFZZ to achieve this requirement.
G. Lakshmipathi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am not sure why you have used Invoice no. as tax Invoice no. (faktur No.)
SAP has given standard configuration to generate faktur no. for each invoice. Separate number range has to be maintained for the same.
Tax Invoice number is populated in the Reference field of Invoice and same is copied in Accounting document.
For changes of status code on the basis of Customer tax classification we have implemented customer exit where we change the first two digits appropriately based on Customer tax classification.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
11 | |
10 | |
6 | |
5 | |
5 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.