RSPC - Prozessketten
 The following messages are stored in message class RSPC: Prozessketten.
It is part of development package RSPC in software component BW-WHM-DST. This development package consists of objects that can be grouped under "Process Chains".
 It is part of development package RSPC in software component BW-WHM-DST. This development package consists of objects that can be grouped under "Process Chains".
| Message Nr ▲ | Message Text | 
|---|---|
| 001 | Variant already exists. Enter another value. | 
| 002 | Job or process &1, waiting for event &2 &3 is unknown | 
| 003 | Job &1, waiting for event &2 &3, has no predecessor | 
| 004 | No start information on process &2 | 
| 005 | Process &1, variant &2, ended with invalid status &3 | 
| 006 | Process &1, variant &2 is not scheduled waiting for event &3 &4 | 
| 007 | Process &1, job count &2 should already have started | 
| 008 | Variant &1, instance &2 started in chain run &3 | 
| 009 | Process &1, variant &2 has status &4 (instance &3) | 
| 010 | Only One General Starter Is Allowed Per Chain (&1) | 
| 011 | The starter may not have a predecessor | 
| 012 | Processes are already connected | 
| 013 | Function not yet implemented | 
| 014 | Internal Error | 
| 015 | Please enter an existing variant | 
| 016 | No F4 help is available for process type '&1' | 
| 017 | Process type &1 is not known | 
| 018 | Process type &1 does not send any events -> No successors are possible | 
| 019 | Version '&2' of chain &1 was saved without checking | 
| 020 | Chain has no starter. Add a starter. | 
| 021 | Process &1 has no predecessor | 
| 022 | Processes with &1 | 
| 023 | Variant & is not persistent | 
| 024 | Each Starter Is Only To Be Used In A Individual Chain | 
| 025 | Chain &1 Was Activated And Scheduled | 
| 026 | Chain & was removed from scheduling | 
| 027 | No logs were found | 
| 028 | Chain Is OK | 
| 029 | Transaction Started In New Mode | 
| 030 | Event &1 Triggered With Parameter &2 | 
| 031 | &4 Chains Were Selected | 
| 032 | Chain &1 Was Deleted | 
| 033 | Variant &2 Of Type &1 Does Not Exist | 
| 034 | Chain &1 Does Not Exist | 
| 035 | Process &1 And Variant &2 Were Deleted | 
| 036 | Process &1 And Variant &2 Were Saved | 
| 037 | AND process &1 called more than once with event &2 parameter &3 | 
| 038 | This event is feedback to a predecessor process | 
| 039 | Please enter an existing program | 
| 040 | Event &1 &2 not (yet) received | 
| 041 | Event &1 &2 received on &3 at &4 | 
| 042 | Enter an existing destination | 
| 043 | Enter an existing function module | 
| 044 | Parameter could not be defined | 
| 045 | Function for remote calls only possible in systems with SAPI 3.0 | 
| 046 | Another call of exclusive OR: No event triggered | 
| 047 | First call of exclusive OR: Event is triggered | 
| 048 | Process chain already displayed. Choose another chain. | 
| 049 | Job started | 
| 050 | Undocumented exception &1 in function &2 | 
| 051 | Error in remote call of destination &1: &2&3&4 | 
| 052 | Variant &1 still executing from previous run | 
| 053 | There is no open run for variant &1 | 
| 054 | No documentation available | 
| 055 | Activation failed | 
| 056 | You cannot schedule a chain in itself | 
| 057 | Process did not report an instance -> no log | 
| 058 | Error &1 occurred in function '&2' | 
| 059 | No job found | 
| 060 | Process &1 variant &2 is referenced but is not in the chain | 
| 061 | Process &1 variant &2 is referenced but is not a predecessor | 
| 062 | Internal error with CCMS connection: RC &1. | 
| 063 | Process chains CCMS monitoring | 
| 064 | Process chain & already exists. Enter a different value | 
| 065 | Job &1 could not be scheduled. Termination with returncode &2 | 
| 066 | Conversion of job with type &1 not supported | 
| 067 | Only programs and no external commandos can be converted | 
| 068 | Object name &1 lies within SAP name range, please choose another name | 
| 069 | Process of type &1 is to be generated -> check | 
| 070 | First specify destination | 
| 071 | Complete all fields | 
| 072 | Process chain &1 started in system &2 | 
| 073 | Remote chain &1: Destination &2 does not exist. Please maintain. | 
| 074 | Termination of chain has been reported to meta chain &1 | 
| 075 | Termination of chain has been reported to workflow ID &1 | 
| 076 | System command &1 executed on host &2 (repeat &3) | 
| 077 | Command ends with status &1, return code &2 | 
| 078 | You do not have authorization for scheduling system commands | 
| 079 | You do not have authorization for scheduling programs | 
| 080 | Messages within the subchain &1: | 
| 081 | Object &1 has name &2 in Content and &3 in the active version | 
| 082 | Process &1, variant &2 was saved in the target system under &3 names | 
| 083 | Process &1, variant &2 is unable to be transported | 
| 084 | Add at least one process to the chain before saving | 
| 085 | No destination maintained in target client &1 -> Not activated | 
| 086 | Chain &1 was saved as active | 
| 087 | Communication buffer deleted from previous run &1 (status &2) | 
| 088 | Previous run &1 not yet complete (status &2), termination | 
| 089 | Communication buffer deleted from previous run &1 (status &2) | 
| 090 | Previous run &1 not yet complete (status &2), termination | 
| 091 | No start information on process &2 | 
| 092 | Select a line or choose "Red" | 
| 093 | Entire chain now has status '&' | 
| 094 | Event &1, parameter &2 already received | 
| 095 | This AND process is not waiting for event &1, parameter &2 | 
| 096 | Process was not simulated | 
| 097 | Process variant &1 &2 does not exist in version A | 
| 098 | String '&1' found in output row &2 (value '&3') position &4 | 
| 099 | String '&1' not found in output | 
| 100 | Process terminated with status &1 as requested | 
| 101 | Chain &1 can only be edited in client &2 | 
| 102 | Process chains are executed with the BW background user | 
| 103 | Process chains are executed by scheduled users | 
| 104 | Collector processes are not useful as end point | 
| 105 | Not all conditions have formulas | 
| 106 | Not all formulas exist on the database | 
| 107 | Process type &1 does not send multi-events | 
| 108 | Event &1 is not triggered by predecessors | 
| 109 | Calculate condition &1 | 
| 110 | Error in calculation &1 | 
| 111 | InfoObject 0BOOL could not be activated | 
| 112 | Function cannot be executed in display mode | 
| 113 | Chain changed! Scheduling in display mode not possible | 
| 114 | Process &1 &2 has no successor for option &4 | 
| 115 | Process type not usable | 
| 116 | You have to maintain at least two rows | 
| 117 | Switching to detail view to display erroneous process | 
| 118 | Too many parallel processes for chosen server &1 | 
| 119 | Variant &1 cannot be deleted because it already exists in chains | 
| 120 | Status &1 has already been reported to instance &2, variant &3, in run &4 | 
| 121 | Process chain &1 is not active. Activate first | 
| 122 | Start condition "immediate start" for interrupt process makes no sense | 
| 123 | Internal error in DWB navigation | 
| 124 | No values for this selection | 
| 125 | Process type & is only released for use in BW standard client | 
| 126 | Alert &1 triggered | 
| 127 | You have activated chain &1 | 
| 128 | Run & is still active; cannot delete | 
| 129 | Logs for run &1 of &2, &3 deleted | 
| 130 | You are not authorized to write the trace file | 
| 131 | Cannot open trace file | 
| 132 | Everything OK | 
| 133 | Several processes exist for Log ID &1, type &2, variant &3 | 
| 134 | There is only one server; server set to initial | 
| 135 | Check results for process &1 &2 in chain &3: | 
| 136 | Instance &1 reported to chain synchronously with Hold = '&2', status '&3' | 
| 137 | Process &1 &2, instance &3 does not exist in run &4 | 
| 138 | Process &1 &2. Instance &3 cannot be restarted. | 
| 139 | Process type &1 cannot be restarted and was not checked | 
| 140 | Selected processes were deleted | 
| 141 | Chain run &1 to be terminated as soon as possible due to user request | 
| 142 | Shadow object &1 cannot be expanded; chain is inconsistent | 
| 143 | Interrupt was successfully reset | 
| 144 | No open run found; reset not necessary | 
| 145 | Termination request for run &1 was canceled | 
| 146 | Process &1 &2, instance &3 was reset | 
| 147 | Chain &1 was generated; cannot be changed | 
| 148 | &4: Process chain &2 has status "&3" (log ID &1) | 
| 149 | &4: Process chain &2 has status "&3" (run &1 was canceled manually) | 
| 150 | Wait another &3 minutes to start process &1 withi job count &2 | 
| 151 | No wildcards allowed in field names; use search help | 
| 152 | Chain &1 runs infrequently or rarely. Prognosis not possible | 
| 153 | Chain &1 is not scheduled (anymore) | 
| 154 | Kette &1 is scheduled multiple times. Check scheduling | 
| 155 | Chain &1 has not run in a long time | 
| 156 | Start process &1 &2 in run &3 of chain &4 | 
| 157 | Start program &1 with program variant &2 | 
| 158 | Trigger &1 of subchain &2 terminated | 
| 159 | Chain cannot be assigned to generated objects | 
| 160 | Remove lower-level components first | 
| 161 | Move assigned chains first | 
| 162 | Generated components cannot be deleted or changed | 
| 163 | Content not created: Duplicate delivery object &1 &2 | 
| 164 | Job name: &1 , ID: &2 . | 
| 165 | Subcomponents cannot be created under generated components | 
| 166 | Run canceled manually. Restart not required by user | 
| 167 | Started subsequent process after error. User action/restart not required | 
| 168 | DataSource &1 applied to variant &2 | 
| 169 | Authorization "S_PROGRAM" with activity "Submit" is required | 
| 170 | Chain &1 cannot be deleted because it already exists in other chains | 
| 171 | Process &1 &2, instance &3: Repair triggered | 
| 172 | Process &1 &2, instance &3: Repeat triggered | 
| 173 | Repeat for &1 processes triggered. Repair triggered for &2 processes. | 
| 174 | Only one trigger with immediate start or start via API allowed (&1) | 
| 175 | Please select a valid include to delete | 
| 176 | Server & does not exist as an active server. Choose anyway? | 
| 177 | Host & does not exist as an active host. Choose anyway? | 
| 178 | Server group & does not exist. Choose anyway? | 
| 179 | Process &1 and variant &2 saved in object version 'M' | 
| 180 | Only Display Mode allowed | 
| 181 | There must be one trigger with immediate start or start via API | 
| 182 | Process type &1 does not allow streaming | 
| 183 | Process variant &1 &2 does not allow streaming | 
| 184 | Process &1 &2 is not a successor | 
| 185 | No job found. Variants for &1 jobs are missing in client &2. | 
| 186 | Processes are called to exit streaming mode | 
| 187 | ==== Process &3 &4 started in run &2 of chain &1 >>>> | 
| 188 | <<<< Process &3 &4 ended in run &2 of chain &1 ==== | 
| 189 | At least 3 logs must be kept | 
| 190 | Number of repetitions must be smaller than or equal to number of old logs | 
| 191 | Set both values or clear both values | 
| 192 | Process &1 &2 is also in other streaming chain &3 | 
| 193 | Process &1 &2 is also in other chain &3 | 
| 194 | Process &1 &2 is also in streaming chain &3 | 
| 195 | Initialization (&1) is not finished (&2); cannot reschedule yet | 
| 196 | Unschedule chain before changing streaming property | 
| 197 | Broadcaster: Trigger event data change in BOE | 
| 198 | Event &1 is not available in BOE destination &2 | 
| 199 | Steps to configure SSL encrypted http destination | 
| 204 | Processing ended at &1 &2 | 
| 215 | Streaming not possible in this client | 
| 666 | &1&2&3&4 |