The purpose of this Wiki is to present common reasons for the runtime error MESSAGE_TYPE_X to happen when executing transaction TBB1 and suggestions on how to solve it.
Most of times the runtime error MESSAGE_TYPE_X happens for transaction TBB1 due to inconsistencies that must be analyzed and fixed by SAP. However, in some circustancies this dump can be eliminated by modifying your customizing, executing missing migration steps or applying correction notes.
Customizing has been changed
There was a change in your customizing (e.g. assignment of Accounting Code to Company Code or assignment of Company Code to a Valuation Area) and you have created deals or carried out changes for the position before that change. Therefore the related deal has wrong information associated to it.
To correct these inconsistencies for that deal execute the following steps:
1. Reset the customizing changes which were done before the creation of the deal.
2. Reverse the deal.
3. Carried out customizing changes.
4. Create the deal again.
Migration steps have not been executed
There are no flows in treasury ledger for a Valuation Area due to unexecuted steps in TPM_MIGRATION. The error is caused by improper migration handling. Refer to Migration Guide for more information on how to execute those steps or even start the migration process from the beginning.
Make sure the following correction notes are applied:
SAP Note 1619662 : TBB1 in bkgd job: ABAP Programming Error
SAP Note 1657817 : TBB1: Termination MESSAGE_TYPE_X TPM_TRL 065 23
SAP Note 1654669 : TBB1: Termination MESSAGE_TYPE_X TPM_TRL 065 23
SAP Note 1584499 : Termination with KE499 due to missing profitability
SAP Note 1412683 : TRL: Technical problems with Note 1407845
SAP Note 821854 : Treasury management implementation