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)
Basic Data
| Data Element | RETMNTPROCTDNAME |
| Short Description | Text Module for Description of Notice Procedure |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TDOBNAME | |
| Data Type | CHAR | Character String |
| Length | 70 | |
| Decimal Places | 0 | |
| Output Length | 70 | |
| Value Table |
Further Characteristics
| Search Help: Name | RETMNTPROCTDNAME | |
| Search Help: Parameters | TDNAME | |
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Text |
| Medium | 15 | Text Module |
| Long | 20 | Text Module Name |
| Heading | 20 | Text Module Name |
Documentation
Use
To be able to include the notice agreement in your correspondence, enter an appropriate description in the text module.
Dependencies
Text modules exist independently of their actual use. It is possible to have more than one reference to the same text module. Therefore, you should keep in mind that any changes to the contents of a text module affect all of its different uses.
Text modules are client-dependent and have to be transported separately (Proceed).
Example
Example 1 for a Notice Procedure
Notice rule 3 Months at End of Month applies for both contracting parties.
Notice Rule Contracting Party
3 Months at End of Month Both
Example 2 for a Notice Procedure
In residential rental, different notice periods apply for the tenant and landlord. Therefore, two different notice rules, Residential Tenant and Residental Landlord are defined and combined in a notice procedure.
Notice Rule Contracting Party
Residential Tenant Contractee
Residential Landlord Contractor
History
| Last changed by/on | SAP | 20020506 |
| SAP Release Created in | 110 |
