SAP CELONIS_EXTRACION role
The following describes in detail what the SAP CELONIS_EXTRACION role contains and why the authorizations are necessary along with customization options
Cross-application Authorization Objects
Authorization Check for RFC Access - So the Extractor can remotely access the functions in the RFC module
Object | Field | Activities/Values |
|---|---|---|
S_RFC | ACTVT | 16 |
S_RFC | RFC_NAME | /CELONIS/46C_EXTRACTION, /CELONIS/CL_EXTRACTION, /CELONIS/EXTRACTION, /CELONIS/V2_CL_EXTRACTION, /CELONIS/V2_EXTRACTION, RFC1, SDIFRUNTIME, SDTX, SRFC, SYST, SYSU |
S_RFC | RFC_TYPE | FUGR |
Basis: Administration
Background Processing: Operations on Background Jobs - So the RFC module can immediately run the extractions as background jobs
Object | Field | Activities/Values |
|---|---|---|
S_BTCH_JOB | JOBACTION | RELE |
S_BTCH_JOB | JOBGROUP | * |
Administration Functions in Change and Transport System - So the RFC module can list directory contents
No longer necessary in RFC Module versions >= 1.8.0
Object | Field | Activities/Values |
|---|---|---|
S_CTS_ADMI | CTS_ADMFCT | EPS1 |
Authorization for file access - So the RFC module can write, read, and delete files in the physical path defined for the logical path 'Z_CELONIS_TARGET'
Object | Field | Activities/Values |
|---|---|---|
S_DATASET | ACTVT | 06, 33, 34 |
S_DATASET | FILENAME | * |
S_DATASET | PROGRAM | /CELONIS/* |
Note
You can replace the '*' in 'FILENAME' with the physical path you have chosen for Z_CELONIS_TARGET, e.g. /<YOUR_PATH>/*
Table Maintenance (via standard tools such as SM30) - So the RFC module can extract data from tables
Object | Field | Activities/Values |
|---|---|---|
S_TABU_DIS | ACTVT | 03 |
S_TABU_DIS | DICBERCLS | * |
Note
You can replace the '*' in 'DICBERCLS' with the authorisation group of tables you will be extracting.
Alternatively, If you need to control access to individual tables instead to groups of tables, you can use authorisation object S_TABU_NAM.
Important: When using the Real-Time Extractor, the Changelog tables (ZCL...) should also be whitelisted.
Basis - Development Environment - Generic Program Start
Object | Field | Activities/ Values |
|---|---|---|
S_PROGNAM | P_ACTION | BTCSUBMIT |
S_PROGNAM | P_PROGNAM | /CELONIS/RP_BG_EXTRACT |
Basis - Central Functions- Applications log
Object | Field | Activities/ Values |
|---|---|---|
S_APPL_LOG | ALG_OBJECT | /CELONIS/ |
S_APPL_LOG | ALG_SUBOBJ | * |
S_APPL_LOG | ACTVT | 06 |