Authorization Object: S_IDOCDEFT

WFEDI: S_IDOCDEFT – Access To Idoc Development

Category: IDoc interface

 

Definition

Click on the objects below, to expand data.

Object Fields

The list below includes the object’s fields, ordered by industry-standard importance:

ACTVT Activity Filled in 91% of cases
EDI_CIM Extension Filled in 88% of cases
EDI_DOC Basic Type Filled in 88% of cases
EDI_TCD Transaction Code Filled in 91% of cases

 

Popularity Statistics

Average popularity of S_IDOCDEFT in roles: 0% (What does this mean?)
Average popularity of S_IDOCDEFT by users: 5% (What does this mean?)

Object S_IDOCDEFT is frequently used by users in the following areas:
BC:Basis Components
FI:Financial Accounting

Environmental Analysis

1. Common authorization objects used with S_IDOCDEFT:

S_IDOCREPA WFEDI: S_IDOCREPA – Access To Repair Programs Objects appear together in 80% of cases
PLOG Personnel Planning Objects appear together in 33% of cases
S_DEVELOP ABAP Workbench Objects appear together in 25% of cases
S_RFC Authorization Check For RFC Access Objects appear together in 19% of cases
S_IDOCCTRL WFEDI: S_IDOCCTRL – General Access To Idoc Functions Objects appear together in 2% of cases
S_IDOCMONI WFEDI: S_IDOCMONI – Access To Idoc Monitoring Objects appear together in 2% of cases

  2. Appearance of S_IDOCDEFT in T-Codes:

IDOC IDoc: Repair and check programs Used in 100% of cases
BDFG ALE Interfaces from Function Module Used in 94% of cases
BDBG Create ALE Interface for BAPI Used in 91% of cases
WE61 Documentation for IDoc record types Used in 86% of cases
WE62 Documentation for segments Used in 86% of cases
WE63 Documentation Used in 86% of cases
WE32 Development IDoc View Used in 77% of cases
WE81 Logical message types Used in 77% of cases
WE82 Assignment Messages for IDoc Type Used in 77% of cases
WE60 Documentation for IDoc types Used in 72% of cases
WE30 Development IDoc Type Used in 66% of cases
WE31 Development IDoc Segment Used in 66% of cases
BD87 Status Monitor for ALE Messages Used in 61% of cases

Leave a Reply

Your email address will not be published. Required fields are marked *