Hierarchy
EA-FIN (Software Component) EA-FIN⤷
RE-FX (Application Component) Flexible Real Estate Management⤷
RE_CA_CU (Package) RE: Customizing (IMG) and Area Menu
IMG Activity
| ID | REFXVC_TIVCARSRULE | Define Resubmission Rules |
| Transaction Code | S_ALN_01002142 | (empty) |
| Created on | 20030403 | |
| Customizing Attributes | REFXVC_TIVCARSRULE | Define Resubmission Rules |
| Customizing Activity | REFXVC_TIVCARSRULE | Define Resubmission Rules |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | REFXVC_TIVCARSRULE |
Use
In this activity, you create your own custom rules for generating the dates on which you want to be reminded that objects may need further processing.
Prerequisites
SAP provides the following resubmission rules in the standard system:
- A01 - One-Time Occurrence
- A02 - &1 Months/&2 Days Before &3
- C01 - As of date &1 every &2 months
- P01 - &1 Months/&2 Days Before End of Term
- P02 - &1 Months/&2 Days Before 1st Contract End (Initial Term)
- P11 - &1 Months/&2 Days Before Notification of Renewal Option
- P12 - &1 Months/&2 Days Before Renewal Option
- P21 - &1 Months/&2 Days Before Notification of Automatic Renewal
- P22 - &1 Months/&2 Days Before Automatic Renewal
- P31 - &1 Months/&2 Days Before Notice Date
@1A@ If you want to program new rules, make sure that the names are in the customer name range (starting with Y or Z)!
Activities
Resubmission rules first have to be programmed, then they can be assigned and given parameters in this activity. For the rules to be available in the application, you have to assign them to object types, along with one or more resubmission reasons, in the Define Settings per Object Type IMG activity.
It is then possible to assign a resubmission rule, process and even change it (for instance the resubmission reason) in the application, such as processing a rental object.
For more information on programming new resubmission rules, refer to . Implement Enhancements (BAdI).
SAP provides these parameter types: Date, Number (4 Characters) and Yes/No. In addition to these, you can define your own parameters that the system uses to generate dates. These parameters are then required entry fields in the application.
You can set the Start Date, End Date, and Periodic indicators here, but they are not required entry fields in the application.
Example
Rule Parameter Type Parameters
A01 One-Time Occurrence Date Start Date
C01 As of date &1 every &2 months Date Start Date
Number (4 Characters) Interval in Months
P01 &1 Months/&2 Days Before
Contract End Number (4 Characters) Number of Months
Number (4 Characters) Number of Days
P02 &1 Months/&2 Days Before
Notice Date Number (4 Characters) Number of Months
Number (4 Characters) Number of Days
Yes/No Inactive Notice Also
@0S@ The Yes/No parameter type appears in the application as a checkbox in the application. You have to enter your own text for it in Customizing (see the example).
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 1 | Mandatory 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 | REFXVC_TIVCARSRULE | 0 | ALN0000031 | Flexible Real Estate Management |
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 |
| VC_TIVCARSRULE | C - View cluster | SM34 |
History
| Last changed by/on | SAP | 20030403 |
| SAP Release Created in | 200 |
