on 08-25-2011 4:26 PM
Dear All,
I created a scenario like... ECC to JDBC and in return I will get 2 fields to ECC via PI.
I am able to get the response from JDBC to PI, but unable to send it to ECC.
I developed ESR and ID objects as below...
1 Data type and 1 Msg type for ECC
1 Data type and 1 Msg type for JDBC
1 Service Interface for outbound
1 service interface for Inbound
1 Msg Mapping from Ecc -> JDBC(request)
1 Msg Mapping from JDBC -> ECC(response)
1 Operation Mapping - for ECC->JDBC Mapping in request Tab and
JDBC->ECC Mappinf in Response Tab.
In ID I created scenario as ECC in sender Communication Channel and JDBC in Receiver Commnication channel and other objects.
Any one help me if any changes are there in above developed objects.
Reagrds,
Hari
hi
when you say you are am able to get the response from JDBC to PI, is that mean you see any error in MONI due to whcih you
are not able to see the messages in ECC?
check your configuration , also in case your not seeing any entry in SXMB_MONI , would like to know if you have turned on the synch message loggin in SXMB_ADM
best regards
srinivas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hari,
How are you sending response back to ECC,using Proxy or RFC(BAPI)?
below design you have to implement
ECC(ABAP Proxy)->PI>JDBC Sync mode
ECC(BAPI)>PI->JDBC Sync mode.
Regards,
Raj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Hari,
Couple of questions:
1) Are you using the same message type for both request and response in the Service Interface?
2) What is the exact error that you are getting? Is it in sxmb_moni?
3) Is your proxy code capable of handling synchronous requests?
This will help in analysing the issue.
Regards,
Sanjeev.
User | Count |
---|---|
76 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.