Below table details the likely Integration Errors and suggested areas for troubleshooting each. If in doubt, please raise a support ticket via support@basistechnologies.com
| Code | Example Message | Suggested root-cause / areas for troubleshooting |
|---|---|---|
| 1 | Notification type & is not supported | The ActiveControl notification API was called with an unknown notification type. |
| 2 | & is not a merge target | The polling program will report this if the target in the selection screen is invalid. |
| 3 | There are no transports to send to & | The polling program will report this. |
| 4 | Not all objects of request & were merged in target &. (&) | The message will appear either when the notification API is called with “C” or when a transport with AC status = “To be completed” is processed AND there are outstanding objects in this transport that are not yet merged in the target system. Check the status table for the status of all objects of the TR. |
| 5 | There are & pending requests containing some of the objects in req. & (&) | This error will occur when trying to merge or complete a request that contains objects that are part of other still pending requests. Running the function module /BTI/TE_SS_GET_DEPENDENCIES should output a list of the conflicting requests. |
| 6 | Error when releasing the TOC for new objects: | New objects are moved to the target system via a TOC or via the original request. If either cannot be released, this error occurs. The error after the “:” should give a hint as to why. The status table may have the problematic TR in the column “IMPORTED_REQ”. |
| 7 | Error when creating the TOC for new objects: | New objects are moved to the target system via a TOC or via the original request. If the TOC couldn’t be created in the source system, this error occurs. The error after the “:” my give a hint as to why. Root cause could be that the object list is empty or that the RFC connection is down . |
| 8 | Error when creating merge request: | The error happens in the target system when creating the merge workbench request or when trying to add the objects to it. The error after the “:” was returned by the standard SAP function, please look up this error message first. The status table may have the problematic TR in the column “MERGE_REQ”. |
| 9 | Error when marking request as having been manually applied | The original request is marked as “manually applied” to the target system because no actual import takes place for existing objects. If that step fails, this error occurs. Try marking it as manually applied in the AC GUI. The merge request is in column “MERGE_REQ” in the status table. |
| 10 | Error when preparing to import new objects, check log and target/location | This error occurs when trying to import a request. Check the log table. Check the target, location and source/target systems in the status table. Possibly, the wrong target was set as parameter for the polling report. |
| 11 | ToC form creation failed (&): | The standard transport form saving function module encountered a problem. Try creating a transport form manually for the TR and check the error message. |
| 12 | Merge form creation failed (&): | The standard transport form saving function module encountered a problem. Try creating a transport form manually for the TR and check the error message. |
| 14 | Object existence check failed because no check function exists for type | The object existence check in the target system was unsuccessful because the request contains objects of unsupported type. Try removing the unsupported objects from the TR. |
| 15 | Error when deleting transport form & | Sometimes a transport form has to be deleted. Most likely it was locked by a user or the current user does not have authorization. |
| 16 | Error when adding transport form & to control point | The TOC for new objects could not be added to the import queue of the merge target. Is the location and target correct? |
| 17 | Error when approving transport form | When trying to complete, the original form could not be approved out of the outbox of the merge target. Perhaps the form was already approved manually or the target is invalid. |
| 18 | The overtake and regression check found & dependent request(s) for & (&) | This error will occur when trying to merge or complete a request that contains objects that are part of other still pending requests. Run the overtake and regression analyzer in the Windows GUI for a list of transports. |
| 19 | Merge API was called with notification type ‘&’ | Not an error |
| 20 | No transport objects that need to be merged were found | The processing report started the merge for a request that doesn’t have objects that need to be merged – this should not happen. |
| 21 | Request & was not released. Import aborted. | Obsolete |
| 22 | Timeout when releasing request & | The parameter ybt_cts/sync_release_timeout controls the time to wait before timeout. |
| 23 | Import of request & failed with RC=8 | This message will be written to the log table if the import fails. |
| 24 | Cannot cancel request & in target & (&) | It is not allowed to cancel a request that contains objects that are already completed, marked as “to be completed”, or in an error state. |
| 25 | Error returned by & | Error during polling. The appended error message was returned by the smartRetrofit API. |
| 26 | Cannot reach target system & (RFC) | Self-explanatory – check RFCs. |
| 27 | No handler class maintained for status type &. Check /BTI/TE_SS_HANDL. | Customizing issue. Check table /BTI/TE_SS_HANDL. |
| 28 | & status entries will be processed | Not an error |
| 29 | Entry processed successfully | Not an error |
| 30 | Entry not updated | Not an error |
| 31 | Processing class was called for entries with incorrect status | This indicates a bug in the processing report. |
| 32 | Dependency API was called | Not an error |
| 33 | Entry processed with errors, see log table for details | Not an error |
| 34 | The import of request & returned with warnings. Return code: &. (ignored) | Non-critical return codes during import are ignored. Check the import log in the ActiveControl GUI for the import log. |
| 35 | Cancelling a merged request is not allowed, the transport will be locked | It is not allowed to cancel a request that contains objects that are already merged or marked as to be merged. The transport form will be locked during cancellation. |
| 36 | Could not lock transport form & | During cancellation, locking the transport form failed. This message will only be in the log table because it’s not a critical exception. |
| 37 | Cannot determine the ActiveControl target from the system ID ‘&’. | The system ID, e.g. HD2, is ambiguous. Check if there are more than one ActiveControl target ID for the same request and the same system ID in the status table. |
Post your comment on this topic.