FARR_MSG_CUSTOM - Customizable Messages for Revenue Accounting
 The following messages are stored in message class FARR_MSG_CUSTOM: Customizable Messages for Revenue Accounting.
It is part of development package FARR_FOUNDATION in software component FI-RA. This development package consists of objects that can be grouped under "Revenue Accounting: Reuse Objects".
 It is part of development package FARR_FOUNDATION in software component FI-RA. This development package consists of objects that can be grouped under "Revenue Accounting: Reuse Objects".
| Message Nr ▲ | Message Text | 
|---|---|
| 001 | Name of leading performance obligation &1 is missing | 
| 002 | Performance obligation type of performance obligation &1 is missing | 
| 003 | Not duration but end date is provided for time-based perf. oblig. &1 | 
| 004 | Start date is provided for time-based perf. oblig. &1 during creation | 
| 006 | Leading performance obligation &1 has no linked performance obligation | 
| 007 | Account provided for statistic condition type &1 of perf. oblig. &2 | 
| 008 | Total fulfilled qty. &1 is greater than total qty &2 of perf. oblig. &3 | 
| 010 | Leading perf. oblig. &1 of perf. oblig. &2 is not completely fulfilled | 
| 011 | Leading perf. oblig. &1 of perf. oblig. &2 not fully fulfilled (cont. &3) | 
| 012 | Contract &1 has multiple customer IDs | 
| 013 | This operation causes target contract to contain multiple customer IDs | 
| 014 | The standalone selling price of performance obligation &1 is zero | 
| 015 | Contract &1 has multiple business partners | 
| 016 | For contract &1 no unique receivable adjust. account can be determined | 
| 017 | FI posting period &2 for company code &1 is closed | 
| 018 | For contract &1 no unique refund liability account can be determined | 
| 019 | Customer &1 of perf. oblig. &2 is not created in company code &3 | 
| 020 | Multiple perf. oblig. are marked as residual in the same group (incl. &1) | 
| 021 | For contract &1 no unique refund asset account can be determined | 
| 022 | All transaction prices in contract &1 must have the same sign. | 
| 023 | Acct. assignments of acct. &1 are re-derived: &2 is changed from &3 to &4 | 
| 024 | The trans. amount (trans. currency &2) of POB &1 (condi. &3) cannot be 0. | 
| 025 | The amount of POB &1 (condition &4) in local currency &2 &3 cannot be 0. | 
| 026 | Perf. obl. &1's invoice amount must not exceed its contractual price | 
| 027 | Perf. obl. &1's invoice amount must be equal to its contractual price. | 
| 028 | Perf. Obl. &1's invoice quantity must not exceed its total quantity | 
| 029 | Perf. obl. &1's invoice quantity must be equal to its total quantity | 
| 030 | Condition type &1 does not exist in deferal items | 
| 031 | Performance obligation &1 has no deferral items | 
| 032 | CO object numbers in use. Include Header ID &1, contract &2 at cleanup. | 
| 033 | Local curr. &1 and &2 must have same amount for Cond. &3 of Perf. Obl. &4 | 
| 034 | It is not allowed to change price from &1 to &2 for POB &3 Cond. Type &4 | 
| 035 | Time-based performance obligation &1 cannot have open revenue | 
| 036 | Can't delete POB &1; Compound POB &2 must have more than 1 low level POB | 
| 037 | Compound POB &1 has only one non-distinct, lower-level POB | 
| 038 | Alloc. BAdI: Alloc. amt of PerOb. (not excl. from alloc) has differ. sign | 
| 039 | Time-based performance obligation &1 cannot have fulfillment RAI | 
| 040 | It's not possible to create manual Performance Obligations | 
| 041 | Event date of manual fulfillment for POB &1 can't be in future period. | 
| 042 | Transaction price of perf. oblig. &1 cannot change from pos. to neg. | 
| 043 | Transaction price of perf. oblig. &1 cannot change from neg. to pos. | 
| 044 | Account &1 not valid; recognized revenue account must be a P/L account | 
| 092 | POB &1: Total invoiced amount cannot be negative. | 
| 093 | POB &1: Total invoiced amount cannot be positive. | 
| 158 | Fulfillment of POB &1: Total fulfilled amount cannot be negative. | 
| 343 | Amount in local currency &2 must not be zero for item ID &1 | 
| 500 | ************************* Consistency Check ************************* | 
| 501 | Item &1: Revenue accounting item error reported for status &2. | 
| 502 | Item &1: Attribute value differs for the item. | 
| 503 | Item &4: Field &1-Integration component: &2; Revenue Accounting: &3. | 
| 504 | Item &2: Attribute value differs for condition type &1. | 
| 505 | Item &2: Condition type &1 wasn't deleted. | 
| 506 | Item &2: Condition type &1 wasn't created. | 
| 507 | Item &1: The item status is Processable. Process the item. | 
| 508 | Item &1: The item status is Raw. Transfer the item. | 
| 509 | Item &1: The item wasn't transferred from the integration component. | 
| 510 | Item &1: For status &2, the item was deleted and its RAI isn't marked. | 
| 511 | Item &1: For status &2, the item was deleted and its RAI is marked. | 
| 512 | ContAcqui cost can't be processed; Cost recog not defined for AcctPri &1. | 
| 513 | ContAcqui cost can't be processed; Cost recog not defined for POB &1. | 
| 514 | Time-based POB &1 has 0 revenue but it starts before transfer date. | 
| 515 | Fulfilled quantity of perf. obl. &1 must be 0 if its migrated rev. is 0 | 
| 516 | Loc.curr. &1 and trans.curr. must have same amount for POB &2(Cond. &3) | 
| 517 | Cannot edit spreading for periods where postings occurred (POB &1) | 
| 518 | erf. obl. &1 that has been 100% fulfilled cannot have open revenue | 
| 519 | Duration of time-based POB &1 is greater than &2 years. | 
| 800 | ************************* Adapter Reuse Layer *********************** | 
| 835 | Obsolete revenue accounting item &1 &2 deleted | 
| 836 | Item &1: The quantity unit in fulfillment differs from the orig. item | 
| 837 | Item &1: The quantity unit in invoice does not match with the orig. item | 
| 855 | Item &1: quantity neither sent nor determined correctly via rules. |