Here's some text from a presentation I did:
TEXT CONVERSION LESSONS LEARNED
1. & (frequently used in place of ‘and’) in MO Text converted to &,  , which weren’t handled by UBE MO functions.
We reported this as an issue to Oracle and eventually obtained a fix. This was unknown until after go-live. Bug # 29313018, fix is in TR 9.2.3.3
2. We knew the Text Conversion program created double spacing and had communicated this to users. However once users saw printouts double and triple in size we had to come up with a solution – fast!.
3. 13% of Text Media Objects not converted by P98MOHTM. That’s 13% of 900,000 attachments.
Lesson Learned: If we had to do it all over again we probably wouldn’t use Oracle’s Text Conversion (P98MOHTM) at all.
How we Fixed Our MO Text
1. A SQL DB Function that converted the F00165 binary values to text
2. A SQL DB View that used the above function to provide a view of F00165 Text Media Objects
3. A SQL DB Stored Procedure that accepts Text and updates a specific F00165 entry with the binary equivalent.
4. A Crystal Report used as a ETL tool that
- Read the original F00165 text using the above view
- Presented the text as plain text but with correct vertical and horizontal spacing.
- Transformed the RTF line breaks \par + CHR(13) to \<br>
- Created a SQL Statement that executed the Stored Procedure above passing the Key Fields and the modified Plain text
- Pasted the output SQL file from Crystal into SSMS and executed it
Here's a sample SQL:
EXECUTE JDE_MO_TEXT_UPDATE 'GT4101', '108670', 1, N'THIS BOM INCLUDES A FILTER, 106748, THAT IS OBSOLETE.<br>THE OIL REGULATOR THAT THIS FILTER WAS ASSEMBLED INTO<br>NOW COMES WITH THIS FILTER AS PART OF THE REGULATOR<br>ASSEMBLY, 139616. 3-18-15 BSC<br>';