SAP ABAP Message Class RMPS_DISPOSAL (Disposal According to TNA)
Basic Data
Hierarchy
☛
SAP_ABA (Software Component) Cross-Application Component
⤷ CA-GTF-RCM (Application Component) Records and Case Management
⤷ RMPSPRO_DISPOSAL (Package) PRO Disposal
⤷ CA-GTF-RCM (Application Component) Records and Case Management
⤷ RMPSPRO_DISPOSAL (Package) PRO Disposal
Attributes
Message class | RMPS_DISPOSAL | |
Short Description | Disposal According to TNA | |
Changed On | 20110908 | |
Last Changed At | 160734 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 001 | There is already a data record with the same key | Space: object requires documentation | |
2 | 002 | Text Table RMPSPRO_RULEBAST inconsistent with RMPSPRO_RULEBASE | Space: object requires documentation | |
3 | 003 | New disposal schedule &1 created successfully | Space: object requires documentation | |
4 | 004 | No entries were selected | Space: object requires documentation | |
5 | 005 | Marked entries were deleted | Space: object requires documentation | |
6 | 006 | Action cancelled by user | Space: object requires documentation | |
7 | 007 | Period must be 0 years and 0 months later | Space: object requires documentation | |
8 | 009 | Rule &1 is already flagged for deletion | Space: object requires documentation | |
9 | 010 | Internal error: Program was terminated | Space: object requires documentation | |
10 | 011 | Internal error occurred during saving of change reason | Space: object requires documentation | |
11 | 012 | Error during update. Changes were reversed | Space: object requires documentation | |
12 | 013 | Disposal schedule &1 was changed | Space: object requires documentation | |
13 | 014 | Enter a period larger then 0 years and 0 months | Space: object requires documentation | |
14 | 015 | Internal error: Action is canceled | Space: object requires documentation | |
15 | 016 | File was created successfully (&1 entries) | Space: object requires documentation | |
16 | 017 | There are entries with identical keys | Space: object requires documentation | |
17 | 018 | Disposal schedules were imported successfully (&1 entries) | Space: object requires documentation | |
18 | 019 | No changes were made | Space: object requires documentation | |
19 | 020 | You must enter a change reason | Space: object requires documentation | |
20 | 021 | No change data available | Space: object requires documentation | |
21 | 022 | Internal error when saving comment | The short text describes the object sufficiently | |
22 | 023 | Some objects were not processed successfully | Space: object requires documentation | |
23 | 024 | All objects were processed successfully | The short text describes the object sufficiently | |
24 | 025 | There is no default RMS ID | The short text describes the object sufficiently | |
25 | 026 | It is only possible to unlock at folder level | The short text describes the object sufficiently | |
26 | 027 | &1 stage(s) created for disposal schedules | The short text describes the object sufficiently | |
27 | 028 | Errors in &1 disposal schedule(s); schedule(s) not imported | The short text describes the object sufficiently | |
28 | 029 | &1 stages have errors and were not imported | The short text describes the object sufficiently | |
29 | 030 | Postprocessing run finished: &1 successful, &2 failed | The short text describes the object sufficiently | |
30 | 050 | The end date cannot be before the start date | The short text describes the object sufficiently | |
31 | 051 | Select at least one disposal action | The short text describes the object sufficiently | |
32 | 052 | Select at least one object type | The short text describes the object sufficiently | |
33 | 053 | Enter a class or a start and end date | Space: object requires documentation | |
34 | 054 | You must enter an RMS ID | The short text describes the object sufficiently | |
35 | 055 | Internal error: Search query canceled | The short text describes the object sufficiently | |
36 | 056 | No element type found for TNA fileplan class | The short text describes the object sufficiently | |
37 | 057 | No objects were found under this fileplan class | Space: object requires documentation | |
38 | 058 | Enter a start and end date | The short text describes the object sufficiently | |
39 | 059 | Enter a fileplan class | The short text describes the object sufficiently | |
40 | 060 | No objects found for the selection conditions | The short text describes the object sufficiently | |
41 | 061 | A disposal lock is set on at least one selected object | Space: object requires documentation | |
42 | 062 | Transfer canceled. See long text for more information | Space: object requires documentation | |
43 | 063 | Destruction canceled. See long text for more information | Space: object requires documentation | |
44 | 064 | The current export status is preventing the export from being confirmed | Space: object requires documentation | |
45 | 065 | The object selected does not exist or was deleted | The short text describes the object sufficiently | |
46 | 066 | Current RMS ID &1 does not permit disposals according to the TNA standard | The short text describes the object sufficiently | |
47 | 067 | Inconsistent data in folder &1 document &2 | Space: object requires documentation | |
48 | 068 | Operation terminated, processing stopped | The short text describes the object sufficiently | |
49 | 069 | Part: &1 (PDIR ID: &2) | The short text describes the object sufficiently | |
50 | 070 | Enter a valid selection date | The short text describes the object sufficiently | |
51 | 071 | Could not save transaction data | The short text describes the object sufficiently | |
52 | 100 | Conflict: Destruction of folder overrides review of document | The short text describes the object sufficiently | |
53 | 101 | Conflict: Date of action at folder level before action at document level | The short text describes the object sufficiently | |
54 | 102 | New rule is identical to the inherited rule of the superordinate class | The short text describes the object sufficiently | |
55 | 103 | New rule has a longer period than the rule of the superordinate class | The short text describes the object sufficiently | |
56 | 104 | New rule has a shorter period than the rule of the superordinate class | The short text describes the object sufficiently | |
57 | 105 | New rule has a stronger action than the rule of the superordinate class | The short text describes the object sufficiently | |
58 | 106 | New rule has a weaker action than the rule of the superordinate class | The short text describes the object sufficiently | |
59 | 107 | Action and period of the rule of the superordinate class are identical | The short text describes the object sufficiently | |
60 | 108 | Conflict: Destruction of folder overrides export of document | The short text describes the object sufficiently | |
61 | 109 | Conflict: Destruction of folder overrides transfer of document | The short text describes the object sufficiently | |
62 | 110 | Conflict: Transfer of folder overrides review of document | The short text describes the object sufficiently | |
63 | 111 | Conflict: Transfer of folder overrides export of document | The short text describes the object sufficiently | |
64 | 112 | Conflict: Export of folder overrides review of document | The short text describes the object sufficiently | |
65 | 113 | Document '&1' has no disposal schedule | The short text describes the object sufficiently | |
66 | 114 | Document '&1' has no disposal due date | The short text describes the object sufficiently | |
67 | 115 | Destruction cannot be the first assigned rule | The short text describes the object sufficiently | |
68 | 150 | XML Export | The short text describes the object sufficiently | |
69 | 151 | Directory &1 could not be created | Space: object requires documentation | |
70 | 152 | Attribute for &1 could not be saved | Space: object requires documentation | |
71 | 153 | Contents of &1 could not be saved | Space: object requires documentation | |
72 | 154 | Log for &1 could not be saved | Space: object requires documentation | |
73 | 155 | &1 could not be executed for &2 "&3" | The short text describes the object sufficiently | |
74 | 156 | Table &1 does not exist | The short text describes the object sufficiently | |
75 | 157 | Error in foreign key check for &1-&2 | The short text describes the object sufficiently | |
76 | 158 | Entry &1 does not exist for &2; check your input | The short text describes the object sufficiently | |
77 | 159 | Schedule &1 not created | The short text describes the object sufficiently | |
78 | 200 | The export directory could not be created | The short text describes the object sufficiently | |
79 | 201 | You must enter a comment | The short text describes the object sufficiently | |
80 | 202 | The export directory already exists, delete it or choose another | The short text describes the object sufficiently | |
81 | 250 | There are no entries for the selection criteria | The short text describes the object sufficiently | |
82 | 300 | The export status was successfully changed to "export confirmed" | The short text describes the object sufficiently | |
83 | 301 | Error during update in database, export status not converted | The short text describes the object sufficiently | |
84 | 302 | Display variant could not be deleted | The short text describes the object sufficiently | |
85 | 303 | Export confirmed partially. Update not possible for some objects | The short text describes the object sufficiently | |
86 | 349 | Log opening disposal - export process | The short text describes the object sufficiently | |
87 | 350 | Log Opening Disposal - Destruction Process | The short text describes the object sufficiently | |
88 | 351 | Log Opening Disposal - Destruction According to Transfer | The short text describes the object sufficiently | |
89 | 352 | Log closing - Destruction finished successfully | The short text describes the object sufficiently | |
90 | 353 | Log closing - Destruction could not be finished successfully | The short text describes the object sufficiently | |
91 | 354 | Successful destruction of document '&1' (&2) | The short text describes the object sufficiently | |
92 | 355 | Failed destruction of document '&1' (&2) | The short text describes the object sufficiently | |
93 | 356 | Successful destruction of part '&1' | The short text describes the object sufficiently | |
94 | 357 | Destruction of part '&1' failed | The short text describes the object sufficiently | |
95 | 358 | Successful destruction of folder '&1' | The short text describes the object sufficiently | |
96 | 359 | Destruction of folder '&1' failed | The short text describes the object sufficiently | |
97 | 360 | Successful destruction of alternative display of doc. '&1' (&2) | The short text describes the object sufficiently | |
98 | 361 | Failed destruction of alternative repres. of document '&1' | The short text describes the object sufficiently | |
99 | 362 | Destruction of folder '&1' failed: 'no authorization' | The short text describes the object sufficiently | |
100 | 363 | Destruction of folder '&1' failed: 'Container enqueued' | The short text describes the object sufficiently | |
101 | 364 | Folder '&1' successfully deleted from file plan | The short text describes the object sufficiently | |
102 | 365 | Folder '&1' not deleted successfully from file plan | The short text describes the object sufficiently | |
103 | 366 | Start export of folder '&1' | The short text describes the object sufficiently | |
104 | 367 | Start export of part '&1' (&2) | The short text describes the object sufficiently | |
105 | 368 | Start export of document '&1' (&2) | The short text describes the object sufficiently | |
106 | 369 | Error when exporting folder '&1' | The short text describes the object sufficiently | |
107 | 370 | Error when exporting part '&1' (&2) | The short text describes the object sufficiently | |
108 | 371 | Error when exporting document '&1' (&2) | The short text describes the object sufficiently | |
109 | 372 | Log closing - export finished successfully ID: &1 | The short text describes the object sufficiently | |
110 | 373 | Log closing - export could not be finished successfully | The short text describes the object sufficiently | |
111 | 374 | Link from superior part removed | The short text describes the object sufficiently | |
112 | 375 | Link from superior folder removed | The short text describes the object sufficiently | |
113 | 376 | Start export alternative display of document '&1' | The short text describes the object sufficiently | |
114 | 377 | Termination: Rule of document "&1" possibly deleted | The short text describes the object sufficiently | |
115 | 378 | Could not update '&1' &2 | The short text describes the object sufficiently | |
116 | 379 | Could not destroy (&1) incoming post item '&2' &3 | The short text describes the object sufficiently | |
117 | 380 | Incoming post item '&2' &3 destroyed (&1) | The short text describes the object sufficiently | |
118 | 381 | Post-export: update objects if disposal is multistage | The short text describes the object sufficiently | |
119 | 382 | Post-export actions successful | The short text describes the object sufficiently | |
120 | 383 | Post-export actions not successful | The short text describes the object sufficiently | |
121 | 400 | Complete all fields | The short text describes the object sufficiently | |
122 | 401 | Path does not exist | The short text describes the object sufficiently | |
123 | 402 | Log for object '&1' (&2) was successfully exported | The short text describes the object sufficiently | |
124 | 403 | Log for object '&1' could not be exported | The short text describes the object sufficiently | |
125 | 405 | Physical content of object '&1' &2 flagged for export | The short text describes the object sufficiently | |
126 | 406 | Current RMS ID '&1' does not allow disposal according to DOD standard | The short text describes the object sufficiently | |
127 | 407 | No &1-relevant RMS found | The short text describes the object sufficiently | |
128 | 500 | Current RMS ID '&1' does not allow disposal according to DoD standard | The short text describes the object sufficiently | |
129 | 600 | Could not create ALV table | The short text describes the object sufficiently | |
130 | 700 | Cancelled by user | The short text describes the object sufficiently | |
131 | 701 | Event types downloaded | The short text describes the object sufficiently | |
132 | 702 | Could not download event types | The short text describes the object sufficiently | |
133 | 703 | No entries found in event table | The short text describes the object sufficiently | |
134 | 704 | No entries found in event text table | The short text describes the object sufficiently | |
135 | 705 | Could not import event types | The short text describes the object sufficiently | |
136 | 706 | All event types imported | The short text describes the object sufficiently | |
137 | 707 | &1 entries imported; existing entries not overwritten | The short text describes the object sufficiently | |
138 | 708 | All event texts imported | The short text describes the object sufficiently | |
139 | 709 | Could not import event texts | The short text describes the object sufficiently | |
140 | 710 | Request for transaction ID: &1 for transfer | Space: object requires documentation | |
141 | 711 | Incorrect set selected. Reference to transaction ID: &1 | Space: object requires documentation | |
142 | 712 | Error in the ALV selection for the process "Transfer to External Folder" | The short text describes the object sufficiently | |
143 | 713 | Selected documents do not contain a target or do not have a unique target | Space: object requires documentation | |
144 | 714 | Following SPS_ID was determined by the system: &1 | The short text describes the object sufficiently | |
145 | 715 | You must first maintain external target folder in view "RMPS_DOD_DOCSTRG" | The short text describes the object sufficiently | |
146 | 716 | Incorrect or missing value for offline store, see long text | Space: object requires documentation | |
147 | 717 | Log transfer terminated | The short text describes the object sufficiently | |
148 | 718 | Download for log file terminated by the user | The short text describes the object sufficiently | |
149 | 719 | Open log: Transfer to external storage | The short text describes the object sufficiently | |
150 | 720 | Area ID "&1" was determined on the basis of these data records | The short text describes the object sufficiently | |
151 | 721 | Unable to determine area ID | The short text describes the object sufficiently | |
152 | 722 | RMS ID "&1" was determined on the basis of these data records | The short text describes the object sufficiently | |
153 | 723 | Unable to determine RMS ID | The short text describes the object sufficiently | |
154 | 724 | Authorization check performed successfully | The short text describes the object sufficiently | |
155 | 725 | &1 objects are available to be transferred to an offline store | The short text describes the object sufficiently | |
156 | 726 | Error occurred determining document numbers | The short text describes the object sufficiently | |
157 | 727 | Error occurred during relocation process | The short text describes the object sufficiently | |
158 | 728 | Start performed in the test mode | The short text describes the object sufficiently | |
159 | 729 | Error occurred during the download | The short text describes the object sufficiently | |
160 | 730 | Unable to start logging process -> Termination | The short text describes the object sufficiently | |
161 | 731 | Process performed without serious problems occurring | The short text describes the object sufficiently | |
162 | 732 | Details logged in the application log (SLG1) | The short text describes the object sufficiently | |
163 | 733 | Log file successfully downloaded to local PC | The short text describes the object sufficiently | |
164 | 734 | Error occurred while transferring detailed logging to SLG1 | The short text describes the object sufficiently | |
165 | 735 | Start transfer process to offline storage "&1" | The short text describes the object sufficiently | |
166 | 736 | No open content available for &1 (&2) | The short text describes the object sufficiently | |
167 | 737 | Application log successfully instantiated | The short text describes the object sufficiently | |
168 | 738 | Closing log. Export started successfully. ID: &1 | The short text describes the object sufficiently | |
169 | 739 | Transaction ID &1 generated for disposal evaluation | The short text describes the object sufficiently | |
170 | 740 | Transfer status was successfully changed to "Export Confirmed" | The short text describes the object sufficiently | |
171 | 741 | Unable to set transfer status to "Export Confirmed" | The short text describes the object sufficiently | |
172 | 742 | Attributes for transaction ID: &1 changed for document &2 | The short text describes the object sufficiently | |
173 | 743 | 1 (&2) must contain embedded font types for the transfer to NARA | The short text describes the object sufficiently | |
174 | 744 | Attribute update for transaction ID "&1", Doc."&2" failed | The short text describes the object sufficiently | |
175 | 745 | Attributes for new folder successfully logged in document "&1" | The short text describes the object sufficiently | |
176 | 746 | Logging for new folder in document "&1" failed | The short text describes the object sufficiently | |
177 | 747 | Attribute '&1' for document '&2' successfully converted | The short text describes the object sufficiently | |
178 | 748 | Attribute conversion to '&1' for document '&2' failed | The short text describes the object sufficiently | |
179 | 749 | Update of attribute '&1' and/or '&2' for doc. '&3' failed | The short text describes the object sufficiently | |
180 | 750 | Update of attributes '&1' and '&2' successful for '&3' | The short text describes the object sufficiently | |
181 | 751 | Inconsistency in 'Folder/Part' "&1" &2 &3 | The short text describes the object sufficiently | |
182 | 752 | Content of this folder is not observed during the transfer | The short text describes the object sufficiently | |
183 | 753 | Conflict occurred during record/part check '&1' &2 &3 | The short text describes the object sufficiently | |
184 | 754 | Record/part '&1' &2 &3 determined successfully | The short text describes the object sufficiently | |
185 | 755 | Object '&1' in record/part '&2' cannot be transferred to external storage | Space: object requires documentation | |
186 | 756 | Unable to generate object icon &1 | The short text describes the object sufficiently | |
187 | 757 | Inconsistencies detected between folder &1 and document for attribute &2 | The short text describes the object sufficiently | |
188 | 758 | Object type &1 selected for transfer to external storage not supported | The short text describes the object sufficiently | |
189 | 759 | Processing for record "&1" terminated | The short text describes the object sufficiently | |
190 | 760 | Error occurred while processing attributes for record '&1' | The short text describes the object sufficiently | |
191 | 761 | Status for record "&1" corresponds to "&2" &3 in this run | The short text describes the object sufficiently | |
192 | 762 | Selected record "&1" has no content -> Transfer status cannot be defined | The short text describes the object sufficiently | |
193 | 763 | Selected data record(s) cannot be transferred to external storage | The short text describes the object sufficiently | |
194 | 764 | Identical data records should be updated -> See long text | Space: object requires documentation | |
195 | 765 | Results of run '&1' being updated for Tx.: RMPS_DOD_TRANS | The short text describes the object sufficiently | |
196 | 766 | Run '&1' is not updated for Tx.: RMPS_DOD_TRANS (test mode) | The short text describes the object sufficiently | |
197 | 767 | Attribute update for record '&1' partially/completely failed | The short text describes the object sufficiently | |
198 | 768 | Record '&1' is observed for the run in spite of date conflicts | The short text describes the object sufficiently | |
199 | 769 | Document '&1' is processed for the run in spite of date conflicts | The short text describes the object sufficiently | |
200 | 770 | Unable to find document for object '&1' (&2 &3) | The short text describes the object sufficiently | |
201 | 771 | Processing of linked objects failed | The short text describes the object sufficiently | |
202 | 772 | Check/processing of linked objects for document '&1' performed | The short text describes the object sufficiently | |
203 | 773 | Start performed in update mode | The short text describes the object sufficiently | |
204 | 774 | Error occurred updating RMPSPRO_DP_REP1 | The short text describes the object sufficiently | |
205 | 775 | Inconsistency in document object '&1 &2' | The short text describes the object sufficiently | |
206 | 776 | Paper document &1 included as "Transfer to Offline Storage" | The short text describes the object sufficiently | |
207 | 897 | &1&2&3&4 | The short text describes the object sufficiently | |
208 | 898 | Transaction ID: &1, user: &2, time stamp: &3 | The short text describes the object sufficiently | |
209 | 899 | &1 &2 &3 &4 | The short text describes the object sufficiently | |
210 | 900 | Destruction for object &1 failed since it is frozen | The short text describes the object sufficiently |
History
Last changed on/by | 20110908 | SAP | |
SAP Release Created in | 110_620 |