snehareddy
IS-IT--Management
Hello,
On Mercator we receive IDocs from SAP R/3 system(R/3 Release 4.6C) using outbound ALE adopter.
The Mercator Version we are using: 6.7(306_1EM) on HP-UX plotform.
We are facing problem with the RFC Destination to Mercator ports, where it is failing to send IDcos to Mercator and many iDocs are getting stuck up.
And if once we restart all the Event Servers on Mercator the RFC Destination is resuming with its functionality and we are receiving all the IDocs at once and getting processed.
Is this problem because of - ALE IDocs are communicated through memory buffers, without intermediate
files, directly to or from an RFC port using transactional remote function calls (RFCs)?.
Another important issues is:
We observed the DATA LOSS , some of the idocs were not reached to Mercator which were created at SAP and sent successfully.
During this problem we observed that The RFC Destination was up and running and able to ping the RFC Destination from SM58.
We process the high volumes of data.
Please let us know the possible causes and remedy for the above problem.
Thanks in Advance!!
On Mercator we receive IDocs from SAP R/3 system(R/3 Release 4.6C) using outbound ALE adopter.
The Mercator Version we are using: 6.7(306_1EM) on HP-UX plotform.
We are facing problem with the RFC Destination to Mercator ports, where it is failing to send IDcos to Mercator and many iDocs are getting stuck up.
And if once we restart all the Event Servers on Mercator the RFC Destination is resuming with its functionality and we are receiving all the IDocs at once and getting processed.
Is this problem because of - ALE IDocs are communicated through memory buffers, without intermediate
files, directly to or from an RFC port using transactional remote function calls (RFCs)?.
Another important issues is:
We observed the DATA LOSS , some of the idocs were not reached to Mercator which were created at SAP and sent successfully.
During this problem we observed that The RFC Destination was up and running and able to ping the RFC Destination from SM58.
We process the high volumes of data.
Please let us know the possible causes and remedy for the above problem.
Thanks in Advance!!
