SAP ABAP Message Class /BCV/SIN (Message class for SIN)
Basic Data
Hierarchy
☛
SAP_BS_FND (Software Component) SAP Business Suite Foundation
⤷
CA-EPT-BCV (Application Component) Business Context Viewer
⤷
/BCV/SIN (Package) BCV Search Integration Layer
SAP_BS_FND (Software Component) SAP Business Suite Foundation⤷
CA-EPT-BCV (Application Component) Business Context Viewer⤷
/BCV/SIN (Package) BCV Search Integration Layer 
Attributes
| Message class |  |
/BCV/SIN |
| Short Description |  |
Message class for SIN |
| Changed On |  |
20130531 |
| Last Changed At |  |
122858 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
System has updated fields; save changed data | Space: object requires documentation | |
| 2 | 001 |
Navigation to &1 is not allowed; select header entry first | The short text describes the object sufficiently | |
| 3 | 002 |
Only one master system is allowed | The short text describes the object sufficiently | |
| 4 | 004 |
Search connector ID &1: Values of field &2 are different in &3 (input) | Space: object requires documentation | |
| 5 | 005 |
Search connector ID &1: Field &2 does not exist (input) | Space: object requires documentation | |
| 6 | 006 |
Search connector ID &1: Enter InfoProvider | The short text describes the object sufficiently | |
| 7 | 007 |
Search connector ID &1: Values of field &2 are different in &3 (output) | Space: object requires documentation | |
| 8 | 008 |
Search connector ID &1: Field &2 does not exist | Space: object requires documentation | |
| 9 | 009 |
Search connector ID &1: InfoProvider &2 does not exist in system &3 | The short text describes the object sufficiently | |
| 10 | 010 |
Search connector ID &1: Search ID not found | The short text describes the object sufficiently | |
| 11 | 011 |
Search connector ID &1: Data provider checked; parameters read | The short text describes the object sufficiently | |
| 12 | 012 |
Search connector ID &1: Input and output parameters checked | The short text describes the object sufficiently | |
| 13 | 013 |
Search connector ID &1: Invalid class name | The short text describes the object sufficiently | |
| 14 | 014 |
Search connector ID &1: Invalid class name &2; change Customizing | The short text describes the object sufficiently | |
| 15 | 015 |
Search connector ID &1: InfoProvider &2 does not exist; change Customizng | The short text describes the object sufficiently | |
| 16 | 016 |
Search connector ID &1: Query &2 does not exist; change Customizing | The short text describes the object sufficiently | |
| 17 | 017 |
RFC call failed; check connection to system &1 | The short text describes the object sufficiently | |
| 18 | 018 |
Enter a search connector ID | The short text describes the object sufficiently | |
| 19 | 019 |
No InfoProviders found; check your system entry | The short text describes the object sufficiently | |
| 20 | 020 |
No queries found; check your system entry and InfoProvider entry | The short text describes the object sufficiently | |
| 21 | 021 |
No values found; check system, InfoProvider, and your query | The short text describes the object sufficiently | |
| 22 | 022 |
No values found; check class name | The short text describes the object sufficiently | |
| 23 | 023 |
Search connector ID &1: Template ID &2 does not exist; correct the entry | The short text describes the object sufficiently | |
| 24 | 024 |
Search connector ID &1: ID &2 does not exist; correct the entry | The short text describes the object sufficiently | |
| 25 | 025 |
Search conn. ID &1: Srch req ID &3 does not exist for search conn. ID &2 | The short text describes the object sufficiently | |
| 26 | 027 |
Search connector ID &1: Search conn ID is initial; enter search conn. ID | The short text describes the object sufficiently | |
| 27 | 028 |
Search connector ID &1: Search request ID is initial; enter srch req ID | The short text describes the object sufficiently | |
| 28 | 029 |
Search connector ID &1: Template ID is initial; enter template ID | The short text describes the object sufficiently | |
| 29 | 030 |
Enter a valid system ID | The short text describes the object sufficiently | |
| 30 | 031 |
Enter a valid business object | The short text describes the object sufficiently | |
| 31 | 032 |
Enter a valid object type | The short text describes the object sufficiently | |
| 32 | 033 |
Enter a valid business object and an object type | The short text describes the object sufficiently | |
| 33 | 034 |
Search connector ID &2 is used in query &1 | The short text describes the object sufficiently | |
| 34 | 035 |
Search connector ID &2 is not used in any query | The short text describes the object sufficiently | |
| 35 | 036 |
Enter valid parameters | The short text describes the object sufficiently | |
| 36 | 037 |
Test of RFC connection to system &1 was not successful | The short text describes the object sufficiently | |
| 37 | 038 |
RFC connection to system &1 does not exist | The short text describes the object sufficiently | |
| 38 | 039 |
RFC connection problems with system &1 | The short text describes the object sufficiently | |
| 39 | 040 |
No systems found for search connector ID &1 | The short text describes the object sufficiently | |
| 40 | 041 |
Creation of instance failed for search connector ID &1 | The short text describes the object sufficiently | |
| 41 | 042 |
Configuration object &1 is not consistent | The short text describes the object sufficiently | |
| 42 | 043 |
No export parameter defined for search connector ID &1 | The short text describes the object sufficiently | |
| 43 | 044 |
Search connector ID &1: Technical name in BI is too long (&2) | The short text describes the object sufficiently | |
| 44 | 045 |
Search connector ID &1: Enter port name | The short text describes the object sufficiently | |
| 45 | 046 |
&1&2&3&4 | The short text describes the object sufficiently | |
| 46 | 047 |
Generation of InfoSet search connector not possible | Space: object requires documentation | |
| 47 | 048 |
Search connector ID &1: The search connector is errornous | The short text describes the object sufficiently | |
| 48 | 049 |
Search connector ID &1 is not used in any query | The short text describes the object sufficiently | |
| 49 | 050 |
Search connector ID &1 is used in 1 query | The short text describes the object sufficiently | |
| 50 | 051 |
Search connector ID &1 is used in &2 queries | The short text describes the object sufficiently | |
| 51 | 052 |
Search connector ID &1 is used in query &2 | The short text describes the object sufficiently | |
| 52 | 053 |
Not all queries could be shown because of insufficient authorizations | The short text describes the object sufficiently | |
| 53 | 054 |
Search connector ID &1: Query &3 in InfoCube &2 does not exist | The short text describes the object sufficiently | |
| 54 | 055 |
Search connector ID &1: Unknown conversion exit &3 in input field &2 | Space: object requires documentation | |
| 55 | 056 |
Search connector ID &1: Unknown conversion exit &3 in output field &2 | Space: object requires documentation | |
| 56 | 057 |
Search connector ID &1: System ID &2 not valid. | The short text describes the object sufficiently | |
| 57 | 058 |
Search connector ID &1: Template ID &2 doesn't exist for Srch Conn ID &3 | The short text describes the object sufficiently | |
| 58 | 059 |
Search connector ID &1: No valid length for field &2 specified | The short text describes the object sufficiently | |
| 59 | 060 |
Search connector ID &1: No valid datatype for field &2 specified | The short text describes the object sufficiently | |
| 60 | 061 |
Search connector ID &1: No valid data provision technology | The short text describes the object sufficiently | |
| 61 | 062 |
Search connector ID &1: Port name &2 is not available | The short text describes the object sufficiently | |
| 62 | 063 |
Choose "Reset fields" to update your input and output fields | The short text describes the object sufficiently | |
| 63 | 064 |
Search connector ID &1: Enter class name | The short text describes the object sufficiently | |
| 64 | 065 |
Changing the datatype may cause problems | The short text describes the object sufficiently | |
| 65 | 066 |
Changing the length may cause problems | The short text describes the object sufficiently | |
| 66 | 067 |
Changing the decimals may cause problems | The short text describes the object sufficiently | |
| 67 | 068 |
InfoCube &1 does not exist, or connection to system &2 failed | The short text describes the object sufficiently | |
| 68 | 069 |
Data element &1 does not exist | The short text describes the object sufficiently | |
| 69 | 070 |
Conversion exit &1 does not exist | The short text describes the object sufficiently | |
| 70 | 071 |
Search connector ID &1: Unknown data element &3 in input field &2 | The short text describes the object sufficiently | |
| 71 | 072 |
Search connector ID &1: Unknown data element &3 in output field &2 | The short text describes the object sufficiently | |
| 72 | 073 |
Search connector ID &1: InfoProvider &2 does not exist | The short text describes the object sufficiently | |
| 73 | 074 |
Search connector ID &1: Interface type changed and system ID deleted | The short text describes the object sufficiently | |
| 74 | 075 |
Search connector ID &1: Interface type changed | The short text describes the object sufficiently | |
| 75 | 076 |
Search connector ID &1: Query &2 does not exist (interface type &3) | The short text describes the object sufficiently | |
| 76 | 077 |
Search connector ID &1: InfoProv. &2 does not exist (interface type &3) | The short text describes the object sufficiently | |
| 77 | 078 |
Search connector ID &1: BICS interface error ocurred | The short text describes the object sufficiently | |
| 78 | 079 |
Easy Query interface is not available in system &1 | The short text describes the object sufficiently |
History
| Last changed on/by | |
20130531 | SAP |
| SAP Release Created in | 701 |
