APB_FPM_CORE - FPM messages
The following messages are stored in message class APB_FPM_CORE: FPM messages.
It is part of development package APB_FPM_CORE in software component BC-WD-CMP-FPM. This development package consists of objects that can be grouped under "Floorplan Manager (Framework)".
It is part of development package APB_FPM_CORE in software component BC-WD-CMP-FPM. This development package consists of objects that can be grouped under "Floorplan Manager (Framework)".
Message Nr ▲ | Message Text |
---|---|
000 | ************************************************************************* |
001 | FPM EXCEPTION |
002 | ************************************************************************* |
003 | |
004 | Unknown environment; restart not possible |
005 | Restart in SAP GUI not possible |
006 | System alias required |
007 | OBN restart not possible |
020 | Variant &1 requires a main view |
021 | Variant &1 requires a subview |
022 | Variant &1 requires a UIBB |
023 | Main view &1 requires a subview |
024 | Subview &1 requires a UIBB |
025 | Content area requires a section |
026 | Content area &1 requires a section |
027 | List requires Drag-and-Drop information |
028 | Variant &1 requires a tab |
029 | Tab &1 requires a UIBB |
030 | You must have at least one variant |
031 | Variant &1 or main view &2 or main step &2 do not exist |
032 | The substep variant &1 does not exist |
033 | Substep &1 requires a UIBB |
100 | ************************************************************************* |
101 | RUNTIME EXCEPTIONS |
102 | ************************************************************************* |
103 | Component &1 does not implement a valid interface |
104 | Valid parameter for IF_FPM~RESUME_EVENT_PROCESSING are OK or FAILED |
105 | Usage groups on the floorplan component are already in use |
106 | Only 1 floorplan instance is allowed per work area |
107 | Shared data component cannot be attached; it is already instantiated |
108 | FPM event loop is not allowed to be resumed while running |
109 | Call of method is not allowed at this point in time |
110 | FPM application &1 was started with an invalid or without configuration |
111 | FPM start event was cancelled |
112 | No valid target content area found |
113 | FPM Application was terminated |
114 | No FPM event provided |
115 | Conversion error occurred |
200 | ************************************************************************* |
201 | FLOORPLAN EXCEPTIONS |
202 | ************************************************************************* |
203 | Variant &1 does not exist |
204 | Subview &1 does not exist or cannot be accessed at the moment |
205 | Changing the target subview only allowed while view-switch event |
206 | Subroadmap &1 does not exist or cannot be accessed at the moment |
207 | No variant is selected |
208 | Mainview or mainstep &1 does not exist within variant &2 |
209 | Method &1 is called with invalid parameters |
210 | The same UIBB can only be used once |
211 | At least one visible item is necessary |
212 | ID &1 already exists within the affected scope |
213 | Tab &1 is invalid |
214 | UIBB &1 was not found |
215 | Index is out of range |
216 | The configuration is, at this point in time, not changeable |
217 | Configuration &1 is corrupt |
218 | The entity with ID &1 does not exist |
219 | You can only define one wire for each UIBB instance key |
220 | Inconsistent API-Call: Existing action with different parameters |
221 | Invalid Connector Class &1 |
222 | ID for content area must be unique |
223 | Content Area has no ID |
300 | ************************************************************************* |
301 | CONFIGURATION EXCEPTIONS |
302 | ************************************************************************* |
303 | Component &1 specified as APP_SPECIFIC_CC does not implement &2 |
304 | Configuration &1 for component &2 does not exist |
305 | No variant is configured |
306 | No main view for variant &1 is configured |
307 | No subview for mainview &1 of variant &2 is configured |
308 | No UIBB is configured for subview &1 of mainview &2 of variant &3 |
309 | No ID is configured for item of main view &2 in variant &1 |
310 | UIBB &1 can only be used once |
311 | Component &1 does not implement &2 |
312 | Enter a valid component |
313 | Enter a valid component for UIBB (Window Name) &1 |
314 | Component &1 of UIBB (Window Name) &2 implements an invalid interface |
315 | Enter a valid window name for UIBB &1 |
316 | Window name &1 for component &2 does not exist |
317 | Window name &1 of component &2 can only be configured once |
318 | Configuration &1 of component &2 can only be configured once |
319 | Component &1 is not allowed within GAF for UIBB (Window Name) |
320 | Configuration name &1 does not exist |
321 | Configuration is inconsistent |
322 | Event cancelled due to inconsistent runtime state |
323 | Class &1 does not implement interface &2 |
324 | No transaction handler class has been maintained |
325 | UIBB key is not valid (Component &1, Config ID &2, Instance ID &3) |
326 | UIBB key does not provide a feeder model (component &1, config id &2) |
327 | Port is not valid |
328 | Connector class &1 does not match model namespace |
329 | Component &1 is only allowed within Confirmation Screen |
330 | Component &1 is not allowed within OIF for UIBB (Window Name) &2 |
331 | Component &1 is not allowed within Tabbed UIBB (Window Name) |
332 | Source and Target UIBB must be different |
333 | Configuration type &1 is not supported |
334 | Component &1 is not allowed within GAF for UIBB (Window Name) &2 |
335 | UIBB key (component &1 config id &2) multiple-assigned as wire target |
336 | '&1' |
337 | Selected display type is not applicable for &1 |
338 | Coordinates of window name &1 of Component &2 exceed boundaries |
339 | Overlap in window name &1 of component &2 |
340 | Only one UIBB with Height > 1 is allowed |
341 | UIBB can only have Height > 1 or Width > 1 |
342 | The same view &1 is not allowed to be rendered twice |
343 | Coordinates Row 1, Column 1 should not be empty |
344 | No UIBB on right side allowed without a UIBB on left side |
345 | No empty row allowed between two UIBBs |
346 | Only "Standard" layout type allows all UIBBs to be underneath each other |
347 | Messages for &1 &2 / &3 &4 |
348 | Window &1 of component &2 and configuration &3 requires an "Instance ID" |
349 | Component &1 does not exist |
350 | Enter a valid configuration name |
351 | Valid units for width are PX and EM; % is not a valid unit |
352 | & must contain at least one UIBB |
353 | Element & already exists in the configuration layer |
354 | Element & restored |
355 | Element renamed from &1 to &2 |
356 | & has been successfully re-set |
357 | & will be re-set |
358 | UIBB cannot refer to itself |
359 | Configuration name & exists only on customizing level |
360 | Context menu & does not exist |
361 | Context menu &1 has a row action assigned in item &2 |
362 | Access key for object &1 required (See long text) |
363 | Transient state is not allowed in conjunction with wiring |
364 | UIBB (Window Name) &1 needs stretching; set UIBB Stretching flag |
365 | UIBB (Window Name) &1 requires web-browser supporting HTML5 standard |
366 | Element & cannot be of data type Measure |
367 | Add at least one element of data type Dimension |
368 | Add at least one element of data type Measure |
369 | Axis Index cannot be greater than & |
370 | UIBB (Window Name) &1 requires installation of SAP Visual Business client |
371 | Application &1 is not valid |
372 | At least one Dimension should have Axis Index value of & |
373 | An error with configuration &1 occurred |
374 | Value &1 is invalid |
375 | Dual quickview assignment at field &1 |
376 | Invalid image field assignment &1 at field &2 |
377 | Enter a valid window name for Quickview &1 |
378 | Column &1 uses fixed values but is sorted by internal values |
379 | Column &1 uses enumeration and has display type Input Field |
380 | Column &1 is fixed and will be ignored (Fit to Table Width is active) |
381 | Column exists without Column ID |
382 | The feeder class is not notified of every selection change |
383 | Messages for &1 &2 |
384 | Styles have been adapted |
385 | New element for node &1 with semantic primary attribute in enhancement |
386 | Application &1 (3D scenario) can only be displayed using native client |
387 | & has hidden content only |
388 | Please enter percent value including sign '%' |
389 | Wire Model cannot not be resolved, since Source UIBB & belongs to a loop |
390 | Graphical Wire Editor not started due to errors in the Wire Model |
392 | Invalid Scope |
400 | ************************************************************************* |
401 | CNR EXCEPTIONS |
402 | ************************************************************************* |
500 | ************************************************************************* |
501 | IDR EXCEPTIONS |
502 | ************************************************************************* |
503 | Item ID &1 does not exist |
504 | Item &1 cannot be changed |
505 | Invalid format of path &1 |
506 | Invalid path &1 |
507 | Guided activity floorplan does not have a ticket area |
508 | Key does not exist or is marked for deletion |
509 | Application ID does not exist within the navigation object |
600 | ************************************************************************* |
601 | MESSAGE MANAGER EXCEPTIONS |
602 | ************************************************************************* |
603 | Controller reference is initial in method &1 |
604 | Message &1 is not reported with mapping to context |
605 | &1 |
606 | &1&2&3&4 |
607 | &1 &2 &3&4 |
608 | &1&2 &3&4 |
609 | &1 &2 &3 &4 |
610 | &1&2 &3 &4 |
611 | &1&2&3 &4 |
612 | &1 &2&3&4 |
613 | &1 &2&3 &4 |
700 | ************************************************************************* |
701 | GUIBB EXCEPTIONS |
702 | ************************************************************************* |
703 | Class &1 does not implement feeder interface &2 |
704 | Field catalog has no structure |
705 | The selected configuration is not a valid GUIBB configuration |
706 | An action exists already |
707 | Enter valid feeder class parameters |
708 | Selected element cannot be deleted |
709 | Feeder class &1 has no visible parameters |
710 | Feeder class data has been changed |
711 | Invalid elements have been removed |
712 | The description of the field &1 given by the feeder class is ambiguous |
713 | The field &1 has no description given by the feeder class |
714 | Action name &1 contains unallowed characters |
715 | Field properties: the special group &1 is not defined |
716 | Field properties: the field &1 is not in the feeder catalog |
717 | &2: The action &1 is not defined by the feeder class |
718 | &2: the field &1 is not in the feeder catalog |
719 | Field &1 is used multiple times as input-capable field |
720 | Field &1 is a technical field and cannot be configured |
721 | &1: Display type &2 not allowed here |
722 | &1: Separator cannot have any action assigned |
723 | &1: Button choice has only one action assigned |
724 | &1: Only button choice can have multiple actions assigned |
725 | &1: Toolbar element or a button-like element has no action assigned |
726 | Fields with no description given by the feeder class exist |
727 | Button set does not exist |
728 | Mandatory parameter &1 is not set |
730 | Enter a valid namespace |
731 | Enter a valid message context |
732 | Invalid Original Message |
733 | Invalid Alternate Message |
734 | Record already exists |
735 | Entry cannot be overridden |
736 | Enter a valid "Message Category" |
737 | Either "Role" or "Instance" field is empty: enter valid value |
738 | Enter a valid launchpad |
739 | Problem with Message Mapper Logging BADI Implementation |
740 | Enter a valid feeder class |
741 | Number of selected components exceeds number of available placeholders |
742 | Position overlap: Group &1 and label &2 |
743 | Position overlap: Group &1 and field &2 |
744 | Position overlap: Group &1 and group &2 |
745 | Position overlap: Label &1 and label &2 |
746 | Position overlap: Label &1 and field &2 |
747 | Position overlap: Label &1 and group &2 |
748 | Position overlap: Field &1 and label &2 |
749 | Position overlap: Field &1 and field &2 |
750 | Position overlap: Field &1 and group &2 |
751 | Invalid position: Label &1 - field &2 |
752 | Invalid position: &1 |
753 | Field &1: enter an action |
754 | Button no. &1 of button row &2: enter an action |
755 | Button &1: enter an action |
756 | Drop is not possible without a group line item |
757 | Button row element cannot be added to the melting group |
758 | Button row element cannot be added to the melting group element |
759 | Master column cannot be moved |
760 | Master column cannot be removed |
761 | Insertion of Tabbed UIBB inside Composite UIBB not allowed |
762 | Nesting of Composite UIBBs not allowed |
763 | Search Group has no ID; enter a Search Group ID |
764 | Search Group &1 contains no Search Criteria; add Search Criteria |
765 | Search Criteria &1 is not assigned to a Search Group; enter a Group ID |
766 | Group ID for Search Criteria &1 does not exist; enter a valid Group ID |
767 | Search Group ID &1 already exists; enter another Group ID |
768 | Search Group &1 does not have a title; enter a Group Title |
769 | More than &1 attributes is not recommended |
770 | Group field &1 is not allowed |
771 | Schema &1 is not allowed |
772 | Search Help &1 for field &2 does not have the field &3 as a column |
773 | Search Help &1 for field &2 is a collective search help; see long text. |
774 | Collective Search &1 for &2 does not have search &3 as search included |
775 | Field &1: Please select a Search Help text or deselect flag Enable Tokens |
776 | Selection mode '&1' and 'Export selected rows only' does not match |
780 | Chart Type &1 (&2) cannot be used for the selected dimensions / measures |
790 | Reference Field "&1" is invalid |
800 | Invalid class name &1 |
801 | Configurations selected: &1, configurations analyzed: &2 |
803 | No inconsistencies found |
811 | Neither the group header text nor the field reference is configured |