| UKM092 |
&1 (based on &2) |
| UKM093 |
Context &1 |
| UKM094 |
Database tables were generated when saving |
| UKM095 |
Database tables will become obsolete when saving |
| UKM096 |
Source key corresponds to target key |
| UKMPI000 |
***** Consistency: UKMPI |
| UKMPI001 |
No key mapping found for message &1 namespace &2 |
| UKMPI002 |
Key mapping &1 found for message &2 namespace &3 |
| UKMPI003 |
Path inconsistent: Element levels are not sequentially numbered |
| UKMPI004 |
Condition &1 inconsistent: Element missing |
| UKMPI005 |
Element mapping &1 inconsistent; element missing |
| UKMPI006 |
Parsing error |
| UKMPI008 |
No element mapping created for mapping &1 |
| UKMPI010 |
***** Processing: UKMPI |
| UKMPI011 |
Not all subtrees of path leaves used in key mapping |
| UKMPI012 |
Condition check of subtree of leaf &2 at position &1 used in key mapping: |
| UKMPI013 |
Contents of element &1 assigned from &2 to &3 |
| UKMPI014 |
Contents of attribute &1 element &2 assigned from &3 to &4 |
| UKMPI017 |
Condition check of subtree of leaf &2 at position &1: |
| UKMPI018 |
Condition check of element &1 with value &2 successful |
| UKMPI019 |
Condition check of attribute &1 element &2 with value &3 successful |
| UKMPI022 |
Could not construct path from message &1 |
| UKMPI026 |
***** Prozessing: UKMPI <--> UKM |
| UKMPI028 |
No key mapping found for context &1, sender &2, key &3 |
| UKMPI032 |
Key mapping for context &1, sender &2, sender key &3 --> |
| UKMPI033 |
Receiver &1, receiver key &2 found |
| UKMPI034 |
Receiver &1 found does not agree with receiver &2 |
| UKMPI036 |
New key mapping for context &1, sender &2, sender key &3 --> |
| UKMPI037 |
Receiver &1, receiver key &2 created |
| UKMPI038 |
Internal error while creating key mapping |
| UKMPI041 |
***** Consistency: Mapping interface |
| UKMPI042 |
Sender is empty |
| UKMPI043 |
Receiver is empty |
| UKMPI044 |
Message interface is empty |
| UKMPI045 |
Message namespace is empty |
| UKMPI046 |
Receiver is not empty; receiver not determined |
| UKM_BP000 |
&1 &2 &3 &4 |
| UKM_BP001 |
You are not authorized to change credit segment & |
| UKM_BP002 |
You are not authorized to display credit segment & |
| UKM_BP003 |
You are not authorized to delete credit segment & |
| UKM_BP004 |
Error in rule &1: &2 |
| UKM_BP005 |
Risk class error: &1 |
| UKM_BP006 |
Error in limit calculation: &1 |
| UKM_BP007 |
The validity date of the credit limit is in the past |
| UKM_BP008 |
The resubmission date is in the past |
| UKM_BP009 |
The validity date of the score is in the past |
| UKM_BP010 |
Risk class has been changed |
| UKM_BP011 |
Error occurred in formula &1 |
| UKM_BP012 |
No risk class defined for score with value &1 |
| UKM_BP013 |
Score has changed |
| UKM_BP014 |
Delete the other credit segments before the main segment |
| UKM_BP015 |
Credit limit increased |
| UKM_BP016 |
Credit limit reduced |
| UKM_BP017 |
Credit segment &1 does not exist |
| UKM_BP018 |
Customer credit group &1 does not exist |
| UKM_BP019 |
User &1 does not exist |
| UKM_BP020 |
Fill the fields Information Category and Information Type |
| UKM_BP021 |
The combination info. category &1 and info. type &2 is not supported |
| UKM_BP022 |
The data is incorrect, it cannot be saved |
| UKM_BP023 |
Information category &1 is not permitted for credit segment |
| UKM_BP024 |
You are not authorized to view change documents in Credit Management |
| UKM_BP031 |
Exposure Changed |
| UKM_BP085 |
First select a valid credit segment |
| UKM_BP099 |
Specify the rating procedure required |
| UKM_BP100 |
No data import possible for rating procedure &1 |
| UKM_BP101 |
Error requesting data for rating procedure &1 |
| UKM_BP102 |
Incorrect Call - No Selection Specified |
| UKM_BP103 |
You are not authorized to approve the limit |
| UKM_CHECK001 |
Credit limit &1 &2 exceeded by &3 &4 |
| UKM_CHECK002 |
Currency &1 could not be translated to &2 for &3 |
| UKM_CHECK003 |
The lock indicator in credit segment &1 has lock reason &2 |
| UKM_CHECK004 |
Maximum document value was exceeded by & & |
| UKM_CHECK005 |
Dunning level &1 exceeds maximum dunning level &2 |
| UKM_CHECK006 |
Credit check executed with rule & |
| UKM_CHECK007 |
Check was successful |
| UKM_CHECK008 |
Check was not successful |
| UKM_CHECK009 |
Total liability & & does not exceed the credit limit & & |
| UKM_CHECK010 |
Document value & & does not exceed the maximum document value & & |
| UKM_CHECK011 |
Dunning level & does not exceed the maximum dunning level & |
| UKM_CHECK012 |
Dunning level & is invalid |
| UKM_CHECK013 |
The data for the oldest open item is invalid |
| UKM_CHECK014 |
Oldest open item is & days overdue |
| UKM_CHECK015 |
Oldest open item is less than & days overdue |
| UKM_CHECK016 |
Invalid or initial data for payment behavior index in credit segment &1 |
| UKM_CHECK017 |
Payment behavior: Key figure has value &1, maximum value is &2 |
| UKM_CHECK018 |
Payment behavior: Key figure is less than & |
| UKM_CHECK019 |
Payment behavior: Check amount has value &1 &2, maximum value is &3 &4 |
| UKM_CHECK020 |
Payment behavior: Check amount is less than & & |
| UKM_CHECK021 |
No check rule defined for business partner &1 |
| UKM_CHECK022 |
Liability from system &1 could not be determined |
| UKM_CHECK023 |
Payment behavior: Key figure has value &1, minimum value is &1 |
| UKM_CHECK024 |
Partner &1 does not exist |
| UKM_CHECK025 |
No log found for document &1 |
| UKM_CHECK026 |
Credit segment &1 of partner &2 |
| UKM_CHECK027 |
Document data &1 is not in credit horizon &2 |
| UKM_CHECK028 |
Old credit exposure in credit horizon &1 &2 &3 |
| UKM_COMM001 |
Conflicting lock with &1: &2 |
| UKM_COMM002 |
System error during locking |
| UKM_COMM003 |
Recursive definiton of relationship with partner &1 |
| UKM_COMM004 |
Details in spool: & |