Message Number list used by SAP ABAP Program SEA_SEXT2_F01 (Include SEA_SEXT2_F01)
SAP ABAP Program
SEA_SEXT2_F01 (Include SEA_SEXT2_F01) is using
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
| 1 | CL_SEA_MESSAGES - 139 | Editing could cause service implementation inconsistency | ||
| 2 | CL_SEA_MESSAGES - 152 | XSD Types are not supported for Aggregated or Core data types | ||
| 3 | CL_SEA_MESSAGES - 151 | No Data Types correspond to the selection criteria | ||
| 4 | CL_SEA_MESSAGES - 150 | ES Repository only supports Data Types, XSD Types are not supported | ||
| 5 | CL_SEA_MESSAGES - 149 | Enter XSD Type | ||
| 6 | CL_SEA_MESSAGES - 148 | Enter Data Type | ||
| 7 | CL_SEA_MESSAGES - 147 | Current ESR only supports cardinality "0..1", all others are reset | ||
| 8 | CL_SEA_MESSAGES - 143 | Do you want to generate proxy for Data Type Enhancement '&1'? | ||
| 9 | CL_SEA_MESSAGES - 140 | Do you want to create the ESR content for '&1'? | ||
| 10 | CL_SEA_MESSAGES - 153 | Data Type search criteria is too short | ||
| 11 | CL_SEA_MESSAGES - 138 | Do you want to continue? | ||
| 12 | CL_SEA_MESSAGES - 137 | Editing the DTE can cause service implementation inconsistency. | ||
| 13 | CL_SEA_MESSAGES - 136 | Proxy of object '&1' might be already used in BAdI implementations. | ||
| 14 | CL_SEA_MESSAGES - 135 | Proxy already generated | ||
| 15 | CL_SEA_MESSAGES - 134 | Regenerate proxy for Data Type Enhancement '&1'? | ||
| 16 | CL_SEA_MESSAGES - 132 | Do you want to delete the BAdI implementation '&1'? | ||
| 17 | CL_SEA_MESSAGES - 130 | Starting SOA Manager failed | ||
| 18 | CL_SEA_MESSAGES - 129 | Starting SOA Manager for '&1' | ||
| 19 | CL_SEA_MESSAGES - 166 | Creation of ES Repository content failed | ||
| 20 | CL_SEA_MESSAGES - 179 | Transaction canceled; Service Extension Workbench is not available | ||
| 21 | CL_SEA_MESSAGES - 178 | The DTE will be regenerated in ESR. Do you want to proceed? | ||
| 22 | CL_SEA_MESSAGES - 177 | Enter Type for the Data Type Enhancement item | ||
| 23 | CL_SEA_MESSAGES - 176 | Select a BAdI line | ||
| 24 | CL_SEA_MESSAGES - 175 | Select a Data Type Enhancement line | ||
| 25 | CL_SEA_MESSAGES - 174 | No BAdI definition exists. Added fields cannot be mapped | ||
| 26 | CL_SEA_MESSAGES - 171 | Deletion of ES Repository content failed | ||
| 27 | CL_SEA_MESSAGES - 169 | Deletion of BAdI implementation failed | ||
| 28 | CL_SEA_MESSAGES - 128 | Do you want to delete the ESR content for &1? | ||
| 29 | CL_SEA_MESSAGES - 165 | Deletion of DTE proxy failed | ||
| 30 | CL_SEA_MESSAGES - 164 | Creation of DTE proxy failed | ||
| 31 | CL_SEA_MESSAGES - 163 | Some of the restrictions cannot be interpreted for this type | ||
| 32 | CL_SEA_MESSAGES - 161 | Details of a non XSD Type cannot be modified | ||
| 33 | CL_SEA_MESSAGES - 160 | Switch to edit mode first | ||
| 34 | CL_SEA_MESSAGES - 156 | No input help is available in display mode | ||
| 35 | CL_SEA_MESSAGES - 155 | Occurrences value is not supported by SEW | ||
| 36 | CL_SEA_MESSAGES - 154 | DTE contains an anonymous inner type which cannot be edited by SEW | ||
| 37 | CL_SEA_MESSAGES - 036 | Service Interface Tree cannot be rendered | ||
| 38 | CL_SEA_MESSAGES - 046 | The Data Type Enhancement has been saved successfully | ||
| 39 | CL_SEA_MESSAGES - 045 | The Data Type Enhancement has been changed successfully | ||
| 40 | CL_SEA_MESSAGES - 042 | Select a Data Type to create Enhancement | ||
| 41 | CL_SEA_MESSAGES - 041 | No Data Type Enhancements found for selected service | ||
| 42 | CL_SEA_MESSAGES - 040 | Select Software Component Version | ||
| 43 | CL_SEA_MESSAGES - 039 | Only one Data Type Enhancement can be edited/displayed at a time | ||
| 44 | CL_SEA_MESSAGES - 038 | Fill name and/or type for the element | ||
| 45 | CL_SEA_MESSAGES - 037 | Table cannot be rendered | ||
| 46 | CL_SEA_MESSAGES - 047 | Enter Name for the Data Type Enhancement item | ||
| 47 | CL_SEA_MESSAGES - 035 | Data Type Enhancement not created/updated. Check the Application Log | ||
| 48 | CL_SEA_MESSAGES - 030 | Data Type Enhancement element not selected | ||
| 49 | CL_SEA_MESSAGES - 029 | No elements added to the Data Type Enhancement | ||
| 50 | CL_SEA_MESSAGES - 028 | Name and/or namespace for the new Data Type Enhancement not specified | ||
| 51 | CL_SEA_MESSAGES - 027 | Select a line | ||
| 52 | CL_SEA_MESSAGES - 024 | Enterprise Service cannot be found | ||
| 53 | CL_SEA_MESSAGES - 023 | Class editor could not be open | ||
| 54 | CL_SEA_MESSAGES - 015 | No BAdI definition found in the implementation of ES &1 | ||
| 55 | CL_SEA_MESSAGES - 089 | Failed to call the where used list functionality | ||
| 56 | CL_SEA_MESSAGES - 114 | DTE &1 has been deleted successfully | ||
| 57 | CL_SEA_MESSAGES - 113 | Activating change list after deletion failed | ||
| 58 | CL_SEA_MESSAGES - 111 | Do you want to delete the proxy of &1? | ||
| 59 | CL_SEA_MESSAGES - 101 | Proxy is up to date. No changes necessary. | ||
| 60 | CL_SEA_MESSAGES - 100 | Proxy already exists. Do you want to regenerate it? | ||
| 61 | CL_SEA_MESSAGES - 099 | Confirmation | ||
| 62 | CL_SEA_MESSAGES - 098 | Select only one Data Type Enhancement | ||
| 63 | CL_SEA_MESSAGES - 097 | Proxy has been generated for enhancement '&1' | ||
| 64 | CL_SEA_MESSAGES - 008 | Generation of implementation class &1 was successful | ||
| 65 | CL_SEA_MESSAGES - 082 | Starting WS Navigator for '&1' | ||
| 66 | CL_SEA_MESSAGES - 078 | Starting WS Navigator failed | ||
| 67 | CL_SEA_MESSAGES - 065 | No Connection to ES Repository | ||
| 68 | CL_SEA_MESSAGES - 056 | There is no BAdI implementation class for &1 service | ||
| 69 | CL_SEA_MESSAGES - 055 | No service has been selected yet | ||
| 70 | CL_SEA_MESSAGES - 051 | Could not start the value help | ||
| 71 | CL_SEA_MESSAGES - 049 | Proxy already generated for &1. Editing is allowed with restrictions | ||
| 72 | CL_SEA_MESSAGES - 048 | Namespace and/or SWCV for Data Type Enhancement element not specified |