cancel
Showing results for 
Search instead for 
Did you mean: 

JDBC Sender to Asynchronous Scenario

Former Member
0 Kudos

Hello.

I´m implementing a JBDC Sender to a RFC Asynchronous. The import parameter of the RFC is an optional table.

In TA: SXMB_MONI the payload of my inbound message is:

And i´m not getting any value in my sap system.

Thanks in advance.

Accepted Solutions (1)

Accepted Solutions (1)

former_member206760
Active Contributor
0 Kudos

there is some problem in your mapping..

chk it properly using the test tab in the mapping

Answers (6)

Answers (6)

Former Member
0 Kudos

i solve the issue.

Thanks for your help. It was very useful and instructive.

The reasons for the error were:

1. I´m not using a service without party and the communication channel wasn´t OK

2. I forgot to map fields without JDBC correspondence to a blank constants.

Former Member
0 Kudos

I solve that.

First the communication channel was in error because i´m not using service without party.

Second the mapping was in error because i forgot map fields to blank constants.

Thanks

Former Member
0 Kudos

It´s seems to failed the RFC Channel Communication:

A resume of the error message in RWB is the following.

Error can not instantiate RfcPool caused by:

com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed

former_member208856
Active Contributor
0 Kudos

Check setting steps given in my earlier reply.

1. Check the RFC Destination used in CC

& Check that in SM59, it should work correctly.

former_member206760
Active Contributor
0 Kudos

Chk if the user id used in the RFC destination in SM59 is not locked...

Former Member
0 Kudos

I test the message mapping and the interface mapping in the Integration Repository and the result for both is OK.

And i have the message mapping correctly defined in Interface Determination.

Any other ideas please?

Thanks in advance!.

former_member208856
Active Contributor
0 Kudos

have you checked RFC Communication Channel configuration ?

And RFC Destination used in CC, working in SM59 ?

former_member200962
Active Contributor
0 Kudos

can you list down the steps followed (by you) while designing this interface?

May be you have included all the required objects properly, but the cache might have not updated properly....check for any Activation error in IR and ID.....also confirm that your objects are present in SXI_CACHE.

If nothing works then try re-creating the objects....is there any validation being done in the mapping (some if-else logic applied)?

former_member200962
Active Contributor
0 Kudos

Have you defined any mapping for your scenario...if, yes then you should test the mapping with this payload in Integration repository and confirm that it is working fine....if you have not defined any mapping then you are bound to get an empty payload.

Also the mapping should be included in the Interface Determination.

Regards,

Abhishek.

former_member208856
Active Contributor
0 Kudos

check problem in RWB > Component Monitoring> Adapter --> Communication Channe Monitoring

Also check your RFC destination from PI to ECC, ABAP Type. It is working or not.