CMS_MOV - Message Class for Movables

The following messages are stored in message class CMS_MOV: Message Class for Movables.
It is part of development package CMS_OMS_MOV in software component FS-CMS-MD-MOV. This development package consists of objects that can be grouped under "Object Systems for Collateral Management: Movables".
Message Nr
Message Text
001&1 Primary key GUID not found
002Collateral object type &1 is not defined
003Collateral object &1&2 already exists; specify a unique identifier
004Collateral object category &1 type &2 Id &3 already locked
005Entity locked for editing by user &1
006Cannot create objects;number range interval &1 not defined for object &2
007Interval &1 is not internal; select an internal number range interval
008Number range object &1 not defined; contact your system administrator
009Cannot create any further objects; contact your system administrator
010Internal error occurred while saving objects; contact your system admin
011Assigned numbers are being exhausted; contact your system administrator
012No collateral object found for the given criteria
013Object with ID &1 type &2 saved
014Enter the unit price currency for collateral object &1&2
015Enter the determined price currency for collateral object &1&2
016Enter measurement unit for max take-off weight for collateral object &1&2
017Enter measurement unit for permissible weight for collateral object &1&2
018Enter measurement unit for inventory quantity of collateral object &1&2
019Date of last rate fixing for &1&2 must be before the current date
020Cannot create object; number range assignment is missing
021Collateral object cannot be set to inactive; active change request exist
022Cannot set to inactive; active change request exists
023Cannot start liquidation; active change request exists
024Cannot complete liquidation; active change request exists
025Priority field cannot be an initial or left empty
026Priority for vehicle types should be unique
027Priority for devices types should be unique
028Priority for aircraft types should be unique
029Priority for inventory types should be unique
030Priority for other valuable types should be unique
031Priority for bundle types should be unique
Privacy Policy