FARR_PROCESS_CHECK - Messages for Input Checks in Process Layer
The following messages are stored in message class FARR_PROCESS_CHECK: Messages for Input Checks in Process Layer.
It is part of development package FARR_CONTRACT_SERVICE in software component FI-RA. This development package consists of objects that can be grouped under "Processes and Services for the RAR Contract".
It is part of development package FARR_CONTRACT_SERVICE in software component FI-RA. This development package consists of objects that can be grouped under "Processes and Services for the RAR Contract".
Message Nr ▲ | Message Text |
|---|---|
| 001 | POB &1 has start date type '3', or a duration. This is not supported |
| 002 | POB &1 has time-based attributes but is not a time-based POB |
| 003 | POB &1 has a duration but no duration unit |
| 004 | Perf. oblig. &1 has company code &2 instead of &3 |
| 005 | Cost currency used in contract &1 must not deviate from currency &3 |
| 006 | At least one condition for contract &1 has empty currency code |
| 007 | Currency code &2 specified for contract &1 does not exist |
| 008 | Deferral method missing for time-based POB &1 |
| 009 | Not authorized to create contracts for comp. code &1 |
| 010 | Not authorized to change contracts for comp. code &1 |
| 011 | Performance obligation &1 has bill of material. This is not supported |
| 012 | Performance obligation &1 has a hierarchy. This is not supported |
| 013 | Performance obligation &1 has a right of return. This is not supported |
| 014 | Performance obligation &1 has simplified invoice. This is not supported |
| 015 | POB &1 is value-relevant with certain attributes. This is not supported |
| 016 | POB &1 has the event date as a start date but no duration |
| 017 | POB &1 is relevant for results analysis. This is not supported |
| 018 | Performance obligation &1 has POC fulfillment type. This is not supported |
| 019 | Man. fulfillment of POB &1: The provided fulfillment type &2 is invalid |
| 020 | Perf. oblig. &1 is a POB for contract acquisition cost. Not supported |
| 021 | Perf. oblig. &1 has a finalization date. This is not supported |
| 022 | The effective date of POB &1 must be the same for all POBs |
| 023 | Main price condition missing for performance obligation &1 |
| 024 | Main price condition of perf. oblig. &1 must not be statistic |
| 025 | Linked performance obligation &1 must not have a price condition type |
| 026 | Contract &1 is loaded from legacy data. This is not supported |
| 027 | Processing of initial load fulfillment items is not supported |
| 028 | Performance obligation &1 is not a distinct POB. This is not supported |
| 029 | Contr. early termination must be sent for all POBs. POB&1 is inconsistent |
| 030 | POB &1 has a duration. This is only supported with start date type '3'. |
| 031 | Fulfillment item for POB &1 has event type &2. This is not supported |
| 032 | Creating POB &1 is not supported as RAIs are terminated early |
| 033 | POB &1 is a linked POB, but not time-based. This is not supported |
| 034 | Time-based performance obligation &1 has a start date but no end date |
| 035 | Condition type &2 of POB &1 is deleted and created at the same time |
| 036 | Condition type &2 of POB &1 is deleted and changed at the same time |
| 037 | POB &1 has event type &3. This is not supported |
| 038 | Deleting POB &1 is not supported as RAIs are terminated early |
| 039 | Provide a freeze date for the performance obligation &1 |
| 040 | Unfreeze date cannot be earlier than or equal to a corresp. freeze date |
| 041 | Unfreeze date must be earlier than a new performance obligation end date |
| 042 | POB &1 has start date type '3', but Duration or Duration Unit are missing |
| 043 | Man. fulfillment of POB &1: Percentage to be fulfilled cannot exceed 100% |
| 044 | Man. fulfillment of POB &1: Percentage to be fulfilled cannot be negative |
| 045 | Man. fulfillment of POB &1: Quantity unit must be a percentage |
| 046 | A single manual fulfillment item is expected for the perf. oblig. &1 |
| 047 | You are not authorized to manually fulfill performance obligations |
| 048 | Provide an unfreeze date for the performance obligation &1 |
| 049 | POB &1: Freeze Periods must not overlap &2 &3 |
| 050 | Required field "Quantity" of fulfillment item of POB &1 is empty |
| 051 | Required field "Quantity unit" of fulfillment item of POB &1 is empty |
| 052 | Required field "Fulfillment Date" of fulfillment item of POB &1 is empty |
| 053 | Early termination of POB &1 not supported for Contract Management Classic |
| 054 | Quantity Unit &2 of fulfillment item for POB &1 has invalid value |
| 055 | Early termination is not supported: POB &1 |
| 056 | POB &1: Event type of POB doesn�t support value-based fulfillments |
| 057 | Contract &1 is specified more than once for contract combination |
| 058 | Contract &1 was created with Classic RAR. Combination not supported |
| 059 | Combining contracts &2 and &3 with future effect. Date &1 not supported |
| 060 | POB &1 Value Based Fulf. not supported for invoice effective type &2 |
| 061 | Linked performance obligation &1 must not have a cost condition type |
| 062 | Main cost condition type missing for performance obligation &1 |
| 063 | Negative performance obligation &1 must have SSP set to zero |
| 064 | Negative perf. oblig. &1 must not be marked as excluded from allocation |
| 065 | Negative perf. oblig. &1 must not be marked as residual allocation |
| 066 | Quantity and Delivered_qty_diff of fulfillment item of POB &1 are empty |
| 067 | POB &1: Finalization date earlier than start date. This is not supported |
| 068 | Performance obligation &1 for cost of acquisition cannot have linked POBs |
| 069 | Performance obligation &1 for cost of acquisition must be distinct |
| 070 | Acquisition cost POB &1 must have start date type "Available at creation" |
| 071 | Performance obligation &1 for cost of acquisition must be time-based |
| 072 | Value-based fulfillment is not supported for non-distinct POB &1 |
| 073 | Exclude from allocation is not supported for non-distinct POB &1 |
| 074 | Residual allocation is not supported for non-distinct POB &1 |
| 075 | Non-distinct POB &1 cannot be a leading or linked POB |
| 076 | Compound group POB &1 must have fulfillment type PoC or time-based |
| 077 | POB &1: Event type of POB doesn�t support cost recognition. |
| 078 | Manual changes to non-distinct POB &1 are not supported |
| 079 | POB &1: fulfillments with Event Type 'CP' are not supported |
| 080 | Non-distinct POB &1 in PoC compound group must be PoC or event-based |
| 081 | Non-distinct POB &1 in time-based compound group: must be time-based |
| 082 | Leading POB &1 cannot be added to compound group |
| 083 | Compound group POB &1 contains less than two non-distinct POBs |
| 084 | Compound group POB &1 cannot be a leading or linked POB |
| 085 | Compound group POB &1 cannot have a higher-level POB |
| 086 | POB &1 has unsupported duration unit &2 |
| 087 | Billing element performance obligation &1: Attribute &2 must be empty |
| 088 | Performance obligation &1 must have a fulfillment type |
| 089 | Billing element perf. oblig. &1 is a leading POB. This is not supported. |
| 090 | Billing element performance obligation &1 must be distinct |
| 091 | Billing element POB &1 must have fulfillment type "No fulfillment" |
| 092 | Billing element POB &1 cannot have fulfillments based on values |
| 093 | Contract &1 has billing element but no standard POBs. This is not allowed |
| 094 | Billing element performance obligation &1 must contain the ID of a &2. |
| 095 | POB &1: Event type of POB doesn�t support start date type '3'. |
| 096 | POB &1: Start date type 3 only supports distinct POBs |
| 097 | POB &1: No account found for impairment of cost. |
| 098 | Combination of contracts &1 and &2 not supported: different IP versions. |
| 099 | POB &1: Start date type 3 only supports standard POB with POB category '' |
| 100 | Inconsistent RAI class in mapping entries for contract &1. |
| 101 | Mapping data missing for contract &1. Combination not possible. |
| 102 | Mapping data missing for all contracts. Combination not possible. |
| 103 | Contract &1 could not be loaded completely |