/BCV/SIN - Message class for SIN
The following messages are stored in message class /BCV/SIN: Message class for SIN.
It is part of development package /BCV/SIN in software component CA-EPT-BCV. This development package consists of objects that can be grouped under "".
It is part of development package /BCV/SIN in software component CA-EPT-BCV. This development package consists of objects that can be grouped under "".
Message Nr ▲ | Message Text |
---|---|
000 | System has updated fields; save changed data |
001 | Navigation to &1 is not allowed; select header entry first |
002 | Only one master system is allowed |
004 | Search connector ID &1: Values of field &2 are different in &3 (input) |
005 | Search connector ID &1: Field &2 does not exist (input) |
006 | Search connector ID &1: Enter InfoProvider |
007 | Search connector ID &1: Values of field &2 are different in &3 (output) |
008 | Search connector ID &1: Field &2 does not exist |
009 | Search connector ID &1: InfoProvider &2 does not exist in system &3 |
010 | Search connector ID &1: Search ID not found |
011 | Search connector ID &1: Data provider checked; parameters read |
012 | Search connector ID &1: Input and output parameters checked |
013 | Search connector ID &1: Invalid class name |
014 | Search connector ID &1: Invalid class name &2; change Customizing |
015 | Search connector ID &1: InfoProvider &2 does not exist; change Customizng |
016 | Search connector ID &1: Query &2 does not exist; change Customizing |
017 | RFC call failed; check connection to system &1 |
018 | Enter a search connector ID |
019 | No InfoProviders found; check your system entry |
020 | No queries found; check your system entry and InfoProvider entry |
021 | No values found; check system, InfoProvider, and your query |
022 | No values found; check class name |
023 | Search connector ID &1: Template ID &2 does not exist; correct the entry |
024 | Search connector ID &1: ID &2 does not exist; correct the entry |
025 | Search conn. ID &1: Srch req ID &3 does not exist for search conn. ID &2 |
027 | Search connector ID &1: Search conn ID is initial; enter search conn. ID |
028 | Search connector ID &1: Search request ID is initial; enter srch req ID |
029 | Search connector ID &1: Template ID is initial; enter template ID |
030 | Enter a valid system ID |
031 | Enter a valid business object |
032 | Enter a valid object type |
033 | Enter a valid business object and an object type |
034 | Search connector ID &2 is used in query &1 |
035 | Search connector ID &2 is not used in any query |
036 | Enter valid parameters |
037 | Test of RFC connection to system &1 was not successful |
038 | RFC connection to system &1 does not exist |
039 | RFC connection problems with system &1 |
040 | No systems found for search connector ID &1 |
041 | Creation of instance failed for search connector ID &1 |
042 | Configuration object &1 is not consistent |
043 | No export parameter defined for search connector ID &1 |
044 | Search connector ID &1: Technical name in BI is too long (&2) |
045 | Search connector ID &1: Enter port name |
046 | &1&2&3&4 |
047 | Generation of InfoSet search connector not possible |
048 | Search connector ID &1: The search connector is errornous |
049 | Search connector ID &1 is not used in any query |
050 | Search connector ID &1 is used in 1 query |
051 | Search connector ID &1 is used in &2 queries |
052 | Search connector ID &1 is used in query &2 |
053 | Not all queries could be shown because of insufficient authorizations |
054 | Search connector ID &1: Query &3 in InfoCube &2 does not exist |
055 | Search connector ID &1: Unknown conversion exit &3 in input field &2 |
056 | Search connector ID &1: Unknown conversion exit &3 in output field &2 |
057 | Search connector ID &1: System ID &2 not valid. |
058 | Search connector ID &1: Template ID &2 doesn't exist for Srch Conn ID &3 |
059 | Search connector ID &1: No valid length for field &2 specified |
060 | Search connector ID &1: No valid datatype for field &2 specified |
061 | Search connector ID &1: No valid data provision technology |
062 | Search connector ID &1: Port name &2 is not available |
063 | Choose "Reset fields" to update your input and output fields |
064 | Search connector ID &1: Enter class name |
065 | Changing the datatype may cause problems |
066 | Changing the length may cause problems |
067 | Changing the decimals may cause problems |
068 | InfoCube &1 does not exist, or connection to system &2 failed |
069 | Data element &1 does not exist |
070 | Conversion exit &1 does not exist |
071 | Search connector ID &1: Unknown data element &3 in input field &2 |
072 | Search connector ID &1: Unknown data element &3 in output field &2 |
073 | Search connector ID &1: InfoProvider &2 does not exist |
074 | Search connector ID &1: Interface type changed and system ID deleted |
075 | Search connector ID &1: Interface type changed |
076 | Search connector ID &1: Query &2 does not exist (interface type &3) |
077 | Search connector ID &1: InfoProv. &2 does not exist (interface type &3) |
078 | Search connector ID &1: BICS interface error ocurred |
079 | Easy Query interface is not available in system &1 |
080 | Select at least one search connector that uses Enterprise Search |
081 | Select valid transport request |
082 | &1 search connector(s) selected. Start adjustment process? |
083 | Search connector &1: Object is locked by user &2 |
084 | Search connector &1: Current ES connector ID is valid |
085 | Search connector &1: ES connector ID changed from &2 to &3 |
086 | Search connector &1: No suitable ES connector ID found |
087 | Search connector &1: Template ID &2 is invalid |
088 | Search connector &1: No authorization to change object |
089 | &1 search connector(s) adjusted |
090 | Search connector &1: Request ID &2 is invalid |
091 | BAPI &1 does not exist |