Note

The site administrator user who created the organization is owner of the organization and is the user identified in the Owner attribute on the organization information page. (The organization owner of the initial organization created during installation is the administrator user that was identified during installation, by default wcadmin.) The organization owner can be changed to another user by editing the organization.

For a description of the contents of the templates, see Out-of-the-box Organization Templates on page 151 .

Owning Organization Participants

Parts or documents created within an organization context are automatically owned by the organization participant associated with the organization context. However, the site can choose to allow users to specify a different organization participant, such as one associated with an external vendor or supplier, as the owner of an object. For example, if a part used in a part structure is acquired from a vendor, you can create an organization participant for that vendor, and select that vendor’s organization participant as the owning organization for the part.

To change the out-of-the-box functionality so that a user who creates a part or document can specify which organization participant owns the part or document, you must do the following things:

•Set up domains for use with owning organizations. For more information, see

Setting Up Domains for Use with Owning Organization Participants on page 161 .

•Create or update organization participants to be used as owning organizations, sometimes referred to as internal organizations. For more information, see Creating and Updating Owning Organization Participants on page 161

•Enable the appropriate preferences to display the owning organization on objects, using the Preference Management utility:

○Expose Organization – Displays the organization for all objects except

change objects.

○Expose Organization for Change Management Objects – Displays the

organization for change objects. The Expose Organization preference must also be enabled.

•Configure the context where the parts or documents will reside so that the user enters the part or document number (rather than having the numbers autogenerated). How to turn off autonumbering is described in the PTC Windchill Specialized Administration Guide.

For information about creating object initialization rules, see the help available from the Object Initialization Rules Administration utility.

An alternative to having the user enter the part of document number is to set up object initialization rules for parts and documents that automatically set different numbers depending on the owning organization.

For an example of the XML elements that can be used in an object initialization rule to set this up, see the PTC Windchill Specialized Administration Guide.

Setting Up Domains for Use with Owning Organization Participants

To allow users to identify the ownership of parts and documents that are created in the solution with external vendors and suppliers, the organization participants created for vendors and suppliers must be in a domain that allows the users read access to the organization participant.

A simple approach to setting this up is the following:

1.Create a domain that will be used specifically for this purpose. For example create the /Vendors domain using the Policy Administration utility from the site context.

2.Create the access control rule in the Vendors domain that grants READ permission on WTOrganization objects to ALL users.

3.When creating the organization participants that represent external vendors and suppliers using the Participant Administration utility, select the /Vendors domain for the Windchill Domain field.

For more information on domains, see Managing User Access to Data on page 34

Creating and Updating Owning Organization

Participants

Use the Participant Administration utility to create a new organization participant or update an existing organization participant for use as an owning organization by including the following attributes on the participant:

•The Organization ID attribute indicates the type and value that is specified for the globally unique organization identifier under which the organization is registered. Select the type from the drop-down list. By default, the drop-down list contains CAGE Code, DUNS Number, and ISO 6523.

Note

The organization identifier, such as a CAGE code or DUNS number, is an internationally coded number that is assigned when the organization registers with a specific site. For site registration information, see the Registration Authority

If the drop-down list does not contain the type required, you can specify a new list by adding the wt.org.organizationTypes property to the wt.properties file. The wt.org.organizationTypes property value is a comma-separated list of coding systems, where each coding system has two parts in the following format:

<ICD_number>/<coding_system name>

where:

<ICD_number> is the international code designator number assigned to the coding system. For example, the CAGE ICD number is 0141. For a list of ICD numbers, see the Registration Authority

<coding_system_name> is the name of the coding system.

If the wt.org.organizationTypes property does not exist in the wt.properties file, then the following wt.org.organizationTypes property value is used:

0141/CAGE Code,0060/DUNS Number,0026/ISO 6523

If you add the wt.org.organizationTypes property, be sure to include all coding systems that you want to appear in the drop-down list. For example, to include CAGE Code, DUNS Number, and GTE/OSI Network, set the wt.org. organizationTypes property by entering the following xconfmanager command from a windchill shell:

xconfmanager -s wt.org.organizationTypes="0141/CAGE Code,0060/DUNS Number,

0126/GTE/OSI Network" -t codebase/wt.properties -p

Note

After restarting the method server with the above property set, the drop-down list contains CAGE Code DUNS Number and

GTE/OSI Network but not ISO 6523