Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
NMED (Package) R/3MED: Medical documentation GSD
Basic Data
| Data Element | N2_FTOTEXT |
| Short Description | ConvertToText Function Module |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR30 | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 6 | ToText |
| Medium | 15 | ToText Function |
| Long | 31 | ConvertToText Function Module |
| Heading | 31 | ConvertToText Function Module |
Documentation
Definition
The function module ConvertToText (further abbreviated as ToText) is used for transferring data, which has previously either been determined or modified by the functions Query, Get, CheckValue, Save, HelpF4 or XCode, from the memory of the external data module to the calling dialog application. In the dialog application, the corresponding documentation elements are then predefined or modified using the data transferred.
The function module ToText is used for supplying unstructured documentation elements (including long text) and simple structures. The data format is then converted into text format. For this reason, when defining the documentation elements, the compatibility of the data category to the source of the external data must be verified, where an appropriate data element will be assigned or defined.
When supplying structures, the function module for each documentation element that is assigned to the structure will be called. Depending on the name of the documentation element or its ED Alias, the function module can make the relevant data available in each case. The number of documentation elements that the external data module can supply does not have to be identical to the number of documentation elements which the structures to be supplied will create. For the names or EDAlias of the documentation elements that are to be supplied, the appropriate names determined by the external data module have to be used.
When supplying long texts, all lines (rows) of a long text will be made available to the interface table line-by-line.
Interface parameter
- Importing
- VALUE(DOK_ID) LIKE N2REFHDR-REFDOK OPTIONAL (from interface vers. 1 on)
- VALUE(DOKELEMENTID) LIKE N2DE-DEID
- VALUE(REFKEY) LIKE N2REFHDR-REFKEY OPTIONAL (from interface vers. 1 on)
- Tables
- TEXTTAB STRUCTURE RN2TEXT
- Exceptions
- NODATA
- CONVERSIONERROR
TEXTTAB is the general interface through which data of all formats are transferred. This implies that in the next step, all data must be converted in the function module ToText into text format and will then be converted into the destination format by the generated application program. For this reason, the structure of the interface can generally be used independent of the data to be transferred and the external data modules. In the document definition, the compatibility of the source and destination format should be verified.
History
| Last changed by/on | SAP | 20050301 |
| SAP Release Created in |
