SOR_FRM_EXT_SRCE_MSG - Message class for create SOR from external source
The following messages are stored in message class SOR_FRM_EXT_SRCE_MSG: Message class for create SOR from external source.
It is part of development package RAP_SD_SLS_AUTOEXTRN in software component SD-SLS-IMP-DOX. This development package consists of objects that can be grouped under "SD Restful ABAP Programming(Creat SO - Automatic Extraction)".
It is part of development package RAP_SD_SLS_AUTOEXTRN in software component SD-SLS-IMP-DOX. This development package consists of objects that can be grouped under "SD Restful ABAP Programming(Creat SO - Automatic Extraction)".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1&2&3&4 |
| 001 | Could not convert extracted country/region "&1" into internal key. |
| 002 | Extracted delivery date "&1" was invalid. |
| 003 | Data extraction service failed to create client. |
| 004 | Data extraction service is temporarily unavailable. |
| 005 | Country/Region not proposed |
| 009 | Cannot get extraction result for the file due to parameter error. |
| 010 | Exact match of "&1" in &2 |
| 011 | Fuzzy match of "&1" for &2 |
| 023 | Sales order request number for the extracted file is &1. |
| 024 | Line item &2: Cannot convert extracted crcy (ISO) "&1" into internal crcy |
| 025 | Item &1: Could not convert extracted UoM "&2" into internal key. |
| 027 | Enterprise search error: Cannot determine sold-to party. |
| 028 | Enterprise search error: Cannot determine ship-to party. |
| 029 | Sold-to party &1 was determined with reference to order creation history. |
| 030 | Ship-to party &1 was determined with reference to order creation history. |
| 031 | Sold-to party &1 has not been defined for sales area &2/&3/&4. |
| 032 | Sold-to party &1 has been determined via &2. |
| 033 | Ship-to party &1 has been determined via &2. |
| 034 | Product &1 has been determined via &2. |
| 035 | For numeric header field &1, extracted value "&2" is invalid. |
| 036 | For numeric field &2 in line item &1, extracted value "&3" is invalid. |
| 037 | In line items &1, extracted item number "&2" exists more than once. |
| 038 | Header:Cannot convert extracted currency (ISO) "&" into internal currency |
| 039 | Header: Cannot convert extracted UoM (ISO) "&" into internal UoM |
| 040 | Data extraction service has started to extract data for the retry request |
| 041 | Data extraction service could not upload file: invalid file content. |
| 042 | Data extraction service could not upload file: malware detected. |
| 043 | Data extraction service could not upload file: file pages exceeding 50. |
| 044 | A technical error occurred. Contact your system administrator. |
| 045 | The requested operation is invalid. |
| 047 | Sold-to party not determined |
| 048 | Ship-to party not determined |
| 049 | No product can be determined for item &1. |
| 050 | Contact your system admin to set up the required communication scenario. |
| 051 | Archiving failed. The customer is used in a sales order request. |
| 052 | Sold-to party &1 was determined via exact search. |
| 053 | Sold-to party &1 was determined via fuzzy search. |
| 054 | Ship-to party &1 has been determined via exact search. |
| 055 | Ship-to party &1 was determined via fuzzy search. |
| 056 | Item &1: Product &2 was determined via exact search. |
| 057 | Item &1: Product &2 was determined via fuzzy search. |
| 060 | Product determination: Exact match of "&1" in product master |
| 061 | Product determination: Exact match of "&1" in customer material master |
| 062 | Product detn: Exact match of "&1" in additional customer material master |
| 070 | Failed to connect to data extraction service. |
| 071 | Data extraction has started. |
| 072 | Retry extraction: Failed to connect to data extraction service.& |
| 073 | Retry extraction: Data extraction has started. |
| 074 | Data extraction was completed. |
| 075 | Data extraction failed. |
| 076 | Document currency proposed from company code &1 |
| 077 | Sales order type defaulted to standard order (OR) |
| 078 | Requested delivery date set to first valid date in extracted item data |
| 079 | Item &1: UoM not proposed. System cleared UoM and requested quantity. |
| 080 | Could not convert extracted currency "&2" into internal key. |
| 081 | Extracted currency was missing. |
| 095 | BAdI call: Could not propose "&1" for requested delivery date. |
| 096 | BAdI call: Item number &1 exists more than once. |
| 097 | BAdI call: Could not create an item for item number &1. |
| 099 | BAdI call: Could not propose "&1" for UoM. |
| 100 | BAdI call: Sales order request items were overwritten. |
| 101 | BAdI call: Sales order request header was overwritten. |
| 103 | Sales area &1/&2/&3 was determined from sold-to party &4. |
| 104 | Ship-to party &1 from master data determination invalid for sales area |
| 105 | Sales area &1/&2/&3 was determined from ship-to party &4. |
| 106 | Sold-to party determination: Fuzzy match of "&1" for &2 |
| 107 | Ship-to party determination: Fuzzy match of "&1" for &2 |
| 108 | Could not determine a unique sales area from sold-to or ship-to party. |
| 109 | Sales area &1/&2/&3 from ship-to party &4 and valid for sold-to party |
| 111 | Product determination: Fuzzy match of "&1" for &2 |
| 112 | Sold-to party determination: Exact match of "&1" for &2 |
| 113 | Sold-to party determination: Retrieved from sales order request &1 |
| 114 | Ship-to party determination: Retrieved from sales order request &1 |
| 115 | Item &1: Extracted UoM was missing. |
| 116 | UoM proposed |
| 117 | Item &1: UoM was proposed based on extracted UoM "&2". |
| 118 | Item &1: Requested quantity not proposed |
| 119 | Item &1: Extracted quantity "&2" is not a numeric value. |
| 120 | Item &1: Extracted quantity was missing. |
| 121 | Requested quantity proposed |
| 122 | Item &1: Requested quantity was copied from extracted quantity "&2". |
| 123 | Customer reference not proposed |
| 124 | Extracted purchase order number was missing or invalid. |
| 125 | Customer reference proposed |
| 126 | Customer reference was copied from extracted purchase order number "&1". |
| 127 | Requested delivery date not proposed |
| 128 | Extracted delivery date was missing. |
| 129 | Requested delivery date proposed |
| 130 | Requested delivery date was copied from extracted delivery date "&1". |
| 131 | Sold-to party determined |
| 132 | Ship-to party determined |
| 133 | Ship-to party &1 is valid for sales area &2/&3/&4. |
| 134 | Sales area not determined |
| 135 | Sales area determined |
| 136 | Item &1: Product determined |
| 137 | Item &1: Product &2 determined with reference to order creation history |
| 138 | Product determination: Retrieved from item &1, sales order request &2 |
| 139 | Item &1: Product not determined |
| 140 | BAdI call: &1 was overwritten. |
| 141 | BAdI call: In item &1, &2 was overwritten. |
| 142 | Item &1: Product &2 returned via fuzzy search, but invalid for sales area |
| 143 | Controlled document type: Report an incident to component CA-ML-DOX. |
| 144 | Input limit exceeded for trial account. Please retry next week. |
| 145 | Extraction service unavailable. Ask administrator to check OAuth setup. |
| 146 | Check your oAuth 2.0 client settings in the communication system. |
| 147 | Item &1: Could not convert extracted delivery date "&2" into a date. |
| 148 | |
| 149 | Extraction service unavailable. Ask administrator to check RFC connection |
| 150 | Check your host name in the communication system. |