cancel
Showing results for 
Search instead for 
Did you mean: 

Number Ranges

Former Member
0 Kudos

Dear All,

In System configurations, we do not transport Number ranges from Golden to DEV, Q and Prodn and create them individually in the respective systems. Is there any specific reason why we do not do that, even though we can Transport them through requests.Please explain me.

Is there any SAP document that says you should not transport them. Please forward the same or forward the link for that.

Samar

Accepted Solutions (0)

Answers (4)

Answers (4)

rupesh_brahmankar3
Active Contributor
0 Kudos

Dear,

Number Range has to be maintained individually in each client.

Pls refer OSS note 1290138 and 165792

Regards,

R.Brahmankar

rupesh_brahmankar3
Active Contributor
0 Kudos

Dear,

Number Range has to be maintained individually in each client.

Pls refer this link,

[Link|]

Regards,

R.Brahmankar

former_member199502
Active Contributor
0 Kudos

Hi,

refer this link.

http://help.sap.com/saphelp_nw04/helpdata/en/1f/83112d4bc511d189750000e8322d00/content.htm

It is always advisable to do in individual client system bcos when u transport first it will deleate the existing entries and then transport the changes.

Hope it is helpfull

Former Member
0 Kudos

Hi,

IT is recommend that you create the number ranges individually in each client rather than transport them. This is because if you transport the number ranges, you could cause a problem with duplicate entries in the database. If this situation happens, the SAP program will abort and the data will not be saved.

For example: In client 001 you have a number range from 0000001 to 9999999. The current number is 000084. In client 002, you have the same number range, but the current number is 0003429. These represent records in the database. Now you transport from 001 to 002. Your new starting number is 0000084 in client 002. When you try and save the record, the system assigns 0000085 to the document. But document 0000085 already exists in the database. The transaction terminates with an error and the data is not saved.

Regards,