Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ FVVI (Package) R/3 appl.dev. for Financial Assets Management: Real estate
IMG Activity
ID | SIMG_CFMENUOFDIKUEN3 | Periods of Notice - Maintain Deadline Regulation |
Transaction Code | S_ALR_87007669 | IMG Activity: SIMG_CFMENUOFDIKUEN3 |
Created on | 19981222 | |
Customizing Attributes | SIMG_CFMENUOFDIKUEN3 | Determine Periods of Notice - Deadline Regulation |
Customizing Activity | SIMG_CFMENUOFDIKUEN3 | Determine Periods of Notice - Deadline Regulation |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_CFMENUOFDIKUEN3 |
In this section, you determine different notice regulations (periods of notice) for the automatic calculation of notice dates.
Depending on the contract term, you can determine the following:
- Notice date on an exact day
- Here you can make the calculation of the notice date dependent on the exact date of receipt of notice.
The regulations are defined by means of notice keys depending on:
- Tenancy law
- Contract type
- Contract term
Example
You want to determine for a particular notice key that
- For a contract term smaller than 12 months
- Notice can only become effective on 03/15 of the following year
- If the notice is received by 10/03 (calendar day) of a year
- And for a contract term greater than 12 months but smaller than 24
- Notice can only become effective on 06/30 of a year
- If notice is received by 03/04 (calendar day) of a year
Create in the maintenance view a shared notice key for different contract terms:
Notice key :Test1 Notice key:Test1
RA duration (months): 12 RA duration (months: 24)
No. of days field: 3 4
Received month (RM) field: 10 3
Received year (RYr) field:
CD/WD indic.field: 1 2
Notice date field: 15 30
Notice month field: 3 6
Notice year field:
This notice key can now be assigned while editing the contract; the effect on the calculation of the notice date would be as follows:
Receipt of notice Contract term = Date of notice
upto 10/03/1997 < 12 months 03/15/1998
after 10/031997 < 12 months 03/15/1999
03/04/1997 > 12 months 06/30/1998
03/05/1997 > 12 months 06/30/1999
Activities
Check the standard settings and adapt these to your requirements if necessary.
Use the above example as a guide.
Note
Independent of the notice key, you can alternatively enter a free deadline regulation in the master data of a contract.
If the tenant gives notice and other periods of notice apply, these should be defined with the same key in the "Varying Notice Deadlines for Tenants" table.
Business Attributes
ASAP Roadmap ID | 250 | Define Number Range and Basic Structures |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | SIMG_CFMENUOFDIKUEN3 | 0 | I090004611 O I090004612 |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
VTIVKUE3 | V - View | SM30 | VTIVKUE3 | Deadline Regulation for LO Periods of Notice | ||
VTIVKUE3V | V - View | SM30 | VTIVKUE3 | Varying Notice Deadlines for Tenants |
History
Last changed by/on | SAP | 20000126 |
SAP Release Created in |