Ansicht
Dokumentation
EDI-03 - Assign authorizations
General Data in Customer Master ABAP Short ReferenceThis documentation is copyright by SAP AG.
Profiles contain authorization objects for defined areas. In this activity you generate a profile and allocate these users. Also note the documentation on Profile Generator (transaction PFCG). You must only enter the transactions or menus and the relevant profiles are automatically created.
SAP delivers roles that affect the IDoc interface.
- SAP_BC_USER_AG (with IDoc lists)
- SAP_BC_SRV_EDI_ADMIN_AG (port, partner, monitoring, IDoc administration)
- SAP_BC_SRV_EDI_DEVELOPER_AG (all IDoc functions)
Each of the three groups is contained in a corresponding composite role SAP_BPT_USER, SAP_BPT_ADMIN or SAP_BPT_DEVELOPER which is valid for the areas workflow, Business Workplace and IDoc Interface.
Activities
- Check the roles using transaction PFCG.
- If the roles are not sufficient, you must create new groups according to your requirements. If you want to assign authorization objects by hand (therefore no transactions or menus) then you must see the section below on authorization objects.
Notes on transport
Note the documentation on transaction PFCG.
Authorization objects
The following list shows which authorization objects are checked by the individual functions of the application. They belong to the object class "Basis - central functions".
Function | Authorization object |
IDoc display | S_IDOCMONI display IDoc |
Access to IDoc functions | S_IDOCCTRL IDoc functions |
IDoc development | S_IDOCDEFT IDoc development |
Partner profiles | S_IDOCPART IDoc partner |
Port definition | S_IDOCPORT IDocs ports |
Object: S_IDOCMONI IDoc Interface: Display of IDocs
Definition
Controls access to IDocs in the statistics and monitoring programs for the test tool (template of an existing IDoc).
Defined fields
- EDI_TCD,,Current transaction
- ACTVT,,Permitted activity
- EDI_MES,,Permitted message type
- EDI_DIR,,IDoc direction: 1 = outbound, 2 = inbound
- EDI_PNR,,Permitted partner number
- EDI_PRT,,Permitted partner type
In the following functions, the following values are checked:
Function | Transaction | ACTVT | |
---|---|---|---|
IDoc display | WE02 | 02-03 | |
IDoc list | WE05 | 02-03 | |
IDoc statistics | WE07 | 02-03 | |
IDoc search (database) | WE09 | 02-03 | |
IDoc search (archive) | WE10 | 02-03 | |
Test tool | WE19 | 03 |
The activities mean: 01 - Create, 2 - Change, 03 - Display
Object: S_IDOCCTRL IDoc Interface: Access to IDoc functions
Definition
Controls access to IDoc Interface programs.
Defined fields
- EDI_TCD,,Executed transaction
- ACTVT,,Permitted activity
In the following functions, the following values are checked:
Function TA/Program EDI_TCD ACTVT |
---|
Active monitoring RSEIDOCM WE07 16 |
Archiving not checked 24 |
Display file status WE08 WE08 03 |
Customizing: Activate IDoc inb.procg OYEB OYEB 03 |
Customizing: Extended |
status processing OYED OYED 03 |
Customizing: Make error processes |
for standard tasks OYSP OYSP 03 |
Customizing: Delete process |
technology in logistics OYEC OYEC 03 |
Generate file name WE55 WE55 01-03 |
IDoc administration WE46 WE46 02,03 |
Possible partner types WE44 02,03 |
Status maintenance WE47 WE47 02,03,36 |
Display status record WE43 WE43 02,03 |
Test outb. procg from MC WE15 WE15 16 |
Test outb. procg from IDoc WE14 WE14 16 |
Test inb. procg of mod. outb. file WE12 WE12 16 |
Test inb. procg of orig. inb. file WE16 WE16 16 |
Generate test status file WE18 WE18 16 |
Process test status file WE17 WE17 16 |
Test tool WE19 WE19 16 |
Process code outbound processing WE41 WE41 02,03 |
Process code inbound processing WE42 WE42 02,03 |
Process code status WE56 WE56 01-03 |
Process code system WE40 WE40 02,03 |
Forward inbound processing WE45 WE45 02,03 |
Assign FM to |
Message and IDoc type WE57 WE57 02,03 |
Delete IDocs WE11 WE11 06 |
Delete from IDoc queue WEOUTQUEUE WEINBQUEUE 06 |
The activities mean: 01 - Create, 02 - Change, 03 - Read, 06 - Delete, 16 - Execute, 24 - Archive, 36 - Extended maintenance.
Object: S_IDOCDEFT IDoc Interface: Access to IDoc development
Definition
Controls access to IDoc development tools and documentation tools.
Defined Fields
- EDI_TCD,,Executed transaction
- ACTVT,,Permitted activity
- EDI_DOC,,Permitted basic type
- EDI_CIM,,Permitted extension
In the following functions, the following values are checked:
Function | EDI_TCD | ACTVT | EDI_DOC,EDI_CIM | |
---|---|---|---|---|
Docum.IDoc types | WE60 | 03 | checked | |
Docum.IDoc record types | WE61 | 03 | not checked | |
Docum.IDoc segments | WE62 | 03,03 | " | |
Parser | WE63 | 03 | checked | |
IDoc views | WE32 | 01-03 | not checked | |
IDoc type editor (WE30) | WE30 | 01-03,06,43 | checked | |
Segment editor (WE31) | WE30 | 01-03,43 | not checked | |
Message/appl.object | WE57 | 01-03 | " | |
Message type | WE81 | 01-03 | " | |
Message/IDoc type | WE82 | 01-03 | " |
Activities:
01 - Add, 02 - Change, 03 - Read, 06 - Delete, 43 - Release
In the case of functions which check authorization for the combination of basic type and extension for the required activity, the activities of a user can be restricted to a defined "namespace" of basic types and extensions.
The segment editor and IDoc type editor are closely related. As a result, the same authorizations are used for both WE30 and WE31.
Object: S_IDOCPART IDoc Interface: Access to IDoc partner
Definition
Controls access to the partner profiles (transaction WE20).
Defined fields
- EDI_TCD,,Executed transaction: WE20
- ACTVT,,Permitted activity: 01-03 (create, change, display)
- EDI_PNR,,Permitted partner number
- EDI_PRT,,Permitted partner type
The fields EDI_PNR and EDI_PRT can be used to define which user can process which partner in which way.
Object: S_IDOCPORT IDoc Interface: Access to IDoc ports
Definition
Controls access to the port definition.
Defined fields
- EDI_TCD,,Current transaction
- ACTVT,,Permitted activity
- EDI_POR,,Permitted port type
In the following functions, the following values are checked:
Function | EDI_TCD | ACTVT | EDI_POR | |
---|---|---|---|---|
Port definition | WE21 | 01-03 | 0-5 |
Activities:
01 - Create, 02 - Change, 03 - Display
Port types:
0 = CPI-C, 1 = tRFC, 3 = File, 4 = Internet 5 = Programming interface
General Material Data Fill RESBD Structure from EBP Component Structure
This documentation is copyright by SAP AG.
Length: 12961 Date: 20240523 Time: 162140 sap01-206 ( 89 ms )