SAP ABAP Message Class /SAPTRX/ASC (Event Manager: Messages from application server customizing)
Basic Data
Hierarchy
☛
PI_BASIS (Software Component) Basis Plug-In
⤷
SCM-EM-AS (Application Component) Application System
⤷
/SAPTRX/ASCU (Package) Application System customizing and communication
⤷
⤷
Attributes
| Message class | /SAPTRX/ASC | |
| Short Description | Event Manager: Messages from application server customizing | |
| Changed On | 20090618 | |
| Last Changed At | 100632 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | No parameters available for determining application object type | Space: object requires documentation | ||
| 2 | No application object type found for &1 &2 &3 | Space: object requires documentation | ||
| 3 | No unique application object type found for &1 &2 &3 | Space: object requires documentation | ||
| 4 | No application object type found for &1 | Space: object requires documentation | ||
| 5 | Application object reference for &1 &2 in system &3 is locked by &4 | Space: object requires documentation | ||
| 6 | SAP Event Management communication aborted; no AOTs defined | Space: object requires documentation | ||
| 7 | No event management-relevant application object determined | Space: object requires documentation | ||
| 8 | Logical system could not be determined | Space: object requires documentation | ||
| 9 | Required control table &1 for AO type &2 not available | Space: object requires documentation | ||
| 10 | Assigned application table &1 for AO type &2 is not available | Space: object requires documentation | ||
| 11 | Application object type &1 not relevant for object &2 &3 | Space: object requires documentation | ||
| 12 | Name tab for table &1 could not be read | Space: object requires documentation | ||
| 13 | Application object type &1 relevant for object &2 &3 | Space: object requires documentation | ||
| 14 | Condition &1 for application object type &2 incorrect | Space: object requires documentation | ||
| 15 | Application object type determination stopped for object &1 &2 | Space: object requires documentation | ||
| 16 | Control parameter determination error; check control parameter extraction | Space: object requires documentation | ||
| 17 | Event handler for application object &1 &2 cannot be changed | Space: object requires documentation | ||
| 18 | Event handler type for application object &1 &2 could not be determined | Space: object requires documentation | ||
| 19 | Processing and communication aborted for AO type &1 | Space: object requires documentation | ||
| 20 | Processing and communication to SAP Event Management completely aborted | Space: object requires documentation | ||
| 21 | Drilldown is not possible from this field | Space: object requires documentation | ||
| 22 | No SAP Event Management defined | Space: object requires documentation | ||
| 23 | Key length of table &1 is defined as 0 for business process type &2 | Space: object requires documentation | ||
| 24 | Data tables for application object type & successfully set up | Space: object requires documentation | ||
| 25 | Objects for AO type &1 will be evaluated using condition &2 | Space: object requires documentation | ||
| 26 | Event management relevance will not be checked for AO type &1 | Space: object requires documentation | ||
| 27 | Event management relevance condition &1 could not be read | Space: object requires documentation | ||
| 28 | Appl. object &1 skipped for AO type &2 due to settings | Space: object requires documentation | ||
| 29 | Appl. object &1 skipped for AO type &2 because main object is unchanged | Space: object requires documentation | ||
| 30 | Appl. object &1 skipped for AO type &2 (main & master object unchanged) | Space: object requires documentation | ||
| 31 | Appl. object &1 skipped for AO type &2 because object was deleted | Space: object requires documentation | ||
| 32 | AO type &1 processed: &2 new or changed relevant objects found | Space: object requires documentation | ||
| 33 | AO type &1 processed: &2 deleted relevant objects found | Space: object requires documentation | ||
| 34 | All application objects rejected by SAP Event Management | Space: object requires documentation | ||
| 35 | SAP Event Management communication aborted due to deactivation of BPT &1 | Space: object requires documentation | ||
| 36 | Application interface running in maintenance mode for BPT &1 | Space: object requires documentation | ||
| 37 | Database table definition for AO type &1 is not set: BPT &2, table &3 | Space: object requires documentation | ||
| 38 | Key for appl. obj &1 &2 could not be determined. Detail log not available | Space: object requires documentation | ||
| 39 | Referencing of main and master table fields &1 - &2 successful | Space: object requires documentation | ||
| 40 | Referencing of main and master table fields &1 - &2 failed | Space: object requires documentation | ||
| 41 | Start of evt management relevance processing for application object &1 &2 | Space: object requires documentation | ||
| 42 | End of evt management relevance processing for application object &1 &2 | Space: object requires documentation | ||
| 43 | Dynamic assignment of structure field &1 - &2 failed | Space: object requires documentation | ||
| 44 | Determination of evt management relevance of appl. object &1 by function | Space: object requires documentation | ||
| 45 | Determination of evt management relevance of AO &1 by Boolean condition | Space: object requires documentation | ||
| 46 | AO type &1 evaluation set to condition but no condition defined | Space: object requires documentation | ||
| 47 | AO type &1 evaluation set to function but no function defined | Space: object requires documentation | ||
| 48 | Objects for AO type &1 will be evaluated using function &2 | Space: object requires documentation | ||
| 49 | Start of status check in SAP Event Management | Space: object requires documentation | ||
| 50 | End of status check in SAP Event Management | Space: object requires documentation | ||
| 51 | Enter parameter tables for condition definition | Space: object requires documentation | ||
| 52 | Condition ID &1 does not exist for determining application object type | Space: object requires documentation | ||
| 53 | Editing system parameters is not permitted | Space: object requires documentation | ||
| 54 | Application object type &1 already used for BPT &2 | Space: object requires documentation | ||
| 55 | Multiple use of sequence no. &1 for BPT &2; assign unique sequence no. | Space: object requires documentation | ||
| 56 | Sequence number is initial; assign unique sequence number | Space: object requires documentation | ||
| 57 | SAP Event Management general: &1 &2 &3 &4 | Space: object requires documentation | ||
| 58 | SAP Event Management application object-specific: &1 &2 &3 &4 | Space: object requires documentation | ||
| 59 | Function &1 could not be created; check function type and template | Space: object requires documentation | ||
| 60 | No event management-relevant event determined | Space: object requires documentation | ||
| 61 | Check RFC destination and/or logical system specification | Space: object requires documentation | ||
| 62 | SCEM-AI: Database operation &1 failed for table &2 with return code &3 | Space: object requires documentation | ||
| 63 | Function module &1 for function &2 not found; correct settings | Space: object requires documentation | ||
| 64 | Condition &1 not found; correct settings in the appl. object conditions | Space: object requires documentation | ||
| 65 | Interface for function &1 is incorrect; correct function module interface | Space: object requires documentation | ||
| 66 | Function &1 has not been activated | Space: object requires documentation | ||
| 67 | Structure name and DDIC stucture must be defined | Space: object requires documentation | ||
| 68 | SAP Event Management communic. process aborted; RFC communication failure | Space: object requires documentation | ||
| 69 | Required control table &1 for event type &2 is not available | Space: object requires documentation | ||
| 70 | Assigned application table &1 for event type &2 is not available | Space: object requires documentation | ||
| 71 | Objects for event type &1 will be evaluated using condition &2 | Space: object requires documentation | ||
| 72 | Event type &1 evaluation set to condition but no condition defined | Space: object requires documentation | ||
| 73 | Objects for event type &1 will be evaluated using function &2 | Space: object requires documentation | ||
| 74 | Event type &1 evaluation set to function but no function defined | Space: object requires documentation | ||
| 75 | Event management relevance will not be checked for event type &1 | Space: object requires documentation | ||
| 76 | End of event management relevance processing for event &1 &2 | Space: object requires documentation | ||
| 77 | Condition &1 for event type &2 incorrect | Space: object requires documentation | ||
| 78 | Event type &1 relevant for object &2 &3 | Space: object requires documentation | ||
| 79 | Event type determination stopped for object &1 &2 | Space: object requires documentation | ||
| 80 | Event type &1 not relevant for object &2 &3 | Space: object requires documentation | ||
| 81 | Data tables for event type &1 successfully set up | Space: object requires documentation | ||
| 82 | Determination of event management relevance of event &1 by function | Space: object requires documentation | ||
| 83 | Determination of evt management relevance of evt &1 by boolean condition | Space: object requires documentation | ||
| 84 | Event type &1 processed: &2 new or changed relevant objects found | Space: object requires documentation | ||
| 85 | No SAP Event Management communication for events; no event types defined | Space: object requires documentation | ||
| 86 | Old main table has &1 key fields for referencing (reduces performance). | Space: object requires documentation | ||
| 87 | AO type &1 skipped: No SAP Event Management entry maintained | Space: object requires documentation | ||
| 88 | Main table &1 is incompatible with extractor &2 in &3 &4. | Space: object requires documentation | ||
| 89 | Master table &1 is incompatible with extractor &2 in &3 &4. | Space: object requires documentation | ||
| 90 | EH creation not permitted: AOT evaluation skipped | Space: object requires documentation | ||
| 91 | Database table definition for event type &1 is not set: BPT &2, table &3 | Space: object requires documentation | ||
| 92 | Key for event &1 &2 could not be determined. Detail log not available | Space: object requires documentation | ||
| 93 | Start of evt management relevance processing for event &1 &2 | Space: object requires documentation | ||
| 94 | End of evt management relevance processing for event &1 &2 | Space: object requires documentation | ||
| 95 | Event message sending not permitted: Event type evaluation skipped | Space: object requires documentation | ||
| 96 | EH creation not permitted: AOT evaluation skipped | Space: object requires documentation | ||
| 97 | Event message sending not permitted: Event type evaluation skipped | Space: object requires documentation | ||
| 98 | Event type &1 skipped: no SAP Event Management entry maintained | Space: object requires documentation | ||
| 99 | Internal error in function module /SAPTRX/INTERNAL_EM_READ_TCON | Space: object requires documentation | ||
| 100 | No parameters defined in the application system | Space: object requires documentation | ||
| 101 | Maintain expected event lists for SAP EM interface functions | Space: object requires documentation | ||
| 102 | No application object types found | Space: object requires documentation | ||
| 103 | No business process types maintained in the SAP Event Management | Space: object requires documentation | ||
| 104 | Communication failure to RFC destination &1 | Space: object requires documentation | ||
| 105 | System failure when calling function &1 on RFC dest. &2 | Space: object requires documentation | ||
| 106 | Business process type &1 not found in any EM global BPT directory | Space: object requires documentation | ||
| 107 | No release information maintained in Customizing for defining SAP EM | Space: object requires documentation | ||
| 108 | No suitable event management relevance condition found | Space: object requires documentation | ||
| 109 | &1 | Space: object requires documentation | ||
| 110 | &1&2 | Space: object requires documentation | ||
| 111 | &1&2&3 | Space: object requires documentation | ||
| 112 | &1&2&3&4 | Space: object requires documentation | ||
| 113 | An entry already exists with the same key; choose another key | Space: object requires documentation | ||
| 114 | If SAP EM runs locally, only set synchronous communication | The short text describes the object sufficiently | ||
| 115 | Business object &1 was posted to SAP EM but not acknowledged | The short text describes the object sufficiently | ||
| 116 | Business object &1 was rejected by SAP EM due to locked event handler | The short text describes the object sufficiently | ||
| 117 | Business object &1 was rejected by SAP EM due to processing error | The short text describes the object sufficiently | ||
| 118 | Specify the AOID extractor field when determining the AOID from function | The short text describes the object sufficiently | ||
| 119 | Specify the AOID field when determining the AOID from field | The short text describes the object sufficiently | ||
| 120 | Select either the main object table or master reference table option | The short text describes the object sufficiently | ||
| 121 | Select the method for determining the tracking ID | The short text describes the object sufficiently | ||
| 122 | Specify the extractor when determining tracking ID from function | The short text describes the object sufficiently | ||
| 123 | Specify the tr. ID and code set fields to determine tr. ID from field | The short text describes the object sufficiently | ||
| 124 | Specify the function name when event relevance determined from function | The short text describes the object sufficiently | ||
| 125 | Specify the condition when event relevance determined from condition | The short text describes the object sufficiently | ||
| 126 | Key definition in BPT &1 not correct for specified Del.Obj. Table in AOT | Space: object requires documentation | ||
| 127 | Specify an existing target table before choosing a target field | Space: object requires documentation | ||
| 128 | Specify an existing structure or table name before choosing a field name | Space: object requires documentation | ||
| 129 | Specify an existing message structure before choosing a field name | Space: object requires documentation | ||
| 130 | Specify an existing extraction field before choosing an extraction index | Space: object requires documentation | ||
| 131 | Enter a field name that is contained in the structure or table specified | Space: object requires documentation | ||
| 132 | Enter a target field that is contained in the target table specified | Space: object requires documentation | ||
| 133 | You do not have the authorization to call transaction &1 | The short text describes the object sufficiently | ||
| 134 | Subordinate log could not be found | Space: object requires documentation | ||
| 135 | SCEM process log appended to application log | Space: object requires documentation | ||
| 136 | Subordinate log created for object &1 &2 | Space: object requires documentation | ||
| 137 | External: &1 | Space: object requires documentation |
History
| Last changed on/by | 20090618 | SAP | |
| SAP Release Created in |