/PM0/ABP_TMF_MSG - Nachrichtenklasse der Zeitmodellfunktionen Basis

The following messages are stored in message class /PM0/ABP_TMF_MSG: Nachrichtenklasse der Zeitmodellfunktionen Basis.
 It is part of development package /PM0/ABP_BTX_CROSS in software component FS-PM. This development package consists of objects that can be grouped under "FS-PM Basis: BTX-API: General Objects".
Message Nr ▲
Message Text
001&1 / Eff.date &3: Investment stop; contract-relevant update not possible
002Contract &1: Building structure insurance expires
003Contract &1: Error in PM call
004&1: End on &2; further updating not possible
005Contract &1: &2
006&1 / Eff. Date &4: Error executing &2 (date &3)
010&1: Scheduling of date &2 &3 not possible on &4
011&1 / Eff.date &3: Date &2 is not permitted and has been deleted
020&1/ Eff Date &3: For date &2, an exception (category &4) has occurred
021&1: Cannot continue positioning for date &2
022&1/ Eff Date &3: Positioning for date &2 has been stopped (exception &4)
023&1: Eff.date &3: Positioning skips date &2 (exception &4)
024&1 / EffDate &3: Positioning after date '&2' stopped (event &4)
025&1: Scheduling &2 for &3 not possible; TMF would interrupt interval
026&1: Scheduling &2 to &3 not possible; TMF would interrupt interval of &4
027&1: Scheduling &2 to &3 not possible; effective date &4 already reached
028&1: Scheduling &2 to &3 not possible; external or correspondence date
029&1: &2 should be scheduled by &3; cycle
030&1: No date defined for "dependency resolution" date category
031&1: Scheduling &2 for &3 not possible. Conflict with scheduled BTS date
032&1: BTrans "Renewal Decision" was not yet executed
033&1 / Effective date &3: Positioning after date '&2' was stopped
034&1: BTrans "Renewal Preparation" not yet executed
035&1: Loaded version for new contract is too high
036&1: Scheduling &2 for &3 is not possible
037&1 / EffDate &3: Date &2: Payment request sent for actual investment
039&1 / Effective date &3 / &2: Update stop due to unloaded contracts
040&1: Eff. date &3: Error for date &2: Claim must be closed
041&1: Eff. date &3: Error for date &2: Calculation bases are not available
042&1: Eff. date &3: Error for date &2: Tax records are not available
043&1: Eff. date &3: Error for date &2: Error in insurance mathematics
044&1: Eff. date &3: Error for date &2: Investment stop is set
045&1: Eff.date &3:Err.for date &2: Follow-up date cannot be uniquely ident.
046&1: Eff.date &3: Error for date &2: Policy date cannot be executed
047&1: Eff. date &3: Error for date &2: BTS date processing contains errors
048&1: Eff. date &3: Error for date &2: Release date &4 not reached
049&1 / Eff.dt &3: Error for date &2: Adjustment rejection has errors
050&1 /Eff.dt &3: Error with date &2: Extension not possible
051&1: Eff.date &3: Error for date &2: BTS date cannot be executed via TM
052&1: Eff.date &3: Error with date &2: Postdated business process
053&1 / Effective date &3: Error in date &2: No reimplementation possible
054&1 / Eff.Date &3: Error with date &2: Provisional BTS date
055&1 / EffDate &3: Date &2: Postdated contract creation cannot be resolved
060Incomplete key: Policy ID = &1, contract ID = &2
070Implementation of enhancement spot &1 &2 is not unique
071Enhancement spot &1 &2 for &3 not implemented
088Policy &1: Call of P&C adapter method &2
089Parameters: BusProcess &1, BusTrans &2, Date &3, Postdated &4
090&1: Cash value cannot be determined for previous highest version &2
091&1/Effective date &3: Error in BTS date &2; related obj.does not exist
092&1: Request for renewal has not yet been sent
093Time model function can be executed in policy mode only
Privacy Policy