Robert Robinson
Reputable Poster
Thanks for this forum Eric. Having a conduit (XML) instead of a stop sign (pdf) opens up a world of possibilities for JD Edwards data, especially since the Microsoft Office line uses XML to store and share document data.
Don't know if everyone has seen this...normally, JDE instances have to be on E1 8.12/Tools 8.97 to use the "Phase 2" functionality of XML (BI) Publisher. We have since found baseline ESU JJ15756 that will allow companies on 8.11 SP1 and 8.97 to use XML without having to make the 8.12 Application Release migration. We will take a bite of this apple soon.
Questions? I got a million of 'em...but will stay in my shoes for now, and ask just a few:
Is there anyone who has taken the XML plunge who would mot mind sharing their experiences? How did the UBE output change? If you migrated to XML from the pdf output, were you able to leverage your existing custom UBEs and retrofit to XML use (could still use all UBEs, right?)
Don't know if everyone has seen this...normally, JDE instances have to be on E1 8.12/Tools 8.97 to use the "Phase 2" functionality of XML (BI) Publisher. We have since found baseline ESU JJ15756 that will allow companies on 8.11 SP1 and 8.97 to use XML without having to make the 8.12 Application Release migration. We will take a bite of this apple soon.
Questions? I got a million of 'em...but will stay in my shoes for now, and ask just a few:
Is there anyone who has taken the XML plunge who would mot mind sharing their experiences? How did the UBE output change? If you migrated to XML from the pdf output, were you able to leverage your existing custom UBEs and retrofit to XML use (could still use all UBEs, right?)