PPESCMPV - Nachrichten zu Statusanbindung f�r CMP-Varianten

The following messages are stored in message class PPESCMPV: Nachrichten zu Statusanbindung f�r CMP-Varianten.
It is part of development package CPPESCMPV in software component AP-PPE. This development package consists of objects that can be grouped under "Status of iPPE CMP Variant".
Message Nr
Message Text
500**************** Messages for Release of Change Number ***************
501Status &1 is not known
502Release of &2 is invalid: &1 has not reached a status that allows &3
503Specify an object type for the person responsible
504Could not determine a person responsible
505Select the required rows for this function
506Select one row only for this function
507There is no long text for the variant
508Release completed
509Display has been refreshed
510Workflows have been generated for the selected status objects
511Data has been saved.
512No attachments exist for the selected status object
513Status object selected without specifying person responsible
514Status object is already in the workflow
600***************** Messages for Evaluation Report **********************
601You must make an entry on the selection screen
602No status objects exist for this selection
603Selection only possible using template and single value
604Selection only possible using interval and single value
605Function not possible; status cockpit is already loaded
606Select at least one field in the workflow area
701No object type has been created for status &1 (cross-application object)
702Status &1 had an incorrect object type (cross-application object)
703Create predecessor status &1 for current status &2 first
704Status &1 must have the same parameters as predecessor &2
800************************* Connection of CMP Variants to Status
801Variants &1 must be on level &2
802Status graph &1 does not exist
803API error status &1: TOPCSID has not been filled
804API error status &1: TOPCSID cannot be changed
805&1 application object type is not allowed for status &2 for &3
810Error locking &1 against changes with &2
811&1 successfully locked against changes with &2
812Object management record &1 for change number &2 has not been closed
Privacy Policy