Hierarchy
BBPCRM (Software Component) BBPCRM⤷
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_CFMENUOFDICPOI1 | Maintain Letter Recipients |
| Transaction Code | S_ALR_87100666 | (empty) |
| Created on | 19991117 | |
| Customizing Attributes | SIMG_CFMENUOFDICPOI1 | Maintain Letter Recipients |
| Customizing Activity | SIMG_CFMENUOFDICPOI1 | Maintain Letter Recipients |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUOFDICPOI1 |
Here, a role category hierarchy is defined for each contract type. If you use the Customizing entries for determining the letter recipient when generating a letter for this contract type, the first role category in the hierarchy is checked to see whether a partner with this role category is assigned to the contract. If not, this procedure is repeated with the each subsequent role category in the hierarchy until a match is found; the first partner role category found is the role category of the letter recipient. A letter is then generated for each contract partner with this role category (each of these partners is a letter recipient).
If the contract has not been assigned any partner with a role category that corresponds to one of the role types in the hierarchy, you have to manually enter the role category of the recipient when generating standard letters.
Example
You have made the following entry for the contract type "Residential lease-out":
Seq no. Role cat. Name
1 0601 Tenant (not customer)
2 0600 Master tenant w/ cust. acct.
A letter is then generated for any partners with role category 0601. A letter is only generated for the master tenant with customer account if no partner with role category 0601 is assigned to the contract.
If for any reason there is no partner with either of the role categories, you will not receive the option to read the Customizing entries; you have to enter the recipient manually.
Requirements
Standard settings
Recommendation
Activities
Further notes
Of course, you can also choose not to read the Customizing entries when generating letters and enter the role category of the partner yourself.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-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_CFMENUOFDICPOI1 | 0 | I090004636 | Correspondence |
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 |
| VTIVCPOI01 | V - View | SM30 |
History
| Last changed by/on | SAP | 19991117 |
| SAP Release Created in |
