WRMA_FI - Messages for RMA
The following messages are stored in message class WRMA_FI: Messages for RMA.
It is part of development package WRMA_FI in software component LO-RFM-OBS. This development package consists of objects that can be grouped under "Inbound Interface for RMA Revaluation".
It is part of development package WRMA_FI in software component LO-RFM-OBS. This development package consists of objects that can be grouped under "Inbound Interface for RMA Revaluation".
Message Nr ▲ | Message Text |
|---|---|
| 000 | No Data Exists |
| 001 | RMA profile &1 does not exist |
| 002 | Table &3 does not have an entry for application &1 and condition type &2 |
| 003 | Table &3 does not have an entry for appl. &1 and condition meaning &2 |
| 004 | Table &3 does not have an entry for BI cond. type &1 and cond. type &2 |
| 005 | Table &2 does not have an entry for BI condition type &1 |
| 006 | Tax code or tax JurCode (tax-free) missing for company code &1 |
| 007 | No calculation procedure determined (procedure determ. and RMA profile) |
| 008 | Site &1 is not relevant for RMA (no RMA profile assigned) |
| 009 | No entry for customer number &1 of site in table &2 |
| 010 | The transferred message is inconsistent |
| 011 | Application log handle does not exist (internal error) |
| 012 | Transferred field &1 does not have valid content; class &2 |
| 013 | Material &2 already exists for plant &1 |
| 014 | RMA posting run &1 does not exist |
| 015 | RMA is not active in this client |
| 016 | The transferred currency, &1, differs from company code currency &2 |
| 017 | The data for company code &1 is inconsistent |
| 018 | No entries for FI update condition types in table &1 |
| 019 | Incorrect call of method &1 in class &2 |
| 020 | Entry in table &1 for application &2 and meaning &3 incorrect |
| 021 | No entry in table &3 for application &1 and meaning &2 |
| 022 | Condition type &1 missing in schema &2 |
| 023 | The "Provision" flag is not allowed for condition type &1 |
| 024 | Only calculation rule &1 is allowed for condition type &2 |
| 025 | Only calculation rule &1 is allowed for condition type &2 |
| 026 | No entries in calculation schema &1 |
| 027 | Basic formula &3 missing at step &2 in schema &1 |
| 028 | Subtotal &3 missing at step &2 in scheme &1 |
| 029 | Condition type &1 does not have any allowed &2 condition types |
| 030 | "Manual" flag not set in step &2 of schema &1 |
| 031 | Condition meaning &1 has multiple non-statistical conditions in schema &2 |
| 032 | Condition type &1 in schema &2 differs from FI update cond. type &3 |
| 033 | No condition category should be assigned to condition type &1 |
| 034 | No reference value should be assigned to condition type &1 |
| 035 | No reference steps are assigned to condition type &2 in schema &1 |
| 036 | Condition type &2 groups the various condition meanings in schema &1 |
| 037 | Condition type &2 should not have any reference steps in schema &1 |
| 038 | Externally assigned update cond. type &1 is statistical in schema &2 |
| 039 | Condition type &1 is not statistical in schema &2 |
| 040 | Condition type &1 is missing in schema &2 |
| 041 | FI update condition type &1 is statistical in schema &2 |
| 042 | The document to cancel, &1, is not relevant for RMA |
| 043 | Document &1 has a different billing doc. type (&2) than doc. &3 (cancel.) |
| 044 | Billing document type &1 for payment type &2 is not relevant for RMA |
| 045 | Billing document type &1 for payment type &2 has application &3 |
| 046 | Method &1 of class &2 was called incorrectly |
| 047 | Cannot create agency document |
| 048 | Error during &1 of table &2 |
| 049 | Incorrect grouping of condition types with cond. meaning &1 in schema &2 |
| 050 | Additional statistical conditions with condition meaning &2 in schema &1 |
| 051 | Site &1 in item &2 differs from site &3 in the header |
| 052 | Field &1 in item &2 does not contain a valid value |
| 053 | The RMA transfer run (run number &1) must be canceled by another run |
| 054 | Condition type &1 has an invalid condition class, &2 |
| 055 | &1 has value &2 and cannot be converted to &3 |
| 056 | Condition type &1 cannot be a condition for an invoice list |
| 057 | Account key entered at step &2 of schema &1 (statistical) |
| 058 | No account key for accruals in schema &1 at step &2 |
| 059 | BI condition type &1 occurs multiple times in the data for item &2 |
| 060 | Condition type &1 is assigned multiple times for item &2 via table &3 |
| 061 | Item &1: statist./non-statist. conditions determined for cond. meaning &2 |
| 062 | RMA posting run missing for document &1 |
| 063 | RMA posting run for canceled document &1 (cancellation doc. &2) missing |
| 064 | Document &1 can only be canceled using an RMA program |
| 065 | The agency document has status &1 and therefore cannot be saved |
| 066 | Agency documents can only be created by an RMA program |
| 067 | Could not determine posting run data for document &1 |
| 068 | RMA condition data missing for condition type &1 |
| 069 | RMA condition data for condition type &1 is incorrect |
| 070 | Billing document type &1 does not have application &2 |
| 071 | Cancellation billing document type &1 does not have application &2 |
| 072 | Billing document type &1 is not flagged as relevant for RMA |
| 073 | Cancellation billing document type &1 is not flagged as relevant for RMA |
| 074 | Field &1 of billing document type &2 must have value &3 |
| 075 | Field &1 of cancellation billing document type &2 must have value &3 |
| 076 | Field &1 of payment type &2 must have value &3 |
| 077 | Field &1 of billing document type &2 must be set |
| 078 | Field &1 of cancellation billing document type &2 must be set |
| 079 | Field &1 of payment type &2 must be set |
| 080 | Enter at least a value of &1 (or no value at all) |
| 081 | You cannot set field &1 of billing document type &2 |
| 082 | You cannot set field &1 of cancellation billing document type &2 |
| 083 | You cannot set field &1 of payment type &2 |
| 084 | Condition type &1 does not have condition meaning &2 |
| 085 | No entries for application &1 and BI condition type &2 in table &3 |
| 086 | The transferred data is inconsistent; class &1 |
| 087 | Fiscal year variant &1 differs from that of company code &2 |
| 088 | Agency document &1 will be created |
| 089 | Agency document &1 will be canceled by agency document &2 |
| 090 | RMA posting run has been processed completely |
| 091 | RMA posting run has been processed by a cancellation run |
| 092 | RMA posting run is already being processed by IDoc &1 |
| 093 | Agency document &1 cannot be canceled |
| 094 | The data of the RMA cancellation run is inconsistent |
| 095 | No tax code is required for the RMA |
| 096 | You cannot cancel a cancellation run |
| 097 | There is no application log to display |
| 098 | Posting date &1 for variant &2 is in period &3 and not in &4 |
| 099 | FI period &1 is still open. Archiving not allowed |
| 100 | --- Messages for BW Extraction ------------------------------------------ |
| 101 | Control data for stock transfer sales price missing: &1/&2 &3/&4 |
| 102 | Extract data for material document incomplete: &1 &2 &3 |
| 103 | Error in extraction document: &1 &2 |
| 104 | Document not found: &1 &2 &3 |
| 105 | Removal for putaway missing: &1 &2 &3 |
| 106 | Post the goods issue for purchase order &1 &2 first |
| 107 | Transferred parameters not unique |
| 109 | Site and fiscal year variant do not match |
| 150 | --- Messages for Master Data -------------------------------------------- |
| 151 | Revaluation at retail profile &1 not allowed for RMA |
| 152 | The article has a different profit center (&1) than the site (&2) |
| 153 | Ledger &1 has a different fiscal year variant: &2 |
| 154 | Distribution chain &1/&2, plant &3: Set splitting type to 1 (Explode) |
| 155 | Value-based inventory management possible for RMA site: Customer &1 |
| 156 | No plant found with RMA profile assigned |
| 157 | No company code is configured in SAP BW for RMA |
| 158 | Configure a G/L account for chart &1, key &2 |
| 159 | Maintain a standard hierarchy for profit center accounting |
| 160 | No RMA plant found with profit center assigned |
| 161 | Reorganization plan active for profit centers |
| 200 | --- Messages for IDoc Inbound ------------------------------------------- |
| 201 | An IDoc can only have one header segment |
| 300 | --- Messages RMA Reports ----------------------------------------- |
| 301 | There are entries to be deleted |
| 302 | &1 entries have been deleted |
| 303 | &1 entries cannot be deleted. (FI period is still open) |
| 304 | There are no entries to be deleted |
| 305 | No data could be selected |
| 306 | No fiscal year has been transferred |
| 307 | Operator &1 is not allowed in selection of fiscal years |
| 308 | Data can only be deleted up to fiscal year &1 |
| 309 | Data only deleted up to fiscal year &1 |
| 310 | Entries for fiscal year &1 cannot be deleted |
| 311 | Enter a number of years |
| 312 | Maximum entry is fiscal year &1 |
| 313 | Enter site and fiscal year |
| 314 | No RMA posting run exists with number &1 |
| 315 | Selection using RMA posting run number is not possible |
| 316 | No data exists for selection |
| 317 | The selected data could not be displayed in the ALV |
| 318 | Payment type &1 and billing types (&2/&3) are valid for RMA |
| 319 | No relevant sites could be selected |
| 320 | 1 entry has been deleted |
| 321 | No data exists |
| 322 | An entry cannot be deleted. (FI period is still open) |
| 323 | &1 entries cannot be deleted |
| 324 | An entry cannot be deleted |
| 325 | Program will not delete entry (posting date is still current) |
| 326 | Program will not delete &1 entries (posting date is still current) |
| 327 | No entries for testing exist |
| 328 | Too many AC posting periods remain open for company code |