UPS1 - Nachrichten SEM-BPS Status- und Trackingsystem
The following messages are stored in message class UPS1: Nachrichten SEM-BPS Status- und Trackingsystem.
It is part of development package UPS in software component BW-PLA-BPS. This development package consists of objects that can be grouped under "Status and Tracking System".
It is part of development package UPS in software component BW-PLA-BPS. This development package consists of objects that can be grouped under "Status and Tracking System".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Hierarchy &1 contains range nodes. This is not allowed |
| 002 | First determine a planning area |
| 003 | Determine characteristic names |
| 004 | Hierarchy &1 contains dummy nodes. This is not allowed |
| 005 | You have not selected a subplan in order to determine its header charas |
| 006 | You have not selected a planning session to define header characteristics |
| 007 | Determine a subplan |
| 008 | Select a planning session |
| 009 | Characteristic &1 has overlapping selection conditions |
| 010 | No hierarchy is yet determined for subplan &1, maintain |
| 011 | Hierarchy &1 was not yet imported into STS - maintain |
| 012 | Serious error in maintenance for STS hierarchy |
| 013 | A lock has been set in subplan &1 (&2), planning session &3 (&4) |
| 014 | No authorization to execute the report (object R_STS_CUST) |
| 015 | Parameters for subplan and planning session are not specified in the URL |
| 016 | Error when reading the hierarchy |
| 017 | User &1 has no entry in the hierarchy |
| 018 | Hierarchy was successfully imported into STS |
| 019 | &1 messages successfully sent |
| 020 | F4 Help only for BW version as of 3.x |
| 021 | Hierarchy cannot contain more than one root text node |
| 022 | Planning session cannot to be empty |
| 023 | Planning session &1 does not exist in the database. Create |
| 024 | Select a planning application |
| 025 | Entry &1 does not exist in USR02 |
| 026 | Hierarchy import was exited without action |
| 027 | No authorization to execute the Status and Tracking System |
| 028 | No authorization for subplan &1 and planning session &2 |
| 029 | No history available |
| 030 | Status &1 is the same as status &2 |
| 031 | Status switch from &1 to &2 already has an assigned sequence |
| 032 | Hierarchy &1 for subplan &2 was not converted |
| 033 | Hierarchy &1 for subplan &2 was partly converted |
| 034 | Hierarchy &1 for subplan &2 was completely converted |
| 035 | No hierarchy assignment exists for selected subplan &1 |
| 036 | Hierarchy for subplan &1 has already been imported acc. to new standard |
| 037 | Hierarchy for subplan &1 is already completely converted |
| 038 | You have to set both the from status and the to status |
| 039 | Planning sequence &1 does not exist |
| 040 | Time &1 cannot be interpreted, no change |
| 041 | Time stamp &1 in time zone &2 could not be converted |
| 042 | Attributes for subplan &1 planning session &2 are not maintained |
| 043 | Error when reading the table of events for status switch |
| 044 | Action terminated without data change |
| 045 | &1 entries successfully copied |
| 046 | &1 data records deleted |
| 047 | Error when reading substitute table |
| 048 | Data records were deleted successfully |
| 049 | No e-mail address is maintained in USR02 for user &1 |
| 050 | There is already a partial assignment of &1 to &2 |
| 051 | There is already a higher-level assignment of &1 to &2 |
| 052 | Assignments already exist: &1 to &2 is not possible |
| 053 | E-mail dispatch is not activated for subplan &1, planning session &2 |
| 054 | You have not specified a planning sequence |
| 055 | Save has been terminated |
| 056 | There is no person responsible maintained for this node |
| 057 | It is not possible to navigate to other nodes |
| 059 | Entry &1 does not exist in USR02 |
| 060 | Planning session &1 does not exist in the database |
| 061 | Subplan &1 does not exist in the database |
| 062 | You have not specified any subobjects for copying |
| 063 | &3: Target planning session does not have attributes. &3 aborted |
| 064 | Existing entries were copied successfully |
| 065 | No hierarchy is maintained in the STS for subplan &1 |
| 066 | Entries with matching nodes have been copied |
| 067 | Select a subplan |
| 068 | Select a planning session |
| 069 | You have not specified any subobjects to be deleted |
| 070 | &1: Target planning session was initialized |
| 071 | The URL for the planning application was copied successfully |
| 072 | The URL for the control report was copied successfully |
| 073 | The completion time was passed on successfully |
| 074 | Nodes were unlocked successfully |
| 075 | Changed data was saved successfully |
| 076 | Background job for e-mail dispatch restarted successfully |
| 077 | Background job for e-mail dispatch is incorrect |
| 078 | You have not specified a time zone. A default value was generated |
| 079 | The completion time was not passed on. Process has been terminated |
| 080 | Subplan &1, planning session &2 has been initialized successfully |
| 081 | The log file has been saved under number &1 in the database |
| 082 | No planning application URL entered to be copied |
| 083 | No control report URL entered to be copied |
| 084 | Copying is not possible as there are no other units on the same level |
| 085 | Copying is not possible as there are no other units on the same level |
| 086 | Choose either the BPS or the BI planning sequence |
| 087 | Enter a BI planning sequence first |
| 088 | You can only enter variants for BI planning sequences |
| 089 | Variant &1 does not exist for planning sequence &2 |
| 091 | Error when parsing BW hierarchy in XML |
| 092 | Hierarchy contains more than one top node |
| 093 | The top node of the hierarchy is not a text node |
| 094 | Errors while sending e-mail |
| 095 | Enter at least one planning session for the transport |
| 096 | Enter a transport request |
| 097 | Enter at least one subplan for the transport |
| 099 | Unexpected status; processing terminated |
| 100 | &3: At least 1 entry could not be deleted |
| 101 | &1: Entries for the selection were deleted |
| 102 | &1: No entries were found for the selection |
| 103 | Comments: Could not deleted everything for &1 &2 of &3 &4 |
| 104 | &1: Hierarchies for subplan &2 were deleted from the STS |
| 105 | &1: Deletion of hierarchies for subplan &2 from the STS has been aborted |
| 106 | Comments: All deleted for &1 &2 of &3 &4 |
| 107 | &3: You do not have authorization for subplan &1, planning session &2 |
| 108 | &2: Attributes are not maintained for any planning session for subplan &1 |
| 109 | &3: No hierarchies for subplan &1 were found in the STS |
| 110 | Comments: No attributes are maintained for &1 &2 of &3 &4 |
| 111 | Hierarchy: No hierarchies were found for subplan &1 |
| 112 | Lock on data set by Status & Tracking System |
| 130 | Insert: &3: At least one entry could not be inserted |
| 131 | Insert: &1: Entries for the selection were inserted |
| 132 | Insert: &1: No entries to be copied were found for the selection |
| 140 | Delete: &3: At least one entry could not be deleted |
| 141 | Delete: &1: Entries for the selection were deleted |
| 142 | Delete: &1: No entries were found for the selection |
| 150 | Subplans &1 and &2 have no common node intersections |
| 151 | Subplans &1 and &2 have &3 common nodes |
| 160 | Errors occurred during deletion: A rollback was performed |
| 161 | Errors occurred during copying: A rollback was performed |
| 162 | Delete operation was completed successfully |
| 163 | Copying process was completed successfully |
| 170 | Invalid Navigation State |