Ansicht
Dokumentation

CRMC_TERR_PFCT - Assign Partner Function to Assignment Function Category

CRMC_TERR_PFCT - Assign Partner Function to Assignment Function Category

TXBHW - Original Tax Base Amount in Local Currency   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

You can use this Customizing activity, to specify in which partner function an employee can be assigned to the territory via the position. This Customizing step is optional. If you omit this step, the partner function is not visible when you maintain a territory, and all employees (positions) are assigned without a specific partner function to territories.

For example, a territory is defined for Boston, U.S. Three employees are assigned to this territory: John Smith as a sales representative, Carol Jones as a key account manager, and David Brown as a marketing specialist.

The system can be customized to ensure that only the sales representative is determined automatically as employee responsible in the business transaction, and that data linked to the territory is distributed in Mobile Sales, only to the sales representative and the key account manager, but not to the marketing specialist.

In the standard system there are three assignment function categories provided by SAP. The assignment function category determines which cases consider an assignment of a position to a territory:

Assign. Funct. Cat.

0000 0001 0002
Sales Rep Mobile Data Receiver Backoffice
Case
Partner determination in business transaction X
Territory determination in business transaction X
Subscription generation based on territory data (attributes) X X
Subscription generation based on territory data (territory hierarchy ID) X X

These assignment function categories can be mapped to partner functions in this Customizing step. The mapped partner functions can then be used to classify the assignment of an employee (position) to a territory.

Example:

You can map the following partner functions in this Customizing step:

Partner Function Description Assign. Funct. Cat. Description
00000012 Sales Representative 0000 Sales Rep (for John Smith)
00000054 Key Account Manager 0001 Mobile Data Receiver (for Carol Jones)
Z0000099 Marketing Specialist 0002 Back Office (for David Brown)

You can then classify the assignment between a position and a territory by Sales Representative, Key Account Manager, Marketing Specialist, or leave it unclassified.

The following positions are assigned to the territory responsible for Boston, U.S.:

  • Position of John Smith using partner function 00000012 (Sales Representative)
  • Position of Carol Jones using partner function 00000054 (Key Account Manager)
  • Position of David Brown using partner function Z0000099 (Marketing Specialist)

The employee responsible is determined in business documents based on Territory Management data. If the territory for Boston, U.S. is determined as responsible in a business document, then only John Smith (assignment function category = 0000) is proposed as the employee responsible, and not Carol Jones or David Brown.

Furthermore, data related to the territory Boston, U.S. is downloaded for John Smith and Carol Jones (assignment function category = 0001) to CRM Mobile by using a corresponding subscription generator.

For more information about the subscription generator, see the SAP Library documentation for Customer Relationship Management under Data Exchange and Mobile Technologies -> CRM Integration Services → The Administration Console → Creating and Managing Replication Relevant Objects → Managing the Subscription Generator (the Subscription Agent).

Remark
Subscription generators can be built based on either territory attributes, (for example, subscription generator CUST & PROS (BY COU® OF TERR) is based on territory attributes countryand region), or on the territory ID. In both cases, assignment of the employee to the territory via the position is taken into account for distribution. The subscription generator identifies which attributes (first case) or territory ID (second case) an object has to have in the publication in order to be distributed to this employee in CRM Mobile.

The enabling of territory determination in business documents for an assignment function category is relevant if, for example, John Smith is assigned to the territory Boston, U.S. as a sales representative, and to another territory California, U.S. as a marketing specialist. Furthermore, the employee responsible is determined in business documents by other means than Territory Management. This means that the territory is determined from the employee responsible. If, in the example, John Smith is determined as the employee responsible, then territory Boston, U.S. is taken as the responsible territory.

Note
  • If you do not classify a partner function, that is, if you leave the field blank when you assign a position to a territory, this is considered as if a partner function mapped to assignment function category 0000 is used. This means that in this example, the employee would be considered just as John Smith.
  • The partner function in the business document and in the territory assignment do not have to be identical for partner determination based on Territory Managementby default.
For example, John Smith is assigned as partner function sales representative to Boston, U.S., but he is also determined for partner function employee responsible in the business document.
If you want the partner function to be identical in the partner determination and in the territory assignment, you have to set an X in the field Consider Partner Function.

0002

0002

0002

In this step you assign a partner function to an assignment function category in Territory Management.

0002

For information on setting up partner functions, see Customizing step: Customer Relationship Management -> Basic Functions -> Partner Processing -> Define Partner Functions






Vendor Master (General Section)   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 9072 Date: 20240606 Time: 174910     sap01-206 ( 136 ms )