Ansicht
Dokumentation
CRMV_TERRLEVEL - Define Territory Hierarchy Levels
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up ABAP Short ReferenceThis documentation is copyright by SAP AG.
In this Customizing activity you
- define the structure of the territory hierarchy by specifying territory levels,
- define territory level descriptions,
- define the format of the territory hierarchy ID
- indicate whether the territory ID should be generated automatically.
A territory can for example, be a geographical area, a product line, or a customer, or can consist of a combination of attributes, such as the country, state, zip code, and product category.
Each level of a territory hierarchy has its own territory ID. The territory IDs of these levels are strung together in sequence to make up the ID of a territory hierarchy (see example below).
- You have maintained the organizational model for your enterprise, including positions and assigned employees in IMG activity Change Organizational Model.
- You have completed step Define Number Range Interval for Territory Hierarchy Levels
- You know how you want to organize your territories and how to place them in the territory hierarchy. This includes, in particular
- The number of levels in your territory hierarchy
- The length of the territory ID for each level.
For example the top level "Company" consists of two characters, such as A1 (see example below)
In order to define the territory hierarchy levels for your enterprise, proceed as follows:
- Select New Entries.
-
In the Territory Level field, enter the number of the hierarchy level.
By doing this, you determine where the territory ID of this level appears in the territory ID of the territory hierarchy.
The level for the top hierarchy node must be 0. - In the Description field, enter an appropriate name for this level.
-
In the Offset field, enter the position in which the territory ID for this level is entered in the territory ID for the territory hierarchy.
The territory hierarchy ID is made up of territory IDs of each territory level in the hierarchy. For example, territory hierarchy ID A1B01C001D0000001 can be broken down as follows (see also example below): A1 is the ID for the company, B01 is the ID for the product line and so on. For B01 the offset is 3, that is, the ID for the product line starts in the 3rd position.
You work out the offset as follows: Offset Area = Offset Region + Length Region = 6 + 4 = 10 -
In the Length field, enter the length of the territory ID. You usually use longer territory IDs for territories at lower levels of the hierarchy than for territories at higher levels.
The territory hierarchy ID may not exceed 30 characters. - Enter the Number Object Interval. What you can select here depends on the list of number range intervals defined.
- Enable the Auto Generate Territory ID for the levels where you want the system to generate an ID when you create territories. You will still be able to overwrite what is proposed.
Warning: Do not change the length of the territory ID once the system is productive.
For Territory Management your enterprise has the following structure:
- Company - the entire enterprise
- Line - one or several product categories
- Region - larger geographical region, including several territories
- Area - smaller, more specific geographical region
Step 1: You define the following hierarchy levels in the IMG:
| Territory Level | Level Description | Offset | Length | Auto Generate Territory ID | |
|---|---|---|---|---|---|
| 0 | Company | 0 | 2 | ||
| 1 | Line | 2 | 3 | (enabled) | |
| 2 | Region | 5 | 4 | ||
| 3 | Area | 9 | 8 | ||
Step 2: You then define the following territories:
| Territory Level | Territory ID | Territory Description |
|---|---|---|
| Company | A1 | ABC Inc. |
| Line | B01 | Bottles |
| B02 | Cans | |
| Region | C001 | North |
| C002 | South | |
| C003 | South | |
| Area | D0000001 | Boston |
| D0000002 | New York | |
| D0000003 | Miami | |
| D0000004 | New Orleans | |
| D0000005 | Baton Rouge |
The territories in our example, once created, would look as follows:
| A1 | ABC Inc. |
| B01 | Bottles |
| C001 | North |
| D0000001 | Boston |
| D0000002 | New York |
| C002 | South |
| D0000003 | Miami |
| D0000004 | New Orleans |
| B02 | Cans |
| C003 | South |
| D0000005 | Baton Rouge |
In this example, the territory hierarchy Company A1 (ABC Inc.), Product Line B01 (Bottles), Region C001 (North), and Area D00000001 (Boston) has the territory hierarchy ID A1B01C001D0000001.
Note that the territory ID for each territory is unique. This means that, in the example above, for "South" you need two territory IDs.
General Material Data ROGBILLS - Synchronize billing plans
This documentation is copyright by SAP AG.
Length: 8242 Date: 20240523 Time: 170057 sap01-206 ( 72 ms )
