/BOBF/COM_GEN_FRAME - Messages from message class COM_GEN_FRAME: AP-SGA
The following messages are stored in message class /BOBF/COM_GEN_FRAME: Messages from message class COM_GEN_FRAME: AP-SGA.
It is part of development package /BOBF/CONFIGURATION in software component BC-ESI-BOF. This development package consists of objects that can be grouped under "Business Object Processing Configuration".
It is part of development package /BOBF/CONFIGURATION in software component BC-ESI-BOF. This development package consists of objects that can be grouped under "Business Object Processing Configuration".
Message Nr ▲ | Message Text |
---|---|
004 | Error when instantiating &1 in &2 |
005 | Class &1 does not implement interface &2 |
006 | Package was not specified for generation |
007 | A transport request was not specified for the generation |
008 | Generation tool for &1 could not be carried out |
016 | Package was not specified for the simulation |
017 | Transport request was not specified for the simulation |
020 | Request Type: &1 |
021 | |
100 | Start generation through user &1 |
101 | Start generation through user &1 at &2 |
102 | Start generation through user &1 (with db conversion) |
103 | Start generation through user &1 at &2 (with db conversion) |
104 | Preparation for generation &1 |
105 | Preparation of local existence check &1 |
106 | Preparation of existence check via object catalog &1 |
107 | Mass activation of ABAP dictionary objects &1 |
108 | Generation request explosion &1 |
110 | Closing of generation &1 |
111 | Start deletion through user &1 |
112 | Start deletion through user &1 at &2 |
113 | Final Processing &1 |
114 | Preparation of deletion &1 |
115 | &1 is not relevant |
116 | Deletion: not relevant objects &1 |
118 | Object with request type &1 could not be determined |
120 | &1 &2 |
121 | &1 was successfully generated |
122 | Warnings occurred during generation of &1 |
123 | Errors occurred during generation of &1 |
124 | Generation was terminated as a result of a serious error in &1 |
125 | Error in object &1 &2 &3 (see activation log) |
126 | Error in object &1 &2 &3 corrected by reactivation |
127 | Error during mass activation of ABAP Dictionary Objects |
128 | Mass activation successfully completed |
129 | Warnings occurred during mass activation of ABAP dictionary objects |
130 | Could not delete &1 |
131 | &1 was deleted successfully |
132 | Warnings occurred during deletion of &1 |
133 | Errors occurred during deletion of &1 |
134 | Deletion was interrupted because of a serious error in &1 |
135 | Closing of deletion &1 |
136 | &1 must not be generated |
137 | Generation of &1 |
138 | Warning for object &1 &2 &3 |
140 | &1 is available |
141 | &1 is available actively |
142 | &1 is available inactively |
143 | &1 does not exist |
144 | Warinings occurred during check of &1 |
145 | Errors occurred during check of &1 |
146 | Check was interrupted because of a serious error in &1 |
147 | Start local/positive existence check by user &1 |
148 | Start local/negative existence check by user &1 at &2 |
149 | Closing of local existence check &1 |
151 | &1 is available globally |
152 | &1 is available locally |
153 | Start of existence check via object catalog by user &1 |
154 | Start of existence check via object catalog by user &1 at &2 |
155 | Closing of existence check via object catalog &1 |
156 | Start of local/negative existence check by user &1 |
157 | Start of local/positive existence check by user &1 at &2 |
158 | Check for &1 is not possible as package information is missing |
159 | &1 was not checked (TADIR program ID &2) |
161 | &1 was simulated successfully |
162 | Warnings occurred during simulation of &1 |
163 | Errors occurred during simulation of &1 |
164 | Simulation was interrupted as a result of a serious error in &1 |
165 | Simulation of &1 |
166 | Start of simulation by user &1 |
167 | Start of simulation by user &1 at &2 |
168 | Preparation of simulation &1 |
169 | Closing of simulation &1 |
170 | (-) &1 is not relevant for generation |
171 | (-) &1 is not relevant for deletion |
172 | (-) &1 is not relevant for simulation |
200 | Usage &1 does not exist |
201 | A request interpreter has not been configured for usage &1 |
202 | Request type &1 does not exist |
203 | Entry in COM_GEN_GTREE for request type &1 (usage &2) is missing |
204 | Processing for request type &1 (usage &2) is deactivated |
300 | Transport request &1 does not exist |
301 | Transport request &1 cannot be changed |
302 | &1 must be a transport request for workbench or Customizing |
303 | Transport request &1 belongs to user &2 |
305 | Package &1 may not contain local objects |
306 | Package &1 may only include local objects |
308 | Target system of order &1 does not match generation mode &2 |
310 | Variable &1 of generation strategy has incorrect value &2 |
311 | Interaction Mode is not allowed in Configuration Generator Mode |
400 | Impermissable change of request type &1 by request interpreter |
401 | Warnings occurred during the generation request explosion |
402 | Errors occurred during the generation request explosion |
403 | A serious error occurred during generation request explosion |
404 | |
500 | Syntax error in line &1 of template &2 |
501 | Generation request is not permissible |
502 | Status &1 of object &2 is not defined |
503 | Error during object determination (request type: &1) |
510 | &1 is inconsistent |
511 | &1 is an interface |
512 | &1 does not have a short description |
513 | &1 is not specified |
514 | Error during data retrieval for generation of &1 |
515 | Error while preparing protected areas of &1 |
516 | &1 is not a method |
517 | Generation of method &1 |
518 | Simulation of method &1 |
519 | Method &1 of class &2 was deleted |
520 | Method &1 of class &2 could not be deleted |
521 | Method &1 of class &2 is not available |
522 | Method &1 could not be deleted as the class could not be determined |
523 | Method name &1 is too short (class name might be missing) |
524 | Error during data retrieval for deletion of &1 |
527 | Index for index group &1 of table &2 was deleted |
528 | Index for index group &1 of table &2 cannot be deleted |
541 | Include &1 for function group &2 created |
542 | TOP include of function group &1 has been created |
550 | Generation of local test class include &1 |
551 | Simulation of local test class include &1 |
552 | Test class include &1 of class &2 was deleted |
553 | Test class include &1 of class &2 could not be deleted |
554 | Test class include &1 of class &2 is not available |
555 | Include &1 could not be deleted as the class could not be determined |
556 | Include &1 could not be created as the class could not be determined |
800 | Message &1(&2) was issued using unknown message type (&3) |
801 | Message &3&1(&2) was not written to the log |
802 | Messages of 'generation log' functionality (generation log) |
803 | Internal messages of 'generation log' functionality |
804 | Messages for treating level of detail in the generation log |
805 | The level of detail was increased &1 time(s) too often |
806 | The level of detail was reduced &1 time(s) too often |
807 | Messages with errors when inserting into generation log |
808 | Messages that could not be inserted into the generation log |
809 | Generation log for application '&1' |
810 | Impermissible character in ID '&1' of the generation log |
811 | Generation log has not been created because of consistency problems |
812 | Generation log was not saved |
813 | Generation log buffer has not been completeley initialized |
814 | Generation logs do not exist under description '&1' |
815 | Internal error during display of generation log |
816 | You are not authorized to display the generation log |
817 | The generation log is no longer available |
818 | The generation log does not contain any messages |
899 | Testmessage for ABAPUnit: &1, &2, &3, &4. |