Configuring Special Features of Text Control

If the text of a text type can be copied, that is, if an access sequence is assigned to the text type in the text determination procedure, you can define for the text type in the text determination procedure whether the copied text is copied (duplicated) or referenced from the source object.

The following screenshot shows the option to reference or duplicate texts.

Duplicating a text has the following consequences:

The transferred (duplicated) text is stored in the database at its own data record. Source text and transferred text are completely independent of each other. You can change both the copied (duplicated) text and the text in the source object without any interaction. Duplicating texts requires more memory space than referencing texts from a source object. Therefore, you should only decide to duplicate if it is functionally required.

Transfer a text as a reference has the following consequences:

The text exists only once in the database, that is, if you change the text in the source object, the transferred text also changes. It's the same! You can also change the copied text in the document. However, if you change the transferred text, the text is automatically duplicated. Afterward, changes to the text in the source object no longer affect the transferred text.

The Text is mandatory or should be displayed field controls the following two behavior for the text type:

1. One, whether a text that is transferred to this text type is displayed during the transfer or not. If the text is displayed during copying, a dialog box appears in sales document processing on the overview screen in which the text of the text type is displayed. If required, the text can also be edited here.

2. Second, whether text for this text type is mandatory in the sense of the incompleteness check or not. If a text type is controlled as mandatory and no text is transferred for this text type or entered during document processing, the document is incomplete in the sense of the incompleteness check. The hard-coded error incompleteness procedures 50 and 51 can only be processed using the view maintenance V_TVUVF using transaction SM31. For details, see SAP Note 385982 Incompleteness of texts Customizing.

If you want to create data transfer routines for texts, use the transaction VOFM Maintain: Requirements & Forms.

In the data transfer routine, requirements for the transfer of texts can be formulated in ABAP. These data transfer routines can then be assigned in an access sequence to an access. This access then procures the text with the programmed logic. The name space for customer-specific routines is between 50 and 99 (two-character key). You can find the descriptions of the available data structures in the delivered sample routines with the numbers 1 Exit sample and 2 Exit Sample 2.

The figure shows an example of a data transfer routine for texts.

The example of the figure is as follows: The data transfer routine 91 determines the text from the text object TEXT (standard texts) from the text ID SDVD from the (standard) text with the name ZMAT:*. * is always replaced with the current material number of the respective document item (ABAP statement: refer-tdname+5=FTVOM-MATNR.). For example, if material P650-100 is sold in an item, the system searches for a (standard) text with the name ZMAT:P650-100. The prerequisite is an access sequence with an access to the object TEXT and the TEXT ID SDVD. The data transfer routine must be defined in this access. In addition, suitable standard texts (text name ZMAT:*) are required. The standard texts are maintained using transaction SO10 Standard Text: Request.