RV_BELEG depending on: fiscal year, sales organization, month

[Former Member]

Hi everyone.

We are facing an issue involving SD invoices numbering:

we are currently using 3 numberings: one for receipts, one for invoices, and another one for cancelling invoices.

The request is: this numbering should depend on fiscal year AND sales organization AND month (i.e. period).

The problem is: we have sort of 30 sales organizations. Which yields 30 (sales orgs.) * 12 (months) * 3 (numberings) = sort of 1000 ranges EACH YEAR.

But range RV_BELEG does not depend on anything, we can only define range numbers with a two-character string. If we used 0-9,A-Z coding we can use 36*36 = 1296 ranges.

Which means: OK for the first year, but we cannot extend all these ranges for the 2nd and subsequent years.

Anyone can help. Kind regards.

Alvaro

[Lakshmipathi · Accepted solution]

First of all, your requirement of having SD number ranges fiscal year itself is WRONG. It should be a continuous one and only when the ranges reaches the final stage, you have to change.

Let us assume, you had generated a billing document in 2009 with reference as 10. As per your requirement, if you assign a new number range, the same reference (10) will be generated once again for some other customer and if you check in VBRK or VBRP table, you can see only one data.

thanks

G. Lakshmipathi

[Former Member]

Hi,

Pls consider the thoughts as mentioned above by the other people here.

We had a requirement to have the number ranges as per the Sales org's in EMEA and different ranges for Debit and credits but not for each month though.

Even after considering the requirements, if you still feel that you want to have the number ranges as per sales org and month, then you can use the User Exit RV60AFZZ to drive custom number ranges.

What we did was we had a custom table that had fields Sales Org, Billing type, Prefix and suffix (some European countries needed this), and the Number range object. So from this table, SAP know which number range object should be applicable.

Now for rv_beleg, you can maintain the actual number range objects intervals. As suggested, you can also use wild chr's to name your objects.

In the user exit mentioned, you can put code to use the number ranges instead of using the standard range as maintained in the Billing type.

Hope this helps.

[eduardo_hinojosa]

Hi all,

I understand the requirements of Alvaro, he's spanish, as me, and it is a frequent requirement by spanish managers.

First, try to understand the reason of this requirement. Perhaps the end users have the habit to know in which year and month was created the invoice by the ID (ie: VBRK-VBELN). You have a lot of fields for this in the interface to FI (check Note 301077 - User exits for the interface to accounting), after you can view this fields in FBL5N or other reports (you can enhance FBLXN tcodes, see SAP Note 215798 - FBL*N: Special fields are not displayed and related notes if the field populated is not in the standard). For instance, in field BSEG-SGTXT you have 50 characters to concatenate year, month, sales org and so on.

Finally, explain to your client or to your boss that it's impossible. Think that by tax authority requirements in Spain, you can delete or archive invoices after 5 years, and field VBELN is a key of VBRK. And of course, it's not in legal requirements.

I hope this helps you

Regards

Eduardo

[Former Member]

Hi Alvaro,

First of all i am not able to understand why they need a different number series for each month wrt to sales org.

For your problem solution may is given below,

you can use two digit char like 0 - 9, A - Z & all special Char like @, #, $, % etc

you will get more than 2000 number series wrt these codes.

Once more thing you can do is deletion of previous or previous number series. Let us take example: this month is April ie 04, that tim you can delete all Jan month number series, ie you will be keep on getting new two digit codes.

Regards,

Nagesh