Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Create Infoset

Former Member
0 Kudos
589

Hi,

I have provided access to Tcode SQ02 in our Production client to the users...

When they are trying to create an Infoset "Changes to Repository or cross-client Customizing are not permitted"

I have checked the client settings.. It is okie...

Are there any other changes to be done?

Thanks,

RaHuL...

1 ACCEPTED SOLUTION

alaindewitte
Discoverer
281

Add user parameter AQW (value empty) to the user or in TR SQ02 select standard query area.

(default is global query area, but this is not possible when client is closed)

Ragards,

ALain De Witte

8 REPLIES 8

pradeepmathewch
Advisor
Advisor
0 Kudos
281

Hi,

Are you sure that you checked the client for the correct client?

Thanks and regards, Pradeep

sdipanjan
Active Contributor
0 Kudos
281

Where did you check the client settings? Also, what is the version of your system? If the "Cross-client object changes" is set to allowed as you mentioned then you can have a look on the following SAP Note.

[Note 627499 - SAP Query: TK 730|https://service.sap.com/sap/support/notes/627499]

Regards,

Dipanjan

Former Member
0 Kudos
281

Hi,

Thanks a lot both for your reply...

Same Client settings are working for me in different landscape...

This is for ECC 6.0 and not for 4.6B and so Dipanjan your note doesnt help...Thanks anyway...

Is there a table entry to be made probably for that user..

Or may be SE06 - System Change Option...

If yes? Does anyone know...

Thanks,

RaHuL...

sdipanjan
Active Contributor
0 Kudos
281

>

> Is there a table entry to be made probably for that user..

>

No.

> Or may be SE06 - System Change Option...

>

In production, your system change option should as you got the message. But in Dev, the Cross client & Repository changes should be allowed.

> If yes? Does anyone know...

>

Ask your BASIS team to check in Dev. Maintain/Create Infoset in Dev and Transport it to Production.

After allowing if you get any authorization error for the user, run a trace by using ST01.

Regards,

Dipanjan

Former Member
0 Kudos
281

If it is creation of infoset in reference to production system, then definately you'll face this problem.

we generally have such issues, where most of the users do face this problem, the only solution is to get a service window( SE06> set all the components to be modifiable and SCC4> client specific and croos client specific should be set to changes allowed, save these setiings). you shoul dbe now able to create the infoset in production system.

But do remember to close the production system( All the settings from SE06 and SCC4 should be set as they were before) after the changes.

Regards,

Sarita

0 Kudos
281

Thanks for the reply...

We have another production server where users are able to create query/infoset with the same client settings and also SE06 system change options...

There should be some exception or settings for production client for creating query/infoset..

Settings i have checked are of R/3 4.6B and this issue is in ECC 6.0...

Can there be any difference in these two versions...

Thanks,

RaHuL...

0 Kudos
281

Hi,

The very first thing, infoset creation is meant for BW systems only, it is totally irrelevent for R/3 systems.

Secondly, infoset creation must be done in devlopment system only and from there it should be imported to quality and production systems( it keeps your dev, quality and prod systems in sync).

Are you trying to create the same in your BW production system,

If you can create in development and then import it to production system, that would be the best practice, and if the creation can only be don ein prod systems you should go for the service window as I suggested earlier.

Regards,

Sarita

alaindewitte
Discoverer
282

Add user parameter AQW (value empty) to the user or in TR SQ02 select standard query area.

(default is global query area, but this is not possible when client is closed)

Ragards,

ALain De Witte