SAP ABAP Message Class UPARI (UPARI)
Basic Data
Hierarchy
☛
SAP_BW (Software Component) SAP Business Warehouse
⤷
BW-PLA-BPS (Application Component) Business Planning and Simulation
⤷
UPARI (Package) Retail Assortment Planning Data Interface

⤷

⤷

Attributes
Message class | ![]() |
UPARI |
Short Description | ![]() |
|
Changed On | ![]() |
20141101 |
Last Changed At | ![]() |
091659 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | ![]() |
Enter a date or IMMEDIATELY for the start time | Space: object requires documentation | |
2 | ![]() |
No job defined | The short text describes the object sufficiently | |
3 | ![]() |
No message type selected | Space: object requires documentation | |
4 | ![]() |
Selection criterion &1 is mandatory. Please check red lights | Space: object requires documentation | |
5 | ![]() |
Multilevel reference for field & is not allowed | Space: object requires documentation | |
6 | ![]() |
Server group &1 does not exist | Space: object requires documentation | |
7 | ![]() |
Product & successfully released | Space: object requires documentation | |
8 | ![]() |
Release run started. You can find the results in the application log | Space: object requires documentation | |
9 | ![]() |
Simulation run started. You can find the results in the application log | Space: object requires documentation | |
10 | ![]() |
Application log error: & | Space: object requires documentation | |
11 | ![]() |
Error while processing function module & | Space: object requires documentation | |
12 | ![]() |
Product & is not released | Space: object requires documentation | |
13 | ![]() |
Assortment & is not released | Space: object requires documentation | |
14 | ![]() |
Key of the selection criteria: &1 Please check long text | Space: object requires documentation | |
15 | ![]() |
Number of successfully created objects: &1 | The short text describes the object sufficiently | |
16 | ![]() |
Number of objects with errors / warnings: &1 | The short text describes the object sufficiently | |
17 | ![]() |
Assortment &1, Product &2 successfully released | Space: object requires documentation | |
18 | ![]() |
Assortment &1, Version &2, Product &3 successfully released | Space: object requires documentation | |
19 | ![]() |
Assortment &1 Version &2 does not have any product assignments | Space: object requires documentation | |
20 | ![]() |
Assortment &1, Version &2: Assortment is not released | Space: object requires documentation | |
21 | ![]() |
Assortment &1, Version &2: Product &3 is not released | Space: object requires documentation | |
22 | ![]() |
No selection criteria found | Space: object requires documentation | |
23 | ![]() |
Product & has no description | Space: object requires documentation | |
24 | ![]() |
Location group &1 (&2) successfully released | Space: object requires documentation | |
25 | ![]() |
Location Group & has no description | Space: object requires documentation | |
26 | ![]() |
The assigned message &1 is not selected | Space: object requires documentation | |
27 | ![]() |
Please define a RFC destination for message type & | Space: object requires documentation | |
28 | ![]() |
Error in BW system '&1'; see help text | Space: object requires documentation | |
29 | ![]() |
Execution is prohibited in this system and/or client | The short text describes the object sufficiently | |
30 | ![]() |
Checking of TR OBJECT aborted | The short text describes the object sufficiently | |
31 | ![]() |
Error while creating transport request | The short text describes the object sufficiently | |
32 | ![]() |
Table entries of budget type written successfully to transport request | Space: object requires documentation | |
33 | ![]() |
No data selected | The short text describes the object sufficiently | |
34 | ![]() |
Enter a valid combination for application, budget type and start date | The short text describes the object sufficiently | |
35 | ![]() |
Budget type not active | The short text describes the object sufficiently | |
36 | ![]() |
No Productive system assigned to budget type &1 | The short text describes the object sufficiently | |
37 | ![]() |
Finish date must be later than start date | Space: object requires documentation | |
38 | ![]() |
OTB and Sales Reduction Budget cannot be selected simultaneously | Space: object requires documentation | |
39 | ![]() |
General selection criteria are not relevant for message type &1 | The short text describes the object sufficiently | |
40 | ![]() |
Assortment &1 successfully released | Space: object requires documentation | |
41 | ![]() |
No MAP inbound exists on ERP system &1 | Space: object requires documentation | |
42 | ![]() |
Assortment &1 Version &2 does not have any fixture assignments | Space: object requires documentation | |
43 | ![]() |
No authorization to release Assortment &1 Version &2 | Space: object requires documentation | |
44 | ![]() |
No authorization to release Assortment &1 | Space: object requires documentation | |
45 | ![]() |
Product & has no material group | The short text describes the object sufficiently | |
46 | ![]() |
Product & has no base unit of measure | The short text describes the object sufficiently | |
47 | ![]() |
Product & has no vendor | The short text describes the object sufficiently | |
48 | ![]() |
Product & has no purchasing organisation | The short text describes the object sufficiently | |
49 | ![]() |
Product & has no purchasing price | The short text describes the object sufficiently | |
50 | ![]() |
Product & has a price without a currency | The short text describes the object sufficiently | |
51 | ![]() |
Product & has at least one missing sales price | The short text describes the object sufficiently | |
52 | ![]() |
Assortment &1, Version &2 released without product assignments | The short text describes the object sufficiently | |
53 | ![]() |
Assortment &1, Product &2: Fixture &3 does not contain characteristic &4 | The short text describes the object sufficiently | |
54 | ![]() |
Material purchase price data for Product & successfully released | The short text describes the object sufficiently | |
55 | ![]() |
Material sales price data for Product & successfully released | The short text describes the object sufficiently | |
56 | ![]() |
Product &1, Measure &2 has no unit of measure | The short text describes the object sufficiently | |
57 | ![]() |
Unable to retrieve information about Assortment &1 Version &2 | The short text describes the object sufficiently | |
58 | ![]() |
Unexpected message type encountered | The short text describes the object sufficiently | |
59 | ![]() |
Info object &1 not found | The short text describes the object sufficiently | |
60 | ![]() |
Mapping error for Assortment &1 Version &2 | The short text describes the object sufficiently | |
61 | ![]() |
Unable to identify info object corresponding to criteria &1 | The short text describes the object sufficiently | |
62 | ![]() |
Missing Distribution Chain, please fill it in &1 or &2. | The short text describes the object sufficiently | |
63 | ![]() |
Different Sales Organizations are provided in &1 or &2 | The short text describes the object sufficiently | |
64 | ![]() |
Different Distribution Channels are provided in &1 or &2 | The short text describes the object sufficiently | |
65 | ![]() |
Release run started. Run Analyses Application Log (SLG1) with options: &1 | The short text describes the object sufficiently | |
66 | ![]() |
Product &1, &2 unit of measure &3 has no ISO code | The short text describes the object sufficiently | |
67 | ![]() |
Product &1, &2 currency code has no ISO code | The short text describes the object sufficiently | |
68 | ![]() |
Choose a planning area that is no multi planning are | Space: object requires documentation | |
69 | ![]() |
Enter a planning level with exactly one keyfigure | The short text describes the object sufficiently | |
70 | ![]() |
Enter a planning level that contains info object &1 | The short text describes the object sufficiently | |
71 | ![]() |
Enter a planning level with exactly one characteristic for currency key | The short text describes the object sufficiently | |
72 | ![]() |
Enter a planning level that does not contain characteristic &1 | The short text describes the object sufficiently | |
73 | ![]() |
Enter a planning level with allowed time characteristics | Space: object requires documentation | |
74 | ![]() |
Enter a planning level with only one level of consumer decision tree | Space: object requires documentation | |
75 | ![]() |
Enter a planning level with only one level of merchandise hierarchy | Space: object requires documentation | |
76 | ![]() |
Enter a planning level without a characteristic for a unit key | The short text describes the object sufficiently | |
77 | ![]() |
Enter a valid planning method of the planning level | The short text describes the object sufficiently | |
78 | ![]() |
Enter a planning function of type exit function | The short text describes the object sufficiently | |
79 | ![]() |
Enter a planning function of type exit function that uses module &1 | The short text describes the object sufficiently | |
80 | ![]() |
Enter a planning level with all characteristics selected in package | The short text describes the object sufficiently | |
81 | ![]() |
Status has to get reset to "inactive"! | The short text describes the object sufficiently | |
82 | ![]() |
It is not possible to delete an active Budget Type | The short text describes the object sufficiently | |
83 | ![]() |
Budget Level and Keyfigure Set must use the same infocube! | The short text describes the object sufficiently | |
84 | ![]() |
Keyfigure Set &1 is assigned to active budget type &2. | The short text describes the object sufficiently | |
85 | ![]() |
Deletion of Customizing entries not possible. Restart of transaction | The short text describes the object sufficiently | |
86 | ![]() |
Budget Level &1 is assigned to active budget type &2. | The short text describes the object sufficiently | |
87 | ![]() |
It is not possible to assign more than 3 keyfigures to one set | The short text describes the object sufficiently | |
88 | ![]() |
Infoobjects of Type &1 could not get assigned to a budget level | Space: object requires documentation | |
89 | ![]() |
InfoObject &1 could not assigned to a budget level | Space: object requires documentation | |
90 | ![]() |
InfoCube &1 does not contain InfoObject 0VERSION | The short text describes the object sufficiently | |
91 | ![]() |
Only keyfigures can be assigned to a set (no other infoobjects) | The short text describes the object sufficiently | |
92 | ![]() |
Type or unit of budget keyfigure is wrong | Space: object requires documentation | |
93 | ![]() |
Aggregation attributes of budget keyfigure are wrong | Space: object requires documentation | |
94 | ![]() |
Keyfigure Set &1 uses more than one keyfigure | Space: object requires documentation | |
95 | ![]() |
Budget Type was already transfered | The short text describes the object sufficiently | |
96 | ![]() |
Budget Type in System &1 has Status &2 | The short text describes the object sufficiently | |
97 | ![]() |
No Update of Customizing in System &1 done | The short text describes the object sufficiently | |
98 | ![]() |
No valid budget type could get selected | The short text describes the object sufficiently | |
99 | ![]() |
Unexpected Returncode &2 in function module &1 | Space: object requires documentation | |
100 | ![]() |
Budget Level &2 of Budget Type &3 valid from &4 contains &1 entries | The short text describes the object sufficiently | |
101 | ![]() |
Keyfigure Set &2 of Budget Type &3 valid from &4 contains &1 entries | The short text describes the object sufficiently | |
102 | ![]() |
Add a periodicity (time characteristic) to the budget level | Space: object requires documentation | |
103 | ![]() |
Enter a valid time characteristic or a valid combination of them | Space: object requires documentation | |
104 | ![]() |
It is not possible to assign more than 10 characteristics | The short text describes the object sufficiently | |
105 | ![]() |
Select another budget level: No hierarchy specified in level &1 | The short text describes the object sufficiently | |
106 | ![]() |
ODS object &1 already exist | The short text describes the object sufficiently | |
107 | ![]() |
Infoarea &1 does not exist | The short text describes the object sufficiently | |
108 | ![]() |
InfoObject &1 does not has data type CHAR of length 2 | The short text describes the object sufficiently | |
109 | ![]() |
Reference characteristic of &1 must be a time characteristic | Space: object requires documentation | |
110 | ![]() |
Enter a characteristic | The short text describes the object sufficiently | |
111 | ![]() |
Reference characteristic &1 must be assigned to budget level &2 | The short text describes the object sufficiently | |
112 | ![]() |
For Budget Type &1 of application &2 exist alraedy 2 valid entries | The short text describes the object sufficiently | |
113 | ![]() |
Enter another budget type. First entry of type &1 unlimited valid | The short text describes the object sufficiently | |
114 | ![]() |
Start Date is adjusted to end date of first validity time frame | The short text describes the object sufficiently | |
115 | ![]() |
Maintain a value for fiscal year variant | Space: object requires documentation | |
116 | ![]() |
Enter another budget level | Space: object requires documentation | |
117 | ![]() |
Assign InfoObject 0CM_HIEID to the budget level | Space: object requires documentation | |
118 | ![]() |
Assign an Info Object to order period | The short text describes the object sufficiently | |
119 | ![]() |
End date is adjusted to &1 (= end of planning period &2). | The short text describes the object sufficiently | |
120 | ![]() |
Periods >= &1 contain &2 budgets. | Space: object requires documentation | |
121 | ![]() |
It exists one budget type for Application PPW. Only one type is allowed | The short text describes the object sufficiently | |
122 | ![]() |
Identify exactly one level of article hierarchy for budget level &1 | The short text describes the object sufficiently | |
123 | ![]() |
Identify exactly one level of merchandise category hierarchy | The short text describes the object sufficiently | |
124 | ![]() |
System crash occurs on the receiving side RFC destination &1 | The short text describes the object sufficiently | |
125 | ![]() |
Connection or communication problem to RFC destination &1 | The short text describes the object sufficiently | |
126 | ![]() |
Budget type &1 (valid from &2 until &3) has status inactive | The short text describes the object sufficiently | |
127 | ![]() |
Budget type &1 (valid from &2 until &3) has status active | The short text describes the object sufficiently | |
128 | ![]() |
Last change of budget type: Day &1, Time &2, Program &3, User &4 | The short text describes the object sufficiently | |
129 | ![]() |
Activation of Budget Type &1 not possible | The short text describes the object sufficiently | |
130 | ![]() |
Budget type &1 succesful activated | The short text describes the object sufficiently | |
131 | ![]() |
Unexpected return code &1 during database access &2 on table &3 | The short text describes the object sufficiently | |
132 | ![]() |
Select for periods only including single values or intervals | The short text describes the object sufficiently | |
133 | ![]() |
Select another period interval | Space: object requires documentation | |
134 | ![]() |
Maintain RFC Destination in Customizing | The short text describes the object sufficiently | |
135 | ![]() |
Split criterium must be an infoobject of budget level | The short text describes the object sufficiently | |
136 | ![]() |
Select for split criterium only including single values or intervals | The short text describes the object sufficiently | |
137 | ![]() |
Activate Budget type &1 in destination &2 | The short text describes the object sufficiently | |
138 | ![]() |
Budget type not consistent with budget type in destination &1 | The short text describes the object sufficiently | |
139 | ![]() |
Unexpected logical expression &1 while processing &2 | The short text describes the object sufficiently | |
140 | ![]() |
Start of releasing planned budgets: day &1, time &2 | The short text describes the object sufficiently | |
141 | ![]() |
End of releasing planned budgets: day &1, time &2 | The short text describes the object sufficiently | |
142 | ![]() |
&1 packages for data transfer created | The short text describes the object sufficiently | |
143 | ![]() |
error processing package &1 characteristic &2 = &3 destination &4 | The short text describes the object sufficiently | |
144 | ![]() |
Start of processing package characteristic &1 = &2: day &3, time &4 | The short text describes the object sufficiently | |
145 | ![]() |
End of processing package characteristic &1 = &2: day &3, time &4 | The short text describes the object sufficiently | |
146 | ![]() |
Number of analyzed budgets of package characteristic &1 = &2: &3 | The short text describes the object sufficiently | |
147 | ![]() |
&1 new budgets have to get created | Space: object requires documentation | |
148 | ![]() |
&1 new budgets created succesfully | Space: object requires documentation | |
149 | ![]() |
&1 existing budgets have to get updated | The short text describes the object sufficiently | |
150 | ![]() |
&1 budget values updated succesfully | The short text describes the object sufficiently | |
151 | ![]() |
&1 budgets have to get deactivated | The short text describes the object sufficiently | |
152 | ![]() |
&1 budgets deactivated succesfully | Space: object requires documentation | |
153 | ![]() |
&1 budgets have to get activated | The short text describes the object sufficiently | |
154 | ![]() |
&1 budgets activated successfully | The short text describes the object sufficiently | |
155 | ![]() |
&1 budgets not changed within tolerance of &2 % | The short text describes the object sufficiently | |
156 | ![]() |
Start of messages from destination &1: &2 | The short text describes the object sufficiently | |
157 | ![]() |
End of messages from destination &1: &2 | The short text describes the object sufficiently | |
158 | ![]() |
All budgets already created during initial release | The short text describes the object sufficiently | |
159 | ![]() |
&1 new budgets created in addition to initial release | The short text describes the object sufficiently | |
160 | ![]() |
&1 new budget allocations created succesfully | The short text describes the object sufficiently | |
161 | ![]() |
All budget allocations created during initial release | The short text describes the object sufficiently | |
162 | ![]() |
&1 new budget allocations created in addition to initial release | The short text describes the object sufficiently | |
163 | ![]() |
&1 budget allocation values updated succesfully | The short text describes the object sufficiently | |
164 | ![]() |
&1 &2 &3 &4 | The short text describes the object sufficiently | |
165 | ![]() |
&1 new budgets could not get created | The short text describes the object sufficiently | |
166 | ![]() |
Update of budget &1 (&2) failed | The short text describes the object sufficiently | |
167 | ![]() |
Available budget &1 (&2) negative: &3 &4 | The short text describes the object sufficiently | |
168 | ![]() |
budget &1 deactivated: open documents exist | The short text describes the object sufficiently | |
169 | ![]() |
budget &1 (&2) not deactivated: open documents exist | The short text describes the object sufficiently | |
170 | ![]() |
Budgets exist in destination &1 | The short text describes the object sufficiently | |
171 | ![]() |
Reorganization of budgets not possible | The short text describes the object sufficiently | |
172 | ![]() |
Reorganization of budgets successfully completed | The short text describes the object sufficiently | |
173 | ![]() |
Reorganization of budget type not possible | The short text describes the object sufficiently | |
174 | ![]() |
Reorganization of budget type successfully completed | The short text describes the object sufficiently | |
175 | ![]() |
Reorganize budgets first | The short text describes the object sufficiently | |
176 | ![]() |
&1 budgets deleted | The short text describes the object sufficiently | |
177 | ![]() |
Budget type still valid: End date = &1. Reorganization not possible | The short text describes the object sufficiently | |
178 | ![]() |
&1 data records modified successfully | The short text describes the object sufficiently | |
179 | ![]() |
For activation of a budget type infoobject &1 must be active | The short text describes the object sufficiently | |
180 | ![]() |
Name of keyfigure &1 contains more than 30 characters | The short text describes the object sufficiently | |
181 | ![]() |
&1 packages processed | The short text describes the object sufficiently | |
182 | ![]() |
Saving not possible! Inconsistent data | The short text describes the object sufficiently | |
183 | ![]() |
Unknown message &1 message class &2 destination &3 parameters &4 | The short text describes the object sufficiently | |
184 | ![]() |
&1 data sets of database table &2 updated successfully | The short text describes the object sufficiently | |
185 | ![]() |
Automatic mapping for infoobject &1 executed | The short text describes the object sufficiently | |
186 | ![]() |
Automatic mapping for infoobject &1 not possible | The short text describes the object sufficiently | |
187 | ![]() |
Start Date has to get adjusted to system date | The short text describes the object sufficiently | |
188 | ![]() |
End Date of budget type &1 is adjusted | The short text describes the object sufficiently | |
189 | ![]() |
Only two different finish dates for all types allowed: Choose &1 or &2 | The short text describes the object sufficiently | |
190 | ![]() |
At least one budget type is infinite valid. Limit that finish date first | The short text describes the object sufficiently | |
191 | ![]() |
Periodicity must be unique; Level &1 does not contain infoobject &2 | The short text describes the object sufficiently | |
192 | ![]() |
Data input has to get reset | The short text describes the object sufficiently | |
193 | ![]() |
There exist already two valid time frames | The short text describes the object sufficiently | |
194 | ![]() |
ODS object &1 already assigned to budget type &2 | The short text describes the object sufficiently | |
195 | ![]() |
Available budget negative: budget &1; order period &2 to &3; value &4 | The short text describes the object sufficiently | |
196 | ![]() |
Reorganize budget type in destination &1 first | The short text describes the object sufficiently | |
197 | ![]() |
Budget type does not exist in destination &1 | The short text describes the object sufficiently | |
198 | ![]() |
It exist no budget with number &1 | The short text describes the object sufficiently | |
199 | ![]() |
End date entered is different from end date &1 of planning period &2 | The short text describes the object sufficiently | |
200 | ![]() |
Only planned data for actual or future periods can be released | The short text describes the object sufficiently | |
201 | ![]() |
budget &1 created | The short text describes the object sufficiently | |
202 | ![]() |
budget &1 updated | The short text describes the object sufficiently | |
203 | ![]() |
budget &1 deactivated | The short text describes the object sufficiently | |
204 | ![]() |
budget &1 activated | The short text describes the object sufficiently | |
205 | ![]() |
Only one level of article hierarchy can be used for all budget types | The short text describes the object sufficiently | |
206 | ![]() |
budget &1 locked | The short text describes the object sufficiently | |
207 | ![]() |
&1 budgets marked for initial release | The short text describes the object sufficiently | |
208 | ![]() |
Function for budgets of past periods not executable | The short text describes the object sufficiently | |
209 | ![]() |
Release of budgets terminated | The short text describes the object sufficiently | |
210 | ![]() |
No valid table entries selected | The short text describes the object sufficiently | |
211 | ![]() |
Function only for budgets of past periods executable | The short text describes the object sufficiently | |
212 | ![]() |
Budget &1 exist in SAP ERP; deletion not possible | The short text describes the object sufficiently | |
213 | ![]() |
Planned value not yet released; function not executable | The short text describes the object sufficiently | |
214 | ![]() |
Budgets are currently locked by user &1; only display possible | The short text describes the object sufficiently | |
215 | ![]() |
Enter a valid value for infoobject &1 | The short text describes the object sufficiently | |
216 | ![]() |
Transfer of budget &1 failed | The short text describes the object sufficiently | |
217 | ![]() |
Job for release of budgets created | The short text describes the object sufficiently | |
218 | ![]() |
No values exist in cube &1 for the specified selection for infoobject &2 | The short text describes the object sufficiently | |
219 | ![]() |
Message type &1 not active in customizing | The short text describes the object sufficiently | |
220 | ![]() |
Customizing of message types is not complete | The short text describes the object sufficiently | |
221 | ![]() |
No authorization to release messages of type &1 | The short text describes the object sufficiently | |
222 | ![]() |
No authorization to rerelease messages of type &1 | The short text describes the object sufficiently | |
223 | ![]() |
Field &1 of message type &2 is mandatory but not selected | The short text describes the object sufficiently | |
224 | ![]() |
Field &1 is not part of message type &2 | The short text describes the object sufficiently | |
225 | ![]() |
No authorization for the selected budget type | The short text describes the object sufficiently | |
226 | ![]() |
Enter a planning version | The short text describes the object sufficiently | |
227 | ![]() |
Combination of fields/infoobjects &1, &2 not allowed for message type &3 | The short text describes the object sufficiently | |
228 | ![]() |
Data saved successfully | The short text describes the object sufficiently | |
229 | ![]() |
Budgets now locked by another transaction; restart necessary | The short text describes the object sufficiently | |
230 | ![]() |
Assigned InfoObject must be unique | The short text describes the object sufficiently | |
231 | ![]() |
InfoObject &1 cannot be assigned | The short text describes the object sufficiently | |
232 | ![]() |
Only one record allowed without any assigned InfoObject | The short text describes the object sufficiently | |
233 | ![]() |
&1 is no valid destination | The short text describes the object sufficiently | |
234 | ![]() |
Communication method &1 is not allowed for message type &2 / indicator &3 | The short text describes the object sufficiently | |
235 | ![]() |
Update of release status was unsuccessful for &1 | The short text describes the object sufficiently | |
236 | ![]() |
Mapping to external format (XI) failed for field &1 | The short text describes the object sufficiently | |
237 | ![]() |
Inbound process &1 returned error &2, see Application Log in system &3 | The short text describes the object sufficiently | |
238 | ![]() |
Sales Organization &1 does not match with DC dependent Hierarchy &2. | The short text describes the object sufficiently | |
239 | ![]() |
Distribution Channel &1 does not match with DC dependent Hierarchy &2. | The short text describes the object sufficiently | |
240 | ![]() |
Hierarchy &1 is not valid. | The short text describes the object sufficiently | |
241 | ![]() |
Please provide both Sales Organization and Distribution Channel. | The short text describes the object sufficiently | |
242 | ![]() |
No data record found in infoProvider &1 for your selection. | Space: object requires documentation |
History
Last changed on/by | ![]() |
20141101 | SAP |
SAP Release Created in | 350 |