---
sourceDocument: Brazil Customer Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/customer-service-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Customer Service Management

ft:clusterId :

    - csm

bundleId :

    - csm

workflow :

    - Customer and Industry


---

# Organization codes and paths

# Organization codes and paths {#ariaid-title1}

Release version: Brazil  
Updated September 9, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
An organization code is a unique identifier for a business organization, while an organization path establishes the organization hierarchy.

## Organization codes {#csm-bo-code-bo-path__section_rwz_h2s_w5b}

An organization code must be unique that identifies a business organization in a ServiceNow instance. Attempting to insert a new record with previously existing organization code in the Organization Core
\[sn_customer_service_organization\] table, the value for the code results in the following error:

`java.sql.BatchUpdateException: Duplicate entry for key service_organization_path`

## Organization paths {#csm-bo-code-bo-path__section_yr5_cfs_w5b}

An organization path establishes the hierarchy among different business organizations. This path is stored in the Business Organization Path on the
Business Organization form.

An organization path is a combination of the organization codes for each business organization in the hierarchy. For example, let's use the following business organizations to demonstrate business organization paths.

{#csm-bo-code-bo-path__table_mxm_dst_jyb__entry__3}

| Business Organization | Organization code | Organization path |
|-|-|-|
| Manhattan Main | \~\~\~\~1 | \~\~\~\~1 Manhattan main is the parent company. The business organization path for Manhattan main is the same as the organization code, which indicates that it's the first element in the hierarchy. |
| Manhattan Upper | \~\~\~\~2 | \~\~\~\~1/\~\~\~\~2 Manhattan upper is a child company of Manhattan main. The structure of the business organization path is interpreted as Manhattan main/Manhattan upper. |
| Manhattan Upper East | \~\~\~\~3 | \~\~\~\~1/\~\~\~\~2/\~\~\~\~3 Manhattan upper east is a child company of Manhattan upper and the structure of the business organization path is interpreted as Manhattan main/Manhattan upper/Manhattan upper east. |
| Manhattan Upper West | \~\~\~\~4 | \~\~\~\~1/\~\~\~\~2/\~\~\~\~4 Manhattan Upper West is a child company of Manhattan Upper. The structure of this business organization path is interpreted as Manhattan main/Manhattan upper/Manhattan upper west. |
[Table 1. Example of business organizations to demonstrate organization paths]

{#csm-bo-code-bo-path__table_mxm_dst_jyb}

## Importing business organization records {#csm-bo-code-bo-path__section_g5g_1mf_x5b}

If you create your business organization records by importing the data from some source system through a transform map, make sure that you execute the business rules. The organization Path is added, updated, and deleted based on the insertion, updating, and deletion of records in the Organization Core \[sn_customer_service_organization\] table through the business rules. If the business rules aren't executed, it can result in empty organization paths, which can then result in data access issues.  
Note:  
If you don't execute the business rules during import, run the script in the Update Organization Path business rule for the newly imported records to set the organization paths correctly.

