CWYAP1000-1999: SAP Resource Adapter - Common components
- CWYAP1001
- The application-specific information could not be processed for the following business object: <insert_0>. Error: <insert_1>.
- Explanation
- An error occurred while retrieving the application-specific information for the business object. Use the enterprise metadata discovery(EMD) generated objects. If you have modified the business objects, make sure the structure matches that detailed in the user documentation.
- Response
- Check the business object metadata and verify that it is correct.
- CWYAP1002
- UnsupportedEncodingException is occurred. Exception message <insert_0>.
- Explanation
- SAP JCA Adapter does not support the character encoding provided.
- Response
- Verify that the adapter supports the specified character encoding.
- CWYAP1003
- The following error occurred. Exception <insert_0>, Message <insert_1>. Cause : <insert_2>, Message <insert_3>.
- Explanation
- Exception occurred , See the exception details for more information .
- Response
- An exception occurred, See the exception details .
- CWYAP1004
- SAPManagedConnection Configuration property value =<insert_0> is invalid. See the adapter user guide for property usage.
- Explanation
- The configuration property is invalid.
- Response
- Correct the SAP Configuration property value by assigning a valid value. see the adapter user guide for property usage.
- CWYAP1005
- Business object <insert_0>. The object type could not be determined.
- Explanation
- The object type could not be determined. Check the business object level application-specific information.
- Response
- Either correct the business object level application-specific information or generate the business objects again using enterprise metadata discovery.
- CWYAP1006
- execute() with signature javax.resource.cci.InteractionSpec ispec, javax.resource.cci.Record input,javax.resource.cci.Record output is not supported.
- Explanation
- execute() with signature javax.resource.cci.InteractionSpec ispec, javax.resource.cci.Record input,javax.resource.cci.Record output is not supported.
- Response
- Invoke the execute command passing the proper arguments. Upgrade the SAP Adapter to version 6.1.
- CWYAP1007
- A JCO exception occurred while the SAP Adapter was processing. Group: <insert_0>. Key: <insert_1>. Error Message: <insert_2>. Cause: <insert_3>.
- Explanation
- A JCO exception occurred.
- Response
- This is a generic SAP JCO exception raised by the SAP system. See the exception details for more information.
- CWYAP1008
- Property: <insert_0> cannot be set. Business object <insert_1> cannot be set.
- Explanation
- The adapter is unable to process this property for the specified business object.
- Response
- The property may not exist in the business object or the property name may be misspelled. Verify the business object structure.
- CWYAP1009
- The RFC function <insert_0> cannot be found in this SAP instance.
- Explanation
- The RFC function <insert_0> could not be found in the SAP system.
- Response
- Ensure that the function exists in the SAP application to which you are connecting.
- CWYAP1010
- Business object <insert_0> cannot be created in namespace <insert_2>.
- Explanation
- Unable to create the business object <insert_0> in namespace <insert_2>.
- Response
- Ensure that the namespace is correctly configured.
- CWYAP1011
- A value for maxLength for property: <insert_0>, business object <insert_1> cannot be obtained.
- Explanation
- Unable to get maxLength for property : <insert_0> , business object <insert_1>.
- Response
- Check to see that this property exists, and ensure that maxLength is specified.
- CWYAP1012
- The connection to the SAP application is lost.
- Explanation
- The SAP adapter is unable to connect to SAP the system.
- Response
- The SAP adapter is unable to connect to the SAP system. If the problem persists, restart the SAP Adapter.
- CWYAP1013
- GatewayHost <insert_0> is configured, but GatewayService is not. Either configure both or neither.
- Explanation
- GatewayHost and GatewayService need to be configured in parallel.
- Response
- Either set GatewayService or remove GatewayHost.
- CWYAP1014
- GatewayService <insert_0> is configured, but GatewayHost is not. Either configure both or neither.
- Explanation
- GatewayHost and GatewayService need to be configured in parallel.
- Response
- Either set GatewayHost or remove GatewayService.
- CWYAP1015
- An unrecoverable error occurred: The transaction.properties file cannot be found in either the <insert_0> JAR file or in the class path.
- Explanation
- The transaction.properties file could not be found. This file is used by the SAP adapter to get the transaction property.
- Response
- Create the transaction.properties file and add it to the class path.
- CWYAP1016
- The connection was expecting a local transaction, but a local transaction is not supported by the <insert_0> interface.
- Explanation
- Not all interface types support local transactions.
- Response
- Check to see that the interface type supports local transactions.
- CWYAP1017
- Error:Configuration property SystemNumber <insert_0> is invalid. (This information is provided in the user action section).
- Explanation
- An SAP system expects the SystemNumber to be a numeric value.
- Response
- Enter a valid value for the SystemNumber property. The SystemNumber property must be numeric.
- CWYAP1018
- Error:A value is needed for the <insert_0> property if there is a value for the MessageServerHost property.
- Explanation
- An SAP system expects the SystemNumber to be a numeric value.
- Response
- Enter a valid value for the SystemNumber property
- CWYAP1019
- An exception occurred while connecting to the SAP system. Error message: <insert_0>.
- Explanation
- An exception occurred while making the connection to the SAP application. The SAP adapter is unable to connect using the provided logon credentials.
- Response
- Check the details of the exception message.
- CWYAP1020
- An exception occurred while disconnecting from the SAP system. Error message: <insert_0>.
- Explanation
- An exception occurred while attempting to disconnect from the SAP system.
- Response
- Check the details of the exception message.
- CWYAP1021
- Error: Object type <insert_0> is undefined.
- Explanation
- The business object type does not have a valid value.
- Response
- Revise the object type in the business object. The one provided is not one of the valid values
- CWYAP1022
- The <insert_0>( method with signature javax.resource.cci.InteractionSpec ispec,javax.resource.cci.Record input,javax.resource.cci.Record output is not supported.
- Explanation
- The adapter supports only a certain signature for the execute() method.
- Response
- Use a different execute() method.
- CWYAP1023
- The <insert_0> method is not implemented.
- Explanation
- The adapter does not support the call() method for invocation.
- Response
- Invoke the adapter by using a different method.
- CWYAP1024
- An error occurred while getting the 'TYPE' application-specific information from the business graph for: <insert_0>. Error message: <insert_1>. Valid values are BAPI, ALE and QISS. Refer to the SAP adapter user guide for details.
- Explanation
- An exception occurred while determining the interface type.
- Response
- Check the 'TYPE' application-specific information value for the business graph; the value should be 'BAPI' for the BAPI interface .
- CWYAP1025
- An invalid operation was found for the interface <insert_0>. The following operations are valid for this interface: <insert_1>.
- Explanation
- The ALE interface supports the Execute operation. The BAPI interface supports the following operations: Create, UpdateWithDelete, Delete, and Retrieve. The QISS interface supports the RetrieveAll and the Exists operation.
- Response
- Verify that the operation value set while invoking interface is valid.
- CWYAP1026
- The application-specific information could not be parsed. The SapBusinessObjectMetadata.xsd file might either be missing, outdated or contain multiple versions. Exception <insert_0>.
- Explanation
- The SAP adapter cannot parse the business object application-specific information.
- Response
- Verify that the SapBusinessObjectMetadata file is present and valid and that there is only one version.