SAP ABAP Message Class GRFNMW (MSMP Engine Message Class)
Basic Data
Hierarchy
☛
GRCFND_A (Software Component) GRC Foundation ABAP
⤷
GRC (Application Component) Governance, Risk and Compliance
⤷
GRFN_MSMP_WORKFLOW (Package) GRC Shared MSMP Engine
GRCFND_A (Software Component) GRC Foundation ABAP⤷
GRC (Application Component) Governance, Risk and Compliance⤷
GRFN_MSMP_WORKFLOW (Package) GRC Shared MSMP Engine 
Attributes
| Message class |  |
GRFNMW |
| Short Description |  |
MSMP Engine Message Class |
| Changed On |  |
20141106 |
| Last Changed At |  |
194350 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
&1&2&3&4 | The short text describes the object sufficiently | |
| 2 | 001 |
MSMP runtime instance &1 is locked by user &2 | The short text describes the object sufficiently | |
| 3 | 002 |
MSMP rule type &1 is not supported | The short text describes the object sufficiently | |
| 4 | 003 |
MSMP instance &1 header is locked by user &2 | The short text describes the object sufficiently | |
| 5 | 004 |
MSMP instance &1 line item &2 is locked by user &3 | The short text describes the object sufficiently | |
| 6 | 005 |
Rule validation failed for function ID &1 | The short text describes the object sufficiently | |
| 7 | 006 |
Changes were found in table &1 for process &2 (active version &3) | The short text describes the object sufficiently | |
| 8 | 007 |
No changes were found in table &1 for process &2 (active version &3) | The short text describes the object sufficiently | |
| 9 | 008 |
MSMP configuration view is locked by user &1 | The short text describes the object sufficiently | |
| 10 | 009 |
Active version &1 was generated; new records were created for process &2 | The short text describes the object sufficiently | |
| 11 | 010 |
No changes were found for process &1; no new version was generated | The short text describes the object sufficiently | |
| 12 | 011 |
No process found for the selected criteria | The short text describes the object sufficiently | |
| 13 | 012 |
No active version exists for process &1 | The short text describes the object sufficiently | |
| 14 | 013 |
No data is maintained in table &1 for process &2 | The short text describes the object sufficiently | |
| 15 | 014 |
Active version data not stored for table &1 process &2 | The short text describes the object sufficiently | |
| 16 | 015 |
User &1 is not a recognized approver | The short text describes the object sufficiently | |
| 17 | 016 |
Data read at &1 was changed by another user at &2 | The short text describes the object sufficiently | |
| 18 | 017 |
Error when deserializing data to DDIC structure &1 | The short text describes the object sufficiently | |
| 19 | 018 |
DDIC mismatch; configuration &1 <> runtime data &2 | The short text describes the object sufficiently | |
| 20 | 019 |
Error creating MSMP instance; GUID generation failed | The short text describes the object sufficiently | |
| 21 | 020 |
Enter either external key ID, instance ID, or work item IDs | The short text describes the object sufficiently | |
| 22 | 021 |
Line items &2 of request &1 found in the error status in path &3/&4 | The short text describes the object sufficiently | |
| 23 | 022 |
Process &1 is not configured correctly | The short text describes the object sufficiently | |
| 24 | 023 |
Incorrect path and stage class entry for process &1 | The short text describes the object sufficiently | |
| 25 | 024 |
No data found for process type &1 | The short text describes the object sufficiently | |
| 26 | 025 |
No process found for instance ID &1 | The short text describes the object sufficiently | |
| 27 | 026 |
No routing rule found for process &1 version &2 rule type &3 | The short text describes the object sufficiently | |
| 28 | 027 |
No stage task value table found for path stage type '&1' task '&2' | The short text describes the object sufficiently | |
| 29 | 028 |
Stage configuration not defined for path stage type '&1' version '&2' | The short text describes the object sufficiently | |
| 30 | 029 |
Stage configuration values not defined for path stage '&1' config ID '&2' | The short text describes the object sufficiently | |
| 31 | 030 |
No process type found for process &1 | The short text describes the object sufficiently | |
| 32 | 031 |
No stages defined for process &1 path &2 version &3 | The short text describes the object sufficiently | |
| 33 | 032 |
No stage details found for process &1 path &2 stage &3 version &4 | The short text describes the object sufficiently | |
| 34 | 033 |
No initiator found for process &1 version &2 | The short text describes the object sufficiently | |
| 35 | 034 |
Path stage type not found for process &1 version &2 | The short text describes the object sufficiently | |
| 36 | 035 |
No relevant request found with external key &1 | The short text describes the object sufficiently | |
| 37 | 036 |
More than one instance found for the request with external key &1 | The short text describes the object sufficiently | |
| 38 | 037 |
MSMP instance &1 path &2, stage &3 is locked by user &4 | The short text describes the object sufficiently | |
| 39 | 038 |
Error when updating request instance ID &1 | The short text describes the object sufficiently | |
| 40 | 039 |
Error when updating the header of MSMP instance &1 | The short text describes the object sufficiently | |
| 41 | 040 |
Error when updating line item &2 of MSMP instance &1 | The short text describes the object sufficiently | |
| 42 | 041 |
Error when generating a new version &2 for process &1 | The short text describes the object sufficiently | |
| 43 | 042 |
Error when reading data of the MSMP work item &1 | The short text describes the object sufficiently | |
| 44 | 043 |
Work item &1 is incompatible with instance &2 or stage configuration &3 | The short text describes the object sufficiently | |
| 45 | 044 |
Error while retrieving MSMP execution context info for work item &1 | The short text describes the object sufficiently | |
| 46 | 045 |
MSMP instance &1 not found | The short text describes the object sufficiently | |
| 47 | 046 |
Database error &1 | The short text describes the object sufficiently | |
| 48 | 047 |
Line item &1 already exists for MSMP instance &2 | The short text describes the object sufficiently | |
| 49 | 048 |
Error resolving the path for the request with external key &1 process &2 | The short text describes the object sufficiently | |
| 50 | 049 |
No path is mapped to routing result &1, external key &2, process &3 | The short text describes the object sufficiently | |
| 51 | 050 |
Error creating data log entry for instance ID &1 | The short text describes the object sufficiently | |
| 52 | 051 |
Workflow process &1 path &2 version &3 failed to start | The short text describes the object sufficiently | |
| 53 | 052 |
Request submission inconsistent; process &1, version &2, external ID &3 | The short text describes the object sufficiently | |
| 54 | 053 |
Error reading instance status ext. key &1 process &2 instance &3 | The short text describes the object sufficiently | |
| 55 | 054 |
Error reading configuration process ID &1 version &2 | The short text describes the object sufficiently | |
| 56 | 055 |
Configuration error when reading the stage sequence by index &1 | The short text describes the object sufficiently | |
| 57 | 056 |
Error while reading the escalation settings; failed to resolve agent | The short text describes the object sufficiently | |
| 58 | 057 |
Configuration error while reading escalation settings | The short text describes the object sufficiently | |
| 59 | 058 |
Error whle reading the escalation settings | The short text describes the object sufficiently | |
| 60 | 059 |
Error whle reading the number of stages for the path | The short text describes the object sufficiently | |
| 61 | 060 |
Error while updating the path status | The short text describes the object sufficiently | |
| 62 | 061 |
Error when updating the line item approval status; failed to aggregate | The short text describes the object sufficiently | |
| 63 | 062 |
Error when updating the line item approval status | The short text describes the object sufficiently | |
| 64 | 063 |
Error when updating runtime execution details; failed to aggregate | The short text describes the object sufficiently | |
| 65 | 064 |
Error when updating runtime execution details | The short text describes the object sufficiently | |
| 66 | 065 |
Error while reading the configuration | The short text describes the object sufficiently | |
| 67 | 066 |
Error when trying to complete/forward work item &1 | The short text describes the object sufficiently | |
| 68 | 067 |
MSMP instance &1 is not in running state; current state is &2 | The short text describes the object sufficiently | |
| 69 | 068 |
Error when reading line item &2 for MSMP instance &1 | The short text describes the object sufficiently | |
| 70 | 069 |
Error while calculating the end of the path for &1 path and &2 sequence | The short text describes the object sufficiently | |
| 71 | 070 |
Line item &1 was not found; cannot remove | The short text describes the object sufficiently | |
| 72 | 071 |
Line item &1 already exists; cannot add another line item with same ID | The short text describes the object sufficiently | |
| 73 | 072 |
Requested object cannot be locked | The short text describes the object sufficiently | |
| 74 | 073 |
Rule ID &3 (rule type &2) is not registered for process type &1 | The short text describes the object sufficiently | |
| 75 | 074 |
Rule ID &3 (rule type &2) is not compatible with process type &1 | The short text describes the object sufficiently | |
| 76 | 075 |
Failed to determine agent | The short text describes the object sufficiently | |
| 77 | 076 |
Failed to determine escalation agent | The short text describes the object sufficiently | |
| 78 | 077 |
Cannot create rule parameters table (context &1/&2, DDICs &3/&4) | The short text describes the object sufficiently | |
| 79 | 078 |
MSMP instance already exists with external key &1 and process ID &2 | The short text describes the object sufficiently | |
| 80 | 079 |
Wrong class-based rule ID &1; not implementing interface &2 or &3 | The short text describes the object sufficiently | |
| 81 | 080 |
Rule ID &4, type &3 was not implemented for process type &1, rule type &2 | The short text describes the object sufficiently | |
| 82 | 081 |
Routing rule &2/&3 in process &1; stage level routing not recognized | The short text describes the object sufficiently | |
| 83 | 082 |
Rule-based agent ID &1 returned an unknown approver ID &2 | The short text describes the object sufficiently | |
| 84 | 083 |
Mandatory parameter &1 not found in the rule parameter table | The short text describes the object sufficiently | |
| 85 | 084 |
Rule parameter &1 has incompatible type &2; enter type &3 or &4 | The short text describes the object sufficiently | |
| 86 | 085 |
Specify mapping class for conversion from DDIC &1 to &2 | The short text describes the object sufficiently | |
| 87 | 086 |
Error when reading line item &1 | The short text describes the object sufficiently | |
| 88 | 087 |
Class &3 for conversion from DDIC &1 to &2 cannot be instantiated | The short text describes the object sufficiently | |
| 89 | 088 |
Class &3 does not support conversion from DDIC &1 to &2 | The short text describes the object sufficiently | |
| 90 | 089 |
Class &3 conversion from DDIC &1 to &2 failed | The short text describes the object sufficiently | |
| 91 | 090 |
Rule parameter &1 must be based on the DDIC structure (current type &2) | The short text describes the object sufficiently | |
| 92 | 091 |
Rule parameter &1; actual data type '&3', declared as '&2' - mismatch | The short text describes the object sufficiently | |
| 93 | 092 |
Rule &1/&2/&3 is being validated ... | The short text describes the object sufficiently | |
| 94 | 093 |
Rule &1/&2/&3 was validated | The short text describes the object sufficiently | |
| 95 | 094 |
Rule &1/&2/&3 is executing ... | The short text describes the object sufficiently | |
| 96 | 095 |
Rule &1/&2/&3; checking input parameters ... | The short text describes the object sufficiently | |
| 97 | 096 |
Rule &1/&2/&3 executed | The short text describes the object sufficiently | |
| 98 | 097 |
Error during execution of rule &1/&2/&3 | The short text describes the object sufficiently | |
| 99 | 098 |
Rule &1/&2/&3 returned results | The short text describes the object sufficiently | |
| 100 | 099 |
Rule &1/&2/&3; no results retrieved | The short text describes the object sufficiently | |
| 101 | 100 |
No conversion is necessary for rule &1, &2, and &3 input parameters | The short text describes the object sufficiently | |
| 102 | 101 |
Rule &1/&2/&3 - request header converted to type &4 | The short text describes the object sufficiently | |
| 103 | 102 |
Rule &1/&2/&3 - line items converted to type &4 | The short text describes the object sufficiently | |
| 104 | 103 |
Rule &1/&2/&3 - conversion of input parameters failed | The short text describes the object sufficiently | |
| 105 | 104 |
Conversion failed for source DDIC structure &1; no data was passed | The short text describes the object sufficiently | |
| 106 | 105 |
Conversion failed for target DDIC structure &1; cannot create work area | The short text describes the object sufficiently | |
| 107 | 106 |
Conversion failed for source DDIC structure &1; incompatible data passed | The short text describes the object sufficiently | |
| 108 | 107 |
Unexpected error during conversion from DDIC &1 to DDIC &2 | The short text describes the object sufficiently | |
| 109 | 108 |
Exception occurred for process &2, database &1 | The short text describes the object sufficiently | |
| 110 | 109 |
Trying to activate next process ID &1 | The short text describes the object sufficiently | |
| 111 | 110 |
Error when generating MSMP rule of type &1/&2 for process &3 | The short text describes the object sufficiently | |
| 112 | 111 |
Generation of rule of type &1/&2 for process &3 is not supported | The short text describes the object sufficiently | |
| 113 | 112 |
Rule of type &1/&2 for process &3 was generated | The short text describes the object sufficiently | |
| 114 | 113 |
Rule ID &1 is not in the customer namespace | The short text describes the object sufficiently | |
| 115 | 114 |
Rule application and group ID &1 are not in the customer namespace | The short text describes the object sufficiently | |
| 116 | 115 |
Error in agent determination for agent ID &1, type &2, object &3 | The short text describes the object sufficiently | |
| 117 | 116 |
Generating rule type &1/&2 for process &3; the rule name is &4 | The short text describes the object sufficiently | |
| 118 | 117 |
Rule ID = &1, rule type = &2 | The short text describes the object sufficiently | |
| 119 | 118 |
Validating rule ID &1, rule type &2/&3 for process &4 | The short text describes the object sufficiently | |
| 120 | 119 |
Rule ID &1, rule type &2/&3 validation was successful | The short text describes the object sufficiently | |
| 121 | 120 |
Rule ID &1, rule type &2/&3 validation failed | The short text describes the object sufficiently | |
| 122 | 121 |
BRFplus application &1 (ID &2) was successfully created | The short text describes the object sufficiently | |
| 123 | 122 |
Checking BRFplus application &1 | The short text describes the object sufficiently | |
| 124 | 123 |
Object type &1 does not exist (DDIC type, runtime type, class type) | The short text describes the object sufficiently | |
| 125 | 124 |
Approval request '&1' is currently being edited by user '&2' | The short text describes the object sufficiently | |
| 126 | 125 |
Validating and executing the rule with external DDIC structures | The short text describes the object sufficiently | |
| 127 | 126 |
Validating and executing with internal DDIC structures (with conversion) | The short text describes the object sufficiently | |
| 128 | 127 |
Rule parameter &1 has DDIC type &2, but is declared as &3 | The short text describes the object sufficiently | |
| 129 | 128 |
Generation of rule = &1 (customer namespace = &2) | The short text describes the object sufficiently | |
| 130 | 129 |
Validation run for rule = &1 (use line item table with empty row = &2) | The short text describes the object sufficiently | |
| 131 | 130 |
Execution run for rule = &1 (use line item table with empty row = &2) | The short text describes the object sufficiently | |
| 132 | 131 |
Retrieved rule result: &1/&2 | The short text describes the object sufficiently | |
| 133 | 132 |
Agent ID '&1' is not for requested purpose '&3'; agent purpose = '&2' | The short text describes the object sufficiently | |
| 134 | 133 |
Agent ID '&1' has unsupported agent purpose = '&2' | The short text describes the object sufficiently | |
| 135 | 134 |
Retrieved rule result: &1/&2/&3 | The short text describes the object sufficiently | |
| 136 | 135 |
Retrieved rule result: &1/&2/&3/&4 | The short text describes the object sufficiently | |
| 137 | 136 |
Error while evaluating routing rule; check MSMP log for more details | The short text describes the object sufficiently | |
| 138 | 137 |
To create FM-based MSMP rule, use template FM GRFN_MSMP_RULE_TEMPLATE | Space: object requires documentation | |
| 139 | 138 |
To create a class-based MSMP rule, use as template predelivered examples | Space: object requires documentation | |
| 140 | 139 |
BEGIN - Debug message(s) entry requested (caller ID &1) | The short text describes the object sufficiently | |
| 141 | 140 |
END - Debug message(s) entry requested (caller ID &1) | The short text describes the object sufficiently | |
| 142 | 141 |
Structure beginning - simple components of structure '&1' | The short text describes the object sufficiently | |
| 143 | 142 |
Component &1, value: &2 | The short text describes the object sufficiently | |
| 144 | 143 |
Component &1 value cannot be retrieved; unsupported type for display | The short text describes the object sufficiently | |
| 145 | 144 |
Structure end - simple components of structure '&1' | The short text describes the object sufficiently | |
| 146 | 145 |
Debug messages entry requested (caller ID &1); empty table passed | The short text describes the object sufficiently | |
| 147 | 146 |
End of path reached (instance &1, path: &2/&3); calling exit | The short text describes the object sufficiently | |
| 148 | 147 |
End of path reached (instance &1,path: &2/&3); returned from exit | The short text describes the object sufficiently | |
| 149 | 148 |
End of request reached (instance &1, ext. ID &2/&3); calling exit | The short text describes the object sufficiently | |
| 150 | 149 |
End of request reached (instance &1, ext. ID &2/&3) - returned from exit | The short text describes the object sufficiently | |
| 151 | 150 |
Determining agents for (running) lines - &1 | The short text describes the object sufficiently | |
| 152 | 151 |
Determining agents for (unknown) lines - &1 | The short text describes the object sufficiently | |
| 153 | 152 |
Calculated approvers found for line item &1 - approver &2 | The short text describes the object sufficiently | |
| 154 | 153 |
Calculated approvers not found for line item &1 | The short text describes the object sufficiently | |
| 155 | 154 |
Line item &1 is calculating approvers for &2 | The short text describes the object sufficiently | |
| 156 | 155 |
Getting stage details by index | The short text describes the object sufficiently | |
| 157 | 156 |
Beginning determining agents | The short text describes the object sufficiently | |
| 158 | 157 |
Notification for &1 already processed by instance &2, path &3, stage &4 | The short text describes the object sufficiently | |
| 159 | 158 |
Calculating notifications for &1 for instance &2, path &3, stage &4 | The short text describes the object sufficiently | |
| 160 | 159 |
Sending notifications for &1 for instance &2, path &3, stage &4 | The short text describes the object sufficiently | |
| 161 | 160 |
Reading stage escalation settings | The short text describes the object sufficiently | |
| 162 | 161 |
Reading stage configuration | The short text describes the object sufficiently | |
| 163 | 162 |
Reading stage configuration completed | The short text describes the object sufficiently | |
| 164 | 163 |
Reading path configuration - number of stages | The short text describes the object sufficiently | |
| 165 | 164 |
Updating path runtime status to running | The short text describes the object sufficiently | |
| 166 | 165 |
Reading path configuration finished successfully | The short text describes the object sufficiently | |
| 167 | 166 |
Evaluating detour conditions | The short text describes the object sufficiently | |
| 168 | 167 |
Error reported while evaluating detour conditions | The short text describes the object sufficiently | |
| 169 | 168 |
Evaluation of detour conditions finished successfully | The short text describes the object sufficiently | |
| 170 | 169 |
Instance ID &1 submission executed successfully | The short text describes the object sufficiently | |
| 171 | 170 |
Error when setting aggregated status (Instance ID: &1, Path &2/&3) | The short text describes the object sufficiently | |
| 172 | 171 |
Duplicate records returned by rule were removed (&1 -> &2 records) | The short text describes the object sufficiently | |
| 173 | 172 |
Error occurred in program &1, include &2, source line &3 | The short text describes the object sufficiently | |
| 174 | 173 |
Number of submitted line items: &1, calling initiator logic | The short text describes the object sufficiently | |
| 175 | 174 |
Initiator returned &1 results; mapping results to path ID | The short text describes the object sufficiently | |
| 176 | 175 |
Line item &1 is preparing to take escape route | The short text describes the object sufficiently | |
| 177 | 176 |
Line item &1 finished taking escape route | The short text describes the object sufficiently | |
| 178 | 177 |
MSMP request instance created for external identification &1 (&2) | The short text describes the object sufficiently | |
| 179 | 178 |
All initiator results successfuly mapped to path IDs | The short text describes the object sufficiently | |
| 180 | 179 |
Checking stage completion conditions (triggered from UI) | The short text describes the object sufficiently | |
| 181 | 180 |
Sending BWF stage completed event | The short text describes the object sufficiently | |
| 182 | 181 |
Stage was not completed; stage completed event was not sent | The short text describes the object sufficiently | |
| 183 | 182 |
Error when preparing line item data for rule execution DDIC &1 | The short text describes the object sufficiently | |
| 184 | 183 |
MSMP rule &1 returned incomplete results | The short text describes the object sufficiently | |
| 185 | 184 |
MSMP agent rule &1 returned &2 approvers | The short text describes the object sufficiently | |
| 186 | 185 |
Path mapping not found for &1, rule ID &2/&3, result value &4 | The short text describes the object sufficiently | |
| 187 | 186 |
Unable to create stage; completed event for rerouting request | The short text describes the object sufficiently | |
| 188 | 187 |
MSMP agent &1 did not return any approvers | The short text describes the object sufficiently | |
| 189 | 188 |
Cached rule results found for &1 &2 &3 | The short text describes the object sufficiently | |
| 190 | 189 |
Cached data not found for &1 | The short text describes the object sufficiently | |
| 191 | 190 |
Exception when routing line items to new instance of path &1/&2 | The short text describes the object sufficiently | |
| 192 | 191 |
File log for MSMP instance &1 not found | The short text describes the object sufficiently | |
| 193 | 192 |
Error when reading log file &1 | The short text describes the object sufficiently | |
| 194 | 193 |
End of path exit failed (instance:&1, path: &2/&3) | The short text describes the object sufficiently | |
| 195 | 194 |
End of path (instance:&1, path: &2/&3): &4 line items in error status | The short text describes the object sufficiently | |
| 196 | 195 |
No MSMP debug log found for instance &1; check if debug is enabled | The short text describes the object sufficiently | |
| 197 | 196 |
Error reading MSMP debug log file &1 | The short text describes the object sufficiently | |
| 198 | 197 |
You are not authorized to use the MSMP instance monitor | The short text describes the object sufficiently | |
| 199 | 198 |
Path ID &2/&3 of MSMP instance &1 is not in running state | The short text describes the object sufficiently | |
| 200 | 199 |
MSMP instance is not in running state | The short text describes the object sufficiently | |
| 201 | 200 |
Already in author action mode; further forwarding is not allowed | The short text describes the object sufficiently | |
| 202 | 201 |
User &1 is already in forward and return path; not allowed to forward | The short text describes the object sufficiently | |
| 203 | 202 |
Configuration of stage (&1/&2/&3/&4) allows detour; action not possible | The short text describes the object sufficiently | |
| 204 | 203 |
MSMP instance is currently on hold by &1 | The short text describes the object sufficiently | |
| 205 | 204 |
Cannot add line item in continue mode; restarting instance is required | The short text describes the object sufficiently | |
| 206 | 205 |
Mapping class &1 reported warnings when converting structures &2->&3 | The short text describes the object sufficiently | |
| 207 | 206 |
--- End of Warning Messages from Mapping Class &1 (&2->&3) | The short text describes the object sufficiently | |
| 208 | 207 |
Adding line item &1 is ambiguous; the UI is processing more than one path | Space: object requires documentation | |
| 209 | 208 |
MSMP UI session is invalid (already closed); re-enter your application | The short text describes the object sufficiently | |
| 210 | 209 |
No users are specified for forward (line item &1) | The short text describes the object sufficiently | |
| 211 | 210 |
Author action forward allowed for one author only for line item &1 | The short text describes the object sufficiently | |
| 212 | 211 |
User &1 cannot forward to self; line item &2 | The short text describes the object sufficiently | |
| 213 | 212 |
Error when sending stage completed event to workflow subsystem | The short text describes the object sufficiently | |
| 214 | 213 |
Instance is entering "No Stage Path" &1 | The short text describes the object sufficiently | |
| 215 | 214 |
Line item &1 is entering "No Stage Path" &2 | The short text describes the object sufficiently | |
| 216 | 215 |
Unable to send notification for event &1 for path &2 and stage &3 | The short text describes the object sufficiently | |
| 217 | 216 |
Adding line item ID &1 to the current stage failed | The short text describes the object sufficiently | |
| 218 | 217 |
Error writing audit trail messages | The short text describes the object sufficiently | |
| 219 | 218 |
Error getting next stage details; stage &1 is the last stage in path &2 | The short text describes the object sufficiently | |
| 220 | 219 |
User '&1' has no debug authorization | The short text describes the object sufficiently | |
| 221 | 220 |
User '&1' has no authorization to activate new version for process '&2' | Space: object requires documentation | |
| 222 | 221 |
User '&1' has no authorization to configure process '&2' | Space: object requires documentation | |
| 223 | 222 |
User '&1' has no authorization to trigger archiving for process '&2' | Space: object requires documentation | |
| 224 | 223 |
User '&1' has no authorization for process '&2' administration | Space: object requires documentation | |
| 225 | 224 |
User '&1' has no authorization for process '&2', activity '&3' | Space: object requires documentation | |
| 226 | 225 |
Agent '&1' returned empty User ID (for Line Item '&2') | The short text describes the object sufficiently | |
| 227 | 226 |
No escape path configured for process ID &1 | The short text describes the object sufficiently | |
| 228 | 227 |
Escape path needs to have at least 1 stage; check configuration | The short text describes the object sufficiently | |
| 229 | 228 |
No agent found for escape path first stage; check configuration | The short text describes the object sufficiently | |
| 230 | 229 |
UI signature (ID:'&2') not MSMP - action for WorkItem &1 not allowed | The short text describes the object sufficiently | |
| 231 | 230 |
Processing Escalation at Path &1 and Stage &2 Type &3 Agent &4 | The short text describes the object sufficiently | |
| 232 | 231 |
Invalid Return to stage &1 | The short text describes the object sufficiently | |
| 233 | 232 |
Flat rule type mismatch ('&1' <> '&2') | The short text describes the object sufficiently | |
| 234 | 233 |
Error moving to next stage after escalation | The short text describes the object sufficiently | |
| 235 | 234 |
This operation is not allowed in admin mode; use regular Forward instead | The short text describes the object sufficiently | |
| 236 | 235 |
Sending of notification for event '&1' failed | The short text describes the object sufficiently | |
| 237 | 236 |
User &1 attemping to approve has no active delegation for &2 | The short text describes the object sufficiently | |
| 238 | 237 |
At least one work itme is required to perform approver actions | The short text describes the object sufficiently | |
| 239 | 238 |
Inserting cache data of Work Item &1 failed | The short text describes the object sufficiently | |
| 240 | 239 |
Deleting cache data of Work Item &1 failed | The short text describes the object sufficiently | |
| 241 | 240 |
Error parsing notification variable &1/&2 (return type &3) | The short text describes the object sufficiently | |
| 242 | 241 |
Cannot evaluate notification variables, process &1, event &2, template &3 | The short text describes the object sufficiently | |
| 243 | 242 |
Notification for user &1 supressed by end user settings (event &2/&3) | The short text describes the object sufficiently | |
| 244 | 243 |
Workflow instance will be cancelled; do you wish to continue? | The short text describes the object sufficiently | |
| 245 | 244 |
MSMP Workflow Instance has been cancelled | The short text describes the object sufficiently | |
| 246 | 245 |
Error while trying to cancel msmp workflow instance &1 | The short text describes the object sufficiently | |
| 247 | 246 |
MSMP agent &1 did not return any approvers for Line Item '&2' | The short text describes the object sufficiently | |
| 248 | 247 |
Notifications sent for Instance ID &1 | The short text describes the object sufficiently | |
| 249 | 248 |
Notification sent for Instance ID &1 to Approver ID &2 | The short text describes the object sufficiently | |
| 250 | 249 |
Error sending notifications for Request ID:&1/Instance ID:&2 | The short text describes the object sufficiently | |
| 251 | 250 |
No running paths; instance cannot be cancelled or aborted | The short text describes the object sufficiently | |
| 252 | 251 |
Process &1 version &2 does not allow rejection over-ride | The short text describes the object sufficiently | |
| 253 | 252 |
Failure when sending notification for event &1 (template &2) | The short text describes the object sufficiently | |
| 254 | 253 |
MSMP configuration view &1 is locked by user &2 | The short text describes the object sufficiently | |
| 255 | 254 |
Line Item '&1' has aggregated approval status '&2' | The short text describes the object sufficiently | |
| 256 | 255 |
Application specific escalation type '&1' not supported | The short text describes the object sufficiently | |
| 257 | 256 |
Rule &1/&2, result value '&3' mapped to Path ID '&4' | The short text describes the object sufficiently | |
| 258 | 257 |
Rule &1/&2, result value '&3' - no mapped Path found | The short text describes the object sufficiently | |
| 259 | 258 |
Retrieved rule result: Template ID '&1', Variable '&2', value '&3' | The short text describes the object sufficiently | |
| 260 | 259 |
As a result of detour -> starting new instance of path &1/&2 | The short text describes the object sufficiently | |
| 261 | 260 |
Line Item '&1' (Path &2/&3): Request for detour to path ID '&4' ignored | The short text describes the object sufficiently | |
| 262 | 261 |
Cannot determine path/stage class for process &1 (version &2) Path ID &3 | The short text describes the object sufficiently | |
| 263 | 262 |
Line items have error status; do you wish to abort the instance? | The short text describes the object sufficiently | |
| 264 | 263 |
Configuration ID &1 check reported errors (BADI for task &2 - class &3) | The short text describes the object sufficiently | |
| 265 | 264 |
Error retrieveing WorkItem info - WF instance &1/&2/&3 | The short text describes the object sufficiently | |
| 266 | 265 |
Error in 'Notification for Submission' at &1 | The short text describes the object sufficiently | |
| 267 | 266 |
Item '&1' resulted to '&2'; cannot resolve path; check routing mapping | The short text describes the object sufficiently | |
| 268 | 267 |
Error in Process Global Settings | The short text describes the object sufficiently | |
| 269 | 268 |
Reject By Email cannot be choosen without Request Rejected | The short text describes the object sufficiently | |
| 270 | 269 |
There is more than one active version in the system for process &1 | The short text describes the object sufficiently | |
| 271 | 270 |
BADI_GRFN_MSMP_APPROVER_VALID: validating &1 line item/user id records | The short text describes the object sufficiently | |
| 272 | 271 |
BADI_GRFN_MSMP_APPROVER_VALID: validation returned back &1 records | The short text describes the object sufficiently | |
| 273 | 272 |
User ID validation failed (BADI_GRFN_MSMP_APPROVER_VALID) | The short text describes the object sufficiently | |
| 274 | 273 |
Approver ID &1 is being used in agent &2 | The short text describes the object sufficiently | |
| 275 | 274 |
No notification variables rule configured; variables will not be replaced | The short text describes the object sufficiently | |
| 276 | 275 |
Work-Item &1 was set to error (associated with Line-Item '&2') | The short text describes the object sufficiently | |
| 277 | 276 |
Line-Item '&1':cannot set status to Error; whole path is set to Error | The short text describes the object sufficiently | |
| 278 | 277 |
Stage Config ID &1 is being used in version &2 Process &3 Path &4 | The short text describes the object sufficiently | |
| 279 | 278 |
Event '&1', template '&2', document object '&3/&4' - notification skipped | The short text describes the object sufficiently | |
| 280 | 279 |
MSMP Approval status sync. (LineItem Key: &1, Line Items: &2, Type: &3) | The short text describes the object sufficiently | |
| 281 | 280 |
MSMP Approval status evaluation for Line Item &1 | The short text describes the object sufficiently | |
| 282 | 281 |
Updating line item &1 MSMP statuses: &2/&3/&4 | The short text describes the object sufficiently | |
| 283 | 282 |
Workflow-Key Entry cannot be created (&1/&2/&3/&4) | The short text describes the object sufficiently | |
| 284 | 283 |
Workflow-Key Entry '&1' not valid (class: '&2') | The short text describes the object sufficiently | |
| 285 | 284 |
Escape to Path ID '&1', Stage ID '&2' not possible | The short text describes the object sufficiently | |
| 286 | 285 |
Cancelling Path &1/&2 and detouring to escape path | The short text describes the object sufficiently | |
| 287 | 286 |
No agent found, cancelling path &1 (in stage no. &2 - &3) | The short text describes the object sufficiently | |
| 288 | 287 |
Post-request activities reported problems; check logs for details | The short text describes the object sufficiently | |
| 289 | 288 |
Request &1/&2 - submission of more than &3 line-items not allowed | The short text describes the object sufficiently | |
| 290 | 289 |
Submission failure of request &1/&2 - Process ID &3 | The short text describes the object sufficiently | |
| 291 | 290 |
Approvers from agent '&1' were adjusted by BADI Implementation - &2 | The short text describes the object sufficiently | |
| 292 | 291 |
Line-item '&1': Only 1st &2 approvers (from &3 returned) will be used | The short text describes the object sufficiently | |
| 293 | 292 |
Error in End of Path, Escape for '&1' not Enabled, Ending Path '&2' | The short text describes the object sufficiently | |
| 294 | 293 |
WARNING: Stage Configuration &2/&3 (Process &1) allows runtime changes | Space: object requires documentation | |
| 295 | 300 |
Enter Rule ID | The short text describes the object sufficiently | |
| 296 | 301 |
Decision table Header field &1: &2 | The short text describes the object sufficiently | |
| 297 | 302 |
Decision table Item field &1: &2 | The short text describes the object sufficiently | |
| 298 | 400 |
>>>>>>>>>>>> 400 - 500 RESERVED FOR ARCHIVING MESSAGES <<<<<<<<<<<<<<<< | The short text describes the object sufficiently | |
| 299 | 401 |
MSMP Request Instance successfully written to archive | The short text describes the object sufficiently | |
| 300 | 402 |
Error when archiving MSMP Instance | The short text describes the object sufficiently | |
| 301 | 403 |
Related BWF instance &1 (Main WorkItem &2) to be archived separately | The short text describes the object sufficiently | |
| 302 | 404 |
Error when compressing MSMP instances (from date &1 to date &2) | The short text describes the object sufficiently | |
| 303 | 405 |
Specify exactly one date range for archiving | The short text describes the object sufficiently | |
| 304 | 406 |
Snapshot archived | The short text describes the object sufficiently | |
| 305 | 407 |
Retention Time Reached | The short text describes the object sufficiently | |
| 306 | 408 |
Error when calling archiving BADI | The short text describes the object sufficiently | |
| 307 | 409 |
&1 Entries has been deleted from database table &2 | The short text describes the object sufficiently | |
| 308 | 410 |
Error while deleting entry from database table using BADI | The short text describes the object sufficiently | |
| 309 | 411 |
Error while retriving the data from archiving | The short text describes the object sufficiently | |
| 310 | 412 |
Error while retriving the data for &1 | The short text describes the object sufficiently | |
| 311 | 415 |
Error while retriving the information for archiving | The short text describes the object sufficiently | |
| 312 | 416 |
Related BWF instance &1 to be archived separately | The short text describes the object sufficiently | |
| 313 | 417 |
Error when deleting archived object from database tables | The short text describes the object sufficiently | |
| 314 | 418 |
Archived object successfully deleted from database tables | The short text describes the object sufficiently | |
| 315 | 419 |
Error while retriving the archive object for reload | The short text describes the object sufficiently | |
| 316 | 420 |
Error while inserting few entries in database table &1 | The short text describes the object sufficiently | |
| 317 | 421 |
Customizing not found for archiving object | The short text describes the object sufficiently | |
| 318 | 422 |
Error while retriving the next object | The short text describes the object sufficiently | |
| 319 | 423 |
Error while reloading the data from archiving to database | The short text describes the object sufficiently | |
| 320 | 424 |
Data has been reloaded into the Database successfully | The short text describes the object sufficiently | |
| 321 | 425 |
&1 of records has been reloaded to database table &2 | The short text describes the object sufficiently | |
| 322 | 426 |
Error while archiving table &1 | The short text describes the object sufficiently | |
| 323 | 427 |
No data to display | The short text describes the object sufficiently | |
| 324 | 428 |
Escape Condition '&1' in Path '&2' routed to Path '&3' by BADI &4 | The short text describes the object sufficiently | |
| 325 | 429 |
Stage Escalation Changed to Type '&1', Agent '&2' by BADI'&3' | The short text describes the object sufficiently | |
| 326 | 430 |
Stage Escalation Changed by BADI '&1', Escalating Only Pending Items | The short text describes the object sufficiently | |
| 327 | 500 |
>>>>>>>>>>>> 500 - 800 RESERVED FOR AUDIT MESSAGES <<<<<<<<<<<<<<<< | The short text describes the object sufficiently | |
| 328 | 501 |
UI action &1 invoked by user &2 (object ID / action detail: &3) | The short text describes the object sufficiently | |
| 329 | 502 |
Approved by &1 on behalf of forwarding approver &2 at path &3 stage &4 | The short text describes the object sufficiently | |
| 330 | 503 |
Request has been partially directed to path &1 and stage &2 | The short text describes the object sufficiently | |
| 331 | 504 |
Request has been partially directed to path &1 and stage &2 | The short text describes the object sufficiently | |
| 332 | 505 |
Detour condition &1 with value &2 is satisfied at path &3 and stage &4 | The short text describes the object sufficiently | |
| 333 | 506 |
Request is closed | The short text describes the object sufficiently | |
| 334 | 507 |
Escalated and moved to the next stage &1 at path &2 and stage &3 | The short text describes the object sufficiently | |
| 335 | 508 |
Escalated to the specified agent &1 at path &2 and stage &3 | The short text describes the object sufficiently | |
| 336 | 509 |
Escape route applied in Path &1 and Stage &2 | The short text describes the object sufficiently | |
| 337 | 510 |
Approver not found; Applied Escape route; Path &1 Stage &2 | The short text describes the object sufficiently | |
| 338 | 511 |
Re-routed in path &1 and stage &2 to path &3 and stage &4 | The short text describes the object sufficiently | |
| 339 | 512 |
Re-routed in the same path &1 and stage &2 to previous stage &3 | The short text describes the object sufficiently | |
| 340 | 513 |
Request is released by administrator user &1; previously on hold by &2 | The short text describes the object sufficiently | |
| 341 | 518 |
Request &1 submitted by &2 | The short text describes the object sufficiently | |
| 342 | 521 |
End of path handler resulted in errors | The short text describes the object sufficiently | |
| 343 | 522 |
End of request handler resulted in errors | The short text describes the object sufficiently | |
| 344 | 523 |
Request rejected and closed by &1 | The short text describes the object sufficiently | |
| 345 | 524 |
Error raising start event for re-routed path &1 in admin mode | The short text describes the object sufficiently | |
| 346 | 525 |
Error cancelling path &1 after re-reoute in admin mode | The short text describes the object sufficiently | |
| 347 | 526 |
Configuration error; requested re-routed path &1 and stage &2 not found | The short text describes the object sufficiently | |
| 348 | 527 |
Request is cancelled by administrator user &1 | The short text describes the object sufficiently | |
| 349 | 528 |
Request is aborted by administrator user &1 | The short text describes the object sufficiently | |
| 350 | 529 |
Requested cancellation process has failed | The short text describes the object sufficiently | |
| 351 | 530 |
Approval path processing is finished, end of path reached | The short text describes the object sufficiently | |
| 352 | 531 |
New line items added to request at path: &1 stage: &2 | The short text describes the object sufficiently | |
| 353 | 532 |
Re-evaluating current paths in %1 mode | The short text describes the object sufficiently | |
| 354 | 533 |
Starting new path &1 | The short text describes the object sufficiently | |
| 355 | 534 |
Starting new instance of the Path &1; Path Sequence: &2 | The short text describes the object sufficiently | |
| 356 | 535 |
Path &1 is already finished and will not be re-evaluated | The short text describes the object sufficiently | |
| 357 | 536 |
Request is pending for approval at path &1 stage &2 | The short text describes the object sufficiently | |
| 358 | 537 |
Approver ID: &1 | The short text describes the object sufficiently | |
| 359 | 538 |
Auto provisoning failed; Applied Escape route: Path &1 and Stage &2 | The short text describes the object sufficiently | |
| 360 | 539 |
Approver not found at Path &1 Stage &2; escape path is not enabled | The short text describes the object sufficiently | |
| 361 | 540 |
Auto provisoning failed at Path &1 Stage &2; escape path is not enabled | The short text describes the object sufficiently | |
| 362 | 541 |
Comments entered by Administrator user &1 | The short text describes the object sufficiently | |
| 363 | 542 |
Escape path cannot be same as the current path; path ID &1 | The short text describes the object sufficiently | |
| 364 | 543 |
Agent '&1' at path &2 stage &3 - evaluation result has been altered | The short text describes the object sufficiently | |
| 365 | 544 |
Debug Mode Switched Off for Process ID '&1' (by User ID &2) | The short text describes the object sufficiently | |
| 366 | 545 |
Full Debug Mode Switched On for Process ID '&1' (by User ID &2) | The short text describes the object sufficiently | |
| 367 | 546 |
Current Debug Mode Settings for Process ID '&1': &2 | The short text describes the object sufficiently | |
| 368 | 547 |
Rule &1/&2/&3: No result retrieved for Line-Item '&4' | The short text describes the object sufficiently | |
| 369 | 548 |
Rule &1/&2/&3: Returned result for not requested Line-Item '&4' | The short text describes the object sufficiently | |
| 370 | 549 |
Process &1, version &2: Cannot retrieve configuration, generate new one | The short text describes the object sufficiently | |
| 371 | 600 |
For RouteMapping &1, Parent Rule ID &2 does not exist | The short text describes the object sufficiently | |
| 372 | 601 |
For Path &1 and Stage &2, Parent Stage &3 does not exist | The short text describes the object sufficiently | |
| 373 | 602 |
For Path &1 and Stage &2, Parent Path ID &3 does not exist | The short text describes the object sufficiently | |
| 374 | 603 |
For Path &1, Parent Process ID &2 does not exist | The short text describes the object sufficiently | |
| 375 | 604 |
For Initiator &1, Parent Process ID &2 does not exists | The short text describes the object sufficiently | |
| 376 | 784 |
Agent &1 is being used in global notification settings for event &2 | The short text describes the object sufficiently | |
| 377 | 785 |
Agent &1 is used as notification recipient in Path &2 Stage &3 | The short text describes the object sufficiently | |
| 378 | 786 |
Notification Event '&1' - specify both Template and Recipient | The short text describes the object sufficiently | |
| 379 | 787 |
Notification Event '&1' is unknown; enter correct value | The short text describes the object sufficiently | |
| 380 | 788 |
Begin: Embedded check of Process Level Notifications ... | The short text describes the object sufficiently | |
| 381 | 789 |
End: Embedded check of Process Level Notifications ... | The short text describes the object sufficiently | |
| 382 | 790 |
Approval Process &1 supports rejection override | The short text describes the object sufficiently | |
| 383 | 791 |
Checking Stage Configuration ID '&1' ... | The short text describes the object sufficiently | |
| 384 | 792 |
Checking Registry of Notification Templates (Process &1) ... | The short text describes the object sufficiently | |
| 385 | 793 |
Begin: Embeded check, Stage Configuration ID &4 (used in &1/&2/&3) | The short text describes the object sufficiently | |
| 386 | 794 |
End: Embeded check, Stage Configuration ID &4 (used in &1/&2/&3) | The short text describes the object sufficiently | |
| 387 | 795 |
Escape Stage &4 (Path '&3') not found (Process &1, Escape Condition '&2') | The short text describes the object sufficiently | |
| 388 | 796 |
Escape Path '&3' not found (Process &1, Escape Condition '&2') | The short text describes the object sufficiently | |
| 389 | 797 |
Escape Condition '&2' not supported for Process &1 | The short text describes the object sufficiently | |
| 390 | 798 |
Checking Process Escape Conditions (Process &1) ... | The short text describes the object sufficiently | |
| 391 | 799 |
Checking Process Initiator Settings (Process &1) ... | The short text describes the object sufficiently | |
| 392 | 800 |
>>>>>>> 800 - 900 RESERVED FOR CHECK CONFIGURATION MESSAGES <<<<<<<<<< | The short text describes the object sufficiently | |
| 393 | 801 |
&1 - checking configuration; Database table &2 | The short text describes the object sufficiently | |
| 394 | 802 |
In table &1, field &2 value '&3' is not correct | The short text describes the object sufficiently | |
| 395 | 803 |
In table &1, values are not maintained for field &2 | The short text describes the object sufficiently | |
| 396 | 804 |
Table, field, or both are missing | The short text describes the object sufficiently | |
| 397 | 805 |
In table &1, field &2 value &3 exists in check table &4 | The short text describes the object sufficiently | |
| 398 | 806 |
No check table is defined for table &1 field &2 | The short text describes the object sufficiently | |
| 399 | 807 |
MSMP content check is checking IMG and system tables | The short text describes the object sufficiently | |
| 400 | 808 |
MSMP content check is checking version tables | The short text describes the object sufficiently | |
| 401 | 809 |
Latest version &2 of process &1 is not marked as active | The short text describes the object sufficiently | |
| 402 | 810 |
Database Table &1 - record not found (key: &2&3&4) | The short text describes the object sufficiently | |
| 403 | 811 |
Configuration error in process &1/&2: &3&4 | The short text describes the object sufficiently | |
| 404 | 812 |
MSMP process &1 version &2 contains errors | The short text describes the object sufficiently | |
| 405 | 813 |
Table &1, field &2: value &3 not found in check table &4 | The short text describes the object sufficiently | |
| 406 | 814 |
No result value maintained for process &1 | The short text describes the object sufficiently | |
| 407 | 815 |
Mandatory field &2 in table &3 is blank for process &1 | The short text describes the object sufficiently | |
| 408 | 816 |
Error while reading the list of config. tables for process &1 version &2 | The short text describes the object sufficiently | |
| 409 | 817 |
Failed to update escalation approver for instance &1 line item &2 | The short text describes the object sufficiently | |
| 410 | 818 |
MSMP process table entry &1 was not found in type-pool constants | The short text describes the object sufficiently | |
| 411 | 819 |
MSMP process type-pool constant for &1 not found in process table | The short text describes the object sufficiently | |
| 412 | 820 |
MSMP content check - checking system tables entries | The short text describes the object sufficiently | |
| 413 | 821 |
Version could not be generated | Space: object requires documentation | |
| 414 | 822 |
Mandatory field &2 in table &3 is blank for process type &1 | The short text describes the object sufficiently | |
| 415 | 823 |
DDIC structure specified &2 is not valid for process type &1 | The short text describes the object sufficiently | |
| 416 | 824 |
Mandatory field &2 in table &3 is blank for stage type &1 | The short text describes the object sufficiently | |
| 417 | 825 |
Unsupported MSMP rule type &1; check configuration | The short text describes the object sufficiently | |
| 418 | 826 |
Rule with ID &2 does not exist for rule type 1 | The short text describes the object sufficiently | |
| 419 | 827 |
Failed to escalate stage to the next stage | The short text describes the object sufficiently | |
| 420 | 828 |
Failed to raise stage completed event after escalation | The short text describes the object sufficiently | |
| 421 | 829 |
Agent &2 for process type &1 not found; check configuration | The short text describes the object sufficiently | |
| 422 | 830 |
Mandatory field &2 in view &3 is blank for process type &1 | The short text describes the object sufficiently | |
| 423 | 831 |
Process ID &1 forced configuration activation without checking | The short text describes the object sufficiently | |
| 424 | 832 |
Activating configuration of process ID &1 | The short text describes the object sufficiently | |
| 425 | 833 |
Simulation mode; no database changes | The short text describes the object sufficiently | |
| 426 | 834 |
Checking MSMP content, flags: system=&1, IMG=&2,version=&3,extended=&4 | The short text describes the object sufficiently | |
| 427 | 835 |
Mandatory field &2 in table &3 is blank for stage definition &1 | The short text describes the object sufficiently | |
| 428 | 836 |
Checking Registry of Rule Results (for Process &1) ... | The short text describes the object sufficiently | |
| 429 | 837 |
End of path variables &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 430 | 838 |
Rule ID must be of rule type R for process type &1 and stage &2 | The short text describes the object sufficiently | |
| 431 | 839 |
Mandatory field &3 is blank for path &1, stage seq. no. &2 | The short text describes the object sufficiently | |
| 432 | 840 |
Maintain 'Process Global Settings' for process ID &1 | The short text describes the object sufficiently | |
| 433 | 841 |
Mandatory field &2 in view &3 is blank for process ID &1 | The short text describes the object sufficiently | |
| 434 | 842 |
Rule must be of rule type 'initiator rule' for process ID &1 | The short text describes the object sufficiently | |
| 435 | 843 |
Maintain route mapping for rule &2 for process ID &1 | The short text describes the object sufficiently | |
| 436 | 844 |
Result value &2 does not exist in rule results registry for rule &1 | The short text describes the object sufficiently | |
| 437 | 845 |
Versions specified do not exist; enter existing versions | The short text describes the object sufficiently | |
| 438 | 846 |
Mandatory field &2 is blank for agent ID &3 for process type &1 | The short text describes the object sufficiently | |
| 439 | 847 |
For process &1, path &2, stage seq. &3, stage config. is invalid | The short text describes the object sufficiently | |
| 440 | 848 |
Table &1 is locked by user &2 | The short text describes the object sufficiently | |
| 441 | 849 |
Agent '&1' has incorrect value in field Agent Type ('&2') | The short text describes the object sufficiently | |
| 442 | 850 |
Path &1 is being used in version &2 | The short text describes the object sufficiently | |
| 443 | 851 |
Rule &1 is being used in version &2 | The short text describes the object sufficiently | |
| 444 | 852 |
Rule &1 is being used in stage definition &2 | The short text describes the object sufficiently | |
| 445 | 853 |
Rule result &1 is being used in version &2 | The short text describes the object sufficiently | |
| 446 | 854 |
Agent &1 is being used in version &2 | The short text describes the object sufficiently | |
| 447 | 855 |
Agent &1 is being used in stage definition &2 | The short text describes the object sufficiently | |
| 448 | 856 |
Template ID &1 does not exist | The short text describes the object sufficiently | |
| 449 | 857 |
External DDIC structure for process type &1 not defined (field &2) | The short text describes the object sufficiently | |
| 450 | 858 |
External DDIC structure &1 for process type &2 invalid (field &3) | The short text describes the object sufficiently | |
| 451 | 859 |
External structure mapping class undefined, process type &1 (field &2) | The short text describes the object sufficiently | |
| 452 | 860 |
Process type &1, structure conversion failed (from &1 to &2 by &4) | The short text describes the object sufficiently | |
| 453 | 861 |
Process type &1, internal and extrenal DDIC structures (&2) should differ | The short text describes the object sufficiently | |
| 454 | 862 |
Content configuration check completed | The short text describes the object sufficiently | |
| 455 | 863 |
Process ID '&1' based on non-existing process type '&2' | The short text describes the object sufficiently | |
| 456 | 864 |
MSMP process type table entry &1 was not found in type-pool constants | The short text describes the object sufficiently | |
| 457 | 865 |
MSMP type-pool constant for &1 not found in process type table | The short text describes the object sufficiently | |
| 458 | 866 |
For process type &1 and stage &2,choose correct value for Escalation Type | The short text describes the object sufficiently | |
| 459 | 867 |
For process &1,path &2,stage seq&3,choose correct Escalation Type value | The short text describes the object sufficiently | |
| 460 | 868 |
Checking configuration of process &1, version &2 ... | The short text describes the object sufficiently | |
| 461 | 869 |
Checking current configuration of process &1 ... | The short text describes the object sufficiently | |
| 462 | 870 |
For &2, Stage &3 is last stage;cannot have Escalation Type as 'NextStage' | The short text describes the object sufficiently | |
| 463 | 871 |
Maintain route mapping for rule &3 for process ID &1 (version &2) | The short text describes the object sufficiently | |
| 464 | 872 |
Path ID cannot be empty, please enter correct value | The short text describes the object sufficiently | |
| 465 | 873 |
Path ID '&1', Stage Seq. Nr. '&2' is reserved, please use another value | The short text describes the object sufficiently | |
| 466 | 874 |
Approver Group '&1' referenced by Agent '&2' is not defined | The short text describes the object sufficiently | |
| 467 | 875 |
PFCG Role '&1' referenced by Agent '&2' is not defined | The short text describes the object sufficiently | |
| 468 | 876 |
PFCG User Group ID '&1' referenced by Agent '&2' is not defined | The short text describes the object sufficiently | |
| 469 | 877 |
More Notification Templates with ID '&1' exist (Process Type &2) | The short text describes the object sufficiently | |
| 470 | 878 |
Message Class &3/&4 Not Maintained (Template ID &1/&2) | The short text describes the object sufficiently | |
| 471 | 879 |
Document Object &2/&3 for Template ID '&1' not Found (Language '&4') | The short text describes the object sufficiently | |
| 472 | 880 |
Invalid Notification Event &1 (Process &2, Path &3, Stage No. &4) | The short text describes the object sufficiently | |
| 473 | 881 |
Checking Definition of Agent '&1' (Process Type &2) ... | The short text describes the object sufficiently | |
| 474 | 882 |
Process ID '&1' - unexpected configuration error | The short text describes the object sufficiently | |
| 475 | 883 |
Checking Definition of Notification Template '&1' (Process Type &2) ... | The short text describes the object sufficiently | |
| 476 | 884 |
Empty rule result ID is reserved; use another value (Rule &1/&2/&3) | The short text describes the object sufficiently | |
| 477 | 885 |
No result values defined for used routing rule '&2/&3' (of process &1) | The short text describes the object sufficiently | |
| 478 | 886 |
No result values defined for used initiator rule '&2/&3' (of process &1) | The short text describes the object sufficiently | |
| 479 | 887 |
Routing Result '&1' (Rule '&2') used in Path/Stage '&3/&4' not mapped | The short text describes the object sufficiently | |
| 480 | 888 |
Initiatior Result '&1' (Rule '&2') not mapped | The short text describes the object sufficiently | |
| 481 | 889 |
Checking Process Global Settings (&1) ... | The short text describes the object sufficiently | |
| 482 | 890 |
Checking Process Paths (&1) ... | The short text describes the object sufficiently | |
| 483 | 891 |
Checking Stage &2 of Path &1 (Stage Configuration ID '&3') ... | The short text describes the object sufficiently | |
| 484 | 892 |
Checking Stage Configurations (Process Type '&1') ... | The short text describes the object sufficiently | |
| 485 | 893 |
Checking Routing Mapping (Process '&1') ... | The short text describes the object sufficiently | |
| 486 | 894 |
Checking Process Type &2 (of Process &1) ... | The short text describes the object sufficiently | |
| 487 | 895 |
Checking Rules Registry (of Process &1) ... | The short text describes the object sufficiently | |
| 488 | 896 |
Checking Agents Registry (of Process &1) ... | The short text describes the object sufficiently | |
| 489 | 897 |
Checking Stage Tasks Metadata (of Process &1) ... | The short text describes the object sufficiently | |
| 490 | 898 |
Checking Process Definition (&1) ... | The short text describes the object sufficiently | |
| 491 | 899 |
Not implemented | The short text describes the object sufficiently |
History
| Last changed on/by | |
20141106 | SAP |
| SAP Release Created in | 600 |
