How to assign CAGEcode for a Product container and all objects created in the container

[SL_10932999]

I am using Windchill PDMLink Release 12.1 and Datecode with CPS 12.1.2.0

We have a requirement for creating an Organization with 2 Sites with different Cage code. When creating a Product context how do we make sure that a product belongs to a particular Site and all objects created in the product gets the Cage code of the particular Site.

[apatil-2]

Cage code is something which is part of Org container. When you create any part in a product container, it will be associated with the cade code where the product is present, you can verify this by looking at its hyperlink.

[BenLoosli]

Can you set the OIR at the product level, instead of the Org level? This would define the Windchill top folder for ne objects. In Creo, use a relation to determine which product the object is going to and set the CAGE code.

[mmeadows-3]

What is the purpose of your cage code?  Is it an application context attribute or the context just drives what value to use?  Is this a CAD Document, Part, or Document attribute?  Are you showing it on drawings, tagging it in BOMs, or something else?

Windchill is structured with one "site" and multiple "organizations".  Each organization can have a difference cage code (PTC's OOTB attribute) assigned to it.

Just guessing at your use case...  Define a unique 'cage code' IBA (e.g. CAGE_CODE).  This is not the organization's cage code and will not impact object uniqueness.  Then use OIRs as @BenLoosli suggests to set the value based on the context.  Then it becomes an attribute you can use it in drawings, BOMs, etc.

[SL_10932999 · Accepted solution]

Hello @mmeadows-3 @BenLoosli @apatil-2 

Thanks a lot for your response, this gave me a clarity!

The problem we had is a client wants to manage data in a single organization, but client has 2 locations each with different CAGECode (same ACLs, OIRs applicable all over the organization except default organization-ID for objects created).

Idea I tried to cross check is that :
- create 2 lightweight organizations (or Organization participant) with each location's CAGECode

- somehow assign it to Product containers during creation, so that all objects created in those product container are with assigned CAGECode instead of default Orgnanization ID. 

I wanted to avoid product level OIR because -
1. it doesn't work for CAD objects when it is being created in workspace, we might have cases where standalone CAD objects created without any relation
2. to maintain all OIRs only at Org level for easier maintenance. 

However, I see that is not at all possible & its confirmed by PTC.  So, finally we decided go with OIR + Exposing organization so that user can choose their locations CAGECode during CAD check-in.