/EACC/DMM - Landkarte (BW-Obj. zu Acc-Views) // dynamische Verwendung
The following messages are stored in message class /EACC/DMM: Landkarte (BW-Obj. zu Acc-Views) // dynamische Verwendung.
It is part of development package /EACC/DM_OBJMAP in software component FIN-BAC. This development package consists of objects that can be grouped under "Data Retention: Map of the Participating Objects".
It is part of development package /EACC/DM_OBJMAP in software component FIN-BAC. This development package consists of objects that can be grouped under "Data Retention: Map of the Participating Objects".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Internal error |
| 001 | Error &1 calling up view maintenance for view &2 |
| 002 | Error &1 calling up maintenance for InfoCube &2 |
| 003 | Map copied from &1 to &2 |
| 004 | Map not copied |
| 005 | Context menu '&1' could not be loaded |
| 006 | Map deleted for data basis &1 |
| 007 | Internal error &1 &2 &3 &4 |
| 008 | This function is not yet supported |
| 009 | Configuration information transferred successfully |
| 010 | Configuration information could not be transferred |
| 011 | Communication problem with BW system &1 |
| 012 | Cube type &1 cannot be generated |
| 013 | DataSource &1 generated successfully |
| 014 | Metadata is inconsistent - check |
| 015 | Failure to generate |
| 016 | Object information contains errors (internal error) |
| 017 | The cluster characteristic was not transferred |
| 018 | Table &1 contains no entry for &2 &3 &4 |
| 019 | RFC destination for logical system '&1' could not be determined |
| 020 | Field &1 does not have an InfoObject assigned to it |
| 021 | No details could be queried for InfoObject &1 |
| 022 | Field &1 does not have the same type as InfoObject &2 (&3/&4) |
| 023 | No dimensions are assigned to field &1 |
| 024 | Dimension &1 contains characteristics of various types |
| 025 | All dimensions created must be used |
| 026 | Dimension &1 is not used |
| 027 | Characteristic &1 is compounded with characteristic &2, but &2 is missing |
| 028 | Unit &2 in key figure &1 is missing |
| 029 | Objet type of dimension &1 could not be determined (internal error) |
| 030 | InfoObject for field &1 could not be determined (internal error) |
| 031 | Metadata is consistent |
| 032 | Metadata is inconsistent |
| 033 | InfoCube &1 generated without errors |
| 034 | InfoCube &1 generated with warnings |
| 035 | Errors occurred during generation of InfoCube &1 |
| 036 | Error accessing remote system |
| 037 | &1&2&3&4 |
| 038 | The name of the InfoCube has not been set |
| 039 | Check whether InfoObject &1 is active in BW system &2 |
| 040 | Calculated key figures could not be read by InfoCube &1 (&2) |
| 041 | Dimension &1 does not meet the naming convention |
| 042 | Logical system &1 is not assigned to the data basis |
| 043 | No characteristics have been defined yet |
| 044 | No key figures have been defined yet |
| 045 | The DataSource will not be generated |
| 046 | The conversion rules were not queried by the view |
| 047 | The structure names were not queried by the journal |
| 048 | No name has been defined yet for the DataSource |
| 049 | Characteristic &1 in the view is not contained in the metadata |
| 050 | Key figure &1 in the view is not contained in the metadata |
| 051 | Characteristic &1 from the metatdata is not required by the view |
| 052 | Key figure &1 from the metatdata is not required by the view |
| 053 | The data retention metadata meet the requirements of the view |
| 054 | Data retention does not meet the requirements of the view |
| 055 | No interface multiprovider entered yet |
| 056 | Name of the DataSource not yet defined |
| 057 | Enter a data basis |
| 058 | The configuration of BTA Pure Profit Record could not be found |
| 059 | Interface structure &1 could not be read |
| 060 | No BW is connected to data basis &1 |
| 061 | The structure names are up to date |
| 062 | The structure names are not up to date |
| 063 | Structure names cannot be checked |
| 064 | Component &1 has type &2 and cannot have BW data (internal error) |
| 065 | Only one data supply flow is permitted for journal &1 |
| 066 | No BW system has yet been defined for storing the transaction data |
| 067 | No changes were made |
| 068 | Variant must be activated/generated first |
| 069 | Extractor could not be regenerated |
| 070 | Extractor regenerated successfully |
| 071 | Error during deletion of data supply flow |
| 072 | Transport request not written (&1) |
| 073 | Cube &1 is appropriate for view &2 |
| 074 | Cube &1 is not appropriate for view &2 |
| 075 | InfoObject &1 missing in Cube &2 |
| 076 | InfoObject &1 in Cubes &2 is not required |
| 077 | DataSource &1 is being used more than once |
| 078 | Use: Client &1 / data basis &2 |
| 079 | Provider &1 is being used more than once |
| 080 | Use: Data basis &1 / BW system &2 |
| 081 | Data stream &1/&2/&3 cannot be assigned - be careful |
| 082 | The system has found an error while checking the object name |
| 083 | The object names are not consistent |
| 084 | Name &1 of the InfoCube begins with a number |
| 085 | Provider &1 is assigned to more than one data supply flow |
| 086 | Provider &1 is not assigned to a data supply flow |
| 087 | Select the costs and revenue journal |
| 088 | Provider &1 is not assigned to a data basis |
| 089 | Restrictions when using more than one data supply flow |
| 090 | Restrictions when using transactional cubes for plan data |
| 091 | Restrictions when using MultiProviders |
| 092 | Invalid dimension key &1 |