/SAPTRX/ASC - Event Manager: Messages from application server customizing
The following messages are stored in message class /SAPTRX/ASC: Event Manager: Messages from application server customizing.
It is part of development package /SAPTRX/ASCU in software component SCM-EM-AS. This development package consists of objects that can be grouped under " Application System customizing and communication".
It is part of development package /SAPTRX/ASCU in software component SCM-EM-AS. This development package consists of objects that can be grouped under " Application System customizing and communication".
Message Nr ▲ | Message Text |
|---|---|
| 000 | No parameters available for determining application object type |
| 001 | No application object type found for &1 &2 &3 |
| 002 | No unique application object type found for &1 &2 &3 |
| 003 | No application object type found for &1 |
| 004 | Application object reference for &1 &2 in system &3 is locked by &4 |
| 005 | SAP Event Management communication aborted; no AOTs defined |
| 006 | No event management-relevant application object determined |
| 007 | Logical system could not be determined |
| 008 | Required control table &1 for AO type &2 not available |
| 009 | Assigned application table &1 for AO type &2 is not available |
| 010 | Application object type &1 not relevant for object &2 &3 |
| 011 | Name tab for table &1 could not be read |
| 012 | Application object type &1 relevant for object &2 &3 |
| 013 | Condition &1 for application object type &2 incorrect |
| 014 | Application object type determination stopped for object &1 &2 |
| 015 | Control parameter determination error; check control parameter extraction |
| 016 | Event handler for application object &1 &2 cannot be changed |
| 017 | Event handler type for application object &1 &2 could not be determined |
| 018 | Processing and communication aborted for AO type &1 |
| 019 | Processing and communication to SAP Event Management completely aborted |
| 020 | Drilldown is not possible from this field |
| 021 | No SAP Event Management defined |
| 022 | Key length of table &1 is defined as 0 for business process type &2 |
| 023 | Data tables for application object type & successfully set up |
| 024 | Objects for AO type &1 will be evaluated using condition &2 |
| 025 | Event management relevance will not be checked for AO type &1 |
| 026 | Event management relevance condition &1 could not be read |
| 027 | Appl. object &1 skipped for AO type &2 due to settings |
| 028 | Appl. object &1 skipped for AO type &2 because main object is unchanged |
| 029 | Appl. object &1 skipped for AO type &2 (main & master object unchanged) |
| 030 | Appl. object &1 skipped for AO type &2 because object was deleted |
| 031 | AO type &1 processed: &2 new or changed relevant objects found |
| 032 | AO type &1 processed: &2 deleted relevant objects found |
| 033 | All application objects rejected by SAP Event Management |
| 034 | SAP Event Management communication aborted due to deactivation of BPT &1 |
| 035 | Application interface running in maintenance mode for BPT &1 |
| 036 | Database table definition for AO type &1 is not set: BPT &2, table &3 |
| 037 | Key for appl. obj &1 &2 could not be determined. Detail log not available |
| 038 | Referencing of main and master table fields &1 - &2 successful |
| 039 | Referencing of main and master table fields &1 - &2 failed |
| 040 | Start of evt management relevance processing for application object &1 &2 |
| 041 | End of evt management relevance processing for application object &1 &2 |
| 042 | Dynamic assignment of structure field &1 - &2 failed |
| 043 | Determination of evt management relevance of appl. object &1 by function |
| 044 | Determination of evt management relevance of AO &1 by Boolean condition |
| 045 | AO type &1 evaluation set to condition but no condition defined |
| 046 | AO type &1 evaluation set to function but no function defined |
| 047 | Objects for AO type &1 will be evaluated using function &2 |
| 048 | Start of status check in SAP Event Management |
| 049 | End of status check in SAP Event Management |
| 050 | Enter parameter tables for condition definition |
| 051 | Condition ID &1 does not exist for determining application object type |
| 052 | Editing system parameters is not permitted |
| 053 | Application object type &1 already used for BPT &2 |
| 054 | Multiple use of sequence no. &1 for BPT &2; assign unique sequence no. |
| 055 | Sequence number is initial; assign unique sequence number |
| 056 | SAP Event Management general: &1 &2 &3 &4 |
| 057 | SAP Event Management application object-specific: &1 &2 &3 &4 |
| 058 | Function &1 could not be created; check function type and template |
| 059 | No event management-relevant event determined |
| 060 | Check RFC destination and/or logical system specification |
| 061 | SCEM-AI: Database operation &1 failed for table &2 with return code &3 |
| 062 | Function module &1 for function &2 not found; correct settings |
| 063 | Condition &1 not found; correct settings in the appl. object conditions |
| 064 | Interface for function &1 is incorrect; correct function module interface |
| 065 | Function &1 has not been activated |
| 066 | Structure name and DDIC stucture must be defined |
| 067 | SAP Event Management communic. process aborted; RFC communication failure |
| 068 | Required control table &1 for event type &2 is not available |
| 069 | Assigned application table &1 for event type &2 is not available |
| 070 | Objects for event type &1 will be evaluated using condition &2 |
| 071 | Event type &1 evaluation set to condition but no condition defined |
| 072 | Objects for event type &1 will be evaluated using function &2 |
| 073 | Event type &1 evaluation set to function but no function defined |
| 074 | Event management relevance will not be checked for event type &1 |
| 075 | End of event management relevance processing for event &1 &2 |
| 076 | Condition &1 for event type &2 incorrect |
| 077 | Event type &1 relevant for object &2 &3 |
| 078 | Event type determination stopped for object &1 &2 |
| 079 | Event type &1 not relevant for object &2 &3 |
| 080 | Data tables for event type &1 successfully set up |
| 081 | Determination of event management relevance of event &1 by function |
| 082 | Determination of evt management relevance of evt &1 by boolean condition |
| 083 | Event type &1 processed: &2 new or changed relevant objects found |
| 084 | No SAP Event Management communication for events; no event types defined |
| 085 | Old main table has &1 key fields for referencing (reduces performance). |
| 086 | AO type &1 skipped: No SAP Event Management entry maintained |
| 087 | Main table &1 is incompatible with extractor &2 in &3 &4. |
| 088 | Master table &1 is incompatible with extractor &2 in &3 &4. |
| 089 | EH creation not permitted: AOT evaluation skipped |
| 090 | Database table definition for event type &1 is not set: BPT &2, table &3 |
| 091 | Key for event &1 &2 could not be determined. Detail log not available |
| 092 | Start of evt management relevance processing for event &1 &2 |
| 093 | End of evt management relevance processing for event &1 &2 |
| 094 | Event message sending not permitted: Event type evaluation skipped |
| 095 | EH creation not permitted: AOT evaluation skipped |
| 096 | Event message sending not permitted: Event type evaluation skipped |
| 097 | Event type &1 skipped: no SAP Event Management entry maintained |
| 099 | Internal error in function module /SAPTRX/INTERNAL_EM_READ_TCON |
| 100 | No parameters defined in the application system |
| 101 | Maintain expected event lists for SAP EM interface functions |
| 102 | No application object types found |
| 103 | No business process types maintained in the SAP Event Management |
| 104 | Communication failure to RFC destination &1 |
| 105 | System failure when calling function &1 on RFC dest. &2 |
| 106 | Business process type &1 not found in any EM global BPT directory |
| 107 | No release information maintained in Customizing for defining SAP EM |
| 108 | No suitable event management relevance condition found |
| 109 | &1 |
| 110 | &1&2 |
| 111 | &1&2&3 |
| 112 | &1&2&3&4 |
| 113 | An entry already exists with the same key; choose another key |
| 114 | If SAP EM runs locally, only set synchronous communication |
| 115 | Business object &1 was posted to SAP EM but not acknowledged |
| 116 | Business object &1 was rejected by SAP EM due to locked event handler |
| 117 | Business object &1 was rejected by SAP EM due to processing error |
| 118 | Specify the AOID extractor field when determining the AOID from function |
| 119 | Specify the AOID field when determining the AOID from field |
| 120 | Select either the main object table or master reference table option |
| 121 | Select the method for determining the tracking ID |
| 122 | Specify the extractor when determining tracking ID from function |
| 123 | Specify the tr. ID and code set fields to determine tr. ID from field |
| 124 | Specify the function name when event relevance determined from function |
| 125 | Specify the condition when event relevance determined from condition |
| 126 | Key definition in BPT &1 not correct for specified Del.Obj. Table in AOT |
| 127 | Specify an existing target table before choosing a target field |
| 128 | Specify an existing structure or table name before choosing a field name |
| 129 | Specify an existing message structure before choosing a field name |
| 130 | Specify an existing extraction field before choosing an extraction index |
| 131 | Enter a field name that is contained in the structure or table specified |
| 132 | Enter a target field that is contained in the target table specified |
| 133 | You do not have the authorization to call transaction &1 |
| 200 | Subordinate log could not be found |
| 201 | SCEM process log appended to application log |
| 202 | Subordinate log created for object &1 &2 |
| 203 | External: &1 |
| 300 | Method "&1" not supported for SAP Global Track and Trace |
| 301 | Check entry for HCI logical system |
| 302 | SAP Track and Trace version has to be set to 'Global Track and Trace 1.0' |
| 303 | SAP EM version must not be set to GTT1.0 or GTT2.0 |
| 304 | Application object type "&1" already used for Global Track and Trace |