Object Changeability

Hello,
I was looking at our Production BW system. I was told that the system is <i>globally</i> set to "not changeable".
However when I look in 'Administrator Workbench: Transport Connection' and I click 'Object Changeability' everything in there is set to 'Everything Changeable'
My question is - How does this effect my transports and my ability to collect objects and transport them into production from my Dev box?
Thanks Nick

Hi
It does not affect the ability to transport from D->Q->P.
It just not allowing to make direct changes to P.
In your D sys you can make any changes you like, and then transport it thru the lndscape.
Sometimes it is helpfull to make changes in P, mainly in day to day operations such as Activating Objects and fixing data loads.
Reg's
Edan

Similar Messages

Query created in production system and object changeability

Hi,
The production BW has the object changeability for query elements set to 'Changeable original'. Some queries which have been created in this system can be changed, others, which have also been created in the system, can not.
All queries are assigned to the development packate $TMP. None of them have been transported anywhere, nor have they been created somewhere else and transported into the system.
The system is BW 3.5, SP 17.
Has anyone got any idea what the problem could be?
Best regards,
Rita

Hi,
The object changeability in the system is set to 'Changeable Original' and I know where to switch from 'not changeable' to 'changeable original' to 'everything changeable'.
The normal development cycle sees reports being created in the development system and then being transported through to the production system. Here, they should not be changeable. However, users with the relevant authorisation should be able to either -
- create new copies of these reports and change them or
- create new ad-hoc reports and also change these
We have several of these reports on the production system. The object changeability is set to 'changeable original', as I mentioned. I would expect that all queries which have been created on this system and never transported (either in or out of the system) should be changeable, based on this setting. However, some are, some ar not. The error message when trying to change the 'non-changeable' ones is 'Operation falied! No error message available from the server'. If I make a copy of one of these queries, hoping to save is as an ad-hoc query and change it, the error message is 'query could not be saved due to a problem in transport'.
How come some can be changed, others can't? Is there anywhere I can check what the difference is between the changeable and non-changeable reports which have been created on the system?
Best regards,
Rita

Is there a way to add new objects to object changeability list?

My production system is locked and I need to change object type RSFO (formula). I looked at the object changeability list and it does not contain RSFO. Is there a way to add this object to this list so I can change it directly in production? Thanks.

hi,
I hope you can create similar formula in the production. as in the production we can change the reports,proces chain,aggregates, infopackages.
Ramesh

SCC4 and Object Changeability question

Gurus,
Note - Please do not send me links ,which has no reference to my questions whtsoever,pls provide me direct answers to the questions if possible.
1)do you need to open the system using SCC4 in order to make the "object changeability" option work??
2)what is the relation between SCC4 and "object changeability"
3)Can the Infopackage transported from dev to prod be changed with "object changeability" option??if yes how ?
or only object created in the production local be changed using "object changeability" option
or i can only change the transported Infopack in production using SCC4 ,system open
thanks in advance.

1)do you need to open the system using SCC4 in order to make the "object changeability" option work??
ans) Pre-requisite -Close the system
2)what is the relation between SCC4 and "object changeability"
ans) Objects of the selected object types exist in your system as changeable with "object changeability option" even if this system is globally set to not changeable.
3)Can the Infopackage transported from dev to prod be changed with "object changeability" option??if yes how ?
or only object created in the production local be changed using "object changeability" option
or i can only change the transported Infopack in production using SCC4 ,system open
ans)"Choose Original Changeable" If you not only want to make objects which are generated in this system changeable, but also those that were imported. This option is required, for example, if you need to make repairs or want to change flexible starting times. Note: New imports can overwrite the changes again
I would advocate to read this link carefully -
http://help.sap.com/saphelp_nw04s/helpdata/en/0e/a7343e8c7f6329e10000000a114084/frameset.htm
Hope it Helps
Chetan
@CP..

Authorization Restriction for Object Changeability :

Hi ,
How to restrict users from using Object changeability in Production System if they are given access to RSA1, even though the system is completely closed , with Object changeability, the users can still create a new Info package and upload data ?
I have gone through the SDN and SAP documentation, but I could not find any such references.
Looking forward to your valuable input on this.
Regards,
Ahmed.

Hi there,
You have an authorization object named S_RS_ADMWB (Data Warehousing Workbench - Objects).
You can with that object restrict the several activities (display, execute, create, etc.) for different Datawarehouse InfoObjects (InfoPackage, etc.).
Try to restrict that to the users.
Diogo.

Object changeabilty RSA1 transport connection object changeability

Recently We have been asked to open (make changeable) the
workbook and query view. this is so users can save a workbook or query view from a workbook. is there any best practices on these objects or information on what issues can result by making these objects changeable. Also is there any security that can be assigned so this is not opened to everyone ?

Hi there,
I have a similar issue but around saving the BEx reports as favourites.
One of our user is not able to save his report in his favourites folder. He was able to
do the same before,but now he can't do it anymore.He gets a error stating 'BW server connection error....' and a VB pop up 'UPDTT' type....This is a problem with only few users and not all of them.
I know we can set the object changeability in RSA1 but that should affect all or none of the users as it is set globally.So,is it possible that I can check it somewhere if that user does have the authorisation for saving the reports as his favourite. There is no direct authorisation problem with his userid as I have checked the SU53 dump also with his logon.
rgrds
Umesh

Object changeability in transports

Hi experts,
i am new to transports, and would like to know, objects can be changed after transportation , wt i mean we can change in prod.. as QA , but we hav option to set the object to notchangeable , where do u set and how do we set it...
*points surely assured*
Regards
Rekha

Hi Rekha,
Objects changebility means not changing the transport request objects.
Once we can import the request in QA/Prod. we can't change those objects directly in QA/Prod.
Objects changebility means genearlly Infopackages, aggregates , process chains and few objects we can change in QA and Prod as well as.
This option we can see in RSA1 -- Transport connection -
there is the option available "object changeability ".. If you click that button we can see the objects which r changeble and which r not changeble.
if u want to change any non changeable object, give the context menu on that object then get a option <b>EVERY THING CHANGEBLE</b> .
Regards,
venkata Sharma.

Object Changeability for Transformations

Hi experts;
I just create one Open Hub Service in DEV system, with transformation and DTP and it works fine.
Due to customer requirements, the path of the file changes according with the system. So, I'd create several files and several paths.
After transport to QAS, I change the Object Changeability for Open Hub Destination (DEST) into "Everything Changeable" and was able to change the file name and activate it.
However, the transformation and DTP become inactive.
I notice that there is a option in Object Changeability for DTP but not for Transformation (well, nothing indicates that is a transformation).
Can you help me activate the transformation (without ADM open the system)?
Thanks & Regards;
Ricardo

Hi Ricardo,
If you have indeed decided to have transformations changeable like DTPs and Process chains in your non-DEV system, the workaround is to have the CHNGPRODFL field changed to "X" in the RSTLOGOPROP table. Once you have done this, this will be like any other changeable object and you can set it to "Everything Changeable" or "Changeable Original".

Recommendation needed on: Locking Down BW Client / Object Changeability:

Hello Experts,
We recently had a problem on our production box and we found the need to lock down the environment with scc4.
We further used object changeability to control the environment and it has been hell ever since. Users have had difficulties running queries, etc.
In a typical BW production environment, what is the approach and what is the common practice?
(Please for each recommended approach include any command you mention)
For example, what transaction do we use to see various users and their authorizations, etc. Who made modification on which object, etc.
Thanks.

Hi Amanda,
In SCC4, you should maintain following values.
Under
>Changes and transport for client specific objects
no changes allowed
under
>Cross client object changes
no changes to repository and cross client customizing
objects
Under
> Protection : Client copier and comparison tool
Protection level 1: NO OVERWRITING
Regards
Sriram

Object changeability: why are some queries now unmodifiable..?

Hi Experts
I recently had BASIS open our BW Production client so I could activate a cube that had been deactivated after a transport to BWP. Then BASIS closed the client (setting = unmodifiable).
After this, some queries in Production are now not available for change. We get this message:
Diagnosis
You want to change objects although the system setting is "Not Changeable".
System Response
The objects cannot be changed.
Procedure
Change the setting for the system or client to "changeable". You can do this using transaction SE06 or SCC4.
For some reason this only occurs for some queries, not all. Some are OK to change, just as they were before.
The client settings are unchanged. I have checked the object changeability options in the Transport Connection - just about everything is set to Everything Changeable or Changeable Original.
Why have some of our queries suddenly become non-changeable??
Points will be given of course for any advice. Thanks in advance
tony

Gents
Thanks for your replies. Unfortunately, none of these suggestions made any difference to the problem although they were good things to check.
It turned out that there was role that had changed, and the cause of the problem was simple authority. The message about the client needing to be opened was a Red Herring..
Bad messaging on SAP's part.
Once again, thanks for your help.
tony

What is object changeability in Rsa1 Transports?

Hi all,
Can anyone let me know the significance of Object changeability found in transaction code rsa1 (transports). can anyone explain me with an example.
thanxs & regds
haritha

Hi,
It allows you to change the objects, if you select the objects here like aggregates, process chains and info packc etc. generally we dont have authorization to change the objects in prodution system, but for few objects like process chians, info pack we need to schedule as per the requriment for this we have to change the existing selections for ex: in quality we are executing a process chian daily once, but in production we have to run it hourly with object changebility option we can do this, same way for info packs.
Regards
Sankar

Prevent creation of additional common objects at the same time ...

Context: A Super User group may require to be allowed to create and/or change queries in Production
Would be possible to prevent creation of additional common objects like rectricted and calculated key figures and variables at the same time allowing creation of queries in terms of dragging and dropping filters, free characteristics, rows and columns?
I know that keeping the system closed to changes and using the transport connection Object Changeability it is possible to restrict change of query elements to those that are original in the system.
Points will awarded.
Thanks
Mathew.

In transport connection Object Changeability, you can only set query elements as modificables but you cant distint between diferent query elements (queries, calculated/restricted key figures, structures, etc).
You can do that distiction in authorization object in rs_comp and rs_comp1.
You should combine transport connection Object Changeability and authorization objects in roles

Object ISIP not modifiable in QA

Hi All,
As all of you may know in spite of the fact that the system has been closed (SCC4) and also whether the system change option is set to not modifiable (SE06) it is possible however to allow certain objects to be changed. In this case I am trying to allow changes to any infopackage. In order to perform this action I have set up the object type ISIP --> InfoPackage as "changeable original" through the object changeability of the transport connection.
However, I still having problems while trying to change my existing infopackages. I am still receiving the following message:
"The system and namespace change option set for this SAP System does not allow any changes to be made to object ISIP"
Did anyone have this problem before?
Thanks,
José.-

Hi All,
Just wanted to share with you the solution that I've found to this problem. Indeed the problem was related to a bug it seems to exist in some versions whereby using the button "switch changeability" does not work (it shows like it has changed but it does not). Instead of this button, better right click on the column and choose the corresponding option.
It worked, so I will close this post.
Thanks anyway,
José.-

Can we lock down the system for BW object and not bex objects

Hello,
I have a question about object changeability. We want to lock down the BW production system but leave it open for adhoc query. Can we lock down the BW system only for few objects like Cubes, ODS, Infoobjects, Infosets, Multiproviders, and keep the system open for Bex objects like Query, varaibles and also for Infopackges and DTP's.
Which tcode can we use for this ?
Thanks,
Message was edited by:
Kiran Mehendale

hi, usaully production system will be non changeable for all objects.. but as far as SAP BW is concerned we can make certain objects changeable by setting as follows..
in production go to RSA1 - Transport Connection, select Object changeability button from tool bar, here you will find a list of objects which can be made changeable in a closed system.. just click on required objects and set it to Everything Changeable..
Reg,
Pradhiba
<REMOVED>

What BI-object must be changable when saving a Broadcasting object ?

HI,
I want to save a Broadcasting-Object (e.g. a query with given variables using e-mail).
Before I can schedule the job, I have to save my settings.Whenever I try this, it's telling me that the system is not changable and I need to open it by using SCC4 or SE06.
It's our Production System, therefore I don't want to open it generally, but I certainly can open the object(s) which would allow me to save my Broadcasting settings..
Would anyone of you know, what I have to open. ?
Thanks

Have you tried changing the BEx Changeability settings for Broadcasting objects in the Transport Connector?
RSA1 -> Transport Connection -> Object Changeability -> BRSE (Broadcast Setting)
If you change this to be changeable you should be able to save new Broadcast Schedules.

Object Changeability

Similar Messages

Maybe you are looking for