FKK_COLLHIST - Nachrichtenklasse der Collection Historie
The following messages are stored in message class FKK_COLLHIST: Nachrichtenklasse der Collection Historie.
It is part of development package FKK_CM in software component FI-CA. This development package consists of objects that can be grouped under "FI-CA: Collections Management".
It is part of development package FKK_CM in software component FI-CA. This development package consists of objects that can be grouped under "FI-CA: Collections Management".
Message Nr ▲ | Message Text |
---|---|
000 | *** Messages for Configuration of Collection History *** |
001 | Event &1 does not deliver a history |
002 | Selection option &1 not allowed here |
003 | Variant not filled |
004 | Variant &1 does not exist |
005 | Neither event &1 nor event category &2 have a text |
006 | Customizing of variant &1 is not valid |
007 | Event not filled |
008 | Event &1 does not exist |
009 | No standard variant defined in Customizing |
010 | No events defined for variant & |
011 | No event category maintained for event &1 |
012 | No reporter class maintained for event &1 |
013 | Event &1: Unable to instantiate reporter class &2 |
014 | Event &1: Reporter &2 delivers no report due to performance reasons |
050 | *** Messages of Collection History application *** |
051 | From Date must not be after the To Date |
052 | Enter at least one master data selection |
053 | No result for at least one event due to performance reasons |
054 | Select an entry in the collection history |
055 | More than &1 entries selected |
100 | *** Messages of abstract reporter class *** |
101 | Reporter was unable to process any available contexts |
102 | Document &1, item &2, due on &3 |
103 | Document &1, item &2 |
104 | Items &1/&2/&3/&4 not found |
150 | *** Messages for example reporter *** |
151 | This is an example header entry |
152 | This is an example detail entry with parameters &1 &2 &3 &4 |
153 | This is an example warning with parameter &1 |
154 | This is an example error message with parameter &1 |
175 | *** Messages for dunning *** |
176 | &1, &2, business partner &3, contract account &4 |
178 | Dunning header &1 has no dunning procedure or collection strategy |
180 | &1 |
181 | Dunning activity has no technical key or name |
182 | Dunning reductions exist for the dunning group |
183 | &1, &2, business partner &3, account group &4 |
184 | &1, &2, business partner &3, contract group &4 |
185 | Success of the dunning was valuated with &2% on &1 |
186 | Dunning run &1/&2 |
200 | *** Messages for correspondence *** |
201 | &1 created for business partner &2, contract account &3 |
202 | Correspondence of type &1 created for business partner &2, account &3 |
225 | *** Messages for work items *** |
226 | &1 for business partner &2, contract account group &3, status &4 |
227 | &1 for business partner &2, contract group &3, status &4 |
228 | Work item contains items subsequently added |
229 | Result code &1, collection specialist &2, department &3 |
230 | Collection specialist &1, department &2 |
231 | Work item already contains inactive items |
250 | *** Messages for payments *** |
251 | Clearing by &1 &2 |
252 | Clearing by payment with reason &1, document number &2 |
253 | Clearing of document &1, item &2, |
275 | *** Messages for promises to pay (P2P) *** |
276 | Business partner &1, reason: &2 |
277 | &1, level of fulfillment: &2% |
278 | &1, promised amount: &2 &3 |
279 | &1 |
280 | Reason: &1 |
300 | *** Messages for installment plans *** |
301 | Installment plan &1 created with start date &2 for partner &3, account &4 |
302 | Deactivated on &1 |
400 | Number of generated unlocking requests: &1 |
401 | Number of unlocking requests not generated: &1 |
402 | Number of reversed unlocking requests: &1 |