cancel
Showing results for 
Search instead for 
Did you mean: 

Error in resource resolution or Initialization: SOAP to RFC scenario error in SAP PI

former_member585940
Participant
0 Kudos

Hi Experts,

We have one SOAP to RFC synchronous scenario. RFC has two tables along with export parameters.

Initially we updated export parameters and one table and it worked fine.

Now I am trying to update other table as well but getting the below error in moni.

This error is coming while calling adapter. If i change the mapping back to update only one table, It will work fine.

Can you please share your inputs here.

Thanks,

Vikram

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member585940
Participant
0 Kudos

Hi,

Thanks for your inputs.

IT is solved now.

This issue occurred because we did not handle exception coming from RFC. Now it works fine.

Thanks,

Vikram

bhakti2
Active Participant
0 Kudos

Hi Varinder, I am getting the same error. Could yu pls help me resolve by giving more details about your solution ? mine is synchronous RFC. Its still not run succesfully anytime. I could see that its reaching the destination Rfc. how do i get the return message?

Coding for calling the PI scenario

try.
create object l_o_proxy.
l_o_proxy->si_create_sa_outbnd(
exporting
output = lt_crt_sa_input
importing
input = lt_crt_sa_output
).
endtry.

loop at lt_crt_sa_output-return-item assigning field-symbol(<fs_return1>).
append initial line to lt_bapimeret2 assigning field-symbol(<fs_return2>).
move-corresponding <fs_Return1> to <fs_return2>.
endloop.

This is screenshot of OM Synchronous Response section

Error details from SXMB_MONI

<SAP:ProcessingMode>synchronous</SAP:ProcessingMode> <SAP:MessageId>BC985A69-32D5-11EB-A579-0000003A5886</SAP:MessageId> <SAP:RefToMessageId>F9635151-022D-1EEB-8CDA-B78AA3AE5071</SAP:RefToMessageId> <SAP:TimeSent>2020-11-30T06:31:53Z</SAP:TimeSent> -<SAP:Sender> <SAP:Service>BS_DA0_300</SAP:Service> <SAP:Interface namespace="http://xxxxx.com/xi/SRM/Contract">SI_Create_SA</SAP:Interface> </SAP:Sender> -<SAP:Receiver> <SAP:Party scheme="XIParty" agency="http://sap.com/xi/XI"/> <SAP:Service>BS_DP1_300</SAP:Service> <SAP:Interface namespace="http://xxxx.com/xi/SRM/Contract">SI_Create_SA_Outbnd</SAP:Interface> </SAP:Receiver> <SAP:Interface namespace="http://xxxx.com/xi/SRM/Contract">SI_Create_SA</SAP:Interface> </SAP:Main> -<SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"> <SAP:QualityOfService>BestEffort</SAP:QualityOfService> </SAP:ReliableMessaging> -<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"> <SAP:Category>XIServer</SAP:Category> <SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code> <SAP:P1>Object ID A936AD588440322A976A5054F762DE41 Software Component 2B2CA5308D5A11E9B924D52CA04505CA</SAP:P1> <SAP:P2/> <SAP:P3/> <SAP:P4/> <SAP:AdditionalText/> <SAP:Stack>Mapping program is not available in runtime cache: Object ID A936AD588440322A976A5054F762DE41 Software Component 2B2CA5308D5A11E9B924D52CA04505CA </SAP:Stack> <SAP:Retry>M</SAP:Retry> </SAP:Error> -<SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"> -<SAP:Hop wasRead="false" timeStamp="2020-11-30T06:31:53Z"> <SAP:Engine type="AE">af.dpi.itdt35ib</SAP:Engine> <SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter> <SAP:MessageId>BC985A69-32D5-11EB-A579-0000003A5886</SAP:MessageId> <SAP:Info/> </SAP:Hop>

Former Member
0 Kudos

Have you tried a cache refresh already?

former_member585940
Participant
0 Kudos

Hi,

I tried it but no luck

Thanks

Former Member
0 Kudos

I had a problem like this recently, and the cache refresh did not work either. Then, i tried to edit the object (in the ESR) and activate it again. It worked for me!

former_member184720
Active Contributor
0 Kudos

go to your interface determination and under the "software component version of the sender interface", leave it blank, instead of a numerical ID.