!--a11y-->
|
Customizing Activity |
Sales and Distribution in R/3 |
CRM |
|
Define Partner Functions |
Different user interface (UI) than in CRM |
Different UI than in R/3 |
|
You specify the relevant partner object, such as the sales document header or customer master. |
N/A |
|
|
Function : a two-digit key for the function |
Function : an eight-digit key for the function |
|
|
Description : a name or short description that is displayed in transactions |
Text : a name or short description that is displayed in transactions |
|
|
N/A |
Abbreviation : a two-digit key for the function which is used internally in the system, not currently displayed in transactions |
|
|
Partner type : a hard-coded category that allows the system to identify the function. It does not correspond with the partner function category in CRM. |
Function category : a hard-coded category that allows the system to identify the function. It does not correspond to the partner type in R/3. |
|
|
Error group : an incompletion procedure which specifies which fields a user must complete in a sales document |
N/A |
|
|
N/A |
Usage : whether the function is used in CRM or Enterprise Buyer |
|
|
N/A |
Relationship category : the business partner relationship category to which this partner function corresponds. The system often enters this category automatically once you have entered the function category because many function categories and relationship categories are hard-coded to correspond to each other. |
|
|
Higher level function : a partner function to which you apply subordinate functions. It can be used to create customer hierarchies. |
N/A This feature is not needed in CRM because an entire hierarchy can be included in a transaction. |
|
|
Unique in customer master : indicates whether you can use this function only once in the customer or vendor master data |
N/A In CRM, in the partner determination procedure, you can set how many times the function can appear in a transaction. |
|
|
N/A |
Block : stops a partner from performing this function for himself |
|
|
Customer hierarchy type : specifies the type of hierarchy, such as pricing |
N/A Partner determination in CRM works with business partner hierarchies as either partner function categories or as sources. |
|
|
Define Access Sequences |
There are no access sequences in R/3 partner determination. The sequence assigned to a partner function in the Customizing activity Define and Assign Partner Determination Procedure specifies when the system determines a partner, for example, before other partners. |
In this activity you define the search strategies the system uses during partner determination. You enter the sources the system uses, and the order in which it uses them. A wizard is available to help you define access sequences. |
|
Partner Teams |
N/A |
A partner team is a group of people involved in a project. For example, the Buying Center in Opportunities includes the people on your customer's side who make purchasing decisions, or influence those making these decisions. |
|
Define (and Assign) Partner Determination Procedure |
In R/3, you define the procedure and assign it to a transaction in this Customizing activity. |
In CRM, your define the procedure in this activity, and assign it to a transaction in another. |
|
No wizard or procedure check are available. |
A wizard and check are available to help you define and check procedures. |
|
|
Overview Screen: Entry a key and description of the procedure |
Overview Screen :Enter a key and description for the procedure. Block: turns off the partner determination procedure so that it is not working in the system Log: automatically generates a log in transaction processing that records how partner determination occurs |
|
|
Procedure Details: Partner Functions: allows to you to switch to a list of all partner functions. |
Procedure user :corresponds to the screen Procedure assignment in R/3 and sets for which business transactions the procedure is valid |
|
|
Procedure partners :Function: two-digit key for the partner function Description: short text Not changeable: sets whether the partner can be manually changed in transactions after determination Mandatory function: sets whether the function is mandatory in the transaction Source: sets whether the system uses the sold-to party's master data for determination, or some other partner's master data, and sets which table the system uses Sequence: indicates when this partner is determined. If the field is blank, this partner is determined first. |
||
|
Procedure assignment: Corresponds to the screen Procedure User in CRM Assigns the procedure to sales documents types |
Partner functions in procedure :Lists all partner functions in the procedure, the maximum and minimum times they can appear in a transaction, the access sequence for each function, when determination occurs, whether or not manual entry is allowed, and other settings |
|
|
User Interface Settings: Sets which partner functions are displayed in the transaction header, and what information about these partners is shown |
||
|
Assign Partner Functions on the Debit Side to Account Groups |
You assign the partner functions that you defined to account groups. A partner function on the debit side can only be used for customer masters that have been assigned to these account groups. Choose Partner functions -> Environment -> Account group assignment |
N/A There are no account groups in CRM |
|
Data Transfer |
N/A |
Allows you to set how R/3 and CRM exchange data, for example how partner functions in CRM correspond to those in R/3 |