Client Settings non modifiable for ob52, ob58 etc

Certain objects in the IMG need to be modifiable in all our clients, specifically transaction OB58 (maintain financial statement version).
Currently, any updates to the standard financial statement (for example, when a new G/L account is created and it does not fall in an existing range) have to be made in the config client and transported across. However, the Financial statement version is not real config, nor is it master data, and we should be able to update it as and when G/L accounts are created.
We can do this in Production but not in our QA clients (it says the client is non modifiable), Production client is also non modifiable but the client role is 'Production', so I presume this client role allows the changes in the operation client.
Is there anyway to modify these in a client that is non modifiable such as our QA and testing clients with making the client modifiable?
We are running ECC 5 on NW04.

Similar Messages

Client reporting non-compliant for unknown reasons

I have a single workstation MBAM test environment, and for whatever reason I cannot get this workstation to appear as compliant with policy. According to the reports, the OS drive (the only drive) is non-compliant, however all of the settings seem
to match. I don't see any errors in the event logs. Can anyone see anything I might be missing?

Gaurav, the client settings were matching the policy. I took nearly all configurations out of the policy to make sure I wasn't missing something.
slaplace, the hotfix looks like it might take care of it. I changed the policy to only require AES 128 bit w/ Diffuser (while the client was encrypted AES 256 bit w/ Diffuser), and the client came back as compliant. I will set policy back to
256 w/ Diffuser and verify the client comes back non-compliant again, then will apply the hotfix and see if that fixes it.
Will let you all know how it works.
EDIT: Applying the hotfix to the client fixed it. The client now reports compliant using 256 bit w/ diffuser. Thanks everyone.

Problem releasing webservice for runtime in non-modifiable client

Hi
I created a webservice definition ( virtual interface & all dependent objects ) in a development client ( client- A ) of a ECC5.0 instance.
Now, we have another client ( client-B ) in the same server that we want to release the webservice for SOAP runtime. ( reason is that the webservice is not available at runtime in this client-B client )
This client-B has status - non-modifiable and hence cannot use WSCONFIG --> create option to release it for runtime.
How do we release this webservice definition to client - B . I tried a SCC1 transaction on client-B pointing to the transport that contains the WS definition in client-A. I got dictionary errors indicating that the WS definition objects are all client independent.
Is there something I am missing ? Any thoughts/similar experiences shared is appreciated.

Good to hear it worked out for you. But like I already said, I haven't experienced anything like this, but for similar problems this is exactly what we did to solve it. But you're probably right, that this is no long term solution. There should be another way of doing this, but no experience in that field expertise.

RE: Client Not Modifiable for Z Tables

Hi all,
One of our developer created 3 custom Ztables, when he is testing in testing environment, he is able to modify 2 of them using SM30, but for one table it says "Client status not modifiable". i checked his profile and he got access to SM30 and also to S_TABU_CLI--> Allowed (X).
I dont know why it is not allowing this table to change and allows other tables to change ( I dont think this is any thing wrong with his authorization)
I also checked in SE11 and his delivery class is type "A" like the other 2 tables.
what else i need to check?
thanks,
Sun
Edited by: sun on Nov 19, 2008 3:53 PM

There was a little bug in SOBJ a while ago which let you change the owner of the object in a development system without transporting. But that should be fixed - as it is simply not an option anymore, also in a production system.
The better (more transparent) option in my opinion is to use the current settings flag if these tables are going to serve a "customizing" type function of the application and you want the flexibility to change them system specifically within your landscape without having to transport it and not wanting to open the (productive or test) client just to make a change of something non-critical for the application.
But you need to pick and choose them carefully. There are also some other settings which you might want to tighten the control on - for example very application sensitive master data.
Now I don't know what these tables are used for, but you did mention S_TABU_CLI being required so they are even client independent (most likely)... at least as far as their maintenance is to be concerned.
As you are asking this in the security forum (and not the ABAP or Data Dictionary forums), you might want to review the technical design of this solution...
It is not unknown that the developer and customizing roles find their way to production and used there with reliance on the SCC4 client settings either, and as these are client dependent... what are the settings of the other clients and the authority of the users in them?
But that is up to you. Certainly training and experience helps as well (which includes learning the hard way
I prefer the current settings to the client settings where the "use case" is justified.
Cheers,
Julius
ps: The one table which could not be changed, was it being changed from a different client than the other two?

Client non-modifiable Warning while execution of RFC

Hi All,
When we execute the RFC in our Test server, I am get following warning. This function module is trying to update the HR infotype data. As this is Test client, it is non-modifiable (from config point of view).
But why its throwing warning, when we change masterdata? Same thing is working fine in Production Server which is also non-modifiable. Please suggest the solution - Regards, Vinod
Message no. TK430
Diagnosis
The system administrator has set your logon client to the 'not modifiable' status.
Client-specific objects can not be changed in this client.
System Response
The function terminates.
Procedure
Contact the system administrator.
For more information, see the SAP Library under Change and Transport System.

Hi Sandeep,
Thanks for the reply, but I couldnt find any namespace properties for HR infotype objects.
Can you please specify the exact path.
Thanks- Vinod

Client Settings for SM 4.0

Hi Experts,
Can any one explain the client settings in Single SM land scape.
My solman is prompting for Transport Request while I do some SPRO settings.
What is standard client setting for single solman client.
Thanks
Samba

Hi Kata,
if you only have one SM client, you can change the client settings in SCC4 so as the system will not ask you for transport requests.
nevertheless, depending the number of people involed in working on the seetings of SOLAMN, i would recommend to set up the transport requests, just for the sake of keeping a better control of what is being modified, although these transport requests won´t be transported to any other system and/or client.
In my case, I have only one SOLMAN system, with only one working client. The majority of the SOLMAN customizing has been performed without having to store the information in transport requests although I have in SE06 the system set as modifiable, and in SCC4.
automatic recording of changes for client dependent objects
and "Changes to Repository and cross-client Customizing " option set in Cross-Client Object Changes.
This setting is not prompting for change requests when setting up SMSY (for example), but obligues me to register in transport changes any OSS Note which I have had to apply with SNOTE in order to avoid bugs. And this is very useful, becasue I know exactly how many OSS Notes and which ones I had to apply and when (although I won´t transport it anywhere).
Hope this helps
Antonio

I have a MacBookPro6,2 and would like to connect an older Dell flatscreen, model L17BNS. I would welcome any information about the type of cable I need and any settings I might need to change, etc. Thank you for your time.

I have a MacBookPro6,2 and would like to connect an older Dell flatscreen, model L17BNS. I would welcome any information about the type of cable I need and any settings I might need to change, etc. Thank you for your time! I really appreciate the assistance. Kathy

According to:
http://en.community.dell.com/support-forums/desktop/f/3515/p/19351107/19767627.a spx#19767627
It has DVI ports. This means you are best to use an adapter that supports DVI. Note there is no audio that carries over DVI. What you need is a mini-Displayport to DVI adapter, and the proper DVI cable. Since Dell doesn't have the specs, you'll need to tell us if you have pins or holes, and how many are grouped.

What are the settings for the "Default Client Settings"?

What are the settings for the "Default Client Settings"? I changed them instead of creating a new policy and would like to fix that.
Thanks
James A+, Network+, MCP

Hi,
The blogs below provides the default client settings.
Default Client Settings in SCCM 2012 SP1
http://prajwaldesai.com/default-client-settings-sccm-2012-sp1-sccm-2012-sp1/
Note: Microsoft provides third-party contact information to help you find technical
support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
Best Regards,
Joyce

How do I batch edit potos for contrast,sharpness,etc or permanently change the settings?

How do I batch edit photos for contrast,sharpness,etc or permanently change those settings?

There a 3rd party application, iPhoto Batch Enhancer, that can batch enhance, change contrast or crop. That's all.
However, once you establish the adjustments to one photo you can copy it via the Edit menu:
and then move to the next photo with the forward arrow and paste those adjustments in the next photo.
OT

Client Settings for Device collections Vs Client Settings for User collections

I noticed there are "Client Settings" set for each User and Group in SCCM. I want all my "Client Settings" configured by Device Collections not User Collections, what can I do? Can someone explain the difference between those?
Thanks
James A+, Network+, MCP

One is for user settings on a client and the other is for device settings on a client. As you can imagine user settings can only be deployed to user collections and device settings can only be deployed to device collections.
For more information about the user and device settings see:
https://technet.microsoft.com/en-us/library/gg682067.aspx?f=255&MSPPError=-2147217396
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

SLD Client Settings for ECC 6.0 IDES system

Hello Friends
I want to configure the SLD Client settings in teh ECC 6.0.
Can you suggest me the correct guide or steps to follow in order to proceed??
Thanks in advance.
Regards
Pooja

Hi Pooja,
Please refer to the document available @ below mentioned link.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50924080-0627-2a10-2b89-8cb87b972fb1
Page number 45 onwards will be useful for you. Please read & then perform
Also for more details refer System Landscape Directory (SLD)
NOTE : This is only applicable , if you are configuring SLD for NW 7.0 underlying engine.
I hope the provided information will help. Please revert for further clarification/details.
Best Regards,
~~ Pradeep Bishnoi ~~

Client settings in R/3 For Extraction to BW

Can any one provide what client settings on R/3 is required to Extract Data from R/3 to BW. any link or docs will do. can send on [email protected]

Hello PraKasH & L.E. HaarHoFF,
how r u ?
could me send ur gmail ID to my ID.... coz the files size is more than 20 MB.
[email protected]
Best Regards....
Sankar Kumar
+91 98403 47141

Solution Manager client settings (modifiable vs. not modifiable)

Does anyone know if Solution Manager 7.1 allows changes to the following object? Everytime we want to make a change to our template we need to open our Production system. This is a tedious task due to audit compliance.
System setting does not allow changes to be made to object SHI3 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
Message no. TO128
Diagnosis
The system and namespace change option set for this SAP System does not allow any changes to be made to object SHI3 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA.
System Response
Editing is terminated, the object can only be displayed.
Procedure
If you want to edit the object SHI3 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA in this SAP System, have your system administator set the SAP System to "modifiable" for this object.
This can affect the modifiability of the namespace &1 or the namespaces that correspond to the pattern &1, as well as the global setting of the system change option.
The system change option is set using the Transport Organizer tools (Transaction SE03). Expand the Administration node and execute the program Set system change option. The options are described there.

Does anyone know if Solution Manager 7.1 allows changes to the following object? Everytime we want to make a change to our template we need to open our Production system. This is a tedious task due to audit compliance.
System setting does not allow changes to be made to object SHI3 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
Message no. TO128
Diagnosis
The system and namespace change option set for this SAP System does not allow any changes to be made to object SHI3 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA.
System Response
Editing is terminated, the object can only be displayed.
Procedure
If you want to edit the object SHI3 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA in this SAP System, have your system administator set the SAP System to "modifiable" for this object.
This can affect the modifiability of the namespace &1 or the namespaces that correspond to the pattern &1, as well as the global setting of the system change option.
The system change option is set using the Transport Organizer tools (Transaction SE03). Expand the Administration node and execute the program Set system change option. The options are described there.

How to make a BW system non-modifiable?

Hello,
How do i do that? Also what if i have to keep only the infopackages open for creation?
Regards,
aby

Hello Abhijit
To make a SAP BW system non-modifiable you have to do at least the following:
1. TCODE SCC4 --> double-click on your client --> Changes and transports for Client-specific Objects should be set to No changes allowed.
2. TCODE SE06 --> click on System change option (you have to have the necessary authorization, or else you can not see the button at top) --> Set the global settings to non-modifiable (Be careful here: a. Software Component "LOCAL" has to have the status modifiable read more about it in the section about transports on help.sap.com. b. I will suggest that you take a snap shot of your settings before changing them to non-modifiable.)
3. Regarding your question about InfoPackages I will suggest that you watch Luis Orama's e-learning session about BW transports on this site. But a quick answer to your question is that this is possible.
TCODE RSOR (Transport Connections) --> Click on "Object Changeability".
Good luck
/FZA

How to install directory server/client on Solaris 9 for dummys

Hi,
after reading hunderts of pages, after asking questions in forums without getting the right answers, i was able to install the directory server in our company.
Here is the summary i made for myself. Perhaps it helps others to avoid the same problems.
Set up a Directory Server (sun one ds 5.1)
Present situation:
-Nisplus is installed
-Solaris OS 9 sparc 64bit is installed
-DS5 Software is normally already installed in Solaris 9. Check off with 'pkginfo | grep IPLT*'
-Otherwise install from Solaris OS 9 Disc1 with 'pkgadd -d IPLTxxxx .'
-Software setup with '/usr/sbin/directoryserver setup'
 Install admin- and directory server.
 For Directory Server use port 389 (necessary for later use of SSL)
 For Admin Server use any empty port > 1024
 Run directoryserver as root (necessary for using port 389 and for -starting servers from console)
 Use default Directory Manager DN cn=Directory manager
 Use your domain as DIT (default information tree) example: dc=example, dc=com
 As second DIT, setup installs o=NetscapeRoot. Don't change this DIT at all!!!!!
The server stores all the default schemas there which are absolutely important for the directoy
server. Don't change anything there !
-Configure software with 'idsconfig'
 Preferred - and default server xxx.xxx.xxx.xxx (ip_adds of your directory server)
 Use default search scope one
 Use credential's Proxy
 Use authentication Simple (you may change this later if needed)
 All the rest should remain on default settings
 You will be asked for a proxy passwort
-Start the directoryserver console with '/usr/sbin/directoryserver startconsole'
-If it's not yet running, start the directory server from console or with command 'directoryserver -s instance_name start'
-If it's not yet running, start the admin server from console or with command 'directoyserver start-admin'
-On directoryserver's gui at configuraton/password set password encryption to 'unix crypt algorithm (CRYPT)'
Import Data
-Get Data from Nisplus with
 'niscat passwd.org_dir passwd.ldap'
 'niscat hosts.org_dir hosts.ldap'
 'niscat groups.org_dir groups.ldap'
 etc
-adjust the files. (try it out with one entry of a file only. You may delete this entry with the gui very easy if it's not successfull.
-hosts.ldap must look like
xxx.xxx.xxx.xxx machine1
xxx.xxx.xxx.xxx machine2
xxx.xxx.xxx.xxx machine3
 First value is the ip-address, second one is the hostname.
 If you have more than one hostname per machine, use a second line (don't write 2 names behind the ip-address like you did in nisplus!!!)
Change content of files into ldif format
-perl migrate_hosts.pl hosts.ldap hosts.ldif
-perl migrate passwd.pl passwd.ldap passwd.ldif
-You may download the above perl-Files from http://www.padl.com
Change the converted passwd.ldif File as follows:
-before change:
dn: uid=mario,ou=People,dc=krinfo,dc=ch
uid: mario
cn: mario
objectClass: account
objectClass: posixAccount
objectClass: top
userPassword: {crypt}6O9m3uK./T/rM
loginShell: /bin/bash
uidNumber: 1020
gidNumber: 14
homeDirectory: /home/mario
-after change:
dn: uid=mario,ou=People,dc=krinfo,dc=ch
uid: mario
cn: mario
objectClass: account
objectClass: posixAccount
objectClass: shadowAccount <--- this line must be inserted
objectClass: top
userPassword: {crypt}6O9m3uK./T/rM
loginShell: /bin/bash
uidNumber: 1020
gidNumber: 14
homeDirectory: /home/mario
Insert the line for every entry in the passwd.ldif file
You may now import all these xxxx.ldif files into the directory server with
-ldapadd -h name_of_directoryserver -D "cn=Directory Manager" -w password -f XXXXX.ldif
You may use this commands later to import further data.
-Initialise a client
'ldapclient -a proxyDN=cn=proxyagent,ou=profile,dc=example,dc=com init xxx.xxx.xxx.xxx'
The xxx.xxx.xxx.xxx at the end is the ip address of the directory server
-This will make a client with data taken from the default profile from the directory server. This profile has been produced with the earlier command idsconfig and can be changed if needed.
-The System will ask you for the proxy password (given the first time in idsconfig dialog)
-You may now look at the produces files
in '/var/ldap/ldap_client_file' for the client settings
in '/var/ldap/ldap_client_cred' for the proxy settings
'ldapclient list' shows the settings of the client
With 'ldaplist -h' you may see all the existing entries with their objects.
Activate the client
-If it's not yet running, start '/usr/lib/ldap/ldap_cachemgr'
-All nisplus daemons/programs have been stopped by ldapclient command. If not, stop them manually.
-/etc/nsswitch.conf should have been copied from /etc/nsswitch.ldap from ldapclient too.
-If not, do it manually.
example
passwd: files ldap
group: files ldap
hosts ldap dns files
etc
I recommend to change the file '/etc/nsswitch.ldap' because the system oftens copies nsswitch.ldap to nsswitch.conf and if nsswitch.ldap is adapted, you must now change it again and again.
you may now check whether ldap is working fine with the following requests:
getent passwd username
getent hosts hostname
getent groups
getent network
These commands should give you the requested answer.
Be sure to clean:
/etc/hosts inside is only your workstation and the directory server
/etc/passwd only default and local entries
/etc/groups only default and local entries
etc
try a telnet to your own machine to check, whether password and automount of your home_dirctory works fine.
I failed here. All was working fine, but the password exchange did not because of credential/authentication problems.
Best regards and good luck
Mario

Directory Server 5.1 does not support Kerberos authentication.
Beside this there are some extensions in MS kerberos authentication that makes it almost impossible to have a MS client authenticate with something else than AD.
Regards,
Ludovic.

Client Settings non modifiable for ob52, ob58 etc

Similar Messages

Maybe you are looking for