Lesson 2 of 5
System change options
10 min
Listen to this lesson
Client settings protect client-specific customizing. The repository, meaning ABAP programs, dictionary objects and other development objects, is protected at system level by the system change option in transaction SE06 (button System Change Option). It answers one question: may repository objects be changed in this system at all, and if so, which ones?
- Is the global setting "Modifiable"?Yes → check the software component and namespace · No → no repository object can be changed in this system
- Is the object's software component or namespace modifiable?Yes → check the client's cross-client setting in SCC4 · No → the change is blocked
- Does SCC4 allow repository changes from this client?Yes → the change can be made (and recorded in a transport) · No → the change is blocked
The global setting
The global setting is either Modifiable or Not Modifiable. If it is Not Modifiable, no repository object can be changed, whatever the other settings say. Production and quality assurance systems normally run Not Modifiable; development systems run Modifiable.
Software components and namespaces
Below the global setting, each software component can be set individually. SAP training describes four values: Modifiable; Restricted Modifiability (objects can only be created as non-originals); Not Modifiable, Enhanceable Only (no changes, but the enhancement framework can still be used); and Not Modifiable, Not Enhanceable. Namespaces are set the same way: the customer name range (Y and Z objects) and any reserved namespaces in the form /NAMESPACE/ can be opened or closed separately.
| Level | Development (CMD) | Quality (CMQ) | Production (CMP) |
|---|---|---|---|
| Global setting | Modifiable | Not Modifiable | Not Modifiable |
| SAP software components | Open only as far as needed (for example for SAP Notes and approved modifications) | Not Modifiable | Not Modifiable |
| Customer name range (Y/Z) | Modifiable | Not Modifiable | Not Modifiable |
| Client cross-client setting (SCC4) | Allowed in the development client | No changes | No changes |
Two practical points help in development. First, changing an SAP-delivered object by hand (a modification) requires the object to be registered with SAP, and the developer gets a key for it; changes made through the Note Assistant do not need such a key. Second, partners and add-on vendors often deliver objects in their own reserved namespace. Keep those namespaces closed in CMD unless you really own the objects, so that nobody "fixes" an add-on locally and breaks its next update.
What SNOTE needs
Implementing SAP Notes with the Note Assistant (SNOTE) changes SAP repository objects, so in the development system the affected software components must be set to Modifiable or Restricted Modifiability, and the general SAP name range must be modifiable. In QA and production, notes arrive by transport, never by running SNOTE there.
Emergency opening of production
Occasionally production must be opened, but only as a break-glass step for a setting or repair that cannot be transported, for example when SAP support must make a correction directly in production. Code and configuration emergency fixes do not qualify: as the release management course explains, they are still built in development (CMD) and moved through the transport path, with faster approval and a minimum safe test. Treat any opening as a controlled exception. SE06 changes are logged in the system, but an approved procedure makes the difference between an audited emergency and a finding.
- RequestChange owner documents why the change cannot be transported and how long production must stay open
- ApproveRelease manager (Luis at Contoso) and system owner approve the window
- OpenSam opens only the needed component or namespace in SE06 and the client in SCC4
- ChangeOnly the non-transportable change is made and recorded; anything that can be transported goes through CMD and the transport path
- Close and verifySettings are restored; a second person checks SE06 and SCC4 and records the evidence
- Follow upThe same change is applied in CMD and CMQ so the landscape stays in sync
What would you do?
During cutover rehearsal, Kenji asks Sam to set CMQ to Modifiable "for the afternoon" so he can debug and patch a custom report directly. What is the best answer?
- SE06 controls repository changes: global setting, then software components and namespaces.
- Production and QA: global setting Not Modifiable. Development: Modifiable, opened only as needed.
- A cross-client change needs both SE06 and SCC4 to allow it.
- Open production only as break-glass for non-transportable settings, through an approved, time-boxed, verified procedure; code and config fixes still go CMD → transport path.
Check your understanding · not graded
Lesson check
1. Which transaction holds the system change option?
2. What does "Not Modifiable, Enhanceable Only" allow for a software component?
3. A cross-client customizing change is blocked although SCC4 allows it. What else must allow it?
4. How should SAP Notes reach production?