Solution : https://service.sap.com/sap/support/notes/581779 (SAP Service marketplace login required)
Summary :
In the SAP system, users reported an issue where despite configuring a text ID with an access sequence, the system fails to determine the text, incorrectly triggering error message VX111 indicating a nonexistent access sequence. This issue originates from a programming error. To address this, changes are recommended in the view cluster definitions according to outlined steps involving transaction SE57 and subsequent modification of specific parameters. Additionally, SAP Notes 649895 and 606643 should be consulted for a complete resolution. Caution is advised as the initial correction point is incorrectly listed and further guidance in Note 649895 should be observed.
Key words :
call transaction se57 - choose 'edit viewcluster', system processes message vx111, message number vx111, - choose 'create/change', text determination procedure, text customizing votxn, attached correction instructions, view cluster definitions, view cluster vc_ordh, access sequence exists
Related Notes :
| 771777 | VOTXN: No automatic generation of accesses |
| 744390 | VOTXN: No automatic generation in TTXVR after shipment |
| 713082 | RVTEXTE Access sequences missing in text procedures |
| 659741 | BC set activation: Access sequences are missing |
| 649895 | VOTXN: Incorrect entrs in TTXVR after saving access sequence |
| 606643 | VOTXN: incorrect txt determ after transport into target syst |
| 574841 | There are various errors/ms in transaction VOTXN. |