Combined Sales Area Determination in C4C Sales Transactions
With 1605 (May 2016) release, Cloud for Customer has come up with a new functionality which allows defaulting of combined sales area in a sales transaction. The combined sales area represent combination of Sales Organization, Distribution Channel and Division. This functionality can be scoped in after selecting the respective scoping question available in Sales Order, Leads, Opportunity, Sales Quote and Activities sections. Below screenshot shows the scoping question as available under Sales Order section.
Once this option is scoped in your implementation project, the defaulting of the combined sales area in a sales transaction would happen as per the below sequence:
Combined Sales Area Determination Sequence
- Intersection of Account Sales Data and Employee Sales Data
- Compare match of Sales Organization + Distribution Channel + Division
- Compare match of Sales Organization + Distribution Channel
- Compare match of Sales Organization
- Employee Sales Data
- Intersaction of Account Sales Data and Sales Organization of Employee Assignment
- Account Sales Data
- Sales Organization of Employee Assignment
The determination logic will stop at the sequence step in case it finds relevant data. In case it finds more than one entry at any sequence step, the system would pick one from the list.
When this new scoping is in place, the value help on Sales Organization in a sales transaction screen shows restricted values as per the above sequence. A sample screenshot shows the options available in this value help:
The user has options to filter the data shown in this value help. There is a possibility for the system administrator to adapt these queries. In case, the access to Acocunt’s sales data be restricted then the system admin can remove this query from this value help. Note, for flexibility purpose, C4C allows user to change the determined Distribution Channel and Division in a sales transaction screen. In case, change on these fields be restricted, the C4C admin can make these fields read-only.
Apart from determination of sales area, few other sales area dependent fields are also determined accordingly in a sales quote or sales order screens. These fields are Incoterms, Payment Terms, Curreny, Delivery Priority etc. A change in sales area will result in re-determination of the sales area dependent fields . In case, the account sales area does not values for these sales area dependent fields, then no data will initialzed for these field in sales quote and order screens.
Apart from this combined sales area determination, we also need to take a look at the sales unit determination. Combined sales area determination does not default the sales unit of a sales transaction. To default the sales unit on a sales transaction, we need to use Sales Unit determination as available in the maintain Involved Party configuration of that sales transaction. The involved party determination is a part of Cloud for Customer from past many releases.
The various possible steps for the sales unit determination are shown below:
The sales unit determination steps are:
- Step 1 – Responsibility “Sales Unit of Sales”
- Step 5 – Account’s Sales Data
- Step 20 – Functional Organization Unit of Employee Responsible
- Step 30 – Organizational Unit from Org Model if only one suitable Functional Unit exists
In case you want to use the new combined sales area determination then only the Step 20 of the above list would be sufficient for the sales unit determination.
Step 1 uses the feature that is offered in work center Administrator under General Settings. This is Work Distribution -> Organizational Work Distribution which includes business area Sales Unit for Sales.
Step 5 defaults the sales area from the account’s sales data. This determination step defaults the sales unit in arbitrary fashion if several sales area are maintained at account level. The sales unit determination follows the below sequence:
- If a sales group is assigned in the account’s sales data then this determination step defaults the sales unit with the sales group.
- If only a sales office is assigned to the account’s sales data then the sales unit is defaulted with the sales office.
- If no sales office or sales group is maintained, the sales unit is equal to sales organization.
Step 20 defaults the sales unit from the organizational unit to which the employee responsible (owner) belongs, provided that organization unit has sales function. This step does not take into account the sales data maintained at the employee level.
Its a very useful doc.
Thanks for sharing your knowledge.
Note, that the determination has been enhanced in the meanwhile to also consider a main indicator that can be set at employee's sales data:
The Sales Area Determination business option allows the user to add through the selection of the Sales Organization its corresponding Distribution Channel and Division valid for the account and employee. It will be defaulted if the sales area matches from the employee and the account. If multiple matching assignments exist, the user can select the appropriate one. If an employee is not assigned to a sales area, the determination will consider account’s sales data only.
Determination sequence logic in online mode:
If employee sales data has a main indicator set, system defaults this sales data to the transaction, but still considers an intersection of the account sales data, such as:
Without a main indicator, system defaults
The system defaults in all these cases where an intersection with the account sales data is found sales org., distribution channel, division, sales office and sales group from account sales data.
* If several sales data entries are relevant for defaulting, system picks one from the list