Example: Material Sales Texts 

You want to migrate material sales texts from a legacy system to the SAP system.

 

Structures and Fields in the SAP System for the Migration Object Class 00

LTXTH: Long text header

STYPE	Record type (technical field)
OBJECT	Application object
NAME	Text name
ID	Text ID
SPRAS	Language

LTXTL: Long text line

STYPE	Record type (technical field)
TEXTFORMAT	Format field (2 characters)
TEXTLINE	Application object

 

Source structures and fields

Since the SAP system expects a two-level hierarchy, there have to be two hierarchy levels in the project as well.

MVTX1: Material sales text header

Material number    C (018)

Language       C (002)

MVTX2: Material sales text line

Text line         C (050) 

 

Structure relationships between the legacy system and the SAP system

LTXTH <<<< MVTX1

LTXTL <<<<  MVTX2

 

Field relationships and field assignments

Field relationships and field assignments are created in the same way as done with the remaining migration objects as well. However, note that the material number (length 18), sales organization (length 04), and distribution channel (length 02) are included in the SAP field NAME. This means, the field relationship and field assignments for the NAME field might look like this:

 

 

When you use a rule other than MOVE (for example, translation) to convert the key for migration of the application object, you also have to use this conversion for generation of the NAME field. Failure to do this causes the link between application and text object to be lost.

The text is handled as continuous text if you do not specify a value for the Text Format field. If you want the lines to be wrapped, branch to the editor and enter the following code:

 LTXTL text format = '*'. (<quotation mark><asterisk><quotation mark><period>).

 

Example of input data stored in a Microsoft Excel table