SAP ABAP Message Class UPS1 (SEM-BPS Status and Tracking System Messages)

Basic Data

Hierarchy

☛ SAP_BW (Software Component) SAP Business Warehouse
   ⤷ BW-PLA-BPS (Application Component) Business Planning and Simulation
     ⤷ UPS (Package) Status and Tracking System

Attributes

Message class	UPS1
Short Description	SEM-BPS Status and Tracking System Messages
Changed On	20130531
Last Changed At	094825

Messages

#	Message	Message Short Text	Documentation status	Authorization check
1	001	Hierarchy &1 contains range nodes. This is not allowed	Space: object requires documentation	☐
2	002	First determine a planning area	Space: object requires documentation	☐
3	003	Determine characteristic names	Space: object requires documentation	☐
4	004	Hierarchy &1 contains dummy nodes. This is not allowed	Space: object requires documentation	☐
5	005	You have not selected a subplan in order to determine its header charas	Space: object requires documentation	☐
6	006	You have not selected a planning session to define header characteristics	Space: object requires documentation	☐
7	007	Determine a subplan	Space: object requires documentation	☐
8	008	Select a planning session	Space: object requires documentation	☐
9	009	Characteristic &1 has overlapping selection conditions	Space: object requires documentation	☐
10	010	No hierarchy is yet determined for subplan &1, maintain	Space: object requires documentation	☐
11	011	Hierarchy &1 was not yet imported into STS - maintain	Space: object requires documentation	☐
12	012	Serious error in maintenance for STS hierarchy	Space: object requires documentation	☐
13	013	A lock has been set in subplan &1 (&2), planning session &3 (&4)	Space: object requires documentation	☐
14	014	No authorization to execute the report (object R_STS_CUST)	Space: object requires documentation	☐
15	015	Parameters for subplan and planning session are not specified in the URL	Space: object requires documentation	☐
16	016	Error when reading the hierarchy	Space: object requires documentation	☐
17	017	User &1 has no entry in the hierarchy	Space: object requires documentation	☐
18	018	Hierarchy was successfully imported into STS	Space: object requires documentation	☐
19	019	&1 messages successfully sent	Space: object requires documentation	☐
20	020	F4 Help only for BW version as of 3.x	Space: object requires documentation	☐
21	021	Hierarchy cannot contain more than one root text node	Space: object requires documentation	☐
22	022	Planning session cannot to be empty	Space: object requires documentation	☐
23	023	Planning session &1 does not exist in the database. Create	Space: object requires documentation	☐
24	024	Select a planning application	Space: object requires documentation	☐
25	025	Entry &1 does not exist in USR02	Space: object requires documentation	☐
26	026	Hierarchy import was exited without action	Space: object requires documentation	☐
27	027	No authorization to execute the Status and Tracking System	Space: object requires documentation	☐
28	028	No authorization for subplan &1 and planning session &2	Space: object requires documentation	☐
29	029	No history available	Space: object requires documentation	☐
30	030	Status &1 is the same as status &2	Space: object requires documentation	☐
31	031	Status switch from &1 to &2 already has an assigned sequence	Space: object requires documentation	☐
32	032	Hierarchy &1 for subplan &2 was not converted	The short text describes the object sufficiently	☐
33	033	Hierarchy &1 for subplan &2 was partly converted	The short text describes the object sufficiently	☐
34	034	Hierarchy &1 for subplan &2 was completely converted	The short text describes the object sufficiently	☐
35	035	No hierarchy assignment exists for selected subplan &1	The short text describes the object sufficiently	☐
36	036	Hierarchy for subplan &1 has already been imported acc. to new standard	The short text describes the object sufficiently	☐
37	037	Hierarchy for subplan &1 is already completely converted	The short text describes the object sufficiently	☐
38	038	You have to set both the from status and the to status	Space: object requires documentation	☐
39	039	Planning sequence &1 does not exist	Space: object requires documentation	☐
40	040	Time &1 cannot be interpreted, no change	Space: object requires documentation	☐
41	041	Time stamp &1 in time zone &2 could not be converted	Space: object requires documentation	☐
42	042	Attributes for subplan &1 planning session &2 are not maintained	Space: object requires documentation	☐
43	043	Error when reading the table of events for status switch	The short text describes the object sufficiently	☐
44	044	Action terminated without data change	Space: object requires documentation	☐
45	045	&1 entries successfully copied	The short text describes the object sufficiently	☐
46	046	&1 data records deleted	Space: object requires documentation	☐
47	047	Error when reading substitute table	The short text describes the object sufficiently	☐
48	048	Data records were deleted successfully	The short text describes the object sufficiently	☐
49	049	No e-mail address is maintained in USR02 for user &1	Space: object requires documentation	☐
50	050	There is already a partial assignment of &1 to &2	Space: object requires documentation	☐
51	051	There is already a higher-level assignment of &1 to &2	Space: object requires documentation	☐
52	052	Assignments already exist: &1 to &2 is not possible	Space: object requires documentation	☐
53	053	E-mail dispatch is not activated for subplan &1, planning session &2	Space: object requires documentation	☐
54	054	You have not specified a planning sequence	Space: object requires documentation	☐
55	055	Save has been terminated	Space: object requires documentation	☐
56	056	There is no person responsible maintained for this node	Space: object requires documentation	☐
57	057	It is not possible to navigate to other nodes	Space: object requires documentation	☐
58	059	Entry &1 does not exist in USR02	Space: object requires documentation	☐
59	060	Planning session &1 does not exist in the database	Space: object requires documentation	☐
60	061	Subplan &1 does not exist in the database	The short text describes the object sufficiently	☐
61	062	You have not specified any subobjects for copying	Space: object requires documentation	☐
62	063	&3: Target planning session does not have attributes. &3 aborted	Space: object requires documentation	☐
63	064	Existing entries were copied successfully	The short text describes the object sufficiently	☐
64	065	No hierarchy is maintained in the STS for subplan &1	Space: object requires documentation	☐
65	066	Entries with matching nodes have been copied	Space: object requires documentation	☐
66	067	Select a subplan	The short text describes the object sufficiently	☐
67	068	Select a planning session	The short text describes the object sufficiently	☐
68	069	You have not specified any subobjects to be deleted	The short text describes the object sufficiently	☐
69	070	&1: Target planning session was initialized	The short text describes the object sufficiently	☐
70	071	The URL for the planning application was copied successfully	The short text describes the object sufficiently	☐
71	072	The URL for the control report was copied successfully	The short text describes the object sufficiently	☐
72	073	The completion time was passed on successfully	The short text describes the object sufficiently	☐
73	074	Nodes were unlocked successfully	Space: object requires documentation	☐
74	075	Changed data was saved successfully	Space: object requires documentation	☐
75	076	Background job for e-mail dispatch restarted successfully	Space: object requires documentation	☐
76	077	Background job for e-mail dispatch is incorrect	Space: object requires documentation	☐
77	078	You have not specified a time zone. A default value was generated	Space: object requires documentation	☐
78	079	The completion time was not passed on. Process has been terminated	Space: object requires documentation	☐
79	080	Subplan &1, planning session &2 has been initialized successfully	The short text describes the object sufficiently	☐
80	081	The log file has been saved under number &1 in the database	The short text describes the object sufficiently	☐
81	082	No planning application URL entered to be copied	The short text describes the object sufficiently	☐
82	083	No control report URL entered to be copied	The short text describes the object sufficiently	☐
83	084	Copying is not possible as there are no other units on the same level	The short text describes the object sufficiently	☐
84	085	Copying is not possible as there are no other units on the same level	The short text describes the object sufficiently	☐
85	086	Choose either the BPS or the BI planning sequence	Space: object requires documentation	☐
86	087	Enter a BI planning sequence first	The short text describes the object sufficiently	☐
87	088	You can only enter variants for BI planning sequences	The short text describes the object sufficiently	☐
88	089	Variant &1 does not exist for planning sequence &2	Space: object requires documentation	☐
89	091	Error when parsing BW hierarchy in XML	Space: object requires documentation	☐
90	092	Hierarchy contains more than one top node	The short text describes the object sufficiently	☐
91	093	The top node of the hierarchy is not a text node	The short text describes the object sufficiently	☐
92	094	Errors while sending e-mail	The short text describes the object sufficiently	☐
93	095	Enter at least one planning session for the transport	The short text describes the object sufficiently	☐
94	096	Enter a transport request	The short text describes the object sufficiently	☐
95	097	Enter at least one subplan for the transport	The short text describes the object sufficiently	☐
96	099	Unexpected status; processing terminated	The short text describes the object sufficiently	☐
97	100	&3: At least 1 entry could not be deleted	Space: object requires documentation	☐
98	101	&1: Entries for the selection were deleted	Space: object requires documentation	☐
99	102	&1: No entries were found for the selection	Space: object requires documentation	☐
100	103	Comments: Could not deleted everything for &1 &2 of &3 &4	Space: object requires documentation	☐
101	104	&1: Hierarchies for subplan &2 were deleted from the STS	Space: object requires documentation	☐
102	105	&1: Deletion of hierarchies for subplan &2 from the STS has been aborted	The short text describes the object sufficiently	☐
103	106	Comments: All deleted for &1 &2 of &3 &4	Space: object requires documentation	☐
104	107	&3: You do not have authorization for subplan &1, planning session &2	Space: object requires documentation	☐
105	108	&2: Attributes are not maintained for any planning session for subplan &1	Space: object requires documentation	☐
106	109	&3: No hierarchies for subplan &1 were found in the STS	Space: object requires documentation	☐
107	110	Comments: No attributes are maintained for &1 &2 of &3 &4	Space: object requires documentation	☐
108	111	Hierarchy: No hierarchies were found for subplan &1	The short text describes the object sufficiently	☐
109	112	Lock on data set by Status & Tracking System	The short text describes the object sufficiently	☐
110	130	Insert: &3: At least one entry could not be inserted	Space: object requires documentation	☐
111	131	Insert: &1: Entries for the selection were inserted	Space: object requires documentation	☐
112	132	Insert: &1: No entries to be copied were found for the selection	Space: object requires documentation	☐
113	140	Delete: &3: At least one entry could not be deleted	Space: object requires documentation	☐
114	141	Delete: &1: Entries for the selection were deleted	Space: object requires documentation	☐
115	142	Delete: &1: No entries were found for the selection	The short text describes the object sufficiently	☐
116	150	Subplans &1 and &2 have no common node intersections	Space: object requires documentation	☐
117	151	Subplans &1 and &2 have &3 common nodes	Space: object requires documentation	☐
118	160	Errors occurred during deletion: A rollback was performed	Space: object requires documentation	☐
119	161	Errors occurred during copying: A rollback was performed	Space: object requires documentation	☐
120	162	Delete operation was completed successfully	The short text describes the object sufficiently	☐
121	163	Copying process was completed successfully	The short text describes the object sufficiently	☐
122	170	Invalid Navigation State	The short text describes the object sufficiently	☐

History

Last changed on/by	20130531	SAP
SAP Release Created in	3.1A