CRM_SERV_ACCOUNTING - CRM_Service: Messages for R/3 Integration
The following messages are stored in message class CRM_SERV_ACCOUNTING: CRM_Service: Messages for R/3 Integration.
It is part of development package CRM_SERVICE_ACCOUNTING in software component CRM-BTX-COI-SRV. This development package consists of objects that can be grouped under "CRM Service: Controlling Integration".
It is part of development package CRM_SERVICE_ACCOUNTING in software component CRM-BTX-COI-SRV. This development package consists of objects that can be grouped under "CRM Service: Controlling Integration".
Message Nr ▲ | Message Text |
---|---|
000 | Program can only be called up using the Implementation Guide |
001 | No target system found |
002 | Several target systems determined; check the proposal |
010 | Specify a service order ID and an item number. |
011 | The service order item you specified, doesn�t exist. |
101 | Warnings occurred during cost calculation in ERP system &1 |
102 | Error when connecting to ERP: &1 |
201 | Process type is missing |
202 | Process type is not valid |
203 | Only process types for service contracts and orders allowed |
204 | Item category is missing |
205 | Item category is not valid |
206 | Only item categories for service contracts and orders allowed |
207 | You cannot remove relevance for Revenue Accounting after release |
208 | Status of company code &1 cannot be determined |
209 | Status of migration package &1 of company code &2 cannot be determined |
210 | Business Function &1 is not active |
211 | Message log cannot be created or updated |
212 | Load is started |
213 | Reset is started |
214 | Simulation mode is on |
215 | Migration package &1 and company code &2 not in status for initial load |
216 | Company code &1 not in status for initial load |
217 | Remote communication failed: &1 |
218 | Business transaction &1 not loaded because of database issue |
219 | Business trans. &1 not loaded because of lock or authoriz. issue |
220 | Business trans. &1 not loaded: Billing doc. locked or no change authoriz. |
221 | Business transaction &1 and others in package not loaded as update failed |
222 | Business transaction &1 not reset because of database issue |
223 | Business transaction &1 not reset because of lock or authoriz. issue |
224 | Business transactions not reset because update failed |
225 | Business trans. &1 not reset: Billing doc. locked or no change authoriz. |
226 | Enrichment processing started |
227 | Transaction &1, Item &2: Reference Type: &3, Reference ID: &4 assigned |
228 | No organizations in Service could be determined for company code &1 |
229 | No active BADI implementation exists for CRM_SERVICE_REVACC_RELEVANCE |
230 | Enrichment processing finished |
231 | Destination of ERP site cannot be determined |
232 | Transfer date is not consistent or missing |
233 | Transaction &1, item &2: Update failed |
234 | Transaction &1: Processing skipped as reading in change mode failed |
235 | Transaction &1 set to relevant for Revenue Accounting |
236 | Program started in background, see application log for details |
237 | Package &1 generated, number of transactions selected: &2 |
238 | No transactions were selected |
239 | Cannot determine RFC destination for &1 |
240 | Sales Document &1, Item &2: Reference Type: &3, Reference ID: &4 assigned |
241 | Load finished |
242 | Reset finished |
243 | Relevance of transaction &1 is reset |
244 | Error when deleting table &1 for transaction &2, item &3 |
245 | Transaction &1: Processing skipped as accounting relevance is active |
246 | Transaction &1: Processing skipped as predecessor exists |
247 | Own logical system cannot be determined |
248 | No service transactions were selected |
249 | No sales transactions were selected |
250 | Package &1 generated, number of service transactions selected: &2 |
251 | Package &1 generated, number of sales transactions selected: &2 |
252 | Relevance type missing in billing documents and due list items |
301 | Package &1 doesn't exist in Revenue Accounting. Enter existing package. |
302 | Customizing status of the package &1 couldn't be determined |