SAP ABAP Message Class TBA1 (Messages for Treasury Basis Objects)
Basic Data
Hierarchy
☛
PI_BASIS (Software Component) Basis Plug-In
⤷ CA-GTF-TRB (Application Component) Financial Risk Management Basis
⤷ FTR_BASIS_DATA_ACCESS (Package) Treasury Basis Objects - Data Access
⤷ CA-GTF-TRB (Application Component) Financial Risk Management Basis
⤷ FTR_BASIS_DATA_ACCESS (Package) Treasury Basis Objects - Data Access
Attributes
Message class | TBA1 | |
Short Description | Messages for Treasury Basis Objects | |
Changed On | 20140121 | |
Last Changed At | 111204 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 010 | &1 is initial | The short text describes the object sufficiently | |
2 | 011 | No entry found for &1 | The short text describes the object sufficiently | |
3 | 012 | No entry found for &1 and &2 | The short text describes the object sufficiently | |
4 | 013 | No entry found for &1, &2, and &3 | The short text describes the object sufficiently | |
5 | 014 | No entry found for &1, &2, &3, and &4 | The short text describes the object sufficiently | |
6 | 015 | Combination of parameters &1 and &2 not valid | The short text describes the object sufficiently | |
7 | 016 | Error while processing DCS &1; action &2 is not permitted | The short text describes the object sufficiently | |
8 | 017 | &1 is inactive | The short text describes the object sufficiently | |
9 | 018 | &1 is not valid | The short text describes the object sufficiently | |
10 | 019 | Market identifier code &1 is still used; deletion not possible | Space: object requires documentation | |
11 | 020 | Period determination method &1 is still used; deletion not possible | Space: object requires documentation | |
12 | 021 | Physical commodity &1 is still used; deletion not possible | Space: object requires documentation | |
13 | 022 | Security ID determination method &1 is still used; deletion not possible | Space: object requires documentation | |
14 | 023 | DCS & does not exist | The short text describes the object sufficiently | |
15 | 024 | Tick parameter values are too high; tick calculation leads to overflow | The short text describes the object sufficiently | |
16 | 025 | Derivative category of period determination method &1 is initial | The short text describes the object sufficiently | |
17 | 026 | Timing of period determination method &1 is initial | The short text describes the object sufficiently | |
18 | 027 | No.Periods of period determination method &1 is initial | The short text describes the object sufficiently | |
19 | 028 | Period Type of period determination method &1 is initial | The short text describes the object sufficiently | |
20 | 029 | Identical time offset specified for times to maturity &1 and &2 | The short text describes the object sufficiently | |
21 | 030 | Settings for period det. method &1, phys. comm. &2 valid from &3 missing | Space: object requires documentation | |
22 | 031 | No periods defined for DCS | The short text describes the object sufficiently | |
23 | 032 | End date &1 must fall after start date &2 for key date &3 | The short text describes the object sufficiently | |
24 | 033 | Period definition contains initial lines | The short text describes the object sufficiently | |
25 | 034 | No period type specified for key date &1 | The short text describes the object sufficiently | |
26 | 035 | No period start date specified for key date &1 | The short text describes the object sufficiently | |
27 | 036 | No period end date specified for key date &1 | The short text describes the object sufficiently | |
28 | 037 | Period with missing key date | The short text describes the object sufficiently | |
29 | 038 | Key date description not specified for key date &1 | The short text describes the object sufficiently | |
30 | 039 | Strike currency (Min Strike Price &1) differs from quotation currency | The short text describes the object sufficiently | |
31 | 040 | Time to maturity definition contains more than one time parameter | The short text describes the object sufficiently | |
32 | 041 | Specify either number of years, number of months, or number of days | The short text describes the object sufficiently | |
33 | 042 | Physical commodity does not match the underlying &1 | The short text describes the object sufficiently | |
34 | 043 | No contract size specified | The short text describes the object sufficiently | |
35 | 044 | No contract size unit of measure specified | The short text describes the object sufficiently | |
36 | 045 | Period type &1 must be specified for key date &2 | The short text describes the object sufficiently | |
37 | 046 | For key date &1, the period of type &2 is only allowed once | The short text describes the object sufficiently | |
38 | 047 | Key date &1 does not have &2 | The short text describes the object sufficiently | |
39 | 048 | Underlying key date missing for key date &1 | The short text describes the object sufficiently | |
40 | 049 | Underlying key date &1 for key date &2 missing in underlying DCS &3 | The short text describes the object sufficiently | |
41 | 050 | No calendar found for derivative contract specification &1 | The short text describes the object sufficiently | |
42 | 051 | Error during calendar evaluation | The short text describes the object sufficiently | |
43 | 052 | Specify a key date | The short text describes the object sufficiently | |
44 | 053 | No BAdI implementation for filter &1 | The short text describes the object sufficiently | |
45 | 054 | Parameter definition for &1 is invalid | The short text describes the object sufficiently | |
46 | 055 | Error in configuration for period determination method &1 | Space: object requires documentation | |
47 | 056 | Period determination method &1 is not valid for this derivative category | The short text describes the object sufficiently | |
48 | 057 | Calendar &1 invalid for date &2 | The short text describes the object sufficiently | |
49 | 058 | Quotation period missing for key date &1 and timing &2 | The short text describes the object sufficiently | |
50 | 059 | There must be at least one Quotation Period Settlement per DCS. | The short text describes the object sufficiently | |
51 | 060 | Error in transport configuration | The short text describes the object sufficiently | |
52 | 061 | Entries for table &1 could not be added to transport request | The short text describes the object sufficiently | |
53 | 062 | Transport error for table &1; missing table definition | The short text describes the object sufficiently | |
54 | 063 | No transport request selected | The short text describes the object sufficiently | |
55 | 064 | Derivative contract specifications can only be displayed | Space: object requires documentation | |
56 | 065 | For key date &1 and timing &2 period type &3 is allowed only once | The short text describes the object sufficiently | |
57 | 066 | Contract period missing for key date &1 and timing &2 | The short text describes the object sufficiently | |
58 | 067 | Commodity forward index does not support period type &1 | The short text describes the object sufficiently | |
59 | 068 | No timing specified for key date &1 | The short text describes the object sufficiently | |
60 | 069 | &1 does not support period type &2 | The short text describes the object sufficiently | |
61 | 070 | No authorization to display DCS with type &1 | The short text describes the object sufficiently | |
62 | 071 | No authorization to display derivative contract specification &1 | The short text describes the object sufficiently | |
63 | 072 | No authorization to change derivative contract specification &1 | The short text describes the object sufficiently | |
64 | 073 | Switch to change mode not permitted for DCS &1 with status "Obsolete" | The short text describes the object sufficiently | |
65 | 074 | No authorization to create derivative contract specification &1 | The short text describes the object sufficiently | |
66 | 075 | Display mode not possible for new DCS &1 | The short text describes the object sufficiently | |
67 | 076 | No authorization to delete DCS with type &1 | Space: object requires documentation | |
68 | 080 | Derivative contract specification &1 is locked by user &2 | The short text describes the object sufficiently | |
69 | 081 | System failure during enqueue | The short text describes the object sufficiently | |
70 | 090 | BAdI implementation missing; functionality is not available | The short text describes the object sufficiently | |
71 | 091 | FX forward rate determination error &1 | The short text describes the object sufficiently | |
72 | 100 | Derivative contract specification &1 does not exist | The short text describes the object sufficiently | |
73 | 101 | DCS &1 does not specify a listed option or future | The short text describes the object sufficiently | |
74 | 102 | Derivative category of underlying DCS ID is not permitted | The short text describes the object sufficiently | |
75 | 103 | Listed option &2 of underlying DCS &1 is "Released" or "In Preparation" | The short text describes the object sufficiently | |
76 | 104 | Version of listed option &1 missing for version &2 of underlying | Space: object requires documentation | |
77 | 110 | Save failed | The short text describes the object sufficiently | |
78 | 111 | Transport failed | The short text describes the object sufficiently | |
79 | 112 | Transport request cannot be created; check system settings | The short text describes the object sufficiently | |
80 | 113 | Deletion failed | The short text describes the object sufficiently | |
81 | 120 | Derivative contract specification is consistent | The short text describes the object sufficiently | |
82 | 121 | Transport task &1 was successfully created | The short text describes the object sufficiently | |
83 | 122 | DCS &1 successfully saved | The short text describes the object sufficiently | |
84 | 123 | DCS &1 successfully deleted | The short text describes the object sufficiently | |
85 | 124 | Version mismatch between future &1 which is underlying and listed options | Space: object requires documentation | |
86 | 130 | There is a tick value for unlisted MIC &1 | The short text describes the object sufficiently | |
87 | 131 | Tick value is too large | Space: object requires documentation | |
88 | 132 | Tick data is not provided for all MICs | The short text describes the object sufficiently | |
89 | 133 | Tick value is not correct for 'Valid from' date &1 | Space: object requires documentation | |
90 | 134 | MIC & does not exist | The short text describes the object sufficiently | |
91 | 135 | Invalid tick currency unit &1 defined for MIC &2 | The short text describes the object sufficiently | |
92 | 136 | Invalid tick currency &1 defined for MIC &2 (&3 is expected) | The short text describes the object sufficiently | |
93 | 137 | No MIC specified | The short text describes the object sufficiently | |
94 | 138 | MIC &1 has status &2 | The short text describes the object sufficiently | |
95 | 139 | No tick value specified for MIC &1 for 'Valid from' date &2 | The short text describes the object sufficiently | |
96 | 140 | Currency units &1 and &2 are incompatible | The short text describes the object sufficiently | |
97 | 141 | Currency unit is not specified for derivative contract specification | The short text describes the object sufficiently | |
98 | 142 | Currency unit &1 is not specified | The short text describes the object sufficiently | |
99 | 143 | Currency unit &1 is not compatible with currency &2 | The short text describes the object sufficiently | |
100 | 144 | Quotation UoM does not match contract size UoM | The short text describes the object sufficiently | |
101 | 145 | MIC &1 is not in use | The short text describes the object sufficiently | |
102 | 146 | UoM &1 for key date &2 is not allowed for listed options | The short text describes the object sufficiently | |
103 | 147 | Underlying DCS is not valid on &1 | The short text describes the object sufficiently | |
104 | 148 | UoM &1 of underlying DCS cannot be converted to quotation UoM &2 | The short text describes the object sufficiently | |
105 | 149 | Contract size UoM does not match physical commodity UoM | The short text describes the object sufficiently | |
106 | 150 | Version of 'Valid from' &1 already exists | The short text describes the object sufficiently | |
107 | 151 | Derivative contract specification &1 already exists | The short text describes the object sufficiently | |
108 | 152 | 'Valid from' date was changed to lowest date &1 permitted | The short text describes the object sufficiently | |
109 | 153 | Version of 'Valid from' &1 does not exist | The short text describes the object sufficiently | |
110 | 160 | 'From' amount of strike must be smaller than 'to' amount | The short text describes the object sufficiently | |
111 | 161 | No strike amounts specified | The short text describes the object sufficiently | |
112 | 162 | For strike amount range, only one strike amount permitted | The short text describes the object sufficiently | |
113 | 169 | MICs in listed option does not correspond to the MICs in underlying DCS | The short text describes the object sufficiently | |
114 | 170 | DCS &1 cannot be released since underlying DCS is not released | The short text describes the object sufficiently | |
115 | 171 | DCS &1 cannot be released since underlying DCS is obsolete | The short text describes the object sufficiently | |
116 | 172 | Calendar is required for MIC &1 | The short text describes the object sufficiently | |
117 | 173 | Calendars are required for entries where "MIC Usable" is selected | The short text describes the object sufficiently | |
118 | 180 | Deletion is only available for the DCS that is in preparation | The short text describes the object sufficiently | |
119 | 181 | DCS &1 is used as underlying DCS of other listed options | The short text describes the object sufficiently | |
120 | 182 | No periods found for specified date &1 | The short text describes the object sufficiently | |
121 | 183 | Date &1 does not fall in an available period; no key date found | The short text describes the object sufficiently | |
122 | 190 | The fields Quantity and UoM have to be both filled or both empty | The short text describes the object sufficiently | |
123 | 200 | &1 and &2 must be disjoint for key date &3 and timing &4 | The short text describes the object sufficiently |
History
Last changed on/by | 20140121 | SAP | |
SAP Release Created in | 740 |