Bulk product-territory alignment from external systems
Key Takeaway
Imported Product Territory Availability records stay in Draft until you run the Publish Draft Product Territory Alignments batch job. The job makes them Active and creates detailed availability records for child territories.
Bulk product-territory alignment lets you load product-to-territory alignment data from an external system instead of aligning products one at a time in the Admin Console. The imported records arrive in a Draft state, so importing them doesn't publish anything. A batch job then activates them and builds the detailed availability records that give users in each territory access to the right products.
What product-territory alignments are
Product-territory alignments control how products and product messages are assigned to territories. The goal is that the correct user has access to the correct product in the correct territory.
Aligning a product to a territory creates Product Territory Availability records. Each record has one of four alignment types.
| Alignment type | What it means |
|---|---|
| Inclusion | The territory is directly aligned. |
| Territory and Subordinates Inclusion | The territory and its child territories are aligned. |
| Territory Exclusion | The territory is excluded even though its parent is aligned. |
| Inclusion (Inherited) | The territory is included because a parent territory is aligned. |
When a territory isn't aligned to a product, no record is created.