Question:
Hi'
OPS6 is a strange transaction - you can reach it from both user-menu and IMG.
I cannot update and Im not asked for transport request.
I need to be able to update the transaction - but NOT to open for customizing.
Can anyone tell me how to do this trick?
Best regards from
LoneW
Answer:
Hi
If the Client is Productive and set as "Non Modifiable" a user should still be able to update OPS6 if they have access to the t-code.
OPS6 in this instance becomes a Cusamen table (see OSS note for more details).
Basically you can change OPS6 so long as you have access
So...in fact you can only prevent OPS6 from being maintained in Production if you don't allow anyone access to OPS6.
This is the same for OPS7 (Maintain Applicant)
Hope this helps
Regards
Crazy George
Answer:
Hi'
My problem is, that in our production system we can change - and in our test system we cannot. It is unfortunately not an authorization problem.
I get the message that:
Client 003 has status 'not modifiable'
I have been spoken to our basis team, but they have not been able to help me.
They said that there should be an opportunity to change some customizing so selected tables could be updated even if the client is not open for customizing.
I hope you can help.
best regards
Lone
Answer:
The client has to be flagged as "Productive".
And status of client has to be set to "not modifiable"
You have the 2nd part ok i.e not modifiable.
Ask your basis team for the fulls in/outs of making a client "productive or no productive"
Ask them if your test client is flagged as Productive (I don't think it will be).
Ask them if they can flag it as productive (don't now if they can) I'm not familiar with...but this is your solution, hence the reason why you can do it in Prod but not in Test.
I would be interested to know how to check if a client is productive or not
(if you find out let me know by reply).
Good luck
Regards
Crazy George
Answer:
I found this on the net, maybe useful
Introduction
Certain change control processes in SAP conflict with business users’ requirements to update data which change on a regular basis. For example, users may need to change international currency exchange rates on a daily, or even hourly, basis in the production environment. Traditionally SAP required either that the production client be open for changes or that the changes be made in development and transported across the system landscape.
SAP does allow operational modification of various data in productive SAP clients without transports and without requiring those clients to be open for any form of update. In SAP terminology, these data are called “current settings”.
Documentation of the meaning and use of this magical status is sparse to say the least but it seems that only objects defined in the IMG are eligible to be considered. In order to make a transaction or the object it manipulates a “current setting”, its IMG configuration menu path must be defined in the table CUSAMEN. Once an IMG menu path is defined in CUSAMEN and the SAP supplied [OSS 77430] program ZSIMG025 is run, the objects may be changed via the defined path in a client which has been set to “productive” status with no changes allowed according to the SCC4 description of the client.
Identifying the entry to add to CUSAMEN
Transaction SOBJ shows the list of “maintenance objects” which are involved in customising. Double clicking the object name from the first screen shown in SOBJ will return the “Object: Header Data: Details” screen which includes one important check-box under the “Derived Characteristics” heading: this is the “Current setting” check box. If this box is checked then this object can be modified in a “no-changes” productive client.
The name of the desired object, IMG path and transaction name can be displayed via transaction SM31using the process outlined below.
It is not clear whether all transactions can update an object marked as a current setting or if access is restricted to only those transactions for which a specific IMG path name has been added to CUSAMEN. I would therefore recommend using the IMG path specifically addressing the desired transaction to minimise the possibility for error and maximise control.
Transaction SM31 can be used to identify all IMG paths which affect a given table. SM31 returns many possible paths so some functional/customising expertise is required to be certain the appropriate entries are selected.
The procedure for modifying CUSAMEN is as follows.
1. Set the target client to:
1.1. Category: Test
1.2. Changes and transports for client-dependent objects radio button:
Automatic recording of changes
1.3. Client-independent object changes:
Changes to Repository and client-ind. customizing allowed
2. Identify the tables/views affected by the transaction.
2.1. SE80: Select the “Other objects” radio button then press the “Edit” button.
2.2. Select the “Transaction” radio button and enter the name of the transaction.
2.3. Follow the menu path: Goto è Object list.
2.4. Expand the hierarchy “Transactions”
2.5. Double click on the desired transaction.
2.6. You will now have either a description of the view used from the front screen or the program which is run by the transaction.
2.6.1. Finding a table from a view.
2.6.1.1. SE80: select the “Dictionary objects” radio button and press “Edit”.
2.6.1.2. Select the “View” radio button and enter the view name.
2.6.1.3. Follow the menu path: Goto è Object list.
2.6.1.4. Expand the hierarchy “Dictionary Objects è Views”.
2.6.1.5. Double click the view name to obtain a list of tables involved in the view.
2.6.2. Finding a table from a program
2.6.2.1. Double click on the program name.
2.6.2.2. Search through the source and any includes for table declarations.
3. Identify entries for table CUSAMEN.
3.1. If the entry already exists you can find it as follows
3.1.1. Use transaction SOBJ
3.1.2. Press the “Display” button
3.1.3. Scroll the list of objects to see if the desired table or view is listed. If not see below, otherwise continue here.
3.1.4. Press the selection button next to the object to highlight it.
3.1.5. Click the subobjects viewer button.
3.1.6. The IMG entry for CUSAMEN appears on the screen.
3.2. If the entry does not exist you must determine what entry is required before adding it.
3.2.1. SM31: enter table name and press the “customizing” button.
3.2.2. Choose “w/o project” in the dialogue pop-up.
3.2.3. From the list of “Areas in IMG” window, choose the most appropriate activity from the bottom of one of the trees and double click on that line.
3.2.4. Follow the menu path: Goto è Document Attributes è Display.
3.2.5. Press the “objects” button to display a window showing sets of three lines: the first line shows the workbench organiser object name and the transaction code; the second contains the IMG path and the last is a description of the business process.
3.2.6. Select a set in which the correct transaction code is shown in the right hand box of the first line. If no such set exists, go back to the activities window and try another activity as above.
4. Use SM30 to update table CUSAMEN.
4.1. Click the “new entries” button.
4.2. Assign an appropriate transport number to keep all changes together.
4.3. Copy the IMG details from the “objects” window. Note that there is a sequence number column hidden away to the right. I would recommend using the third line as the description in the update.
4.4. Register the object from line 1 of the “objects” window with OSS.
5. Repeat the whole process for all desired transactions.
6. After all updates have been made to CUSAMEN, run the ZSIMG025 program supplied in OSS note 77430.
7. Use SCC4 to change the client to:
7.1. Category: Productive
7.2. Changes and transports for client-dependent objects radio button:
No changes allowed
7.3. Client-independent object changes:
no changes to Repository and client-independent custom. obj.
Answer:
Hi'
That seems usefull - I try that and return an answer to the "productive thing" if I can find out.
Thanks a lot!!!
Best regards from
Lone
Answer:
Hi'
That was usefull information - I have now found out.
Transaction SCC4 told me that the client was not productive.
Thanks a lot!