RETAIL_ST_ODATA - Messages for use in Fiori Retail Store Applications
The following messages are stored in message class RETAIL_ST_ODATA: Messages for use in Fiori Retail Store Applications.
It is part of development package ODATA_RETAIL_ST_COMMON in software component LO-RFM-STO-FIO. This development package consists of objects that can be grouped under "OData Service - Retail Store Common".
It is part of development package ODATA_RETAIL_ST_COMMON in software component LO-RFM-STO-FIO. This development package consists of objects that can be grouped under "OData Service - Retail Store Common".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Cannot delete product &1 from the list |
| 001 | No store assigned |
| 002 | Cannot get authorized stores for user &1 |
| 003 | User &1 does not have any authorized stores |
| 004 | Cannot get the store assigned to user &1 |
| 005 | Cannot assign store to user &1 |
| 006 | Not authorized for store &1 |
| 007 | System encountered an error when processing the request; check the logs |
| 008 | No authorization for goods movement |
| 009 | Not available in language &1 |
| 010 | &1&2&3&4 |
| 011 | Internal error in processing of request; action aborted: &3&4 in &1 |
| 012 | Dynamic SQL error in "&1": row &2 at &3 (&4) |
| 013 | No store assigned to user &1 |
| 014 | The key of entity &1 must be fully specified |
| 015 | Entity set can be accessed only by navigating from entity type(s) "&1" |
| 016 | Entity set "&1" can be accessed intern. only by providing a list of IDs |
| 017 | EAN128 bar code decoding not possible;return code was &1 (legend: &2&3&4) |
| 018 | A technical error occurred reading storage locations in database |
| 019 | Date out of calendar; check factory calendar of store &1 |
| 021 | Bar code &1 not recognized |
| 022 | Storage location for product &1 in site "&2" cannot be determined |
| 023 | Purchasing group for site "&1" and product "&2" cannot be determined |
| 024 | Company code for site "&1" cannot be determined |
| 025 | Purchasing organization for site "&1" cannot be determined |
| 026 | &1 &2 |
| 027 | |
| 028 | |
| 030 | Select one customizing schema as standard. |
| 031 | RFC destination &1 does not exist. |
| 032 | Unprocessed sales data are not available (schema '&2'). |
| 033 | Unprocessed sales data are still used in '&1'. Deactivate? |
| 034 | The active BADI_RTST_CAR returns inactive. First deactivate the BAdI. |
| 040 | Maintain at least one of the following fields: &1 or &2. |
| 041 | Enter a value in field '&1'. |
| 042 | Enter a value in field '&1' for schema '&2'. |
| 043 | Enter a positive value in field '&1' for schema '&2'. |
| 044 | Schema '&2' is still assigned to &3 sites. For example to '&1'. |
| 059 | RFC destination for call to SAP CAR in not set in Customizing |
| 060 | Cannot execute call to SAP CAR due to system or communication failure |
| 061 | SAP Cust. Act. Rep. Integration is not enabled in Customizing. |
| 100 | Posting of package &1 for &2 (&3) started (&4). |
| 101 | Pre-check for post started (&1). |
| 102 | Pre-check for post finished in &1 seconds. |
| 103 | Pre-check for post finished with errors in &1 seconds. |
| 104 | Post started (&1). |
| 105 | Post cannot be started because pre-check revealed errors for all items. |
| 106 | Post finished successfully in &1 sec and material document &2/&3 created. |
| 107 | Post finished with errors in &1 seconds (after successful pre-check). |
| 108 | Posting of package &1 not started due to RFC error '&2&3' (&4). |
| 109 | Post not started due to wrong server group &1. Check in Customizing. |
| 110 | Post not started due to missing resources on server group &1. |
| 111 | Parallel posting of &1 packages (size &2) on server group &3 started (&4) |
| 112 | Parallel posting of &1 packages on server group &2 finished in &3 sec. |
| 113 | Sequential posting of &1 packages (size &2) started (&3). |
| 114 | Sequential posting of &1 packages finished in &2 seconds. |
| 115 | Post of product &1 (&2) was canceled. Check previous message. |
| 116 | Parallel posting is not possible. |
| 117 | Post for products with retail movement code &1 started. |
| 118 | Post for products with retail movement code &1 finished. |
| 150 | Post for product &1 finished and quantity reduced from &3 to &2 &4. |
| 200 | Parallel processing profile (&1) does not exist. Check Customizing. |
| 201 | Server group (&1) does not exist or has no application server(s). |
| 202 | No application server of the server group (&1) is available. |
| 203 | Parallel processing profile (&1) incomplete. Check Customizing. |
| 300 | Print job is already closed. Create a new print job. |
| 301 | Print job is not opened. Open a print job to start printing. |
| 302 | Print job is already open. Reuse this print job or create a new one. |
| 303 | You can only print forms with technology '&1' with this print job. |
| 304 | Print job cannot be opened: &1. |
| 305 | Print job cannot be printed: &1. |
| 306 | Print job cannot be closed: &1. |
| 307 | Supported form technologies: XFA2 for cloud and XFA/XFA2 for on premise. |
| 400 | Application log cannot be displayed. |
| 401 | For more information, check application log &1 in transaction slg1. |
| 402 | &1 entries selected for deletion. |
| 403 | No filter conditions set. |
| 404 | Buffered unprocessed sales for &1 store(s) were deleted. |
| 450 | Previous update of unprocessed sales for store &1 took too long. |
| 451 | Previous update of unprocessed sales for store &1 failed. |
| 500 | Errors while aggregating unprocessed sales in external system. |
| 501 | Duplicate entries received from SAP CAR System (RFC Destination: &1). |