...
The settings from the example below will allow us to track sales entries by salesperson and the area the salesperson is responsible for. It will also be possible to track the cost spent on profitability of a sales campaign for a given area. Corresponding dimensions can be further useful, for example, to track the profitability of specific projects or the costs we incur per employee.
...
When setting up corresponding dimensions, you must also keep in mind that this extension works recursively. So, for example, when you assign a specific salesperson to a customer, or fill it out in the sales invoice of that customer, not only the dimension for the area is automatically populated, but also the sales campaign Sales Campaign dimension that is bound to that area Area dimension.
| Tip |
|---|
The settings below make sense. |
...
| Warning |
|---|
The settings below don't make sense. Given the recursive nature of correspodning dimensions, it is unnecessary to bind the sales campaign to the salesperson Salesperson dimension, since the salesperson Salesperson dimension already contains the dimension for the area, and with it all the dimensions bound to that dimension. |
...
| Note |
|---|
The same message appears if we limit the salesperson Salesperson and area Area dimensions and only block the combination of certain values. For example, based on our setup above, we might want to prevent salespeople from interfering with each other's areas of responsibility to prevent subsequent distortion of the tracked data. Therefore, if we limit Jim Oliva's access to areas of Southern Europe and North America, as he is only responsible for Northern Europe, it will be possible to assign the Area as a corresponding dimension of the Salesperson, but if in the next step we try to assign the salesperson Jim Oliva to a region other than Northern Europe, we will not be able to complete the setup. |
...
For a practical explanation of the priority system, we can use the following example. We want to analyse the costs incurred in profitability of sales campaigns for a specific segment of the goods sold - a business group. Furthermore, we will also want to keep track of the entries of the salespeople responsible for a given area. Each area will also have its own sales campaign so that we can track the costs spent on profitability of this type of campaign as well.
...
The setup above therefore implies that the first thing to be added is the Salesperson and its corresponding dimensions, the Area with code 20 corresponding to Northern Europe and the Sales Campaign with the corresponding value for a campaign targeting Scandinavian countries. The salesperson Salesperson will be added first because each customer usually has a salesperson assigned to them, so when a new sales document is created, this value will be added automatically.
...
In the next step, however, we must also fill in the value to the dimension for the business groupBusiness Group. Since the business group Business Group was filled in last in the sequence, its value for the sales campaign Sales Campaign will overwrite the sales campaign Sales Campaign tied to the salesperson. The sales campaigns Sales Campaigns are assigned to each product segment as follows.
...
Therefore, if we fill in the the business group Business Group with the value ELECTRONICS, the sales campaign will be overwritten with the value CAMPUSACAN corresponding to the sales campaign Sales Campaign targeting North America, which may be undesirable.
...
If, in the context of this example, we wanted to avoid overwriting corresponding dimensions values due to the system of priorities, the following change in the dimensions settings could be a solution. The salesperson Salesperson dimension will now also carry a dimension for the sales groupBusiness Group, so that we are able to track the items entries for the segment of goods sold. And we will adjust the criteria by which we want to track the cost profitability of a sales campaigns so that it can be tied either only to the segment of goods sold (see below), or only to the area that the campaign would target.
...
If we decide to use the same corresponding dimension for multiple dimensions, it may also cause a collision. For example, we may have a salesperson Salesperson dimension set up with corresponding dimensions for area Area and sales campaignSales Campaign. In addition to this dimension, we also want to use the area Area dimension, which has a corresponding dimension for the sales campaignSales Campaign. Next, when we create a sales document, we will probably add the salesperson Salesperson dimension first, because in most cases customers are assigned to a particular salesperson. Based on the salesperson Salesperson dimension, their corresponding dimensions - the value for the area Area and sales campaignSales Campaign, are then automatically added to the document line. At this point, the dimension priorities come into play again. Because the dimension for the area Area is added second, and also has its own corresponding dimension for the sales campaignSales Campaign, the system will automatically fill in the value it takes from the sales campaign Sales Campaign directly tied to the areaArea, and the value of the sales campaign Sales Campaign bound to the salesperson Salesperson will never have its turn.
...
| Tip |
|---|
Collisions Collision of corresponding dimensions can occur due to inefficiently designed settings. The simplest best solution is therefore to consider which corresponding dimensions make sense and which can conflict with each other during the process of setting up the corresponding dimensions. Besides, it is also necessary to thoroughly test all scenarios for which we will intend to use this extension. |
V příkladu, který jsme popsali výše dává smysl prodejní kampaň z dimenze prodejce zcela odstranit. Je totiž pravděpodobné, že kromě analýzy prodejů daného prodejce zodpovídajícího za konkrétní oblast, budeme chtít také sledovat náklady na prodejní kampaně za konkrétní oblast. Tím, že naše nastavení vázaných dimenzí funguje rekurzivně, jinými slovy, že dimenze pro oblast vázaná na prodejci zároveň implicitně obsahuje také dimenzi pro oblast, na kterou je vázaná dimenze pro prodejní kampaň, se nám při správném nastavení hodnot doplní všechny požadované informace tam, kam chceme, a nebudou si navzájem překážet.
...
In the example we described above, it makes sense to remove the Sales Campaign from the Salesperson dimension entirely. Because it is likely that, in addition to analysing the sales of a particular salesperson responsible for a particular area, we will also want to track the sales campaigns for a particular area. And because the corresponding dimensions are recursive, meaning that the Area dimension tied to the Salesperson also implicitly contains the Area dimension to which the Sales Campaign is tied, it will fill in all the required information exactly where we want it, and the dimension values will not interfere with each other if the setup is done correctly.
...