FMCA_DM_EN - Debt Management Messages
The following messages are stored in message class FMCA_DM_EN: Debt Management Messages.
It is part of development package FMCA_DM_MAIN in software component IS-PS-CA. This development package consists of objects that can be grouped under "PSCD: Public Sector Debt Management Main Package".
It is part of development package FMCA_DM_MAIN in software component IS-PS-CA. This development package consists of objects that can be grouped under "PSCD: Public Sector Debt Management Main Package".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 &2 &3 &4 |
| 001 | Select records to update. |
| 002 | RFC destination call &1 failed or doesn't exist. |
| 003 | Data weren't found. |
| 004 | Error updating the database. |
| 005 | Error deleting from the database. |
| 006 | Check failed for RFC connection &1. &2 &3 &4. Check RFC in SM39. |
| 007 | System parameters couldn't be determined. |
| 008 | Record &1 is processed and will be skipped. |
| 009 | No unprocessed data were found. |
| 010 | Debt Collection Management is already active in S/4 HANA. |
| 021 | Dunning block &1 is entered for business partner &2. |
| 022 | &1 open items are added to debt set &2. |
| 023 | Collection strategy for debt set &1 has been changed from &2 to &3. |
| 024 | Master data group for &1 &2 &3 &4 doesn't exist. |
| 025 | &1 open items are removed from debt set &2. |
| 026 | &1 open items were in debt set &2 and remain in debt set &2. |
| 027 | Debt set &2 is protected and &1 open items were not removed from it. |
| 028 | &1 were added to enforcement action &2. |
| 029 | &1 were removed from enforcement action &2. |
| 030 | Debt set &2 is protected and &1 open items were not added to it. |
| 031 | &1 open items added to debt set &2 because the original is protected. |
| 032 | No active BRFplus function for event &1 for master data group &2. |
| 033 | &1 open items are removed from debt set &2 and aren't in any debt set. |
| 034 | &1 open items not removed from set &2 because they were added manually. |
| 035 | &1 open items not removed from set &2 because they are in proposal mode. |
| 036 | Proposed collection step is excluded. |
| 037 | | Coll. step &1 is determined instead of manually set coll. step &2 |
| 038 | Debt Set &1 will not be created, there is no value for collection step |
| 051 | Debt set &1 doesn't exist. |
| 052 | Debt set &1 is protected, open item &2 can't be removed. |
| 053 | Open item &2 assigned to debt set &1. |
| 054 | Debt set &1 is protected, open item &2 can't be assigned to it. |
| 055 | Debt set &1 does not exist, open item &2 can't be assigned to it. |
| 056 | Open item &2 unassigned from debt set &1. |
| 057 | Open item &2 is added to debt set &1 in proposal mode. |
| 058 | Open item &2 can't be unassigned from debt set &1. |
| 100 | ----------------------------- ACTIVITY RUN ----------------------------- |
| 101 | Activity run &1 for debt set &2 starts for debtor &3. |
| 102 | Activity run &1 for debt set &2 is complete. |
| 103 | Activity run &1 for debt set &2 is in simulation mode. |
| 104 | Activity run &1 for debt set &2 created &3&4. |
| 105 | There aren't any actions for debt set &1 in this activity run. |
| 106 | There's no valid authorization for activity run &1 debt set &2. |
| 107 | Debt set &1 is added to existing enforcement action &2. |
| 199 | |
| 200 | * -------------- Replication of Enforcement Action ------------------- * |
| 201 | Error occurred during database save; invalid update mode &1 in object &2. |
| 202 | No enforcement action data are provided. |
| 203 | Method &1 called with incorrect parameters. |
| 204 | Enforcement action wasn't created because it exists in the buffer. |
| 205 | Enforcement action wasn't created because it exists in the database. |
| 206 | Error occurred creating a UUID for field name &1. |
| 207 | Error occurred changing header object in enforcement action buffer. |
| 208 | Error occurred creating enforcement action &1 in buffer. |
| 209 | Error occurred saving to buffer. |
| 210 | Error during processing of enforcement action &1; no changes made in ERP. |
| 211 | Enforcement action &1 processed without errors. |
| 212 | An exception occurred without an assigned message. |
| 213 | Business partner &1 used in partner function &2 doesn't exist in SAP ERP. |
| 214 | A newer version of the enforcement action '&1' exists in SAP ERP |
| 215 | No authorization for some requested objects |
| 216 | Select at least one line |
| 217 | Error occurred deleting enforcement action &1 |
| 218 | Error occurred deleting header object in enforcement action buffer |
| 219 | You're not authorized to create or change enforcement action in &1 |
| 220 | You don�t have authorization for object &1 activity &2 |
| 221 | Fee/item was not created because it already exists in the buffer |
| 222 | Error while removing item from buffer for '&1' |
| 223 | Fee has not been created because it already exists in the database |
| 224 | Error occurred changing item object '&1' in enforcement action buffer |
| 225 | Business partner &1 is locked by user &2 |
| 226 | A newer version of the enforcement action item '&1' exists in SAP ERP |
| 300 | --------------------C O N F I G U R A T I O N---------------------------- |
| 301 | Enter a unique application name. |
| 302 | Enter a unique function name. |
| 303 | Enter a valid application name. |
| 304 | Enter a valid function name. |
| 305 | Enter the application name and function name. |
| 306 | Enter a function name. |
| 307 | Event P430 is not implemented |
| 400 | ----------------------------REAL TIME DUNNING---------------------------- |
| 401 | Run Time Dunning was executed succesfully! |
| 402 | Unable to open the Scheduler, the operation is aborted |
| 403 | Unable to start a Job |
| 404 | There are no items for this execution |
| 405 | This report can only be executed when switch &1 is active |
| 406 | GUID creation fail |
| 407 | Error in Dunning execution (&1), check log of dunning ID &2 &3 |
| 408 | There is no log yet, execute it first |
| 409 | Real Time Dunning item for Debtor & is obsolete |
| 410 | Dunning Process &1 &2 is running externally |
| 450 | -----------------------SPECIAL REPORTS FOR DUNNING----------------------- |
| 451 | Start the process of fixing Number Range table |
| 452 | TEST mode |
| 453 | PRODUCTIVE mode |
| 454 | Delete: Number Type &1, Range Type &2 because number &3 do not exists |
| 455 | Update: Number Type &1, Range Type &2, from number &3 to &4 |
| 456 | Finish the process of fixing Number Range table |
| 457 | Changes saved successfully |
| 458 | Changes were not saved, an error occurs |
| 459 | Starting check step &1 |
| 460 | There are some debt sets out of ranges |
| 461 | Debt Set &1 is out of range |
| 462 | End of check step &1 |
| 463 | Reset: Number Type &1, Range Type &2 because number &3 do not exists |
| 464 | Debt Set &1 exist in history table but not in the header |
| 465 | Debt Set &1 do not exist in history table |
| 466 | Open Item &1 is duplicated in &2 debt sets |
| 467 | Debt Set &1 has categories but not header |
| 468 | Debt set &1 has Open Items values but not header |
| 469 | Invalid Debt Set &1 in Open Items &2 (Table DFKKOP) |
| 470 | It is not possible to check category tables using Business Partner |
| 471 | It is not possible to check debt set items using Business Partner |
| 472 | We are checking &1 lines of Dunning History containing Debt Sets values |
| 473 | &1 new Debt Sets created for this dunning run |
| 474 | &1 lines evaluated for possible duplication |
| 475 | Evaluating Debt Set categories without a header |
| 476 | Evaluating Debt Set open items without a header |
| 477 | &1 Dunning History lines evaluated |
| 478 | Start the check for Debt Management consistency |
| 479 | End the check for Debt Management consistency |
| 480 | There is no item to check consistency |