CRMN_REPORT - Reporting: Messages
The following messages are stored in message class CRMN_REPORT: Reporting: Messages.
It is part of development package CRM_REPORT in software component CRM-BTX-ANA-RFW. This development package consists of objects that can be grouped under "Operative Reporting in CRM".
It is part of development package CRM_REPORT in software component CRM-BTX-ANA-RFW. This development package consists of objects that can be grouped under "Operative Reporting in CRM".
Message Nr ▲ | Message Text |
|---|---|
| 100 | No business partners created |
| 101 | & documents found for selection criteria |
| 102 | & documents found |
| 103 | No changes made to the selection criteria |
| 104 | &1 added to your favorites |
| 105 | Selected lines added to your favorites |
| 106 | Select at least one line |
| 107 | Enter different currencies |
| 108 | Choose a transaction |
| 109 | No partial document processing allowed for transaction type &1 |
| 110 | & entries were found for the selection criteria |
| 111 | Selection option not supported for component field |
| 112 | Not all components can be identified |
| 113 | Make further restrictions to your selection by component |
| 114 | Only the first 100 components are used for selection |
| 115 | Selection according to different objects is not supported |
| 116 | Only the first 100 installed bases are used for the selection |
| 117 | Increase restrictions for selection according to installed base |
| 118 | Selection option not supported for installed base field |
| 119 | Too many partners for entry; search cannot start |
| 120 | PARTNER_NO_SECOND/PARTNER_PFT_SECOND not usable due to authorization |
| 121 | Changes have been made |
| 122 | Order due date: RFC system error in accessed system |
| 123 | Order due date: RFC communication after successful initialization |
| 124 | Order due date: Undefined error in APO system |
| 125 | Order due date: Problem in APO business logic |
| 126 | No application error exists for the changes to be made |
| 127 | &1 cannot be changed |
| 128 | Enter card type and number |
| 129 | Enter card number and type |
| 130 | Enter at least one selection criterion |
| 131 | Object not found |
| 132 | No selection of campaign contacts when a * is entered in partner field |
| 133 | Enter at least one selection criterion for items |
| 134 | Opportunity speed: Customizing in SAP namespace is inconsistent |
| 135 | Error aggregating currency amounts; amounts set to 0 |
| 136 | Error converting currency; enter source currency |
| 137 | Error converting currency amounts; amounts set to 0 |
| 138 | &1 |
| 139 | Only operator 'EQ' supported for single value field &1 |
| 140 | Single value field &1 cannot be used multiple times |
| 141 | Date format invalid |
| 142 | No program ID available |
| 143 | Only equals operator allowed in search for product and product selection |
| 144 | Search contains too many partner functions |
| 145 | Only single values allowed in search for product and product selection |
| 146 | Search may contain only one entry for status area |
| 147 | Some entries already exist in the favorites |
| 148 | You cannot use field &1 more than once |
| 150 | Error when deleting session buffer |
| 151 | Error when deleting buffer table |
| 152 | Service date fields cannot be combined with other date fields |
| 153 | Error converting quantities; quantities set to 0 |
| 154 | Search by product selection not allowed without entering product |
| 155 | Search for category ID not possible without process type |
| 156 | Search contains fields where wild card search is not allowed |
| 157 | & documents not found for selection criteria |
| 200 | Field &1 added to DataSource &2 (selection &3) |
| 201 | Extend BI Content manually in the BW client |
| 202 | Field &1 mapped to InfoObject &2 (type &3) |
| 203 | Field &1 deleted from DataSource &2 |
| 204 | Generate extension also in target system |
| 205 | Error transporting mapping information |
| 206 | Process object &1 &2 in the original system &3 |
| 207 | Select a field first |
| 208 | Select a reporting application |
| 209 | Field added to list |
| 210 | Reporting field list empty; add a field |
| 211 | Reporting field list cleared |
| 212 | Reporting application does not support items |
| 213 | Field type not supported |
| 214 | Field name too long |
| 215 | Field not supported for search in interactive reporting |
| 216 | Include error |
| 217 | No mapping information for this field available |
| 218 | Field already included |
| 219 | Document contains errors and cannot be processed for Billing |