SAP ABAP Message Class FDM_COLLECTION (SAP Collections Management)
Basic Data
Hierarchy
☛
SAP_FIN (Software Component) SAP_FIN
⤷
FIN-FSCM-COL-AR (Application Component) Accounts Receivable Accounting Process Integration
⤷
FDM_AR_COLLECTION (Package) FSCM Collections Management FI-AR
⤷
⤷
Attributes
| Message class | FDM_COLLECTION | |
| Short Description | SAP Collections Management | |
| Changed On | 20130531 | |
| Last Changed At | 100435 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Select at least one invoice | Space: object requires documentation | ||
| 2 | Select exactly one invoice | The short text describes the object sufficiently | ||
| 3 | Customer &1 is currently being processed by user &2, only display poss. | Space: object requires documentation | ||
| 4 | Select exactly one promise to pay | Space: object requires documentation | ||
| 5 | Select at least one promise to pay | Space: object requires documentation | ||
| 6 | Promise to pay was created | Space: object requires documentation | ||
| 7 | The selected promises to pay have been withdrawn | Space: object requires documentation | ||
| 8 | Before saving, you have to distribute the amount to the invoices | Space: object requires documentation | ||
| 9 | The promise to pay has been confirmed and you can no longer change it | Space: object requires documentation | ||
| 10 | Promises to pay already exist for the invoices selected | Space: object requires documentation | ||
| 11 | Select one line only | Space: object requires documentation | ||
| 12 | No hits for the custom selection for the customer | Space: object requires documentation | ||
| 13 | No hits for the custom selection for the company code | Space: object requires documentation | ||
| 14 | Select a company code | The short text describes the object sufficiently | ||
| 15 | Select only one entry | The short text describes the object sufficiently | ||
| 16 | Only select invoices of a single head office | The short text describes the object sufficiently | ||
| 17 | Select at least one invoice | The short text describes the object sufficiently | ||
| 18 | There is no implementation for function code &1 | The short text describes the object sufficiently | ||
| 19 | Customer has been dunned | The short text describes the object sufficiently | ||
| 20 | No dunning notice has been created | The short text describes the object sufficiently | ||
| 21 | No active implementation for BAdI FDM_PARTNER_MAPPING | The short text describes the object sufficiently | ||
| 22 | RFC error during determination of mapping information in system &1 | The short text describes the object sufficiently | ||
| 23 | No recipient for message type &1 found | The short text describes the object sufficiently | ||
| 24 | New printout &1 has been requested | The short text describes the object sufficiently | ||
| 25 | Correspondence &1 has not been requested | The short text describes the object sufficiently | ||
| 26 | Dunning notices for additional customer contacts have been created | Space: object requires documentation | ||
| 27 | Correspondence print not requested. Print settings are invalid | The short text describes the object sufficiently | ||
| 28 | There is no implementation for contact type &1 | The short text describes the object sufficiently | ||
| 29 | You have not selected a company code | The short text describes the object sufficiently | ||
| 30 | You are not authorized to display billing documents | The short text describes the object sufficiently | ||
| 31 | > Document &1/&2/&3 will not be dunned until &4 due to promise to pay | Space: object requires documentation | ||
| 32 | New output of billing document has been terminated | The short text describes the object sufficiently | ||
| 33 | Billing document cannot be printed. No valid message type | The short text describes the object sufficiently | ||
| 34 | Error when printing 'new output of billing document' | The short text describes the object sufficiently | ||
| 35 | Error with the print view 'new output of the billing document' | The short text describes the object sufficiently | ||
| 36 | Error occurred when requesting 'new output of billing document' | The short text describes the object sufficiently | ||
| 37 | Summary of customer contact sent to customer by e-mail | The short text describes the object sufficiently | ||
| 38 | You have terminated the action | The short text describes the object sufficiently | ||
| 39 | Dunning notice by e-mail to &1 | The short text describes the object sufficiently | ||
| 40 | Dunning notice by fax to &1 &2 | The short text describes the object sufficiently | ||
| 41 | Enter a valid e-mail address | The short text describes the object sufficiently | ||
| 42 | Enter fax number and the country of the fax number | The short text describes the object sufficiently | ||
| 43 | Navigate to document &1 to change the texts | The short text describes the object sufficiently | ||
| 44 | Contact person data for customer &1 selected | The short text describes the object sufficiently | ||
| 45 | Changes have been successfully saved | The short text describes the object sufficiently | ||
| 46 | Correspondence &1 could not be requested | Space: object requires documentation | ||
| 47 | Account &1 not posted to. Print view/print account statement not possible | The short text describes the object sufficiently | ||
| 48 | Promise to pay has already been withdrawn | The short text describes the object sufficiently | ||
| 49 | Total of assigned amounts will be transferred as promised amount | Space: object requires documentation | ||
| 50 | Distributed amount &1 &3 and promised amount &2 &3 are not equal | Space: object requires documentation | ||
| 51 | &1 &2 were distributed over the selected invoices | Space: object requires documentation | ||
| 52 | The promised amount has been distributed completely | Space: object requires documentation | ||
| 53 | No promise to pay selected | Space: object requires documentation | ||
| 54 | State '4' must not be set in the BADI FDM_P2P_JUDGE | Space: object requires documentation | ||
| 55 | Lock error: User &4 is processing promise for invoice &1 &2 &3 | Space: object requires documentation | ||
| 56 | Promise for invoice &1 &2 &3 was valuated with '&4' | Space: object requires documentation | ||
| 57 | The promise for invoice &1 &2 &3 has been confirmed | Space: object requires documentation | ||
| 58 | There are no promises to pay to be confirmed | Space: object requires documentation | ||
| 59 | State of the promise for invoice &1 &2 &3 has not been changed | Space: object requires documentation | ||
| 60 | Promise for invoice &1 &2 &3: Valuation not possible | Space: object requires documentation | ||
| 61 | There is no promise to pay for the invoice selected | Space: object requires documentation | ||
| 62 | Test run; no changes executed | Space: object requires documentation | ||
| 63 | The promise for invoice &1 &2 &3 can be confirmed | Space: object requires documentation | ||
| 64 | Account for document & & & locked by user & | Space: object requires documentation | ||
| 65 | Promise to pay for invoice & & & locked by user & | Space: object requires documentation | ||
| 66 | Invoice & & &: | Space: object requires documentation | ||
| 67 | No invoice selected with an open amount not equal to zero | Space: object requires documentation | ||
| 68 | Customer &1 has not been created in any company code of segment &2 | The short text describes the object sufficiently | ||
| 69 | Customer &2 is subject to legal dunning procedure in company code &1 | The short text describes the object sufficiently | ||
| 70 | Customer has more than 100 invoices; see long text | Space: object requires documentation | ||
| 71 | Promise to pay for &1 from customer &2 (CoCode &3) | The short text describes the object sufficiently | ||
| 72 | Promise to pay of &1 from customer &2 (CoCode &3) is locked by &4 | The short text describes the object sufficiently | ||
| 73 | Promise to pay of &1 from customer &2 (CoCode &3) is valuated with &4 | The short text describes the object sufficiently | ||
| 74 | Promise to pay of &1 from customer &2 (CoCode &3) has been confirmed | The short text describes the object sufficiently | ||
| 75 | Promise to pay of &1 from customer &2 (CoCode &3) can be confirmed | The short text describes the object sufficiently | ||
| 76 | Locking error: user &3 is editing promise from customer &1 (CoCode &2) | The short text describes the object sufficiently | ||
| 77 | State of promise for &1 from customer &2 (CoCode &3) not changed | The short text describes the object sufficiently | ||
| 78 | Promise for &1 from customer &2 (CoCode &3): valuation not possible | Space: object requires documentation | ||
| 79 | There are no open items for which a dispute case can be created | Space: object requires documentation | ||
| 80 | No items selected | Space: object requires documentation | ||
| 81 | There are no dispute cases for the invoices selected | Space: object requires documentation | ||
| 82 | Enter a selection criterion | Space: object requires documentation | ||
| 83 | No customer found; check the selection criteria | Space: object requires documentation | ||
| 84 | Enter a currency | Space: object requires documentation | ||
| 85 | Enter an amount receivable | Space: object requires documentation | ||
| 86 | All customers selected participate in the debit memo procedure | Space: object requires documentation | ||
| 87 | Business partner &1 was not translated into a customer | The short text describes the object sufficiently | ||
| 88 | Select exactly one dispute case | The short text describes the object sufficiently | ||
| 89 | Select at least one item from the selected company code &1 | The short text describes the object sufficiently | ||
| 90 | No item in company code &1 for which a case can be created | The short text describes the object sufficiently | ||
| 91 | No invoices for dispute case selected | The short text describes the object sufficiently | ||
| 92 | No dispute cases for the selected credit items | The short text describes the object sufficiently | ||
| 93 | There are no resubmissions for the selected invoice | The short text describes the object sufficiently | ||
| 94 | There are no notes for the selected invoice | The short text describes the object sufficiently | ||
| 95 | There are no invoices for the selected resubmission | The short text describes the object sufficiently | ||
| 96 | There are no invoices for the selected note | The short text describes the object sufficiently | ||
| 97 | Attachments for these note types are not supported | Space: object requires documentation | ||
| 98 | Notes have already been deleted, refresh the display | The short text describes the object sufficiently | ||
| 99 | Resubmissions have already been deleted, refresh the display | The short text describes the object sufficiently | ||
| 100 | Additional list entries for other note types have been created | The short text describes the object sufficiently | ||
| 101 | No note key has been defined for note type &1 in BAdI implementation | The short text describes the object sufficiently | ||
| 102 | Cannot display history | Space: object requires documentation | ||
| 103 | Special G/L indicator &1 is not allowed for document &2 &3 | Space: object requires documentation | ||
| 104 | Cleared residual items with reference to promise to pay | Space: object requires documentation | ||
| 105 | Several promises to pay active for an invoice | Space: object requires documentation | ||
| 106 | Clearing of partial payment for a promise to pay is not possible | Space: object requires documentation | ||
| 107 | Change partial payment with promise to pay kept | Space: object requires documentation | ||
| 108 | Clearing for item with promise to pay kept has been reset | Space: object requires documentation | ||
| 109 | Change partial payments for promises to pay individually | Space: object requires documentation | ||
| 110 | Invoice reference was not changed | Space: object requires documentation | ||
| 111 | Select exactly one resubmission | The short text describes the object sufficiently | ||
| 112 | You cannot change completed resubmissions | The short text describes the object sufficiently | ||
| 113 | Select at least one note | The short text describes the object sufficiently | ||
| 114 | Select at least one resubmission | The short text describes the object sufficiently | ||
| 115 | Only select one note | The short text describes the object sufficiently | ||
| 116 | Resubmission event is in the past | The short text describes the object sufficiently | ||
| 117 | Resubmission date is in the past | The short text describes the object sufficiently | ||
| 118 | Customer will not appear on worklist before &1 | Space: object requires documentation | ||
| 119 | No resubmission created during customer contact | The short text describes the object sufficiently | ||
| 120 | No promise to pay created during customer contact | The short text describes the object sufficiently | ||
| 121 | No dispute case created during customer contact | The short text describes the object sufficiently | ||
| 122 | Time of customer contact cannot be in the future | The short text describes the object sufficiently | ||
| 123 | Select exactly one customer contact | The short text describes the object sufficiently | ||
| 124 | &1 dispute cases have been voided | The short text describes the object sufficiently | ||
| 125 | &1 promises to pay have been voided | The short text describes the object sufficiently | ||
| 126 | No note was created during the customer contact | The short text describes the object sufficiently | ||
| 127 | Enter a resubmission date earlier than 31.12.9999 | The short text describes the object sufficiently | ||
| 128 | Select one or more customer contacts | The short text describes the object sufficiently | ||
| 129 | &1 promises to pay have this invoice number | The short text describes the object sufficiently | ||
| 130 | &1 promises to pay do not have this invoice number | The short text describes the object sufficiently | ||
| 131 | Error updating the promise to pay for invoice &1: | The short text describes the object sufficiently | ||
| 132 | No blling document available for selected invoice | The short text describes the object sufficiently | ||
| 133 | The receivables for the head office are displayed in a separate window | The short text describes the object sufficiently | ||
| 134 | Missing display authorization for all company codes of segment | The short text describes the object sufficiently | ||
| 135 | You do not have display authorization for all company codes of segment | The short text describes the object sufficiently |
History
| Last changed on/by | 20130531 | SAP | |
| SAP Release Created in | 2004_1_470 |