Error Codes
The following tables list error codes, detailed explanation of each error, and where applicable, ways to solve different errors.
Error Code and Error Message | Role | Category | Description | Solution |
---|---|---|---|---|
TIBCO-BW-SR-SAPCONNECTION-200001
Creating Shared Resource {0}. |
debug | BW-Plug-in | The SAP Connection shared resource {0} is being created. | None. |
TIBCO-BW-SR-SAPCONNECTION-200002
Starting Shared Resource {0}. |
debug | BW-Plug-in | The SAP Connection shared resource {0} is being started. | None. |
TIBCO-BW-SR-SAPCONNECTION-200003
Updating Shared Resource {0}. |
debug | BW-Plug-in | The SAP Connection shared resource {0} is being updated. | None. |
TIBCO-BW-SR-SAPCONNECTION-200004
Stopping Shared Resource {0}. |
debug | BW-Plug-in | The SAP Connection shared resource {0} is being stopped. | None. |
TIBCO-BW-SR-SAPCONNECTION-200005
Deleting Shared Resource {0}. |
debug | BW-Plug-in | The SAP Connection shared resource {0} is being deleted. | None. |
TIBCO-BW-SR-SAPCONNECTION-201001
[{0}]. |
debug | BW-Plug-in | Debug information [{0}] is generated when a JCoException is received, a function is being removed from cache, or the server connection status is changed. | None. |
TIBCO-BW-SR-SAPCONNECTION-301007
Reconnect attempt {0} for connection {1} |
debug | BW-Plug-in | This information is generated to notice that the SAP client or server connection {1} is trying to reconnect for the {0}th attempt. | None. |
TIBCO-BW-SR-SAPCONNECTION-301020
Connection disconnected |
info | BW-Plug-in | This information is generated when the SAP client connection starts to be reconnected. | None. |
TIBCO-BW-SR-SAPCONNECTION-301021
Activated timer to check connectivity to R/3 for connection-pool {0} |
info | BW-Plug-in | This information is generated when the SAP client connection starts to be reconnected. | None. |
TIBCO-BW-SR-SAPCONNECTION-401004
Server connection {0} will not be initialized: {1} |
warn | BW-Plug-in | The server connection {0} cannot be initialized when creating a server connection with the combination of the program ID, gateway host, and gateway service that have already been used by another server connection. | None. |
TIBCO-BW-SR-SAPCONNECTION-500001
Creating Shared Resource {0} failed. |
error | BW-Plug-in | Creating the SAP Connection shared resource {0} fails. | Check the items in the error message. |
TIBCO-BW-SR-SAPCONNECTION-501001
Connection Error. Unable to create a connection with the target application {0} using connection parameters {1} and the target application error is {2} |
error | BW-Plug-in | Creating a client connection with the application server {0} fails.
The SAP JCo error is {2}. |
Check the client connection parameters. |
TIBCO-BW-SR-SAPCONNECTION-501003
Client connection {0} is invalid |
error | BW-Plug-in | The client connection {0} is invalid. | Check the client connection parameters and the network connectivity. |
TIBCO-BW-SR-SAPCONNECTION-501004
Connection Error. {0} stopping due to persistent connection errors to the SAP R/3 system(s) |
error | BW-Plug-in | The client or server connection {0} is stopped because of the persistent connection errors. | Check the client or server connection parameters and the network connectivity. |
TIBCO-BW-SR-SAPCONNECTION-501007
Server connection {0} is invalid: {1} |
error | BW-Plug-in | The server connection {0} is invalid. | Check the server connection parameters and the network connectivity. |
TIBCO-BW-SR-SAPCONNECTION-501008
Starting Shared Resource {0} failed. |
error | BW-Plug-in | Starting the SAP Connection shared resource {0} fails. | Check the items in the error message. |
TIBCO-BW-SR-SAPCONNECTION-501009
Server Error: {0} |
error | BW-Plug-in | The server error {0} occurs. | Check the server connection parameters, the network connectivity, and whether the SAP system is shut down. |
TIBCO-BW-SR-SAPCONNECTION-501010
Server Exception: {0} |
error | BW-Plug-in | The server exception {0} occurs. | Check the items in the error message. |
TIBCO-BW-SR-SAPCONNECTION-501011
Server connection pool: {0} suspended due to exceeded attempts to connect to SAP system |
error | BW-Plug-in | The server connection pool is suspended when the server connection cannot be established after the maximum time interval between two successive attempts. | Check the server connection parameters, the network connectivity, and whether the SAP system is shut down. |
Error Code and Error Message | Role | Category | Description | Solution |
---|---|---|---|---|
TIBCO-BW-SR-SAPTIDMANAGER-200001
Creating Shared Resource {0}. |
debug | BW-Plug-in | The SAP TIDManager shared resource {0} is being created. | None. |
TIBCO-BW-SR-SAPTIDMANAGER-200002
Starting Shared Resource {0}. |
debug | BW-Plug-in | The SAP TIDManager shared resource {0} is being started. | None. |
TIBCO-BW-SR-SAPTIDMANAGER-200003
Updating Shared Resource {0}. |
debug | BW-Plug-in | The SAP TIDManager shared resource {0} is being updated. | None. |
TIBCO-BW-SR-SAPTIDMANAGER-200004
Stopping Shared Resource {0}. |
debug | BW-Plug-in | The SAP TIDManager shared resource {0} is being stopped. | None. |
TIBCO-BW-SR-SAPTIDMANAGER-200005
Deleting Shared Resource {0}. |
debug | BW-Plug-in | The SAP TIDManager shared resource {0} is being deleted. | None. |
TIBCO-BW-SR-SAPTIDMANAGER-500001
Creating Shared Resource {0} failed. |
error | BW-Plug-in | Creating the SAP TIDManager shared resource {0} fails. | None. |
TIBCO-BW-SR-SAPTIDMANAGER-500002
Starting TIDmanager Shared Resource {0}. |
error | BW-Plug-in | Starting the TIDManager shared resource {0} fails. | None. |
TIBCO-BW-SR-SAPTIDMANAGER-500003
Can't register JDBC driver {0}. |
error | BW-Plug-in | The JDBC driver for the TID management cannot be registered. | None. |
TIBCO-BW-SR-SAPTIDMANAGER-500004
Can't deregistered JDBC driver {0}. |
error | BW-Plug-in | The JDBC driver for the TID management cannot be unregistered. | None. |
TIBCO-BW-SR-SAPTIDMANAGER-500005
Sql Exception {0}. |
error | BW-Plug-in | The SQL exception occurs in the database. | None. |
TIBCO-BW-SR-SAPTIDMANAGER-500006
Table TIDManager does not exist in database, the URL is \u201C{0}\u201D, Please create table first! |
error | BW-Plug-in | The database table for the TID management does not exist. | None. |
Error Code and Error Message | Role | Category | Description | Solution |
---|---|---|---|---|
TIBCO-BW-PALETTE-SAP-104001
Received IDoc(s). RFC Function=[{0}], IDOC Name=[{1}], Number=[{2}], Receiving Partner=[{3}], Count=[{4}]. |
debug | BW-Plugin-in | The information about the request from the SAP system is displayed. | None. |
TIBCO-BW-PALETTE-SAP-104002
Start marshaling the IDoc, Transaction ID is [{0}]. |
debug | BW-Plugin-in | The IDoc marshal is started. | None. |
TIBCO-BW-PALETTE-SAP-104003
Finish marshalling the IDoc, the elapsed time is [{0} ms], Transaction ID is [{1}]. |
debug | BW-Plugin-in | The IDoc marshal is finished, and the elapsed time is [{0} ms]. | None. |
TIBCO-BW-PALETTE-SAP-104004
Message has been sent to queue [{0}] successfully. The content of message is {1} |
debug | BW-Plugin-in | An IDoc message is sent to the queue [{0}] successfully, and the content of the message is {1}. | None. |
TIBCO-BW-PALETTE-SAP-104005
Error occurred when processing the IDoc. The error message is [{0}]. |
error | BW-Plugin-in | The error [{0}] occurs when processing the IDoc. | None. |
TIBCO-BW-PALETTE-SAP-105001
Received the raw type of IDoc from the queue [{0}]. IDoc Name=[{1}], IDoc Number=[{2}]. |
error | BW-Plugin-in | The information about the IDoc in raw type received from the queue [{0}] is displayed. | None. |
TIBCO-BW-PALETTE-SAP-105002
Output has been generated. The content of the output is {0} |
error | BW-Plugin-in | An IDoc message is converted into the XSD format. The converted content is {0}. | None. |
TIBCO-BW-PALETTE-SAP-105003
Connection Exception occurred. EventSource will deactivate. |
error | BW-Plugin-in | The EMS server is not accessible. | Start the EMS server. |
TIBCO-BW-PALETTE-SAP-105004
Trying to see if connection is re-established...... |
error | BW-Plugin-in | Reconnecting to the EMS server is tried. | None. |
TIBCO-BW-PALETTE-SAP-105005
Connection re-established successfully. Starting EventSource |
error | BW-Plugin-in | The connection to the EMS server is established successfully. | None. |
TIBCO-BW-PALETTE-SAP-105006
Error occurred while trying to cancel reconnection mechanism scheduling |
error | BW-Plugin-in | Canceling a connection fails. | None. |
TIBCO-BW-PALETTE-SAP-105007
Connection not yet Established. Event Source not started. Retrying in 8 seconds |
error | BW-Plugin-in | Reconnecting to the EMS server is tried. | None. |
TIBCO-BW-PALETTE-SAP-105008
Error occurred when initialization. The error message is [{0}]. |
error | BW-Plugin-in | The error [{0}] occurs when initializing the IDoc Parser activity. | None. |
TIBCO-BW-PALETTE-SAP-105009
On exception in IDoc Parser from AbstractJmsReceive. Started value is [{0}]. |
error | BW-Plugin-in | An exception is returned from AbstractJmsReceive. | None. |
TIBCO-BW-PALETTE-SAP-105010
On stop in IDoc Parser from AbstractJmsReceive. Started value is [{0}]. |
error | BW-Plugin-in | The stop method is invoked by AbstractJmsReceive. | None. |
TIBCO-BW-PALETTE-SAP-105011
The IDocParser failed to a generate a new event due to schema mismatch. The IDoc set for IDocParser[{0}], the IDoc received [{1}]. |
error | BW-Plugin-in | The IDoc Parser activity fails to generate a new event due to the schema mismatch. | None. |
TIBCO-BW-PALETTE-SAP-106001
Received the message of IDoc from the queue [{0}]. IDoc Name=[{1}], IDoc Number=[{2}]. |
debug | BW-Plugin-in | An IDoc message is received from the queue [{0}]. | None. |
TIBCO-BW-PALETTE-SAP-106002
Acknowledged the message with the ID [{0}] from the queue [{1}]. |
debug | BW-Plugin-in | The received message with the ID [{0}] is acknowledged. | None. |
TIBCO-BW-PALETTE-SAP-106003
Sent the message to the error destination [{0}], due to the error [{1}]. |
debug | BW-Plugin-in | An IDoc is sent to the error destination [{0}] because of the error [{1}]. | None. |
TIBCO-BW-PALETTE-SAP-106004
Posting the IDoc to the client. TID=[{0}]. |
debug | BW-Plugin-in | An IDoc is being posted to the client. | None. |
TIBCO-BW-PALETTE-SAP-106005
Posted the IDoc to the client. TID=[{0}]. |
debug | BW-Plugin-in | An IDoc is posted to the client. | None. |
TIBCO-BW-PALETTE-SAP-106006
Error occurred when initialization. The error message is [{0}]. |
error | BW-Plugin-in | The error [{0}] occurs when initializing the IDoc Reader activity. | None. |
TIBCO-BW-PALETTE-SAP-106007
The transaction is confirmed. The TID is [{0}]. |
error | BW-Plugin-in | The transaction of posting an IDoc to the SAP system is confirmed. | None. |
TIBCO-BW-PALETTE-SAP-106008
On exception in IDoc Reader from AbstractJmsReceive. Started value is [{0}]. |
error | BW-Plugin-in | An exception is returned from AbstractJmsReceive. | None. |
TIBCO-BW-PALETTE-SAP-106009
On stop in IDoc Reader from AbstractJmsReceive. Started value is [{0}]. |
error | BW-Plugin-in | The stop method is invoked by AbstractJmsReceive. | None. |
TIBCO-BW-PALETTE-SAP-106010
Confirmation report has been published on the queue [{0}]. |
debug | BW-Plugin-in | A confirmation report is published in the confirmation queue [{0}]. | None. |
TIBCO-BW-PALETTE-SAP-106011
Received a message in the RAW format. IDoc Number = [{0}]. |
debug | BW-Plugin-in | An IDoc message in raw format is received. | None. |
TIBCO-BW-PALETTE-SAP-106012
Received a message in the XML format. IDoc Number = [{0}]. |
debug | BW-Plugin-in | An IDoc message in XML format is received. | None. |
TIBCO-BW-PALETTE-SAP-106013
Could not find the mandatory property EDI_DC40 in the message. |
error | BW-Plugin-in | The mandatory property EDI_DC40 cannot be found in the message. | None. |
TIBCO-BW-PALETTE-SAP-106014
Error occurred when getting JCo attributes. The error message is [{0}]. |
error | BW-Plugin-in | The error {0} occurs when getting JCo attributes. | Check the client connection parameters and the network connectivity. |
TIBCO-BW-PALETTE-SAP-106015
Error occurred when initialize the error IDoc destination [{0}]. The error message is [{1}]. |
error | BW-Plugin-in | The error {1} occurs when initializing the error IDoc destination [{0}]. | None. |
TIBCO-BW-PALETTE-SAP-106016
Error occurred when initialize the confirmation IDoc destination [{0}]. The error message is [{1}]. |
error | BW-Plugin-in | The error {1} occurs when initializing the confirmation IDoc destination [{0}]. | None. |
TIBCO-BW-PALETTE-SAP-106017
Error occurred when trying to send the confirmation message. The error message is [{0}]. |
error | BW-Plugin-in | The error {0} occurs when trying to send the confirmation message. | None. |
TIBCO-BW-PALETTE-SAP-106018
Application will try to establish the connection in 3 seconds. |
error | BW-Plugin-in | The plug-in tries to establish the connection in 3 seconds. | None. |
TIBCO-BW-PALETTE-SAP-106019
The connection to EMS server has been established. |
error | BW-Plugin-in | The connection to the EMS server has been established. | None. |
TIBCO-BW-PALETTE-SAP-107001
Invalid configuration data. JMS destination is not specified. |
error | BW-Plugin-in | The JMS destination is invalid. | Check the configuration of the JMS destination in the activity. |
TIBCO-BW-PALETTE-SAP-107002
Failed to create connection to the JMS server. {0} |
error | BW-Plugin-in | Creating connections to the EMS server fails. | Check the JMS Connection shared resource and whether the EMS server is running. |
TIBCO-BW-PALETTE-SAP-107003
Unable to find destination [{0}] on JMS server |
error | BW-Plugin-in | The JMS destination [{0}] cannot be found on the EMS server. | Check whether the specified destination exists on the EMS server. |
TIBCO-BW-PALETTE-SAP-107004
Error occurred when attempting to create MessageConsumer |
error | BW-Plugin-in | An error occurs when creating a message consumer. | Check the JMS Connection shared resource and whether the EMS server is running. |
TIBCO-BW-PALETTE-SAP-107005
Error occurred when attempting to receive a JMS message |
error | BW-Plugin-in | An error occurs when receiving a JMS message. | Check the activity configuration, the JMS Connection shared resource, and whether the EMS server is running. |
TIBCO-BW-PALETTE-SAP-107006
Error occurred when attempting to send a JMS message |
error | BW-Plugin-in | An error occurs when sending a JMS message. | Check the activity configuration, input data, JMS Connection shared resource, and whether the EMS server is running. |
TIBCO-BW-PALETTE-SAP-107007
Error occurred when attempting to resolve destination |
error | BW-Plugin-in | An error occurs when resolving the destination. | Check the JMS Connection shared resource and whether the EMS server is running. |
TIBCO-BW-PALETTE-SAP-107008
Invalid configuration data. JMS connection reference is not specified. |
error | BW-Plugin-in | The JMS connection reference is not specified. | Check the activity configuration for the JMS Connection reference. |
TIBCO-BW-PALETTE-SAP- 108001
Posting the Acknowledgment IDoc to the client. TID=[{0}]. |
debug | BW-Plugin-in | The plug-in is posting an acknowledgment IDoc to the client. | None. |
TIBCO-BW-PALETTE-SAP- 108002
For IDoc=[{0}] posted the Acknowledgment IDoc to the client. TID=[{1}]. |
debug | BW-Plugin-in | The acknowledgment IDoc with TID=[{1}] for IDoc=[{0}] is posted the to the client. | None. |
TIBCO-BW-PALETTE-SAP- 108003
Error occurred when posting an acknowledgment to IDoc [{0}] to SAP, error message=[{1}] |
error | BW-Plugin-in | The error [{1}] occurs when posting an acknowledgment to the IDoc [{0}] to the SAP system. | None. |
TIBCO-BW-PALETTE-SAP- 108005
Both the successMessage and the errorMessage are missing in the input data, will have no acknowledgment sent back to SAP, the Acknowledgment to the IDoc [{0}] will be skipped. |
error | BW-Plugin-in | Both the successMessage and the errorMessage items are missing in the input data, and no acknowledgment is sent back to the SAP system. The acknowledgment to IDoc [{0}] is to be skipped. | None. |
TIBCO-BW-PALETTE-SAP- 109001
Received message from the queue [{0}]. TID = [{1}], The correlationID = [{2}]. |
debug | BW-Plugin-in | The information about the IDoc confirmation message from the queue [{0}] is displayed. | None. |
TIBCO-BW-PALETTE-SAP- 109002
Successfully invoked function [{0}]. TID = [{1}], IDoc Number = [{2}]. |
debug | BW-Plugin-in | The IDoc number related to the TID = [{1}] is returned by invoking function [{0}] successfully. | None. |
TIBCO-BW-PALETTE-SAP- 109003
Successfully invoked function [{0}]. IDoc Number = [{1}], IDoc status = [{2}]. |
debug | BW-Plugin-in | The IDoc status for the IDoc with IDoc number being [{1}] is returned by invoking function [{0}] successfully. | None. |
TIBCO-BW-PALETTE-SAP- 109004
Received message from the queue [{0}]. The correlationID is [{1}]. The error message is [{2}]. |
debug | BW-Plugin-in | The IDoc Confirmation activity receives a confirmation message with the error message [{2}] from the queue [{0}] with JMS correlation ID being [{1}]. The error message includes information related to the reason the IDoc fails to be sent to the SAP server. | Check the structure of the IDoc that fails to be sent to the SAP server. |
TIBCO-BW-PALETTE-SAP- 109005
On stop in IDoc Confirmation from AbstractJmsReceive. Started value is [{0}]. |
debug | BW-Plugin-in | The status [{0}] of JMS is displayed when JMS is stopped in the IDoc Confirmation activity. | Check the JMS Connection shared resource and whether the EMS server is running. |
TIBCO-BW-PALETTE-SAP- 109006
On exception in IDoc Confirmation from AbstractJmsReceive. Started value is [{0}]. |
debug | BW-Plugin-in | The status [{0}] of JMS is displayed when an exception is returned from JMS in the IDoc Confirmation activity. | Check the JMS Connection shared resource and whether the EMS server is running. |
TIBCO-BW-PALETTE-SAP- 109007
Acknowledged the message with the ID [{0}] from the queue [{1}]. |
debug | BW-Plugin-in | The confirmation message is confirmed from the queue [{1}] with JMS correlation ID being [{0}]. | None. |
TIBCO-BW-PALETTE-SAP- 109008
Acknowledged the message with the ID [{0}] from the queue [{1}]. |
debug | BW-Plugin-in | The information about the output of the IDoc Confirmation activity is displayed. | None. |
TIBCO-BW-PALETTE-SAP- 109009
JMS Exception occurred, the error message is [{0}]. |
error | BW-Plugin-in | The error [{0}] occurs when trying to confirm the message but the JMS is not in an appropriate state. | Check the JMS Connection shared resource and whether the EMS server is running. |
TIBCO-BW-PALETTE-SAP- 109010
IDoc sent to SAP via qRFC. IDoc number is unavailable. The original TID is [{0}]. |
debug | BW-Plugin-in | The original TID [{0}] is displayed in the IDoc Confirmation activity if the IDoc is sent to the SAP server through qRFC by the IDoc Reader activity. | None. |
TIBCO-BW-PALETTE-SAP- 109011
RFC function execution failure : {0}; function name : [{1}]. |
error | BW-Plugin-in | The error [{0}] occurs if an exception is returned from the SAP server when invoking the function [{1}]. | Check whether the IDoc exists on the SAP server. |
TIBCO-BW-PALETTE-SAP-201001
{0} |
debug | BW-Plugin-in | The input of the Job Data view is displayed. | None. |
TIBCO-BW-PALETTE-SAP-201002
{0} |
debug | BW-Plugin-in | The output of the Job Data view is displayed. | None. |
TIBCO-BW-PALETTE-SAP-201003
{0} |
debug | BW-Plugin-in | The data in the console is displayed. | None. |
TIBCO-BW-PALETTE-SAP-201004
JCo Attributes {0} |
debug | BW-Plugin-in | JCo attributes are displayed. | None. |
TIBCO-BW-PALETTE-SAP-201005
Dynamic connection {0} is closed. |
debug | BW-Plugin-in | The dynamic connection is closed. | None. |
TIBCO-BW-PALETTE-SAP-201006
End Context. Session id is {0} |
debug | BW-Plugin-in | The context of the transaction ends. | None. |
TIBCO-BW-PALETTE-SAP-201007
Context timeout sets {0} |
debug | BW-Plugin-in | The context of the transaction times out. | None. |
TIBCO-BW-PALETTE-SAP-401001
Unable to convert string "{0}" to {1} for {2} in {3}, data suppressed. |
warn | BW-Plugin-in | The string {0} in the {2} field cannot be converted to the data type {1} in the {3} tab. | Check the field configuration. |
TIBCO-BW-PALETTE-SAP-500001
Invalid SAP Connection reference. SAP Connection is not specified. |
error | BW-Plugin-in | The SAP connection is not specified for the activity. | Specify the SAP connection for the activity. |
TIBCO-BW-PALETTE-SAP-500002
Invalid Server Connection reference or Server Connection is disabled. Please pick a enabled sever connection. |
error | BW-Plugin-in | The server connection reference is invalid, or the server connection is disabled. | Select an enabled server connection. |
TIBCO-BW-PALETTE-SAP-500003
Cannot get server connection {0} |
error | BW-Plugin-in | Using the server connection {0} fails. | Check the server connection parameter. |
TIBCO-BW-PALETTE-SAP-500004
{0} |
error | BW-Plugin-in | Initializing the RFC BAPI Listener activity fails. | Check the program ID, gateway service, or gateway host in the SAP connection. |
TIBCO-BW-PALETTE-SAP-501002
Context timeout is Zero, cannot continue RFC invoke in context |
error | BW-Plugin-in | The timeout value of the context is zero. | Reset the timeout value for the context. |
TIBCO-BW-PALETTE-SAP-501003
Invalid Connection for pool {0} |
error | BW-Plugin-in | The connection to the connection pool {0} is invalid. | Check the connection parameters. |
TIBCO-BW-PALETTE-SAP-501004
Getting Function for {0} is failure from Connection Pool, Error: {1} |
error | BW-Plugin-in | The error {1} occurs when failing to get the function by using the specified connection pool. | Check the connection pool. |
TIBCO-BW-PALETTE-SAP-501007
Cannot find transaction with SessionID: {0} to Continue. |
error | BW-Plugin-in | Finding the transaction with the session ID {0} fails. | Check the session ID. |
TIBCO-BW-PALETTE-SAP-501009
Request Response error. ErrorMessage : {0} |
error | BW-Plugin-in | The error {0} occurs when the RFC/BAPI request fails. | Check the configuration parameters. |
TIBCO-BW-PALETTE-SAP-501010
The transaction committed failure for RFC function : {0} errorMessage: {1} |
error | BW-Plugin-in | The error {1} occurs when the transaction of the function {0} fails to be committed. | Check the configuration parameters. |
TIBCO-BW-PALETTE-SAP-501011
RFCBAPI Listener error. Timeout waiting for reply, Function: {0}. |
error | BW-Plugin-in | The response of the function {0} times out. | Check the configuration parameters. |
TIBCO-BW-PALETTE-SAP-501013
Request Response error. errorMessage : {0} |
error | BW-Plugin-in | The error {0} occurs when failing to find the function in the SAP system. | Check the function configuration. |
TIBCO-BW-PALETTE-SAP-501014
RFC error encountered and AutoCommit would be skipped for RFC function : {0} error: {1} |
error | BW-Plugin-in | The error {1} occurs, and the function module {0} can skip the automatic commit. | Check whether the return TYPE is "S" or " " or "I" in the case of the associated TYPE starting with "BAPIRET" from EXPORT parameters and TABLE parameters in the SAP server. |
TIBCO-BW-PALETTE-SAP-501015
Transaction with SessionID: {0} timed out. |
error | BW-Plugin-in | The transaction with the session ID {0} times out. | Check the earlier error messages in the log file. |
TIBCO-BW-PALETTE-SAP-501016
{0} |
error | BW-Plugin-in | Reconnecting to the SAP system fails. | Check connection parameters and the network connectivity. |
TIBCO-BW-PALETTE-SAP-501017
There is an empty string or invalid character at the attribute of connection type. {0} |
error | BW-Plugin-in | An empty string or invalid character exists in the value of the connectionType input element. | Check the value of the connectionType input element. |