Relationships and Partner
Functions 
Purpose
When defining your own relationship or partner function categories, the necessary Customizing must be maintained in both CRM Enterprise and Mobile Sales:
- MSA client tables:
¡ SMOKVBEZTP Allowed Relationship/Partner Function Categories in MSA
¡ SMOKVBEZTX Table for Language-Dependent Texts of KVBEZTP
¡ SMOKVLKTAB Assign Relationship/Partner Function Categories to Interlinkage Table
- CRM business configuration table TBZ9
- Business Partner/Partner tables (for exchange with R/3):
¡ CRMC_PARTNER_2CR Mapping Table for R/3 Partner Functions in CRM
¡ CRMC_PARTNER_2R3 Mapping Table for Partner Functions in R/3
Process Flow
Described below are the three main Customizing steps. Depending on your scenarios, you will require the following steps:
· Customizing steps 1, 2, and 3 when exchanging data between MSA, CRM, and R/3.
· Customizing steps 1 and 2 when exchanging data between MSA and CRM, without R/3.
· Customizing steps 2 and 3 when exchanging data between CRM and R/3, without MSA.
Note that you should create your own relationship categories in the customer namespace beginning with Y or Z and with a maximum length of 6, and partner function categories with a maximum length of 8 (for example, Y0000001, a partner function between two business partners). Relationship category names and partner function category names must not be the same.
1. Defining Partner Functions and Relationship Categories in the Mobile Client
...
1. Assign the subscriptions belonging to the following publications to the Customizing client:
¡ Mobile-specific Customizing objects
¡ Customizing objects
¡ Employees
Read the data in the Customizing client.
2. Choose Mobile System Maintenance ® Cross-Component Settings ®Relationship Categories.
3. Maintain partner function and relationship categories.
a. Create a record in the Relationship Category tile (table SMOKVBEZTP) and make the following entries:
§ Relationship Category = Y0000001
§ Source = CAP, CON, or *
§ Destination = CAP, CON, EMP, or *
§ Classification = R/3 System (if the relationship is a partner function and should be displayed in the Partner Functions tile set for destination CAP or CON, or in the Sales Team tile set, Partner Functions tile for destination EMP). Otherwise select System.
§ Directed = Set indicator if relationship is directed
§ Cardinality = * (if n Y0000001 assignments are allowed)
§ Cardinality = 1 (if only 1 Y0000001 assignment is allowed)
§ Active = Set indicator
§ Visible = Set indicator
§ Navigation = Set indicator
b. Create language-dependent records in the Relationship Category Text tile (table SMOKVBEZTX) and make the following entries:
§ Language in which the text should be available
§ View From = Not directed, if the relationship is not directed
§ View From = Source, if the relationship is directed and the text is viewed from the source
§ View From = Destination, if the relationship is directed and the text is viewed from the destination
Where a
relationship is directed, enter two texts, one viewed from the source and the
other from the destination.
§ Description = Text description
c. Create a record in the Relationship Category Link Table tile (table SMOKVLKTAB) and make the following entries:
§ Select KVBEZ6 if the relationship is between a business partner or contact person and another business partner or contact person and should be visible in the Relationships tile set.
§ Select KVBEZ7 if the relationship is between a business partner or contact person and employee and should be visible in the Sales Team tile set.
Both link
tables KVBEZ6 and KVBEZ7 can be maintained for a partner function or
relationship category. The destination entered must be *. Provided the
business partner is maintained with both the roles CON and EMP, the partner
function or relationship is downloaded to SMOKVBEZ6 and SMOKVBEZ7 and is
visible in the Relationships and Sales Team tile
sets.
4. Once the necessary partner function and relationship categories have been created in the mobile client, send the data to the middleware using CONNTRANS. The three tables SMOKVBEZTP, SMOKVBEZTX, and SMOKVLKTAB will be updated in the middleware.
2. Defining Partner Functions and Relationship Categories in CRM
...
1. Define partner functions in CRM
To do this, choose in Customizing Customer Relationship Management ® Basic Functions ® Partner Processing ® Define Partner Functions (for more information, see the Implementation Guide (IMG) documentation).
Define the partner function category with the same name used for the partner function category in the mobile client.
2. Define relationship categories in CRM
To do this, use transaction BUBA. For more information, see the SAP Business Partner Development Manual Business Partner Relationship Control, Chapter A4.5 (SAPNet ® Alias CRM-CRD ® SAP Business Partner ®Development Manuals (Quick Links)).
Define the relationship category with the same name used for the relationship category in the mobile client. The business configuration table TBZ9 is an E table with customer namespaces Y and Z.
Partner functions can only be grouped with relationship categories in CRM Enterprise. This Customizing must be downloaded to the mobile client, table CDBC_PARTNER_FCT, containing the association between partner function and relationship category from CRM Enterprise.
Only relationship categories without a time constraint, that is those with the value SPACE or 0 for the Time Constraint field in the table TBZ9, can be assigned a partner function category.
3. Defining Partner Functions and Relationship Categories in OLTP R/3 System
To exchange partner functions with the OLTP R/3 System, you must customize both CRMC_PARTNER_2CR and CRMC_PARTNER_2R3 (in Customizing choose Customer Relationship Management ® Basic Functions ® Partner Processing ® Data Transfer).
The following reports are available in CRM for downloading customer relationship categories and partner functions from CRM Online to CDB:
§ CRM_DOWNLOAD_CDB_BP_PFT for partner functions
§ CRM_DOWNLOAD_BP_RELTYPE for relationship categories