Professional Documents
Culture Documents
GU - SAP S4 HANA - 966625 - Dummy Phantom Texts or Unclear Text Origin
GU - SAP S4 HANA - 966625 - Dummy Phantom Texts or Unclear Text Origin
com/
When you create a document (for example, a sales order), texts (header or/and item) with an
unclear origin are determined. Furthermore, the text determination analysis cannot explain the
origin of the text.
After you save the document, the incorrect texts sometimes no longer exist in the document.
The problem is most likely due to the dummy texts in the system.
The reason for creating the incorrect texts (dummy texts) is as yet unclear.
However, they are almost certainly generated as a result of a modification.
Solution
Delete the dummy texts
To correct the text tables or delete the dummy texts, you can execute the RVTEXTE report with
action 'X'.
For more information, see the documentation for the RVTEXTE report in SAP Note 963314.
Background information
Dummy texts are texts that were incorrectly written to the database with a name temporarily
assigned by the application - without the text name being correctly renamed beforehand.
The "administrative data" of texts is stored in the STXH table. The MANDT, TDOBJECT, TDNAME,
TDID and TDSPRAS fields are key fields. The TDNAME field (name) is filled with the key of the
application object.
If texts are now saved or posted as a result of a modification before the renaming, dummy texts that
have names that still contain the temporary document number are created.
For example, this may be caused by calling the 'SD_COMMIT_TEXT' or 'COMMIT_TEXT' function
module with incorrect parameter settings in a user exit.
https://www.linkedin.com/in/mickaelquesnot/
1
Mickael QUESNOT © https://s4hclub.com/
https://www.linkedin.com/in/mickaelquesnot/
2
Mickael QUESNOT © https://s4hclub.com/
https://www.linkedin.com/in/mickaelquesnot/
3
Mickael QUESNOT © https://s4hclub.com/
https://www.linkedin.com/in/mickaelquesnot/
4
Mickael QUESNOT © https://s4hclub.com/
o D Delete the complete texts (headers and lines; see the tables STXH and STXL) using
the selection criteria "Text object", "Text types", "Text language", "Text name",
"User" and "Commit after n records".
The other indicators are ignored.
A confirmation prompt occurs in the dialog before deleting the selected texts.
o E E The system displays all the texts that do not contain a reference to current
documents (only background processing possible). In this case, the selection
criteria/indicators are ignored.
For large data volumes, this action may require long runtimes.
Data inconsistencies are the cause of such texts.
o F Deleting the texts without document reference. In this case, the selection
criteria/indicators are ignored.
A confirmation prompt occurs in the dialog before deleting the selected texts.
For large data volumes, this action may require long runtimes.
o X Deleting all dummy texts. In this case, the selection parameters/indicators are
ignored. A confirmation prompt occurs in the dialog before deleting the selected
texts.
Consultation note 966625 contains further information about dummy texts.
The following text entries (see text headers) are removed:
VBBK X*
https://www.linkedin.com/in/mickaelquesnot/
5
Mickael QUESNOT © https://s4hclub.com/
VBBK $*
VBBP X*
VBBP $*
VBKA X*
VBKA $*
VTTK $*
WBRK $*
WBRP....................$*
WBHK $*
WBHI $*
KNA1 INTERN*
KNB1 INTERN*
KNVK INTERN*
KNVV INTERN*
https://www.linkedin.com/in/mickaelquesnot/
6
Mickael QUESNOT © https://s4hclub.com/
Recommendation Before deleting these texts, you should display the text headers with
the action parameter "A" and check them again, if required.
You can display the texts when executing an individual text of the function module READ_TEXT
(transaction SE37).
Caution Before you execute action "X", you must check if the text names listed in this table are not
used as external (document) numbers (see background information in SAP Note 966625).
- TTXER:
Entries with multiple assignment of a text type (TDID) for a text determination procedure
(TXTGR) are deleted.
Entries with the initial text object (TDOBJECT) are deleted.
Entries with the initial text type (TDID) are deleted.
Entries with the initial sequence number (LFDTX) are corrected.
Entries of mandatory texts are corrected regarding the error group/incompletion
procedure (FEHGR).
- TTXZI:
Identical entries that only differ in the sequence number (TXLFN) are deleted.
Entries with the initial sequence number (TXLFN) are corrected.
Inconsistent entries regarding the partner role (PARVW_VON) are corrected.
KNA1, KNVK, KNVV, KONA, KONP, VBBK, VBBP, VBKA, VTTK, AKKP, EMBK, WBRK, WBRP,
WBHK, and WBHI, and
- With the initial text group object (TXTOB), or
- With the initial text type (TDID), or
- With the initial sequence number (LFDTX).
The selection criterion/indicators are ignored - also the indicator "Sort Customizing
Tables".
https://www.linkedin.com/in/mickaelquesnot/
7
Mickael QUESNOT © https://s4hclub.com/
https://www.linkedin.com/in/mickaelquesnot/
8
Mickael QUESNOT © https://s4hclub.com/
https://www.linkedin.com/in/mickaelquesnot/
9
Mickael QUESNOT © https://s4hclub.com/
https://www.linkedin.com/in/mickaelquesnot/
10
Mickael QUESNOT © https://s4hclub.com/
https://www.linkedin.com/in/mickaelquesnot/
11
Mickael QUESNOT © https://s4hclub.com/
https://www.linkedin.com/in/mickaelquesnot/
12
Mickael QUESNOT © https://s4hclub.com/
Result
https://www.linkedin.com/in/mickaelquesnot/
13