Outbound Program using ALE/IDOC

[Former Member]

Dear All,

We are trying to send data from SAP custom table to TIBCO (Middleware) using outbound Idoc..

Can anyone tell me the procedural steps i need to follow for this development.

Note: I know how to send data from SAP-SAP using outbound Idoc. Please let me know if i can adopt the same procedure for sending the data from SAP to TIBCO also orelse, is there any change in the procedure..pls advice..

[Former Member]

Nope...

I dont think there is some other way.

Only thing you got to have the details of the server, login id and password to connect.

First, I would recommend you to check SM59 connection between your system and the middlware system by giving the necessary log on credentials.If you are successfull, go ahead and perform the steps to send the data.

Hope this is helpful..

[Former Member]

Hi,

All the configuration will be same as sap to sap except Rfc connection and port creation.

Thanks,

Asit Purbey.

[Former Member]

Hi,

All the steps would be the same, except for specifying the connection type between the two systems.

Thanks

Krithika

[Former Member]

Ram, Do we have any existing Interfaces to TIBCO or its entirely new application.

If you already have Interfaces the life will be easy as you just need to pick up the RFC which is pointing to TIBCO system otherwise as already suggested in thread you need to have (Basis team?) to create New RFC with corresponding Connection Type.

Once this is done you can do other ALE config to send and receiver the Table data.

Let us know how it progresses.

Regards

Shital

[Former Member]

Hi,

I have made all the configurations, but while processing the IDOC, it was throwing the error like "No partner profile (outbound parameter) could be found using the

following key " and message no 29.

Pls suggest what is the error message indicates.

[abdul_hakim]

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.

Regards,

Hakim

Edited by: Abdul Hakim on Mar 18, 2009 6:33 AM

[Former Member]

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

Do you face the problem.

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 Paramters and add the message type.

Finally, you got to create the Distribution model to achieve connection fine.

I encountered similar problem earlier and resolved it by doing the same.

Please re check your connections.

[Former Member]

Hi,

Thank you very much to all..iam able to generate the IDOCs now but with warning for some of the IDOCs generated..

Warning message is: "Receiver exists , No filters , No conversion , No version change".

Please suggest what it says..

[Former Member]

It says that the Idoc is in Middleware.

Hope the status of the Idoc is 03

Check the target system now

[Former Member]

Hi Babu Kilari,

Actually my custom table have 59 records, so iam sending 59 Idocs. Among 59 , 57 Idocs status is 30 and for the rest of the IDOCs status is 3. Pls guide me..

[Former Member]

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 status will change to 03.

Hope the explanation is clear.

[Former Member]

Adding to the above,

Have you used the Commit work statement after your function module.

Check that as well.

My suggestion is to use the following piece of code after the MASTER_IDOC_DISTRIBUTE Function module.

IF sy-subrc = 0.

CALL FUNCTION 'DEQUEUE_ALL'.

COMMIT WORK.

ENDIF.

Hope everything is successfull now.

[Former Member]

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

after MASTER_IDOC_DISTRIBUTE

Call FM "EDI_DOCUMENT_DEQUEUE_LATER"

and pass the Communication IDOC number to it.

Hope this helpful

surya

[Former Member]

My problem is resolved..thanks alot to all who had given valuable suggestions in developing this Custom outbound IDOC..