CWYAP3000-3999: SAP Software resource adapter - ALE IDoc processing
- CWYAP3001
- The business object structure for the business object <insert_0> is not valid. The Control and Data record objects cannot be determined. Error: <insert_1>
- Severity
- 20 : Error
- 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.
- Response
- Correct the business object structure.
- CWYAP3002
- The business object structure for the business object <insert_0> is not valid. The <insert_1> property cannot be processed. Error: <insert_2>
- Severity
- 20 : Error
- 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.
- Response
- Correct the business object structure.
- CWYAP3003
- The value for the NameOfTableStructure property in the control record is not valid. The current value is set to <insert_0>.
- Severity
- 20 : Error
- 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.
- Response
- Set the value to EDI_DC or EDI_DC40 to represent the version of the IDoc record types you want to process.
- CWYAP3004
- In the <insert_0> business object, the value for the <insert_1> property has been truncated from <insert_2> to <insert_3>.
- Severity
- 10 : Warning
- Explanation
- The truncation of the value may have adverse affects on the intended meaning of the value.
- Response
- 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.
- CWYAP3005
- The value for the NameOfTableStructure property in the control record is not valid. The current value is set to <insert_0>.
- Severity
- 20 : Error
- 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.
- Response
- Set the value to EDI_DC or EDI_DC40 to represent the version of the IDoc record types you want to process.
- CWYAP3006
- A segment name has not been sent from SAP for IDoc type <insert_0>.
- Severity
- 20 : Error
- Explanation
- The segment name is needed to set the data in the correct business object.
- Response
- Check the IDoc in SAP and make sure that the segment exists.
- CWYAP3007
- The child business object for the IDoc segment <insert_0> cannot be found for the <insert_1> business object. This segment cannot be set.
- Severity
- 10 : Warning
- 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.
- Response
- Ensure that the business object definition contains the correct segment or that the data from the segment is needed for the business object.
- CWYAP3008
- An event for the transaction ID <insert_0> contains an empty data record.
- Severity
- 10 : Warning
- Explanation
- An event cannot be created for an IDoc with an empty data record because there is no data to process.
- Response
- 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.
- Severity
- 20 : Error
- Explanation
- An endpoint needs to be active before an event can be sent to it.
- Response
- This is an unexpected error. Make sure that the endpoint is active.
- CWYAP3010
- An empty value cannot be set for the DummyKey property from the foreign key reference.
- Severity
- 20 : Error
- 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.
- Response
- 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 not valid. Currently it is set to <insert_0>.
- Severity
- 20 : Error
- Explanation
- The value specified in the foreign key application-specific information does not point to a valid property in the business object.
- Response
- Ensure that the foreign key application-specific information for the DummyKey property is correct.
- CWYAP3012
- A NULL value was found for the <insert_0> property in business object <insert_1>. The value for the DummyKey property could not be set and the event will fail.
- Severity
- 20 : Error
- 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.
- Response
- 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.
- CWYAP3013
- The foreign key application-specific information for the DummyKey property cannot be set to a contained (complex) type property.
- Severity
- 20 : Error
- Explanation
- The foreign key application-specific information must be set to a simple property.
- Response
- Check the XPath value specified in the application-specific information for the DummyKey property.
- CWYAP3014
- The operation metadata is incorrect. For the IDoc type <insert_0>, the combination of MsgType=<insert_1>, MsgCode=<insert_2>, and MsgFunction=<insert_3> is already mapped to the <insert_4> operation.
- Severity
- 20 : Error
- Explanation
- Two operations for the same IDoc type cannot have the same values for the MsgType, MsgCode, and MsgFunction.
- Response
- Check the operation application-specific information, and specify a valid combination of MsgType, MsgCode, and MsgFunction.
- CWYAP3015
- For the IDoc type <insert_0>, the combination MsgType=<insert_1>, MsgCode=<insert_2>, and MsgFunction=<insert_3> could not be found in the application-specific information for any of the operations.
- Severity
- 20 : Error
- Explanation
- The MsgType, MsgCode, and MsgFunction need to be set so that the operation can be determined.
- Response
- Check the operation application-specific information, and specify a valid combination of MsgType, MsgCode, and MsgFunction.
- CWYAP3016
- The business object operation is set to <insert_0>. ALE outbound processing supports only EXECUTE as an operation.
- Severity
- 20 : Error
- Explanation
- For ALE outbound processing, the adapter does not support any operations other than EXECUTE.
- Response
- Change the operation that is set on the object to EXECUTE.
- CWYAP3017
- The function name in the InteractionSpec is empty. For ALE outbound operations, only EXECUTE is supported as a function name.
- Severity
- 20 : Error
- Explanation
- A function name of EXECUTE is required for outbound processing.
- Response
- Set EXECUTE as the function name in the InteractionSpec.
- CWYAP3018
- 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 <insert_0>.
- Severity
- 20 : Error
- Explanation
- A function name of EXECUTE is required for outbound processing.
- Response
- Set EXECUTE as the function name in InteractionSpec.
- CWYAP3019
- The SapIDocControlRecord child object is not valid in the <insert_0> business object.
- Severity
- 20 : Error
- Explanation
- The structure of the SapIDocControlRecord child object has caused a processing error.
- Response
- Correct the business object structure.
- CWYAP3020
- An unexpected, unchecked exception was generated while delivering an event to the <insert_0> endpoint.
- Severity
- 20 : Error
- Explanation
- An unexpected error occurred while delivering the business object to an endpoint.
- Response
- Check the previous exception messages and correct the error.
- CWYAP3021
- The ALE event listeners cannot be restarted because the retry limit has been reached.
- Severity
- 20 : Error
- Explanation
- Attempts to restart the ALE event listeners have failed. The SAP system might be down.
- Response
- After ensuring that the SAP system is accessible, try to stop and then restart the adapter.
- CWYAP3022
- The retry mechanism has failed to restart the existing ALE event listeners. The adapter will attempt to start new listeners.
- Severity
- 10 : Warning
- Explanation
- If the retry mechanism cannot restart existing listeners, the adapter will attempt to start new ALE event listeners.
- Response
- Configure the RestartLimit and the RestartInterval properties appropriately to make sure that 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.
- Severity
- 20 : Error
- Explanation
- J2C local transactions are only supported when the SAPTransactionID property is present.
- Response
- Make sure that the business object definition is valid.
- CWYAP3024
- You must set valid values for the following mandatory IDocControlRecord parameters: <insert_0>, <insert_1>, <insert_2>, <insert_3>, <insert_4>, and <insert_5>.
- Severity
- 20 : Error
- Explanation
- IDocs cannot be posted to the SAP system if any of the required fields in the control record are not set.
- Response
- Make sure that all of the required fields are set in the control record.
- CWYAP3025
- Error: The remote function <insert_0> cannot be found.
- Severity
- 20 : Error
- Explanation
- Check the SAP system to make sure the remote function you are trying to call is available.
- Response
- Make sure that the remote function is available in the SAP system.
- CWYAP3026
- The adapter is trying to restart ALE event listeners. Retry number <insert_0> of <insert_1> total retries.
- Severity
- 0 : Information
- Explanation
- ALE event listeners have stopped listening and are being restarted.
- Response
- 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.
- CWYAP3027
- RetryLimit is configured as 0. The adapter will try to restart the ALE event listeners infinitely. The current retry number is <insert_0>.
- Severity
- 10 : Warning
- Explanation
- ALE event listeners have stopped listening and are being restarted.
- Response
- 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.
- CWYAP3040
- The value for the Boolean SplitIDocPacket application-specific information of <insert_0> is unsupported.
- Severity
- 20 : Error
- Explanation
- None of the expected values for the SplitIDocPacket application-specific information were found.
- Response
- Check the value in the SplitIDocPacket application-specific information of the business object.
- CWYAP3041
- The value for the Type application-specific information of <insert_0> is unsupported.
- Severity
- 20 : Error
- Explanation
- None of the expected values for the Type application-specific information were found.
- Response
- Check the value in the Type application-specific information of the business object. Supported values are IDOC and UNPARSED.
- CWYAP3042
- The <insert_0> business graph specified in the <insert_1> namespace cannot be created.
- Severity
- 20 : Error
- Explanation
- The business graph might not exist or might exist in a different namespace.
- Response
- Ensure that the business graph exists in the specified namespace.
- CWYAP3043
- The <insert_0> business object cannot be created.
- Severity
- 20 : Error
- Explanation
- The business object either might not exist, might be in the wrong namespace, or might not be located in the class path.
- Response
- 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 <insert_0>.
- Severity
- 20 : Error
- Explanation
- The xpath found in the application-specific information might be incorrect or the foreign key property might not exist.
- Response
- Ensure that either 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: <insert_0>
- Severity
- 20 : Error
- Explanation
- The business object might either not exist, might be located in the wrong namespace, or might not be in the class path.
- Response
- 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: <insert_0>
- Severity
- 20 : Error
- Explanation
- When generating the object with the data from the SAP system, an exception occurred with the application-specific information.
- Response
- Check the exception details in the error message for more information about the problem with the application-specific information.
- CWYAP3047
- An exception occurred during object generation. Exception: <insert_0>
- Severity
- 20 : Error
- Explanation
- An exception occurred when generating the object with the data from the SAP system.
- Response
- Check the exception details in the error message for specific details about the problem.
- CWYAP3048
- The child object <insert_0> is not expected in the IDoc control record object.
- Severity
- 20 : Error
- Explanation
- The IDoc control record object should have only simple properties.
- Response
- Remove the child object.
- CWYAP3049
- The segment name for some IDoc data cannot be found for the IDoc number <insert_0>. This data cannot be processed.
- Severity
- 20 : Error
- Explanation
- The IDoc data from the SAP system is incomplete and therefore cannot be processed.
- Response
- 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 <insert_0>. Exception: <insert_1>
- Severity
- 20 : Error
- Explanation
- An exception occurred while processing the segment data from the SAP system.
- Response
- Refer to details in the exception for more information about the problem.
- CWYAP3051
- The maxLength application-specific information for the <insert_0> property cannot be obtained.
- Severity
- 20 : Error
- Explanation
- The maxLength metadata for the given property cannot be found.
- Response
- Ensure that there is a maxLength value for the given property.
- CWYAP3052
- An exception occurred while retrieving application-specific information metadata. Exception: <insert_0>
- Severity
- 20 : Error
- Explanation
- An exception occurred while retrieving application-specific information metadata.
- Response
- Check the 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: <insert_0>
- Severity
- 20 : Error
- Explanation
- An exception occurred while retrieving the application-specific information metadata for the DummyKey property.
- Response
- Check the details in the error message for the specific issue with the metadata.
- CWYAP3054
- The event for the transaction ID <insert_0> contains no data for any of the segments.
- Severity
- 20 : Error
- Explanation
- No object can be created if there is no data.
- Response
- Check the 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: <insert_0>
- Severity
- 20 : Error
- Explanation
- An exception occurred while determining the operation.
- Response
- Check the details in the error message for the specific issue with the operation.
- CWYAP3056
- The operation metadata is incorrect. A combination of IDocType <insert_0>, MsgType <insert_1>, MsgCode <insert_2>, and MsgFunction <insert_3> is already mapped to operation <insert_4>.
- Severity
- 20 : Error
- Explanation
- The combination of operation metadata can only occur once for the correct operation to be determined.
- Response
- Change the operation metadata so that the combination occurs in one operation only.
- CWYAP3057
- The operation for the combination of IDocType <insert_0>, MsgType <insert_1>, MsgCode <insert_2>, and MsgFunction <insert_3> cannot be determined.
- Severity
- 20 : Error
- Explanation
- There is no operation metadata set that matches the data in the IDoc.
- Response
- Set the operation metadata for the IDoc type.
- CWYAP3058
- The notification method for event delivery cannot be determined. Exception: <insert_0>
- Severity
- 20 : Error
- Explanation
- The notification method is needed to send events to the endpoint.
- Response
- Check the details in the error message for the specific issue with the notification method.
- CWYAP3059
- An unexpected, unchecked exception occurred while delivering an event to the <insert_0> endpoint. Exception: <insert_1>
- Severity
- 20 : Error
- Explanation
- An error occurred while attempting to deliver the event to the endpoint.
- Response
- Check the exception details in the error message for the specific reason for the exception.
- CWYAP3060
- An endpoint is unavailable for the notification method specified. Exception: <insert_0>
- Severity
- 20 : Error
- Explanation
- An endpoint is needed for an event to be delivered.
- Response
- Check the details in the error message for the reason why the endpoint is unavailable.
- CWYAP3061
- An exception occurred while calling the <insert_0> method for a message endpoint. Exception: <insert_0>
- Severity
- 20 : Error
- Explanation
- One of the methods called for sending an event to the message endpoint caused an exception.
- Response
- Check the exception details in the error message for the specific reason that the exception occurred.
- CWYAP3062
- An error occurred while processing transaction ID <insert_0>, and the IgnoreIDocPacketErrors configuration property is not set. Processing is ending. The failure occurred in IDoc number <insert_1>.
- Severity
- 20 : Error
- 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.
- Response
- Either resolve the error in the IDoc, or set the IgnoreIDocPacketErrors configuration property to ignore the error.
- CWYAP3063
- The verb property is set to <insert_0> in the business graph. ALE outbound processing does not use the verb property. This interface supports only EXECUTE as an operation.
- Severity
- 20 : Error
- Explanation
- The value in the verb property should be empty.
- Response
- Remove the value that has been set in the verb property.
- CWYAP3064
- In the method <insert_0>, the IDoc wrapper is present but there is a single cardinality DataRecord object in the wrapper.
- Severity
- 20 : Error
- Explanation
- The DataRecord object needs to have multiple cardinality.
- Response
- Change the DataRecord object to have multiple cardinality.
- CWYAP3065
- An invalid JCo connection was encountered while sending an IDoc. Error message: <insert_0>
- Severity
- 20 : Error
- Explanation
- The JCo connection properties are not valid.
- Response
- Correct the JCo connection properties.
- CWYAP3066
- The adapter Inbound call failed while the transaction ID <insert_0> was being processed; however, processing will continue. The failure occurred for the IDoc number <insert_1>.
- Severity
- 20 : Error
- Explanation
- An error has occurred in an IDoc, but because the IgnoreIDocPacketErrors property has been set, processing will continue.
- Response
- Resolve the error in the IDoc and resend it.
- CWYAP3067
- The <insert_0> property could not be found. The IDoc number cannot be determined.
- Severity
- 20 : Error
- Explanation
- To determine the IDoc number, the SapIDocControlRecord property is needed.
- Response
- Resolve the error in the business object for the property specified in the error message.
- CWYAP3068
- The Cursor.getNext() method call failed. Error: <insert_1>
- Severity
- 20 : Error
- 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.
- Response
- . Verify that the input business object Cursor <insert_0> data is initialized before calling the getNext() method.
- CWYAP3069
- An error occurred while getting metadata for property <insert_0>. Error: <insert_1>
- Severity
- 20 : Error
- Explanation
- An error was encountered while processing the property metadata.
- Response
- Resolve the error in the business object for the property specified in the error message.
- CWYAP3070
- The ALE Outbound call is unable to retrieve the transaction ID from the SAPTransactionID field. Error: <insert_0>
- Severity
- 20 : Error
- Explanation
- The adapter cannot read the transaction ID from the Accessor.
- Response
- Verify that this call is a transactional call.
- CWYAP3071
- The Accessor for verb <insert_0> cannot be obtained. Error: <insert_1>
- Severity
- 20 : Error
- Explanation
- ALE Outbound processing does not use the verb property. This interface supports only EXECUTE as an operation.
- Response
- Either unset the verb, or set it to null for ALE Outbound processing.
- CWYAP3072
- Error: <insert_0>
- Severity
- 20 : Error
- Explanation
- Check the exception message to determine the problem.
- CWYAP3073
- An error occurred while calling the getNext() method on the OutputCursor object.
- Severity
- 20 : Error
- Explanation
- The data has not been populated in the Cursor.
- Response
- Check the exception message to determine the problem.
- CWYAP3074
- Error: <insert_0>
- Severity
- 20 : Error
- Explanation
- Check the exception message to determine the problem.
- CWYAP3075
- An error occurred while calling the getNext() method on the TopLevelcursor.
- Severity
- 20 : Error
- Explanation
- The data has not been populated in the Cursor.
- Response
- Ensure that data has been set on the Cursor.
- CWYAP3076
- An error occurred while getting metadata. Error: <insert_0>
- Severity
- 20 : Error
- Explanation
- Metadata is not valid.
- Response
- Check the exception message to determine the problem.
- CWYAP3077
- An error occurred while getting metadata. Error: <insert_0>
- Severity
- 20 : Error
- Explanation
- The metadata is not valid.
- Response
- Check the exception message to determine the problem.
- CWYAP3078
- An error occurred while getting metadata. Error: <insert_0>
- Severity
- 20 : Error
- Explanation
- The metadata is not valid.
- Response
- Check the exception message to determine the problem.
- CWYAP3079
- An error occurred while getting metadata. Error: <insert_0>
- Severity
- 20 : Error
- Explanation
- The metadata is not valid.
- Response
- Check the exception message to determine the problem.
- CWYAP3080
- The adapter cannot find local transaction support in the current resource adapter, which is required for Queued RFC (qRFC) behavior. The IDoc is being processed using Transactional RFC (tRFC). Message: <insert_0>
- Severity
- 20 : Error
- Explanation
- The IDoc is being processed using tRFC. Because local transactions are not supported, qRFC cannot be used.
- Response
- Use the _TX version of the RAR file to run the qRFC call.
- CWYAP3081
- A valid queue name value was not found. The IDoc will be processed with tRFC. Queued RFC(qRFC) cannot be supported. Message: <insert_0>
- Severity
- 10 : Warning
- Explanation
- The IDoc is being processed with tRFC because qRFC cannot be supported without a valid queue name.
- Response
- The IDoc is being processed using the default protocol.
- CWYAP3082
- A qRFC queue list was not found in the enterprise information system (EIS).
- Severity
- 20 : Error
- Explanation
- No qRFC queue is available in the EIS; therefore, qRFC functionality cannot be supported.
- Response
- Ensure that the queue mentioned is created and is usable in the SAP EIS.
- CWYAP3083
- The value for the Dummy Key <insert_0> is null.
- Severity
- 10 : Warning
- Explanation
- The value of the DummyKey XPATH has been assigned a null value.
- Response
- Provide a value for the field that corresponds to the DummyKey.
- CWYAP3084
- The selected IDOC, <insert_0>, has unreleased segments.
- Severity
- 0 : Information
- Explanation
- The selected IDOC contains segments that are still not released. The adapter might experience runtime issues while working with this IDOC.
- Response
- No action is required.
- CWYAP3085
- Unable to find business object definition for segment <insert_0>.
- Severity
- 10 : Warning
- Explanation
- There is a mismatch between segment definition and business object definition.
- Response
- Ensure that the IDoc sent from SAP system is the same version as discovered during metadata discovery.