Proposal of new number Range FY16-17

[Former Member]

Hi All,  Good day.

We are in need of a clarification as below, Could you please help us with your comments on the below.

We have a new Proposal to reset the number series of upcoming financial year 2016 -2017.

For Example the interval 6k has the range from 1635806001 to 163899999 and the current number range is 1635806083.

The proposal is to reset the current running number to 0 and have a new range of numbers as below without overlap.

From 2516500001 to 251659999.

We would like to have a confirmation whether we can go with the new proposal and it does not have any impact on documents that have already consumed the old numbers.

Thanks is advance for your reply.

Regards

Ganesh

[Former Member]

Hi Ganesh,

In continuation with Jignesh comment, We must never reset the running number range (6K). It will impact the exiting document, until archiving is done.

Year wise number range resetting  only happen  in CIN.

Ask business / steering committee , near about how much they can expect to consume the number for the billing document (compare with last year consumption ). say 100 or 150 documents in a year. As you can see there only 1635806083 (83) billing has been generated in a year but the rage is given is very large 1635806001 to 163899999.

Following steps can  be done.

1) Restrict the existing number range (6K) 1635806001 to 163899999.  to 1635806001 to 1635806100.

2) Better create new number range id say 6L

3) Start with number range (as per expected consumption in a year) 1635806201 to 1635806299.

This way you can save you number range.

Regards

Avinash

[Lakshmipathi]

Please try to phrase the query with some clarity instead of reproducing users' contents.  New number range for what ?   Sale Order ?  Delivery ?  Shipment ? 

Nevertheless, you cannot have a new number range year wise for any SD documents.  Only in case of FI, it is possible.

G. Lakshmipathi

[Former Member]

The new number range is for billing documents (transaction VF01)

Credit note

Debit note

Miscellaneous billing

Commercial Invoice etc.

It is not FI document.

Thanks

[VeselinaPeykova]

Is this a one-time adjustment, or you need to have numbers reset every year for a specific company code?

If it is the second and you are looking for a way to automate it, I had something similar in a previous project. We achieved that with a user exit and a z-table (we needed different number ranges per year for specific billing types in one of the many company codes). The exit for billing documents is in RV60AFZZ - USEREXIT_NUMBER_RANGE, which allows you to substitute the number range interval in VOFA with one of your choosing.

It is very likely that the year-dependent number range is a new legal requirement and that the business operation could also ask for non-buffered billing numbering.

If you currently buffer RV_BELEG (by default SAP delivers it with not buffered setting, but some companies change that for performance reasons), switching to non-buffered only for the specified billing document types in this company codes is also possible.

If it is a one-time adjustment and sequential numbering is not required for legal reasons, I cannot see how using a completely new number range interval without overlap could cause problems for the documents already billed.

I would not change the current number for the old interval to zero - who and why advised you to do that?

But just for you to feel safer - test that in a sandbox and you will know .

[jignesh_mehta3]

Hello Ganesh,

Unless it is a legal requirement to have year specific number ranges for SD Invoice documents, I would not suggest to go for it. This is so because over a period of time (I mean after a few years) it becomes very difficult to find empty number range slots and number ranges becomes confusing.

Also this will bring possibilities of new requirements like having company code specific Invoice number ranges and so on.

Thus it make sense to discuss with business / steering committee and decide to have sequential number ranges for SD Invoice documents over several years.

Thanks,

Jignesh Mehta