SAP ABAP Message Class FVD_INV_ACC (Message Class for Investor Contract)
Basic Data
Hierarchy
☛
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
⤷ FS-CML-NB (Application Component) New business
⤷ FVVD_INVESTOR_ACCOUNT (Package) Investor Acount
⤷ FS-CML-NB (Application Component) New business
⤷ FVVD_INVESTOR_ACCOUNT (Package) Investor Acount
Attributes
Message class | FVD_INV_ACC | |
Short Description | Message Class for Investor Contract | |
Changed On | 20110810 | |
Last Changed At | 072751 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | *** General / Method Messages ******************************************* | The short text describes the object sufficiently | |
2 | 001 | Company code or contract number not provided | The short text describes the object sufficiently | |
3 | 002 | Function not permitted for product category investor contract | The short text describes the object sufficiently | |
4 | 003 | Transfer parameters contradictory: &1 &2 | The short text describes the object sufficiently | |
5 | 008 | &1 could not be posted | Space: object requires documentation | |
6 | 009 | *** Contract Creation *************************************************** | The short text describes the object sufficiently | |
7 | 010 | Product type &1 is invalid for investor contract | The short text describes the object sufficiently | |
8 | 011 | Product category &1 is not an investor contract | The short text describes the object sufficiently | |
9 | 012 | Conditions have been provided for product type &1; no conditions required | The short text describes the object sufficiently | |
10 | 013 | No flows have been provided for product type &1; Conditions not required | The short text describes the object sufficiently | |
11 | 014 | Flows have been provided for product type &1; Conditions required | The short text describes the object sufficiently | |
12 | 015 | No conditions have been provided for product type &1; Conditions required | The short text describes the object sufficiently | |
13 | 030 | *** Contract Change ***************************************************** | The short text describes the object sufficiently | |
14 | 031 | Missing contract lock, set a contract lock | Space: object requires documentation | |
15 | 032 | Contract lock has been reset | The short text describes the object sufficiently | |
16 | 034 | Main contract partner cannot be changed, partner: &1 -> &2 | The short text describes the object sufficiently | |
17 | 035 | Incoming payment posted, change &1 not permitted, old value: &2 new: &3 | The short text describes the object sufficiently | |
18 | 039 | Posting date for balance sheet transfer missing | The short text describes the object sufficiently | |
19 | 049 | Status change is currently not supported | The short text describes the object sufficiently | |
20 | 050 | *** Conditions/Flow Data ************************************************ | The short text describes the object sufficiently | |
21 | 051 | &1 Condition &2 flow category &3 not permitted for investor contract | The short text describes the object sufficiently | |
22 | 055 | Planned record with due date &1 falls in posted period | The short text describes the object sufficiently | |
23 | 056 | Planned record with due date &1 affects the capital amounts | The short text describes the object sufficiently | |
24 | 057 | Planned record with due date &2 affects accrual/deferral | The short text describes the object sufficiently | |
25 | 058 | Due date for planned record must be provided | The short text describes the object sufficiently | |
26 | 059 | Calculation date for planned record must be provided | The short text describes the object sufficiently | |
27 | 060 | Planned record due date &1 is after end of term &2 | The short text describes the object sufficiently | |
28 | 061 | Planned record calculation date &1 is after end of term &2 | The short text describes the object sufficiently | |
29 | 062 | Planned record due date &1 is before start of term &2 | The short text describes the object sufficiently | |
30 | 063 | Planned record calculation data &1 is before start of term &2 | The short text describes the object sufficiently | |
31 | 064 | Double planned records exist (flow type &1 and calculation date &2) | The short text describes the object sufficiently | |
32 | 065 | Inconsistencies in new planned records | The short text describes the object sufficiently | |
33 | 066 | Exchange rate flows added to planned records due to rounding differences | The short text describes the object sufficiently | |
34 | 100 | *** Performance Problems ************************************************ | The short text describes the object sufficiently | |
35 | 101 | No flows maintained for application subfunction &1 (table &2) | The short text describes the object sufficiently | |
36 | 102 | Only 1 entry permitted cond. group &1 app. subfunction &2 table &3 | The short text describes the object sufficiently | |
37 | 103 | Assign exactly one flow to condition group &1 and appl. subfunction &2 | Not yet documented | |
38 | 104 | Enter a valid date for key date &1 | The short text describes the object sufficiently | |
39 | 105 | No alternative payer &2 exists as customer for loan &1 | The short text describes the object sufficiently | |
40 | 106 | Key date for payoff &1 is not the same as due date for payoff &2 | The short text describes the object sufficiently | |
41 | 107 | Payoff amount must be copied to field &1 parameter &2 | The short text describes the object sufficiently | |
42 | 108 | No entry in field &1 in full payoff parameter &2 | The short text describes the object sufficiently | |
43 | 109 | Field &1 of parameter &2 contains empty or invalid input value &3 | The short text describes the object sufficiently | |
44 | 110 | Condition header for company code &1 and loan &2 were not found | The short text describes the object sufficiently | |
45 | 111 | No partner data exists for date of payoff &2 for loan &1 | The short text describes the object sufficiently | |
46 | 112 | Flow type &1 for application subfunction &2 not permitted (table &3) | The short text describes the object sufficiently | |
47 | 113 | Error in the interface &1 &2 | The short text describes the object sufficiently | |
48 | 114 | &1 &2: enter at least &3 and &4 | The short text describes the object sufficiently | |
49 | 115 | An amount must be transferred field &1 parameter &2 | The short text describes the object sufficiently | |
50 | 116 | Parameter &1 contains invalid flow type &2 | The short text describes the object sufficiently | |
51 | 117 | &1 &2 contains no values, end of fixed int. per. or remaining cap. exists | The short text describes the object sufficiently | |
52 | 118 | New planned records have not been completed | The short text describes the object sufficiently | |
53 | 119 | Cannot assign &1 to &2 &3 | The short text describes the object sufficiently | |
54 | 120 | No new planned records are permitted in import table &1 | The short text describes the object sufficiently | |
55 | 121 | Due date for new planned record &1 must be after key date payoff &2 | The short text describes the object sufficiently | |
56 | 122 | Due date charge &1 is different than due date of payoff from &2 | The short text describes the object sufficiently | |
57 | 123 | Missing import parameter &1 for call &2 flow-based investor contract | The short text describes the object sufficiently | |
58 | 124 | Payment method must be transferred field &1 parameter &2 | The short text describes the object sufficiently | |
59 | 125 | No entries found in table &1 for product category investor contract | The short text describes the object sufficiently | |
60 | 126 | Assignment of text to &1 &2 not possible | The short text describes the object sufficiently | |
61 | 127 | Assignment of defaults to &1 &2 not possible | The short text describes the object sufficiently | |
62 | 128 | Parameter &1 to &2 is initial/does not correspond to prod.type invst.ctrt | The short text describes the object sufficiently | |
63 | 129 | Status of contract for company code &1 and product type &2 not found | The short text describes the object sufficiently | |
64 | 130 | Parameter & must be transferred | The short text describes the object sufficiently | |
65 | 131 | No entries permitted for parameter & | The short text describes the object sufficiently | |
66 | 132 | Entries in form field &1: 'I' | The short text describes the object sufficiently | |
67 | 133 | Product Type &1 does not belong to Investor Contract | The short text describes the object sufficiently | |
68 | 134 | Outgoing payment method must be transferred field &1 parameter &2 | The short text describes the object sufficiently | |
69 | 135 | Simulation of payoff was & | The short text describes the object sufficiently | |
70 | 136 | Payoff posted successfully | The short text describes the object sufficiently | |
71 | 137 | Payment method for payoff &1 and payment method charges &2 not identical | The short text describes the object sufficiently | |
72 | 138 | Repayment type &1 changed to &2, since the loan contract is flow based | The short text describes the object sufficiently | |
73 | 139 | No entries found in table &1 for &2 | The short text describes the object sufficiently | |
74 | 147 | Planned records result in negative remaining capital (overpayment) | The short text describes the object sufficiently | |
75 | 148 | Conditions result in negative remaining capital (overpayment) | The short text describes the object sufficiently | |
76 | 149 | No flows for posting have been transferred | The short text describes the object sufficiently | |
77 | 150 | Field &1 with value &2 has been changed to &3 | The short text describes the object sufficiently | |
78 | 200 | ***Reversal************************************************************** | The short text describes the object sufficiently | |
79 | 201 | When posting (without simulation) an open item for document &1 is created | The short text describes the object sufficiently | |
80 | 300 | *** Payment upon Request ************************************************ | The short text describes the object sufficiently | |
81 | 301 | Payment amount & must be greater than 0 | The short text describes the object sufficiently | |
82 | 302 | No open items exist | The short text describes the object sufficiently | |
83 | 303 | Open items & & smaller than payment amount & & are not permitted | The short text describes the object sufficiently | |
84 | 304 | Split exec. for open itm & post. ind. & using &. & were released for pymt | The short text describes the object sufficiently | |
85 | 305 | Pymt lock removed for open item & post. ind. &. & were released for pymt | The short text describes the object sufficiently | |
86 | 306 | No authorization for Payment upon Request function (OBJ FD_IA_ZANF) | The short text describes the object sufficiently | |
87 | 307 | Enter a currency & | The short text describes the object sufficiently | |
88 | 308 | Error Customizing investor contract: maintain evaluation criteria | The short text describes the object sufficiently | |
89 | 311 | Document does not exist &1 &2 &3 | The short text describes the object sufficiently | |
90 | 352 | You cannot process parked document &1; Document has been deleted | The short text describes the object sufficiently | |
91 | 500 | No loan data for loan &1 company code &2 | The short text describes the object sufficiently | |
92 | 501 | Set either full payoff or repayment change type for partial payoff | The short text describes the object sufficiently | |
93 | 502 | Error calling condition- or flow-based contract product type &1 | The short text describes the object sufficiently | |
94 | 503 | File upload of &1 not possible | The short text describes the object sufficiently | |
95 | 504 | Generation of planned records table for flow-based contracts failed | The short text describes the object sufficiently | |
96 | 505 | Enter values in tab Payoff | The short text describes the object sufficiently | |
97 | 601 | Incoming payment not simulated or transferred | The short text describes the object sufficiently | |
98 | 602 | Business Partner &1 has not been assigned to contract &2 | The short text describes the object sufficiently | |
99 | 715 | Remaining capital &1 at end of new fixing | The short text describes the object sufficiently |
History
Last changed on/by | 20110810 | SAP | |
SAP Release Created in | 600 |