SAP ABAP Message Class RETMPE (Clauses for Validity Period)
Basic Data
Hierarchy
☛
EA-FIN (Software Component) EA-FIN
⤷
RE-FX-CN (Application Component) Real Estate Contract
⤷
RE_TM_PE (Package) RE: Terms - Period (Terms for Term)
⤷
⤷
Attributes
| Message class | RETMPE | |
| Short Description | Clauses for Validity Period | |
| Changed On | 20100310 | |
| Last Changed At | 200337 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Activity is not available for rule type &1 | Space: object requires documentation | ||
| 2 | Notice rule &1 does not exist | Space: object requires documentation | ||
| 3 | Notice rule &1 does not belong to rule type &2 | Space: object requires documentation | ||
| 4 | Notice rule &1: party giving notice not specified | Space: object requires documentation | ||
| 5 | Notice rule &1: Cancellation party &2 is not allowed | Space: object requires documentation | ||
| 6 | Notice rule &1: definition does not exist | Space: object requires documentation | ||
| 7 | Notice rule &1: there is no default entry for validity | Space: object requires documentation | ||
| 8 | Notice rule &1 / &2: Further default entry not permitted | Space: object requires documentation | ||
| 9 | Notice rule &1 / &2: Validity date already exists | Space: object requires documentation | ||
| 10 | Notice rule &1 / &2: Validity is within range of preceding entry | Space: object requires documentation | ||
| 11 | Notice rule &1 / &2: You must make an entry in the 'Notice per' field | Space: object requires documentation | ||
| 12 | Notice rule &1 / &2: Entry &3 is not permitted in the 'Notice per' field | Space: object requires documentation | ||
| 13 | Notice rule &1 / &2: You must enter the type of grace days | Space: object requires documentation | ||
| 14 | Notice rule &1 / &2: You must enter the calendar for grace days | Space: object requires documentation | ||
| 15 | Notice rule &1 / &2: Type of grace days &3 is not permitted | Space: object requires documentation | ||
| 16 | Notice rule &1 / &2: Calendar &3 does not exist | Space: object requires documentation | ||
| 17 | Notice rule &1/&2: month &3 and day &4 do not result in a valid date | Space: object requires documentation | ||
| 18 | Notice rule &1/&2: month &3 does not result in a valid date | Space: object requires documentation | ||
| 19 | Notice rule &1/&2: day &3 does not result in a valid date | Space: object requires documentation | ||
| 20 | Notice rule &1/&2: for one-time notice, enter 'Term To' | Space: object requires documentation | ||
| 21 | Notice rule &1/&2: entering a period of notice does not make sense | Space: object requires documentation | ||
| 22 | Notice rule &1/&2: use 'No Notice Possible' only on individual basis | Space: object requires documentation | ||
| 23 | Notice rule &1/&2: relative year not allowed for receipt of notice | The short text describes the object sufficiently | ||
| 24 | Notice rule &1/&2: enter year of the notice date | The short text describes the object sufficiently | ||
| 25 | Notice rule &1/&2: enter year notice received | The short text describes the object sufficiently | ||
| 26 | Notice rule &1/&2: date notice was recieved is after notice date | The short text describes the object sufficiently | ||
| 27 | Text module &1 assigned in Customizing is empty | Space: object requires documentation | ||
| 28 | No text module was assigned to notice procedure &1 | Space: object requires documentation | ||
| 29 | Enter a text module name first. | Space: object requires documentation | ||
| 30 | Enter a notice procedure | Space: object requires documentation | ||
| 31 | Notice rule contains no entries for periods or dates | Space: object requires documentation | ||
| 32 | No errors found in cancellation procedure &1 | Space: object requires documentation | ||
| 33 | Error in definition of cancellation procedure &1 | Space: object requires documentation | ||
| 34 | Errors in definition of notice rule &1 | Space: object requires documentation | ||
| 35 | Notice term has to be defined as contract term | Space: object requires documentation | ||
| 36 | Simulation not possible, notice procedure contains errors | Space: object requires documentation | ||
| 37 | Simulation not possible, notice rule contains errors | Space: object requires documentation | ||
| 38 | Rule type &1 is not defined | Space: object requires documentation | ||
| 39 | Notice procedure &1 does not contain a notice rule | Space: object requires documentation | ||
| 40 | The individual notice procedure does not contain a notice rule | Space: object requires documentation | ||
| 41 | The notice procedure does not contain a rule for the contractee | Space: object requires documentation | ||
| 42 | The notice procedure does not contain a rule for the contractor | Space: object requires documentation | ||
| 43 | No period of notice was agreed; notice can be given at any time | Space: object requires documentation | ||
| 44 | Fast entry mode not possible, period regulation is too complex | The short text describes the object sufficiently | ||
| 45 | Fast entry mode not possible, deadline regulation is too complex | The short text describes the object sufficiently | ||
| 46 | Not possible to simulate giving notice for contract end in Customizing | Space: object requires documentation | ||
| 47 | Notice term of objects: term number is missing | Space: object requires documentation | ||
| 48 | Notice term of objects: term number &1 does not exist | Space: object requires documentation | ||
| 49 | No renewal rule was entered | Space: object requires documentation | ||
| 50 | You did not assign a text module to the renewal rule | Space: object requires documentation | ||
| 51 | Text module &1 assigned in Customizing is empty | Space: object requires documentation | ||
| 52 | Enter the '1st Contract End' in the term section | Space: object requires documentation | ||
| 53 | Renewal rule &1 does not contain any extension period | Space: object requires documentation | ||
| 54 | Individual renewal rule does not contain any extension periods | Space: object requires documentation | ||
| 55 | Repeating renewal rule contains an option as last element | Space: object requires documentation | ||
| 56 | Number of years, months, or days at which renewal occurs is not entered | Space: object requires documentation | ||
| 57 | The extension period entered consists only of &1 day(s) | Space: object requires documentation | ||
| 58 | Enter notice period for the option | Space: object requires documentation | ||
| 59 | Simulation is not possible, the renewal rule contains errors | Space: object requires documentation | ||
| 60 | Extension period is less than 1 month, rounding not possible | Space: object requires documentation | ||
| 61 | Notification period is less than 1 month, rounding is not possible | Space: object requires documentation | ||
| 62 | Renewal term has to be defined as contract term | Space: object requires documentation | ||
| 63 | Messages for renewal terms | Space: object requires documentation | ||
| 64 | There is no renewal term | Space: object requires documentation | ||
| 65 | Renewal term of objects: term number missing | The short text describes the object sufficiently | ||
| 66 | Renewal term of objects: term number &1 does not exist | The short text describes the object sufficiently | ||
| 67 | Enter the notice period for the automatic renewal | The short text describes the object sufficiently | ||
| 68 | Deletion not possible because activated option(s) exist | Space: object requires documentation | ||
| 69 | Renewal rule contains no options, but there are activated options | The short text describes the object sufficiently | ||
| 70 | Options were changed despite already activated options | The short text describes the object sufficiently | ||
| 71 | Starting date of cash flow is before the contract start date | Space: object requires documentation | ||
| 72 | Starting date of cash flow is after the end of the contract term | Space: object requires documentation | ||
| 73 | The 1st contract end is before the contract start date | Space: object requires documentation | ||
| 74 | End of the contract term is before the contract start date | Space: object requires documentation | ||
| 75 | Starting date of cash flow (&1) is before default date (&2) | Space: object requires documentation | ||
| 76 | The first contract end date on &1 is not allowed | Space: object requires documentation | ||
| 77 | Date of 1st posting is not in interval from &1 to &2 | The short text describes the object sufficiently | ||
| 78 | Date entries for possession dates are inconsistent | Space: object requires documentation | ||
| 79 | 'Cash Flow From' date &1 is before earliest 'Possession Date From' &2 | The short text describes the object sufficiently | ||
| 80 | 'Cash Flow From' date &1 is after latest 'Possession Date To' &2 | The short text describes the object sufficiently | ||
| 81 | A term of more than 9999 months is not useful | The short text describes the object sufficiently |
History
| Last changed on/by | 20100310 | SAP | |
| SAP Release Created in | 110 |