UKM - UKM Nachrichtenklasse

The following messages are stored in message class UKM: UKM Nachrichtenklasse.
It is part of development package S_UKM_IF in software component BC-SRV-UKM. This development package consists of objects that can be grouped under "Unified Key Mapping Interface".
Message Nr
Message Text
000Mapping could not be added
001Read lock could not be set for table &1
002Could not set exclusive lock for table &1
003No lock could be set for table &1
004Locks were set
005Mapping context &1 does not exist
006There is no mapping
007CCT identifer agency with the following values does not exist.
008SchemeAgencyID &1
009SchemeAgencySchemeID &1
010SchemeAgencySchemeAgencyID &1
011Schema with the following values does not exist:
012SchemeID &1
013SchemeVersionID &1
014CCT-ID agency with the following values could not be created:
015Schema with the following values could not be created:
016Internal AGENCY_ID &1 not found in UKM_AGENCY
017Internal SCHEME_ID &1 not found in UKM_SCHEME
018Table UMK_AGENCY could not be locked against write access
019Table UMK_SCHEME could not be locked against write access
020Persistence object for context Main: &1 Sub: &2 could not be created
021CCT IDs cannot be created: SchemeID is initial
022CCT ID value is initial
023Data not deleted
024Mapping context &1 / &2 successfully created
025Mapping context &1 / &2 could not be registered
026Database table &1 not found
027Mapping context &1 / &2 already registered
028Mapping context &1 / &2 successfully registered
029Database table &1 already exists
030Database table &1 could not be created
031Database table &1 successfully created
032Database table &1 successfully activated
033Database table &1 could not be activated
034Index &1 for database table &2 successfully created
035Index &1 for database table &2 successfully activated
036Index &1 for database table &2 could not be created
037Index &1 for database table &2 could not be activated
038Database table &1 could not be deleted
039Database table &1 successfully deleted
040Mapping context &1 / &2 successfully deregistered
041Mapping context &1 / &2 already instantiated
042Mapping context &1 / &2 successfully instantiated
043Mapping context &1 / &2 not found
044Mapping context &1 / &2 could not be instantiated
045Mapping context &1 / &2 locked
046Mapping context &1 / &2 already exists
047No free mapping context code found for &1
048Index &1 for database table &2 successfully deleted
049Index &1 for database table &2 could not be deleted
050Possible context codes exhausted
051Maximum number of buffer entries reached
052Mapping context &1 / &2 already registered
053Database table &1 not found
054Generated copy of &1 (&2 &3)
055Mapping added
056Mapping deleted
057Mapping found
058Changes saved
059Changes discarded
060Mapping not found
061Processing terminated without warnings
062Processing completed, but with warnings
063Processing completed, but has errors
064CCT-Identifier with the following values does not exist:
065CCT-Identifier with the following values is marked for deletion:
066CCT-Identifier value and ID are initial
067Internal AGENCY_ID &1 not found in table &2
068Internal SCHEME_ID &1 not found in table &2
069Unexpected agency &1 in object (expected: &2)
070Internal key agency &1 not found
071Internal key schema &1 not found
072Conversion could not be executed
073Call does not contain any data
074Mapping must contain at least 2 objects
075Object must contain at least 1 key
076Object not found
077Key not found
078Key &1 not found
079No context was selected
080No existing schemeAgencyID specified
081No new schemeAgencyID specified
082New and existing schemeAgencyID must be different
083schemeAgencyID &1 not found
084schemeAgencyID &1 already exists
085Entries were checked
086Could not lock database table &1
087Change successfully executed
088Error occurred during execution (rollback)
089Mapping context &1 does not contain data
090A general exception was raised
091This combination of parameters is not supported
092&1 (based on &2)
093Context &1
094Database tables were generated when saving
095Database tables will become obsolete when saving
096Source key corresponds to target key
097Update of long key values requires exclusive locks
098Update of existing keys requires exclusive locks
Privacy Policy