tecn

Solution
The solution is to use the RW_SOPLINECommentText user defined report writer function in the system series in a set of calculated fields.  I recommend making each line the maximum 80 characters and creating 8 lines.  This gives the potential for 640 characters and so should easily be able to display the 500 characters of comment text (even with not breaking words in half or additionalcarriage returns).
Why 8 lines?  This is so we can place two lines on each of the 4 additional footer sections.  If we update the suppression logic correctly, it will mean there will only be the possibility of one blank line between SOP line items. With only 4 section breaks, we can only print 0, 2, 4, 6 or 8 lines at a time, so if there are actually an odd number of lines to be printed, therewill be one blank line printed.  If there are an even number of lines, then there will be no blank line.
You might ask (as Mariano did): "Why not create 4 additional footers, so that each comment line can have its own section?". Well, the problem here is that there are no additional fields that can be used as a break field to add an additional footer. The Component Sequence and Break Field 1, BreakField 2, & Break Field 3 are all used for the 4 existing additional footers.
We will also create a similar 8 lines of 80 characters for the document level comments to demonstrate the use of the RW_SOPHDRCommentText report writer function.
The parameters for the RW_SOPLINECommentText report writer function are:
in integer IN_Type;        { SOP Type of Document }
in string  IN_Number;      { SOPNumber of Document }
in long    IN_LineItem;    { Line Item Sequence of Line }
in long    IN_Component;   { Component Sequence of Line }
in integer IN_characters;  { Number of Characters per Line }
in integer IN_line;        { Line Number to Return }
The parameters for the RW_SOPHDRCommentText report writer function are:
in integer IN_Type;        { SOP Type of Document }
in string IN_Number;      { SOP Number of Document }
in integer IN_characters;  { Number of Characters per Line }
in integer IN_line;        { Line Number to Return }
 
Implementation
The steps below assume some knowledge of report writer. If you need detailed step by step instructions please look at the How to document. 
 
PART A: Line Comments
1. Create 8 calculated fields of result type string for the8 Line level comment lines:
 
(c) Line Comments 1 = FUNCTION_SCRIPT(  RW_SOPLINECommentText  SOP_LINE_WORK.SOP Type  SOP_LINE_WORK.SOP Number  SOP_LINE WORK.Line Item Sequence  SOP_LINE_WORK.Component Sequence  80  1  )
 
(c) Line Comments 2 = FUNCTION_SCRIPT(  RW_SOPLINECommentText  SOP_LINE_WORK.SOP Type  SOP_LINE_WORK.SOP Number  SOP_LINE WORK.Line Item Sequence  SOP_LINE_WORK.ComponentSequence  80  2  )
 
(c) Line Comments 3 = FUNCTION_SCRIPT(  RW_SOPLINECommentText  SOP_LINE_WORK.SOP Type  SOP_LINE_WORK.SOP Number  SOP_LINE WORK.Line Item Sequence  SOP_LINE_WORK.Component Sequence  80  3  )
 
(c) Line Comments 4 = FUNCTION_SCRIPT(  RW_SOPLINECommentText  SOP_LINE_WORK.SOP Type  SOP_LINE_WORK.SOP Number  SOP_LINE WORK.Line Item Sequence  SOP_LINE_WORK.Component Sequence 80  4  )
 
(c) Line Comments 5 = FUNCTION_SCRIPT(  RW_SOPLINECommentText  SOP_LINE_WORK.SOP Type  SOP_LINE_WORK.SOP Number  SOP_LINE WORK.Line Item Sequence  SOP_LINE_WORK.Component Sequence  80  5  )
 
(c) Line Comments 6 = FUNCTION_SCRIPT(  RW_SOPLINECommentText  SOP_LINE_WORK.SOP Type  SOP_LINE_WORK.SOP Number  SOP_LINE WORK.Line Item Sequence  SOP_LINE_WORK.Component Sequence  80  6  )
 
(c)Line Comments 7 = FUNCTION_SCRIPT(  RW_SOPLINECommentText  SOP_LINE_WORK.SOP Type  SOP_LINE_WORK.SOP Number  SOP_LINE WORK.Line Item Sequence  SOP_LINE_WORK.Component Sequence  80  7  )
 
(c) Line Comments 8 = FUNCTION_SCRIPT(  RW_SOPLINECommentText  SOP_LINE_WORK.SOP Type  SOP_LINE_WORK.SOP Number  SOP_LINE WORK.Line Item Sequence  SOP_LINE_WORK.Component Sequence  80  8  )
 
Note: The only...