PCF_REGISTRY - Predefined Fields: Registry Texts

The following messages are stored in message class PCF_REGISTRY: Predefined Fields: Registry Texts.
It is part of development package S_PCF_REGISTRY_HANDLER in software component BC-SRV-APS-EXT-FLD. This development package consists of objects that can be grouped under "Predefined Fields: PCF Node Handler".
Message Nr
Message Text
000Operation failed. Node &1 could not be locked.
001Node &1 cannot be locked for editing due to system failure.
002Node &1 is currently being edited by &2.
003Node &1 does not exist.
004Node &1 with version &2 does not exists.
005Node &1 already exists.
006Could not determine root view for node &1.
007Node &1 could not be updated. Please correct errors first.
008Technical field type &1 of field &2 is not valid.
009Technical field type &1 of field &2 requires a max length.
010Length of technical field type &1 of field &2 cannot be adapted.
011Field &1 does not start with field name prefix &2.
012Persistence content object must not be empty.
013Persistence content object &1 does not exists.
014Enhancement category of &1 must be at least #EXTENSIBLE_CHARACTER_NUMERIC
015Persistence content object &1 is not been included in table &2.
016Persistence content object &1 must be a structure.
017Node &1 does not exist.
018Primary Table &1 does not exists.
019Object &1 is not a transparent database table.
020Field name prefix must not be empty.
021Field name prefix &1 is not unique. Prefix is already in use in node &2.
022Internal error. Please report an incident on component BC-SRV-APS-EXT-FLD
023Table &1 is not client dependent.
024Node &1 requires a behaviour definition
025Behaviour definition of &1 is not managed. And therefore not supported.
026Node &1 has no alias in behaviour definition.
027Database table &1 is not persistence of behaviour definition &2.
028Enhancement category of &1 must be at least #EXTENSIBLE_ANY.
029Related CDS view &1 does not exist.
030Data Source Alias &1 is not defined in &2.
031Related CDS view &1 does not read data from database table &2.
032Transport object directory entry for node &1 already exists.
033Node &1 has no behaviour definition.
034Field name &1 is too long. Maximum length is &2 characters.
035Data Definition &1 does not exist in active version.
036Activation of node &1 failed.
037Origin &1 is invalid.
038Behaviour definition &1 must support on save validation extensions.
039Behaviour definition &1 must support on modify determination extensions.
040Node &1 has a BOPF draft. BOPF drafts are not supported.
041Generation of enhancements failed.
042Could not determine ABAP language version for package &1.
043User has no authorization for ABAP language version &1.
044Could not determine ABAP language version authorization.
045User has no authorization to create new predefined field registration.
046User has no authorization to change predefined field registration.
047User has no authorization to delete predefined field registration.
048User has no authorization to display predefined field registration.
049Field &3: Length of technial type &1 is too long. Maximum length is &2.
050Predefined field definition content could not be understood.
051Field Name Prefix &1 must not start with YY and ZZ.
052API Snapshot was created by &1 on &2. Last changed by &3 on &4.
053Predefined Fields Enabling &1 needs to be released be used by customers.
054Predefined Fields Enabling &1 has no API snapshot to ensure compatibility
055Activation only possible after change of node data.
056Content object &1: Extension with name &2 could not be generated.
057Extension with name &1 does not exist.
058CDS View &1 needs annotation &2.
059Add data source &1 to annotation &2 in CDS view &3.
060No field definitions found. Define at least one predefined field.
Privacy Policy