IST_EBS - Schnittstelle zwischen IS-T und externem Billing System
The following messages are stored in message class IST_EBS: Schnittstelle zwischen IS-T und externem Billing System.
It is part of development package IST20 in software component IS-T. This development package consists of objects that can be grouped under "IS-T : Interfaces".
It is part of development package IST20 in software component IS-T. This development package consists of objects that can be grouped under "IS-T : Interfaces".
Message Nr ▲ | Message Text |
---|---|
100 | No agreements or invalid agreements were made for system &1 |
109 | Application &1 is not permitted for document transfer |
110 | An error occured while converting the &1 segment |
111 | No control lines were found for document &1 |
112 | No items were found for document &1 |
113 | Entry &1 is too long for a contract account number |
114 | Entry &1 is too long for a contract reference |
115 | Contract item &1 could not be found in the VBKD table |
116 | Entry &1 is too long for a business partner number |
117 | Contract account for business partner &1 could not be found |
118 | Business partner &1 has more than one contract account |
119 | No contract account could be found for the telephone number &1 |
120 | The taxes for doc. &1 are incompatible with the internally calc. taxes |
121 | The taxes for the item are incompatible with the internally calc. taxes |
122 | Condition type &1 does not exist or is not intended for taxes |
123 | The external doc. no. &1 is too long to be used as an internal doc. no. |
124 | The &1 field in the transfer structure must contain a value |
125 | The date entered, &1, has an incorrect or invalid form |
126 | The currency amount &1 &2 could not be converted |
127 | The &1 field contains invalid characters |
128 | The reference object ID &1 is not defined in the system |
129 | Contract account &1 does not have a unique business partner |
130 | Reversal is not possible using the REVERSE functionality from RM-CA |
131 | Only billing type reversal &1 is from category IS-T external billing |
140 | All documents in the &1 IDoc were posted successfully |
141 | An error occured while posting at least one of the documents in IDoc &1 |
150 | Several documents exist for the triple AWTYP = &1, AWSYS = &2, AWKEY = &3 |
151 | Line &1 of IDoc &2 has an unexpected segment name |
152 | The data string in line &1 of IDoc &2 could not be converted |
153 | Parallelization-object and/or -variant are not maintained (-> long text) |
154 | No document exists for the triple AWTYP = &1, AWSYS = &2, AWKEY = &3 |
155 | All documents identified by IDoc &1 were successfully reversed |
156 | Parallelization variant could not be updated |
157 | No IDocs were selected in the interval between &1 and &2 |
158 | There were problems processing at least one line in the IDoc &1 |
159 | IDoc &1 does not contain any data |
160 | Interval from &1 to &2: &4 of &3 IDocs were successfully processed |
161 | The application could not be determined (problem in FKK_GET_APPLICATION) |
162 | The trunk &1 already has the maximum no. of reconciliation keys (999) |
163 | Error while processing IDoc &1 |
164 | Function module IST_EBS_MRD_DET_FIKEY was called up in the wrong context |
165 | Function module IST_EBS_CLOSE_FIKEY was called up in the wrong context |
166 | Close reconciliation key &1 manually! Call up test reports |
167 | Function module &1 is not intended for the mass activity &2 |
168 | Processing error in IDoc interval between &1 and &2. Message type &3 |
169 | Function module IST_EBS_TOI_DET_FIKEY was called up in the wrong context |
170 | Problem occured in acct determination (Func. mod. FKK_ACCOUNT_DETERMINE) |
171 | User &1 does not have authorization for mass reversal |
172 | Reconciliation key not determined (problem in event T402) |
173 | Inconsistency after form &1. Contact administrator |
174 | Inconsistency after function module &1. Contact administrator |
175 | A problem occured in function module &2 while reversing doc. &1 |
176 | Problem in function module FKK_CREATE_DOC_MASS_STOP. Reconcil. key &1 |
177 | Unexpected problems in function module &1. Contact administrator |
178 | Problems in form &1. Contact administrator |
179 | Cancelled due to inconsistencies in func. mod. FKK_CREATE_DOC_MASS_STOP |
180 | Cancelled because reconciliation key &1 could not be closed |
181 | Function could not be determined. Prob. in FKK_FUNC_MODULE_DETERMINE |
182 | Error processing '69' IDocs that previously were '64' or '66' |
183 | Error processing '69' IDocs that previously had ALE errors |
184 | Error processing '69' IDocs: interval between &1 and &2, message type &3 |
185 | Specify a lower limit |
186 | The action category could not be determined |
187 | The screen is being used in the wrong context |
188 | Activity &2 is defined for user key &1, not activity &3 |
189 | The IST_EBS_VARIANT_CHECK func. mod. does not account for activ. type &1 |
190 | Too few IDocs for processing. Use a different variant |
191 | The range table containing the status is incorrectly filled |
192 | Inconsistency in radio button grp on screen 4550 in IST_EBS_MASS_ACT |
193 | Mass activity type &1 does not exist |
194 | Mass activity &1 and job type &2 do not suit |
195 | A mass activity is already stored for user key &1 |
196 | One of the input parameters is not filled |
197 | Mandatory parameters are not set |
198 | Mass run activity &1 and IDs &2 and &3 could not be created |
199 | No jobs were created |
200 | Error assigning data from IDoc &1 to internal table |
201 | The link between &1 and &2 is not maintained in the TOAOM table |
202 | Error while processing the IDoc segment |
203 | The IDoc was posted successfully |
204 | A link for &2 does not exist in the &1 table |
205 | Invalid date &1 |
206 | Error while checking the date |
207 | Problem occured when reblocking reconciliation key for general ledger |
208 | Cannot find contract account &1 |
209 | The calculative CO-PA profitability analysis is not active |
210 | No characteristic derivation defined for CO-PA operating concern &1 |
211 | Error during characteristic allocation for external characteristic &1 |
212 | Error during CO-PA characteristic allocation of internal characteristics |
213 | Error when copying characteristics to G/L item |
214 | CO-PA characteristic is initial for characteristic val. &1 in op. con. &2 |
215 | No allocation exists for ext. characteristic &1 in operating concern &2 |
300 | No unique entry in IST_EBS_POI_SYST using combination &1/&2/&3/&4 |
301 | Customizing for &1/&2/&3/&4 in IST_EBS_POI_SYST is imcomplete |
302 | &1 is not a date variable |
303 | A system exception occured while converting the IDoc &1 |
304 | Incorrect IDoc: Segment &2 not intended for type &1 |
305 | Inconsistency in conversion of IDoc &1 |
306 | There is no valid customer function module for event T410 |
307 | An error occured while converting the data fields |
308 | Field &1 exceeds the maximum length of &2 |
309 | Account statement only possible if selection entity = VKONT |
310 | Incorrect Customizing: &1 - &2 combination not allowed |
311 | Problem in IST_TELNUM_FIND function module |
312 | No selection conditions. All open items were selected |
313 | Problem in FKK_MASS_OPEN_ITEM_SELECT_GET function module |
314 | IDoc &1 was successfully processed |
315 | At least one incorrect IDoc (no. &1) was created |
316 | Selection conditions exist for two different entities |
317 | Problem reading the Customizing information for the account statement |
318 | At least one of the contract accounts does not exist |
319 | Account statements were only requested for &1 out of &2 contract accounts |
320 | No IDocs were created |
321 | Problem checking the distribution model for message type &1 |
322 | The distribution model for message type &1 is not maintained |
323 | The TFKTVOT text table does not contain an entry for the &1/&2/&3/&4 key |
324 | Incorrect settings in IST_EBS_POI_SYST for &1/&2/&3/&4 |
325 | The T_VKONT selection table is incorrectly filled |
326 | The IST_EBS_POI_SET_CORR_DATE f.m. was called up in the wrong context |
340 | Account statements can only be requested using CACCTs or BPARTs |
341 | No selection conditions specified: the T_SEL_ENT table is empty |
342 | There are already 100 IDs with &2 as body for the date &1 |
350 | The IDoc for the master data output could not be created |
400 | Problems occured while creating the job for submitting FKJO_SCHEDULE |
401 | Problems occured while closing the job for submitting FKJO_SCHEDULE |
402 | FKJO_SCHEDULE exceeded max time: job no. &1, job name &2 |
403 | FKJO_SCHEDULE was cancelled: job no. &1, job name &2 |
404 | The job for executing FKJO_SCHEDULE was not started |
405 | Error reading the job log for job no. &1, job name &2 |
406 | A problem occured while reading the job status of job no. &1, job name &2 |
407 | FKJO_SCHEDULE completed successfully. Mass run is scheduled |
408 | The job log for job no. &1, job name &2 is not in the expected format |
409 | Mass run created with IDs &1 and &2 |
410 | Jobs created with IDs &1 and &2 |
500 | The application is &1, not &2 |
501 | This function is only planned for application &1 or &2 |