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