Risk
Direct production changes can bypass approval, testing and segregation of duties.
ABAP
Settings and priorities
| Technology / priority | Parameter or mechanism | Setting and purpose |
|---|---|---|
| ABAP Critical | SE06 · System Change Option | Not modifiable In TADIR: PGMID=HEAD, OBJECT=SYST, EDTFLAG=N or P. |
| ABAP Critical | SCC4 · production client | Live; no local or cross-client changes In T000: CCCATEGORY=P (also S for 000), CCCORACTIV=2, CCNOCLIIND=3, CCCOPYLOCK=X or L. |
| ABAP Standard | rec/client | ALL or an appropriate client list; not OFF Records changes to tables with logging enabled. |
| ABAP Standard | TLOGOCHECK | TRUE Validates transport file contents. |
| ABAP Standard | abap/ext_debugging_possible | 2 Controls external debugging. |
| ABAP Standard | dbs/dba/ccms_maintenance ; dbs/dba/ccms_security_level | 1 ; 1 Restricts administrative operations in DBA Cockpit. |
| ABAP Extended | RECCLIENT | Enabled; not OFF Records changes during transport imports. |
| ABAP Extended | VERS_AT_EXP ; VERS_AT_IMP | Decide on export and import versioning Consider ALWAYS for VERS_AT_IMP in production; scope depends on the transport strategy. |
Table logging requires both an active rec/client setting and the relevant table technical settings. RDDPRCHK or STDDAT can help review authorization groups, delivery classes and logging.
How to verify
- Check the global system change option and every production client.
- Verify rec/client and the logging flag of relevant tables in SE13.
- Review transport parameters and tp/R3trans versions.
- Retain configuration evidence and approved exceptions.