Basic Administration > Managing Data > Organization Administration > Understanding Organizations > Owning Organization Participants
  
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.
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.
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 auto-generated). How to turn off autonumbering is described in Changing Numbering Schemes.
For information about creating object initialization rules, see About Object Initialization Rules.
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 Numbering for Parts Owned by Multiple Organizations.