CWYEB3000-3999: WebSphere Adapters for Siebel - Adapter Classes
- CWYEB3101
- The object level metadata for business object <insert_0> could not be retrieved.
- Severity
- 30 : Severe error
- Explanation
- The metadata for the specified object could not be retrieved.
- Response
- Ensure that the business object level metadata is populated for the specified business object.
- CWYEB3102
- An exception occurred while processing the service data object (SDO), reason: <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The output property set is empty.
- Response
- Check the log file for the reason. Correct the errors and resend the transaction.
- CWYEB3103
- The metadata for property " <insert_0> " could not be obtained.
- Severity
- 30 : Severe error
- Explanation
- This error can occur if the metadata is empty or invalid for the specified property.
- Response
- Correct the metadata for the specified property in the business object.
- CWYEB3104
- A Siebel exception occurred. Reason: <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The invocation of the specified method on the business service failed.
- Response
- Check the log file for the reason. Correct the errors and resend the transaction.
- CWYEB3105
- No key attribute is found set.
- Severity
- 30 : Severe error
- Explanation
- The object key specified in the Object Key field of the event component appears to be empty.
- Response
- Correct the object key in the event table.
- CWYEB3106
- Attribute <insert_0>, defined as the PrimaryRowId, is empty.
- Severity
- 10 : Warning
- Explanation
- The attribute value that is specified as the PrimaryRowId is empty.
- Response
- Ensure that the attribute specified as the PrimaryRowId is populated.
- CWYEB3107
- The business object level metadata is empty.
- Severity
- 10 : Warning
- Explanation
- The business object level metadata cannot be empty, it needs to be set.
- Response
- Ensure that the object level metadata is populated with the correct information.
- CWYEB3108
- Attribute <insert_0> is defined as a single container, but multiple objects were returned.
- Severity
- 10 : Warning
- Explanation
- The attribute in the business object is defined as a single container, but more than one object was retrieved.
- Response
- If the specified object is defined as a single container, change the definition to multiple if necessary.
- CWYEB3109
- The property set could not be constructed from the input business object.
- Severity
- 30 : Severe error
- Explanation
- The property set could not be constructed from the input business object.
- Response
- Check the log file for the exact error message. Take corrective action as needed and resend the transaction.
- CWYEB3110
- The method invoked on the business service, has failed.
- Severity
- 30 : Severe error
- Explanation
- The method invoked on the business service, has failed.
- Response
- Check the log file for the exact error message. Take corrective action as needed and resend the transaction.
- CWYEB3111
- The business object could not be created from the output property set.
- Severity
- 30 : Severe error
- Explanation
- The business object could not be created from the output property set.
- Response
- Check the log file to get the exact error message. Take corrective action as needed and resend the transaction.
- CWYEB3112
- Application-specific information for the business service name is missing from the business object <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The transaction has been terminated as the application-specific information for the BSN tag is empty.
- Response
- Set the object level application-specific information for the tag, BSN.
- CWYEB3113
- Application-specific information is null in the business object <insert_0> for the attribute <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- The transaction has been terminated as the application-specific information for the FN tag is empty.
- Response
- Set the FN tag with the field name of the specified attribute.
- CWYEB3201
- Logging off failed! Reason <insert_0>
- Severity
- 30 : Severe error
- Explanation
- If the Siebel server is down, the adapter will fail when trying to log off the beans.
- Response
- Check the Siebel server log file for the error.
- CWYEB3202
- Detach failed!
- Severity
- 30 : Severe error
- Explanation
- If the Siebel server is down, the adapter will fail when trying to detach the beans.
- Response
- Check the Siebel server log file for the reason.
- CWYEB3203
- Login failed!
- Severity
- 30 : Severe error
- Explanation
- If the Siebel server is down, the login attempt will fail.
- Response
- Check your Siebel server log file for the reason
- CWYEB3301
- The ManagedConnection is invalid.
- Severity
- 30 : Severe error
- Explanation
- The ManagedConnection not an instance of the SiebelManagedConnection class.
- Response
- Check the ManagedConnection.
- CWYEB3302
- An error occurred while processing the request.
- Severity
- 30 : Severe error
- Explanation
- An error occurred while processing the request.
- Response
- Check the log file for the error message.
- CWYEB3303
- The output record is not SiebelRecord type.
- Severity
- 30 : Severe error
- Explanation
- The output record is not SiebelRecord type.
- Response
- Check output record type.
- CWYEB3401
- The event id is invalid.
- Severity
- 30 : Severe error
- Explanation
- The event id is invalid.
- Response
- Ensure that the event id is of the correct data type.
- CWYEB3402
- The event time in the event component could not be converted into the proper DateTime format.
- Severity
- 30 : Severe error
- Explanation
- The event time in the event component might not be in the correct format.
- Response
- Correct the event time.
- CWYEB3403
- The event status could not be updated.
- Severity
- 30 : Severe error
- Explanation
- The adapter could not update the event status for the corresponding record in the event component.
- Response
- Check the log file for the reason.
- CWYEB3404
- The event priority could not be parsed.
- Severity
- 30 : Severe error
- Explanation
- The adapter could not parse the event priority for the corresponding record in the event component.
- Response
- Check the log file for the message.
- CWYEB3405
- The event status could not be parsed.
- Severity
- 30 : Severe error
- Explanation
- The adapter could not parse the event status for the corresponding record in the event component.
- Response
- Check the event status value in the event table and correct it.
- CWYEB3406
- The application-specific information for the event method is empty for business object <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The application-specific information event method should not be empty.
- Response
- Enter the correct value for the event method in the business object level application-specific information.
- CWYEB3407
- The event type is invalid.
- Severity
- 30 : Severe error
- Explanation
- The event type must be either Create, Update, or Delete.
- Response
- Check the event type specified in the event store and correct it.
- CWYEB3501
- The top level Siebel business component cannot be found.
- Severity
- 30 : Severe error
- Explanation
- The business component name is not set on the application-specific information of the data object.
- Response
- Check the data object definition file.
- CWYEB3502
- More than one record was returned for the top level business component.
- Severity
- 30 : Severe error
- Explanation
- The primary key property values are not unique for the business component <insert_0>.
- Response
- Check the value of the properties that are primary keys in the data object.
- CWYEB3503
- Records of the child component <insert_0> could not be retrieved.
- Severity
- 30 : Severe error
- Explanation
- The child component does not match the Siebel business component.
- Response
- Check the container metadata of this property to see if the business component matches the Siebel enterprise information system (EIS).
- CWYEB3504
- More than one record was returned for the pickList business component: <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The value of the From property is not unique for the pickList business component.
- Response
- Check the value of the From property, which is a foreign key of this pickList component.
- CWYEB3505
- The search specification for this pickList business component could not be set: <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The value of the From property is not set for the pickList business component.
- Response
- Ensure that the value is set for the From property, which is a foreign key of this pickList component.
- CWYEB3506
- The search specification for this simple attribute pickList business component cannot be set. The value of the restrict property: <insert_0> is not set.
- Severity
- 30 : Severe error
- Explanation
- The value of the restrict property is not set for the pickList business component, it should be set.
- Response
- Ensure that the value is set for the Restrict property. This will be a foreign key in this pickList business component.
- CWYEB3507
- The corresponding business component of the following property cannot be obtained: <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The metadata information of the property is not correct.
- Response
- Check the property metadata for this property, and compare it with the data structure in Siebel.
- CWYEB3508
- The field <insert_0> of the Siebel business component <insert_1> cannot be updated.
- Severity
- 30 : Severe error
- Explanation
- The specified field of the Siebel business component configuration does not have update permissions.cannot be updated.
- Response
- Check the business component configuration of the Siebel enterprise information system (EIS) to confirm if the field is inactive. If yes, do the needful to make it updatable.
- CWYEB3509
- The property metadata definition is not correct. Error :<insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The property metadata definition is wrong.
- Response
- Check the application specific information of the property, correct the same as needed and resend the transaction.
- CWYEB3510
- The key property <insert_0> value is null.
- Severity
- 30 : Severe error
- Explanation
- The key property value is null.
- Response
- Check the key property's value to see if it is set or not.
- CWYEB3511
- No record was retrieved using the search criteria provided.
- Severity
- 30 : Severe error
- Explanation
- No record exists in the Siebel system with these key values.
- Response
- Ensure that the key properties' values are correct.
- CWYEB3511
- The command factory failed to create the SiebelRetrieveCommand instance.
- Severity
- 30 : Severe error
- Explanation
- Either the business object or the business component does not exist in the Siebel system.
- Response
- Check the business object and component names in the metadata.
- CWYEB3511
- The child component relationship is incorrectly defined.
- Severity
- 30 : Severe error
- Explanation
- The child component relationship is not defined correctly.
- Response
- Check the business object definition of this attribute in the metadata and correct the same as needed.
- CWYEB3514
- The <To> application-specific information value of the pickList component is either empty or null.
- Severity
- 30 : Severe error
- Explanation
- The <To> application-specific information of the pickList component is either empty or null. Update it with the right value and resend the transaction.
- Response
- Check the business object definition of the <To> attribute of the pickList component in the metadata.
- CWYEB3515
- The fields in the <To> and <From> attributes of the pickList component do not match.
- Severity
- 30 : Severe error
- Explanation
- The fields in the <To> and <From> attributes of the pickList component must match.
- Response
- Check the business object definition of the <To> and <From> attributes of the pickList component in the metadata.
- CWYEB3516
- The property name specified in the <From> attribute of the pickList component metadata is not defined in the current data object.
- Severity
- 30 : Severe error
- Explanation
- The property name specified in the <From> attribute of the pickList component metadata is not defined in the current data object.
- Response
- Check the business object definition of the <From> attributes of the pickList component in the metadata and correct the same.
- CWYEB3516
- The property name specified in the <Restrict> attribute of the Simple pickList component metadata is not defined in the current data object.
- Severity
- 30 : Severe error
- Explanation
- The property name specified in the <Restrict> attribute of the pickList component metadata is not defined in the current data object.
- Response
- Check the business object definition of the <Restrict> properties of the pickList component in the metadata. Values are not found in the incoming business object for one or more of the <Restrict> properties. Fill in all values as needed and resend the transaction.
- CWYEB3518
- More than one record was returned for the pickList business component: <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The value of the metadata of the restrict field of this simple pickList component might not be set correctly.
- Response
- Check the metadata of the restrict field of this simple pickList component.
- CWYEB3519
- The property <insert_0> is not found in the definition of the object <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- The value of the application-specific information in the metadata of this component might not be set correctly.
- Response
- Check the metadata value to see if this is a correct property name.
- CWYEB3551
- The record for the pickList cannot be created. It is either bound or not allowed. Return <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The record for the pickList cannot be created. It is either bound or not allowed.
- Response
- Check the log file for further information and take corrective action as needed.
- CWYEB3552
- A new record cannot be created for the Siebel business object <insert_0>, business component <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- The input Siebel business object name and business component cannot be found in the Siebel server.
- Response
- Check the names of the input Siebel business object and business component.
- CWYEB3553
- A record cannot be created in the Siebel Server. Return <insert_0>
- Severity
- 30 : Severe error
- Explanation
- A record cannot be created in the Siebel server.
- Response
- Check the details of the error in the log file.
- CWYEB3554
- More than one association component was found.
- Severity
- 30 : Severe error
- Explanation
- More than one association component was found based on your input value.
- Response
- The object representing the association component in the data object hierarchy does not contain unique values. Correct the same and resend the transaction.
- CWYEB3555
- The Siebel business component cannot be associated. Return: <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The Siebel business component cannot be associated.
- Response
- Check the Siebel server exception in the log file.
- CWYEB3556
- An error occurred during the creation of the child business component. Return <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- An error occurred during the creation of the child business component.
- Response
- Check the log file for further information.
- CWYEB3558
- A record for the Siebel business component cannot be written.
- Severity
- 30 : Severe error
- Explanation
- A record for the Siebel business component cannot be written.
- Response
- Check the Siebel server exception in the log file and take corrective action as needed.
- CWYEB3559
- An error occurred while writing the record for the Siebel business component. Return <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- An error occurred while writing the record for the Siebel business component.
- Response
- Check the log file for further information.
- CWYEB3560
- An error was found while picking the record for the Siebel business component. Return <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- An error was found while picking the record for the Siebel business component.
- Response
- Check the log file for further information and take corrective action as needed.
- CWYEB3562
- The field value in the Siebel server cannot be set. Return <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The field value in the Siebel server cannot be set.
- Response
- Check the Siebel server exception in the log file and take corrective action as needed.
- CWYEB3563
- The required field <insert_0> is not set in the input data object.
- Severity
- 30 : Severe error
- Explanation
- The required field is not set in the input data object, it should be set.
- Response
- Fill in values for the required fields in the input data object.
- CWYEB3564
- The input data object contains an invalid object definition. Return <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The input data object contains an invalid object definition.
- Response
- Check the log file for the reason and take corrective action as needed.
- CWYEB3565
- Either the Siebel business object instance or the business component instance cannot be released. Return <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- Either the Siebel business object instance or the business component instance cannot be released.
- Response
- Check the log file for the exact error and take corrective action as needed.
- CWYEB3566
- The destination data object does not have the field <insert_0> that the source data object has.
- Severity
- 30 : Severe error
- Explanation
- The destination data object does not have the field that the source data object has.
- Response
- Check the destination data object and add the corresponding attribute. If not needed, remove the attribute from the source data object.
- CWYEB3571
- The Siebel business object or component cannot be obtained. Return <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The Siebel business object or component cannot be obtained.
- Response
- Check the log file for further information.
- CWYEB3572
- The child business component cannot be deleted. Return <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The child business component cannot be deleted.
- Response
- Check the log file for further information.
- CWYEB3573
- A set search specification error for the Siebel business component has occurred. Return <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- A set search specification error for the Siebel business component has occurred.
- Response
- Check the log file for further information.
- CWYEB3574
- The record to be deleted cannot be found.
- Severity
- 30 : Severe error
- Explanation
- The record to be deleted cannot be found.
- Response
- Check your input data object for incorrect key values. Correct the same and resend the transaction.
- CWYEB3575
- The record for the Siebel business component cannot be deleted. Return <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The record for the Siebel business component cannot be deleted.
- Response
- Check the Siebel server exception in the log file.
- CWYEB3576
- An error occurred while retrieving records from the Siebel server. Return <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- An error occurred while retrieving records from the Siebel server.
- Response
- Check the log file for further information.
- CWYEB3577
- The collection returned from EIS is null or empty. The RetrieveAll operation cannot be completed.
- Severity
- 30 : Severe error
- Explanation
- The RetrieveAll operation cannot proceed because the collection returned from EIS is null or empty.
- Response
- Take corrective action based on the Siebel Exception.
- CWYEB3578
- The number of instances retrieved from the EIS is <insert_0>. It exceeds the number allowed <insert_1> for the input object <insert_2>. The RetrieveAll operation cannot be completed.
- Severity
- 30 : Severe error
- Explanation
- The number of instances retrieved from the EIS exceeds the number allowed. The RetrieveAll operation cannot be completed.
- Response
- Fill in data against other attributes in the business object to add more conditionality. If it still does not help, increase the number of maximum records allowed in the interaction spec.
- CWYEB3579
- An error occurred while creating the container object for the RetrieveAll operation. Return <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- An error occurred while creating the container object for the RetrieveAll operation.
- Response
- Check the log file for further information.
- CWYEB3581
- An error occurred when the adapter attempted to associate the business component. Return <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- An error occurred when the adapter attempted to associate the business component.
- Response
- Check the Siebel server exception in the log file.
- CWYEB3583
- The child pickList business component with keys was not found: <insert_0>
- Severity
- 30 : Severe error
- Explanation
- The child pickList business component with keys was not found.
- Response
- Check the input data object. Correct the key values as needed and resend the transaction.
- CWYEB3584
- The key values to the output data object could not be set. Return: <insert_0>
- Severity
- 30 : Severe error
- Explanation
- The key values to the output data object could not be set.
- Response
- Check the log file. The data object schema should contain a key field.
- CWYEB3585
- An error occurred while checking for the existence of the Siebel business component. Return <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- An error occurred while checking for the existence of the Siebel business component.
- Response
- Check the log file for further information and take corrective action as needed.
- CWYEB3591
- Multiple records were returned for the top level business component.
- Severity
- 30 : Severe error
- Explanation
- Multiple records were returned for the top level business component.
- Response
- Ensure you have set all the required keys to make the object unique.
- CWYEB3592
- A Siebel exception was generated <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The exception was generated by the Siebel enterprise information system (EIS).
- Response
- Take corrective action based on the information provided in the log file.