Do you have any question about this error?
Message type: E = Error
Message class: TPM_TRAC1 - Treasury: Messages on Accounting Adaptor
Message number: 763
Message text: Konflikt bei Zuordnung des Buchungsschemas zu FortschrArt &1 ZV '&2'.
Update type &V1& is assigned for payment activity '&V2&' in the
operative valuation area to multiple flow types, which have different
posting specifications:
&V3&
&V4&
These are posting specifications for parallel position management.
The system does not assign a posting specification to update type &V1&
for payment activity '&V2&'. Otherwise the conversion of the account
determination continues.
Make sure that the Customizing settings are not contradictory.
Alternatively, you can add or change the account determination after the
conversion.
To reconstruct the conflict, check the operative posting specifications
for the flow types listed above in the old account determination.
Compare the operative and the parallel posting specifications. These are
listed in the log of this conversion step.
Typically, the parallel posting specifications have different account
symbols although the operative posting specifications have account
symbols with the same name. This has the following reasons:
The operative posting specifications have different posting categories.
The new account symbols are linked directly to one posting category.
Therefore in this case, two new account symbols must be created for one
operative account symbol.
The operative posting specifications belong to different applications.
In addition, different accounts are assigned to the account symbols with
the same account assignment reference and currency in the same chart of
accounts.
The operative account symbols are defined per application like the
posting specifications. Although the operative account symbols have the
same name, technically they are two different symbols. Since different
accounts have been assigned, you also need to create two new account
symbols.
The different, new account symbols results in different posting
specifications in both cases.
In the first case, you can possibly correct the error by adjusting the
posting categories in the operative posting specification. In the second
case, you need to check which posting specification of the update type
should actually be assigned; add the new account determination according
to this conversion step.
To check the assignment of flow types and update types, call transaction
<DS:TRAN.SM30>SM30</> and enter one of the following views:
Assignment of transaction flow types to update types: V_ATFTA
Assignment of update types to securities flow types: TRDV_DFT_SECASS.
Account determination for the operative valuation area is handled in one
of the following transactions:
<DS:TRAN.TBCY>Account Determination - Money Market (0105)</>
<DS:TRAN.TBCX>Account Determination - Forex (0106)</>
<DS:TRAN.TBCZ>Account Determination - Derivatives (0107)</>
<DS:TRAN.FWZB>Account Determination - Securities Transactions (0110)</>
<DS:TRAN.FWZA>Account Determination - Securities (0102)</>
Das System gibt eine Fehlermeldung aus und erlaubt Ihnen nicht, mit dieser Transaktion fortzufahren, bis der Fehler behoben ist.
Fehlermeldungsextrakt aus SAP-System. Copyright SAP SE
TPM_TRAC1763
- Konflikt bei Zuordnung des Buchungsschemas zu FortschrArt &1 ZV '&2'. ?Get instant SAP help. Start your 7-day free trial now.
TPM_TRAC1762
Konflikt mit vorhandenem Customizing für FortschrArt &1 ZV '&2'.
Was verursacht dieses Problem? Update type &V1& is assigned to the following flow type in the operative valuation area for payment transact...
TPM_TRAC1761
Bukrs &1 ist ungültig. Währungstauschkonten hierzu nicht umgesetzt.
Selbsterklärende Nachricht Da SAP der Meinung ist, dass diese spezielle Fehlermeldung 'selbsterklärend' ist, wurden keine weiteren Informationen geg...
TPM_TRAC1764
Bewertungsbereich &1 unzulässig für Korrekturbuchungen zu Bestandskonten.
Selbsterklärende Nachricht Da SAP der Meinung ist, dass diese spezielle Fehlermeldung 'selbsterklärend' ist, wurden keine weiteren Informationen geg...
TPM_TRAC1765
'&1' ist ein unzulässiger Eintrag für den Zahlungsvorgang.
Was verursacht dieses Problem? '&V1&' has been entered for the payment transaction in the posting specification for flow type &am...
Klicken Sie auf diesen Link, um alle SAP-Meldungen durchsuchen.