/PM0/ABJ_MSG - Nachrichtenklasse f�r das Journal
The following messages are stored in message class /PM0/ABJ_MSG: Nachrichtenklasse f�r das Journal.
It is part of development package /PM0/ABP_JOURNAL in software component FS-PM. This development package consists of objects that can be grouped under "FS-PM Basic Policy Management: Journal Management".
It is part of development package /PM0/ABP_JOURNAL in software component FS-PM. This development package consists of objects that can be grouped under "FS-PM Basic Policy Management: Journal Management".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Policy &1: No application &2 on writing of journal entry &3 |
| 002 | Error occurred in call by load_by_number: &1 &2 does not exist |
| 003 | Error in BADI CREATEAPL_BADI:&1&2&3&4 |
| 004 | Customizing entry journal is missing: Journal mgt categeory for LoB &1 |
| 005 | Customizing entry for journal missing: Service class for &2 category &1 |
| 006 | Policy &1 contract &2: Journal number &3 is not in contract journal |
| 007 | Policy &1: Journal status "&2" is not allowed in background |
| 008 | Policy &1 contract &2: Journal status "&3" is not allowed in background |
| 009 | Cannot create application for policy &1 |
| 010 | Customizing entry for journal missing: process dispatcher service class |
| 011 | Cannot load application for policy &1 |
| 012 | Illegal call get_finish_no without mr_journal |
| 013 | Entity type for BO class &1 is unknown |
| 014 | Customizing entry processing ID is missing: &1 |
| 015 | Policy &1 contract &2: Journal number &3 is not in contract journal |
| 016 | Business object element is blank or zero |
| 017 | IR_BOEC is not top object |
| 018 | No journal entry for contract &1 for changed entities &2 |
| 019 | No journal entry for policy for changed entities &1 |
| 020 | No matching journal entry was found for contract &1 |
| 021 | Journal entry for policy is incorrect |
| 022 | No matching journal entry was found for contract &1 |
| 023 | An incorrect journal entry has been written for the policy |
| 024 | No contract &2 was found for journal entry &1 |
| 025 | No policy was found for journal entry &1 |
| 026 | Another journal business object already exists for journal number &1 |
| 027 | Business process mode &1 is not recognized in journal |
| 028 | Processing &1 is not defined |
| 029 | "Commit" cannot be executed without a previous "Finish" |
| 030 | Policy &1: No contract ID was transferred on creation of journal |
| 031 | Policy &1: No application ID was transferred on creation of journal |
| 032 | Another journal business object already exists for action number &1 |
| 033 | An unsaved business object or journal object exists |
| 034 | IR_BOEC is not a top object |
| 035 | Persist access and IF_ONLY_BO_DATA = ABAP_TRUE are not allowed |
| 036 | Entities: &1 was changed since last 'Finish' |
| 037 | Current journal object is an application journal |
| 038 | Application journal or change option journal was not yet created |
| 039 | An entry exists in the journal |
| 040 | An unsaved business object or journal object exists |
| 041 | Business process mode &1 is not recognized in journal |
| 042 | Optional parameter must be filled for key assignment of a policy |
| 043 | Not possible to load appropriate data record |
| 044 | Policy is no longer valid; Application cannot be created |
| 045 | No contract journal exists for policy &1 |
| 046 | Permitted reactivation is already maintained for ppd_id &1 |
| 047 | Specify at least one permitted reactivation for a journal entity |
| 048 | Multiple records (&1), or none, found; A single record was expected |
| 049 | No reactivation type was found for ppd_id &1 |
| 050 | Permitted reactivation is already maintained for ppd_id &1 |
| 051 | Reactivation type is already maintained for ppd_id &1 |
| 052 | Maximum policy product journal number is zero |
| 053 | Transaction not permitted |
| 054 | Reactivation type &1 is unknown |
| 055 | Error during database access to table &1; sy-subrc = &2 |
| 056 | Error during call of load; iv_secpol_id is empty |
| 057 | Error during call of load; application_id &1 is not in applic.journal |
| 058 | Error on call of load_from_bulk; No journal number was transferred |
| 059 | Load_by_Entry: Application &1 is not yet saved |
| 060 | Load_by_Entry: Change option &1 is not yet saved |
| 061 | An open master data record was found |
| 062 | No application data record &1 was found |
| 063 | Change option data record not found |
| 064 | Incorrect predec.($2)-successor relationship (&1) for entity &3 in ctr &4 |
| 065 | Last data record of entity &1 has value &2 as the termination journal no. |
| 066 | Journal management entity type &1 is not known to pos-data-object |
| 067 | Method &1 is not allowed if parameter IF_ONLY_BO_DATA is set |
| 068 | You cannot select technical journal &1 as a journal number |
| 069 | Technical journal no. is already filled for contract &1; Value: &2 |
| 070 | Applic. creation is not possible on &1 due to dependent journal entries |
| 071 | JournalNoM is already filled for contract &1; Value: &2 |
| 072 | Several transfer-relevant journal numbers found as versions |
| 073 | Journal management entity type &1 is unknown to entity &2 |
| 074 | Contract number &1 is currently being processed by user &2 |
| 076 | No suitable journal entry was found for policy &1 |
| 077 | No application journal number has been entered for contract &1 |
| 078 | Reactivation type &1 is unknown |
| 079 | Error in copy service P2A, entity &1 |
| 080 | Journal management entity type &1 is not known to pos-data-object |
| 082 | No journal entry was found for technical journal number |
| 084 | Use process dispatcher for method &1 |
| 085 | Technical process not allowed for the policy |
| 086 | No journal entry with tech. processing category required for contract &1 |
| 087 | Contract &1 has already been run as scheduled; Reactivation not possible |
| 088 | Technical and legal process; Valid-From/To and Legal-From is required |
| 089 | Legal process; Legal-From Is required |
| 090 | Multiple journal entries were written for a contract |
| 091 | Technical process: Legal-From is not specified |
| 092 | Technical process, Valid-From/To is required |
| 093 | Policy retired on processing date &1 |
| 094 | No contract found with ID &1 |
| 095 | Contract &1 does not exist in BO |
| 096 | No key has been assigned to object &1 |
| 097 | Entity &1: Inadequate legal journal entry for contract &2 |
| 098 | Entity &1: Inadequate technical journal entry for contract &2 |
| 099 | Journal entries of processing category MASTER is not allowed; Contract &1 |
| 100 | Record is dispatched with journal no. &1 => Update is not allowed |
| 101 | Journal entry with processing category 'Other' for ctr &1 not possible |
| 102 | Record was not found in internal memory for table &1 |
| 103 | Release application not possible for amendment option |
| 104 | "Calculated" journal entry was not set for contract &1 |
| 105 | Illegal journal entries exist for contract &1 |
| 106 | Invalid transaction journal entry for contract &1 |
| 107 | Write-entry method was not transferred to top object as ir_boec |
| 108 | is_ppd_changed method was not transferred to top object as ir_boec |
| 109 | Cannot find contract &1 |
| 110 | Effective date &1 is before policy start date &2 |
| 111 | Policy &1 does not exist in contract journal |
| 112 | Cannot insert journal data for contract &1 |
| 113 | Unable to insert required data record in table &1 |
| 114 | Event &2 is not allowed for status &3 in table &1 |
| 115 | Processing category 'OTHERS' is not allowed in Change business process |
| 116 | Multiple technical journal entries were written for contract/policy &1 |
| 118 | Status &2 is not possible; Policy already has the status &1 |
| 119 | Journal number &2 has already been assigned to transaction entity &1 |
| 120 | Table: &1; Required data record does not exist on the database |
| 121 | No policy with policy ID &1 exists in contract journal |
| 123 | Policy is reversed on knowledge date &1 |
| 124 | Processing &1 with processing category &2 cannot be reset |
| 125 | Unable to continue from last technical processing &1 |
| 127 | Persistent attributes &1 of entity(ies) &2 were changed when loaded |
| 128 | Unable to delete journal entry from work area |
| 129 | Error locating technical journal numbers for selection |
| 130 | Journal entry structure does not contain component &1 |
| 131 | Journal status "&1" does not match application |
| 132 | Journal status "&1" does not match change option |
| 133 | Journal exists - save first |
| 134 | Unable to load application in access mode &1 due to journal status |
| 135 | Initialization of class /PM0/cl_ABJ_REGISTRY failed |
| 136 | BP class for bizprc_id &1 not found |
| 137 | legalvfrom &1 of last legal j. entry greater than current j. entry (&2) |
| 138 | Interval end date &1 is before effective start date &2 |
| 139 | Effective date &1 must not be earlier than the previous &2 |
| 140 | Other transaction: valid-from/to and legalvfrom required |
| 141 | Unable to determine processing class for category &1 |
| 142 | Unable to reverse journal entry &1 because it does not exist |
| 143 | Unable to reverse journal entry &1 as it has already been reversed |
| 144 | Journal entries already exist for appl. &1, recreation not possible |
| 145 | Contract: &1; Combination search jrnl no.&2,srch jrnl no.&3 not allowed |
| 146 | Cannot find policy for effective date &1 |
| 147 | Contract &1: Selectable entries were found |
| 148 | Application ID &1 in table &2 not unique |
| 149 | Not possible to write journal entries due to journal status |
| 150 | Journal status is "&1"; Application must have journal status "released" |
| 151 | Eff.date &1 and legally valid from &2 of journal entry must be identical |
| 152 | validfrom_dt &1 and intbegin_dt &2 and intend_dt &3 must be identical |
| 153 | Journal entry not found in application journal |
| 154 | Journal entry not found in amendment option journal |
| 155 | valid_from_dt of journal entry &1 is earlier than existing entry &2 |
| 156 | validfrom_dt &1, intbegin_dt &2 or intend_dt &3 must be identical |
| 157 | Change category and fine control value are less than existing entry |
| 158 | Polciy Product/Policy have differing technical effective date |
| 159 | No valid technical journal entry exists for effective date |
| 160 | Finish with journal number 0 not permitted |
| 161 | Unable to load inactive policy |
| 162 | Journal status is "&1"; Application must have journal status "&2" |
| 163 | Double journal entry for policy issuance |
| 164 | Not possible to write journal entries due to journal status |
| 165 | Policy must be reactivated. Technical &1. Legal &2 |
| 166 | Error while determining financial period |
| 167 | Additional information is missing for processing &1 |
| 168 | You can only reverse a claim/benefit case in the Reset business process |
| 169 | Missing authorization for maintaining financial periods |
| 170 | Missing date input |
| 171 | Date input not ascending |
| 172 | Financial periods assigned with overlaps |
| 173 | Open financial periods still exist |
| 174 | Successive closed financial periods exist |
| 175 | Application ID not found in application journal |
| 176 | No policy status available for effective date |
| 177 | Date is earlier than / same as &1; financial accounting period is closed |
| 178 | No permitted financial period has been defined |
| 179 | Unable to determine balance sheet effective date |
| 180 | Error when calling load_for_migration: &1 &2 does not exist |
| 181 | Only possible to reverse benefit case using the appropriate BTrans |
| 182 | No suitable journal entry was found for policy &1 |
| 183 | Error when accessing table &1 or &2, sy-subrc=&3 |
| 184 | Journal entry not found in contract journal |
| 185 | No journal entry was included for at least one contract |
| 186 | Appl.-persistent transaction: Valid from/to and Legal from/to required |
| 187 | updatetype_id for journal entry &1 is less than existing entry &2 |
| 188 | finectrl_id for journal entry &1 is less than existing entry &2 |
| 189 | Contract data record not found |
| 190 | Application data record not found |
| 192 | Premium payer to be changed by BADI "/PM0/ABJ_CREATEAPL_BADI" not found |
| 193 | Addit. deposit to be changed by BADI /PM0/ABJ_CREATEAPL_BADI not found |
| 194 | Representative to be changed not found by BADI "/PM0/ABJ_CREATEAPL_BADI" |
| 195 | PH to be changed not found by BADI "/PM0/ABJ_CREATEAPL_BADI" |
| 196 | 3rd-party rights to change not found by BADI "/PM0/ABJ_CREATEAPL_BADI" |
| 197 | Right to benefits to change not found by BADI "/PM0/ABJ_CREATEAPL_BADI" |
| 198 | Policy loan payer to change not found for BAdI '/PM0/ABJ_CREATEAPL_BADI' |
| 199 | Address ins. obj. to change not found by BADI "/PM0/ABJ_CREATEAPL_BADI" |
| 200 | Interest payer to be changed not found by BADI "/PM0/ABJ_CREATEAPL_BADI" |
| 201 | Policy loan rec. to change not found for BAdI '/PM0/ABJ_CREATEAPL_BADI' |
| 202 | BO changed by BADI "/PM0/ABJ_CREATEAPL_BADI", journal entry is obligatory |
| 203 | &1: Policy has unreleased versions; release all versions |
| 204 | Loading cancelled |
| 205 | Incorrect status assignment; old: &1 new: &2 |
| 206 | Postdated application &1 cannot be removed until &2 at the earliest |
| 207 | Journal (&1) must not be saved with access mode &2 |
| 208 | Contract &2 of policy &1 is currently being processed by user &3 |
| 209 | You can currently not create any new contract for policy &1 |
| 210 | At least 1 contract for policy &1 is currently being edited by user &2 |
| 211 | Processing of applic. &1 (policy &2 contract &3) was interrupted by &4 |
| 212 | Contract &1/&2 is already being edited by &4 in business process &3 |
| 213 | A postdating date exists for &1; remove it as per &2 |
| 214 | &1&2&3&4 |
| 215 | At least one contract for policy &1 is currently being created by user &2 |
| 216 | Policy &1: Temporary migration data has not yet been deleted |
| 217 | It is not possible to make an inquiry on this requested status |
| 218 | Selection criterion "Release date" is before the new business |
| 219 | Selection criterion "Application Receipt Date" is before new business |
| 220 | Archived log entries exist for policy &1 |
| 221 | You have selected the release date but not specified any date |
| 222 | You have selected the application receipt date but not given any date |
| 223 | Method &1 is not possible in background processing |
| 224 | Policy &1: Contract &2 cannot be loaded on &3 |
| 225 | Effective date &1 is before migration of &2 |
| 226 | No policy version available on &1 |
| 227 | No contract version available on &1 |
| 228 | BO ID &1 still exists; no reloading is posssible |
| 229 | &1/&2: No journal entry for start date shift exists |
| 230 | &1: You are not permitted to edit a status intended for inquiry |
| 231 | Commission at policy level: &1 New contract after &2 is not allowed |
| 232 | Commission at policy level: &1 Reversed contract after &2 is not allowed |
| 233 | Policy processing: &3 &4 cannot be processed; &1 &2 incorrect |
| 234 | Reactivation is not possible before creation of contract package |
| 235 | Current policy version is intended for display only |
| 236 | No policy version was found on &2 for policy &1 |
| 237 | No journal entries exist for policy &1 contract &2 |
| 239 | &1/&2 journal entries with different lines of business for same contract |
| 240 | JOURNALBO_ID &1 already exists; Overwriting with &2 is not allowed |
| 241 | The transferred application reference is a change option &1->&2 |
| 242 | The transferred change option reference is an application |
| 243 | Change option has journal status &1; Transfer is not possible |
| 244 | Change option does not belong to transferred application |
| 245 | Unknown &1 &2 transferred to method &3 in class &4 |
| 246 | Persistent access is not allowed for method &1 |
| 247 | Change option is not supported for method &1 in class &2 |
| 248 | Loading is not possible with a journal entry of <Action> type |
| 249 | Policy mode is not set in policy context |
| 250 | Parameter &1 does not match parameter &2 in class &3 method &4 |
| 251 | Only one entry is allowed in &1 in the dialog in class &2 method &3 |
| 252 | No applic.attribs for BO_ID &1 and application &2 in class &3 method &4 |
| 253 | &1/&2: No entry in contract journal for journal number &3 |
| 254 | &1/&2: No contract data found while writing journal entry |
| 255 | &1 is not possible in the background update |
| 256 | Contracts reversed before &1 will not be loaded |
| 257 | Application must not be released |
| 258 | Application cannot be loaded without active or reversed contracts |
| 259 | &1: Data is incorrect without policy context and contract journal |
| 260 | No policy context found for &1, thus you should only refuse application |
| 261 | No contract-relevant journal entry &1 allowed before policy issuance |
| 262 | Application &1 cannot be refused; journal status is "&2" |
| 263 | Applications processed in dialog mode cannot be loaded in batch mode |
| 264 | Pol. &1 journal status change from '&2' to '&3' for appl. &4 not allowed |
| 270 | Enter a valid application number between &1 and &2 |
| 271 | No external numbers permitted for interval from &1 to &2 |
| 272 | The application number &1 is already assigned |
| 273 | Class &3 method &4: BO_ID &1 and GUID &2 is not a valid key |
| 300 | No more changes are possible for this application; &1->&2 |
| 499 | Application is postdated |
| 500 | Postdated application cannot be resolved until &1 at the earliest |
| 501 | Error in BADI implementation /PM0/ABJ_CREATEAPL_BADI |
| 502 | Application keys from change option were not found |
| 503 | Status of contract &1 of policy &2 was not found in journal |
| 504 | Policy only contains reversed contracts |
| 801 | Serious internal error |
| 802 | Internal error |
| 803 | &1 / &2 is already in process; new persistent application is not possible |
| 804 | Call of LOAD_BY_ENTRY with different applications |