TPM_TRM1 - Migration 4.6 - CFM 1.0
The following messages are stored in message class TPM_TRM1: Migration 4.6 - CFM 1.0.
It is part of development package FTR_MIGRATION_10 in software component FIN-FSCM-TRM-TM. This development package consists of objects that can be grouped under "CFM 1.0: Data Migration".
It is part of development package FTR_MIGRATION_10 in software component FIN-FSCM-TRM-TM. This development package consists of objects that can be grouped under "CFM 1.0: Data Migration".
Message Nr ▲ | Message Text |
|---|---|
| 000 | A fatal error occurred |
| 001 | Error while converting interest accrual/deferral |
| 002 | No general valuation class is available in the system |
| 003 | No business transactions are available for processing |
| 004 | Error in the distribution |
| 005 | Interest accrual/deferral: Unknown activity category |
| 006 | Internal error: Storage of business transactions |
| 007 | Planned WEC, WES and/or WTE records exist |
| 008 | No appropriate corporate action found for co.code &1, daybook number &2 |
| 009 | VWBEVI record: CoCd &1, daybook number &2 does not agree with corp.action |
| 100 | *** Migration of Position Mgmt Documents for Derivatives (DEDOC) *** |
| 101 | Unable to determine business transaction category of document (&1, &2) |
| 102 | Accounting code &1 is not assigned to valuation area 001 |
| 103 | Internal error: Extraction of margin business transactions |
| 104 | For valuation area 001, no posting is stored in the general ledger |
| 105 | For valuation area 001, local currency is not the same as the val. crcy |
| 106 | System settings for migration of futures are consistent |
| 107 | Internal error; FI update for irrelevant business transaction category |
| 108 | Internal error; cannot determine legacy data for margin business trans. |
| 109 | Internal error; cannot determine legacy data for close business trans. |
| 110 | Internal error; in a business trans. the security doc. no. is not unique |
| 111 | Internal error; legacy data is not available in the format expected |
| 112 | Internal error; a business transaction has an unexpected status |
| 113 | Internal error; FI document is not in the expected form |
| 114 | In valuation area 001, the subledger contains a reversed document |
| 115 | There is no FI document for a document in the subledger |
| 116 | There are multiple FI documents for a document in the subledger |
| 117 | Number of line items in subledger document and FI document is different |
| 118 | Subledger document and FI document contain different amounts |
| 119 | For a subledger document, there is no business trans. in futures mgmt |
| 120 | For a subledger document, there are multiple bus. trans. in futures mgmt |
| 121 | Too many/too few line items in subledger document; see long text |
| 122 | Line items in subledger doc. and flows in futures mgmt are different |
| 123 | Subledger document missing for posting-relevant bus. trans; see long text |
| 124 | Migrated data is consistent |
| 125 | Update type &1 is not relevant for posting |
| 126 | Unexpected subledger document for business transaction category &3 |
| 127 | Derived business transaction is missing for a subledger document |
| 128 | Subledger document is missing for a derived business transaction |
| 129 | Derived business transaction cannot be assigned |
| 130 | No display variants found for transaction TPM12 |
| 131 | Error when reading fields from display variant &1 (transaction TPM12) |
| 132 | Backup copy of display variant &1 was generated |
| 133 | Backup copy of display variant &1 is available |
| 134 | Display variant &1 was converted to the new field descriptions |
| 135 | Display variant &1 was converted to the old field descriptions |
| 136 | There are no display variants to convert for transaction TPM12 |
| 137 | Step is not transported, execute in each system. |
| 138 | Selection variants for transaction TPM12 are converted |
| 139 | Error on converting selection variant &1 |
| 140 | Selection variant &1 already exists |