Hi Guys,
Good day!
I am currently having issues on sending IDOCs to BODS.
There are instances that an IDOC gets stuck or ends up with an error in transaction code SM58. In transaction WE02, the IDOC is
successfully processed with status 03. In a set of IDOCs (10 or more), one IDOC is in error in SM58, usually the first IDOC gets the error and the next IDOCs are successfully processed. The error received in SM58 displays the following:
Error 1: R3RfcClient(DI_CLIENT)ActaIDocFunc::Process()...
Error 2: CPIC-CALL ThSAPCMRCV no data received
However, the client interface is active/running.
In the management console, the error Logs-History displays the following:
(14.0) 04-08-14 23:32:51 (E) (8060:3868) Unknown: SP(INVOICE_001, ABC:1234)::flowThread() Flow became
invalid during waiting for request (BODI-300137)
(14.0) 04-08-14 23:32:51 (E) (8060:9356) Unknown: R3RfcClient(RFC_CLIENT_INTERFACE) ActaIDocFunc::Process()
encountered processing error for Requeste(15149) (Communication Error. See real time job log for details.) (IDOC 0000001234567890/ABCDE). (BODI-300129)
For the Real-Time Services log, the following is displayed:
(14.0) 04-08-14 23:32:39 (E) (70684:47620) RUN-051005: |Session REALTIME_INVOICE|Data flow DATAFLOW_INVOICE|Loader query_IDOC_DETAILS Execution of <Regular Load Operations> for target <IDOC_DETAILS> failed. Possible causes: (1) Error in the SQL syntax; (2) Database connection is broken; (3) Database related errors such as transaction log is full, etc.; (4) The user defined in the datastore has insufficient privileges to execute the SQL. If the error is for preload or postload operation, or if it is for regular load operation and load triggers are defined, check the SQL. Otherwise, for (3) and (4), contact your local DBA.
(14.0) 04-08-14 23:32:50 (E) (70684:68856) DBS-070401: |Session REALTIME_INVOICE|Data flow DATAFLOW_INVOICE|Loader query_IDOC_DETAILS ODBC data source <ABC\ABC,12345> error message for operation <SQLExecute>: <[Microsoft][SQL Server Native Client 10.0]TCP Provider: An existing connection was forcibly closed by the remote host. >.|<Regular Load Operations>|<IDOC_DETAILS>
Given this, I would like to ask on how to eliminate this issue.
Thanks,