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