Number range reset to issue in solman 7.1

[Former Member]

Hi,

Currently i am working on ChaRM configuration in solman 7.1.

I am trying to reset the number range /TMWFLOW/M object(Maintenance Project) .

Currently showing number range interval

From number : 000000000 To Number : 099999999 Current Number : 79

I tried to reset the Current Number : 0. But it showing error "Please enter From-number greater 0".

So i tried to change the number range From number : 000000001 To Number : 999999999 , again it showing error "Lower limit can only be changed during initial entry"

Due to this issue i am not able to create task list in maintenance project. It showing " Internal Phase

Controller Problem" error.

So please give some idea to reset the number range.

Rg,

Karthik

[Former Member · Accepted solution]

Hi,

we had the same problem and we are on SP3. We couldnt create any more task lists.

We were told to create an OSS message for that problem as it is allready known.

The SAP developer corrected the number range in our system.

Sorry but that is all i can tell you.

Regards

Daniel

[Former Member · Accepted solution]

Hi Daniel,

SAP developer reset the number range, also upgrade to solman 7.1 SP3.

But still i am getting " Internal Phase Controller Problem" during creation of task list in project( solar_project_admin).

Also i am not able to find any log in SLG1.

Any one face similar issue during creation of task list?

Rg,

Krthik

[Former Member · Accepted solution]

Have you since the adjustment in the table I suggested, created a new project? We just created a new project and that took care of that. All existing projects/ cycles still will have that inconsistency.

[Former Member · Accepted solution]

I created new project and tried the same. Still i am getting same issue.

[Former Member · Accepted solution]

have you tried to use the number after 79 or the range which not yet used?

Thanks,

Jansi

[Former Member · Accepted solution]

Any updates? What did Dev Support finally say?

[Former Member · Accepted solution]

Hi,

Issues are fixed by sap.

1. SAP reset the number range.

2. "the creation of Maintenance Cycle and Tasklist had failed because of

a wrong entry in table bcos_cust. RFC Destination " NONE" (with a leading SPACE) instead of "NONE".

Therefore the creation of Tasklist and Maintenance Cycle failed."

Rg,

Karthik

[Former Member · Accepted solution]

Glad its fixed! But error in BCOS_CUST??

[Former Member · Accepted solution]

Bumping this, because I am getting this in Sp5 now,

Seems this error tracks me down every alternate Sp!

[Former Member]

Hi,

it should accept 01,Please try out , enter 01 in the from number column and enter F4, find out what is the value coming at input help, try to use that.

other way since you already used till 79, use the from number as the one which not yet used.

Please check and update.

Thanks,

Jansi

[Former Member]

Hi Shivjansi,

I am not able to find any input help available in my system.

So i created number range as 02 for certain interval.

So i need change the transaction numbering in SDMM and SDMN like 02?

Rg,

Karthik

[Former Member]

I vaguely remember having this problem during Ramp Up (or a similar problem). Are you on SP3?

This is how I fixed it:

As you have already tried it is not possible to edit the lower

value in the number range from tranx SNRO; but you can edit

(via debugger) the corresponding entry in table NRIV.

( please only do this only if you are absolutely sure what to do ).

The problem can only occur in newly installed systems with

a old version of the note 1576472; But since June, I believe there is a new corrected

version of this note. so ideally this problem should not occur anymore. Which Is why I asked if you are on SP3.

Hope that Helps!

Cheers!

[Former Member]

Hi Invycktus ,

Currently I am having Solution manager 7.1 SP2 version.

So this issue on SP2 version?

Also i am using SP3 version of some other solution manager landscape. but we didn't face any issue on number range assign and task list creation.

I will try the work around and get back to you.

Rg,

Karthik

[Former Member]

Sp2 is where I had this issue at one instance, that is what I remember.

Let us know how it goes!