YieldConfirmationRequest work flow results in the message [STEP = STD_SERVICE]. org.xml.sax.SAXParseException: Premature end of file. What could be the posssible reasons?
Let me give some context to this. I should have done this earlier, sorry! We had a working installation of ME that was linked to an ECC EHP5 box. The ECC box was recently upgraded to EHP6. This issue popped up since the upgrade. Would you advise differently?
Also, since the ME/MII configuration has been untouched, I would think the 1st and 2nd cases noted by you would not be applicable. Would it?
As far as the ERP credentials go, the installation wizard created all the required credentials during the original install. Is there any specific credential that would need change? Or should the installer be run again?
Stepping aside from this specific query, if one were to upgrade the connected ECC box, leaving everything else untouched, what's the best way to go about it?
There has been no ME certification for ERP 6.06 yet, though some guys at Development used this version with ME 6.1 or 6.2 without problems. Of cause, no one tried your scenario with upgrading ERP part. So, we do not have official recommendations on this case,
So, here could be some general suggestions only:
- re-run SAPMEINTCTC;
- check other types of confirmations;
- check inbound requests;
- make sure you test base version of confirmations, without any customizations;
- check logs on ERP side;
- turn on all available debugging for SAPMEINT component and check the detailed log for any clue on the root cause;
- check settings of SAPMEINT_ALE (which is used to call to ERP) in Credentail Store of MII;
- and the last option is to re-execute the full configuration of integration once again from scratch, just if something in config was dropped by ERP upgrade.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.