FMCA_ISR_EN -
The following messages are stored in message class FMCA_ISR_EN: .
It is part of development package FMCA_ISR in software component IS-PS-CA. This development package consists of objects that can be grouped under "PSCD: Internet Service Request".
It is part of development package FMCA_ISR in software component IS-PS-CA. This development package consists of objects that can be grouped under "PSCD: Internet Service Request".
Message Nr ▲ | Message Text |
|---|---|
| 000 | 000 - 030 reserved for FPF Customizing |
| 001 | Work items ID/Version/Type should be filled together |
| 002 | Sequence cannot be duplicated for the same form bundle type |
| 003 | Initial value is not allowed for form configuration selection |
| 004 | No form configuration found for form bundle type &1 |
| 005 | Max number of forms should be greater than min number of forms |
| 006 | Form bundle type &1 not defined |
| 007 | BRF context element &1 does not exist |
| 008 | Errors occurred when accessing context element &1 |
| 009 | Placeholder &1 of type &2 not found |
| 010 | Errors occurred when creating inb. corr. of type &1 for BP/CA/CO &2/&3/&4 |
| 011 | Form bundle &1 has status &2 and therefore is not processed |
| 012 | No form bundle was found in context |
| 013 | InCorr. of type &1 is created for BP/CA/CO &2/&3/&4 |
| 014 | Errors occurred when creating the place holder &1 of type &2 |
| 015 | Errors occurred when creating the payment data for business partner &1 |
| 016 | Errors occurred when creating accounting data for contract object &1 |
| 017 | Bank data of contract account &1 to business partner &2 is updated |
| 018 | Errors occurred when changing payment data for con. acc. &1 of BP &2 |
| 019 | Workflow &1 with reason &2 started |
| 020 | Errors occurred when updating data of form bundle &1 |
| 021 | Errors occurred when creating BUPA relationship for &1 &2 of cat. &3 |
| 022 | BUPA relationship for &1 &2 of cat. &3 is created |
| 023 | Errors occurred when creating/changing rules for InCorr of BP/CO &1 &2 |
| 024 | Rules for InCorr of BP/CO &1 &2 are created |
| 025 | Rules for InCorr of BP/CO &1 &2 are changed |
| 026 | Correspondence of type &1 is created for BP/CA/CO &2/&3/&4 |
| 027 | Errors occurred when creating corr. of type &1 for BP/CA/CO &2/&3/&4 |
| 028 | Placeholder &1 of type &2 exists already and cannot be inserted |
| 029 | Billing document &1 created |
| 030 | Billing document &1 adjusted to zero |
| 031 | Billing document &1 adjusted by billing document &2 |
| 032 | InCorr. of type &1 is cleared for BP/CA/CO &2/&3/&4 |
| 033 | Errors occurred when clearing InCorr. of type &1 for BP/CA/CO &2/&3/&4 |
| 034 | Invoice document &1 created |
| 035 | InCorr. of type &1 reopened for BP/CA/CO &2/&3/&4 |
| 036 | Errors occurred when creating address for business partner &1 |
| 037 | Address with number &1 of type &2 is created for business partner &3 |
| 038 | Form-based process &1 does not support confirmation letters |
| 039 | Bank detail &1 is created for business partner &2 |
| 040 | Error occurred by TOBL for BP &1, CA &2, CO &3, rev.type &4 |
| 041 | Fact type/rep. &1 and fact cat./rep. &2 is not allowed for COTYP &3 |
| 042 | &1 BRF messages for form bundle &2 are created |
| 043 | &1 BRF messages for form bundle &2 are updated |
| 044 | Error occurred when creating the context element &1 in BRF |
| 045 | Form bundle type &1 is date-dependent but no key date is specified |
| 046 | Form bundle type &1 is period-dependent but no period is specified |
| 047 | Either a key date or a period should be specified |
| 048 | Errors occurred when posting billing documents for form bundle &1 |
| 049 | Business partner &1 changed |
| 050 | Object &1 &2 is neither a tax division nor a tax unit |
| 051 | No tax division and no tax unit found for position &1 |
| 052 | Tax division &2 but no tax unit found for position &1 |
| 053 | Tax unit &2 but no tax division found for position &1 |
| 054 | Object &1 is not a tax unit |
| 055 | Object &1 is not a tax division |
| 056 | No tax division found for tax unit &1 |
| 057 | User &1 has no leading position in any tax division/tax unit |
| 058 | No tax division found for user &1 |
| 059 | Workitem &1: Neither a tax unit nor a tax division could be derived |
| 060 | Scenario cannot be found for period &1 and ISR template &2 |
| 061 | Scenario cannot be found for key date &1 and ISR template &2 |
| 062 | System cannot find scenario for ISR template &1 |
| 063 | ID number &1 with ID type &2 of partner &3 is created |
| 064 | ID number &1 with ID type &2 of partner &3 is changed |
| 065 | Error occurred when checking the header of form bundle &1 |
| 066 | Either revenue type or form bundle type is nec to deter. reason codes |
| 067 | Reason code &1 is not allowed for form bundle type &2 |
| 068 | Form bundle type &1 does not have a valid number range |
| 069 | Form bundle type &1 only allows numbers from &2 to &3 |
| 070 | Do not enter a number as form bundle type &1 uses internal assignment |
| 071 | Revenue type &1 does not have a valid number range |
| 072 | Revenue type &1 only allows numbers from &2 to &3 |
| 073 | Do not enter a number as revenue type &1 uses internal assignment |
| 074 | Status Management:Business transaction &1 is applied to object &2 |
| 075 | Revenue distribution key &1 is created |
| 076 | No history object with sequence number &2 if found for form bundle &1 |
| 077 | Specify a caller for form bundle processing |
| 078 | Specify an activity for form bundle processing |
| 079 | Status Management:Business transaction &1 is applied to form bundle &2 |
| 080 | Form bundle &1 does not exist |
| 081 | Form &1 number &2 of form bundle &3 can not be inserted due to duplicate |
| 082 | Enter valid from date |
| 083 | Enter valid to date |
| 084 | Valid to date &1 must be later than valid from date &2 |
| 085 | Validity &1 of ISR scenario &2 must cover validity &3 of BRF event &4 |
| 086 | Errors occurred when posting invoicing documents for form bundle &1 |
| 087 | Form &1 cannot be updated due to erroneous logical key |
| 088 | At least one BRF message of type W, E, A, or X occurred |
| 089 | &1 form bundles were updated with indicator and status in header |
| 090 | Complete master data creation for registration form bundle number &1 |
| 091 | Failed to create master data for registration form &1 |
| 092 | No processing variant is defined for form bundle type &1 and act. &2 |
| 093 | Form based process &1 is not defined |
| 094 | No description for the form based process &1 is found in &2 |
| 095 | Enter either form bundle number or the form bundle guid |
| 096 | No form bundle is found for the specified conditions |
| 097 | Form bundle &1 does not exist |
| 098 | More than one form bundle found |
| 099 | Errors occurred when creating a form bundle |
| 100 | ***reverse for intern use in form processing framework |
| 101 | Start creating business partner |
| 102 | Finish creating business partner successfully |
| 103 | Start creating contract account |
| 104 | Finish creating contract acccount successfully |
| 105 | Contract object &1 is assigned to business partner &2 with account &3 |
| 106 | Start updating contract account with payment data |
| 107 | Start creating contract object |
| 108 | Finish creating contract object successfully |
| 109 | Start creating business location |
| 110 | Start creating accounting data for contract objects |
| 111 | Finish creating accounting data for contract objects successfully |
| 112 | Start creating bank detail |
| 113 | Finish creating bank detail |
| 114 | Status Management: Transaction &1 could not be applied to object &2 |
| 115 | Start changing status |
| 116 | Finish changing status |
| 117 | Start triggering workflows |
| 118 | Finish triggering workflows |
| 119 | Start creating tax obligations |
| 120 | Finish creating tax obligations |
| 121 | Start updating form bundle data |
| 122 | Finish updating form bundle data |
| 123 | Start creating revenue distribution key |
| 124 | Finish creating revenue distribution key |
| 125 | Start creating billing document |
| 126 | Finish creating billing document |
| 127 | Start creating business partner relationship |
| 128 | Finish creating business partner relationship |
| 129 | Start creating/changing rules for creating InCorr. Req. |
| 130 | Finish creating/changing rules for creating InCorr. Req. |
| 131 | Starting creating turn around letters |
| 132 | Finish creating turn around letters |
| 133 | Starting creating conformation letters |
| 134 | Finish creating confirmation letters |
| 135 | Starting clearing inbound correspondence request |
| 136 | Finish clearing inbound correspondence request |
| 137 | Starting creating inbound correspondence request |
| 138 | Finish creating inbound correspondence request |
| 139 | Start creating business partner address |
| 140 | Finish creating business partner address |
| 141 | Start creating business location |
| 142 | Finish creating business location successfully |
| 143 | Start modifying the status of BRF messages |
| 144 | Finish modifying the status of BRF messages |
| 145 | Start creating business partner identification |
| 146 | Finish creating business partner identification |
| 147 | Error occurred when processing ID number &1 with type &2 for partner &3 |
| 148 | Start creating invoicing document |
| 149 | Finish creating invoicing document |
| 150 | Processing rule &1 is not defined for form bundle type &2 |
| 151 | Processing variant &1 is not defined for the form bundle type &2 |
| 152 | You have to enter either revenue type or form bundle type |
| 153 | Form bundle number &1 has already been assigned |
| 154 | Process for registration form bundle number &1 completed |
| 155 | No form-based process is assigned to form bundle type &1 |
| 156 | Start creating/updating CO relationship |
| 157 | Finish creating/updating CO relationship |
| 158 | Event is not defined for &1 &2 &3 |
| 159 | No BRF events determined for form bundle &1 and activity &2 |
| 160 | Start extracting master data from form bundle |
| 161 | Finish extracting master data from form bundle |
| 162 | Start updating tax number for business partner |
| 163 | Finish updating tax number for business partner |
| 164 | Error when creating/updating tax number &1 for business partner &2 |
| 165 | Successfully create/update tax number &1 for business partner &2 |
| 166 | Create relationship type &4 for master data &1 and &2, revenue type &3 |
| 167 | (BP) Identification type &1 is not defined |
| 168 | InCorr. of type &1 created for BP/CA/CO &2/&3/&4 |
| 169 | Start processing SAP User Management Engine (UME) users |
| 170 | ***170-200 reversed for correspondences |
| 171 | Business partner is unknown for correspondence |
| 172 | Return ID is unknown for correspondence |
| 173 | Application class is unknown for correspondence |
| 174 | Action is unknown for correspondence |
| 175 | Business partner not found |
| 176 | Contract account not found |
| 177 | Contract object not found |
| 178 | Timestamp is unknown for correspondence |
| 179 | Business partner relationship not found |
| 180 | Tx obligatn created/updated for BP &1, CA &2, CO &3, rev. type &4 |
| 181 | Form bundle &1 will be processed without any form in context |
| 182 | Start updating industry for business partner |
| 183 | Finish updating industry for business partner |
| 184 | Error when creating/updating industry &2 for business partner &1 |
| 185 | Successfully created or updated industry &2 for business partner &1 |
| 186 | Tax number &1, for business partner &2 |
| 187 | Industry &2 for business partner &1 |
| 188 | Relationship type &4 for master data &1 and &2, revenue type &3 |
| 189 | No valid processing rules is defined for form bundle type &1 and act. &2 |
| 190 | Form bundle type &1 is not assigned to process &2 |
| 201 | *-----201-230 reserved for mass activity FMCAPFPF------------------------ |
| 202 | &1 form bundles were processed |
| 203 | Form bundles not processed successfully: &1 |
| 204 | Form bundles simulated: &1 |
| 205 | Form bundles skipped: &1 |
| 206 | Start processing form bundle &1 |
| 207 | Finish processing form bundle &1 with errors |
| 208 | Finish processing form bundle &1 successfully |
| 209 | Form bundle &1 was not processed in mass activity; see long text |
| 210 | Messages raised during form processing by system |
| 211 | Messages raised during form processing by BRF |
| 212 | No message raised during form processing by system |
| 213 | No message raised during form processing by BRF |
| 214 | &1 is in status &2 - activity &3 not allowed |
| 231 | Object type &1 for trace form processing history is not defined |
| 232 | Object type &1 for trace form processing history has no description |
| 233 | Activity &1 for trace form processing history has no description |
| 240 | Start processing SAP User Management Engine (UME) users |
| 241 | Finish processing SAP User Management Engine (UME) users |
| 242 | SAP User Management Engine (UME) user &1 has been activated successfully |
| 243 | Activation of SAP User Management Engine (UME) user &1 failed |
| 246 | No tax asssessment was created for form bundle &1 |
| 247 | Status of form bundle &1 has been changed to &2 |
| 248 | &1 is not a valid GUID |
| 300 | *** 300-350 reserved for tax case handling |
| 301 | No tax case found for GUID &1 |
| 302 | Error updating or inserting tax case &1 |
| 303 | No risk profile found for taxpayer &1 |
| 304 | Error updating or inserting risk profile |
| 305 | Error creating notes for tax case &1 |
| 306 | Category &1 ID number &2 not valid for selection date &3 |
| 350 | 350 to 399 is reserved for tax return amendment |
| 351 | Duplicated tax return with form bundle number &1 found |
| 352 | Form &1 with form number &2 not found in source tax return |
| 353 | Form &1 with form number &2 not found in target tax return |
| 354 | Return merge can only happen between 2 tax returns |
| 355 | Source and target tax return have same receipt date |
| 356 | Tax return &1 merged to tax return &2 |
| 357 | Amendment processing for tax return &1 is starting |
| 358 | Amendment processing for tax return &1 has ended |
| 359 | Source or target tax return contain incorrect data; see long text |
| 360 | Tax return &1 was merged with tax return &2 |
| 361 | Form &1 with form number &2 in tax return &3 is not active, merge stops |
| 362 | Two duplicated tax returns required |
| 363 | Merge proposal contains invalid form (form name &1/form number &2) |
| 364 | Target tx retrn &1 not duplicated to source tx retrn &2; s. long text |
| 365 | Status of tax return &1 does not allow merging |
| 366 | Selected source/target return diffrnt from merge proposal; s. long text |
| 367 | No authorization for amendment action &1 for process &2; s.long text |
| 370 | No active form with form type &1 in form bundle type &2; s.long text |
| 371 | You cannot merge forms with different form class |
| 372 | You cannot merge table forms |
| 373 | No.of actve forms (form type &1/form bndle type &2) inconsist; s.lng txt |
| 374 | Error during copying of table form; see long text |
| 375 | Form class &1 is not supported |
| 376 | Form bundle &1 with status &2 cannot be processed |
| 377 | Form bundle &1 contains too many active forms of type &2 (Max: &3) |
| 378 | Form bundle &1 contains too few active forms of type &2 (Min: &3) |
| 379 | Select two valid and different form bundles |
| 380 | Not all forms compatible with Form Bundle &1 |
| 381 | Tax return &1 can be merged to tax return &2 |
| 382 | Late amendment return &1 found for tax return &2 |
| 383 | Process duplicated return &2 in amendment mode; see long text |
| 384 | Exactly one duplicated tax return &2 found for tax return &1 |
| 385 | Duplicate return(s) found |
| 386 | Duplicate check was not performed |
| 400 | ** Miscellaneous Form Processing 400-450 |
| 401 | Define residence time for revenue type &1; see longtext |
| 402 | Document not old enough; receipt date &1 after key date &2 |
| 403 | Document not old enough; creation date &1 after key date &2 |
| 404 | Document not old enough; upper bound of period &1 after key date &2 |
| 405 | Document not old enough; statute of limitation date &1 after key date &2 |
| 406 | Form data version &1 does not exist for form &2 &3 |
| 407 | System has copied form data from version &1 to &2 for form &3 &4 |
| 408 | You can only remove newly created or draft forms |
| 409 | No TRM-specifc settings are found for scenario &1 and version &2 |
| 410 | Form bundles with last 3 digits &1 to &2 are currently processed |
| 411 | More than two ISR scenarios &1 &2 are found for template &3 |
| 412 | You cannot relate a scenario to itself |
| 413 | Related scenarios must have different templates with the same interface |
| 414 | The configuration of scenario &1 version &2 is incomplete |
| 415 | No incomplete BI extraction history found in the system |
| 416 | Number of form bundles updated: &1 |
| 417 | Number of forms updated: &1 |
| 418 | Form bundles with last 3 digits &1 to &2 were processed successfully |
| 419 | Form data of &1 forms were updated in delta queue &2 |
| 420 | Do not use number range &1; see long text |
| 421 | Fill BRFplus application when using BRFplus in the rule |
| 422 | Only rules using same rule engine can be set in one variant |
| 423 | Error occurred in BRFplus |
| 424 | Function &1 not found in application &2 |
| 425 | Data object &1 does not exist or invalid input |
| 426 | Calling function &1 failed |
| 427 | Error reading value &1 from BRFplus context |
| 428 | Error reading BRFplus trace |
| 429 | Fill BRFplus function when using BRFplus in the rule |
| 430 | BRFplus application &1 does not exist |
| 431 | BRFplus function &1 does not exist in BRFplus application &2 |
| 432 | Error occurred in BRFplus: &1&2&3&4 |
| 433 | No deployed BRFplus application &1 found |
| 434 | No deployed BRFplus function &1 found for BRFplus application &2 |
| 435 | Form &1 Scenario/Version changed due to Tax Period shift from &2 to &3 |
| 451 | ***451-499*** reversed for BI extraction |
| 452 | DataSource &1 of version &2 does not exist |
| 453 | Form &1 does not support DataSource &2 |
| 454 | The DataSource &1 is not assigned to any ISR scenario |
| 455 | There was an incomplete run on DataSource &1 |
| 456 | Incomplete run on DataSource &1 limited to form bundle type &2 |
| 457 | Delta on DataSource &1 was not initialized successfully |
| 458 | Delta on DataSource &1 limited on FBTYP &2 was not initialized |
| 459 | &2 form bundles that have a number ending with &1 are extracted |
| 460 | &2 forms that have a number ending with &1 are extracted |
| 461 | BI field name &1 is already assigned to the form view field &2 |
| 462 | Field name &1 is defined in extract structure but not in ISR Customizing |
| 463 | Field name &1 defined in ISR &3 for field &2 but not in extract structure |
| 464 | ISR scenario &1 does not exist in version &2 |
| 465 | Include name &1 must begin with CI_FPF_FORM_FIELDS or SI_FPF_FORM_FIELDS |
| 466 | Characteristic &1 is not defined in ISR scenario/version &2/&3 |
| 467 | Definition of scenario &1 and extract structure &2 is consistent |
| 468 | No activation; Use SE11 to check activation status for structure &1 |
| 469 | No DataSource is assigned to ISR scenario &1/version &2 |
| 470 | You cannot delete forms; BI extraction in mass processing is running |
| 471 | Name of DataSource &1 should not begin with 0; see long text |
| 472 | Enter the name for the extract structure to be generated |
| 473 | Enter the name of the include for the fields to be generated |
| 474 | Enter the name of the DataSource to be generated |
| 475 | Function group &1 does not exist |
| 476 | Include &1 has been created |
| 477 | Structure &1 has been created |
| 478 | Creation of include &1 has been reversed |
| 479 | Creation of structure &1 has been reversed |
| 480 | Enter the name of the function group for the extractor to be generated |
| 481 | Structure &1 has no active version |
| 482 | Extractor &1 has not been activated |
| 483 | Extractor &1 already exists |
| 484 | Fill in the name for the extractor to be generated |
| 485 | Creation of extractor &1 has been reversed |
| 486 | Creation of DataSource &1 in version D has been reversed |
| 487 | Extractor &1 has been created in the function group &2 |
| 488 | DataSource &1 has been created in version D |
| 489 | Use the same namespace for objects &1 and &2; see long text |
| 490 | &1 activated with warnings.Check activation log for structure &1 (SE11) |
| 491 | DDIC object &1 has been activated |
| 492 | &1 has data type CURR or QUAN. Please specify a reference field. |
| 493 | No type was defined for &1 |
| 494 | Reference field &1 is not defined in the include &2 |
| 495 | Length of the extract structure name &1 shall not greater than 26 |
| 496 | Specify at least one delta queue for update |
| 497 | Form bundle &1 field &2 could not be converted. |
| 500 | ***501-549 reserved for Table Form |
| 501 | Table &1: Put field &2 of type &3 as key field at position &4 |
| 502 | Change document object &1 does not exist |
| 503 | Include table &1 into change document object &2 |
| 504 | Do not copy table &1 as intrnl table in chnge doc. obj. &2; s. long text |
| 505 | Copy table &1 as internal table in chnge doc. obj.&2; s. long text |
| 506 | Remove table &1 from change document object &2 |
| 507 | Web Dynpro component &1 does not exist or is inactive |
| 508 | Web Dynpro component &1 does not implement interface &2 |
| 509 | Class &1 does not exist or is inactive |
| 510 | Class &1 does not implement interface &2 |
| 511 | Entries created based on fields of table &1 |
| 512 | Program deleted fields that were not available in table &1 |
| 513 | Entries refreshed based on fields of table &1 |
| 514 | No DDIC object generated for table &1 |
| 515 | Generated DDIC object &1 is not compatible with table &2 |
| 516 | Table form &1 does not exist |
| 517 | You are not allowed to maintain this key field |
| 518 | Table form &1 is already assigned to form type &2 |
| 519 | A key field has to be set as a read only input field |
| 550 | ***551-599 reserved for return duplicate check |
| 551 | Provide form bundle GUID or business partner number |
| 552 | Provide form bundle GUID or form bundle number |
| 553 | Form bundle not found for &1 &2 &3 &4 |
| 554 | Error occurs when updating member table for return ID &1 |
| 600 | ***600-649 reserved for Migration from ABTYP to FBTYP |
| 601 | Form bundle type &1 already exists |
| 602 | Rev. type &1 contains form types of different form-based processes |
| 603 | Form bundle type &1 is already assigned to revenue type &2 |
| 604 | In &3 no form bundle type is assigned to rev. type/fb process &1/&2 |
| 605 | Table form definition &1 &2 could not be found |
| 606 | In &3 form bundle type &1 is already assigned to revenue type &2 |
| 607 | Report a customer message to SAP; error occurred when accessing view &1 |
| 608 | Specify validity of revenue type &1/form bundle type &2 relationship |
| 609 | No migration of tax return &1; revenue type missing |
| 610 | Tax returns processed sucessfully: &1 |
| 611 | Tax returns not processed successfully: &1 |
| 612 | Tax returns simulated: &1 |
| 613 | Program did not migrate any tax returns in this run |
| 614 | Specify complete validity of rev. type-form bundle type relationship |
| 615 | In &3 several form bundle type is assigned to rev. type/fb process &1/&2 |
| 616 | Form bundle &1 has already form bundle type &2 -> no migration ncecessary |
| 617 | Table form definition &1 &2 is not valid anymore |
| 618 | Scenario is not valid anymore for period &1 and ISR template &2 |
| 619 | Scenario is not valid anymore for key date &1 and ISR template &2 |
| 620 | Scenario is not valid anymore for ISR template &2 |
| 621 | Related scenario could not be found for scenario &1 and version &2 |
| 622 | Form bundle type &1 is not assigned to revenue type &2 for &3 &4 |
| 623 | The selected options are not allowed |
| 624 | In &3 several revenue types are assigned to fb type &1/fb process &2 |
| 625 | Cannot find revenue type for inbound corresp. category &1 and period &2 |
| 626 | Form bundle type could not be derived in event P348 for &1 &2 |
| 627 | Cannot create tax return for taxpayer &1, period &2, form bundle type &3 |
| 628 | Tax return &1 created for taxpayer &2, period &3, and form bundle type &4 |
| 629 | Trying to create estimated tax return for period &1, revenue type &2 |
| 630 | Trying to fill container for correspondence type &1 |
| 631 | Correspondence container for &1 filled |
| 650 | ***650-700*** reserved for application log and archiving |
| 651 | Form was added |
| 652 | Cannot archive status &1 |
| 653 | Work item with status &1 exists |
| 700 | No billing document data is specified |
| 701 | Table FMCA_ESH_TRM_XML_DATA was generated |
| 702 | No forms were found for the specified form bundle types |
| 703 | Check for addition of generated structures to transport request failed |