IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > SAP Software > Troubleshooting and support
Unreleased IDoc segments cause exceptions
When running the external service wizard or at runtime, unreleased segments in IDocs cause the following exception error messages:
- During object discovery using the external service wizard, you might get the exception "The segment could not be read for the release <release number>.
- At run time you might encounter an error message: "Caused by: commonj.connector.runtime.DataBindingException: Failed in population return object" error. This occurs even if all the business object definitions were generated successfully for the IDoc when you ran the external service wizard.
For any IDoc segment there may be multiple segment definitions at different release levels. Some of these segments may not have been released. If an IDoc contains segments that are unreleased for the selected IDOC release version, then the external service wizard may fail. This might cause a problem for the adapter at run time as the adapter will not be able to find the business object definitions for the unreleased children segments.
For example, if the IDoc MATMAS05 has an unreleased segment E2MARAM005, the external wizard will create an E2MRAM004 (released segment) child business object definition for MATMAS05 business object instead of E2MARAM005.
To resolve this error, you can specify the release version for the IDoc when using the external service wizard to discover IDocs. The default value is the version of the SAP system you are running the wizard against. If the IDoc you selected has unreleased segments, you should set the field "IDoc release version" on "Configure Properties for <IDoc name> page of the wizard to empty (zero length string).