Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
AC (Package) Application Development R/3 Assets: Customizing
IMG Activity
| ID | SIMG_CFMENUORFAAIIO | Define List Variants |
| Transaction Code | S_ALR_87009091 | IMG Activity: SIMG_CFMENUORFAAIIO |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUORFAAIIO | Define List Variants |
| Customizing Activity | SIMG_CFMENUORFAAIIO | Define List Variants |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUORFAAIIO |
You only need to carry out this step if you want to use line item settlement. In this step, you define the display variants and totals variants for line item display in the transaction for allocating the distribution rules.
- The display variant defines the information (fields) that are to be displayed for each individual line item.
- Totals variants define the levels used for the summarized display of line items.
Recommendation
Usually you do not need to define your own display variants. Use the standard display variants supplied by SAP.
Standard settings
SAP delivers the following standard display variants:
- current number / allocation number / document number
- reference number / allocation number / document number
- document number / posting text
SAP delivers the following standard totals variants:
- distribution rule group
- fiscal year
- allocation number
Activities
If needed, you can define individual display variants and totals variants:
- Create a new variant key, or copy an existing variant.
- Define the line structure of the line item display (Insert after/before) in the detail screen. Via Field list, you can display the fields that are available, and select the appropriate field.
Further notes (Transport)
You can include the display variants in a transport request in the overview screen for the transaction (Display variants -> Transport). Note that the definition of the display variant applies only in a specific client. Therefore, transport is necessary not only between systems (such as from a test system to a productive system), but also in order to make the display variant available in other clients.
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_CFMENUORFAAIIO | 1 | HLA0001310 | Line Item Settlement of AUC |
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 |
| AIIO | T - Individual transaction object | AIIO | 9999999999 | List variants for assets under construction |
History
| Last changed by/on | SAP | 19990222 |
| SAP Release Created in |
