PSRM_SOA - Messages for Service Enterprises in PublicSectorRecordsMgnmt

The following messages are stored in message class PSRM_SOA: Messages for Service Enterprises in PublicSectorRecordsMgnmt.
It is part of development package RMPS_SOA_BASIC in software component CA-GTF-RCM. This development package consists of objects that can be grouped under "Basic Functions for Service Enabling".
Message Nr
Message Text
000& & & &
001Technical error in backend of enterprise service (&1 &2)
002Document creation failed
003Document change failed
004Document search failed
005Document read failed
006Record creation failed
007Record change failed
008Assignment of document to record failed
009Read of the record content failed
010Record reading failed
011Area ID could not be found with given SPS ID &1
012Area ID is empty
013Framework could not be started
014Check of RMS ID & failed
015Check of SPS ID & failed
016Check of document ID & failed
017Check of description & failed
018Check of properties failed
019Check of components failed
020MIME type is empty
021MIME type & does not exist in table TOADD
022Number &1 of document components is not supported
023Component info provided, but document content is empty
024RMS ID is empty
025SPS ID is empty
026Document & already exists
027Check of document context attributes for SPS ID & and RMS ID & failed
028Binary content is expected but ASCII content is supplied
029ASCII content is expected but binary content is supplied
030Components counter is initial
031Document context is initial
032Check of document context content for & & failed
033Default MIME type not maintained in table TOADD, constant &1 is used
034Component ID value does not exist
035Component number is empty
036All component information is initial
037Document ID or Document Class is empty
038SPS ID and RMS ID are empty
039Check the file content of & with the component specification &
040Record search failed
041Record read failed
042Model_SPS_ID & does not exist in backend
043ServiceObject & does not fit to SPS_ID &; check the service customising
044Document & already exists (if internal error is raised)
045Error in framework for enterprise service &
046Generation rule &1 &2 does not exist
047Rule type &1 does not match element type &2
048Element type &2 type assignment unknown (type &1 provided)
049Parameter &1 is not maintainable (see DMWB settings)
050MIME type is empty and no default specified in table TOADD
051Invalid input: both binary and ASCII content for document provided
052Invalid input: no selection criteria specified
053Invalid input: selection option &1
054Invalid input: selection sign &1
055Invalid input: property without name and value
056Generation rule check: SPS type could not be determined
057No element specified for Record Assign
058Error in requested ProxyClass
059Error in object &
060Internal error in Service &
061ClassObject & not created by RMPSE factory class
062System error: Invalid ParameterInterface &
063Not specified mapping error
064Mapping error in field &
065Mapping error of fields & and &
066Mapping error in properties
067Mapping failed for requested service
068Field & is empty
069Content of field & cannot be processed
070Field & should be initial
071An initial value was expected
072Error in requested field
073Field & should contain another format
074Format error
075Format error in field &
076Field & not type compatible
077Error in ProxyClass &
078Error in ProxyClass
079AccessPermissionTypeCode: "&" is not customized in the application
080AccessPermissionTypeCode: Maintainance of view "SCMGAUT_SECLEVL" required
081ID Generation failed. Temporary ID is &
082Document in backend does not have a Status Profile. State cannot be set.
084Document Status & is not a valid sequel
Privacy Policy