CWYAP100001F: The external service wizard cannot connect to the SAP host system. Cause: {0}
Explanation: The external service wizard needs these properties to be entered correctly in order to connect to the SAP system. Refer to the adapter user documentation for more details about each of these properties.
User Action: Ensure that all the connection properties are correct and try again.
CWYAP100002F: The metadata tree could not be created for the adapter. Cause: {0}
Explanation: The external service wizard encountered an unrecoverable error while creating the tree-node structures and cannot proceed.
User Action: Ensure that all the connection properties are correct and try again.
CWYAP100003F: The top level tree nodes for the metadata discovery could not be loaded. Cause: {0}
Explanation: The static top-level nodes cannot be obtained. The external service wizard has encountered a severe error and cannot continue.
User Action: Check the connection properties and try to reconnect.
CWYAP100004E: The BOR metadata tree cannot be initialized. Error Code {0}: Detail: {1}
Explanation: The business object repository on the SAP system you are connecting to is either corrupt or is not configured properly.
User Action: Ensure that the business object repository is properly configured on the target SAP system.
CWYAP100005E: The ALE IDocs could not be retrieved from the system.
Explanation: The connection properties are not valid.
User Action: Ensure that the connected SAP system supports ALE metadata introspection.
CWYAP100006I: The external service wizard could not recognize the discovery criteria you entered.
Explanation: The asterisk (*) wildcard character has been found in an unexpected location.
User Action: Correct the placement of the wildcard character in the "Discover By Name" criteria.
CWYAP100007I: The external service wizard could not recognize the discovery criteria you entered.
Explanation: The asterisk (*) character can be used as a wildcard to represent zero or more characters either before or after alphanumeric characters. Searching by description is case sensitive. The expansion symbol (+) for the selected entry disappears if no items are found or if the discovery criteria is not valid.
User Action: Correct the placement of the wildcard character in the "Discover By Description" criteria.
CWYAP100008F: The tool context for the external service wizard cannot be set. Error: {0}
Explanation: The tool environment needs to create a tool context to pass to the discovery service for use until an SAP metadata connection is obtained.
User Action: Try restarting IBM Integration Designer and the external service wizard.
CWYAP100009E: Import configurations could not be generated for the selected nodes. Exception: {0}
Explanation: For every MetadataObject that is to be imported, a configuration needs to be captured. This configuration defines how the SAP MetadataObject is to be included in the generated service description.
User Action: Check the exception and take appropriate action.
CWYAP100010F: The external service wizard encountered an unrecoverable error while creating filtering properties for the tree nodes. Exception: {0}
Explanation: The external service wizard allows filtering of the nodes returned from a query but an error occurred while trying to display them in the tree.
User Action: See the log for more information.
CWYAP100011E: Object properties for the nodes cannot be created. Exception: {0}
Explanation: The external service wizard displays the description of each node when you hover over any node through object properties. These properties provide you with a better understanding of the associated metadata object.
User Action: Restart the external service wizard and try again.
CWYAP100012F: Selection properties cannot be created for the selected nodes. Exception: {0}
Explanation: The external service wizard is unable to generate the metadata properties for the selected nodes.
User Action: Verify that you entered the information correctly and try again.
CWYAP100013E: Selection properties cannot be created for the selected IDoc Objects. Exception: {0}
Explanation: The external service wizard cannot generate the metadata properties for the selected IDoc objects.
User Action: Verify that you entered the information correctly and try again.
CWYAP100014F: An error occurred while creating IDocs from the file. Exception: {0}
Explanation: The external service wizard can only generate IDoc objects from a valid IDoc file. Ensure that the file is properly formatted and accessible.
User Action: Verify that the IDoc file has been generated correctly from the SAP system.
CWYAP100015E: Selection properties cannot be created for the selected BAPI objects. Exception: {0}
Explanation: The external service wizard is unable to generate the metadata properties for the selected BAPI objects.
User Action: See the log for more information.
CWYAP100016E: Inbound connection configuration properties for the selected objects could not be created. Exception: {0}
Explanation: The configuration is used to exchange all the connection information; it is passed in the tooling environment, persisted to permanent storage, and synchronized with the runtime representation Java beans. Inbound connection configuration adds the methods to create and apply ActivationSpec properties and to retrieve the InboundConnectionType.
User Action: Try restarting the external service wizard and if the problem persists, contact IBM Software Support.
CWYAP100017E: ActivationSpec properties for the Inbound connection cannot be created. Exception: {0}
Explanation: The Inbound connection configuration must consist of properties that specify the ActivationSpec properties for Adapter for SAP. Examples of these properties are: SAP Host Name, SAP User name, and password. These properties can be configured through the WebSphere Application Server administrative console.
User Action: Try restarting the external service wizard, and if the problem persists, contact IBM Software Support.
CWYAP100018E: The adapter properties for the Inbound connection cannot be created. Exception: {0}
Explanation: The Inbound connection configuration must consist of properties that are specific to the adapter, such as adapter name, user name, log file name for the adapter, file size, trace file name, and size. Configuration of these properties failed. These properties can be configured later through the WebSphere Application Server administrative console.
User Action: Try restarting the external service wizard. If the problem persists, contact IBM Software Support.
CWYAP100019F: The external service wizard cannot create the managed connection factory properties for the outbound connection. Exception: {0}
Explanation: The outbound connection needs managed connection factory properties, which are used to establish a connection with the SAP system.
User Action: Try restarting the external service wizard and if the problem persists, contact IBM Software Support.
CWYAP100020E: Outbound connection configuration properties cannot be created for the selected objects. Exception: {0}
Explanation: The configuration is used for exchanging all of the connection information; it is passed in the tooling environment, persisted to permanent storage, and synchronized with the runtime representation Java beans. The outbound connection configuration adds the methods to create managed connection factory properties and to retrieve the OutboundConnectionType.
User Action: Try restarting the external service wizard, and if the problem persists, contact IBM Software Support.
CWYAP100021F: The adapter properties for the outbound connection cannot be created. Exception: {0}
Explanation: An exception occurred while adding the outbound connection configuration to the adapter properties.
User Action: Try restarting the external service wizard and if the problem persists, contact IBM Software Support.
CWYAP100022F: The language and codepage combination is not recognized.
Explanation: The SAP system you want to connect to must support these language and codepage values.
User Action: Refer to the SAP product documentation for the correct codepage value and re-enter it.
CWYAP100023W: No operations have been specified for the service artifacts.
Explanation: The external service wizard cannot determine the operations that are needed.
User Action: Specify at least one operation to be associated with the service artifacts.
CWYAP100024F: Service descriptions for the selected nodes in the {0} module cannot be created. Error: {1}
Explanation: The external service wizard encountered an error while creating the service descriptions.
User Action: Try restarting the external service wizard and if the problem persists, contact IBM Software Support.
CWYAP100025F: The metadata for the {0} property could not be set. Error: {1}
Explanation: This might be caused by an issue with the SAP system to which you are connected. The external service wizard encountered an error while populating the schema for the property.
User Action: Using the SAPGUI, check the metadata for the node you selected. If the problem persists, contact IBM Software Support.
CWYAP100026F: Service descriptions cannot be generated for the nodes you have selected.
Explanation: The external service wizard encountered an error while generating outbound service descriptions.
User Action: Try restarting the external service wizard and if the problem persists, contact IBM Software Support.
CWYAP100027F: An error occurred while setting the value for the {0} property. Error: {1}
Explanation: The external service wizard encountered an error while setting the value for the property.
User Action: Close the window and retry.
CWYAP1001E: The application-specific information could not be processed for the following business object: {0}. Error: {1}.
Explanation: An error occurred while retrieving the application-specific information for the business object. Use the objects generated by the external service wizard. If you have modified the business objects, make sure the structure matches the structure described in the user documentation.
User Action: Check the business object metadata and verify that it is correct.
CWYAP1002E: An UnsupportedEncodingException exception has occurred. Exception message: {0}
Explanation: Adapter for SAP does not support the character encoding that is provided.
User Action: Provide a valid, supported character encoding.
CWYAP1003E: The following error has occurred: Exception: {0}, Message: {1}. Cause: {2}, Message: {3}.
Explanation: See the exception details for more information.
User Action: See the exception details for information about the problem.
CWYAP1004E: The value for the SAPManagedConnection configuration property, {0}, is not valid.
Explanation: The value assigned to a configuration property is not valid.
User Action: Assign a valid value for the SAP configuration property. Refer to the adapter user documentation for more information about the properties and their use.
CWYAP1005E: The object type for the {0} business object could not be determined.
Explanation: The adapter is unable to determine the object type. This might be due to an unsupported message or to incorrect application-specific information in the business object.
User Action: Either correct the application-specific information at the business object level or generate the business object (or objects) again using the external service wizard.
CWYAP1006E: The execute function in the Interaction class with three arguments is not supported.
Explanation: The interaction supports the Interaction.execute (InteractionSpec, Record in) signature with two arguments.
User Action: Invoke the Interation.execute() command by passing one input Record object and one output Record object.
CWYAP1007E: A JCo exception occurred while the adapter was processing. Group: {0}. Key: {1}. Error Message: {2}. Cause: {3}.
Explanation: A JCo exception occurred.
User Action: This is a generic SAP JCo exception that is generated by the SAP system. See the exception details for more information.
CWYAP1008E: Property {0} cannot be set for the {1} business object.
Explanation: The property might not exist in the business object or the property name might be misspelled. The adapter cannot process this property for the specified business object.
User Action: Verify that the business object structure is correct.
CWYAP1009E: The RFC function {0} cannot be found in this SAP instance.
Explanation: The RFC function {0} could not be found in the SAP system.
User Action: Ensure that the function exists in the SAP application to which you are connecting.
CWYAP101001F: ALE IDocs could not be retrieved from the SAP system for the node {0}. Error: {1}
Explanation: To be able to introspect the IDocs you have selected, the external service wizard requires that the target SAP system is properly configured.
User Action: Make sure you have enough privileges to do metadata introspection on the target SAP system.
CWYAP101002F: No rows were found in the table {0}.
Explanation: The IDoc for the ALE node you have selected cannot be retrieved. The selected IDoc refers to a segment table that does not contain any rows.
User Action: Check the log for more information.
CWYAP101003E: There is no basic IDoc linked to the extension IDoc {0}. Exception: {1}
Explanation: An unrecoverable error occurred while locating the linked IDoc.
User Action: Check the log for more information.
CWYAP101004E: An error occurred while attempting to find a function in the SAP system. Exception: {0}
Explanation: A function needed for object generation was not found.
User Action: Ensure that the function exists in the target SAP system.
CWYAP101005F: Child objects for {0} could not be created. Exception: {1}
Explanation: This might be related to an issue with the SAP system to which you are connected.
User Action: Using the SAPGUI, check the metadata for the node you selected. If the problem persists, contact IBM Software Support.
CWYAP101006F: Metadata for object {0} could not be set. Exception: {1}
Explanation: Metadata could not be set for the specified object. This might be due to an issue with the SAP system to which you are connected.
User Action: Using the SAPGUI, check the metadata for the node you selected. If the problem persists, contact IBM Software Support.
CWYAP101007E: No segments were found for {0} for the release {1}. Error Code: {2}, Detail: {3}.
Explanation: The Enter the Release input control allows an earlier version of the IDoc type to be used for object generation. If the earlier version of the IDoc type has fewer segments than the current version, the SAP external service wizard might create a definition with missing segments, or the SAP external service wizard displays an error indicating that the generation of the business object was unsuccessful. This inconsistency is due to different versions of SAP requiring different API calls.
User Action: Check the target SAP system to see if there are segments belonging to the release you entered. Re-enter a later release.
CWYAP101008F: An IDoc type could not be found in the file before the segment and field lines were processed.
Explanation: An IDoc type was not found when parsing the file. An IDoc type must exist before the segments and fields are processed.
User Action: Generate the IDoc file from the SAP system again and run the SAP external service wizard with the new file.
CWYAP101009F: An error occurred while converting the value for the 'LEVEL' tag to an integer for segment {0} of the file you are trying to import. Exception: {1}
Explanation: An error occurred while trying to convert the string for the 'LEVEL' tag to an integer.
User Action: Generate the IDoc file from the SAP system again and run the SAP external service wizard with the new file.
CWYAP101010F: A general exception error occurred for {0} of {1}. Reason: {2}
Explanation: The external service wizard has encountered an error and cannot complete the current action.
User Action: See the exception message for more information.
CWYAP101011F: A general exception occurred in terminal {0}. Reason: {2}
Explanation: The external service wizard has encountered an error and cannot complete the current action.
User Action: See the exception message for more information.
CWYAP101012F: No BEGIN_SEGMENT_SECTION was found.
User Action: Generate the IDoc file from the SAP system again and run the SAP external service wizard with the new file.
CWYAP101014F: The {0} property maximum length could not be set properly because of the following exception: {1} The maximum length value will default to 255.
Explanation: An exception occurred when trying to set the maxLength property.
User Action: See the exception message for more information.
CWYAP101015F: An error occurred while calling function {0} because the function was not found. Error Code: {1}, Detail: {2}
Explanation: An exception occurred when trying to discover the IDocs.
User Action: Verify that the SAP system you are connected to has the function that could not be found.
CWYAP101016E: A general exception occurred while creating the ALE nodes. Error: {0}
Explanation: An exception occurred when trying to discover the IDocs.
User Action: Verify that the SAP system you are connected to is properly configured to do IDoc introspection.
CWYAP101017E: The internal language used to build the ALE nodes cannot be set. Error: {0}
Explanation: The external service wizard could not do a lookup for the internal language code in the table T002.
User Action: Verify that a correct language code is used.
CWYAP101018F: An error occurred while making a function call into the SAP system. Exception: {0}
Explanation: The values for the parameters that the function call is making into SAP may be incorrect.
User Action: Check the details of the exception message for more information about why the exception occurred.
CWYAP101019F: The child object {0} was not created. Exception: {1}
Explanation: A segment could not be created as a child object to the parent IDoc object.
User Action: Restart the external service wizard and try generating the IDoc again. If the problem persists, contact IBM Software Support.
CWYAP101020F: Metadata for one of the properties in object {0} could not be set. Exception: {1}
Explanation: An attempt was made to set some metadata for one of the properties in the specified object.
User Action: Restart the external service wizard and try generating the IDoc again. If the problem persists, contact IBM Software Support.
CWYAP101021F: An error occurred while checking to see whether property {0} already exists in segment {1} and trying to create a unique property name. Exception: {2}
Explanation: An exception occurred while trying to verify that a property existed in a segment and while creating a unique property.
User Action: Restart the external service wizard and try generating the IDoc again. If the problem persists, contact IBM Software Support.
CWYAP101022E: An error occurred while expanding the Discover IDoc from File node.
Explanation: The Discover IDoc from File node does not have any child nodes, so the node cannot be expanded.
User Action: First choose the Filter button to choose a file to generate. Then expand the node.
CWYAP101023F: No value was found after the terminal, {0}.
Explanation: This terminal should have a value after it that is used to generate the file.
User Action: Generate the IDoc file from the SAP system again and run the SAP external service wizard with the new file.
CWYAP101024E: A non-IDoc type event was received in the ALE event listener
Explanation: A wrong event was received for the ALE event listener which could not be processed
User Action: Send a correct IDoc event to the RFC destination
CWYAP1010E: Business object {0} cannot be created in namespace {2}.
Explanation: The business object cannot be loaded using the provided namespace.
User Action: Ensure that the namespace is correctly configured.
CWYAP1011E: The maxLength value for the {0} property in the {1} business object cannot be obtained.
Explanation: An error was encountered while getting the value for maxLength for the business object property.
User Action: Check to see that this property exists, and ensure that a value for maxLength is specified.
CWYAP1012E: The connection to the SAP application has been lost.
Explanation: The adapter is unable to connect to SAP.
User Action: Adapter for SAP cannot connect to the SAP system. See the exception message for details about the connection error and correct it. If the problem persists, restart the adapter.
CWYAP1013E: GatewayHost {0} is configured, but GatewayService is not.
Explanation: GatewayHost and GatewayService need to be configured in parallel.
User Action: Either set GatewayService or remove GatewayHost.
CWYAP1014E: GatewayService {0} is configured, but GatewayHost is not.
Explanation: GatewayHost and GatewayService need to be configured in parallel.
User Action: Either set GatewayHost or remove GatewayService.
CWYAP1015E: An unrecoverable error has occurred: The transaction.properties file cannot be found in either the {0} JAR file or in the class path.
Explanation: The transaction.properties file is used by the adapter to get the transaction property.
User Action: Create the transaction.properties file and add it to the class path.
CWYAP1016E: The connection expected a local transaction, but a local transaction is not supported by the {0} interface.
Explanation: Not all interface types support local transactions.
User Action: Choose an interface that supports local transactions.
CWYAP1017E: The value for the configuration property SystemNumber, {0}, is not valid.
Explanation: The SAP system expects the SystemNumber property to have a numeric value.
User Action: Type a valid numeric value, such as 00, for the SystemNumber property.
CWYAP1018E: A value is needed for the {0} property if there is a value for the MessageServerHost property.
Explanation: The SAP system expects the SystemNumber property to have a numeric value.
User Action: Type a valid value, such as 00, for the SystemNumber property.
CWYAP1019E: An exception occurred while connecting to the SAP system. Error message: {0}
Explanation: An exception occurred while making the connection to the SAP application. The adapter cannot connect using the logon credentials that have been provided.
User Action: Refer to the exception message for more details.
CWYAP102001E: The BAPI interfaces for the RFC node you selected under {0} could not be located. Error: {1}
Explanation: The RFC functions under the node you selected could not be retrieved.
User Action: Make sure that you have enough privileges to do metadata introspection on the target SAP system.
CWYAP102002E: The function {0} for generating the leaves for the BOR node was not found.
Explanation: An error occurred while retrieving the leaves of the BOR node because the lookup function cannot be found.
User Action: Check the log for more information.
CWYAP102003E: Metadata information for the BOR node cannot be found. Exception {0}
Explanation: An error occurred while introspecting the BOR tree in the target SAP system.
User Action: There might be a problem with the BOR tree in the target SAP system. Verify that the BOR can be browsed by using the BAPI browser and try again.
CWYAP102004E: Metadata information for RFC could not be found. Error: {0}
Explanation: An error occurred while checking for the RFC nodes.
User Action: Check the log for more information.
CWYAP102005E: Optional parameters for the BAPI, {0}, could not be identified. Exception: {1}
Explanation: An error occurred while checking for the RFC nodes.
User Action: See the log for more information.
CWYAP102006F: The wrapper for the BAPI could not be created. Exception: {0}
Explanation: Enterprise metadata discovery encountered an error while creating a wrapper around the selected BAPI or BAPIs.
User Action: Restart the external service wizard and try regenerating the objects. If the problem persists, contact IBM Software Support.
CWYAP102007E: The BOR node could not be created. Exception: {0}
Explanation: An error occurred while traversing the BOR tree to build the leaves of the BOR node. This issue might be related to the connection.
User Action: Reconnect and try again.
CWYAP102008E: Metadata information for the BOR node cannot be found. Exception: {0}
Explanation: An error occurred while creating the BOR node, which might be due to a problem with the BOR tree in the target SAP system.
User Action: Verify that the BOR tree can be browsed by using the BAPI browser and try again.
CWYAP102009F: A function for the RFC node was not found. Error Code: {0}, Detail: {1}
Explanation: The external service wizard allows generation of only RFC-enabled BAPIs through this node.
User Action: Using the SAPGUI, ensure that the structure of the BAPI is RFC-enabled.
CWYAP102010E: The RFC node could not be built because an error was generated by JCo. Error: {0}
Explanation: The external service wizard allows generation of RFC-enabled BAPIs only through this node when using the SAP JCO API.
User Action: Using the SAPGUI, ensure that the BAPI is RFC-enabled.
CWYAP102011E: One of the leaves under the RFC node cannot be set. Error: {0}
Explanation: An exception occurred when trying to discover the RFC-enabled function.
User Action: Using the SAPGUI, ensure that the structure of the RFC-enabled function is correct.
CWYAP102012E: The business object definitions for {0} could not be built. An error occurred while retrieving the metadata. Details: {1}
Explanation: To generate service definitions, the external service wizard needs complete metadata information for this function.
User Action: Using the SAPGUI, verify the structure of the BAPI.
CWYAP102013E: An error occurred while getting the function template for the selected BAPI, {0}. Error: {1}
Explanation: The external service wizard encountered an error while trying to fetch the function template on which the service definitions are generated.
User Action: Using the SAPGUI, check the details of this function documentation to ensure it exists and is correct.
CWYAP102014E: An error occurred while traversing the parameters for the selected BAPI {0}. Error: {1}
Explanation: The external service wizard encountered an error while trying to fetch the function parameters on which the service object properties are generated.
User Action: Using the SAPGUI, verify the structure of the BAPI.
CWYAP102015E: The definition for the structure or table parameter, {0}, could not be built. Error: {1}
Explanation: The external service wizard encountered an error while trying to fetch the structure definition on which the child service objects are generated for the selected BAPI.
User Action: Using the SAPGUI, check the details of this function's parameters.
CWYAP102016E: The grandchild {0} for the selected BAPI could not be generated. The parameter is of type {1}. Error: {2}
Explanation: The external service wizard encountered an error while trying to generate a nested BAPI structure definition based on the metadata received from the SAP system.
User Action: Check the details of this function's parameters in the SAP system.
CWYAP102017E: The length for the attribute {0} belonging to the structure or table parameter, {1}, could not be set.
Explanation: The external service wizard encountered an error while trying to generate a nested BAPI structure definition based on metadata received from the SAP system.
User Action: Using the SAPGUI, check the details of this structure/table parameters for the selected BAPI.
CWYAP102018E: An error occurred while processing a custom error for the Key: {0}, FieldName: {1}, and ErrorMsg: {2}.
Explanation: The custom RFC error application-specific information XPath is unable to find the corresponding field in the RFC. Make sure the XPATH variable is not of the type Import.
User Action: Ensure that the Xpath variable for the RFC custom error application-specific information is not an Import parameter. It should either be an Export or a Table parameter.
CWYAP102019E: The ErrorCode specified in the business object and the custom-error application-specific information matched. See business object levels 'ErrorConfiguration' AppSpecificInfo, ErrorDetail={0}
Explanation: An error condition for the custom error specified in business object level application-specific information matched the error code.
User Action: Verify the RFC data specified for the custom error application-specific information XPath.
CWYAP102020W: The BAPI listener received an IDOC event
Explanation: An unexpected event type was received by the BAPI listener which cannot be processed
User Action: Ensure that the correct BAPI event is sent to the RFC destination
CWYAP1020E: An exception occurred while disconnecting from the SAP system. Error message: {0}
Explanation: An exception occurred while attempting to disconnect from the SAP system.
User Action: Refer to the exception message for more details.
CWYAP1021E: The Object type {0} is undefined.
Explanation: The business object type does not have a valid value.
User Action: Replace the object type in the business object with a valid value.
CWYAP1022E: The {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 only supports Interaction.execute (javax.resource.cci.InteractionSpec, javax.resource.cci.Record).
User Action: Use a different execute() method.
CWYAP1023E: The {0} method is not implemented.
Explanation: The adapter does not support the call() method for invocation.
User Action: Invoke the adapter by using a different method.
CWYAP1024E: An error occurred while getting the TYPE application-specific information from the business graph for {0}. Error message: {1}
Explanation: An exception occurred while determining the interface type.
User Action: Check the value of the TYPE application-specific information for the business graph; the value should be BAPI for the BAPI interface. Valid values are BAPI, ALE, and QISS. Refer to the Adapter for SAP user documentation for details.
CWYAP1025E: The operation for the {0} interface is not valid.
Explanation: The operation used must be supported by the interface. 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 operations.
User Action: Verify that the operation value set while invoking the interface is valid. The following operations are valid for this interface: {1}.
CWYAP1026E: The application-specific information could not be parsed. Exception: {0}
Explanation: The adapter cannot parse the business object application-specific information. The SapBusinessObjectMetadata.xsd file might either be missing, outdated, or contain multiple versions.
User Action: Verify that the SapBusinessObjectMetadata file exists, is valid and that there is only one version.
CWYAP1027SE: The adapter cannot retrieve a value from the Accessor for the {0} property. Error: {1}
Explanation: The adapter cannot retrieve the application-specific information property value from the Accessor.
User Action: Verify that the values are set in a valid format and that the business object structure is correct.
CWYAP1028SE: The adapter cannot retrieve the {0} value for the ObjectName field. Error: {1}
Explanation: The metadata for the ObjectName field is incorrect.
User Action: Verify that the values are set in a valid format and that the business object structure is correct.
CWYAP1029W: The value for the partner character set in SAP, {0}, is not supported.
Explanation: The default value of UTF-8 is been used.
User Action: No action required.
CWYAP103001F: No table was found for filter {0}.
Explanation: No table which matches the supplied filter exists in the SAP EIS instance.
User Action: Provide a valid table name pattern for the filter.
CWYAP103002F: A WHERE clause entered for table {0} is not valid.
Explanation: An invalid WHERE clause was entered.
User Action: Check the WHERE clause for the table and fix it.
CWYAP103003E: A table structure for the QISS node {0} could not be retrieved. Error: {1}
Explanation: The adapter is unable to retrieve the table for the QISS node you have selected.
User Action: Verify that the table for the QISS node is valid and that it exists in the SAP enterprise information system (EIS).
CWYAP103004E: An error occurred while calling function {0} because the function was not found. Error: {1}
Explanation: The external service wizard encountered an error while trying to fetch a function template. The function module does not exist in the SAP application.
User Action: Using the SAPGUI, check the structure of this function.
CWYAP103005E: No matching data was found in the SAP system for pattern {0}.
Explanation: No data was found in the SAP system to match the given pattern.
User Action: Check the previous errors in the log file.
CWYAP103006E: An error occurred when trying to run function {0}. Error: {1}
Explanation: The SAP external service wizard encountered an error while trying to run a function.
User Action: Using the SAPGUI, check the details of this function in the SAP system to which you are connected.
CWYAP103007E: Exception: {0}
Explanation: An exception has been generated.
User Action: Check the error message.
CWYAP103008E: An error occurred while building the QISS tree. Error: {0}
Explanation: The SAP external service wizard encountered an error while trying to build the QISS tree.
User Action: Restart the SAP External Service wizard and try again.
CWYAP103009E: A problem occurred while generating the metadata object {0}. Error: {1}
Explanation: The SAP external service wizard is unable to generate the metadata object.
User Action: Check the SAP table you are trying to generate. Verify that the correct transaction version for the SAP adapter is being deployed.
CWYAP1030W: The value for partner character set is either not set or set to an unsupported character set. WepSphere Adapter for SAP uses the partner character set value , {0}, from SAP system.
Explanation: The partner character set value from SAP system will be used for this property.
User Action: No action required.
CWYAP1031W: The value entered for the partner character set, {0}, is not supported.
Explanation: The partner character set value is invalid. WebSphere Adapter for SAP will either use a valid value or a non-unicode value from the SAP system, else the default value, UTF-8, is used.
User Action: No action required.
CWYAP104001E: The stream cannot be parsed.
Explanation: Either the BAPI or RFC function name is incorrect in the received stream.
User Action: Ensure that the function name in the input stream is correct.
CWYAP104002E: An incorrect pointer, {0}, was passed to calculate the offset in the stream. The stream cannot be parsed.
Explanation: An offset that is not valid was encountered while attempting to parse the stream.
User Action: Verify that the offset for the property in the error message is correct.
CWYAP104003E: Either {0}, {1}, or {2} is set to null in the ParseMixedElement. The stream cannot be parsed.
Explanation: The input BAPI stream contains either incorrect or null input parameters.
User Action: Ensure that the input stream data for the mixed elements is correct.
CWYAP104004E: Function module {0} was not found; therefore, the stream cannot be parsed.
Explanation: The RFC or BAPI function could not be found in the SAP system.
User Action: Ensure that the function exists in the SAP application to which you are connecting. If it is not, work with the SAP administrator to resolve the problem.
CWYAP104005E: The RFC type {0}, encountered during a parsing function, is not valid; therefore, the stream cannot be parsed.
Explanation: An error occurred while parsing the RFC type in the input stream.
User Action: Ensure that the structure of the BAPI or the RFC in the input stream is correct.
CWYAP104006E: A BCD encoding that is not valid was sent to the adapter, and the stream cannot be parsed. Error: {0}
Explanation: A BCD encoding failed for the bytes to big decimal conversion.
User Action: Ensure that the BCD encoding used by the adapter is valid. Check the exception error message for more information.
CWYAP104007E: The processing of the interceptor {0} failed due to {1}.
Explanation: An unexpected error has occurred while processing the interceptor(s).
User Action: Ensure that the runtime is configured to support the interceptor(s).
CWYAP2001E: The DataGraph.get() method returned a null business object, possibly because there is an error in the business object schema.
Explanation: The business object structure or application-specific information is incorrect.
User Action: Correct the business object structure or application-specific information.
CWYAP2002E: An exception occurred while calling JCo.createFunction(BAPI_TRANSACTION_BEGIN). Error: {0}
User Action: Verify that the transaction version of the adapter is being deployed.
CWYAP2003E: An exception occurred while calling JCo.createFunction(BAPI_TRANSACTION_COMMIT). Error: {0}
Explanation: There is an error in the SAP transaction commit.
User Action: Verify that the transaction version of the adapter is being deployed.
CWYAP2004E: An exception occurred while calling JCo.createFunction(BAPI_TRANSACTION_ROLLBACK). Error: {0}
Explanation: An error occurred in the SAP transaction rollback.
User Action: Verify that the transaction version of the adapter is being deployed.
CWYAP2005E: An error occurred while running JCo.Execute(). Error: {0}
Explanation: The JCo call failed in the adapter.
User Action: Ensure that the business object is valid and contains valid data that corresponds to existing data in the SAP application.
CWYAP2006E: An error occurred while processing the application-specific information for the BAPI. Error: {0}
Explanation: An error occurred while parsing application-specific information for the business object.
User Action: Check the business object application-specific information for the BAPI. It is either invalid or corrupted.
CWYAP2007E: An error occurred while calling a BAPI. Error: {0}
Explanation: The BAPI call failed.
User Action: An error occurred when the adapter called a BAPI. Check the log messages for details and correct the problem.
CWYAP2008E: An error occurred while mapping data from the BAPI paramlist to the SDO property for propertyName={0}({1}), which maps the SAP field names to the SDO types.
Explanation: An error occurred while mapping business object data to the SAP JCA data type.
User Action: Ensure that the application-specific information for the business object is correct and that the data passed to the business object is valid.
CWYAP2009E: An error occurred because data exceeded the maximum length for the BAPI property {0} with ASI {1}. The valid maxLength is {2}, but the length received is {3}.
Explanation: Data retrieved from SAP is longer then the property can hold.
User Action: Reduce the data length for the logged property.
CWYAP2010E: An application-specific information error occurred in the getOperationASI() with the {0} property, in the {1} parent, because the operation is not valid.
Explanation: The business object application-specific information is not valid.
User Action: Ensure that the business object application-specific information is valid.
CWYAP2011E: An SapAsiException exception occurred in the execute() method. Error: {0}
Explanation: A business object application-specific information error occurred.
User Action: The processing failed for some application-specific information. Ensure that the business object schema and the application-specific information are valid.
CWYAP2012E: An exception occurred while calling the commit. Error: {0}
Explanation: An error occurred in the application-specific information.
User Action: Ensure that the application-specific information for the business object and SAP data is correct.
CWYAP2013E: An exception occurred while calling a rollback. Error: {0}
Explanation: A failure occurred while calling a BAPI rollback.
User Action: Ensure that the business object and SAP data are valid.
CWYAP2014E: A SapTransactionException exception error occurred in the execute() method. Error: {0}
Explanation: An error occurred while calling a BAPI transaction. Refer to the WebSphere Adapter for SAP user documentation for more details about using BAPI transactions.
User Action: An error occurred in the SAP BAPI transaction. Ensure that the business object data and the SAP data are valid.
CWYAP2015E: A JCo.Exception occurred in the execute() method. Error: {0}
Explanation: An error occurred in JCo.
User Action: Check the SAP connection. The error was generated by SAP middleware.
CWYAP2016E: A SapBaseException exception occurred in the execute() method. Error: {0}
Explanation: An error occurred in the SAP adapter execute() method.
User Action: Verify and correct the data. If the problem persists, contact IBM support.
CWYAP2017E: A simple BAPI (without transaction) failed. Error: {0}
Explanation: An error occurred while invoking a BAPI. Check the exception message.
User Action: Correct the data in the input BAPI business object. See the exception message for more details.
CWYAP2018E: A SapAsiException occurred in the execute() method. Error: {0}
Explanation: An error occurred in the application-specific information.
User Action: Verify that the business object application-specific information is correct.
CWYAP2019E: A SapAsiException exception occurred in the execute() method. Error: {0}
Explanation: An error occurred in the business object application-specific information.
User Action: Verify that the business object application-specific information is correct.
CWYAP2023E: An error occurred while getting the method name in a BAPI business object: {0}
Explanation: A method is either missing or has application-specific information that is not valid for the operation.
User Action: Verify that the method name is valid in the business object for the current operation.
CWYAP2024E: The verb, {0}, and the operation, {1}, cannot both be null for the adapter to continue processing.
Explanation: The adapter cannot determine the operation to be performed on the business object. Either the verb or operation should have a valid value.
User Action: Pass the matching verb and operation while invoking the adapter. If no matching verb is available, set the operation name in the SAPInteractionSpec object.
CWYAP2025E: The verb, {0}, and operation, {1}, do not match.
Explanation: If only the verb is specified, the operation is automatically set to the same value as the verb. If only the operation is specified, the verb should either be null or it should match the operation.
User Action: Pass the matching verb and operation while invoking the adapter; if no matching verb is available, set the operation name in the SAPInteractionSpec object.
CWYAP2026E: No methods were found for the {0} operation in the business object application-specific information.
Explanation: The top level business object did not find the method in the business object.
User Action: Check the application-specific information at the business object level to verify the method names for the corresponding verb or operation.
CWYAP2027E: The BAPI application-specific information at the business object level is used to determine the BAPI name. It is found to be null.
Explanation: The top-level business object did not find a method in the business object.
User Action: Check the application-specific information at the business object level to verify that the method name for the corresponding verb or operation exists. Verify the business object application-specific information for that BAPI; this information is present in the top-level business object.
CWYAP2028E: The schema definition for the business object {0} was not found in the business object wrapper {1}. Data objects cannot be generated.
Explanation: The child business object of the wrapper business object might be missing.
User Action: Check the application-specific information at the wrapper business object level and verify that the method name for the corresponding verb or operation exists.
CWYAP2029E: An exception occurred in the mapBAPIToSDO method for the {0} function.
Explanation: A JCo exception was generated by the SAP application.
User Action: An error occurred while calling the BAPI RFC function. Verify that valid values are passed to the business object.
CWYAP2030E: The application-specific information for the {0} property could not be found for the {1} data object.
Explanation: Application-specific information is missing for the property in the business object.
User Action: The application-specific information in the business object could not be read; verify that the application-specific information for the property in the corresponding business object is valid.
CWYAP2031E: An exception occurred in the mapBAPIAttributeToSDO method for the {0} property.
Explanation: An error occurred while mapping the SAP.JCo attribute to the business object property.
User Action: Ensure that the types are not mismatched or this version of the SAP instance contains the property.
CWYAP2032E: An error occurred while getting partner-character encoding. Error: {0}
Explanation: The SAP application might not support the specified character set.
User Action: Verify that the partner character set is supplied for the given SAP application.
CWYAP2033E: An error occurred while getting metadata for the BAPI Object. Error: {0}
Explanation: An error occurred while getting metadata for the BAPI object; the BusinessObjectMetadata file might be missing or outdated.
User Action: Verify that the business object metadata is correct.
CWYAP2034E: An error occurred while getting metadata for property {0}. Error Message: {1}
Explanation: An error occurred while getting metadata for the BAPI Object.
User Action: Verify that the business object metadata is correct.
CWYAP2035E: An exception occurred while converting the enterprise information system (EIS) object to a Cursor for the {1} property. Error: {0}
Explanation: An error occurred while converting an EIS object to a business object.
User Action: See the exception message for failed property information, and verify that the business object metadata for the property is correct.
CWYAP2036E: An error occurred while mapping the table field name, {1}, to the property name {2}. Error: {0}
Explanation: Values could not be mapped from the table field to the property.
User Action: Ensure that the data set in the table parameter field that is generating the error is correct.
CWYAP2037E: The adapter cannot get the value for the enterprise information system (EIS) field {1}. Error: {0}
Explanation: The adapter is unable to get the value for the EIS field {1}.
User Action: Verify that the adapter is connected to the correct version of the EIS.
CWYAP2038E: An exception occurred while calling a BAPI rollback.
Explanation: The SAP adapter cannot roll back the BAPI call.
User Action: Verify that the rollback application-specific information in the transaction business object is correct.
CWYAP2039E: An error occurred while calling the bapiSerializer.getBapiCursor() method. Error: {1}
Explanation: The adapter cannot serialize the business object.
User Action: Verify that the application-specific information in the business object is correct.
CWYAP2040E: An error occurred while calling the getNext() method on the TopLevelCursor object. Error: {0}
Explanation: The adapter cannot map data from the enterprise information system (EIS) to the cursor.
User Action: Refer to the exception message for more details.
CWYAP2041E: The adapter has generated a DESPI exception. Error: {0}
Explanation: A DESPI error was generated while mapping data to the DESPI Cursor.
User Action: Refer to the exception message for more details.
CWYAP2042E: The Cursor could not be initialized. Error: {0}
Explanation: The Cursor object could not be initialized.
User Action: Refer to the exception message for more details.
CWYAP2043E: The adapter cannot retrieve the child Cursor for the {1} property. Error: {0}
Explanation: The metadata for this property was either not found or is incorrect.
User Action: Refer to the exception message for more details.
CWYAP2044E: The BAPI, {1}, (without transaction) failed. Error: {0}
Explanation: In the input BAPI business object, either the data, metadata, or both, are incorrect.
User Action: Refer to the exception message for more details.
CWYAP2045E: An error occurred while processing the query. Error: {0}
Explanation: In the input BAPI business object, the XPath value might not correctly reference a BAPI parameter.
User Action: Refer to the exception message for more details.
CWYAP2046E: An error occurred while setting the {1} BAPI property with a value of {2}. Error Message: {0}
Explanation: The metadata for the {1} property is either missing or incorrect.
User Action: Refer to the exception message for more details.
CWYAP2047E: An error occurred while getting the Accessor for the {1} BAPI property. Error Message: {0}
Explanation: The metadata for the {1} property is either missing or incorrect.
User Action: Refer to the exception message for more details.
CWYAP2048I: The adapter is waiting for {0} seconds before invoking BAPI_TRANSACTION_COMMIT BAPI.
Explanation: The adapter will wait for the configured number of seconds before committing the changes to the SAP enterprise information system (EIS). This will give you control over the explicit commit.
User Action: No action is required.
CWYAP2049W: An error occurred while getting the value from the Accessor for the {0} BAPI property. Error Message: {1}
Explanation: The adapter failed to process the property {0}, the property will be skipped.
User Action: Verify the input value provided.
CWYAP2050W: An error occurred while setting the date value {1} to the Accessor for the {0} BAPI property.
Explanation: The adapter will set the date value as string in yyyy-MM-dd date format.
User Action: No action required
CWYAP3001E: The business object structure for the business object {0} is not valid. The Control and Data record objects cannot be determined. Error: {1}
Explanation: The business object structure is incorrect. Use the business objects generated by the external service wizard. If you have modified the business objects, they should conform to the structure and metadata format described in the user documentation.
User Action: Correct the business object structure.
CWYAP3002E: The business object structure for the business object {0} is not valid. The {1} property cannot be processed. Error: {2}
Explanation: The business object structure is incorrect. Use the business objects generated by the external service wizard. If you have modified the business objects, they should conform to the structure and metadata format as described in the user documentation.
User Action: Correct the business object structure.
CWYAP3003E: The value for the NameOfTableStructure property in the control record is not valid. The current value is set to {0}.
Explanation: Use a value of EDI_DC for IDocs that are to be exchanged with an R/3 system of Release 3.0 or 3.1. Use a value of EDI_DC40 for IDocs that are to be exchanged with an R/3 system of Release 4.x or later.
User Action: Set the value to EDI_DC or EDI_DC40 to represent the version of the IDoc record types you want to process.
CWYAP3004W: In the {0} business object, the value for the {1} property has been truncated from {2} to {3}.
Explanation: The truncation of the value may have adverse affects on the intended meaning of the value.
User Action: This is a warning message. Check the maxLength or the value of the property to see if the truncation changes the meaning of the value.
CWYAP3005E: The value for the NameOfTableStructure property in the control record is not valid. The current value is set to {0}.
Explanation: Use a value of EDI_DC for IDocs that are to be exchanged with an R/3 system of Release 3.0 or 3.1. Use a value of EDI_DC40 for IDocs that are to be exchanged with an R/3 system of Release 4.x or later.
User Action: Set the value to EDI_DC or EDI_DC40 to represent the version of the IDoc record types you want to process.
CWYAP3006E: A segment name has not been sent from SAP for IDoc type {0}.
Explanation: The segment name is needed to set the data in the correct business object.
User Action: Check the IDoc in SAP and make sure that the segment exists.
CWYAP3007W: The child business object for the IDoc segment {0} cannot be found for the {1} business object. This segment cannot be set.
Explanation: Some data from SAP is not being populated in the business object, and it might be needed for the business object to be processed correctly.
User Action: Ensure that the business object definition contains the correct segment or that the data from the segment is needed for the business object.
CWYAP3008W: An event for the transaction ID {0} contains an empty data record.
Explanation: An event cannot be created for an IDoc with an empty data record because there is no data to process.
User Action: Check the IDocs for the transaction ID in the SAP application to see why one has an empty record.
CWYAP3009E: The notification method for the event delivery could not be obtained.
Explanation: An endpoint needs to be active before an event can be sent to it.
User Action: This is an unexpected error. Make sure that the endpoint is active.
CWYAP3010E: An empty value cannot be set for the DummyKey property from the foreign key reference.
Explanation: An optional XPath value is expected, which points to a foreign key attribute. If the XPath value is empty, the adapter does not process the Dummy key.
User Action: Check the value for the specified foreign key property, check the IDoc sent from SAP, and check that the correct foreign key is specified for the DummyKey property.
CWYAP3011E: The foreign key application-specific information for the DummyKey property is not valid. Currently it is set to {0}.
Explanation: The value specified in the foreign key application-specific information does not point to a valid property in the business object.
User Action: Ensure that the foreign key application-specific information for the DummyKey property is correct.
CWYAP3012E: A NULL value was found for the {0} property in business object {1}. The value for the DummyKey property could not be set and the event will fail.
Explanation: An optional XPath value is expected, which points to foreign key attribute. If the XPath value is empty, the adapter does not process the Dummy key.
User Action: Check the value for the specified foreign key property. Check the IDoc sent from SAP, and ensure that the correct foreign key is specified for the DummyKey property.
CWYAP3013E: The foreign key application-specific information for the DummyKey property cannot be set to a contained (complex) type property.
Explanation: The foreign key application-specific information must be set to a simple property.
User Action: Check the XPath value specified in the application-specific information for the DummyKey property.
CWYAP3014E: The operation metadata is incorrect. For the IDoc type {0}, the combination of MsgType={1}, MsgCode={2}, and MsgFunction={3} is already mapped to the {4} operation.
Explanation: Two operations for the same IDoc type cannot have the same values for the MsgType, MsgCode, and MsgFunction.
User Action: Check the operation application-specific information, and specify a valid combination of MsgType, MsgCode, and MsgFunction.
CWYAP3015E: For the IDoc type {0}, the combination MsgType={1}, MsgCode={2}, and MsgFunction={3} could not be found in the application-specific information for any of the operations.
Explanation: The MsgType, MsgCode, and MsgFunction need to be set so that the operation can be determined.
User Action: Check the operation application-specific information, and specify a valid combination of MsgType, MsgCode, and MsgFunction.
CWYAP3016E: The business object operation is set to {0}. ALE outbound processing supports only EXECUTE as an operation.
Explanation: For ALE outbound processing, the adapter does not support any operations other than EXECUTE.
User Action: Change the operation that is set on the object to EXECUTE.
CWYAP3017E: The function name in the InteractionSpec is empty. For ALE outbound operations, only EXECUTE is supported as a function name.
Explanation: A function name of EXECUTE is required for outbound processing.
User Action: Set EXECUTE as the function name in the InteractionSpec.
CWYAP3018E: The function name in InteractionSpec is incorrect. For ALE outbound operations, only EXECUTE is supported as a function name. Currently the function name is set to {0}.
Explanation: A function name of EXECUTE is required for outbound processing.
User Action: Set EXECUTE as the function name in InteractionSpec.
CWYAP3019E: The SapIDocControlRecord child object is not valid in the {0} business object.
Explanation: The structure of the SapIDocControlRecord child object has caused a processing error.
User Action: Correct the business object structure.
CWYAP3020E: An unexpected, unchecked exception was generated while delivering an event to the {0} endpoint.
Explanation: An unexpected error occurred while delivering the business object to an endpoint.
User Action: Check the previous exception messages and correct the error.
CWYAP3021E: The ALE event listeners cannot be restarted because the retry limit has been reached.
Explanation: Attempts to restart the ALE event listeners have failed. The SAP system might be down.
User Action: After ensuring that the SAP system is accessible, try to stop and then restart the adapter.
CWYAP3022W: The retry mechanism has failed to restart the existing ALE event listeners. The adapter will attempt to start new listeners.
Explanation: If the retry mechanism cannot restart existing listeners, the adapter will attempt to start new ALE event listeners.
User Action: Configure the RestartLimit and the RestartInterval properties appropriately to make sure that the SAP system is available after a maintenance shutdown.
CWYAP3023E: The SAPTransactionID property is missing. J2C local transactions for ALE outbound operations cannot be supported.
Explanation: J2C local transactions are only supported when the SAPTransactionID property is present.
User Action: Make sure that the business object definition is valid.
CWYAP3024E: You must set valid values for the following mandatory IDocControlRecord parameters: {0}, {1}, {2}, {3}, {4}, and {5}.
Explanation: IDocs cannot be posted to the SAP system if any of the required fields in the control record are not set.
User Action: Make sure that all of the required fields are set in the control record.
CWYAP3025E: Error: The remote function {0} cannot be found.
Explanation: Check the SAP system to make sure the remote function you are trying to call is available.
User Action: Make sure that the remote function is available in the SAP system.
CWYAP3026I: The adapter is trying to restart ALE event listeners. Retry number {0} of {1} total retries.
Explanation: ALE event listeners have stopped listening and are being restarted.
User Action: If the restart retries fail, restart the adapter or the application that is using the adapter. Make sure the RetryInterval property is set to an appropriate value.
CWYAP3027W: RetryLimit is configured as 0. The adapter will try to restart the ALE event listeners infinitely. The current retry number is {0}.
Explanation: ALE event listeners have stopped listening and are being restarted.
User Action: If the restart retries fail, restart the adapter or the application that is using the adapter. Make sure the RetryInterval property is set to an appropriate value.
CWYAP3040E: The value for the Boolean SplitIDocPacket application-specific information of {0} is unsupported.
Explanation: None of the expected values for the SplitIDocPacket application-specific information were found.
User Action: Check the value in the SplitIDocPacket application-specific information of the business object.
CWYAP3041E: The value for the Type application-specific information of {0} is unsupported.
Explanation: None of the expected values for the Type application-specific information were found.
User Action: Check the value in the Type application-specific information of the business object. Supported values are IDOC and UNPARSED.
CWYAP3042E: The {0} business graph specified in the {1} namespace cannot be created.
Explanation: The business graph might not exist or might exist in a different namespace.
User Action: Ensure that the business graph exists in the specified namespace.
CWYAP3043E: The {0} business object cannot be created.
Explanation: The business object either might not exist, might be in the wrong namespace, or might not be located in the class path.
User Action: Ensure that the business object exists and that it is in the correct namespace and in the class path.
CWYAP3044E: An error occurred while setting the DummyKey property for the IDoc number {0}.
Explanation: The xpath found in the application-specific information might be incorrect or the foreign key property might not exist.
User Action: Ensure that either the xpath has been set correctly in the DummyKey property or that the foreign key property exists.
CWYAP3045E: A business object definition was not found during object generation. Exception: {0}
Explanation: The business object might either not exist, might be located in the wrong namespace, or might not be in the class path.
User Action: Ensure that the business object exists and that it is in the correct namespace and in the class path.
CWYAP3046E: An exception occurred for the application-specific information during object generation. Exception: {0}
Explanation: When generating the object with the data from the SAP system, an exception occurred with the application-specific information.
User Action: Check the exception details in the error message for more information about the problem with the application-specific information.
CWYAP3047E: An exception occurred during object generation. Exception: {0}
Explanation: An exception occurred when generating the object with the data from the SAP system.
User Action: Check the exception details in the error message for specific details about the problem.
CWYAP3048E: The child object {0} is not expected in the IDoc control record object.
Explanation: The IDoc control record object should have only simple properties.
User Action: Remove the child object.
CWYAP3049E: The segment name for some IDoc data cannot be found for the IDoc number {0}. This data cannot be processed.
Explanation: The IDoc data from the SAP system is incomplete and therefore cannot be processed.
User Action: Either the data must be removed from the IDoc, or the segment name must be added.
CWYAP3050E: An exception occurred while processing the segment data for the IDoc number {0}. Exception: {1}
Explanation: An exception occurred while processing the segment data from the SAP system.
User Action: Refer to details in the exception for more information about the problem.
CWYAP3051E: The maxLength application-specific information for the {0} property cannot be obtained.
Explanation: The maxLength metadata for the given property cannot be found.
User Action: Ensure that there is a maxLength value for the given property.
CWYAP3052E: An exception occurred while retrieving application-specific information metadata. Exception: {0}
Explanation: An exception occurred while retrieving application-specific information metadata.
User Action: Check the details in the error message for the specific issue.
CWYAP3053E: An exception occurred while retrieving the application-specific information metadata for the DummyKey property. Exception: {0}
Explanation: An exception occurred while retrieving the application-specific information metadata for the DummyKey property.
User Action: Check the details in the error message for the specific issue with the metadata.
CWYAP3054E: The event for the transaction ID {0} contains no data for any of the segments.
Explanation: No object can be created if there is no data.
User Action: Check the transaction ID in the SAP system to see why there is no data for any of the segments.
CWYAP3055E: An exception occurred while determining the operation. Exception: {0}
Explanation: An exception occurred while determining the operation.
User Action: Check the details in the error message for the specific issue with the operation.
CWYAP3056E: The operation metadata is incorrect. A combination of IDocType {0}, MsgType {1}, MsgCode {2}, and MsgFunction {3} is already mapped to operation {4}.
Explanation: The combination of operation metadata can only occur once for the correct operation to be determined.
User Action: Change the operation metadata so that the combination occurs in one operation only.
CWYAP3057E: The operation for the combination of IDocType {0}, MsgType {1}, MsgCode {2}, and MsgFunction {3} cannot be determined.
Explanation: There is no operation metadata set that matches the data in the IDoc.
User Action: Set the operation metadata for the IDoc type.
CWYAP3058E: The notification method for event delivery cannot be determined. Exception: {0}
Explanation: The notification method is needed to send events to the endpoint.
User Action: Check the details in the error message for the specific issue with the notification method.
CWYAP3059E: An unexpected, unchecked exception occurred while delivering an event to the {0} endpoint. Exception: {1}
Explanation: An error occurred while attempting to deliver the event to the endpoint.
User Action: Check the exception details in the error message for the specific reason for the exception.
CWYAP3060E: An endpoint is unavailable for the notification method specified. Exception: {0}
Explanation: An endpoint is needed for an event to be delivered.
User Action: Check the details in the error message for the reason why the endpoint is unavailable.
CWYAP3061E: An exception occurred while calling the {0} method for a message endpoint. Exception: {0}
Explanation: One of the methods called for sending an event to the message endpoint caused an exception.
User Action: Check the exception details in the error message for the specific reason that the exception occurred.
CWYAP3062E: An error occurred while processing transaction ID {0}, and the IgnoreIDocPacketErrors configuration property is not set. Processing is ending. The failure occurred in IDoc number {1}.
Explanation: If the IgnoreIDocPacketErrors configuration property is not set, processing will be terminated so that the error can be resolved. This is useful when the sequence of IDocs in the packet needs to be maintained.
User Action: Either resolve the error in the IDoc, or set the IgnoreIDocPacketErrors configuration property to ignore the error.
CWYAP3063E: The verb property is set to {0} in the business graph. ALE outbound processing does not use the verb property. This interface supports only EXECUTE as an operation.
Explanation: The value in the verb property should be empty.
User Action: Remove the value that has been set in the verb property.
CWYAP3064E: In the method {0}, the IDoc wrapper is present but there is a single cardinality DataRecord object in the wrapper.
Explanation: The DataRecord object needs to have multiple cardinality.
User Action: Change the DataRecord object to have multiple cardinality.
CWYAP3065E: An invalid JCo connection was encountered while sending an IDoc. Error message: {0}
Explanation: The JCo connection properties are not valid.
User Action: Correct the JCo connection properties.
CWYAP3066E: The adapter Inbound call failed while the transaction ID {0} was being processed; however, processing will continue. The failure occurred for the IDoc number {1}.
Explanation: An error has occurred in an IDoc, but because the IgnoreIDocPacketErrors property has been set, processing will continue.
User Action: Resolve the error in the IDoc and resend it.
CWYAP3067E: The {0} property could not be found. The IDoc number cannot be determined.
Explanation: To determine the IDoc number, the SapIDocControlRecord property is needed.
User Action: Resolve the error in the business object for the property specified in the error message.
CWYAP3068E: The Cursor.getNext() method call failed. Error: {1}
Explanation: Input business object data may not have been initialized in the business object specified in the error message. The input data has not been populated in the input business object Cursor.
User Action: . Verify that the input business object Cursor {0} data is initialized before calling the getNext() method.
CWYAP3069E: An error occurred while getting metadata for property {0}. Error: {1}
Explanation: An error was encountered while processing the property metadata.
User Action: Resolve the error in the business object for the property specified in the error message.
CWYAP3070E: The ALE Outbound call is unable to retrieve the transaction ID from the SAPTransactionID field. Error: {0}
Explanation: The adapter cannot read the transaction ID from the Accessor.
User Action: Verify that this call is a transactional call.
CWYAP3071E: The Accessor for verb {0} cannot be obtained. Error: {1}
Explanation: ALE Outbound processing does not use the verb property. This interface supports only EXECUTE as an operation.
User Action: Either unset the verb, or set it to null for ALE Outbound processing.
CWYAP3072E: Error: {0}
Explanation: Check the exception message to determine the problem.
User Action:
CWYAP3072W: A valid queue name value was not found. The IDoc will be processed with tRFC. Queued RFC(qRFC) cannot be supported. Message: {0}
Explanation: The IDoc is being processed with tRFC because qRFC cannot be supported without a valid queue name.
User Action: The IDoc is being processed using the default protocol.
CWYAP3073E: An error occurred while calling the getNext() method on the OutputCursor object.
Explanation: The data has not been populated in the Cursor.
User Action: Check the exception message to determine the problem.
CWYAP3074E: Error: {0}
Explanation: Check the exception message to determine the problem.
User Action:
CWYAP3075E: An error occurred while calling the getNext() method on the TopLevelcursor.
Explanation: The data has not been populated in the Cursor.
User Action: Ensure that data has been set on the Cursor.
CWYAP3076E: An error occurred while getting metadata. Error: {0}
Explanation: Metadata is not valid.
User Action: Check the exception message to determine the problem.
CWYAP3077E: An error occurred while getting metadata. Error: {0}
Explanation: The metadata is not valid.
User Action: Check the exception message to determine the problem.
CWYAP3078E: An error occurred while getting metadata. Error: {0}
Explanation: The metadata is not valid.
User Action: Check the exception message to determine the problem.
CWYAP3079E: An error occurred while getting metadata. Error: {0}
Explanation: The metadata is not valid.
User Action: Check the exception message to determine the problem.
CWYAP3083W: The value for the Dummy Key {0} is null.
Explanation: The value of the DummyKey XPATH has been assigned a null value.
User Action: Provide a value for the field that corresponds to the DummyKey.
CWYAP3084I: The selected IDOC, {0}, has unreleased segments.
Explanation: The selected IDOC contains segments that are still not released. The adapter might experience runtime issues while working with this IDOC.
User Action: No action is required.
CWYAP3085W: Unable to find business object definition for segment {0}.
Explanation: There is a mismatch between segment definition and business object definition.
User Action: Ensure that the IDoc sent from SAP system is the same version as discovered during metadata discovery.
CWYAP4001W: There were no records found in table {0}.
Explanation: No rows were found in SAP for the specified query.
User Action: Check the filter and enter a valid WHERE clause name pattern.
CWYAP4002S: The QISS interface was unable to create a container for the {0} business object.
Explanation: A business object must exist in the namespace before a container can be created for the business object.
User Action: Ensure that the business object exists in the namespace and that the namespace is valid for the business object.
CWYAP4003S: An error occurred while processing the QISS business object {0}. Error: {1}
Explanation: The error must be corrected before the adapter can process the QISS business object.
User Action: Check the exception message and refer to SAP Transaction ST22 to determine the problem.
CWYAP4004S: An error occurred while processing a QISS business object. Error: {0}
Explanation: The error must be corrected before the adapter can process the QISS business object.
User Action: Check the exception message to determine the problem.
CWYAP4005S: An error occurred while parsing the value, {0},for the sapWhereClause. Error: {1}
Explanation: The sapWhereClause should have spaces before the slash character (/).
User Action: Ensure that the format of the sapWhereClause is correct.
CWYAP5001W: No records were found in the event table with the following filter criteria: {0}
Explanation: No rows were found in SAP for the specified query.
User Action: Ensure that the name pattern specified in the EventTypeFilter parameter is valid.
CWYAP5002E: A null JCo connection was encountered. Error: {0}
Explanation: The adapter could not connect to the SAP system because the connection properties are not valid.
User Action: Refer to the error message to determine what connection property is not valid.
CWYAP5003E: A null JCo repository was encountered.
Explanation: The adapter could not access the SAP repository because the connection properties are not valid.
User Action: Ensure that the JCo connection properties are valid.
CWYAP5004E: An error occurred while processing the event with ID {0}.
Explanation: The adapter cannot retrieve values from the SAP system event table.
User Action: Ensure that the data in the SAP system event table is valid for this ID.
CWYAP5005E: The {0} method could not be run because of the following error: {1}
Explanation: An error occurred while processing events from the SAP system.
User Action: Refer to the error message for details about the error.
CWYAP5006I: No records were found in the SAP event table.
Explanation: No records were found in the SAP event table.
User Action: No action is required.
CWYAP5007I: The parameter {0} has the value {1}.
Explanation:
User Action: No user action is required.
CWYAP5008E: The Accessor for property {0} cannot be obtained. Error: {1}
Explanation: The adapter cannot retrieve the Accessor if the Cursor has not been initialized or if it does not have the property.
User Action: Refer to the exception message for details about the error.
CWYAP5009E: The {0} method could not be run. Error: {1}
Explanation: An error occurred while attempting to set values in the event table.
User Action: Refer to the error message for details about the error.