/SCDL/AF - Adapter Framework
The following messages are stored in message class /SCDL/AF: Adapter Framework.
It is part of development package /SCDL/ADAPTER_INTERFACES in software component SCM-EWM-DLP. This development package consists of objects that can be grouped under "Service Adapter Interfaces".
It is part of development package /SCDL/ADAPTER_INTERFACES in software component SCM-EWM-DLP. This development package consists of objects that can be grouped under "Service Adapter Interfaces".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Error in business configuration: &1 |
| 001 | Document category &1 is not valid |
| 002 | Document type &1 is not valid |
| 003 | Item type &1 is not valid |
| 004 | Item category &1 is not valid |
| 005 | Combination of document category &1 and document type &2 is not valid |
| 006 | Document category and type could not be determined |
| 007 | Document category &1 has no follow-on doc. category |
| 008 | The combination of document cat. &1 and item cat. &2 is not valid |
| 009 | The combination of document cat. &1 and item type &2 is not valid |
| 010 | Error accessing location master data: '&1' |
| 011 | The item category and type could not be determined |
| 012 | Process type &1 is not valid |
| 013 | Location &1 not found |
| 014 | No location found for partner &1 |
| 015 | The exception code &1 is not valid |
| 016 | Shipping condition &1 is not valid |
| 017 | Delivery priority &1 is not valid |
| 018 | The combination of document type &1 and item cat. &2 is not valid |
| 019 | Error in location/organizational unit administration |
| 020 | Error during access to business partner master data: &1 |
| 021 | Business partner assignement not unique: Check &1 |
| 022 | Business partner &1 does not exist |
| 023 | Error in accessing business partner administration |
| 024 | No assigned business partner exists for customer &1 (in system &2) |
| 025 | No assigned business partner exists for supplier &1 (in system &2) |
| 026 | No assigned business partner exists for plant &1 (in system &2) |
| 027 | No assigned customer exists for business partner &1 (in system &2) |
| 028 | No assigned supplier exists for business partner &1 (in system &2) |
| 029 | Business partner with GUID &1 does not exist |
| 030 | Error accessing product master data: &1 |
| 031 | Product &1 does not exist |
| 032 | Error accessing product data administration |
| 033 | No business partner exists for sales organization &1 (in system &2) |
| 034 | No assigned sales org. for business partner &1 exists (in system &2) |
| 035 | No sales organization is maintained for ERP delivery &1 |
| 036 | No default sales organization could be found for delivery &1 in ERP |
| 037 | No default sales organization could be found for delivery &1 in SAP EWM |
| 038 | Activity "&1" not allowed; Reason: No status permits it |
| 039 | &1 is already &2; activity "&3" not executed |
| 040 | Error in the status management: &1 |
| 041 | Activity "&1" is not permitted; reason: status "&2" has value "&3" |
| 042 | Internal error: status change at wrong document level |
| 043 | Internal error: inconsistent data in status management |
| 044 | Insufficient data for status operation |
| 045 | Document locked; changes are not currently possible |
| 046 | Error in status management |
| 047 | Activity is not permitted; reason: status "&1" has value "&2" on &3 |
| 048 | Error during assignment of user &1 to business partner &2 |
| 049 | User assignment for planner &1 cannot be changed. |
| 050 | Error: call method & in class & |
| 051 | Shadow FD &1 detected |
| 052 | User &1 does not have an assigned business partner |
| 053 | There is more than one business partner assigned to user &1 |
| 060 | Obsolete, use /SCDL/AF 061 |
| 061 | No authorization for warehouse request or delivery and activity "&1" |
| 062 | Error in authorization administration |
| 070 | Error in field control administration |
| 080 | System partner profile &1 is not valid |
| 081 | Partner profile &2 is not valid |
| 082 | System date profile &1 is not valid |
| 083 | Date profile &2 is not valid |
| 084 | Error in date/time administration |
| 085 | Error in partner processing administration |
| 086 | Process code profile &1 is not valid |
| 090 | Error in search help of the service |
| 100 | Address with ID &1 or handle &2 was not created |
| 101 | Storage location &1 is not valid |
| 102 | Address handle is not filled |
| 103 | Address (ID &1, handle &2 or referece &3) cannot be deleted |
| 104 | The address with the ID &1 cannot be read |
| 105 | The address for handle &1 cannot be read |
| 106 | Handle &1 cannot replace reference &2 |
| 107 | No additional reference &2 can be created for Address ID &1 |
| 108 | The address with ID &1 could not be saved |
| 109 | The address with ID &1 could not be copied |
| 110 | The handle is initial |
| 111 | Error in address management |
| 112 | Address &1 is not of type 1 |
| 113 | Address &1 is not of type 1 |
| 114 | Address type is invalid |
| 115 | Address cannot be saved; parameter error |
| 116 | Address cannot be saved; address does not exist |
| 117 | Address cannot be saved; handle already exists |
| 118 | Address cannot be saved; internal error |
| 119 | Address cannot be saved |
| 130 | Error accessing the reference service |
| 131 | Sytem profile for reference &1 is not valid |
| 132 | Reference profile &1 is not valid |
| 150 | Date type &1 is not valid |
| 200 | Action "&1" could not be converted |
| 250 | Choose a different document type |
| 260 | Default process type &1 is not valid |
| 300 | Error in handling unit administration |