CL_SEA_MESSAGES - Message class for SEW tool
The following messages are stored in message class CL_SEA_MESSAGES: Message class for SEW tool.
It is part of development package SEA_SEW_CORE in software component BC-ESI-SEW. This development package consists of objects that can be grouped under "Core component of SEW".
It is part of development package SEA_SEW_CORE in software component BC-ESI-SEW. This development package consists of objects that can be grouped under "Core component of SEW".
Message Nr ▲ | Message Text |
|---|---|
| 000 | No spot has been found for the BAdI definition &1 |
| 001 | Enhancement spot &1 not found |
| 002 | BAdI interface &1 not found |
| 003 | Enhancement spot &1 found for &2 BAdI definition |
| 004 | BAdI implementation to be generated: &1 |
| 005 | Class name is missing (generation is not yet evaluated) |
| 006 | BAdI implementation class to be generated: &1 |
| 007 | Generation of implementation class &1 was not successful |
| 008 | Generation of implementation class &1 was successful |
| 009 | Implementation class name: &1 |
| 010 | Generation of &1 BAdI implementation was successful |
| 011 | Service name and Namespace or Impl class name should be provided as input |
| 012 | No proxy class found for service &1 in namespace &2 |
| 013 | Proxy class &1 not found |
| 014 | No implementation class could be identified for service &1 |
| 015 | No BAdI definition found in the implementation of ES &1 |
| 016 | Enter a valid package name |
| 017 | Action canceled |
| 018 | &1 |
| 019 | Interface &1 found for &2 BAdI definition |
| 020 | Multiple BAdI definitions found, auto choice not possible |
| 021 | Generation of &1 BAdI implementation element was successful |
| 022 | Request &1 does not exist |
| 023 | Class editor could not be open |
| 024 | Enterprise Service cannot be found |
| 025 | Data Type Enhancement cannot be found |
| 026 | A transport request is needed |
| 027 | Select a line |
| 028 | Name and/or namespace for the new Data Type Enhancement not specified |
| 029 | No elements added to the Data Type Enhancement |
| 030 | Data Type Enhancement element not selected |
| 031 | Select a service |
| 032 | No error description found |
| 033 | Element name already used or missing element type |
| 034 | Invalid Software Component Version or Namespace |
| 035 | Data Type Enhancement not created/updated. Check the Application Log |
| 036 | Service Interface Tree cannot be rendered |
| 037 | Table cannot be rendered |
| 038 | Fill name and/or type for the element |
| 039 | Only one Data Type Enhancement can be edited/displayed at a time |
| 040 | Select Software Component Version |
| 041 | No Data Type Enhancements found for selected service |
| 042 | Select a Data Type to create Enhancement |
| 043 | No Data Type Enhancement selected |
| 044 | The chosen type is not extendable |
| 045 | The Data Type Enhancement has been changed successfully |
| 046 | The Data Type Enhancement has been saved successfully |
| 047 | Enter Name for the Data Type Enhancement item |
| 048 | Namespace and/or SWCV for Data Type Enhancement element not specified |
| 049 | Proxy already generated for &1. Editing is allowed with restrictions |
| 050 | Selected service &1 is inconsistent |
| 051 | Could not start the value help |
| 052 | No proxy found |
| 053 | No ES Repository object found |
| 054 | Prefix &1 is required |
| 055 | No service has been selected yet |
| 056 | There is no BAdI implementation class for &1 service |
| 057 | &1 services found with name "&2" and namespace "&3" |
| 058 | The implementation of ES &1 contains more than one BAdI definition |
| 059 | &1 exception is caught in method &2. Details: &3 |
| 060 | SWCV guid or service name and namespace must be supplied |
| 061 | The provided SWCV name is invalid |
| 062 | Data type enhancement &1 not found in namespace &2 |
| 063 | Data type &1 not found in namespace &2 |
| 064 | More than one DTE found for name &1 and namespace &2 |
| 065 | No Connection to ES Repository |
| 066 | Enter an enteprise service name |
| 067 | Software component version name was not found |
| 068 | Cannot read service interface proxy. Proxy metadata is null |
| 069 | Cannot read service interface proxy. Proxy method is null |
| 070 | Canno read service interface proxy. Method's parameters table is null |
| 071 | Cannot read service interface proxy. Dictionary object is null |
| 072 | Cannot read service interface proxy. Object type is null |
| 073 | Cannot read service interface proxy. Object name is null |
| 074 | Cannot read service interface proxy. Proxy metadata is null |
| 075 | The enterprise service cannot be found: &1 |
| 076 | Parsing of DTE xml failed with error code &1 |
| 077 | Cannot find schema method |
| 078 | Starting WS Navigator failed |
| 079 | The Data Type Enhancement '&1' has been created/updated successfully |
| 080 | WS Navigator URL cannot be generated |
| 081 | No binding found for the service |
| 082 | Starting WS Navigator for '&1' |
| 083 | Starting WS Navigator |
| 084 | No error description found |
| 085 | There is no enterprise service '&1' in namespace '&2' |
| 086 | There is no data type enhancement '&1' in namespace '&2' |
| 087 | Deletion of DTE proxy failed with the following error(s): '&1' |
| 088 | Creation of DTE proxy failed with the following error(s): '&1' |
| 089 | Failed to call the where used list functionality |
| 090 | The BAdI name '&1' was not found |
| 091 | No BAdI Interface found for the BAdI defintion |
| 092 | The chosen name '&1' is not unique |
| 093 | Generation of implementation class '&1' was not successful |
| 094 | The DTE subelements are not defined correctly |
| 095 | Data Type Enhancement '&1' not created/updated |
| 096 | Could not get the values for name and namespace |
| 097 | Proxy has been generated for enhancement '&1' |
| 098 | Select only one Data Type Enhancement |
| 099 | Confirmation |
| 100 | Proxy already exists. Do you want to regenerate it? |
| 101 | Proxy is up to date. No changes necessary. |
| 102 | The deletion of class '&1' has failed |
| 103 | The deletion of enhancement implementation '&1' was successful |
| 104 | The deletion of enhancement implementation element '&1' was successful |
| 105 | The deletion of enhancement implementation '&1' has failed |
| 106 | The deletion of enhancement implementation element '&1' was successful |
| 107 | The deletion of the enhancement has failed |
| 108 | Failed to read the enhancement implementation/element name |
| 109 | The deletion of enhancement implementation element '&1' has failed |
| 110 | Can't delete DTE with generated proxy |
| 111 | Do you want to delete the proxy of &1? |
| 112 | Could not delete DTE &1 |
| 113 | Activating change list after deletion failed |
| 114 | DTE &1 has been deleted successfully |
| 115 | Cannot edit DTE with already generated proxy |
| 116 | Unable to find the elements of the DTE ' &1' |
| 117 | The given elements not found in the DTE |
| 118 | Generation of class '&1' was successful |
| 119 | Generation of interface '&1' was successful |
| 120 | The deletion of class &1 was successful |
| 121 | Data Type Enhancement '&1' is already used in BAdI implementation classes |
| 122 | No 'sequence' node was found below the 'group' node |
| 123 | 'Schema' node has no attributes |
| 124 | 'Schema' node has no attribute 'xmlns' |
| 125 | Restriction elemement '&1' has no attribute 'value' |
| 126 | 'Extension' element has no attributes |
| 127 | 'Extension' element has no attribute 'base' |
| 128 | Do you want to delete the ESR content for &1? |
| 129 | Starting SOA Manager for '&1' |
| 130 | Starting SOA Manager failed |
| 131 | Proxy already generated for &1 but not used by other objects |
| 132 | Do you want to delete the BAdI implementation '&1'? |
| 133 | Subelement '&1' cannot be deleted/changed because it is in use |
| 134 | Regenerate proxy for Data Type Enhancement '&1'? |
| 135 | Proxy already generated |
| 136 | Proxy of object '&1' might be already used in BAdI implementations. |
| 137 | Editing the DTE can cause service implementation inconsistency. |
| 138 | Do you want to continue? |
| 139 | Editing could cause service implementation inconsistency |
| 140 | Do you want to create the ESR content for '&1'? |
| 141 | DTE with name '&1' and namespace '&2' was created in package '&3' |
| 142 | DTE with name '&1' and namespace '&2' was deleted from package '&3' |
| 143 | Do you want to generate proxy for Data Type Enhancement '&1'? |
| 144 | Cannot find proxy version for DTE '&1' in namespace '&2' |
| 145 | Data Type Enhancement '&1' has been deleted from the ES Repository |
| 146 | Invalid name and/or namespace of Enterprise Service |
| 147 | Current ESR only supports cardinality "0..1", all others are reset |
| 148 | Enter Data Type |
| 149 | Enter XSD Type |
| 150 | ES Repository only supports Data Types, XSD Types are not supported |
| 151 | No Data Types correspond to the selection criteria |
| 152 | XSD Types are not supported for Aggregated or Core data types |
| 153 | Data Type search criteria is too short |
| 154 | DTE contains an anonymous inner type which cannot be edited by SEW |
| 155 | Occurrences value is not supported by SEW |
| 156 | No input help is available in display mode |
| 157 | Cannot find any BAdI spot. Do you want to extend this service? |
| 158 | No BAdI spot found for this service |
| 159 | BAdI '&1' ('&2') internal_usage flag is '&3' |
| 160 | Switch to edit mode first |
| 161 | Details of a non XSD Type cannot be modified |
| 162 | '&1' restriction must have a positive integral value |
| 163 | Some of the restrictions cannot be interpreted for this type |
| 164 | Creation of DTE proxy failed |
| 165 | Deletion of DTE proxy failed |
| 166 | Creation of ES Repository content failed |
| 167 | &1&2&3&4 |
| 168 | &1 &2 &3 &4 |
| 169 | Deletion of BAdI implementation failed |
| 170 | Creation of BAdI implementation failed |
| 171 | Deletion of ES Repository content failed |
| 172 | Activation of ES Repository content failed |
| 173 | Possible whiteSpace attribute values are: preserve, replace, collapse. |
| 174 | No BAdI definition exists. Added fields cannot be mapped |
| 175 | Select a Data Type Enhancement line |
| 176 | Select a BAdI line |
| 177 | Enter Type for the Data Type Enhancement item |
| 178 | The DTE will be regenerated in ESR. Do you want to proceed? |
| 179 | Transaction canceled; Service Extension Workbench is not available |