SAP ABAP Message Class PPEACT (Messages for iPPE ACT Application (Activities))

Basic Data

Hierarchy

☛ EA-IPPE (Software Component) SAP iPPE
   ⤷ AP-PPE (Application Component) Integrated Product and Process Engineering
     ⤷ CPPEACT0C (Package) Customizing for iPPE Process Structure

Attributes

Message class	PPEACT
Short Description	Messages for iPPE ACT Application (Activities)
Changed On	20040316
Last Changed At	094210

Messages

#	Message	Message Short Text	Documentation status	Authorization check
1	000	Object &1 could not be created because of an error	Space: object requires documentation	☐
2	001	Object &1 could not be read because of an access error	Space: object requires documentation	☐
3	002	Resource &1 could not be read because of an access error	Space: object requires documentation	☐
4	003	No corresponding relationship type found for object &1 &2 &3 &4	Space: object requires documentation	☐
5	004	Could not find a valid relationship type	Space: object requires documentation	☐
6	005	Assignment relationship could not be created because of an error	Space: object requires documentation	☐
7	006	Relationship could not be created because of an error	Space: object requires documentation	☐
8	007	Relationship could not be deleted because of an error	Space: object requires documentation	☐
9	008	Assignment relationship could not be deleted because of an error	Space: object requires documentation	☐
10	010	Object dependency is not allowed for routing type &1	The short text describes the object sufficiently	☐
11	011	Enter a routing type	The short text describes the object sufficiently	☐
12	012	Object dependencies cannot be maintained for &1 &2	Space: object requires documentation	☐
13	013	Usage for object dependencies must be activated for routing type &1	Space: object requires documentation	☐
14	014	Original status could not be reestablished	The short text describes the object sufficiently	☐
15	051	Start: Generally set the indicator MATFLOW in database table PRSEQ	Space: object requires documentation	☐
16	052	Errors occurred when accessing database table PRSEQ	Space: object requires documentation	☐
17	053	End: Generally set the indicator MATFLOW in database table PRSEQ	Space: object requires documentation	☐
18	054	&1 entries from table PRSEQ were updated	Space: object requires documentation	☐
19	100	********************Object Check***************************	Space: object requires documentation	☐
20	101	Supply area assgmnts not allowed at the &1 &2 of type 'setup/tear down'	Space: object requires documentation	☐
21	102	Component assignments at &1 &2 of type 'setup/tear down' are not allowed	Space: object requires documentation	☐
22	103	Variable time data is not allowed at &1 &2 of type 'setup/tear down'	Space: object requires documentation	☐
23	104	Multi-resources are not allowed at &1 &2 of type 'setup/tear down'	Space: object requires documentation	☐
24	105	Variable capacity reqmts are not allowed at &1 &2, type 'setup/tear down'	Space: object requires documentation	☐
25	106	No plant/location is maintained for &1 &2	Space: object requires documentation	☐
26	107	No primary resource is maintained for &1 &2	Space: object requires documentation	☐
27	108	Scheduling data is incomplete for &1 &2	Space: object requires documentation	☐
28	109	No capacity requirements maintained at &1 &2 for resource &3	Space: object requires documentation	☐
29	110	Type 'setup/tear down' is no longer supported for &1 &2	Space: object requires documentation	☐
30	111	The object dependency at &1 &2 is not active	Space: object requires documentation	☐
31	112	No scrap can be maintained at &1 &2 for type 'Teardown/Setup'	Space: object requires documentation	☐
32	113	&1 &2 cannot have a master reporting point because of the scrap	Space: object requires documentation	☐
33	114	&1 &2 must have a reporting point type because of activity scrap	Space: object requires documentation	☐
34	115	There can only be one activity with a scrap value under &1 &2	Space: object requires documentation	☐
35	116	Scrap is only possible at the last production activity under &1 &2	Space: object requires documentation	☐
36	117	Scrap for &1 &2 is only possible for capacity planning of a resource	Space: object requires documentation	☐
37	118	Master reporting point for &1 &2 with scrap value in &3 &4 not allowed	Space: object requires documentation	☐
38	119	The activity scrap at &1 &2 must be less than 100%	The short text describes the object sufficiently	☐
39	120	Reporting point allowed only at the last production activity under &1 &2	The short text describes the object sufficiently	☐
40	121	Only the first setup activity under &1 &2 can have a setup group	The short text describes the object sufficiently	☐
41	122	There can be only one activity with a reporting point under &1 &2	Space: object requires documentation	☐
42	123	Setup act. with setup group below &1 &2 can only be located at beginning	The short text describes the object sufficiently	☐
43	124	Change numbers &1 and &2 at &3 &4 have the same "Valid from" date	Space: object requires documentation	☐
44	125	&1 &2 requires a reporting point that posts goods movements	Space: object requires documentation	☐
45	126	No primary resource has been specified at &1 &2	Space: object requires documentation	☐
46	127	Specify a reporting point for each change status of &1 &2	Space: object requires documentation	☐
47	200	*************** Messages for Context Menu ************************	Space: object requires documentation	☐
48	201	There are no relationships at object &1	Space: object requires documentation	☐
49	202	Object type of &1 cannot be changed because of relationships	Space: object requires documentation	☐
50	203	No suitable object types found for object &1	Space: object requires documentation	☐
51	204	Select a valid object type	Space: object requires documentation	☐
52	400	************************ACT general*************************************	Space: object requires documentation	☐
53	401	Routing header &1 is still used in a production version	Space: object requires documentation	☐
54	402	Could not delete the old change status &2 of mode &1	Space: object requires documentation	☐
55	403	Object with predecessor-successor relatshp cannot be an assignment obj.	Space: object requires documentation	☐
56	405	Reporting point type &1 at &2 &3 is not recognized	Space: object requires documentation	☐
57	406	Plant/location &3 in setup group/synch. charact. at &1 &2 does not exist	Space: object requires documentation	☐
58	407	No synchronization characteristic allowed at &1 &2 of type 'setup'	Space: object requires documentation	☐
59	408	You cannot define a reporting point type at &1 &2 of type 'setup'	Space: object requires documentation	☐
60	409	Type &1 of &2 &3 is not supported	Space: object requires documentation	☐
61	410	Setup group/sync. charact.and plant must be maintained together at &1 &2	Space: object requires documentation	☐
62	411	Supply area and plnt/location must always be maintained together at &1 &2	Space: object requires documentation	☐
63	412	Plant/location &3 of a supply area assignment at &1 &2 does not exist	Space: object requires documentation	☐
64	413	Supply area &3 does not exist in plnt/locat. &4 in SA assignment at &1 &2	Space: object requires documentation	☐
65	414	Mode of a SA assignment at &1 &2 with plant &4 and SA &3 does not exist	Space: object requires documentation	☐
66	415	&1 &2 of a SA assignment at &3 &4 is not assigned to the latter	Space: object requires documentation	☐
67	416	SA assignment is ambiguous at &1 &2 for mode &3 and component &4	Space: object requires documentation	☐
68	417	Component in a SA assignment at &1 &2 with plant &3 does not exist	Space: object requires documentation	☐
69	418	&1 &2 is used in a supply area assignment at &3 &4	Space: object requires documentation	☐
70	419	No action/reporting point can be defined at &1 &2 of type 'setup'	Space: object requires documentation	☐
71	420	Setup group/synch. char. &4 is not defined in plant/location &3 at &1 &2	Space: object requires documentation	☐
72	421	Fixed times are maintained at &1 &2; the type cannot be changed	Space: object requires documentation	☐
73	422	&1 &2 does not have type 'Setup' and cannot be assigned a setup group	Space: object requires documentation	☐
74	423	&1 &2 cannot have a setup group and setup key	Space: object requires documentation	☐
75	450	**********************COMPONENTS***************************************	Space: object requires documentation	☐
76	451	Component &1 &2 &3 &4 is unknown	Space: object requires documentation	☐
77	452	Variant &1 of object &2 &3 &4 has already been assigned	Space: object requires documentation	☐
78	453	Variant &1 is already indirectly assigned through the object &2 &3 &4	Space: object requires documentation	☐
79	454	Component &1 &2 &3 &4 must be completely described	Space: object requires documentation	☐
80	455	Object &1 &2 &3 &4 must be completely described	Space: object requires documentation	☐
81	456	Component &1 &2 is not assigned to activity &3	Space: object requires documentation	☐
82	457	Component &2 cannot be assigned to setup activity &1	Space: object requires documentation	☐
83	458	Only 'start' or 'no' consumption allowed in the &1 from &2 to &3	Space: object requires documentation	☐
84	459	The object &1 &2 &3 &4 is already assigned	The short text describes the object sufficiently	☐
85	500	********** ACT Application Object **************************************	Space: object requires documentation	☐
86	501	Application object type &1 of &2 &3 is not supported by module	Space: object requires documentation	☐
87	502	PVS object type &1 of &2 &3 is not supported by module	Space: object requires documentation	☐
88	503	Resource &1 &2 &3 has not been created	Space: object requires documentation	☐
89	504	Relationship type &1 is not supported by the module	Space: object requires documentation	☐
90	506	Plant &1 does not exist	Space: object requires documentation	☐
91	508	Resource &1 at &2 &3 is not set for capacity planning	Space: object requires documentation	☐
92	509	APO master data could not be found for resource &1	Space: object requires documentation	☐
93	512	Unit and duration at &1 &2 must be maintained together	Space: object requires documentation	☐
94	513	Unit and requirements at &1 &2 requirements &3 must be maintained togeth.	Space: object requires documentation	☐
95	516	Plant &1 of secondary resource &2 must be the same as plant &3 in mode &4	Space: object requires documentation	☐
96	524	General error when creating the mode	Space: object requires documentation	☐
97	525	General error when deleting the mode	Space: object requires documentation	☐
98	526	Min. interoperation time is greater than the max.for &1 between &2 and &3	Space: object requires documentation	☐
99	527	Mode &1 does not exist at node &2	Space: object requires documentation	☐
100	530	General error when deleting additional capacity requirements	Space: object requires documentation	☐
101	531	&1 is not a time unit in the &2 between &3 and &4	Space: object requires documentation	☐
102	532	Enter a unit for the &1 between &2 and &3	Space: object requires documentation	☐
103	533	Changes are only possible with change number	Space: object requires documentation	☐
104	534	Specified unit of measure &1 is not defined for requirements &4 of &2 &3	Space: object requires documentation	☐
105	535	&1 is not a time unit at &2 &3	Space: object requires documentation	☐
106	538	Plant &2 of resource &3 must be the same as plant &1 in mode &4	Space: object requires documentation	☐
107	539	Mode &1 not found	Space: object requires documentation	☐
108	540	Plant in reqmt &1 does not match primary resource &2 in &3 &4	Space: object requires documentation	☐
109	542	Capacity requirement &1 is relevant to scheduling at &3 &2	Space: object requires documentation	☐
110	543	Specified capacity requirement &1 is assigned more than once at &2 &3	Space: object requires documentation	☐
111	544	Capacity requirement at mode &1 - &2 will be deleted when you save	Space: object requires documentation	☐
112	545	Resource &1 is already defined as a secondary resource/reqmnt at &2 &3	Space: object requires documentation	☐
113	546	Enter a mode number	Space: object requires documentation	☐
114	547	No standard value determination type is defined for time analysis	Space: object requires documentation	☐
115	548	Plant &1 for requirements &2 does not match plant &3 in mode &4	Space: object requires documentation	☐
116	549	Mode &1 with change status &2 has already been historically deleted	Space: object requires documentation	☐
117	550	Mode &1/&2 can only be changed with the same change number in filter mode	Space: object requires documentation	☐
118	551	Reporting point at &1 &2 must be constant for all change statuses	Space: object requires documentation	☐
119	576	Mode linkage at &1 requires identical modes at &2 and &3	Space: object requires documentation	☐
120	577	Resource linkage at &1 requires identical resources at &2 and &3	Space: object requires documentation	☐
121	578	Variable times and variable requirements are maintained at &1 &2	Space: object requires documentation	☐
122	579	You have not specified a mode priority at &1 &2	Space: object requires documentation	☐
123	580	Variable and fixed requirements are maintained for resource &3 at &1 &2	Space: object requires documentation	☐
124	581	You can only assign the calendar indicator once at &1 &2	Space: object requires documentation	☐
125	582	Unit &1 of requirement for secondary resource &2 on &3 &4 is not allowed	The short text describes the object sufficiently	☐
126	583	Variable and fixed times are maintained at &1 &2	Space: object requires documentation	☐
127	585	You must maintain the unit and duration of max. break at &1 &2 together	Space: object requires documentation	☐
128	586	Unit &1 for the maximum break at &2 &3 is not a unit of time	Space: object requires documentation	☐
129	587	Primary resource &1 at &4 &2 cannot be used for planning &3	Space: object requires documentation	☐
130	588	Plant at &1 &2 does not match the one in setup group/sync. characteristic	Space: object requires documentation	☐
131	589	Setup activity in &1 &2 prevents you entering reporting points	Space: object requires documentation	☐
132	590	************** Enhancements to Mode ******************************	Space: object requires documentation	☐
133	591	New mode &1 that you wish to create with change status &2 already exists	Space: object requires documentation	☐
134	592	Mode priority &3 specified at &1 &2 is not supported	Space: object requires documentation	☐
135	593	Plant/location &3 specified at &1 &2 does not exist	Space: object requires documentation	☐
136	594	Only resources of type 'single' or 'multi' are allowed at &1 &2	Space: object requires documentation	☐
137	595	Setup activity of &1 &2 allows 'single' resources only	Space: object requires documentation	☐
138	596	You must specify an action point at &2 &1	Space: object requires documentation	☐
139	597	Setup activity of &2 &1 allows fixed times only	Space: object requires documentation	☐
140	598	Single resource at &2 &1 does not allow fixed times	Space: object requires documentation	☐
141	599	You have not made a selection	Space: object requires documentation	☐
142	600	******************** Relationships *************************************	Space: object requires documentation	☐
143	601	Make one selection only	Space: object requires documentation	☐
144	602	************** Relationships ********************************	Space: object requires documentation	☐
145	603	Object type &4 of &2 is different from object type &3 of &1	Space: object requires documentation	☐
146	604	The objects to be linked, &1 and &2, are not of type 'node'	Space: object requires documentation	☐
147	606	Objects &1 and &2 are indirectly linked on a lower level	Space: object requires documentation	☐
148	607	Only one relationship is allowed between activity &2 and &3	Space: object requires documentation	☐
149	608	Objects &1 and &2 are not assigned to the same object	Space: object requires documentation	☐
150	609	Only two relationships are allowed between &2 and &3 at &1	The short text describes the object sufficiently	☐
151	610	No superior object found for object &1	Space: object requires documentation	☐
152	611	Mult. constraints at &1 between &2 and &3 are only allowed for activities	Space: object requires documentation	☐
153	612	&1 between &2 and &3 must have different relationships	The short text describes the object sufficiently	☐
154	613	&1 between &2 and &3 would cause a parallel sequence	Space: object requires documentation	☐
155	614	Relationship between &1 type &3 and &2 type &4 cannot be maintained	Space: object requires documentation	☐
156	615	Activity &1 has already been assigned to object &2	Space: object requires documentation	☐
157	616	You must specify an object type for the object &1 &2 &3	Space: object requires documentation	☐
158	617	You must specify the exact type for the activity &1 &2 &3	Space: object requires documentation	☐
159	618	Relationship is not valid between &1 type &3 and &2 type &4	Space: object requires documentation	☐
160	619	No relationships start from the object &1 &2 &3	Space: object requires documentation	☐
161	620	*************** Assignment List *************************************	Space: object requires documentation	☐
162	621	The process structure &1 &2 &3 does not exist	Space: object requires documentation	☐
163	622	This version is not allowed in iPPE	Space: object requires documentation	☐
164	623	No iPPE routing is assigned to the access	Space: object requires documentation	☐
165	624	Assignment cannot be deleted because it is not assigned to an activity	Space: object requires documentation	☐
166	625	The assigned activity &1 does not belong to the routing of assignmnt list	Space: object requires documentation	☐
167	626	The product structure &1 &2 &3 &4 does not exist	Space: object requires documentation	☐
168	627	Only mode linkage is allowed between primary resources under &1 &2	Space: object requires documentation	☐
169	628	Under &1 &2 only 'end-start' relationships are allowed between &3 and &4	Space: object requires documentation	☐
170	629	There must be subordinate objects for the &1 between &2 and &3	Space: object requires documentation	☐
171	630	There is an indirect &1 on operation-level for activities &2 and &3	Space: object requires documentation	☐
172	631	&1 between activities &2 and &3 is only valid below operations	Space: object requires documentation	☐
173	632	'Continual res. load' in &1 from &2 to &3 only poss. in res-mode linkage	Space: object requires documentation	☐
174	633	'Continual res. load' in &1 from &2 to &3 only poss. in 'end-start' rel.	Space: object requires documentation	☐
175	634	Unit and minimum transition must be maintained in &1 from &2 to &3	Space: object requires documentation	☐
176	635	Unit and maximum transition must be maintained in &1 from &2 to &3	Space: object requires documentation	☐
177	636	Transition times in &1 from &2 to &3 can not be converted	Space: object requires documentation	☐
178	637	'Continual load res.' must be set between &3 and &4 below &1 &2	Space: object requires documentation	☐
179	638	You must specify a relationship type for the &1 between &2 and &3	Space: object requires documentation	☐
180	640	****************Part_of Relationships****************	Space: object requires documentation	☐
181	641	Hierarchy relationship between &1 and &2 cannot be deleted	Space: object requires documentation	☐
182	642	Hierarchy relationship is not allowed between &1 type &3 and &2 type &4	Space: object requires documentation	☐
183	645	No usage authorization for &1 &2 exists	Space: object requires documentation	☐
184	700	***********************Mode Enhancements*******************************	Space: object requires documentation	☐
185	701	Change status &1 at &2 &3 is not recognized	Space: object requires documentation	☐
186	702	Change status &1 at &2 &3 does not have a purely temporal validity	Space: object requires documentation	☐
187	703	Inconsistency in mode linkage between &1 and &2 at mode &3	Space: object requires documentation	☐
188	704	Inconsistency in resource linkage between &1 and &2 at resource &3	Space: object requires documentation	☐
189	710	Durations at &1 &2 are only accurate up to 3 decimal places	Space: object requires documentation	☐
190	711	Capacity requirements at &1 &2 are only accurate up to 3 decimal places	Space: object requires documentation	☐
191	750	************** Time Analysis - Start **********************************	Space: object requires documentation	☐
192	751	Time analysis control could not be linked	Space: object requires documentation	☐
193	752	Internal error creating or changing a time analysis	Space: object requires documentation	☐
194	753	Internal error deleting a time analysis	Space: object requires documentation	☐
195	754	Time analysis &1 is still used and cannot be deleted	Space: object requires documentation	☐
196	755	You do not have authorization to maintain time analysis &1	Space: object requires documentation	☐
197	756	There is no time analysis defined in the user profile	Space: object requires documentation	☐
198	757	Customizing for the time analysis control could not be read	Space: object requires documentation	☐
199	758	Internal error when reading a mode	Space: object requires documentation	☐
200	759	Internal error in dialog with time analysis control	Space: object requires documentation	☐
201	760	Internal error calling the data provider	Space: object requires documentation	☐
202	761	Change can be made only with change number &1	Space: object requires documentation	☐
203	763	Internal error reading a time analysis	Space: object requires documentation	☐
204	765	An internal error occurred when assigning the time analysis	Space: object requires documentation	☐
205	766	Time analysis is already assigned to mode &1	Space: object requires documentation	☐
206	769	No time analysis assigned to mode &1	Space: object requires documentation	☐
207	770	Assignment of time analysis at mode &1 could not be deleted	Space: object requires documentation	☐
208	771	Assignment of time analysis at mode &1 deleted	Space: object requires documentation	☐
209	772	Select a mode	Space: object requires documentation	☐
210	773	Key field must be filled	Space: object requires documentation	☐
211	774	Only one determination type can be transferred to the time analysis	Space: object requires documentation	☐
212	799	************** Time Analysis - End *************************************	Space: object requires documentation	☐
213	800	**************Consistency Check***********************	Space: object requires documentation	☐
214	801	Consistency check on &1 &2 was started at &3	Space: object requires documentation	☐
215	802	Consistency check on &1 &2 was finished at &3	Space: object requires documentation	☐
216	803	General errors reading data when accessing &1 &2	Space: object requires documentation	☐
217	804	Beginning to check the attributes of subordinate objects of &1 &2	Space: object requires documentation	☐
218	805	Finished checking the attributes of subordinate objects of &1 &2	Space: object requires documentation	☐
219	806	Errors occurred during the consistency check on &1 &2	Space: object requires documentation	☐
220	807	No errors occurred during the consistency check on &1 &2	Space: object requires documentation	☐
221	808	Beginning structure check for &1 &2	Space: object requires documentation	☐
222	809	Finished structure check for &1 &2	Space: object requires documentation	☐
223	810	Beginning to check the relationships of &1 &2	Space: object requires documentation	☐
224	811	Finished checking the relationships of &1 &2	Space: object requires documentation	☐
225	812	&1 &2 is not included in the relationships of &3 &4	Space: object requires documentation	☐
226	813	Relationships between activities at &1 &2 are interrupted &3 times	Space: object requires documentation	☐
227	814	Object &1 &2 is used several times in &3 &4	Space: object requires documentation	☐
228	815	The reporting/action point &1 is used several times in &2 &3 and &4	Space: object requires documentation	☐
229	816	At least one mode at &1 &2 must be available for automatic selection	Space: object requires documentation	☐
230	817	There must be an activity of type 'operation' under &1 &2	Space: object requires documentation	☐
231	818	There can only be one activity of type 'setup' under &1 &2	Space: object requires documentation	☐
232	819	There can only be one activity of type 'tear down' under &1 &2	Space: object requires documentation	☐
233	820	Component assignment to &1 &2 requires capacity planning for resource &3	Space: object requires documentation	☐
234	821	&1 &2 is not designed for planning - only one mode is possible	Space: object requires documentation	☐
235	822	Beginning the check on the assignment relationships from &1 &2	Space: object requires documentation	☐
236	823	Check on the assignment relationships from &1 &2 has finished	Space: object requires documentation	☐
237	824	Component &1 is used several times at &2 &3 and &4	Space: object requires documentation	☐
238	825	You have not maintained an activity in &1 &2	Space: object requires documentation	☐
239	826	You have not maintained a mode for &1 &2	Space: object requires documentation	☐
240	827	&1 &2 does not belong to task list type &3	Space: object requires documentation	☐
241	828	Recursive relationships have been maintained under &1 &2	Space: object requires documentation	☐
242	829	Check of supply area assignments was completed successfully	Space: object requires documentation	☐
243	830	Short dump avoids inconsistent data when archiving the objects	The short text describes the object sufficiently	☐
244	850	**************CTM Checks*****************************	Space: object requires documentation	☐
245	851	CTM planning for &1 &2 only allows linear assigned activities	Space: object requires documentation	☐
246	852	CTM planning only allows one end-start relationship at &1 from &2 to &3	Space: object requires documentation	☐
247	853	CTM planning does not supprt any setup groups and keys at &1 &2	Space: object requires documentation	☐
248	854	CTM planning does not allow any offset times at &1 from &2 to &3	Space: object requires documentation	☐
249	855	CTM planning disallows &1 at &2 as only allowed at last activity	Space: object requires documentation	☐
250	856	CTM planning disallows use of Engineering Change Management for &1 &2	Space: object requires documentation	☐
251	857	CTM planning only allows mode linkage by resources at &1 from &2 to &3	Space: object requires documentation	☐
252	870	******* Customizing *******	Space: object requires documentation	☐
253	871	The changes made do not affect existing production data structures in APO	Space: object requires documentation	☐

History

Last changed on/by	20040316	SAP
SAP Release Created in	46C2