Symptom
1. When you branch to the header or item text screen in a document (such as a sales order), for
example, the system issues message VX 201 "Error in text formatting". The text screen does not
contain any text types.
2. Texts are not found in a document (such as a sales order). From the text determination
analysis, the system issues the information "Access sequence does not exist" (VX 111).
3. In a document (such as a sales order), the system does not display a description for a text
type or text ID and/or when you branch to the text detail or to the SAPscript editor, the system
issues the message "Texts: Internal errors" (VX 205).
Other Terms
VC01N, VC01N_M, VA01, VA02, VA11, VA12, VA21, VA22, VA31, VA32, VA41, VA42, VL01N, VL02N, VF01,
VF02, VA03, VA13, VA23, VA33, VA43, VL03N, VF03, texts, header texts, item texts, text determination
procedure, text group, text type, text ID, access sequence, upgrade
VX 201, VX201, 111, VX111, 205, VX205, SD_WORD_PROCESSING, SAPLV70T, LV70TU01,
SD_WORD_PROCESSING_PUT, LV70TU09, SD_TEXT_DEFAULT_LANGUAGE, SAPLV75T, LV75TU03
VOTX, VOTXN, TTXERN
Reason and Prerequisites
This note provides troubleshooting tips.
The messages VX 201, VX 111 and VX 205 may have different causes, but they are often due to
incorrect or incomplete text Customizing (transaction VOTXN).
Solution
Check the text Customizing (transaction VOTXN):
1. Message VX 201 "Error in text formatting"
a) Text determination procedure use or text determination procedure assignment
The text determination procedure assigned to the document type or the item category used
does not exist.
Assign an existing text determination procedure to the document type or to the item
category, or create the missing text determination procedure.
b) Text determination procedure
The text determination procedure assigned to the document type or to the item category is
empty.
For billing documents (transactions VF01, VF02, VF03), refer to Note 1336286, if it isvalid.
Otherwise, maintain the text determination procedure. A correct text determination procedure
must contain at least one text type or text ID.
c) Too many languages may have been installed - more than 100 - refer to SAP Note 1784478.
2. Message VX 111 "Access sequence does not exist"
a) Generate the access sequences: Transaction VOTXN: From the menu, choose "Texts ->
Generate access".
b) The access sequence assigned to a text type or text ID in the text determination
procedure that is used (document type or item category) does not exist.
Assign an existing access sequence to the text type or text ID, or create the missing access
sequence.
3. Message VX 205 ""Texts: Internal errors"
a) Refer to the following notes, if they are valid (and relevant):
¡ 543726 (consulting)
¡ 582099 (correction)
¡ 585690 (correction)
¡ 622842 (correction)
¡ 764720 (correction)
¡ 767999 (correction)
b) The text type or text ID assigned in the text determination procedure used (document type
or item category) may not be created in transaction SE75 for the relevant text object (VBBK
or VBBP, for example).
Use a valid text type or text ID in the text determination procedure, or assign the text
type or text ID to the relevant text object using transaction SE75.
其他相关Notes：
581779 - Text determination analysis: Access sequence does not exist
771777 VOTXN: No automatic generation of accesses
744390 VOTXN: No automatic generation in TTXVR after shipment
649895 VOTXN: Incorrect entrs in TTXVR after saving access sequence
659741 BC set activation: Access sequences are missing
713082 RVTEXTE Access sequences missing in text procedures
1002455 Errors in texts: Messages VX 201, VX 111, and VX 205
606643 VOTXN: incorrect txt determ after transport into target syst
535649 SAP R/3 Enterprise 47x110 Server installation/upgrade Asia
574841 There are various errors/ms in transaction VOTXN.
970153 Change to Customizing text not transferred to target system
581779 Text determination analysis: Access sequence does not exist
源链接
1184
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
