cancel
Showing results for 
Search instead for 
Did you mean: 

DST - Choose the key from the allowed namespace

Former Member
0 Kudos

Hi everyone. I am trying to add the new Timezone setting as per note 919538.

When I do, I get a message "Choose the key from the allowed namespace". Another search in OSS said that this can only be correct with a support pack.

Does anyone else have experience with this or seen this error?

Thanks!

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

That also gives me the namespace error

Former Member
0 Kudos

Hello, Chuck

I ended up using note 198411 and uploading program ZZCUIM_46C.abap. Using this program, I was able to apply DST data to my clients. It worked well. On my first attempt I did not include file name in the directory path, this was wrong. With the file name (tzdata.dat) as the part of the absolute path, entered as a parameter, program worked well.

SAP answered that that problem we encountered while trying to manually enter data is happening in some versions, but can be avoided. They did not tell me how as of yet.

Thanks

Galina

Former Member
0 Kudos

Chuck,

Just start from scratch you'll fix it.

1. add the values as per note + enter

2. if you see 1st 2 feilds highlited - > click in one of thenm + enter

3. SAVE

4. create Transport request

Hope this solves your issue.

Uday

Answers (5)

Answers (5)

Former Member
0 Kudos

OK, those instructions worked PERFECTLY Uday.

Thanks!

Former Member
0 Kudos

Chuck,

For manual entry:

After I tried to Save and got this message, I had to hit Enter, and everything worked.

This was the same SAP told me to do.

Thanks

Galina

Former Member
0 Kudos

None! I was able to encapsulate the change into a transport, but it seems to have happened when I just messed around with it. I am not sure on the procedure I used to do so?

I have three other systems to do, and it is proving to be the same challenge.

As I mentioned, the odd thing is that I am having this issue on all systems. Even ones that are independent from the other ones.

Hopefully someone has a solution for this!

Former Member
0 Kudos

Hello,

I have the same problem. I asked SAP this question. Now I am waiting. If there will be any response, I will let you know.

Galina

Former Member
0 Kudos

Hi friends,

The problem is , may be you are all trying to click " SAVE" after doing all the entries.

1. Do all the entries

2 Click Enter ( or) that green tick mark on the top left corner next to the place where we put the TCODE.

You will get the transport request for the change you have made

Hope this helps, points are appreciated

Uday

Former Member
0 Kudos

Re: DST - Choose the key from the allowed namespace

Posted: Mar 6, 2007 6:36 PM in response to: Galina Savikovsky

Click to reply to this thread Reply

Hi friends,

The problem is , may be you are all trying to click " SAVE" after doing all the entries.

1. Do all the entries

2 Click Enter ( or) that green tick mark on the top left corner next to the place where we put the TCODE.

You will get the transport request for the change you have made

Hope this helps, points are appreciated

Uday

Former Member
0 Kudos

Also Note :

In connection to the message above.

The tables for time zone customizing are client dependent and therefore it is necessary to change the time zone settings in each client to Receive a correct date/time calculation. It is necessary to update the DST rules in all clients including 000 001 and 066.

Former Member
0 Kudos

I am not sure WHERE to enter in ZZ or YY?

There is nothing in the documentation on that? I am following note 919538.

I also have a 4.0b environment which I tried this note and got the error message in that environment too!

Former Member
0 Kudos

Chuck,

I have the same problem. Any solutions from your end yet?

Former Member
0 Kudos

I am also getting the same error. I have filled in all the fileds correctly. For most of the fields there is a pop up list but for they year we had to key in manually.

Please help.

Thanks

Sumit Mathur

Former Member
0 Kudos

Hi

Generally this error pops up when we define the New field without USING "ZZ" or "YY"...

If you are creating with "ZZ" then i am not sure of the issue?

Thanks