Resetting number ranges through SNRO

[Former Member]

Client Copy: Each time a client copy is made, material movement postings cannot be processed until several number ranges are reset and the user gets the message Express document “update was terminated”. These number ranges can be reset thru SNRO. But identifying what objects need to be reset also difficult. I don’t know how to identify what objects need to be reset the number ranges for the problem. This problem occurs each time a client copy is made (The user faces). Does anyone know what each object in that table? Where can I find the descriptions of each object? How do I know what objects need to be reset?

Thanks,

Sobhan

[Manohar2u]

one way is to keep a break point in numbergetnext fm, as the object names are hardcoded (likely i guess) in respective programs.

Regds

Manohar

[Former Member]

Hi,

You can find the objects in the table TNRO and texts in TNROT table.

I created a goods movement using MIGO and it hit the following objects

MATBELEG

RF_BELEG

Thanks,

Naren

Message was edited by: Narendran Muthukumaran

[Former Member]

Hi Narendran,

Those texts are not enough to make a decision that this is the object that needs to be used for a particular teask such as purchase order creation.

Precisely, is there some document explains, this object is used in conjuction with a particular task such as creating a purchase order.

Thanks,

Sobhan.

[Former Member]

Hi,

I created a goods movement using MIGO and it hit the following objects

MATBELEG

RF_BELEG

Thanks,

Naren

[Former Member]

Narendran,

Thanks for the help. How do you find that creating a goods movement hit the mentioned objects?

Thanks,

Sobhan.

[Former Member]

Hi,

Check the table T003M for the number range intervals for each transaction / event for goods movement.

Thanks,

Naren

[Former Member]

Debugging..

[Former Member]

Narendran,

I understand your point. How can user identify these are the objects need to be reset the ranges?

Thanks,

Sobhan.

[Manohar2u]

Another way is to get the objects from respective SPRO number range settings.

Regds

Manohar

[Former Member]

Hi Manohar,

Can you give me the path for SPRO number range settings?

Thanks,

Sobhan.

[Former Member]

Standard SAP transaction for setting up the number ranges for the material document MBNK. This transaction has the number range object MATBELEG.

When I debugged the accounting document number range object RF_BELEG was also called. As the accounting document will be posted immediately after the material document.

So I believe you have to reset the object MATBELEG for the material document.

Hope this helps...

Thanks,

Naren

[Manohar2u]

normally even number range settings will also be copied...and the target client can be used direcly with out any manual configs or changes.

Regds

Manohar

[Former Member]

How come your number ranges are not being replaced when you did the client copy?

[Former Member]

The number ranges are also replaced. My basis admin told me that table NRIV is copied. He says if there is a update during the backup (in the production), these updates won't be in the backup. He copies this backup into test system. I am not even clear on this point.

Thanks,

Sobhan.

[Manohar2u]

then get the dump of that table from production and update in this new client programatically.

Regds

Manohar

[Former Member]

How can I get the dump of the table? How can I update the table in the target client?

Thanks,

Sobhan.

[Former Member]

How can I get the dump of the table? How can I update the table in the target client?

Thanks,

Sobhan.

[Former Member]

How can I get the dump from souce table? How can I update the table in target?

Thanks,

Sobhan.

[Former Member]

How can I get the dump of the source table? How can I update the target table?

Thanks,

Sobhan.

[Former Member]

> The number ranges are also replaced. My basis admin

> told me that table NRIV is copied. He says if there

> is a update during the backup (in the production),

> these updates won't be in the backup. He copies this

> backup into test system. I am not even clear on this

> point.

>

> Thanks,

> Sobhan.

Here is the explanation. You take a backup of your production system at a point of time X. At this time, NRIV table has a value of 12345 for document X. Now you refresh your test system with this backup. So your NRIV table in test system will show that the next number available for document X is 12345. Now you create a new document X in test system. It should get the number 12345 allocated to it.

I don't see why it is dumping in your case, unless they are applying different backups to test system in phases like taking a backup of say number ranges at one time and applying that first to test system. In that case, your test system will have the next number at 12345. Meanwhile documents are being created in production and the next available one in production may be 12349. Now basis takes a backup of the documents without the taking the new NRIV backup and apply that to test system. Now in your test system you have documents 12345, 12346, 12347, 12348 while the number range says the next available number is 12345. That is where the dump happens.

Check with your basis if they are doing it this way. If they take one backup for all and apply it, then there should be any problem.

[Former Member]

Hello Srinivas,

Thanks for the analysis. I requested my Basis admin to do a homogeneous copy from production to test. After he copied, I will test it and close the thread. Until that I will keep the thread open.

Thanks,

Sobhan.

[Former Member]

Hi,

Please see my earlier reply.

Thanks,

Naren

[Former Member]

Standard SAP transaction for setting up the number ranges for the material document MBNK. This transaction has the number range object MATBELEG.

When I debugged the accounting document number range object RF_BELEG was also called. As the accounting document will be posted immediately after the material document.

So I believe you have to reset the object MATBELEG for the material document.

Hope this helps...

Thanks,

Naren