Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-CIC (Application Component) Interaction Center WinClient⤷
INSC (Package) Application Development R/3 Plant Maintenance Customizing
IMG Activity
| ID | SIMG_CFMENUV_TQ80_SM | Define Order Types and Special Notification Parameters |
| Transaction Code | S_P00_07000288 | (empty) |
| Created on | 20000201 | |
| Customizing Attributes | SIMG_CFMENUV_TQ80_SM | Define Order Types and Special Notification Parameters |
| Customizing Activity | SIMG_CFMENUV_TQ80_SM | Define Order Types and Special Notification Parameters |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUOLIAOIM9 |
In this step, you can set additional special notification parameters.
For service notifications, you can:
- Define a sales order type for creating a sales order from the service notification
- Activate automatic contract determination
After an object is assigned to the notification, the system uses automatic contract determination to search for valid service contracts for this object. If only one valid contract can be determined, the contract number is copied automatically to the notification and saved there. If the system determines several contracts, the user is offered the list of contracts for selection.
Note that if the object in the notification is changed, contract determination is triggered again.
- Define another order type for notifications with reference to service contracts
In this field, you can specify another order type, as well as the standard order type, that should be used for notifications of this type. This is always useful if you have to generate different order types from a notification type, because some of the orders can be charged to your customers by means of service contracts, but service orders cannot.
In the 'Order type for notifications with service contracts' field, you must specify the service order type that allows settlement to service contracts.
The settlement profile for this order type must be defined so that no revenue can be posted to this order type. This is because the revenues should be aggregated in the assigned sales order.
When an order is generated from a notification, orders can be generated with two different order types. If the notification does not have a service contract number, the order type is set as standard; if the notification is given the number of a service contract, the order type is 'Order type for notifications with service contracts'.
This setting is useful for notifications, to which a service contract is assigned.
Requirements
The notification types should already be fully defined.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| 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 | SIMG_CFMENUOLIAOIM9 | 0 | HLA0009533 | Maintenance Processing |
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 |
| V_TQ80_SM | V - View | OIM9 | Define Special Notification Parameters |
History
| Last changed by/on | SAP | 20000201 |
| SAP Release Created in | 46C |
