Do you have any question about this error?
Message type: E = Error
Message class: WA - Messages from Workflow Event Manager
Message number: 642
Message text: Lien de types entre & & et & : entrée avec autres données secondaires
When the specified linkage was entered, it was found that an entry with
this key already exists. However, the entry which already exists has
different secondary data than that currently passed. This means that
one of the following fields has a different value for the existing
entry than that passed in the current call:
CHECKFB (check function module)
RECFB (receiver function module)
RECGETFB (function module for determining receiver type)
GLOBAL (indicator for type linkage)
The action was terminated. The old entry is not changed, the new entry
was not inserted.
Check the call of the function module in your source text. Compare the
values passed (e.g. using the event trace) with the values already
contained in the type linkage table (e.g. using trasaction
<DS:TRAN.SWETYPV>SWETYPV</>). If necessary, delete the old entry and
then try the action again.
Extrait du message d'erreur du système SAP. Copyright SAP SE.
WA642
- Lien de types entre & & et & : entrée avec autres données secondaires ?Get instant SAP help. Start your 7-day free trial now.
WA641
Lien de types entre & & et & : exception & lors insert. objet transport
Quelle est la cause de ce problème? The specified exception was initiated for the specified type linkage between the object type and event and the ...
WA640
Lien de types entre & & et & : exception & lors ctrl objet de transport
Quelle est la cause de ce problème? The specified exception was initiated for the specified type linkage between the object type and event and the ...
WA643
Imposs. de supprimer les liens de types pour la tâche & de la table &
Quelle est la cause de ce problème? The type linkages to task &v1& cannot be deleted from table &v2&.Réponse du système The acti...
WA644
Impossible d'actualiser les liens de types entre &1-&2 et &3
Message auto-explicatif Étant donné que SAP estime que ce message d'erreur spécifique est 'auto-explicatif', aucune autre information n'a été fou...
Cliquez sur ce lien pour rechercher tous les messages SAP.