SAP ABAP Message Class ESH_TAC_MSG (Checks (Test Framework))
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-EIM-ESH (Application Component) NetWeaver Enterprise Search
⤷
S_ESH_TST_AUT_CHECKS (Package) Checks for the test framework (category, task)
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-EIM-ESH (Application Component) NetWeaver Enterprise Search⤷
S_ESH_TST_AUT_CHECKS (Package) Checks for the test framework (category, task) 
Attributes
| Message class |  |
ESH_TAC_MSG |
| Short Description |  |
Checks (Test Framework) |
| Changed On |  |
20140121 |
| Last Changed At |  |
103723 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
Check processed | The short text describes the object sufficiently | |
| 2 | 001 |
Coming soon ... | The short text describes the object sufficiently | |
| 3 | 002 |
TREX RFC destination &1 is OK | The short text describes the object sufficiently | |
| 4 | 003 |
&1 | The short text describes the object sufficiently | |
| 5 | 004 |
No TREX destination defined for ESH | The short text describes the object sufficiently | |
| 6 | 005 |
TREX RFC destination &1 does not work | The short text describes the object sufficiently | |
| 7 | 006 |
EPM Auto - one or both PO and text connectors is not registered for RTI | The short text describes the object sufficiently | |
| 8 | 007 |
Error occurred while pinging RFC destination &1 for system &2: &3 | The short text describes the object sufficiently | |
| 9 | 008 |
RFC destination &1 for system &2 is OK | The short text describes the object sufficiently | |
| 10 | 009 |
EPM Auto: PO and text connectors are registered for RTI | The short text describes the object sufficiently | |
| 11 | 010 |
No records found in EPM AUTO: PO with lifecycle status New. Generate data | The short text describes the object sufficiently | |
| 12 | 011 |
Precheck, EPM Auto: PO, po_id = &1 is inconsistent with the table SNWD_PO | The short text describes the object sufficiently | |
| 13 | 012 |
Precheck is OK, EPM Auto: PO and table SNWD_PO records are consistent | The short text describes the object sufficiently | |
| 14 | 013 |
RTI push with data in change pointer is working as expected | The short text describes the object sufficiently | |
| 15 | 014 |
RTI push with data in CP is not working as expected. Check it manually | The short text describes the object sufficiently | |
| 16 | 015 |
EPM Auto: Connectors can be used for searching | The short text describes the object sufficiently | |
| 17 | 016 |
EPM Auto: Connectors are not available - unit test NOT executed | The short text describes the object sufficiently | |
| 18 | 017 |
Error: Unexpected exception has been raised; message: &1 | The short text describes the object sufficiently | |
| 19 | 018 |
Import of EPM Auto SWC to NW Enterprise Search Repository was successful | The short text describes the object sufficiently | |
| 20 | 019 |
Model unknown, obj. type import must have been unsuccessful | The short text describes the object sufficiently | |
| 21 | 020 |
Model ID unknown, object type import must have been unsuccessful | The short text describes the object sufficiently | |
| 22 | 021 |
Model unknown, object type import must have been unsuccessful | The short text describes the object sufficiently | |
| 23 | 022 |
Connectors are created and prepared successfully | The short text describes the object sufficiently | |
| 24 | 023 |
Category could not be instantiated | The short text describes the object sufficiently | |
| 25 | 024 |
No Authorization to create instance to Object Types | The short text describes the object sufficiently | |
| 26 | 025 |
Exception occurred during retrieval of category IDs | The short text describes the object sufficiently | |
| 27 | 026 |
Exception occurred when retrieving parent category of child category | The short text describes the object sufficiently | |
| 28 | 027 |
Error when instantiating a connector | Space: object requires documentation | |
| 29 | 028 |
No Connectors available for more testing | Space: object requires documentation | |
| 30 | 029 |
Connector instance provided unexpected connector ID | Space: object requires documentation | |
| 31 | 030 |
Connector instance provided unbound request_type | Space: object requires documentation | |
| 32 | 031 |
Unexpected amount of request attribute type objects | Space: object requires documentation | |
| 33 | 032 |
Error when instantiating a request type | Space: object requires documentation | |
| 34 | 033 |
Connector instance provided initial response_attribute_type | Space: object requires documentation | |
| 35 | 034 |
Attribute type object returned unbound | Space: object requires documentation | |
| 36 | 035 |
Wrong attribute type returned | Space: object requires documentation | |
| 37 | 036 |
Existing response attribute type could not get retrieved | Space: object requires documentation | |
| 38 | 037 |
Connector instance provided initial response attribute group. | Space: object requires documentation | |
| 39 | 038 |
Connector instance provided unbound response attribute | Space: object requires documentation | |
| 40 | 039 |
Connector instance provided unbound related connector | Space: object requires documentation | |
| 41 | 040 |
Connector instance provided initial relation type | Space: object requires documentation | |
| 42 | 041 |
Connector instance provided unbound UI area | Space: object requires documentation | |
| 43 | 042 |
Connector instance provided UI area without entities | Space: object requires documentation | |
| 44 | 043 |
Connector instance provided unexpected searchable flag | Space: object requires documentation | |
| 45 | 044 |
Connector instance provided unexpected local flag | Space: object requires documentation | |
| 46 | 045 |
Connector instance did not provide response attribute types | Space: object requires documentation | |
| 47 | 046 |
Connector instance provided initial layout template | Space: object requires documentation | |
| 48 | 047 |
Unexpected amount of layout templates | Space: object requires documentation | |
| 49 | 048 |
Connector instance provided a layout template of a wrong platform | Space: object requires documentation | |
| 50 | 049 |
Connector instance provided unexpected amount of related connectors | Space: object requires documentation | |
| 51 | 050 |
Connector instance provided unexpected amount of connector relations | Space: object requires documentation | |
| 52 | 051 |
Connector instance provided unbound connector relation | Space: object requires documentation | |
| 53 | 052 |
Connector instance provided unbound request attribute | Space: object requires documentation | |
| 54 | 053 |
Connector relation provided an unexpected exception | Space: object requires documentation | |
| 55 | 054 |
Connector instance provided unbound parameter | Space: object requires documentation |
History
| Last changed on/by | |
20140121 | SAP |
| SAP Release Created in | 730 |
