Document Number Already assigned error...?

[Former Member]

Hi Gurus,

I am trying to create a document in FI but whenver i enter all valid values and try to post it says document number already assigned...the number range is not getin refreshed...

I am new to this so if you cud provide me detail steps on what can I check or do to resolve this issue...

Please provide some inputs...

Cheers:

Sam

[Former Member]

Hi,

You can go transaction SNRO to check the number range for the corresponding object name of FI document.

If you are not familiar with FI number ranges, please ask FI functional folk for help to enlarge the number range.

Here is online document for number ranges.

http://help.sap.com/saphelp_47x200/helpdata/en/2a/fa02e3493111d182b70000e829fbfe/frameset.htm

Regards,

Ferry Lianto

[Former Member]

Thanks for the response ferry...

Actually here the situation is that we are using BAPI BAPI_ACC_DOCUMENT_POST for posting FI document....but it gives this Document Number already assigned...It is not getin refreshed...I looked at the FM number_range_interval_init for resetting the number range but then it will reset the entire number range....

I am not sure how to proceed on this ....

[Former Member]

Hi,

I am afraid that document number range was exhausted and the system is recycling the document number.

You need either to expand the number range or archive the FI document number.

Regards,

Ferry Lianto

[Former Member]

Thanks Ferry...

What do u mean by archive the document number...

The system is not able to recycle the document number i think..?

we can expand the number range but when it goes live...do u think this issue will happen again...

I men i dont want in production that we face the same issue...

Thanks

Cheers:Sam

[Former Member]

I'm with Rob on this ... what does happen when you try exactly the same document posting manually through FB01 or similar? The message you describe sounds more like you already have a document "NNNNNN" in your system, and that (justifiably) the processing in the BAPI has stopped.

I've seen this type of thing happen in Dev systems in particular where number ranges and document stores get mis-aligned through client copys and manual "accidents". So my suggestion would to be to try FB01 manually, and check the values in SNUM for the number range object your document should be using, and check that BKPF doesn't already have that number.

Jonathan

[Former Member]

What happens when you post the same document manually?

Rob

[Former Member]

Hi,

What do you mean by archive the document number?

Basically, it will delete/remove the SAP document from system (transaction SARA).

The system is not able to recycle the document number i think?

That is way you got an error message the document already assigned when the system trying to recycle the number.

We can expand the number range but when it goes live...do you think this issue will happen again. I meant I dont want in production that we face the same issue.

No need to worry. This is FI functional folk job to ensure the document number range is not exhausted in production. This is not your responsibility as developer.

Regards,

Ferry Lianto