/PM0/ABQ_MIG_MSG - Nachrichtenklasse Migration RV-OV

The following messages are stored in message class /PM0/ABQ_MIG_MSG: Nachrichtenklasse Migration RV-OV.
It is part of development package /PM0/AB_MIGRATION in software component FS-PM. This development package consists of objects that can be grouped under "FS-PM Basic System: Migration".
Message Nr
Message Text
000BO_ID,VERSION_ID(&1) invalid for master policy: &2
001BO_ID,PARENT_ID,VERSION_ID(&1): Invalid Customizing value for &2
002BO_ID,PARENT_ID,VERSION_ID(&1) invalid for sample application: &2
003BO_ID,VERSION_ID(&1) invalid for insurable object: &2
004BO_ID,PARENT_ID,VERSION_ID(&1): Invalid Customizing values for &2 and &3
005BO_ID,PARENT_ID,VERSION_ID(&1) invalid for insurable obj. address: &2
006BO_ID,PARENT_ID,VERSION_ID(&1) invalid for insurable object address usage
007BO_ID,PARENT_ID,VERSION_ID(&1) invalid for insurable object enhancement
008BO_ID,PARENT_ID,VERSION_ID(&1) invalid for insurable obj. item assignment
009Master policy &1 to be deleted was not found
010Insurable object &1 to be deleted was not found
011Master policy number is already assigned
012Sample application data transferred but not master policy data
013Address data transferred but no insurable object data
014Enhancement data transferred but no insurable object data
015Item assignment data was transferred; INBO data was not
016Address usage data was transferred; address data was not
017Number of insurable object is already assigned in target system
018Master policy &1 was transferred more than once
019Insurable object &1 was transferred more than once
020&1 is not a valid list value for field &2 in GO-ID &3
021&1 is not a valid Customizing entry for field &2 in GO-ID &3
022Policy &1 already exists in the system
023Policy &1 has already been released
024Missing entries in table &1
025Processing terminated due to specified error; the entire block is refused
026Policy no. &1 was deleted
027Could not find key for fund number &1
028Policy status changed more than once; policy no.: &1, journal no.: &2
029Policy &1 journal no. &2 changed persistently on loading (entity &3)
030Master policy changed more than once. MP no.: &1, journal no.: &2
031Fund changed more than once. Fund no. &1, version &2
032Insurable object changed more than once. Object no.: &1, journal no.: &2
033Fund range changed more than once. Range no. &1, version &2
034Fund price changed more than once. Fund &1, quotation date &2, ER type &3
036Policy &1 with journal number &2 has been validated successfully
037&1 policies selected for processing
038INBO: &1 with journal number &2 was checked successfully
039Master policy: &1 with journal number &2 was checked successfully
040You are not permitted to execute a simulation run during migration
041Error while entering default attributes (BO-ID: &1, version: &2)
042Number range &1 interval &2 does not exist
043No external number range interval assigned for policy
044Policy number &1 is not valid
045Effective date for policy &1 not in ascending order
046&1 (BO ID: &2, PARENT_ID: &3, VERSION_ID: &4)
047&1
048Policy: &1 with journal no.: &2 already validated
049Number of cash flow end dates exceeds maximum permitted number (1)
050It is not possible to use field &1 as key for entity &2
051Template assignments were transferred but no master policy data
052BO_ID,PARENT_ID,VERSION_ID(&1) invalid for template assignment: &2
053Template &1 does not exist
054Error Accessing the In-Force Business Configurator
055Incomplete fund prices during update after migration
056Calculation bases missing during update after migration
057Error during update after migration
058You do not have authorization
059Policy &1 cannot be validated
060Policy no. &1 has been created
061Error in validation: &1 &2 &3 &4
062BO_ID &1 PARENT_ID &2 VERSION_ID &3: Field &4 has initial value
063Policy &1: Start validation of version &2
064Fill EXTOBJNR_TT and/or INSOBJNR_TT
065External number &1: INSOBJNR_TT must be filled for object category &2
066Object number &1 is outside interval for object category &2
067External number of insurable object has already been assigned
068No data transferred for insurable object
069Could not read number range data for object type &1
070Unpositioned status must be used for display only
071Cannot compare without creating a copy
072Object number &1 could not be validated for object type &2
073Entities /PM0/ALDAACCSING and /PM0/ALDAACCFSHR are not migrated
074Policy &1 is not a migrated policy
075Policy &1 has already been validated; cannot schedule BTS date
076Policy number &1 does not match BTX key &2
077BTS date &2 for policy number &1 is before last status on &3
078Could not determine (unique) higher-level for sibling &1
079&1 insurable objects selected for processing
080Validation of object &1, journal number &2, ID &3 has started
081Select a policy from the list
082Validation run with run ID &1 completed
083Policy &1: Version &2 cannot be validated
084Policy &1: Error while selecting the status to be validated
085Migration journal: Entry for policy &1, journal no. &2 is not saved
086Distribution plan &1 already exists
087Effective date for distribution plan &1 is not later than previous date
088No external number range interval assigned for distribution plan
089Distribution plan number &1 is not valid
090Distribution plan number &1 does not exist
091Distribution plan number &1 was deleted
092Distribution plan number &1 was created
093Distribution plan number &1 was not migrated
095Error during conversion of child entities of &1
096Entity &1 violates the FS-PM naming convention
097&1 is a sibling, but it was transferred as an entity
098&1 is an entity, but it was transferred as a sibling
099File &1 will be opened for conversion
100File &1 was converted to file &2
101Files in folder &1 will be converted
102Append for structure &1 is too long
103Validation of distribution plan &1 journal number &2 ID &3 has started
104Distribution plan &1 with journal number &2 was changed more than once
105Distribution plan &1 with journal number &2 was validated
106No distribution plan &1 exists
107Entity &1 violates the FS-PM naming convention
108&1 is an entity, but it was transferred as a sibling
109&1 is a sibling, but it was transferred as an entity
110One version of the policy that can be processed was already validated
111Error during conversion of child entities of &1
112Migrated object cannot &2 cannot be loaded; Migration status is &1
113Attribute BO ID of migration structure has a double assignment
114Migrated insurable object &2 has migration status &1
115Migrated insured object &2 cannot be loaded due to migration status '&1'
116Migrated master policy &2 cannot be loaded due to migration status '&1'
117Application number &1 already exists in the system
118Policy number &1 was assigned more than once
119Application number &1 was assigned more than once
120Policy &1: Versions exist that have not been successfully validated
121Policy &1: Temporary migration data was deleted from system
122No external number range interval was assigned for application
123Application number &1 is invalid
130Technical error: Entity of migration file identified without an ID
145No temporary data found for deletion
Privacy Policy