Sending IDoc from TIBCO to SAP

[achim_pellen]

Hi,

request is to send IDoc type PURCONTRACT_CREATE01 from TIBCO to SAP.

After sending the data from Tibco there is nothing received in SAP although TIBCO adapter says successfully created.

But no entry in BD87 (IDoc monitor), no entry in SM48 (tRFC queue) on SAP side.

How can I recognize what went wrong - on TIBCO or SAP side?

Shouldn't there be an entry in IDoc monitor at least although content of sender or receiver data or IDoc would be wrong that was sent by TIBCO?

Has the TIBCO adapter to do a kind of commit ?

Help is highly appreciated.

thx.

Achim

[Former Member]

Hi,

Configure the appropriate message type for the partner in the outbound parameter of the partner profile (WE20) . Afterwards reprocess your failed idoc using the program RBDAGAIN

Try Posting the Idoc with the help of WE19 instead of using your report

Status 29 indicates that the Partner Profile is not configured correctly.

As you know the target logical system is nothing but the partner, select that and click on Outbound Parameters and add the message type.

Status 30 indicates that the Idoc has been generated successfully.

Status 03 indicates that the Idoc has been reached Middleware.

Try running the standard program RSEOUT00.

All the Idocs in 30 statuses will change to 03.

To get all the IDOC's in status '03'

after MASTER_IDOC_DISTRIBUTE

Call FM "EDI_DOCUMENT_DEQUEUE_LATER"

Regards,

Shamma

[achim_pellen]

Hi Shamma,

as I wrote nothing is received in SAP when TIBCO is sending the IDoc. I can see nothing in the IDoc monitor.

I am asking myself how can I 100% proof where the fault is (on SAP or TIBCO side).

The partner profile should be correct as testing WE19 this is found correctly.

Thx.

Achim

[Sandra_Rossi]

trace all RFC calls a few seconds during the TIBCO call if you can (ST05)

[achim_pellen]

Hi Sandra,

I already checked ST05 but there is no entry regarding the function module IDOC_INBOUND_ASYNCHRONOUS that should be executed by TIBCO.

Any other clue?

Thx a lot

Achim

[Sandra_Rossi]

I didn't mean to look at one function module especially, but all RFCs. If you don't detect RFC activity, it means that the error comes from TIBCO (more or less). Moreover, check user and password used by TIBCO, maybe they are obsolete or user is locked.

[achim_pellen]

Hi Sandra,

At the end th problem seems to be at TIBCO side.

All traces by SAP (Authorization, RFC,...) where showing nothing at all.

The only thing that could be traced was testing the connection by TIBCO. But sending the IDOC couldn't.

There seems to be a problem regarding TIBCO version (5.6) and SAP ERP 6.00. Please be aware!!

Thx.

Achim

[Sandra_Rossi]

Fine. Keep us informed here when you have the final answer

[Former Member]

Hi,

You can monitor the IDOC flow in the WE05 or WE02 transactions.

Give the message type and the date range to track whether TIBCO system has sent you the IDOC's or not.

If you don't find the IDOC's there, then you can tell the TIBCO team that you haven't received the IDOC's into SAP system at all.

I hope I have answered your question.

Thanks,

Mahesh.