SAP ABAP Message Class FKK_EBS (Interface between FI-CA and External Billing System)
Basic Data
Hierarchy
☛
FI-CA (Software Component) FI-CA
⤷ FI-CA (Application Component) Contract Accounts Receivable and Payable
⤷ FKKIDOC (Package) Contract Accounts Receivable and Payable: IDoc Interface
⤷ FI-CA (Application Component) Contract Accounts Receivable and Payable
⤷ FKKIDOC (Package) Contract Accounts Receivable and Payable: IDoc Interface
Attributes
Message class | FKK_EBS | |
Short Description | Interface between FI-CA and External Billing System | |
Changed On | 20130531 | |
Last Changed At | 112234 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 010 | Error calling event 2480 | The short text describes the object sufficiently | |
2 | 011 | Error determining field for invoice number | The short text describes the object sufficiently | |
3 | 012 | No document found for invoice number &1 | The short text describes the object sufficiently | |
4 | 013 | Field &1 does not exist in document table (DFKKKO) | The short text describes the object sufficiently | |
5 | 014 | No document exists for document number &1 | The short text describes the object sufficiently | |
6 | 015 | Invoice number &1 is not unique; more than 1 document found | The short text describes the object sufficiently | |
7 | 016 | Communication error calling XI interface: &1 | The short text describes the object sufficiently | |
8 | 017 | Length of invoice number &1(&2) > length of field &3(&4) | The short text describes the object sufficiently | |
9 | 098 | No payment method in SAP system for external payment method &1 | The short text describes the object sufficiently | |
10 | 099 | No internal ID in SAP system for external business partner ID &1 | The short text describes the object sufficiently | |
11 | 100 | No agreements or invalid agreements exist for system &1 | Space: object requires documentation | |
12 | 102 | Key of the payment form item is formally incorrect | Space: object requires documentation | |
13 | 108 | No deferred revenue posting permitted for revenue items with amount 0 | The short text describes the object sufficiently | |
14 | 109 | Application &1 is not permitted for document transfer | Space: object requires documentation | |
15 | 110 | An error occured while converting the &1 segment | Space: object requires documentation | |
16 | 111 | No control lines were found for document &1 | Space: object requires documentation | |
17 | 112 | No items were found for document &1 | Space: object requires documentation | |
18 | 113 | Entry &1 is too long for a contract account number | Space: object requires documentation | |
19 | 114 | Entry &1 is too long for a contract reference | Space: object requires documentation | |
20 | 115 | Contract item &1 could not be found in the VBKD table | Space: object requires documentation | |
21 | 116 | Entry &1 is too long for a business partner number | The short text describes the object sufficiently | |
22 | 117 | Contract account for business partner &1 could not be found | Space: object requires documentation | |
23 | 118 | Business partner &1 has more than one contract account | Space: object requires documentation | |
24 | 119 | No contract account could be found for the telephone number &1 | Space: object requires documentation | |
25 | 120 | The taxes for doc. &1 are incompatible with the internally calc. taxes | Space: object requires documentation | |
26 | 121 | The taxes for the item are incompatible with the internally calc. taxes | Space: object requires documentation | |
27 | 122 | Condition type &1 does not exist or is not intended for taxes | Space: object requires documentation | |
28 | 123 | The external doc. no. &1 is too long to be used as an internal doc. no. | Space: object requires documentation | |
29 | 124 | Field &1 must contain a value in the transfer structure | Space: object requires documentation | |
30 | 125 | The date &1 entered is incorrect format or invalid | The short text describes the object sufficiently | |
31 | 126 | The currency amount &1 &2 could not be converted | Space: object requires documentation | |
32 | 127 | Field &1 contains invalid characters | Space: object requires documentation | |
33 | 128 | External document category &1 is not permitted (IV, AJ, DP) | The short text describes the object sufficiently | |
34 | 129 | Contract account &1 does not have a unique business partner | Space: object requires documentation | |
35 | 130 | No reversal possible using REVERSE function of FI-CA | Space: object requires documentation | |
36 | 131 | Tax amount is different in BPITEM and TAXITEM | The short text describes the object sufficiently | |
37 | 132 | Name for the external system must be unique | Space: object requires documentation | |
38 | 133 | No external tax processing permitted for down payment requests | The short text describes the object sufficiently | |
39 | 134 | External tax percentage rate is not permitted here | Space: object requires documentation | |
40 | 135 | No open items found for business partner &1 | The short text describes the object sufficiently | |
41 | 136 | Unable to find open item with number &1 | The short text describes the object sufficiently | |
42 | 137 | No &1 permitted in write-off process | The short text describes the object sufficiently | |
43 | 138 | Errors occurred during creation of profitability segments | The short text describes the object sufficiently | |
44 | 139 | Deferred revenues are higher than actual revenues | The short text describes the object sufficiently | |
45 | 140 | All documents successfully configured in reconciliation key &1 | Space: object requires documentation | |
46 | 141 | An error occured while posting at least one of the documents in IDoc &1 | Space: object requires documentation | |
47 | 142 | No assignment of tax item categories to other tax codes exists | The short text describes the object sufficiently | |
48 | 143 | No entry in Customizing for receiver &1 and sender &2 | Space: object requires documentation | |
49 | 144 | No internal ID in SAP system for external contract account ID &1 | The short text describes the object sufficiently | |
50 | 145 | Assign a unique reference number for each business partner item | The short text describes the object sufficiently | |
51 | 146 | Reference number &1 exists already | The short text describes the object sufficiently | |
52 | 147 | No &2 permitted in prepayment process | The short text describes the object sufficiently | |
53 | 148 | For external write-off only external tax handling is permitted | The short text describes the object sufficiently | |
54 | 149 | Information for creating an IDoc is missing | The short text describes the object sufficiently | |
55 | 150 | Several documents exist for the triple AWTYP = &1, AWSYS = &2, &3 = &4 | Space: object requires documentation | |
56 | 151 | Line &1 of IDoc &2 has an unexpected segment name | Space: object requires documentation | |
57 | 152 | The data string in line &1 of IDoc &2 could not be converted | Space: object requires documentation | |
58 | 153 | Parallelization object and/or variant are not maintained (-> long text) | Space: object requires documentation | |
59 | 154 | No document exists with AWTYP = &1, AWSYS = &2, &3 = &4 | Space: object requires documentation | |
60 | 155 | All documents identified by IDoc &1 were successfully reversed | The short text describes the object sufficiently | |
61 | 156 | Parallelization variant could not be updated | Space: object requires documentation | |
62 | 157 | No IDocs were selected in the interval between &1 and &2 | Space: object requires documentation | |
63 | 158 | There were problems processing at least one line in the IDoc &1 | Space: object requires documentation | |
64 | 159 | IDoc &1 does not contain any data | Space: object requires documentation | |
65 | 160 | Interval from &1 to &2: &4 of &3 IDocs were successfully processed | Space: object requires documentation | |
66 | 161 | The application could not be determined (problem in FKK_GET_APPLICATION) | Space: object requires documentation | |
67 | 162 | The trunk &1 already has the maximum no. of reconciliation keys (999) | Space: object requires documentation | |
68 | 163 | Error while processing IDoc &1 | Space: object requires documentation | |
69 | 164 | Function module FKK_EBS_MRD_DET_FIKEY was called in incorrect context | Space: object requires documentation | |
70 | 165 | Function module FKK_EBS_CLOSE_FIKEY was called in incorrect context | Space: object requires documentation | |
71 | 166 | Close reconciliation key &1 manually! Call up test reports | Space: object requires documentation | |
72 | 167 | Function module &1 is not intended for the mass activity &2 | Space: object requires documentation | |
73 | 168 | Processing error in IDoc interval between &1 and &2; Message type &3 | Space: object requires documentation | |
74 | 169 | Function module FKK_EBS_TOI_DET_FIKEY was called in incorrect context | Space: object requires documentation | |
75 | 170 | Problem occured in acct determination (Func. mod. FKK_ACCOUNT_DETERMINE) | Space: object requires documentation | |
76 | 171 | User &1 does not have authorization for mass reversal | The short text describes the object sufficiently | |
77 | 172 | Reconciliation key not determined (event 2402) | Space: object requires documentation | |
78 | 173 | Inconsistency after form &1; contact administrator | The short text describes the object sufficiently | |
79 | 174 | Inconsistency after function module &1; contact administrator | Space: object requires documentation | |
80 | 175 | A problem occured in function module &2 while reversing doc. &1 | Space: object requires documentation | |
81 | 176 | Problem in function module FKK_CREATE_DOC_MASS_STOP; reconcil. key &1 | Space: object requires documentation | |
82 | 177 | Unexpected problems in function module &1; contact administrator | Space: object requires documentation | |
83 | 178 | Problems in form &1; contact administrator | The short text describes the object sufficiently | |
84 | 179 | Cancelled due to inconsistencies in func. mod. FKK_CREATE_DOC_MASS_STOP | Space: object requires documentation | |
85 | 180 | Cancelled because reconciliation key &1 could not be closed | Space: object requires documentation | |
86 | 181 | Function could not be determined; prob. in FKK_FUNC_MODULE_DETERMINE | Space: object requires documentation | |
87 | 182 | Error processing '69' IDocs that previously were '64' or '66' | Space: object requires documentation | |
88 | 183 | Error processing '69' IDocs that previously had ALE errors | Space: object requires documentation | |
89 | 184 | Error processing 69 IDoc interval between &1 and &2, message type &3 | The short text describes the object sufficiently | |
90 | 185 | Specify a lower limit | Space: object requires documentation | |
91 | 186 | The action category could not be determined | Space: object requires documentation | |
92 | 187 | The screen is being used in the wrong context | Space: object requires documentation | |
93 | 188 | Activity &2 is defined for user key &1, not activity &3 | Space: object requires documentation | |
94 | 189 | Function module FKK_EBS_VARIANT_CHECK does not support activity type &1 | Space: object requires documentation | |
95 | 190 | Too few IDocs for processing; use a different variant | Space: object requires documentation | |
96 | 191 | The range table containing the status is incorrectly filled | Space: object requires documentation | |
97 | 192 | Inconsistency in selection button grp on screen 4550 of FKK_EBS_MASS_ACT | Space: object requires documentation | |
98 | 193 | Mass activity type &1 does not exist | Space: object requires documentation | |
99 | 194 | Mass activity &1 and job type &2 do not suit | Space: object requires documentation | |
100 | 195 | A mass run is already defined for user key &1 | Space: object requires documentation | |
101 | 196 | One of the input parameters is not filled | Space: object requires documentation | |
102 | 197 | Required parameters are not set | The short text describes the object sufficiently | |
103 | 198 | Mass run activity &1 and IDs &2 and &3 could not be created | Space: object requires documentation | |
104 | 199 | No jobs were created | Space: object requires documentation | |
105 | 200 | Error assigning data from IDoc &1 to internal table | Space: object requires documentation | |
106 | 201 | The link between &1 and &2 is not maintained in the TOAOM table | Space: object requires documentation | |
107 | 202 | Error while processing the IDoc segment | Space: object requires documentation | |
108 | 203 | IDoc was posted successfully | The short text describes the object sufficiently | |
109 | 204 | No link for &2 exists in table &1 | The short text describes the object sufficiently | |
110 | 205 | Invalid date &1 | The short text describes the object sufficiently | |
111 | 206 | Error checking the date | The short text describes the object sufficiently | |
112 | 207 | Problem occured when reblocking reconciliation key for general ledger | Space: object requires documentation | |
113 | 208 | Cannot find contract account &1 | Space: object requires documentation | |
114 | 209 | The accrued CO-PA profitability analysis is not active | The short text describes the object sufficiently | |
115 | 210 | No characteristic derivation defined for CO-PA operating concern &1 | Space: object requires documentation | |
116 | 211 | Error in CO-PA characteristic assignment for external characteristic &1 | Space: object requires documentation | |
117 | 212 | Error in CO-PA characteistic assignment of internal characteristics | Space: object requires documentation | |
118 | 213 | Error when copying characteristics to G/L item | The short text describes the object sufficiently | |
119 | 214 | CO-PA charac. is initial for charac. value &1 in operating concern &2 | Space: object requires documentation | |
120 | 215 | No assignment exists for ext. characteristic &1 in operating concern &2 | Space: object requires documentation | |
121 | 216 | Error determining CO default account assignments | Space: object requires documentation | |
122 | 217 | Incorrect processing logic: Logic without CO-PA, but CO-PA data segment | The short text describes the object sufficiently | |
123 | 218 | Billing system data cannot be loaded from Customizing | The short text describes the object sufficiently | |
124 | 219 | Activity category is unknown | The short text describes the object sufficiently | |
125 | 220 | Unable to determine the data of the billing system | Space: object requires documentation | |
126 | 221 | &1 documents successfully imported to reconciliation key &2 | The short text describes the object sufficiently | |
127 | 300 | No unique entry in FKK_EBS_POI_SYST with combination &1/&2/&3/&4 | Space: object requires documentation | |
128 | 301 | Customizing for &1/&2/&3/&4 in FKK_EBS_POI_SYST is incomplete | Space: object requires documentation | |
129 | 302 | &1 is not a date variable | Space: object requires documentation | |
130 | 303 | A system exception occured while converting the IDoc &1 | Space: object requires documentation | |
131 | 304 | Incorrect IDoc: Segment &2 not intended for type &1 | Space: object requires documentation | |
132 | 305 | Inconsistency in conversion of IDoc &1 | Space: object requires documentation | |
133 | 306 | No correct customer function module entered for event 2410 | Space: object requires documentation | |
134 | 307 | An error occured while converting the data fields | Space: object requires documentation | |
135 | 308 | Field &1 exceeds the maximum length of &2 | Space: object requires documentation | |
136 | 309 | Account statement only possible if selection entity = VKONT | Space: object requires documentation | |
137 | 310 | Incorrect Customizing: &1 - &2 combination not allowed | Space: object requires documentation | |
138 | 311 | Problem in IST_TELNUM_FIND function module | Space: object requires documentation | |
139 | 312 | No selection conditions; all open items were selected | Space: object requires documentation | |
140 | 313 | Problem in FKK_MASS_OPEN_ITEM_SELECT_GET function module | Space: object requires documentation | |
141 | 314 | IDoc &1 was successfully processed | Space: object requires documentation | |
142 | 315 | At least one incorrect IDoc (no. &1) was created | Space: object requires documentation | |
143 | 316 | Selection conditions exist for two different entities | Space: object requires documentation | |
144 | 317 | Problem reading the Customizing information for the account statement | Space: object requires documentation | |
145 | 318 | At least one of the contract accounts does not exist | Space: object requires documentation | |
146 | 319 | Account statements were only requested for &1 out of &2 contract accounts | Space: object requires documentation | |
147 | 320 | No IDocs were created | Space: object requires documentation | |
148 | 321 | Problem checking the distribution model for message type &1 | Space: object requires documentation | |
149 | 322 | The distribution model for message type &1 is not maintained | Space: object requires documentation | |
150 | 323 | The TFKTVOT text table does not contain an entry for the &1/&2/&3/&4 key | Space: object requires documentation | |
151 | 324 | Incorrect settings in FKK_EBS_POI_SYST for &1/&2/&3/&4 | Space: object requires documentation | |
152 | 325 | The T_VKONT selection table is incorrectly filled | Space: object requires documentation | |
153 | 326 | Function module FKK_EBS_POI_SET_CORR_DATE was called in incorrect context | Space: object requires documentation | |
154 | 340 | Account statements can only be requested using CACCTs or BPARTs | Space: object requires documentation | |
155 | 341 | No selection conditions specified: T_SEL_ENT table is empty | The short text describes the object sufficiently | |
156 | 342 | There are already 100 IDs with &2 as body for the date &1 | Space: object requires documentation | |
157 | 350 | The IDoc for the master data output could not be created | Space: object requires documentation | |
158 | 400 | Problems occurred during creation of job for SUBMIT for FKJO_SCHEDULE | The short text describes the object sufficiently | |
159 | 401 | Problems occured while closing the job for submitting FKJO_SCHEDULE | The short text describes the object sufficiently | |
160 | 402 | FKJO_SCHEDULE exceeded maximum time: Job number &1, job name &2 | Space: object requires documentation | |
161 | 403 | FKJO_SCHEDULE was cancelled: Job number &1, job name &2 | Space: object requires documentation | |
162 | 404 | The job for executing FKJO_SCHEDULE was not started | Space: object requires documentation | |
163 | 405 | Error reading the job log for job no. &1, job name &2 | Space: object requires documentation | |
164 | 406 | A problem occured while reading the job status of job no. &1, job name &2 | Space: object requires documentation | |
165 | 407 | FKJO_SCHEDULE completed successfully; mass run is scheduled | Space: object requires documentation | |
166 | 408 | The job log for job no. &1, job name &2 is not in the expected format | The short text describes the object sufficiently | |
167 | 409 | Mass run created with IDs &1 and &2 | The short text describes the object sufficiently | |
168 | 410 | Jobs created with IDs &1 and &2 | The short text describes the object sufficiently | |
169 | 500 | The application is &1, not &2 | Space: object requires documentation | |
170 | 501 | This function is only planned for application &1 or &2 | Space: object requires documentation | |
171 | 502 | No tax on sales and purchases code exists for key &1 | The short text describes the object sufficiently | |
172 | 503 | No condition found for keys &1 and &2 | The short text describes the object sufficiently | |
173 | 504 | No tax code found for key &1 | The short text describes the object sufficiently | |
174 | 505 | No open items found with reference item &1 | The short text describes the object sufficiently |
History
Last changed on/by | 20130531 | SAP | |
SAP Release Created in |