PAK - Paket-API / Paket-Tools
The following messages are stored in message class PAK: Paket-API / Paket-Tools.
It is part of development package SPAK_API in software component BC-DWB-TOO-PAK. This development package consists of objects that can be grouped under "Package API".
It is part of development package SPAK_API in software component BC-DWB-TOO-PAK. This development package consists of objects that can be grouped under "Package API".
Message Nr ▲ | Message Text |
---|---|
001 | Function &1 &2 is not yet implemented |
002 | Function &1 &2 is currently being developed |
003 | Reading package hierarchy data has not yet been implemented |
004 | &1 &2: No development objects used |
005 | No authorization to display package &1 |
006 | System data not configured |
007 | Standard transport layer not configured |
008 | Software component '&1' not allowed; superpackage has SW component '&2' |
009 | No authorization to display package interface &1 |
010 | Application component '&1' is not allowed (see long text) |
011 | Internal error in &1 / &2. Reason: &3 &4 |
012 | Parameter error in &1 / &2. Parameter '&3' with value '&4' |
013 | Internal error in &1 / &2 |
014 | Unexpected exception in &1 / &2 |
015 | Invalid object of type &1 with key &2 &3 &4 |
016 | Error accessing object of type &1 with key &2 &3 &4 |
017 | Package &1 has to be assigned to a superpackage |
018 | Package &1 is its own superpackage |
019 | Package &1 contains dev. objects and therefore cannot be a main package |
020 | No authorization to change object type '&1' with key &2 &3 &4 |
021 | Object does not exist in database; object type '&1' with key &2 &3 &4 |
022 | Object already exists in database; object type '&1' with key &2 &3 &4 |
023 | Short text does not exist for object type '&1' with key &2 |
024 | Database access error (table &1) |
025 | Use access &1 still exists in subpackages |
026 | Enter a valid value for the translation relevance |
027 | Create a structure package only as a subpackage of a structure package |
028 | Create a main package only as a subpackage of a structure/main package |
029 | A structure package can only be a subpackage of a structure package |
030 | A main package can only be a subpackage of a structure/main package |
031 | Object was already changed; object type '&1' with key &2 &3 &4 |
032 | Package assignment cannot be changed (package interface &1 is not empty) |
033 | Use access &1 &2 does not exist in the database |
034 | Package interface &1 already exists |
035 | Package &1 exists only in the buffer; save first |
036 | Package &1 already deleted in the buffer |
037 | Package &1 already has a superpackage assigned |
038 | Package &1 cannot be changed |
039 | No authorization to change the direct superpackage of package &1 |
040 | Package &1 does not exist |
041 | No packages or package interfaces were selected |
042 | Package &1 already exists |
043 | Package &1 already exists in the buffer |
044 | Character string '&1' not allowed as name of a package |
045 | Package &1 begins with an invalid character (such as a digit) |
046 | Package &1 is reserved for local SAP classes |
047 | Package &1 is invalid |
048 | Enter short description for package &1 |
049 | Enter a valid user, not &1, as the person responsible |
050 | Enter application component for package &1 |
051 | Package &1 still contains development objects or other packages |
052 | Package interface &1 is not assigned to package &2 |
053 | Package &1 does not contain any subpackages |
054 | Package &1 only exists in the buffer |
055 | Package interface &1 does not exist |
056 | Package interface &1 already exists |
057 | Package interface &1 already exists in the buffer |
058 | Package &1 is already locked |
059 | Package interface &1 is already locked |
060 | Package &1 was already deleted |
061 | Package interface &1 was already deleted |
062 | No authorization to change package &1 |
063 | No authorization to change package interface &1 |
064 | Package &1 was not locked |
065 | Package &1 is already changed in the buffer |
066 | Package interface &1 was not locked |
067 | Package interface &1 is already changed in the buffer |
068 | Package interface &1 exists only in the buffer; save first |
069 | Package interface &1 is already deleted from the buffer |
070 | Package interface &1 is already locked |
071 | Package interface &1 was not locked |
072 | Package interface &1 is already changed in the buffer |
073 | Access control list for package interface &1 is already locked |
074 | Access control list for package interface &1 was not locked |
075 | Access control list for package interface &1 already changed in buffer |
076 | Properties of package interface &1 cannot be changed |
077 | Content of package interface &1 cannot be changed |
078 | Access control list of package interface cannot be changed |
079 | Package interface &1 exists only in the buffer |
080 | Package interface &1 still contains development elements |
081 | Package interface &1 does not contain &2/&3 as a development element |
082 | Package interface element &1 &2 cannot be deleted |
083 | Package interface &1 already released for package &2 |
084 | Access control list of package interface &1 is empty |
085 | Package &1 is not the superpackage of package &2 |
086 | Package &1 has no superpackage assigned |
087 | Administration authorization required for changing package &1 |
088 | Application component '&1' does not exist |
089 | Package &1 locked; data refresh not possible |
090 | Use accesses for package &1 are already locked |
091 | Use accesses for package &1 were not locked |
092 | Use accesses for package &1 were already changed in the buffer |
093 | Use access from package &1 to package interface &2 already exists |
094 | Package interface element &1 &2 cannot be changed |
095 | Package interface element &1 &2 does not exist in package interface &3 |
096 | Development element &1 &2 already exists in package interface &3 |
097 | Interface element &1 &2 in interface &3 already deleted in the buffer |
098 | Development element &1 &2 in package interface &3 cannot be changed |
099 | Enter short description for package interface &1 |
100 | Internal error: package &1 was deleted and could not be unlocked |
101 | Internal error: cannot unlock deleted package interface |
102 | User &1 not valid |
103 | Access control list for package interface &1 cannot be changed |
104 | Cannot change content of package interface &1 |
105 | Package interface &1 locked; refresh of data not possible |
106 | Use accesses for package &1 are not locked |
107 | Development element needed for surrounding package interface &1 |
108 | Local packages must begin with 'TEST' |
109 | Package interface prefix &1 is already in use |
110 | Development element type &1 is not supported |
111 | Development element &1 &2 does not exist |
112 | Development element &1 &2 is not stored in the package interface package |
113 | Cannot change type of package interface &1 |
114 | Package name must start with S or TEST |
115 | Package name must start with A-R, U-X, or TEST |
116 | Application component cannot be set for local packages |
117 | Error checking application component |
118 | Package &1 cannot be its own superpackage |
119 | Package interfaces must not contain the character string '&1' |
120 | Main packages are locked for extensions |
121 | Package interface &1 does not exist |
122 | Package interface &1 is locked for extensions |
123 | Only &2 elements can be added to package interface &1 |
124 | Cannot access release attribute for development element &1 &2 |
125 | Specifying local or private packages is not allowed |
126 | No access control list activated for package interface &1 |
127 | List of client packages for package interface &1 is not empty |
128 | Development element cannot be added to package interface |
129 | Package &1 has no use access to package interface &2 |
130 | Package interface &1 has no main package |
131 | Package interface &1 points to a package that is too deeply nested |
132 | Use accesses to a package's own package interface are not possible |
133 | A main package cannot be a subpackage of a development package |
134 | Cannot add further development objects to &1 &2 |
135 | You have no authorization to switch off the package check |
136 | Package API could not be initialized |
137 | Application component &1 does not exist |
138 | Query of global TADIR currently not possible |
139 | Cannot lock package interface &1 for deletion |
140 | Structure package name or main package name must start with A-S or U-X |
141 | Package &1 is locked in roll area and was already changed in the buffer |
142 | Package &1 already deleted in the buffer |
143 | Package interface &1 is already deleted from the buffer |
144 | Package name cannot contain spaces |
145 | Enter a package |
146 | Content of package interface &1 cannot be copied directly |
147 | &1 &2 cannot be included in package interface &3 |
148 | Object &1 &2 with errors in package interface &3 |
150 | The package hierarchy for package &1 contains errors; check package &2 |
151 | You cannot make package &1 a subpackage of package &2 |
152 | Package interface name cannot contain spaces |
153 | Structure package &1 does not exist |
154 | For package &1 only use accesses to other structure packages are possible |
155 | Package interface &1 has an invalid type |
156 | Object &1 &2 does not exist or its package cannot be determined |
157 | Function module &1 does not exist |
158 | Function group &1 has an invalid name |
159 | You have no authorization to create the main package &1 |
160 | Virtual standard package interfaces do not contain any develop. objects |
161 | Filter package interfaces can only contain objects of type 'PCHK' |
162 | Package interface &1 cannot be used by package &2 |
163 | Package &1 must not use any objects from its superpackage &2 |
164 | No authorization to change structure package &1 |
165 | No authorization to change main package &1 |
166 | No authorization for creating package interface &1 |
167 | No authorization for creating structure package &1 |
168 | No authorization for creating package &1 |
169 | Use access to package interface &1 of subpackage &2 is not possible |
170 | Use access to package interface &1 of superpackage &2 is not possible |
171 | Package &2 of filter interface &1 is not directly adjacent to &3 |
172 | Use access to filter package interface &1 is not possible |
173 | Package &1 cannot be its own superpackage |
174 | Package &1 cannot be assigned as a superpackage |
175 | Package &1 cannot be edited |
176 | Package &1 is not allowed as superpackage |
177 | Package &1: creating package interfaces is not allowed |
178 | Package &3 of development object &1 &2 does not exist |
179 | &1 &2: Package hierarchy of package &3 contains errors; check package &4 |
180 | Active version of &1 &2: no development objects used |
181 | Package interface &1 is not visible; see long text |
182 | Package interface &1 contains a cyclical reference: &2 |
183 | &1 &2 produces a cyclical reference and cannot be included |
184 | Filter package interface &1 cannot be included |
185 | Virtual standard package interface &1 cannot be included |
197 | Superpackage &1 not allowed due to switches with varying assignments |
198 | Superpackage &1 not allowed due to switches with varying assignments |
199 | Superpackage &1 not allowed due to switches with varying assignments |
200 | Superpackage &1 not allowed due to switches with varying assignments |
201 | Table entry for function module &1 does not exist |
202 | Cannot write table entry for function module &1 |
203 | &1 &2 (package &3): Software component &4 must not be used here |
204 | &1 &2 (package &3): Do not use software component &4 here |
205 | Error message of package component check (SAP Note 1089479) on &1 &2 |
206 | Warning message of EhP component check (Note 1089479) from &1 &2 |
207 | Combination transport layer &1 / software component &2 not allowed |
210 | Type of previous package and type of new package are different |
211 | Enter a new package |
212 | Package interface &1 cannot be assigned to package &3 |
213 | &1 assigned as new package |
220 | Object R3TR AVAS &1 is still assigned to package &2; see long text |
221 | Object R3TR &1 &2 (&3 &4) is still assigned to package; see long text |
222 | Object R3TR &1 &2 (&3 &4) is still assigned to package; see long text |
223 | Object R3TR &1 &2 is still assigned to package &3; see long text |
224 | Object R3TR &1 &2 is still assigned to package &3; see long text |
225 | Package &2 still contains package &1 as subpackage |
300 | &1 &2: the object used (&3 &4) or object directory entry does not exist |
301 | Name of log for package check of DDIC objects is missing |
302 | Package violation (error): object &1 &2 uses &3 &4 |
303 | Object &1 &2 uses obsolete object &3 &4 |
304 | Package violation (warning): object &1 &2 uses object &3 &4 |
305 | Package violation (info): object &1 &2 uses object &3 &4 |
306 | Error message from package check for &1 &2 |
307 | Warning message from package check for &1 &2 |
308 | Information message from package check for &1 &2 |
309 | The package check did not find any errors |
310 | Package check returned warning or information messages |
311 | Package check of object &1 &2 cannot be executed at present |
312 | Object used, &1 &2, is a HOME object or a local object |
313 | The used object, &1 &2, is not visible |
314 | The used object, &1 &2, is not visible |
315 | The used object, &1 &2, is not visible |
316 | Used object from external structure package not visible |
317 | Package &1 does not have sufficient use access |
318 | Basis decoupling: Use the replacement object &1 &2 |
319 | Basis decoupling: Undesirable use without replacement object |
320 | Usage exception missing for object &1 &2 of product &3 |
321 | Object &1 &2 of product &3 cannot be used |
322 | Object &1 &2 of product &3 is frozen, but not released |
323 | Object &1 &2 of product &3 can have incompatible changes made to it |
324 | Compatibility of object &1 &2 for product &3 is still not determined |
325 | Compatibility of &1 &2 (product &3) could not be determined |
326 | Object &1 &2 for product &3 was changed incompatibly (non-critical) |
327 | Object &1 &2 for product &3 has changed incompatibly |
328 | Object &1 &2 of product &3 was already deleted |
329 | Object &1 &2 from package &3 is a HOME object or a local object |
330 | Object used, &1 &2, is a HOME object |
331 | Object &1 &2 from package &3 is a HOME object or a local object |
332 | Used object &1 &2 belongs to a superpackage and is not visible |
333 | Package &1: Use access '&4' with error severity '&2' (&3) exists |
334 | &1 &2 must no longer be used; use replacement object &3 &4 |
335 | &1 must not be used any longer; replacement: '&2&3&4' |
336 | &1: Object &2 must not be used any longer (replacement: see long text) |
337 | &1: Object &2 must not be used any longer (replacement: see long text) |
338 | &1 &2: Object &3 &4 must not be used any longer |
340 | Missing use access for usage of &3 &4 |
341 | Object used, &3 &4, is not visible |
342 | Object used, &3 &4, is a HOME object or a local object |
343 | Object used, &3 &4, belongs to a superpackage and is not visible |
344 | Do not use &1 &2 any more; use replacement object &3 &4 |
345 | Do not use &1 any more; replacement: '&2&3&4' |
346 | &1: Do not use object &2 any more; for the replacement, see the long text |
347 | &1: Do not use object &2 any more; for the replacement, see the long text |
348 | &1 &2: Do not use object &3 &4 any more |
349 | Package &1: incomplete use access for package interface &4 |
350 | Incomplete use access for using &3 &4 |
351 | SAP_GWFND component check: Invalid use of external objects |
352 | SAP_BASIS component check (forbidden use of SAP_GWFND objects) |
360 | The list of inactive packages was created successfully. |
361 | Error during save of inactive packages: execute program PAKDATBUF. |
400 | The package check for HOME package &1 is deactivated |
401 | Enterprise extension alias & is not assigned to a structure package |
402 | No authorization to maintain data |
403 | No authorization to display data |
404 | Package check is switched off |
418 | Choose a valid application component |
501 | Navigation to ABAP Dictionary object is not possible |
600 | System &1 cannot be reached |
601 | Data could not be passed to system &1 |
602 | No information available for product &1 &2 |
603 | Objects used by product &1 &2 are not yet determined |
604 | System &1 cannot be reached; this operation will be terminated |
605 | There is no active consolidation system for product &1 &2 |
606 | Process was terminated |
607 | Internal error. |
608 | Could not find a system to which the data is to be passed. |
609 | RFC connection &1 is connecting to the wrong system |
610 | Object &1 &2 does not have an object directory entry |
611 | Software component & is not assigned to a product |
612 | Interface was not yet transferred |
613 | Transferred AKB_EXCEPTIONS entries: & AKB_FREEZE: & AKB_EXCEPT_EXT: & |
614 | Start of transfer of &1 &2 entries |
615 | Start of transfer of &1 AKB_FREEZE* entries to system &2 |
616 | DISTRIBUTED flags set in AKB_EXCEPTIONS: &1 |
617 | Creating the overview table... |
618 | Product & is not a client product |
619 | &1 is not the master system of any server product |
620 | The server and client products must not be identical |
621 | Determining the environment for object &1 &2 failed |
622 | Request or task &1 does not exist |
623 | Invalid class name: &1 |
624 | Function &1 does not exist in system &2 |
625 | No compare version found for object &1 &2 |
626 | Use of multiple server products was not yet implemented |
627 | Usage exceptions were created |
628 | Usage exceptions could not be created |
629 | Function &1 cannot be reached through connection &2 |
630 | Start of transfer of & FRODIR entries into system &. |
631 | Start of transfer of & RODIR entries into system & |
632 | Delivery of system &... |
633 | Usage exceptions must only refer to a client product |
634 | Interface is currently locked by another user |
635 | Reset compatibility results: &1 |
636 | Executed compatibility checks: &1, success rate: &2/&3 |
637 | Parameter: Start & end & frscrtch & project & |
638 | System &1 can be reached. AKB Version: &2 |
639 | Calculation of usage structure is not yet completed |
640 | Exceptions were distributed (exceptions left: &1) |
641 | &1 &2 &3 &4 |
642 | Finished processing partition &1; relevant exceptions: &2 |
643 | The exception table is not partitioned |
644 | Processed packages: &1 / &2 |
645 | Object lists exist only for current statistics |
646 | No statistics data available |
647 | Object &1 &2 is already being processed by another user |
650 | There are no objects matching these selection criteria |
651 | The checks were not performed |
652 | The data was saved |
653 | You can define one master system only for each product |
654 | The server product cannot also be a client product |
655 | Invalid system name |
656 | System & specified more than once |
657 | Invalid product description |
658 | The data was not saved due to errors |
659 | Invalid product description |
660 | Invalid software component |
661 | Software component & specified more than once |
662 | Could not start the job |
663 | Choose either one system or all systems |
664 | Started job & |
665 | Could not release the object & & |
666 | Releasing for objects is not yet implemented |
667 | Missing relationship: & & -> & & |
668 | & objects selected |
669 | Consistency check shows no errors |
670 | Release status of & object(s) is insufficient |
671 | Not all objects can be included in the same request |
672 | No actions required |
673 | No usage explanations need be created |
674 | This project is currently being processed by another user |
675 | System comparison with key & unknown |
676 | No check results versioned for object &1 &2 |
677 | No project with the number & is defined |
678 | Usage structure for &1 &2 saved. State: &3 |
679 | Incorrect usage information was corrected. Save this data |
680 | &: No reference version of & & exists; consider the whole environment |
681 | Cannot display object |
682 | The selected function is not available using connection & |
683 | SPDD log with & messages was created |
690 | Job & executed |
700 | Product & & is already defined as a server product |
701 | Product & & is already defined as a product contained in & & |
702 | Invalid dependencies exist for product & & |
703 | Product & & is already defined as a client product of & & |
704 | System & already used for product & & |
705 | There can be only one active system for determining the interface |
706 | Check project & is already used for product & & |
707 | Component & & already belongs to & & |
708 | The package interface was already specified |
850 | Cyclical package structure (beginning with package &1) |
851 | Package interface &1: no object directory entry exists |
852 | Package Builder aborted |