/PM0/ABB_INTERFACE - Nachrichtenklasse f�r Schnittstellen
The following messages are stored in message class /PM0/ABB_INTERFACE: Nachrichtenklasse f�r Schnittstellen.
It is part of development package /PM0/ABT_CROSS in software component FS-PM. This development package consists of objects that can be grouped under "FS-PM Basis Integration: General Objects".
It is part of development package /PM0/ABT_CROSS in software component FS-PM. This development package consists of objects that can be grouped under "FS-PM Basis Integration: General Objects".
Message Nr ▲ | Message Text |
|---|---|
| 000 | *******Factory |
| 001 | No valid line of business was transferred |
| 002 | No valid line of business name was transferred |
| 003 | No impl. class available for interface &1 and line of business &2 |
| 004 | Category conflict between interface and implementing class |
| 005 | No interface reference was transferred |
| 006 | Error while reading the customizing tables in the interface factory |
| 007 | Error while determining online/offline strategy |
| 008 | Attempt made to write a null entry to the status table |
| 009 | No group dimension maintained for integration subject &1 |
| 010 | Error accessing Customizing table &1 |
| 011 | Interface adapter &1 is customized with fixed values |
| 012 | The password you entered is incorrect |
| 013 | Invalid fixed values in Customizing of interface adapter &1 |
| 014 | Invalid status &1 fo interface adapter &2 |
| 015 | Invalid status for interface adapter &1 |
| 027 | Error while calling remote system: Destination &1 |
| 030 | Log start: &1 &2 |
| 031 | End of log: &1&2 |
| 090 | *******BAPI Return |
| 091 | &1&2&3&4 |
| 092 | &1&2&3 &4 |
| 093 | &1&2 &3&4 |
| 094 | &1&2 &3 &4 |
| 095 | &1 &2&3&4 |
| 096 | &1 &2&3 &4 |
| 097 | &1 &2 &3&4 |
| 098 | &1 &2 &3 &4 |
| 099 | *******BP Interface |
| 100 | FS-BP: Switch to partner system not possible |
| 101 | FS-BP: Choose valid address |
| 102 | FS-BP: Description of bank details data not available |
| 103 | FS-BP: Description of payment card data not available |
| 104 | FS-BP: Card number for payment card not available |
| 105 | FS-BP: Error during data selection (open SQL error) |
| 106 | FS-BP: Local strategy for partner system not available |
| 107 | FS-BP: Local strategy for partner system is not implemented |
| 108 | FS-BP: Role category &1 is not a valid FS-PM role |
| 109 | FS-BP: Too many roles in selection conditions |
| 110 | FS-BP: Date of death &1 lies before date of birth &3 for partner &2 |
| 111 | FS-BP: Error while calling remote system |
| 112 | FS-BP: Change "Valid from" for address for business partner &1 |
| 113 | FS-BP: Change "Valid to" for address for business partner &1 |
| 114 | FS-BP: Change "Valid from" for bank details for business partner &1 |
| 115 | FS-BP: Change "Valid to" for bank details for business partner &1 |
| 116 | FS-BP: Error when adding a business partner role |
| 117 | FS-BP: Business Partner &1 is currently being processed by &2 |
| 118 | FS-BP: Invalid entry for the birth year |
| 119 | FS-BP: Invalid entry for month of birth |
| 120 | FS-BP: Invalid entry for birthday |
| 121 | FS-BP: Business partner &1 is currently locked |
| 122 | FS-BP: Business partner &1 does not exist |
| 123 | FS-BP: Enter a unique identification number |
| 124 | FS-BP: Enter a unique business partner number |
| 125 | FS-BP: Business partner &1 is blocked; See long text |
| 126 | FS-BP: &2 &1 is blocked; See long text |
| 127 | FS-BP: Enter a unique recipient number |
| 149 | *******Partner - role assignment |
| 150 | FS-BP: Leave this window with the OK button |
| 151 | FS-BP: No BP roles available for business partner &1 |
| 199 | *******CD interface |
| 200 | FS-CD: policy does not contain an insurance contract |
| 201 | FS-CD: Local strategy for Coll./Disbursements system is not available |
| 202 | FS-CD: not possible to goto Collections/Disbursements system |
| 203 | FS-CD: Customizing: Role relationship not maintained between FS-PM/FS-CD |
| 204 | FS-CD: Customizing: Contract acct cat. not maintained betw. FS-PM/FS-CD |
| 205 | FS-CD: Customizing: Assignment of trans. type to trans. group missing |
| 206 | FS-CD: Customizing: No master data parameters maintained |
| 207 | FS-CD: Customizing: Ins. obj. cat. not maintained between FS-PM/FS-CD |
| 208 | FS-CD: Customizing: Ass. of co. code to in-force bus. range missing |
| 209 | OBSOLETE Cust.: Assignment for main transaction to transaction missing |
| 210 | OBSOLETE Cust.: Assignment for subtransaction to transaction missing |
| 211 | OBSOLETE Cust.: Assignment for doucment type to transaction missing |
| 212 | OBSOLETE Cust.: Assignment for document category to transaction missing |
| 213 | FS-CD: Customizing: Assignment of role for corr. recipient is missing |
| 214 | FS-CD: Customizing: Assignment of role to alt. or add. corr. rec. missing |
| 215 | FS-CD: Error when creating a contract account |
| 216 | FS-CD: Error when amending a contract account |
| 217 | FS-CD: Error when calling information about contract account |
| 218 | FS-CD: Error when creating an insurance object |
| 219 | FS-CD: Error when changing an insurance object |
| 220 | FS-CD: Error when calling information about the insurance object |
| 221 | FS-CD: Error when reading account balance for contract account |
| 222 | FS-CD: Error when setting payment plan items |
| 223 | FS-CD: Error when determining user data |
| 224 | FS-CD: Error when calling a search help |
| 225 | FS-CD: Error in database Commit |
| 226 | FS-CD: Error in database rollback |
| 227 | FS-CD: Error in call for remote system |
| 228 | FS-CD: Error when adding a role to business partner |
| 229 | FS-CD: No valid policy BO was passed to method &1 |
| 230 | FS-CD: No valid claim BO was passed to method &1 |
| 231 | FS-CD: No valid insurance policy BO was passed to method &1 |
| 232 | FS-CD: No valid role key was passed to method &1 |
| 233 | FS-CD: Method &1 was unable to find role entity &2 |
| 234 | FS-CD: Unable to find access strategy for &1 in Customizing |
| 235 | FS-CD: Customizing: No account creation variant available |
| 236 | FS-CD: Customizing: Either no corr. data records exist or more than one |
| 237 | FS-CD: Customizing: No mapping level available for sales product |
| 238 | FS-CD: Unable to determine a valid scenario in method &1 |
| 239 | FS-CD: Customizing: No account determination defined |
| 240 | FS-CD: Customizing: No transaction group defined for posting type &1 |
| 241 | FS-CD: Customizing: No main trans./subtrans. defined for bal. formation |
| 242 | FS-CD: Only one contract is permitted for the policy |
| 243 | FS-CD: Only one premium payer is permitted for the contract |
| 244 | FS-CD: The transfer table contains multiple values for 'Lock' field |
| 245 | FS-CD: User &1 does not exist in Collections/Disbursements system |
| 246 | FS-CD: Error while reading FI-CA contract account list |
| 247 | FS-CD: Access to Collections/Disbursements system cancelled |
| 248 | FS-CD: No valid lock indicator was passed to method &1 |
| 249 | FS-CD: Data was created in FS-CD on &1 instead of on &2 |
| 250 | Obsolete: FS-CD: Customizing: No TMF available for info cat. &1 |
| 251 | Obsolete: FS-CD: No policy found for insurance object &1 |
| 252 | FS-CD: Policy successfully processed in FS-CD system |
| 253 | Obsolete: FS-CD: Info container interface: Info. cat. &1 not supported |
| 254 | FS-CD: Business process &1 defined in multiple groups |
| 255 | FS-CD: Customizing: Master data parameters not defined &1 |
| 256 | FS-CD: Error during determination of number from number range &1 |
| 257 | FS-CD: Policy successfully processed in FS-CD system (policy: &1) |
| 258 | FS-CD: Note: Not possible to determine paid-to date |
| 259 | FS-CD: Error creating payment plan items for document &1 |
| 260 | FS-CD: Int. error in FIND method for class &1 |
| 261 | FS-CD: Master data still open for policy &1 and doc. no. &2 |
| 262 | FS-CD: Contract account &1 created in FS-CD system (policy: &2) |
| 263 | FS-CD: Contract account &1 changed in FS-CD system (policy: &2) |
| 264 | FS-CD: Insurance object &1 created in FS-CD system (policy: &2) |
| 265 | FS-CD: Insurance object &1 changed in FS-CD system (policy: &2) |
| 266 | FS-CD: Internal error in method &1 class &2: Incorrect selection table |
| 267 | FS-CD: Contract account &1 |
| 268 | FS-CD: Insurance object &1 |
| 269 | Obsolete: FS-CD: info cont. inter.: val. date missing, ins. object: &1 |
| 270 | FS-CD: Contract account &1 already exists |
| 271 | FS-CD: Insurance object &1 already exists |
| 272 | FS-CD: Insurance object &1; policy &2; contract &3 |
| 273 | FS-CD: No posting target entered, doc. no. &1 |
| 274 | FS-CD: Not possible to create lock in FS-CD |
| 275 | OBSOLETE: FS-CD reports payment for expired contract &1 |
| 276 | OBSOLETE: FS-CD reports payment for reversed contract &1 |
| 277 | OBSOLETE: FS-CD reports payment for inactive contract &1 |
| 278 | FS-CD: You must specify source and target with a subledger posting |
| 279 | FS-CD: Not possible to determine a valid lock reason |
| 280 | OBSOLETE: FS-CD reports payment for contract &1 with unsched. processing |
| 281 | OBSOLETE: FS-CD reports payment for contract &1 with investment stop |
| 282 | OBSOLETE: FS-CD reports payment for locked contract &1 |
| 283 | OBSOLETE: FS-CD reports payment for contract &1 with premium waiver |
| 284 | FS-CD: Payment plan items for policy &1 (contract &2) created |
| 285 | FS-CD: Error when calling BAdI &1 - error message: &2 &3 |
| 286 | FS-CD: Class &2, method &1 is obsolete. New: &3 |
| 287 | FS-CD: Error while reading company code |
| 288 | FS-CD: Only one CBC amount payer is allowed for the contract |
| 289 | FS-CD: Dispatch of data for information container category &1 cancelled |
| 290 | FS-CD: ROLLBACK WORK was executed |
| 291 | FS-CD: Error while sending info type &2 to system &1 |
| 292 | FS-CD: Info type &2 was successfully sent to system &1 |
| 293 | FS-CD: Error while sending info type &2 to system &1 |
| 299 | ******* Interface CS/ICM *********************************************** |
| 300 | FS-ICM: Local strategy for commission system is not available |
| 301 | FS-ICM: Template include &1 could not be read |
| 302 | FS-ICM: Not possible to generate subroutine pool: Error &1 |
| 303 | FS-ICM: Error when calling transaction &1 (function &2, dest. &3) |
| 304 | FS-ICM: Technical error when calling remote system &1 (function &2) |
| 305 | FS-ICM: No commission application available for destination &1 |
| 306 | FS-ICM: Triggering method for business transaction is not maintained |
| 307 | FS-ICM: Errors in maintenance of commission tables in FS-PM |
| 308 | FS-CS: Error while mapping commission table fields |
| 309 | FS-ICM: Comm. contract &1 does not have an active vers. for eff. date &2 |
| 310 | FS-ICM: Error determining the commission participant |
| 311 | FS-CS: Error determining the organizational unit |
| 312 | FS-ICM: Error determining the active commission contracts from FS-ICM |
| 313 | FS-ICM: Error determining the participant roles from FS-ICM |
| 314 | FS-ICM: Error determining the version of the commission application |
| 315 | OBSOLETE: FS-ICM: The participant should be available in the 'Agent' role |
| 316 | FS-ICM: No commission case found for business object |
| 317 | FS-ICM: Error when calling remote system &1 (function &2) |
| 318 | FS-ICM: Not possible to create referral agent for commission contract &1 |
| 319 | FS-ICM: Referral agent must be entered for commission contract &1 |
| 320 | OBSOLETE: FS-ICM: Error while determining business partner |
| 321 | FS-ICM: Commission contract &1 is not a group commission contract |
| 322 | FS-ICM: Participation role &1 is not permitted for commission contract &2 |
| 323 | FS-ICM: No authorization for this commission contract |
| 324 | FS-ICM: &1&2 (&3, &4) |
| 325 | FS-ICM: Note a possible triggered pending commission case |
| 326 | FS-ICM: Referral agent &1 not created in BP role agent |
| 327 | FS-ICM: Application must be saved before commission simulation |
| 328 | FS-ICM: Connection problem with remote system |
| 329 | FS-ICM: System error for remote system |
| 330 | FS-ICM: Technical error in call (key: &1 version: &2) |
| 331 | FS-ICM: Commission case successfully updated (key: &1/&2/&3) |
| 332 | FS-ICM: Version conflict for ICM application &1 (FS-PM:&2 FS-ICM:&3) |
| 333 | FS-ICM: Error in external system Commit |
| 334 | FS-ICM: Commission case set to pending (key: &1/&2/&3) |
| 335 | FS-ICM: Commission case set to pending by user (key: &1/&2/&3) |
| 336 | FS-ICM: Error when registering ICM interface agents |
| 337 | FS-ICM: Error while determining FS-ICM destination |
| 338 | FS-ICM: No authorization for transaction &1 (function &2, dest. &3) |
| 339 | FS-ICM: Commission application &1 unknown on remote system &2 |
| 340 | FS-ICM: Unable to determine error message |
| 341 | FS-ICM: Data not yet processed exists in qRFC queue |
| 342 | FS-ICM: Data not yet completely transferred to FS-ICM |
| 343 | FS-ICM: Unable to read table &1 |
| 344 | FS-ICM: No business object category exists for product module gorup &1 |
| 345 | FS-ICM: Unable to determine a triggering subobject category |
| 346 | FS-ICM: Technical error in structure &1 |
| 347 | FS-ICM: Data transfer to FS-ICM takes place as planned, with delay |
| 348 | FS-ICM: Not possible to execute commission simulation |
| 349 | FS-ICM: Other error messages from FS-ICM have been suppressed |
| 350 | FS-ICM: This function is not available |
| 351 | FS-ICM: Pending commission cases exist |
| 352 | FS-ICM: Incorrect commission cases exist |
| 353 | FS-ICM: Referencing failed for Replacement Bus./Product Change BTrans |
| 354 | FS-ICM: Maximum number of referencings exceeded |
| 355 | FS-ICM: Error in assign allocation (BAdI method MAP_OBJ_REF_POLPR) |
| 356 | FS-ICM: No valid evaluation path found |
| 357 | FS-ICM: No valid plan variant found |
| 358 | FS-ICM: Policy processing not chosen |
| 359 | FS-ICM: No product module group found for PM-ID &1 |
| 360 | FS-ICM: No dimension stored for table &1 |
| 361 | FS-ICM: General error while reading Customizing table "&1" |
| 362 | FS-ICM: Commission case was simulated without errors |
| 363 | FS-ICM: Requested commission case does not exist |
| 364 | FS-ICM: No commission case exists |
| 365 | FS-ICM: Simulation of commission cannot be performed |
| 366 | FS-ICM: Commission case display for policy is not possible |
| 367 | FS-ICM: No commission-relevant journal entry exists |
| 368 | FS-ICM: &2 for enhancement category &1 is mandatory |
| 369 | FS-ICM: Specify an enhancement category |
| 370 | FS-ICM: &2 not permitted for enhancement category &1 |
| 371 | FS-ICM: Invalid subobject &1 |
| 372 | FS-ICM: Invalid remuneration type &1 |
| 373 | FS-ICM: Alternative commission exists |
| 374 | FS-ICM: Remumerations with different commission exist |
| 375 | FS-ICM: There are still some commission cases that need checking |
| 376 | FS-ICM: synchronous call for test purposes |
| 377 | FS-ICM: Remunerations exist with adjustment document |
| 378 | FS-ICM: Business partner &1 has no commission contract |
| 379 | FS-ICM: Error while assigning attribute &1 |
| 380 | FS-ICM: Copying of structures is not allowed in production system |
| 381 | FS-ICM: Transfer structure cannot be copied |
| 382 | FS-ICM: Error while reading object information |
| 383 | FS-ICM: Structure &1 could not be activated |
| 384 | FS-ICM: Warnings occurred on activation of structure &1 |
| 398 | Customizing do not exist for payment methods |
| 399 | *******Interface RI |
| 400 | FS-RI: Policy cannot be reinsured |
| 401 | FS-RI: Line of business combination key was not created |
| 402 | FS-RI: In-force business range &1 not found in table /MSG/ABUAIFBRFA |
| 403 | FS-RI: Business partner ID of primary insurer in FS-RI was not created |
| 404 | FS-RI: Elementary prod. &1, &2 and &3 do not have assigned FS-RI industry |
| 405 | FS-RI: Local strategy for reinsurance system is not avaialbe |
| 406 | FS-RI: Technical error when calling remote system |
| 407 | FS-RI: Error while reading &1; contact your system administrator |
| 408 | FS-RI: LoB combination key for elementary product &1 was not created |
| 409 | FS-RI: Not possible to save data for RI interface |
| 410 | FS-RI: Incorrect database access |
| 411 | FS-RI: Error when registering RI interface agents |
| 412 | FS-RI: Error in external system Commit |
| 413 | FS-RI: Policy reinsured in FS-RI (object key: &1) |
| 414 | FS-RI: Error in database Rollback |
| 415 | FS-RI: No sales group exists for sales product &1 |
| 416 | FS-RI: No product group exists for product &1 |
| 417 | FS-RI: No elementary product group exists for elementary product &1 |
| 418 | FS.RI: No method/rule exists for sales prod. &1, prod. &2, elem. prod. &3 |
| 419 | FS-RI: No RI posting codes for reinsurance premium |
| 420 | FS-RI: No time for data for accounting data |
| 421 | FS-RI: No value could be determined for business type |
| 422 | FS-RI: Error occurred when calling BAdI: &1&2 |
| 423 | FS-RI: Manual PML is not possible |
| 424 | FS-RI: No reinsurance data exists |
| 425 | FS-RI: Technical error occurred when determining reinsurance data |
| 426 | FS-RI: Manual PML not possible for contract &1 |
| 427 | FS-RI: Policy has an open facultative requirement |
| 428 | FS-RI: Technical error in reinsurance system |
| 429 | FS-RI: Error loading accumulation data (policy no. &1) |
| 430 | FS-RI: Accumulation data is inconsistent |
| 431 | FS-RI: Accumulation &1 for policy is still being processed in FS-RI |
| 432 | FS-RI: Accumulation &1 was postprocessed manually in a previous bus.proc. |
| 433 | FS-RI: Type of aggregation for totals calculation (coverage level) |
| 434 | FS-RI: Type of aggregation for totals calculation (contract level) |
| 435 | FS-RI: Type of aggregation for totals calculation (policy level) |
| 436 | FS-RI: Type of aggregation for totals calculation (cross-policy) |
| 437 | At least one accumulation of policy is locked for processing in RI system |
| 438 | FS-RI: No manual postprocessing possible for a postdated application |
| 439 | FS-RI: No manual PML permitted for contract &1 (&2) |
| 440 | FS-RI: Manual PML is only permitted at contract or coverage level |
| 441 | FS-RI: Result in the release can differ from that of the RI simulation |
| 442 | FS-RI: Facultative requirement established when postdating was removed |
| 443 | FS-RI: Accumulations for policy &1 have not yet been created in RI system |
| 444 | FS-RI: No manual PML is permitted for this coverage &1 (&2) |
| 445 | FS-RI: Accumulation &1 has not yet been created in RI system |
| 446 | FS-RI: Accumulation &1 has been transferred for processing to RI system |
| 447 | FS-RI: The PML in coverage &1 (&2) refers to several accumulations |
| 448 | FS-RI: The PML in contract &1 (&2) refers to several accumulations |
| 449 | FS-RI: Release of application &1 has been interrupted |
| 450 | FS-RI: For a manual PML, an insured object must exist |
| 451 | FS-RI: The manual PML in contract &1 (&2) needs at least one coverage |
| 452 | FS-RI: Accumulation &1 is still being processed in the RI system |
| 453 | FS-RI: Manual postprocessing is not permitted for coverage &1 (&2) |
| 454 | FS-RI: Incorrect data in simulation of accumulation &1 |
| 455 | FS-RI: Technical error: Multiple occurrences of section ID &1 |
| 456 | FS-RI: Period &1 overlaps with period &2: Accumulation &3 |
| 457 | FS-RI: Period &1 overlaps with period &2: Section ID &3 |
| 458 | FS-RI: Section/accum.assignment &1 without supply of related section &2 |
| 459 | FS-RI: RGN &1 is currently locked by user &2 |
| 460 | FS-RI: Facult.cession requirement for non-Life Risk Manager accumul. &1 |
| 461 | FS-RI: Accumulation &1 is currently locked by user &2 |
| 462 | FS-RI: Facultative cession requirement for accumul. &1 exists in FS-RI |
| 463 | FS-RI: "Manual Postprocessing in RI" cannot be executed |
| 464 | FS-RI: Background release is not executable for this application |
| 499 | ******* Interface FI |
| 500 | FI Customizing: Specifications missing for company code &1 |
| 501 | FI Customizing: G/L account assignment missing for posting code &1 |
| 502 | Message from FI-GL: &1&2&3&4 |
| 549 | ******* Interface CML |
| 550 | CML: Error during registration of CML interface agent |
| 551 | FS-CML: Error while calling BAdI &1; Error message: &2 &3 |
| 599 | ******* Interface PFO |
| 600 | PFO: Error when calling remote system |
| 601 | PFO: Not possible to create business object for policy &1 |
| 602 | PFO: No destination maintained for RFCs |
| 603 | PFO: Not possible to delete business object for policy &1 |
| 604 | PFO: Not possible to delete business object assignment |
| 605 | PFO: Not possible to change business object assignment |
| 606 | PFO: Not possible to change business object assignment |
| 607 | PFO: Assignment object for commission contract &1 does not exist |
| 608 | PFO: Segment for commission contract number &1 not found |
| 609 | PFO: Error when registering PFO interface agents |
| 610 | PFO: Error in BAPI Commit on remote system |
| 611 | PFO: Not possible to create business object in remote system |
| 612 | PFO: Not possible to create PFO in remote system |
| 613 | PFO: Error when creating PFO objects in remote system |
| 614 | PFO: Policy &1 does not exist in remote system |
| 615 | PFO: Error when loading policy &1 from remote system |
| 616 | PFO: Error when loading segment/PFO for policy &1 |
| 617 | PFO: Error when loading AO for policy |
| 618 | PFO: unable to change business object for policy &1 |
| 619 | PFO: Unable to delete business object in remote system |
| 620 | PFO: &1&2 (&3, &4) |
| 621 | PFO: Error in Customizing of PFO interface |
| 622 | Error when calling PFO adapter for OM data |
| 623 | PFO: Policy end &1 > segment end &2 for commission contract &3 |
| 624 | Portfolio Assignment: &1 &2 is already assigned for &3 to &4 |
| 625 | PFO: Assignment to commission contract &1 with start &2 is deleted |
| 626 | PFO: Problem connecting to remote system |
| 627 | PFO: System error in remote system |
| 628 | PFO: Error while reading destination |
| 650 | Reference &1 with status &2 does not exist |
| 651 | Multiple occurrences of reference &1 with status &2 |
| 700 | Transfer package to operational systems without errors |
| 701 | Data sent to component &1 but technical error occurred |
| 702 | Data sent to component &1 but a technical error occurred |
| 703 | Transfer to external system successful |
| 704 | Error in transfer - package refused |
| 705 | OBSOLETE: No entries for the selected selection criteria |
| 706 | OBSOLETE: Info container: Processed &1, scheduled &2 |
| 707 | OBSOLETE: No selection criteria |
| 800 | Invalid queue name &1 |
| 801 | Error when reading table entries via RFC |
| 850 | Message cannot be added to PPO item; Contact SAP |
| 851 | ID of request is initial; Contact SAP |
| 852 | No assignment for PPO item found; Contact SAP |
| 853 | Assignment of PPO item has no structure name; Contact SAP |
| 854 | CML: Access strategy for &1 could not be found in Customizing |
| 855 | FS-CML: Technical error during call of operational system |
| 856 | FS-CML: Unprocessed data exists in the qRFC queue |
| 857 | FS-CML: Unprocessed service calls exist |
| 861 | Error during call of BAdI: &1&2 |
| 862 | Error during call of remote system |
| 863 | FI: Error calling BAdI &1; error message: &2 &3 |