CWYAP100001F: The enterprise service discovery wizard cannot connect to the SAP Host system. Cause: {0}
Explanation: The enterprise service discovery wizard needs these properties to be entered correctly in order to connect to the SAP system. Refer to the adapter user guide for more details on each of these properties.
User Action: Ensure that all the connection properties are correctly entered and try again.

 

CWYAP100002F: The metadata tree could not be created for the adapter. Cause: {0}
Explanation: The enterprise service discovery wizard encountered a non recoverable error while creating the tree-node structures and cannot proceed.
User Action: Ensure that all the connection properties are correctly entered 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 enterprise service discovery 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 invalid.
User Action: Ensure that the connected SAP system supports ALE metadata introspection.

 

CWYAP100006I: The enterprise service discovery wizard could not recognize the discovery criteria you entered.
Explanation: The wild card character * has been found in an unexpected location.
User Action: The placement of the wild card character in the discover by name criteria needs to be corrected.

 

CWYAP100007I: The enterprise service discovery wizard could not recognize the discovery criteria you entered.
Explanation: The * character can be used as a wild card to represent zero or more characters 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 there is an illegal discovery criteria.
User Action: The placement of the wild card character in the discover by description criteria needs to be corrected.

 

CWYAP100008F: Unable to set the tool context for the enterprise service discovery wizard. 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 WebSphere Integration Developer and the enterprise service discovery 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.

 

CWYAP100010F: The enterprise service discovery wizard encountered a non-recoverable error while creating filtering properties for the tree nodes. Exception: {0}
Explanation: The enterprise service discovery 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 enterprise service discovery 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 enterprise service discovery wizard and try again.

 

CWYAP100012F: Selection properties cannot be created for the nodes selected. Exception: {0}
Explanation: The Metadata Selection properties are displayed to you to get additional information. This information is necessary to define the structure of the metadata object(s).
User Action: Verify you entered everything correctly and try again.

 

CWYAP100013E: Unable to create Selection properties for the IDoc Objects selected. Exception: {0}
Explanation: The MetadataSelection properties for the IDoc Selection are rendered to the user to get additional information used to create apply to the IDoc Metadata Objects to be imported.
User Action: Verify you entered everything correctly and try again.

 

CWYAP100014F: An error occurred while creating IDocs from the file. Exception: {0}
Explanation: The enterprise service discovery 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 a SAP system.

 

CWYAP100015E: Selection properties cannot be created for the selected BAPI objects. Exception: {0}
Explanation: The MetadataSelection properties for the BAPI Selection are used to get additional information to apply to the BAPI metadata objects to be imported.
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 for all exchange of 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 enterprise service discovery wizard and if the problem persists contact IBM Software Support.

 

CWYAP100017E: Activation specification properties for the Inbound connection cannot be created. Exception: {0}
Explanation: Inbound connection configuration must consist of properties that specify the Activation Specification properties for the SAP Adapter. Examples of these properties are: SAP Host Name, SAP User Id and password. These properties can then be configured through the Server Admin console.
User Action: Try restarting the enterprise service discovery wizard and if the problem persists contact IBM Software Support.

 

CWYAP100018E: The resource adapter properties for the Inbound connection cannot be created. Exception: {0}
Explanation: Inbound connection configuration must consist of properties that are specific to the Resource Adapter. Properties such as Adapter name, ID, log file name for the Adapter, file size, trace file name, size. These properties can be configured later through the Admin console of the server.
User Action: Try restarting the enterprise service discovery wizard. If the problem persists contact IBM Software Support.

 

CWYAP100019F: The enterprise service discovery wizard is unable to create the ManagedConnectionFactory properties for the Outbound connection. Exception: {0}
Explanation: The Outbound connection needs Managed Connection Factory Properties. These properties are used to establish a connection with the SAP system.
User Action: Try restarting the enterprise service discovery wizard and if the problem persists contact IBM Software Support.

 

CWYAP100020E: Unable to create Outbound Connection Configuration properties for the Objects selected. Exception: {0}
Explanation: The configuration is used for all exchange of 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 enterprise service discovery wizard and if the problem persists contact IBM Software Support.

 

CWYAP100021F: Unable to create the Resource Adapter properties for the Outbound connection. Exception: {0}
Explanation: The Outbound connection configuration adds to the base service interfaces and the methods to create, and applies this configuration to the Resource Adapter properties.
User Action: Try restarting the enterprise service discovery 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.

 

CWYAP100023W: No operations have been specified for the service artifacts.
Explanation: Enterprise metadata discovery cannot determine the operations selected by the user.
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 enterprise service discovery wizard encountered an error while creating the Service descriptions.
User Action: Try restarting the enterprise service discovery wizard and if the problem persists contact IBM Software Support.

 

CWYAP100025F: Unable to set the metadata for the property {0}. Error: {1}
Explanation: The enterprise service discovery wizard encountered an error while populating the schema for the property.
User Action: This could be an issue with the SAP system to which you are connected. 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 enterprise service discovery wizard encountered an error while generating Outbound (Import) service descriptions.
User Action: Try restarting the enterprise service discovery wizard and if the problem persists contact IBM Software Support.

 

CWYAP100027F: An error occurred while setting the value for the property {0}. Error: {1}
Explanation: The enterprise service discovery wizard encountered an error while setting the value for the property.
User Action: Close the window and retry.

 

CWYAP1001: 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 enterprise metadata discovery(EMD) generated objects. If you have modified the business objects, make sure the structure matches that detailed in the user documentation.
User Action: Check the business object metadata and verify that it is correct.

 

CWYAP1002: UnsupportedEncodingException is occurred. Exception message {0}.
Explanation: SAP JCA Adapter does not support the provided character encoding.
User Action: Verify that the adapter supports the specified character encoding.

 

CWYAP1003: The following error occurred. Exception {0}, Message {1}. Cause : {2}, Message {3}.
Explanation: Exception occurred , See the exception details for more information .
User Action: An exception occurred, See the exception details .

 

CWYAP1004: SAPManagedConnection Configuration property value ={0} is invalid. see SAP JCA Adapter user document for property usage.
Explanation: The configuration property is invalid.
User Action: Correct the SAP Configuration property value by assigning a valid value. see SAP JCA Adapter user document for property usage.

 

CWYAP1005: Business object {0}. The object type could not be determined.
Explanation: The object type could not be determined. Check the business object level application-specific information.
User Action: 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.
User Action: Invoke execute passing proper arguments.Upgrade the SAP JCA Adapter to 6.1 version .

 

CWYAP1007: A JCO exception occurred while SAP JCA Adapter processing. Group: {0}. Key: {1}. Error Message: {2}. Cause: {3}.
Explanation: A JCO exception occurred.
User Action: This is generic SAP JCO exception raised by SAP system , exception provides the error detail

 

CWYAP1008: Property: {0} cannot be set. Business object {1} cannot be set.
Explanation: Connector is unable to process property for specified BO .
User Action: The property may not exist in BO or property name may be miss- spelt , verify BO structure.

 

CWYAP1009: The RFC function {0} cannot be found in this SAP instance.
Explanation: The RFC function {0} could not be found in SAP system.
User Action: Ensure that the function exists in the SAP application to which you are connecting.

 

CWYAP1010: Business object {0} cannot be created in namespace {2}.
Explanation: Unable to create Business Object {0} in namespace {2}.
User Action: Ensure that the namespace is correctly configured.

 

CWYAP101001F: ALE IDocs could not be retrieved from the SAP system for the node {0}. Error: {1}
Explanation: The enterprise service discovery wizard requires that the target SAP system is properly configured to introspect these IDocs you have selected.
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: A non-recoverable error occurred while locating the linked IDoc.
User Action: Check the log for more information.

 

CWYAP101004E: An error occurred when 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: Child objects could not be created for an IDoc.
User Action: This could be an issue with the SAP system to which you are connected. 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.
User Action: This could be an issue with the SAP system to which you are connected. 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 enterprise service discovery wizard might create a definition with missing segments or the SAP enterprise service discovery wizard displays an error indicating that the generation of the BO 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 processing segment and field lines.
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 enterprise service discovery 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 enterprise service discovery wizard with the new file.

 

CWYAP101010F: A general exception error occurred for {0} of {1}. Reason {2}.
Explanation: The enterprise service discovery 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 enterprise service discovery 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 enterprise service discovery wizard with the new file.

 

CWYAP101014F: The {0} property's maximum length could not be set properly because of Exception: {1}. The maximum length value will default to 255.
Explanation: An exception occurred when trying to set the max length property.
User Action: See the exception message for more information.

 

CWYAP101015F: Error calling function {0}. Function 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 enterprise service discovery wizard failed to do a look-up for the internal language code in the table T002.
User Action: Verify the language code.

 

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 raised.

 

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 enterprise service discovery 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 enterprise service discovery 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 enterprise service discovery wizard and try generating the IDoc again. If the problem persists contact IBM Software Support.

 

CWYAP1011: A value for maxLength for property: {0}, business object {1} cannot be obtained.
Explanation: Unable to get maxLength for property : {0} , business object {1}.
User Action: Check to see that this property exists, and ensure that maxLength is specified.

 

CWYAP1012: The connection to the SAP application is lost.
Explanation: SAP JCA adapter unable to connect to SAP system
User Action: SAP JCA Adapter unable to make connection to SAP system, if the problem persist restart the SAP JCA Adapter.

 

CWYAP1013: GatewayHost {0} is configured, but GatewayService is not, either configure both or none.
Explanation: GatewayHost and GatewayService need to be configured in parallel.
User Action: Either set GatewayService or remove GatewayHost.

 

CWYAP1014: GatewayService {0} is configured, but GatewayHost is not, either configure both or none.
Explanation: GatewayHost and GatewayService need to be configured in parallel.
User Action: Either set GatewayHost or remove GatewayService.

 

CWYAP1015: An unrecoverable error occurred: The transaction.properties file cannot be not found in either the {0} JAR file or in the class path.
Explanation: The transaction.properties file could not be found, this file is used by SAP adapter to get transaction property.
User Action: 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 {0}.
Explanation: Not all interface types support local transactions.
User Action: Check to see that the interface type supports local transactions.

 

CWYAP1017: Error:Configuration property SystemNumber {0} is invalid. (This information is provided in the user action section).
Explanation: An SAP system expects the system number to be a numeric value.
User Action: Enter a valid value for the SystemNumber property. The SystemNumber property must be numeric.

 

CWYAP1018: Error:A value is needed for the {0} property if there is a value for the MessageServerHost property.
Explanation: An SAP system expects the System Number to be a numeric value.
User Action: Enter a valid value for the SystemNumber property

 

CWYAP1019: An exception occurred while connecting to the SAP system. Error message: {0}.
Explanation: An exception occurred while making the connection to the SAP s application . SAP JCA Adapter is unable to make connection using provided logon credentials.
User Action: Check the details of the exception message.

 

CWYAP1020: 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: Check the details of the exception message.

 

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 look-up function cannot be found.
User Action: Check the log for more information.

 

CWYAP102003E: BOR: 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 the BOR using the BAPI browser and try again.

 

CWYAP102004E: RFC: Metadata information 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 could not be identified: {0}. Exception {1}.
Explanation: An error occurred while checking for the RFC nodes.
User Action: Check the log for more information.

 

CWYAP102007F: 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 enterprise service discovery 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.
User Action: This issue might be related to the connection. 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.
User Action: There might be a problem with the BOR tree in the target SAP system. Verify the BOR tree using the BAPI browser and try again.

 

CWYAP102009F: A function for the RFC node was not found. Error Code: {0}, Detail: {1}
Explanation: The enterprise service discovery wizard allows generation of only RFC-enabled BAPIs through this node.
User Action: Using the SAPGUI, verify the structure of the BAPI.

 

CWYAP102010E: The RFC node could not be built because an error was generated by JCO. Error: {0}
Explanation: The enterprise service discovery wizard allows generation of only RFC-enabled BAPIs through this node using the SAP JCO API.
User Action: Using the SAPGUI, check if 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, verify the structure of the RFC-enabled function.

 

CWYAP102012E: The business object definitions for {0} could not be built. An error occurred while retrieving the metadata. Details: {1}
Explanation: In order to generate service definitions, the enterprise service discovery 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 enterprise service discovery 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.

 

CWYAP102014E: An error occurred while traversing the parameters for the selected BAPI {0}. Error: {1}
Explanation: The enterprise service discovery 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/table {0} could not be built. Error: {1}
Explanation: The enterprise service discovery 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 BAPI selected could not be generated. The parameter is of type: {1}. Error :{2}
Explanation: The enterprise service discovery 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 functions parameters in the SAP system.

 

CWYAP102017E: The length for the attribute {0} belonging to the structure/table {1} could not be set.
Explanation: The enterprise service discovery 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.

 

CWYAP1021: Error: Object type {0} is undefined.
Explanation: The business object type does not have a valid value.
User Action: Revise the object type in the business object. The one provided is not one of the valid values

 

CWYAP1022: 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 supports only a certain signature for the execute() method.
User Action: A different execute() method needs to be used.

 

CWYAP1023: 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.

 

CWYAP1024: An error occurred while getting the 'TYPE' application specific information from the Business Graph for: {0}. Error message: {1}.Valid values are BAPI , ALE and SQI , refer SAP JCA Adapter user-documentation for details.
Explanation: An exception occurred while determining the interface type.
User Action: Check the 'TYPE' application-specific information value for the business graph , the value should be 'BAPI' for BAPI interface .

 

CWYAP1025: An invalid operation was found for the interface {0}. The following operations are valid for this interface: {1}.
Explanation: The ALE interface supports the Execute operation. The BAPI interface supports the following operations: Create, UpdateWithDelete, Delete, and Retrieve. The SQI interface supports the RetriveAll and the Exists operation.
User Action: 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, be outdated, or contains multiple versions. Exception {0}.
Explanation: The SAP adapter is cannot parse the business object application-specific information.
User Action: Verify that the SapBusinessObjectMetadata file is present and valid, and that there is only single version.

 

CWYAP103001F: No table found for filter {0}
Explanation: No table matching pattern exists in SAP .
User Action: Check the filter and enter a valid table name pattern.

 

CWYAP103002F: Invalid where clause entered for table {0}
User Action: Check the where clause for the table and fix the where clause.

 

CWYAP103003E: Failed to retrieve any table for the node {0}. Error: {1}
Explanation: Unable to retrieve the table for the SQI node you have selected.
User Action: None

 

CWYAP103004E: Error calling function {0}. This function is not found. Error: {1}
Explanation: The enterprise service discovery 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 found in SAP system for pattern {0}.
Explanation: The error occurred in No matching data for table founf in SAP .
User Action: Check the previous errors.

 

CWYAP103006E: An error occurred when trying to execute function {0}. Error: {1}.
Explanation: The SAP Enterprise Service Discovery encountered an error while trying to execute 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 caught.
User Action: Check the error message.

 

CWYAP103008E: An error occurred while building the SQI tree. Error: {0}.
Explanation: The SAP Enterprise Service Discovery encountered an error while trying to build the SQI tree.
User Action: Restart the SAP Enterprise Service Discovery and try again.

 

CWYAP103009E: Problem occurred when generating the Metadata Object {0}. Error: {1}
Explanation: The SAP Enterprise Service Discovery is unable to generate the Metadata object. Verify that the transaction version for SAP JCA Adapter is being deployed.
User Action: Check the SAP table you are trying to generate.

 

CWYAP2001: DataGraph.get() 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.

 

CWYAP2002: An exception occurred while calling JCO.createFunction(BAPI_TRANSACTION_BEGIN). Error: {0}
User Action: Verify that the transaction version for SAP JCA Adapter is being deployed.

 

CWYAP2003: 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 for SAP JCA Adapter is being deployed.

 

CWYAP2004: 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 for SAP JCA Adapter is being deployed.

 

CWYAP2005: An error occurred while executing 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.

 

CWYAP2007: An error occurred while processing the application-specific information for the BAPI Error: {0}
Explanation: An error occurred while parsing business object application-specific information.
User Action: Check the business object application-specific information for the BAPI. It is either invalid or corrupted.

 

CWYAP2007: A error occurred while calling a BAPI. Error: {0}
Explanation: The BAPI call failed.
User Action: An error occurred while calling a BAPI by the adapter. Check the log messages for details and correct the problem.

 

CWYAP2008: An error occurred while mapping data from the BAPI paramlist to the SDO property for propertyName={0}({1}));
Explanation: An error occurred while mapping business object data to SAP JCA data type.
User Action: Ensure that the business object application-specific information is correct and that the data passed to the business object is valid.

 

CWYAP2009: An error occurred because data exceeded the maximum length for BAPI property ={0} asi={1} valid maxLength={2} received length={3}
Explanation: Data retrieved from SAP is longer then the property can hold.
User Action: Reduce the data length for the logged property.

 

CWYAP2010: An application-specific information error occurred in the getOperationASI() property={0} parent={1}
Explanation: The business object application-specific information is invalid.
User Action: The operation is invalid. Ensure that the business object application-specific information is valid.

 

CWYAP2011: An SapAsiException occurred in execute(). 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.

 

CWYAP2012: An exception occurred while calling the commit. Error:{0}
Explanation: An error occurred in the application-specific information.
User Action: Check the business object and SAP data.

 

CWYAP2013: An exception occurred while calling a rollback. Error:{0}
Explanation: A failure occurred while calling BAPI rollback.
User Action: Ensure that the business object and SAP data are valid.

 

CWYAP2014: A SapTransactionException error occurred in execute(). Error: {0}
Explanation: An error occurred while calling a BAPI transaction. Refer to the WebSphere Adapters SAP User Guide for more details about using BAPI transactions.
User Action: An error occurred in the SAP BAPI transaction. Check the business object and the SAP data to ensure that they are valid.

 

CWYAP2015: A JCO.Exception occurred in execute(). Error: {0}
Explanation: An error occurred in JCO.
User Action: Check the SAP connection; SAP middle ware generated the error.

 

CWYAP2016: A SapBaseException occurred in execute(). Error: {0}
Explanation: An error occurred in the SAP Connector execute() method.
User Action: Verify and correct the data. If the problem persists, contact IBM support.

 

CWYAP2017: A simple BAPI (without-transaction) failed. Error: {0}
Explanation: Error occurred while invoking a BAPI. Check the exception message.
User Action: Verify and correct the data in input BAPI business object. See the exception message for more error details.

 

CWYAP2018: An 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.

 

CWYAP2019: An SapAsiException 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.

 

CWYAP2023: An error occurred while getting the method name in a BAPI business object :{0}
Explanation: A method is either missing or has invalid application-specific information for the operation .
User Action: Verify that the method name is valid in the business object for the current operation.

 

CWYAP2024: The verb={0}, and the operation={1}; both cannot be null.
Explanation: Both verb and operation cannot be null.
User Action: Pass the matching verb and operation while invoking the SAP adapter. If no matching verb is available, set the operation name in SAPInteractionSpec.

 

CWYAP2025: 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 must match the operation.
User Action: Pass the matching verb and operation while invoking the SAP adapter; if no matching verb is available, set the operation name in SAPInteractionSpec.

 

CWYAP2026: No methods were found for verb/operation ={0} 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 business object level application-specific information to verify the method names for the corresponding verb or operation.

 

CWYAP2027: Error BAPI 'MethodName' application-specific information found null, verify the business object application-specific information for that BAPI, this information is present in top-level business object.
Explanation: The top level business object did not find a method in the business object.
User Action: Check the business object level application-specific information to verify that the method name for the corresponding verb or operation exists.

 

CWYAP2028: Business object {0} was not found in the BusinessObject-Wrapper={1}.
Explanation: The child business object of the wrapper business object might be missing.
User Action: Check the Wrapper-BusinessObject level ASI and verify that the method name for the corresponding verb or operation exists.

 

CWYAP2029: An exception occurred in mapBAPIToSDO for function={0}
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.

 

CWYAP2030: The application-specific information for property={0} could not be found for DataObject={1}.
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.

 

CWYAP2031: An exception occurred in mapBAPIAttributeToSDO for property={0}
Explanation: An error occurred while mapping the SAP.JCO attribute to the business objects property.
User Action: Either the types are mismatched or this version of the SAP instance does not contain the property.

 

CWYAP2032: An error occurred while getting partner-character encoding, Error:{0}
Explanation: The SAP application might not support the provided character set.
User Action: Verify that partner character set is supplied for the given SAP application.

 

CWYAP3001: The business object structure for the business object {0} is invalid. 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 enterprise service discovery. If you have modified the business objects, they should conform to the structure and metadata format as detailed in the user documentation.
User Action: Check the business object structure.

 

CWYAP3002: The business object structure for the business object {0} is invalid. The property {1} cannot be processed. Error: {2}
Explanation: The business object structure is incorrect. Use the business objects generated by the enterprise service discovery. If you have modified the business objects, they should conform to the structure and metadata format as detailed in the user documentation.
User Action: Check the business object structure.

 

CWYAP3003: The value for the NameOfTableStructure property in the control record is invalid. The current value is set to {0}.
Explanation: A value of "EDI_DC" is used for IDocs that are to be exchanged with an R/3 system of Release 3.0/3.1. A value of "EDI_DC40" is used for IDocs that are to be exchanged with an R/3 system of Release 4.x or greater.
User Action: Set the value to "EDI_DC" or "EDI_DC40" to represent the version of the IDoc record types you wish to process.

 

CWYAP3004: In the business object {0}, the value for the property {1} 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" attribute of the business object property or the value of the business object property to see if the truncation changes the meaning of the value.

 

CWYAP3005: The value for the NameOfTableStructure property in the control record is invalid. The current value is set to {0}.
Explanation: A value of "EDI_DC" is used for IDocs that are to be exchanged with an R/3 system of Release 3.0/3.1. A value of "EDI_DC40" is used for IDocs that are to be exchanged with an R/3 system of Release 4.x or greater.
User Action: Set the value to "EDI_DC" or "EDI_DC40" to represent the version of the IDoc record types you wish to process.

 

CWYAP3006: 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.

 

CWYAP3007: The child business object for the segment {0} cannot be found for the business object {1}. This segment cannot be set.
Explanation: Some data from SAP is not being populated in the business object and it may be needed for the correct processing of the business object.
User Action: Check if the business object definition needs this segment or if the data from the segment is needed for the business object.

 

CWYAP3008: An event for 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.

 

CWYAP3009: The notification method for the event delivery could not be obtained.
Explanation: An endpoint needs to be alive before and event can be sent to it.
User Action: This is an unexpected error. Make sure that the endpoint is alive.

 

CWYAP3010: An empty value cannot be set to the DummyKey property from the foreign key reference.
Explanation: A value is expected for a foreign key reference or no such reference is needed.
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.

 

CWYAP3011: The foreign key application-specific information for the DummyKey property is invalid. 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: Check foreign key application-specific information for the DummyKey property.

 

CWYAP3012: A NULL value was found for the business object {1}, property {0}. The value for the DummyKey property could not be set. The event will fail.
Explanation: A value is expected for a foreign key reference or no such reference is needed.
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.

 

CWYAP3013: 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 application-specific information for the DummyKey property.

 

CWYAP3014: The operation metadata is incorrect. For the IDoc type {0}, the combination of MsgType={1}, MsgCode={2}, and MsgFunction={3} is already mapped to operation {4}.
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.

 

CWYAP3015: 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.

 

CWYAP3016: The business object operation is set to {0}. ALE outbound processing only supports EXECUTE as an operation.
Explanation: The adapter does not support any operations other than EXECUTE for ALE outbound processing.
User Action: Check the operation that is set in the object.

 

CWYAP3017: The function name in the Interaction Spec is empty. For ALE outbound operations, only EXECUTE is supported as a function name.
Explanation: A function name of EXECUTE is required for any outbound processing.
User Action: Set EXECUTE as the function name in the Interaction Spec.

 

CWYAP3018: The function name in the Interaction Spec 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 any outbound processing.
User Action: Set EXECUTE as the function name in the InteractionSpec object .

 

CWYAP3019: The SAP IDOC control record child object is invalid in the business object {0}.
Explanation: The structure of the SAP IDOC control record child object has caused a processing error.
User Action: Check the business object structure.

 

CWYAP3020: An unexpected, unchecked exception was caught while delivering an event to endpoint {0}.
Explanation: An unexpected error was generated while delivering the business object to an endpoint.
User Action: Check the previous exception messages and correct the error.

 

CWYAP3021: 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: Try to stop and then restart the adapter or application after ensuring that the SAP system is accessible.

 

CWYAP3022: The retry mechanism has failed to restart the existing ALE Event Listeners. Adapter will attempt to start new Listeners.
Explanation: If the retry mechanism could not restart existing listners , adapter will attempt to start new ALE Event Listeners.
User Action: Configure the "Restart Limit" and the "Restart Interval" properties appropriately to make sure the SAP system is available after a maintenance shutdown.

 

CWYAP3023: The SAPTransactionID property is missing. J2C local transactions for ALE outbound operations cannot be supported.
Explanation: J2C local transactions are only be supported when the SAPTransactionID property is present.
User Action: Make sure that the business object definition is valid.

 

CWYAP3024: You must set valid values for the following mandatory IDocControlRecord parameters: {0}, {1}, {2}, {3}, {4}, and {5}.
Explanation: The IDoc posting to the SAP system will fail if all 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.

 

CWYAP3025: 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 SAP system has this remote function.

 

CWYAP3026: Trying to restart ALE Event Listeners. Retry number {0} of {1} total retries.
Explanation: ALE Event Listners 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 Retry Interval property is set to an appropriate value.

 

CWYAP3027: RetryLimit is configured as 0. The adapter will try to restart the ALE Event Listeners infinitely. The current retry number is {1}.
Explanation: ALE Event Listners 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 Retry Interval property is set to an appropriate value.

 

CWYAP3040: The value for the 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.

 

CWYAP3041: 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.

 

CWYAP3042: The business graph {0} specified in the namespace {1} 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.

 

CWYAP3043: The business object {0} 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.

 

CWYAP3044: 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 the xpath has been set correctly in the DummyKey property or that the foreign key property exists.

 

CWYAP3045: A business object definition was not found during object generation. Exception: {0}
Explanation: The business object might either not exist, be located in the wrong namespace, or 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.

 

CWYAP3046: An exception occurred for the application-specific information during object generation. Exception: {0}
Explanation: An exception occurred with the application-specific information when generating the object with the data from the SAP System.
User Action: Check the exception details in the error message to see what is the issue for the application-specific information.

 

CWYAP3047: 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 the specific issue.

 

CWYAP3048: 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: The child object needs to be removed.

 

CWYAP3049: 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.

 

CWYAP3050: 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: Check the exception details in the error message for the specific issue.

 

CWYAP3051: The maxLength application-specific information for the property {0} cannot be obtained.
Explanation: The maxLength metadata for the given property cannot be found.
User Action: Check to see if there is a maxLength for the given property.

 

CWYAP3052: 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 exception details in the error message for the specific issue.

 

CWYAP3053: 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 exception details in the error message for the specific issue with the metadata.

 

CWYAP3054: The event for the transaction ID {0} contains no data from any of the segments.
Explanation: No object can be created if there is no data.
User Action: Check this transaction ID in the SAP system to see why there is no data for any of the segments.

 

CWYAP3055: An exception occurred while determining the operation. Exception: {0}
Explanation: An exception occurred while determining the operation.
User Action: Check the exception details in the error message for the specific issue with the operation.

 

CWYAP3056: 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 so that the correct operation can be determined.
User Action: Change the operation metadata so that the combination occurs only in one operation.

 

CWYAP3057: 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 to match the data in the IDoc.
User Action: Set the operation metadata for the IDoc type.

 

CWYAP3058: 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 exception details in the error message for the specific issue with the notification method.

 

CWYAP3059: An unexpected, unchecked exception was caught while delivering an event to the endpoint {0}. 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 issue with delivering the event.

 

CWYAP3060: 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 exception details for in the error message the specific issue as to why the endpoint is unavailable.

 

CWYAP3061: 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 issue in calling the method.

 

CWYAP3062: An error has 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 need to be maintained.
User Action: Either resolve the error in the IDoc, or set the IgnoreIDocPacketErrors configuration property to ignore the error.

 

CWYAP3063: The verb property is set to {0} in the business graph. ALE outbound processing does not use the verb property. This interface only supports 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.

 

CWYAP3064: Error: In the method {0}, the IDoc wrapper is found but there is a single cardinality DataRecord object in the wrapper.
Explanation: The Data Record object needs to be multiple cardinality.
User Action: Change the DataRecord object to have multiple cardinality.

 

CWYAP3065: An invalid JCo connection was encountered while sending an IDoc. Error message: {0}
Explanation: The JCo connection properties are invalid.
User Action: Check the JCo connection properties.

 

CWYAP3066: 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.

 

CWYAP3067: The property {0} 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.

 

CWYAP3068: Unable to find business object {0} for event={1}, probable cause event {2} is not supported by this application module or activationSpec property RfcProgramID={3} is being used by other SAP adapter instance.
Explanation: Unable to find business object for received event , it could be possible multiple ALE inbound modules are using same RFCProgramID , if that is the case SAP would randomly send event to any of the registered listener of the RFCProgramID.
User Action: Verify that the event received is supported by this application instance . Also verify that RFCProgramID is not used by any other application . If problem still exist check business object metadata .

 

CWYAP3069: Successfully processed event with TID={0} and IDOCNO={1}
Explanation: CEI event log for successfully process event .
User Action: Successfully processed event

 

CWYAP3070: Ale processing failed for event with TID={0} and IDOCNO={1}
Explanation: CEI event log for failed event.
User Action: ALE event failed

 

CWYAP4001W: There were no records found in table {0}.
Explanation: No rows were found for the specified query in SAP.
User Action: Check the filter and enter a valid where clause name pattern.

 

CWYAP4002S: The SQI interface was unable to create a container for the business object {0}.
Explanation: A business object needs to exist in the namespace before a container for the business object can be created.
User Action: Check that the business object exists in the namespace or that the namespace is valid for the business object.

 

CWYAP4003S: An error occurred while processing the SQI business object {0}. Error: {1}
Explanation: The error needs to be corrected before the SQI business object can be processed by the adapter.
User Action: Check the exception message to determine the problem.

 

CWYAP4004S: An error occurred while processing a SQI business object. Error: {0}
Explanation: The error needs to be corrected before the SQI business object can be processed by the adapter.
User Action: Check the exception message to determine the problem.