HRPAY99RU_RMS_DB - RMS DB: Messages for RMS persistence layer

The following messages are stored in message class HRPAY99RU_RMS_DB: RMS DB: Messages for RMS persistence layer.
It is part of development package P99RU_RMS_DB_L2 in software component PY-RU. This development package consists of objects that can be grouped under "RMS Database and persistence API".
Message Nr
Message Text
000Internal error: &1 &2 &3 &4
001Display of object with type &1 for employer &2 in area &3 restricted
002Creation of object with type &1 for employer &2 in area &3 restricted
003Modification of object with type &1 for employer &2 in area &3 restricted
004Finalization of object with type &1 for employer &2 in area &3 restricted
005Deletion of object with type &1 for employer &2 in area &3 restricted
006Display of object with type &1 in area &2 restricted
007Creation of object with type &1 in area &2 restricted
008Modification of object with type &1 in area &2 restricted
009Finalization of object with type &1 in area &2 restricted
010Deletion of object with type &1 in area &2 restricted
011List of employees for report &1 in area &2 restricted
012List of employees for report &1 in area &2 for employer &3 restricted
013Missing authorization to read RMS content for personnel assignment &1
020* Internal date/time format conversion
021Parameter &1 must not be initial
022Parameter &1 has invalid value &2
023Postcondition violated
024Precondition violated
025Program condition violated
026Current state of program is not expected
030* XML request processing
031XML request processing terminated with status &1
032XML request format violated
033There are parsing errors during processing of XML request
040* XML serialization/deserialization
041Unknown error during XML serialization
042Internal error during XML serialization for object &1
043Attribute &1 is mandatory for figure &2 in object &3
044Element &1 not specified for figure &2 in object &3
045Element &1 not allowed for figure &2 in object &3
046Value &1 for element &2 in figure &3 is not expected for object &4
047Element &1 is not expected in XML request
050* Locking messages
051System failure during locking operation
052Object &1 is locked by user &2
053Link from &1 to object &2 is locked by &3
060* RMS Document messages
061Record for document with key &1 does not contain database key
062Document with key &1 referenced by reports and cannot be deleted
063Document with key &1 does not exist in report &2
070* Messages for figure processing in RMS records
071Figure &1, &2 does not exist in record &3
072Figure &1, &2 in record &3 already exists
073Figure &1, &2 in record &3 must have currency
074Figure &1, &2 in record &3 contains wrong unit of measurement
075Figure &1, &2 in record &3 must have unit of measurement
076Figure &1, &2 in record &3 must have only one value
077UOM of figure &1, &2 in record &3 cannot change
078Value &1 for figure &2, &3 in record with key &4 invalid
079Figure &1, &2 in record &3 has unknown datatype
080Figure with name &1 is not permitted for record &2
081Figure name in record &1 cannot be empty
082Figure &1, &2 cannot be used as record key for object &3
090* RMS object access error
091Parameter &1 is initial
092Record &1 cannot be changed; data in future exists
093Invalid value &2 for parameter &1
094Object with key &1 managed by &2 cannot be changed using this instance
095Program condition violated; internal program error
096Postcondition violated; internal program error
097Precondition violated; internal program error
098Current state of object with key &1 is not expected
099Object with key &1 not managed by required class agent
100Object with key &1 is finalized and cannot be changed
101Parameter &1 with value &2 in object &3 is not allowed
102Parameter &1 must have value in object business key
103Object with key &1 is to be created, but exists in database
104Object with key &1 is to be read, but not found
105Record &1 already edited with different in-period date &2
120* ABAP OS wrapping messages
121Object with key &1 not found in database
122ABAP OS reported system error: &1&2&3&4
123Internal check agent reported an error during update process
124ABAP OS Query error: &1&2&3&4
125No entries matching the conditions of the query were found
126Internal error: &1&2&3&4
127ABAP OS transaction started at &1 &2
128ABAP OS transaction completed at &1 &2
129ABAP OS transaction rolled back at &1 &2
130Operation with RMS interface completed with status &1
140
141RMS record &1 must be written only since its for-period end date
Privacy Policy