CWYAP3000-3999: SAP Resource Adapter - ALE IDoc processing
- CWYAP3001
- The business object structure for the business object <insert_0> is invalid. The Control and Data record objects cannot be determined. Error: <insert_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.
- Response
- Check the business object structure.
- CWYAP3002
- The business object structure for the business object <insert_0> is invalid. The property <insert_1> cannot be processed. Error: <insert_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.
- Response
- Check the business object structure.
- CWYAP3003
- The value for the NameOfTableStructure property in the control record is invalid. The current value is set to <insert_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.
- Response
- 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 <insert_0>, the value for the property <insert_1> has been truncated from <insert_2> to <insert_3>.
- 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 of the property 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 invalid. The current value is set to <insert_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.
- Response
- 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 <insert_0>.
- 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 segment <insert_0> cannot be found for the business object <insert_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.
- Response
- 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 <insert_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.
- 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.
- Explanation
- An endpoint needs to be alive before an event can be sent to it.
- Response
- 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.
- 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 invalid. Currently it is set to <insert_0>.
- Explanation
- The value specified in the foreign key application-specific information does not point to a valid property in the business object.
- Response
- Check the foreign key application-specific information for the DummyKey property.
- CWYAP3012
- A NULL value was found for the business object <insert_1>, property <insert_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.
- 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.
- 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.
- Response
- Check 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 operation <insert_4>.
- 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.
- 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.
- Explanation
- The MsgType, MsgCode, and MsgFunction need to be set so that the operation can be determined.
- Response
- Check the operation application-specific information.
- CWYAP3016
- The business object operation is set to <insert_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.
- Response
- Check the operation that is set in the object.
- CWYAP3017
- 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 any outbound processing.
- Response
- Set EXECUTE as the function name in the InteractionSpec.
- 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 <insert_0>.
- Explanation
- A function name of EXECUTE is required for any outbound processing.
- Response
- Set EXECUTE as the function name in InteractionSpec.
- CWYAP3019
- The SapIDocControlRecord child object is invalid in the business object <insert_0>.
- Explanation
- The structure of the SapIDocControlRecord child object has caused a processing error.
- Response
- Check the business object structure.
- CWYAP3020
- An unexpected, unchecked exception was caught while delivering an event to endpoint <insert_0>.
- Explanation
- An unexpected error was generated 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.
- Explanation
- Attempts to restart the ALE event listeners have failed. The SAP system might be down.
- Response
- 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 listeners, the adapter will attempt to start new ALE Event Listeners.
- Response
- Configure the RestartLimit and the RestartInterval 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.
- 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>.
- Explanation
- The IDoc posting to the SAP system will fail if all 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.
- Explanation
- Check the SAP system to make sure the remote function you are trying to call is available.
- Response
- Make sure that the SAP system has this remote function.
- CWYAP3026
- Trying to restart ALE Event Listeners. Retry number <insert_0> of <insert_1> total retries.
- Explanation
- ALE Event Listners 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 appropriate value.
- CWYAP3027
- RetryLimit is configured as 0. Adapter will try to restart the ALE Event Listeners infinitely. Current retry number is <insert_0>.
- 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 appropriate value.
- CWYAP3040
- The value for the SplitIDocPacket application-specific information of <insert_0> is unsupported.
- 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.
- 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.
- CWYAP3042
- The business graph <insert_0> specified in the Namespace <insert_1> cannot be created.
- 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 business object <insert_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.
- 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>.
- Explanation
- The xpath found in the application-specific information might be incorrect or the foreign key property might not exist.
- Response
- 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: <insert_0>
- Explanation
- The business object might either not exist, be located in the wrong Namespace, or 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>
- Explanation
- An exception occurred with the application-specific information when generating the object with the data from the SAP system.
- Response
- Check the exception details in the error message to see what the issue is for the application-specific information.
- CWYAP3047
- An exception occurred during object generation. Exception: <insert_0>
- 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 the specific issue.
- CWYAP3048
- The child object <insert_0>, is not expected in the IDoc control record object.
- Explanation
- The IDoc control record object should have only simple properties.
- Response
- The child object should be removed.
- CWYAP3049
- The segment name for some IDoc data cannot be found for the IDoc number <insert_0>. This data cannot be processed.
- 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>
- Explanation
- An exception occurred while processing the segment data from the SAP system.
- Response
- Check the exception details in the error message for the specific issue.
- CWYAP3051
- The maxLength application-specific information for the property <insert_0> cannot be obtained.
- Explanation
- The maxLength metadata for the given property cannot be found.
- Response
- Check to see if there is a maxLength for the given property.
- CWYAP3052
- An exception occurred while retrieving application-specific information metadata. Exception: <insert_0>
- Explanation
- An exception occurred while retrieving application-specific information metadata.
- Response
- 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: <insert_0>
- Explanation
- An exception occurred while retrieving the application-specific information metadata for the DummyKey property.
- Response
- Check the exception 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.
- Explanation
- No object can be created if there is no data.
- Response
- 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: <insert_0>
- Explanation
- An exception occurred while determining the operation.
- Response
- 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 <insert_0>, MsgType <insert_1>, MsgCode <insert_2>, and MsgFunction <insert_3> is already mapped to operation <insert_4>.
- Explanation
- The combination of operation metadata can only occur once so that the correct operation can be determined.
- Response
- Change the operation metadata so that the combination occurs only in one operation.
- CWYAP3057
- The operation for the combination of IDocType <insert_0>, MsgType <insert_1>, MsgCode <insert_2>, and MsgFunction <insert_3> cannot be determined.
- Explanation
- There is no operation metadata set to match 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>
- Explanation
- The notification method is needed to send events to the endpoint.
- Response
- Check the exception 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 endpoint <insert_0>. Exception: <insert_1>
- 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 issue with delivering the event.
- CWYAP3060
- An endpoint is unavailable for the notification method specified. Exception: <insert_0>
- Explanation
- An endpoint is needed for an event to be delivered.
- Response
- 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 <insert_0> method for a message endpoint. Exception: <insert_0>
- 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 issue in calling the method.
- 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>.
- 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.
- 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 only supports EXECUTE as an operation.
- Explanation
- The value in the verb property should be empty.
- Response
- Remove the value that has been set in the verb property.
- CWYAP3064
- Error In the method <insert_0>, the IDoc wrapper is found but there is a single cardinality DataRecord object in the wrapper.
- 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>
- Explanation
- The JCo connection properties are invalid.
- Response
- Check 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>.
- 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 property <insert_0> could not be found. The IDoc number cannot be determined.
- 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
- Cursor.getNext failed, verify that the input business object Cursor <insert_0> data is initialized. Error Message: <insert_1>
- Explanation
- The input data has not been populated in the input business object Cursor.
- Response
- Input business object data may not have been initialized in the business object specified in the error message.
- CWYAP3069
- Error while getting metadata for property <insert_0>. Error Message: <insert_1>
- 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
- ALE Outbound call is unable to retrieve the transactionID from the 'SAPTransactionID' field. Error Message=<insert_0>.
- Explanation
- Unable to read the transaction ID from the Accessor.
- Response
- Verify that this call is a transactional call .
- CWYAP3071
- Unable to get the Accessor for verb <insert_0>. Error Message: <insert_1>
- Explanation
- ALE Outbound processing does not use the verb property. This interface only supports EXECUTE as an operation.
- Response
- Unset or set verb to null for ALE Outbound. ALE Outbound processing does not use the verb property. This interface only supports EXECUTE as an operation.
- CWYAP3071
- Unable to find local transaction support, which is required for qRFC behavior. IDoc is processed using tRFC. <insert_0>
- Explanation
- IDoc processed using tRFC. Local transactions are not supported, without which qRFC cannot be used.
- Response
- IDoc processed using default protocol.
- CWYAP3072
- Error Message: <insert_0>
- Explanation
- Check the exception message to determine the problem.
- Response
- Check the exception message to determine the problem.
- CWYAP3072
- Valid queue name value not found. IDoc will be processed with tRFC. qRFC will not be supported. <insert_0>
- Explanation
- Queue name value not found. IDoc will be processed with tRFC. qRFC cannot be supported without a valid queue name.
- Response
- IDoc processed using default protocol.
- CWYAP3073
- Error while calling getNext() on the OutputCursor
- Explanation
- The data has not been populated in the Cursor.
- Response
- Check the exception message to determine the problem.
- CWYAP3073
- qRFC queue list not found on the EIS System.
- Explanation
- There is no queue available on the EIS System. Hence, qRFC functionality cannot be supported.
- Response
- No qRFC queue are available on the EIS System.
- CWYAP3074
- Error Message: <insert_0>
- Explanation
- Check the exception message to determine the problem.
- Response
- Check the exception message to determine the problem.
- CWYAP3075
- Error while calling getNext() on the TopLevelcursor
- Explanation
- The data has not been populated in the Cursor.
- Response
- Ensure that data has been set on the Cursor.
- CWYAP3076
- Error while getting metadata. Error Message: <insert_0>
- Explanation
- Metadata is invalid
- Response
- Check the exception message to determine the problem.
- CWYAP3077
- Error while getting metadata. Error Message: <insert_0>
- Explanation
- The metadata is invalid.
- Response
- Check the exception message to determine the problem
- CWYAP3078
- Error while getting metadata. Error Message: <insert_0>
- Explanation
- The metadata is invalid.
- Response
- Check the exception message to determine the problem.
- CWYAP3079
- Error while getting metadata. Error Message: <insert_0>
- Explanation
- The metadata is invalid.
- Response
- Check the exception message to determine the problem.