GOX_OBJECTS_GENERATE - Generation of objects
The following messages are stored in message class GOX_OBJECTS_GENERATE: Generation of objects.
It is part of development package GOX_OBJECT_GEN in software component CA-GTF-EEW-GEN. This development package consists of objects that can be grouped under "Generic Object Extension: Generation".
It is part of development package GOX_OBJECT_GEN in software component CA-GTF-EEW-GEN. This development package consists of objects that can be grouped under "Generic Object Extension: Generation".
Message Nr ▲ | Message Text |
---|---|
000 | The generated object & belongs to local Developmentclass ($TMP) |
001 | The generated object & has no entry in the table TADIR |
002 | One or more objects could not be written to request & |
003 | The entry with that key already exists in the database table & |
004 | The database table & is locked by user & |
005 | Sequence number &1 is not within allowed range |
006 | Duplicate KEY_GUID in GOX Headers (&1). |
100 | API & for DataSource generation not found |
101 | No DataSource master found in object data |
102 | No texts for DataSource found in object data |
103 | No field list for DataSource found in object data |
104 | Missing parameter & for DataSource generation |
105 | Wrong value for parameter OBJVERS (must be 'A') |
106 | Wrong value for parameter TYPE (must be 'ATTR' or 'TEXT') |
107 | Wrong value for parameter EXMETHOD (must be 'V' or 'D') |
108 | Wrong value for parameter EXMETHOD (must be 'V') |
109 | Wrong value for parameter EXSTRUCT (must be 'ROTEXTSTR1' for method 'D') |
110 | Wrong value for parameter DELTA (must be ' ', 'A' or 'E') |
111 | Inconsistent parameters - DataSource cannot be generated |
112 | Inconsistent texts - DataSource cannot be generated |
113 | Wrong value for parameter SELECTION (must be ' ' or 'X' or 'A') |
114 | Inconsistent fields - DataSource cannot be generated |
115 | Inconsistent parameters - DataSource cannot be deleted |
116 | API & for DataSource deletion not found |
117 | DataSource could not be deleted |
118 | DataSource could not be generated |
119 | *** DataSource & *** |
120 | The insert into table & could not be done |
121 | The update into table & could not be done |
122 | No template name found in object data |
123 | Dynpro structure is missing |
124 | database structure is missing |
125 | template dynpro is missing |
126 | template table control is missing |
127 | generation of view maintanance modules failed. |
128 | insert of tvdir entry was failed |
129 | Please maintain delta method 'A' for DataSource &1 manually |
130 | Change document object is &1 |
131 | Table name is &1 |
132 | Function pool not defined or wrong |
133 | Error reading log: & |
134 | Generator Function Module & is missing |
135 | Object & & could not be deleted |
136 | Object & & is used by & &. |
137 | Collective search helps must not contain more than 30 search helps. |
138 | Function group &1 still contains function modules |
139 | &1: &2&3&4 |
140 | Table & has no field &. |
141 | &1 &2 not found |
142 | Syntax error in &1 &2: &3 |
143 | View maintenance is blocked for function group &1 and screen &2 |
144 | &1 &2 can't be created with package &3 |
145 | Function module &1 couldn't be created due to syntax errors |
146 | DataSource & must be activated using transaction BWA5 |
200 | *** 200 - 299: Generator *** |
201 | Object type & is not defined |
202 | Parameter & for Object type & is not defined |
203 | Detail parameter & for Object type & is not defined |
204 | Tabstrip & does not allow further registers |
300 | *** BAdI Implementation &1 *** |
301 | the specified BAdI Implementation name "&1" is too long |
302 | BAdI Implementation name is missing |
303 | template BAdI Implementation name is missing |
304 | the template BAdI Implementation "&1" is not existing |
305 | template BAdI (&1) and new BAdI (&2) belong to different BAdI-definitions |
306 | creating of BAdI Implementation "&1" failed |
307 | deleting of existing BAdI Implementation "&1" failed |
308 | another Request (&1) was used than the given (&2) for BAdI changes |
309 | BAdI &1 was hung into Package &2 instead of the given &3 |
310 | the description of the BAdI Implementation "&1" is too long and was cut |