FKKB_DM - Integration FSCM-Dispute Management / FI-CA
The following messages are stored in message class FKKB_DM: Integration FSCM-Dispute Management / FI-CA.
It is part of development package FKKB_DM in software component FI-CA. This development package consists of objects that can be grouped under "Contract Accts Receivable and Payable - Dispute Management".
It is part of development package FKKB_DM in software component FI-CA. This development package consists of objects that can be grouped under "Contract Accts Receivable and Payable - Dispute Management".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Document is not included in a dispute case |
| 002 | Selection specifications incomplete - selection is required |
| 003 | "Correction for" and "Replacement for" are mutually exclusive |
| 004 | Specify document or case ID |
| 005 | Select a business partner |
| 006 | Case ID &1 was not found in any dispute case for partner &2 |
| 007 | Specify business partner and amount |
| 008 | You cannot specify a document number for this dispute type |
| 009 | Total amount of suitable items is &1 &2 |
| 010 | No line items found for the data specified |
| 011 | Disputed amount must not exceed &1 &2 |
| 012 | Internal dispute type &1 is not supported |
| 013 | Dispute Management is not active in company code &1 |
| 014 | Dispute Management is not active in any of the potential company codes |
| 015 | No authorization to create cases in company code &1 group &2 |
| 016 | No authorization to change cases in company code &1 group &2 |
| 017 | No authorization to display cases in company code &1 group &2 |
| 018 | Proposed dispute type was changed; check required |
| 019 | Correcting document and correction document &1 have same +/- sign |
| 020 | Replacement document and document &1 to be replaced have diff. +/- sign |
| 021 | Dispute type &2/reason &1 is not supported (case type: &3) |
| 022 | Specify both reason and dispute type |
| 023 | Dispute Management Is Not Active |
| 024 | Specify currency of dispute case |
| 025 | Case ID &1 is category "Missing Payment" and is not permitted here |
| 026 | Dispute case locked by user &1 |
| 027 | Invalid call of module &1 (error &2) |
| 028 | Enter a positive dispute amount |
| 029 | Only credit memos can be assigned manually |
| 030 | Credit memo &1 was indicated as a follow-up posting |
| 031 | Assignment can only be reset manually for credit memos |
| 032 | Assignment of credit memo &1 as follow-up posting was reset |
| 033 | Enter a To Date that is later than the From Date |
| 034 | Dispute case not found |
| 035 | No number range found for dispute cases |
| 036 | Dispute case created under case number &1 |
| 037 | Dispute case &1 does not exist |
| 038 | Clarification case &1 cannot be changed (external processing) |
| 039 | No documents found |
| 040 | Business function &1 cannot be activated |
| 041 | Unallowed change of dispute case &1 (internal reason: &2 to &3) |
| 042 | Enter both case types |
| 043 | Enter a valid status for external processing |
| 044 | Unallowed change of dispute case &1 (currency &2 to &3) |
| 045 | Unallowed change of dispute case &1 (partner &2 to &3) |
| 046 | Document &1 (currency &2) cannot be added to dispute case &3 (crcy &4) |
| 047 | Disputed amount (&1 &2) is greater than total amount (&3 &4) |
| 048 | Document &1 cannot be assigned to classification case &2 |
| 049 | Document &1 is not assigned to classification case &2 |
| 050 | You must specify a document number for this internal dispute type |
| 051 | Enter a case number or a CRM dispute case number |
| 052 | No authorization to create clarification cases of the case type &1. |
| 053 | No authorization to change clarification cases of the case type &1. |
| 054 | No authorization to display/read clarification cases of the case type &1. |
| 055 | Error during authorization check for clarification cases. |
| 056 | Saving of dispute case &1 rejected (event 1257) |
| 057 | Saving of dispute case rejected (event 1257) |
| 058 | Missing case type in the creation of the clarification case. |
| 059 | Alternative Currency for at Least one disputed doc. in clarification case |
| 060 | Use the "Manage Dispute Cases" app to create and change |
| 061 | Dispute case &1 already exists in system |
| 099 | & & & & |
| 100 | Internal error in module & & & |
| 101 | Error during creation of case ID |
| 102 | &1 documents were assigned to the dispute case |
| 103 | &1 documents were assigned to subsequent posting |
| 104 | &1 documents were assigned to dispute case |
| 105 | Document &1 was removed |
| 106 | &1 documents were removed |
| 107 | Document &1 was assigned to subsequent posting |
| 108 | Document &1 was assigned to the dispute case |
| 109 | Document &1 was assigned to the dispute case |
| 110 | Documents in follow-on posting are inconsistent. Update the data |
| 111 | Document &1 for business partner &2 does not exist |
| 112 | Document &1 for business partner &2 contract account &3 does not exist |
| 113 | Business partner &1 is locked: No new clarification case possible |
| 114 | Exception occurred during conversion for clarification case &1 |
| 115 | Conversion of clarification case in Dispute Management &1 successful |
| 116 | Notes for clarification case &1 could not be converted |
| 117 | Notes for clarification case in Dispute Management &1 were converted |
| 118 | Attachments for clar. case in Dispute Management &1 were converted |
| 119 | User &1 does not exist |
| 120 | Attachments for clarification case &1 could not be converted |
| 121 | Some attachments and notes are only visible in the Fiori app |
| 122 | Use of app not activated. Use transaction FPDM00 |
| 123 | Conversion status could not be updated for clarification case |
| 124 | Fiori app is not active. Conversion not possible |
| 125 | No authorization to display dispute case |
| 126 | Data inconsistency. Dispute case was changed by another user |
| 127 | Dispute case was created |
| 128 | Error during creation of dispute case |
| 129 | Please use Fiori app to display and maintain dispute case |
| 130 | Disputed object &1 with type &2 already exists in case &3 |
| 131 | Case &1 doesn't have disputed object &2 with type &3 |