Text Replacement Tool 
Use
You can use the Text Replacement Tool to modify industry-specific short texts in an SAP system to suit your particular industry’s requirements, allowing you to work with the terminology that is familiar to you in your industry. The Text Replacement Tool allows you to search for industry-specific texts and convert them for a particular industry.
Prerequisites
...
1. Authorization:
You need authorization S_BRAN_ADM to call up transaction CRMST62. This authorization is contained in the authorization profile of the same name.
2. Worklist Distribution:
To distribute worklists to their processors, the name of the converter must be entered in table (BRAN1). Worklists are distributed according to packages.
3. Data Backup:
You should open a separate directory for data backup. Enter the complete path names of the files in table TSKTF.
Features
The text pool is a table (BRATEXT) that contains the following information for each text:
· Language key
· Industry sector key
· Table name
· Field name
· Table key
· Original short text (standard SAP text)
· Industry-specific short text (the text you wish to use for your industry)
You enter the terms you want to replace and define the corresponding terms that you want to replace them with. The system then determines the packages relevant for the conversion. These definitions are used to locate the relevant texts. You must confirm the texts the system has determined. You must specify new texts for the conversion. The texts must be converted interactively.
To carry out these tasks, the following functions are required:
· Specification of character strings for locating industry-specific terms.
· Construction of a proposal pool for all converted texts.
The process distinguishes between character strings, determinations, target terms, proposals and short texts.
Character strings are the start of the process. As an example, you want to replace the SAP term “Material” with the industry-specific term “Article”. To do this, all composite phrases containing the term “Material” should be converted, for example, “Material Master” to “Article Master”. The system therefore needs to search the system for all possible composite phrases. To do this, enter “Material” or “Mat”, and all other terms that you want to convert. Enter these as character strings and then start the search for all short texts.
The result of the search is a list of words and composite phrases to be processed. At this point, you determine which of the words found should be accepted and which should not be accepted (for example, “Raw Material” should not be replaced with “Raw Article”).
Once you have defined all your source terms, you have to define all the corresponding target terms. This definition can be restricted to generic development classes, but this is not mandatory. For example, you can replace “Material” only in development class M*, or you can set more detailed filters so the term is only replaced in development classes MA*, MAB*, or MABC. Theoretically, you can define as many different target terms as you want for the same source term in as many different generic development classes as you want. The development classes *, M*, MA*, MAB*, and MABC are different from one another, but form a hierarchy. For a short text from a particular development class, the lowest target term in the hierarchy in used. In the above example, the system would first search for a target term for MABC for a short text from development class MABC. If no term was defined here, the system searches for MAB*, then for MA*, M* and finally for *.
Once all target terms have been defined, the system can construct a worklist for the proposal pool. A further search is started to find all short texts that contain the target texts.
The worklist can now be processed. The short texts are converted into industry-specific “dialect” in the same way as normal texts are translated into other languages. Conversion takes place per line and a proposal exists for each line to be converted. The proposals are created by automatically exchanging the individual terms in the short text lines.
Conversion takes place using a special editor. After conversion, the text has status “processed”. If it is not possible to convert a particular text immediately as its meaning is not clear, this text has status “reset” and can be processed again at a later stage.
The editor carries out a check for each text to be converted. It only accepts texts that actually contain the target terms defined by the user.
The worklist has to be rerun at fixed intervals to include texts that have come into the system during the current conversion phase. In some cases, texts that have already been converted have to be updated as the corresponding target terms have been redefined.
Before a new worklist is run, the system checks the proposal pool. It checks whether each source text in the proposal pool also contains a defined target term and whether the converted text contains this target term. If this is not the case, the proposals are deleted from the proposal pool. When the new worklist is run, only current texts with current target terms are entered into the proposal pool.
Once the worklist has been completed, the converted texts can be distributed to the text pool. The text pool contains all short texts to be converted, for each table and table key, in the original version and in the industry-specific version. During distribution to the text pool, the converted texts from the proposal pool are assigned to their tables.
This completes the process of text conversion.
Activities
You call up all functions by using transaction CRMST62.
1. Define character strings.
You can access the relevant editor via Goto à Character Strings.
i. Call up transaction CRMST62.
ii. Choose Goto/Character Strings
iii. Enter a character string to be searched for for each line (at least three characters)
iv. If you want to exclude certain character strings, flag the string with No.
v. Save the defined terms (F11).
vi. Once you have defined all the character strings, start the search: Utilities --> Search Character Strings
2. Step: Determine terms
You can determine terms after the search for character strings has finished. You can access the relevant editor via Goto à Define Terms.
vii. Call up transaction CRMST62.
viii. Use the selection New Entries.
ix. Choose Goto/Determine Terms.
x. If you want to assign a target term, flag the entry with Yes, if not, flag the entry with No. Terms that retain the flag New are reset later when you save.
xi. Save all defined terms (F11).
xii. Once you have determined all terms, use Utilities/Terms to accept the terms flagged with Yes for the definition of corresponding target terms.
3. Step: Define Terms
Once you have accepted all determined terms for definition, you can then define these terms. You can access the relevant editor via Goto à Define Terms.
xiii. Call up transaction CRMST62.
xiv. Use the selection New Entries.
xv. Enter a target term for each source term.
xvi. Save your definitions (F11).
4. Step: Convert Texts
xvii. Call up transaction CRMST62.
xviii. Use the selection New Entries.
xix. Maximize your processing window to full screen.
xx. Check the conversions proposed by the system.
xxi. Save your converted texts.
5. Step: Construct Textpool
Once you have converted all texts, you can construct the textpool.
xxii. Call up transaction CRMST62.
xxiii. Choose Utilities/Distribute Short Texts.
6. Step: Activate / Deactivate Short Text
xxiv. Call up transaction CRMSE62.
xxv. Choose Activate Industry or Deactivate Industry
xxvi. Select the required industry and start activation/deactivation by choosing Execute.
Description of individual functions:
Selections:
Industry Sector Selection:
Choose language and industry sector.
Selection takes place according to entries in tables BRANT and T002T.
Text Selection:
Here you can choose specific texts for processing. For a generic selection, choose *.
Default is space (all).
Short Test:
e.g. *mat*: all texts containing the string “mat”. The search considers upper/lower case spelling.
Development Class:
e.g. M* : Texts from all development classes beginning with M.
Field Length Area:
e.g. from 20 to 30: Texts that have field lengths between 20 and 30 characters.
Qualitative Selection:
New Entries:
This selection is used for determinations, target terms and proposals. You can use it to process the text entries determined automatically.
Already Processed Entries:
This selection allows you to reprocess texts that have already been successfully converted.
Direct Entries:
This selection is only used for target terms. You access an editor in which you can enter target terms directly in addition to the terms determined automatically.
Reset Entries:
You can use this selection to access texts that you could not yet process in the New Entries and which you have flagged as “Reset”.
Quantitative Selection:
Number of Entries:
Use this selection to determine the number of lines you want to process.
Date:
Time interval for selecting terms and proposals.
Converter name:
Use this selection for terms and proposals that have been processed or reset.
Processing:
There are four editors available for processing character strings, term determinations, term definitions and text conversions. You can access the editor for text conversions via Edit, the others via Goto.
Editor for Character Strings:
Enter a typical character string for the terms to be replaced, for example, Mat for Material.
You can exclude certain character strings from the search (exclude column, default is include) so that the search program does not find too many terms.
You get additional empty lines with New Entries.
You can change already existing character strings by overwriting them or deleting them by overwriting them with spaces.
For selecting character strings, you can only use industry sector or text selection (without development class).
Note: The search string should be at least three characters long.
Editor for Determinations:
Here, you can determine which of the terms found by the search you want to define as a term for conversion.
Newly determined terms have the status New.
If you want to assign a target term, flag the entry with Yes, if not, flag the entry with No. Terms that retain the flag New are reset later when you save.
Note: Quantitative selection does not work in this editor.
Editor for Term Definition:
Editor for Text Conversion:
Utilities:
Search Character Strings:
You can use this function to schedule the background program that searches the given character strings in all SAP short texts and that enters the terms found in the table for terms to be determined.
Runtime: Several hours.
Accept Terms:
You can use this function to schedule the background program that transfers the determined terms to the table for target terms..
Runtime: Some minutes.
Create Worklist:
You can use this function to schedule the background program that searches the terms to be replaced in all SAP short texts and that enters the terms found in the proposal pool and the textpool.
Runtime: Several hours.
Note: For this program, the number of terms that consist of more than one work has a considerable effect on runtime. The fewer multiword terms, the shorter the runtime
Distribute Short Texts:
You can use this function to schedule the background program that transfers the converted texts from the proposal pool to the textpool.
Runtime: One to two hours.
Transfer to File:
You can use this function to backup data for character strings, determinations, target terms, proposals and the textpool. The programs are started in the background. You must have already determined the file names using Goto à Path Name.
Runtime: A few minutes each.
Note: You can use Goto à Job Overview to alter the scheduling for these jobs so that they run periodically.
Load from File:
If you lose data, you can use this function to fetch the backup data from the files you determined under Goto à Path Name
Runtime: A few minutes each.
Note: The data in database tables is not deleted before reloading. Existing database entries remain unchanged and are not overwritten by the reload.
Utilities:
Statistics:
Display currently available entries in character strings, determinations, target terms, proposals, textpool.
Textpool:
Display textpool entries.
Target Terms:
Display Target Terms
Industry Sectors:
Display of available industry sectors with industry sector ID.
Converter:
Display converters per industry sector.
Realization:
Character strings, determinations, terms, proposals and the textpool are stored in transparent tables:
Character strings in table TSKTU
Determinations in table TSKTV
Terms in table TSKTW
Proposals in SBM132
Textpool in BRATEXT.
Table TSKTV is filled by the program Search Character Strings according to the entries in TSKTU.
The program Accept Terms transfers the entries from TSKTV to TSKTW.
Locate terms to be replaced in short texts (Program SAPRSBRA)
Generate proposals for proposal pool (Program SAPRSBRG)
Convert short texts in the proposal pool (Transaction CRMST62)
Distribute proposal pool texts to textpool (Table BRATEXT)
Description