Hierarchy
SAP_AP (Software Component) SAP Application Platform⤷
AP-PRC-PR (Application Component) Pricing⤷
PRICING_CUSTOMIZING_C (Package) Customizing for Pricing
IMG Activity
| ID | CRM_VOR_KON_KOND | Define and Assign Groups of Condition Tables and Types |
| Transaction Code | S_AEC_66000658 | (empty) |
| Created on | 20010420 | |
| Customizing Attributes | CRM_PRI_GRUKON | Groups of Condition Tables and Types |
| Customizing Activity | CRM_VOR_KON_KOND | Define and Assign Groups of Condition Tables and Types |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | CRM_PRI_GRUKONKONTR |
Allowed condition tables and types can be assigned here for the following objects:
Purchase contract: the group is assigned to the purchase contract when the item category is maintained. Currently, no changes are to be made to the standard settings.
Sales contract or service contract: the group is assigned to the sales contract or service contract when the item category is maintained (recommended!) or when the transaction type is maintained on the first detail screen. If you change the standard settings, one of the following fields must be contained in the condition tables:
CRM_HEADER_GUID (contract header)
CRM_ITEM_GUID (contract item)
Business partners: the group BUPA exists for business partners for CRM standalone, and group BUPA_R3, if the business partners are copied fromthe R/3 OLTP system. You assign the group under Master Data -> Business Partner -> Basic Settings -> Define Condition Group. If you change the standard settings, one of the following fields must be contained in the condition tables:
'SOLD_TO_PARTY'
'SHIP_TO_PARTY'
'BILL_TO_PARTY'
'PAYER'
'PARTNER_GUID'
Product: the group PRODUCTCRM exists for the products in the standard, for CRM standalone and the group PRODUCT_R3, if the product data is copied from the R/3-OLTP system. You assign the group for products under Master Data -> Product -> Special Settings for Sales Transactions -> Assign Condition Group to Application CRM. If you change the standard settings, the product must be contained as a field (field name:PRODUCT).
Customer hierarchy: the entry HIER_CUST is valid for the customer hierarchy which is copied from the R/3 system. The entry HIER_NODE is valid for the business partner hierarchy of the CRM system.
Campaigns: the condition group 1200 exists for campaigns. This provides you with a campaign-related price and campaign-relate discount. If you include customer-specific fields, at least the CAMPAIGN_GUID field must be available. You assign the group to the application in Customizing under: Marketing -> Marketing Planning and Campaign Management.
Use
Requirements
Standard settings
Activities
Example
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 |
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 |
| /SAPCND/VC_GROUP | C - View cluster | SM34 | 0000000001 | Define Groups | ||
| CRMV_PROCESS_MA | C - View cluster | SM34 | 0000000002 | Assign Transaction Type Group | ||
| CRMV_ITEM_MA | C - View cluster | SM34 | 0000000004 | Assign Item Category Group |
History
| Last changed by/on | SAP | 20010530 |
| SAP Release Created in | 30A |
