APPLG - Application Graphics Messages (Graphic Proxy Framework)
The following messages are stored in message class APPLG: Application Graphics Messages (Graphic Proxy Framework).
It is part of development package SGRB in software component BC-FES-GRA. This development package consists of objects that can be grouped under "ABAP Graphic Proxies".
It is part of development package SGRB in software component BC-FES-GRA. This development package consists of objects that can be grouped under "ABAP Graphic Proxies".
Message Nr ▲ | Message Text |
|---|---|
| 000 | *** Data container messages 001-198 (begin with DC_) |
| 001 | DC: Data element (attribute) is unknown; correct the accessor method |
| 002 | DC: GP handle is initial; check list of GPs for DC |
| 003 | DC: Attribute already exists; check the accessor method for DC |
| 004 | DC: GP is not authorized to access this data |
| 005 | DC: Master cannot be assigned to DC; DC already has a master |
| 006 | DC: Class selected does not support this method; choose appropriate class |
| 007 | DC: The GET method returns a set of values (it is not unique) |
| 008 | DC: Attribute with this key already exists in DC; change application |
| 009 | DC: No key value was specified for the new data record; check call method |
| 010 | DC: Data record does not exist; check the call method |
| 011 | DC: Data records selected as deleted could not be removed |
| 012 | DC: Data container is out of date; processing is terminated |
| 013 | DC: Graphics proxy is already registered; call NOTIFY with READ. |
| 014 | DC: Internal table operation not executed; tell system administrator |
| 015 | DC: DC contains inconsistent data; tell system administrator |
| 016 | DC: Only one GP is allowed to change data per distribution cycle |
| 199 | && End of the data container messages |
| 200 | ***Graphics proxy messages from 201-398 (beginning with GP_) |
| 201 | GP: There is no proxy control to set the character range |
| 202 | GP: DC is empty or does not exist; check call method |
| 203 | GP: Parameter is unknown; correct call method |
| 204 | GP: Function module call returned an error; check call method |
| 205 | GP: GP does not have a connection to DC; check call method |
| 206 | GP: Implementation of function missing; notify person responsible |
| 208 | GP: Object ID registered by graphic unknown; check GP product interface |
| 209 | GP: Unknown graphics product; check GP's call method |
| 210 | GP: GP did not recognize event; check GP implementation |
| 211 | GP: Graphics control could not be created; check method call |
| 212 | GP: Error during data transfer to the graphic; check GP implementation |
| 213 | GP: Data for the graphic could not be formatted; check GP implementation |
| 214 | GP: The front end's window system could not be determined |
| 215 | GP: Required graphics product cannot be run on this GUI |
| 216 | GP: No free WIN ID found; check WIN ID in GP |
| 217 | GP: No multiplexer is specified; check call method in GP |
| 218 | GP: Event could not be registered; check GP's prod.-spec. event numbers |
| 219 | GP: Event could not be deregistered; check call method |
| 220 | GP: Event table could not be read; see long text |
| 221 | GP: Graphics product does not support required function; see long text |
| 222 | GP: Customizing parameter could not be set; see long text |
| 223 | GP: (Shell) event cannot be processed; see long text |
| 224 | GP: Graphics product has no technical name; check product management |
| 225 | GP: Graphics product not available in this system; see long text |
| 226 | GP: There is no reference for the current graphics product |
| 227 | GP: No connection betw. GP and Control Framework; check programming of GP |
| 228 | GP: Method can only be executed for control graphics; contact sys.admin. |
| 229 | GP: Control Framework returned an error; contact system administrator |
| 230 | GP: Name of an attribute in DC is missing; contact system administrator |
| 231 | GP: Names of the attributes in data container could not be changed |
| 232 | GP: Graphics proxy must be active for events to be sent |
| 233 | GP: Attribute bundle is not permitted for this graphics proxy |
| 234 | GP: Attribute bundle cannot be set at the port more than once |
| 235 | GP: Specifications missing for placing graphic in the screen |
| 236 | GP: 3-D data is (not) yet supported |
| 237 | GP: Method is not supported by the class selected |
| 238 | GP: There is no data source (name in DC) for this column of the tree |
| 239 | GP: Customizing bundle not available; not previously assigned to GP |
| 240 | GP: RFC-link to graphics server does not exist - see long text! |
| 241 | GP: Exporting the bitmap to the application server failed |
| 242 | GP: Graphics proxy cannot be used as main proxy |
| 243 | GP: Graphics proxy cannot be used as subproxy |
| 399 | && End of the graphics proxy messages |
| 400 | *** MUX messages from 400 (beginning with MUX) |
| 401 | MUX: Win ID already exists; check GP's call method |
| 402 | MUX: Graphics proxy already registered |
| 403 | MUX: There is no multiplexer to process the graphics event |
| 404 | MUX: Graphics proxy could not be created or destroyed |
| 405 | MUX: Specified synchronization job does not exist |
| 406 | MUX: Key for synchronization job already exists |
| 407 | MUX: Key for synchronization job is incomplete; check call method |
| 408 | MUX: Graphics proxy sending the event is unknown |
| 409 | MUX: Slave proxy already exists in the synchronization job |
| 410 | MUX: Graphics proxy supplied as parameter in method call is unknown |
| 500 | Event-specific message |
| 501 | Dataset: &1 Data group: &2 |
| 600 | *** Customizing object messages from 600 (beginning with CU) |
| 601 | CU: Error in customizing; not all customizing attributes are supported |
| 602 | CU: You cannot maintain values for merged objects |
| 603 | CU: You cannot maintain the reference object for individual attributes |
| 604 | CU: No customizing object exists with merged attribute & |
| 605 | CU: Merged attribute & does not exist |
| 606 | CU: Combination & - & does not exist |
| 607 | CU: Attribute not available for this attribute bundle |
| 608 | CU: User does not have administrative rights |
| 609 | CU: Value entered lies outside the value range |
| 610 | CU: Error occurred on entering changes in transport order |
| 611 | CU: Values cannot be copied; source and target must belong to same class |
| 612 | CU: User canceled transport request dialog |
| 700 | *** Product management messages from 700 (beginning with PROD) |
| 701 | Product management not maintained; check product management for controls |
| 750 | DCW: A file could not be written |
| 751 | DCW: DDIC-structure could not be analyzed |
| 752 | DCW: Entry parameters are incorrect; see long text |
| 753 | DCW: Name of a DDIC-Element is too long; make this element shorter |
| 754 | DCW: Template class could not be read; make sure template class exists |
| 755 | DCW: Class already exists; choose another class or specify overwrite |
| 756 | DCW: Global class could not be deleted; choose another name for class |
| 757 | DCW: Global class could not be created; see long text |
| 758 | DCW: Source for new global class could not be created; see long text |
| 759 | DCW: Line of source code is too long; choose shorter name and regenerate |
| 800 | *** Start: General GFW errors |
| 801 | Error occurred; carry out debugging |
| 802 | An object could not be generated; close some applications to free memory |
| 803 | Error occurred outside the core of the GFW; see long text |
| 850 | *** IGS CCMS messages |
| 851 | Data volume in (min) |
| 852 | Data volume in (max) |
| 853 | Data volume in (avg) |
| 854 | Calls |
| 855 | Data volume out (min) |
| 856 | Data volume out (max) |
| 857 | Data volume out (avg) |
| 858 | Duration (min) |
| 859 | Duration (max) |
| 860 | Duration (avg) |
| 861 | Uptime |
| 862 | No connection to IGS |
| 863 | Connected to IGS |
| 864 | Status of connection between CCMS and IGS |
| 865 | &1 sec |
| 866 | You are not authorized to perform this operation |
| 867 | No connection to IGS (&1&2&3&4) |