Question:
We are in a ECC 6.0 HR environment and are unit testing standard processing txn's PP01, OOQ4, OOSC and others. We get the message that no modifications are allowed. We have set the SCC4 settings to No changes allowed and no changes to cust objects allowed and Productive system to mimic real production. Is there a setting that enables the processing of these transactions that weve missed since they are every day use transactions or are we to go into every one and select the "current settings" for the tables that we are updating. It would not be a problem if it were one or two transactions but we are seeing this with many that our Application specialists say are updated every day.
Thanks in advance
Rob
Answer:
Working as designed... Many of the transaction codes beginning with 'O' are Configuration transactions and should not be changed in a production environment. Are you Application Specialist REALLY changing these daily? As delivered by SAP they should not be, but rather changing them in Dev and transported to QAS for testing and then to PRD for implementation.
There are some table though that SAP believes are Configuration but the customer does change these frequently and can be converted to Application tables. The guideline I usually recomment is if they are chagne one to two times or more per month then you should consider converting the tables.
This is easily done with a minor repair to te system and changing the delivery class of the table to "L". You access this via transaction SE11. There is another way with an obscure table but the name escapes me, it contains OBJ I beleive...
_________________
John A. Jarboe
Answer:
Certain PD objects can be changed . Note 163897. Put X in table T77SO
IMG Path
Personnel Mgmt
Org Mgmt
Transports
Set up transport connections
TRSP CORR put an X - Read the help to understand the impact.
These are tables that get updated daily for us.
Other option is to play with the Current settings, but first option is configurable throuh IMG(Better option)