on 06-03-2016 4:41 PM
Hi Experts,
We are in SAP PI 7.4 version.
We are sending the IDOC from ECC system to SAP PI.
IDOC’s are getting stuck in SM58, below is the error in SM58.
Failed to resolve repository reference-@XI_IDOC_DEFAULT_DEST_XXX
They are getting resent automatically after sometime(20-30min)
I have checked all the blogs and all the required setting but still not able to find the answer.
Any help or suggestion is appreciated.
Thanks,
Riz
Hi Navdeep,
I have already checked destination config for LCRSAPRFC, no RFC details maintained.
@ Apu -
The information which you gave is from the SAP NOTE 1840707, this is taken care.
Still we are facing the same issue, luckily second time the IDOCs are getting posted.
But need to find out why these IDOCs are not posted in first attempt.
Please share your finding and suggestion.
Thanks,
Rizwan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kavita,
We are collecting the IDOCs and then an report is used to post the IDOCs to SAP PI.
Not all idocs makes to SAP PI , few of the IDOCs stuck up in SM58 and after few minutes the reaming get posted.
Wanted to know why all the IDOCs are not making to SAP PI in first attempt.
Thanks,
Rizwan
Hi,
If you are using single stack version of 7.4 and using IDOC_AAE then you try these once -
1. Remove the destination entry from NWA -> SOA ->JCo RFC Provider
2. Restart IDOC service .
Thanks,
Apu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I checked and we are in the latest patch.
Was looking into for more traces
[JRA] ReaderManaged_Application_Thread_57, onConfirmTID(), no Bean found for TID
This is the error which I got in the trace.
As per SAP there is a note 1840707 to resolve. Even I checked the details present in the Note all the config are present as per the note.
Still end up with the same issue.
Thanks,
Rizwan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nazeer,
I was rechecking the configuartion again.
Can you please elaborate more for this point.
What we need to maintain in this.
Thanks,
Rizwan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
multipleRespository parameter should have all the SAP system ID and Corresponding destinations like AI1=AI1CLT001, BC1=BC1CLT010;....
check, if this is correct and same in multipleRespository and CustomDestMap.
if this is all good. check if your IDOC java adapter is on latest patch.
we had exactly same issues when the new stem was installed, but got resolved later after latest patch and sp upgrade. Now things are stable.
Hi Nazeer,
Thanks for this information.
In my case all the setting are saved and noting changes by itself.
Yes- All the necessary configuration are maintained correctly and I crossed checked the details you mentioned.
If anything was missing or not config correctly , I think the IDOCs could have not made in second attempt as well.
Thanks,
Rizwan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rizwan,
we used to have similar issues with IDOC adapter. when the system was newly built. After multiple patch updates this got normalized. It was not recurring.
In my case, the configuration used to get removed without anyone changing it or not getting saved sometimes.
check these setting and make sure, they are all set
1. NWA>Confugurations>Infrastructure>Application resources>inboundRA(Resource Adapter)
a. check what default destination is configured. XI_IDOC_DEFAULT_DESTINATION_XXX . Is working correctly in Destinations.
b. check, if multiRepository setting is correct and not changed
2. NWA>Confugurations>Infrastructure>Application resources>JavaIdocAdapter (Resource Adapter) - check CustomDestMap Class java.lang.String in Properties tab
regards,
Nazeer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All,
Thanks for this Link and suggestion I have already seen all this.
All the setting are in place and correctly maintained.
If any config was missing , the IDOCs will never make to SAP PI system.
In may case the IDOCs are posting to PI system after some time.
They are getting resent automatically after sometime(20-30min)
Wanted to check why there are not posted in the first attempt.
Thanks,
Rizwan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rizwan,
In this case, please select the Adapter as "Integration Server" in PI system. This will help you.
Regards,
Souvik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Rizwan,
Check in PI ID whether the ECC business system has correct adapter specific attributes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.