FPB_EXPRESS_PLANNING - Nachrichten f�r Express Planning
The following messages are stored in message class FPB_EXPRESS_PLANNING: Nachrichten f�r Express Planning.
It is part of development package FPB_EXPRESS_PLANNING in software component EP-PCT-MGR-CO. This development package consists of objects that can be grouped under "Express Planning (Framework)".
It is part of development package FPB_EXPRESS_PLANNING in software component EP-PCT-MGR-CO. This development package consists of objects that can be grouped under "Express Planning (Framework)".
Message Nr ▲ | Message Text |
---|---|
001 | There is no scenario text for scenario &1 |
002 | There is no text for this substep |
003 | There is no text for this step |
004 | No scenario has been transferred to the function module |
005 | Field DCNAME of fpb_exp_stp has not been filled |
006 | Field WDCOMP of fpb_exp_stp has not been filled |
007 | Field OBJECTTYPE of fpb_exp_stp has not been filled |
008 | The substep table has not been filled (fpb_exp_stp) |
009 | The step table has not been filled (fpb_exp_stpgrp) |
010 | No substep has been maintained for this step |
011 | The substep to which this step relates does not exist |
012 | There is no object service for this scenario |
013 | The object service to which this scenario relates does not exist |
014 | There is no step for the scenario |
015 | Step does not exist |
016 | Instance &1 for scenario &2 not found |
017 | Instance 1 for user &2 already exists |
018 | &1 new user instance(s) created |
019 | No export of personalization data without transaction data |
020 | Select at least one entry |
021 | No objects correspond to the selection criteria |
022 | For dialog text &1, no long text was found in language &2 |
023 | No instance was found for scenario &1 |
024 | Group does not exist or contains no single values |
200 | *--------Messages for authorization check-------------------------------* |
201 | You are not authorized to view the Express Planning of other users |
202 | You are not authorized to execute Express Planning |
203 | You are not authorized to create user instances |
204 | You are not authorized to check the Express Planning of other users |
300 | *--------Messages for object service----------------------------------* |
301 | Object service has not been found |
302 | Object type &1 not known |
400 | *-- Additional messages for Customizing of Express Planning ----- |
401 | It is not possible to move entry '&1' |
402 | Technical name &1 has already been used for entry &2 |
403 | It is not possible for you to add any more hierarchy levels |
404 | Data has been saved and imported again |
405 | No save necessary, as you have not made any changes |
406 | &1 &2 &3 &4 |
407 | First select an entry to be copied |
408 | Technical name already exists, correct your entry |
409 | You cannot sort the order of scenarios |
410 | Enter either an interval or a group |
411 | The entry for the interval is incomplete |
412 | An entry is required, select an entry from the list |
413 | You are not authorized to execute this transaction |
414 | Display only |
415 | The entries for reference data &1 are incomplete |
416 | You cannot show reference data &1 on the front end |
417 | You are using identical parameters for reference data &1 and &2 |
418 | Reference data &1 corresponds to planning year for year and value type |
419 | No entry allowed, cost elements are determined from personalization |
420 | No entry allowed, key figures are determined from personalization |
421 | Entry was copied using existing components |
422 | Displaying a variance presupposes the entry of two data columns |
423 | Copying of '&1' has been terminated |
424 | Step |
425 | Substep |
426 | &1 '&2' used several times. Do you want to copy the entry? |
427 | Select entry to be able to append new step or substep |
428 | Select a planning scenario (hierarchy level 1) |
429 | Entry Required |
430 | Scenario &1 was transferred from client &2 |
431 | Instance &1 for scenario &2 already exists |
432 | Scenario &1 does not exist |
433 | Instance &1 for scenario &2 has been created |
434 | Instance &1 for scenario &2 could not be saved |
435 | Editing status for '&1' automatically set in the front end |
436 | The entry selected and subordinate elements have been copied |
437 | Substep '&1' already exists in scenario '&2' |
438 | Step '&1' already exists in scenario '&2' |
439 | Search term '&1' found (&2 of &3) |
440 | Search term '&1' not found |
441 | Technical name in SAP name space. Do not begin with a number |
442 | Entry must be an even number in the range from 2 to 20 |
443 | Scenario '&1' does not yet exist in the database, save first |
444 | First select a controlling area |
445 | Missing names in language &1 have been replaced by technical names |
446 | &1 '&2' exist already, '&2' is used by reference |
447 | Order type &1 does not exist |
448 | Dialog &1 does not contain a field for data type &2 |
449 | Section '&1' already exists in scenario '&2' |
450 | Function only available for steps, substeps and sections |
451 | Function not available for this element level |
452 | First save section '&1' of context area |
453 | Enter a system alias or server address |
454 | Enter a Query / InfoCube or a Web template |
455 | Enter an InfoCube for the query in addition |
456 | Specify a role |
457 | Enter an instance |
458 | Enter a transaction code |
459 | Launchpad assigned cannot be used |
460 | There is no launchpad for the role and instance |
461 | Fill all required entry fields |
462 | Select a document by choosing 'Search' |
463 | The document could not be saved |
464 | Enter an RFC destination |
465 | Enter a BPS server address |
466 | Enter a BPS Web interface |
467 | BPS Web interface does not exist |
468 | Enter a BPS planning area |
469 | BPS planning area does not exist |
470 | Enter either a fixed value or an Express Planning variable |
471 | '&1' is not an Express Planning variable |
472 | Character '&1' is not allowed for a fixed value |
473 | BPS variables for the planning area transferred as proposal |
474 | No BPS variables were found for the selected planning area |