Content Table 

In the table CONTENT (the binary table), document contents are transferred directly. Transfer is via an internal table. The relevant field is LINE :

If a caller transfers the content of a document in the binary table and at the same time defines that the mime type is text/Subtyp , the document is handled as a text document, that is, it is converted into the current R/3 code page and stored as text.

Several components of various documents can be transferred in a content table: A new row is started for each component. The size of the individual components (table COMPONENTS) indicates the beginning and end (row x) in the content table.

In the table ASCII_CONTENT (the ASCII table), document contents are transferred directly. Transfer is via an internal table. The relevant field is LINE :

Several components of various documents can be transferred in a content table. A new row is started for each component. The size of the individual components (table COMPONENTS ) indicates the beginning and end (row x) in the content table.

In the Content table, one text line is transferred per table line. Line breaks are recognized implicitly by the character ¹ Space after the last character, that is, there are no explicit line breaks. Continuous text can be defined for applications with very long text lines. This can be implemented using the statement text_as_stream = 'X' : Carriage Return and Line Feed are in the text implicitly. Therefore, line breaks can be specified explicitly.