Error when creating a Number Range

[Former Member]

When I use transaction ZNRO to create a number range, I get an error message:

"Invalid call sequence for interfaces when recording changes".

All I did was enter the text and a domain for the numbers. There was an earlier error regarding buffering. It said that I should not use buffering for accounting documents. I am not using this for accounting documents and do not care if numbers get skipped. So I continue through that error.

But after that, the "Invalid call sequence . . ." error pops up.

I searched this forum generally, and with portions of the error text, and do not find any discussion of problems creating number ranges.

The number range I'm created is very simple. I just need "one up" numbers for a custom database used to store custom schedule information.

I'm at release 4.6c.

[Former Member]

Waht message ID and number is this? Is there a long text for the messagte?

Rob

[ibrahim_u]

Is it customer program ? Normally standart transaction is SNRO as you know. If there is a SNRO transaction, try with it. If you getting same error, you can tell message number and class us.

ibrahim

[Former Member]

Here is the error message and text.

I have no idea what it means by "interfaces".

When at release 3.1i, I had no trouble creating number ranges.

<b>Message no. TK 425

Diagnosis

The function you selected uses interfaces to record changes made to your objects in requests and tasks.

Before you save the changes, a check needs to be carried out to establish whether the objects may be changed. This check must be performed before you begin to make changes.

System Response

The function terminates.

Procedure

The function you have used must correct the two Transport Organizer interfaces required. Contact your system administrator.</b>

[Former Member]

It says to take it to the system administrator, so show it to your basis people.

It looks like it's trying to create a transport but can't because of some problem with the transport system.

Rob

Message was edited by: Rob Burbank

[Former Member]

We had the same problem in our 4.6 C system.

We applied SAP note 847490 with a correction today - after that Number range creation via transaction SNRO worked!

Hope that helps, regards Carsten