Unique CAD Data/WTParts from one Organization to another Organization?

[SteveVinyard]

Hi guys, I'm really hoping someone can chime in here with some experience. I've run this down with PTC Techsupport and I'm getting a bunch of conflicting information.

Obviously I want two completely separate companies to live in the same Organization (CAD, WTParts, DOCs etc) with each being their own sovereign nation of part numbers/users. I want to be able to have CAD Model 12345.prt live in both orgs simultaneously without any uniqueness errors etc.

Jess@ptc do you know anything about this?


I got the following info from PTC Tech Support (Colorado Team - weak :/).

"As per R&D below they turned off the capability of having non-unique names across organizations in 10.0+. This is no longer available. Sorry if there was any confusion about this .

* Unable to create objects with the same Number in Different Organizations

* Reported to R&D as SPR 2182612
* Works to product specification for Windchill 10.1 all datecodes

The support for this is turned off by default as of 10.0. The reason for this is that support for Organization-level namespace as it used to exist did not cover all end use cases of business. For example, setting the namespace at the organization level can lead to problems in setting the owning organization value of an object that has been moved from one organization to another."

PTC Help Center Supports the solution below but also notes that it doesn't work for CAD Filename (asinine).
Note:
"CAD document file names must be unique across all organizations within the site, regardless of the business object uniqueness configuration. For example, if CADDoc1 exists within Org1, there cannot be a CADDoc1 in any other organization within your site. For more information, see the Using PTC Creo Parametric with PTC Windchill guide."


There is this PTC Knowledgebase Document on setting up a solution that supposedly fixes this (but see note above from help center).

* Subscribe to this Document<">https://www.ptc.com/appserver/cs/view/subscribe.jsp?type=solution&refresh=yes&callnum=CS34592>
Document Information
Type

Article

Date Created

31-Oct-2011 05:36:53 EDT

Date Last Updated

18-Dec-2013 10:14:48 EST


Document Details
Title

How to restrict Object Uniqueness to Organization level instead of Site level in Windchill PDMLink

Description

* How to restrict Object Uniqueness to Organization level instead of Site level
* Possibility to have objects with the same name and file number in different organizations
* Allow creating duplicate part number in different organization
* How to allow the same part or document numbers in multiple organizations
* How to configure business object uniqueness across organizations
* How to create a part with the same number in two different organizations

Applies To

* Windchill PDMLink 9.1 all datecodes, 10.0 all datecodes

Cause

* In a default configuration with multiple organizations, business objects such as parts and documents must be unique across all organizations within the site.

Resolution

* To configure a business object to be unique across organizations set the following properties in wt.properties using xconfmanager from a Windchill Shell:
* wt.inf.container.restrictCrossOrgDataUse=true
* wt.inf.container.orgNamespace=true
* Note: These changes need to be made before loading any data to prevent potential data corruption.
* For additional information refer to Windchill Help Center topics Configuring Business Object Uniqueness Across Organizations<">http://www.ptc.com/cs/help/windchill_hc/wc101_hc/index.jspx?id=WCInstall_ConfigBusinessObj&action=show> and Business Object Uniqueness Considerations<">http://www.ptc.com/cs/help/windchill_hc/wc101_hc/index.jspx?id=SiteAdminChp_BusObjUniqueConsideration&action=show>

[MikeLockwood]

Unless the EPMDOCUMENTMASTER table had a multiple-field primary key, how could the system handle?
[cid:image001.png@01CF5FB7.4F0E39E0]

Doesn't seem like a lot of wiggle room on this one.

[jessh]

I assume you meant jessh@ptc below.

That said, I almost missed this as I was only quickly skimming this
message because it involves issues so far from my areas of familiarity.
I've not had any contact with areas like CAD document namespacing since R8.

--
Jess Holle

[jessh]

ida2a2 is the internal primary key for any Windchill table.

It's not unrelated to any other set of attributes which may have a
uniqueness constraint applied to them.

[patrickchin2000]

Hi Steve,

It's been like this since Windchill 5.0 with WGM and now they have really pushed it across the board. Hence, Windchill is just another single Pro/I. I would really hate to have customers re-identify all their released drawing and models just due to a tool functionality limitation of WGM.

As I mentioned with past post, after saving the CAD package, all the member links and reference links will keep the package intact. Thus, when you open your drawing and assembly from Windchill, you will pull the configuration of your completely linked package.

I believe PTC is still working on it, at least I hope.

This is gold to PTC and they don't even know it for oracle:

SQL> CREATE UNIQUE INDEX EPMDocumentMaster$UNIQUE ON EPMDocumentMaster(documentnumber,doctype,authoringapplication,idA3organizationReference)
TABLESPACE INDX STORAGE ( INITIAL 20k NEXT 20k PCTINCREASE 0 );

SQL> CREATE UNIQUE INDEX EPMDocumentMasterFile$UNIQUE ON EPMDocumentMaster(cadname,authoringapplication,idA3organizationReference)
TABLESPACE INDX STORAGE ( INITIAL 20k NEXT 20k PCTINCREASE 0 );

In Reply to Steve Vinyard:

Hi guys, I'm really hoping someone can chime in here with some experience. I've run this down with PTC Techsupport and I'm getting a bunch of conflicting information.

Obviously I want two completely separate companies to live in the same Organization (CAD, WTParts, DOCs etc) with each being their own sovereign nation of part numbers/users. I want to be able to have CAD Model 12345.prt live in both orgs simultaneously without any uniqueness errors etc.

Jess@ptc do you know anything about this?


I got the following info from PTC Tech Support (Colorado Team - weak :/).

"As per R&D below they turned off the capability of having non-unique names across organizations in 10.0+. This is no longer available. Sorry if there was any confusion about this .

* Unable to create objects with the same Number in Different Organizations

* Reported to R&D as SPR 2182612
* Works to product specification for Windchill 10.1 all datecodes

The support for this is turned off by default as of 10.0. The reason for this is that support for Organization-level namespace as it used to exist did not cover all end use cases of business. For example, setting the namespace at the organization level can lead to problems in setting the owning organization value of an object that has been moved from one organization to another."

PTC Help Center Supports the solution below but also notes that it doesn't work for CAD Filename (asinine).
Note:
"CAD document file names must be unique across all organizations within the site, regardless of the business object uniqueness configuration. For example, if CADDoc1 exists within Org1, there cannot be a CADDoc1 in any other organization within your site. For more information, see the Using PTC Creo Parametric with PTC Windchill guide."


There is this PTC Knowledgebase Document on setting up a solution that supposedly fixes this (but see note above from help center).
https://www.ptc.com/appserver/cs/view/solution.jsp?n=CS34592

Document - CS34592

Document Actions
* Refresh Data<
* Subscribe to this Document<
Document Information
Type

Article

Date Created

31-Oct-2011 05:36:53 EDT

Date Last Updated

18-Dec-2013 10:14:48 EST


Document Details
Title

How to restrict Object Uniqueness to Organization level instead of Site level in Windchill PDMLink

Description

* How to restrict Object Uniqueness to Organization level instead of Site level
* Possibility to have objects with the same name and file number in different organizations
* Allow creating duplicate part number in different organization
* How to allow the same part or document numbers in multiple organizations
* How to configure business object uniqueness across organizations
* How to create a part with the same number in two different organizations

Applies To

* Windchill PDMLink 9.1 all datecodes, 10.0 all datecodes

Cause

* In a default configuration with multiple organizations, business objects such as parts and documents must be unique across all organizations within the site.

Resolution

* To configure a business object to be unique across organizations set the following properties in wt.properties using xconfmanager from a Windchill Shell:
* wt.inf.container.restrictCrossOrgDataUse=true
* wt.inf.container.orgNamespace=true
* Note: These changes need to be made before loading any data to prevent potential data corruption.
* For additional information refer to Windchill Help Center topics Configuring Business Object Uniqueness Across Organizations< and Business Object Uniqueness Considerations<

[ddemay]

Steve,



Sounds like you did your research and have your answer from a "supported"
standpoint. The architecture allows more though in 9.1, but haven't tried
this in 10.1.



I changed this for 9.1 to allow multiple numbers in the SAME organization,
BUT they had to be different format / type. So a ProE Drawing and a CATIA
drawing format could have same part number. A ProE Model and CATIA Model
could have same number. So essentially you could use same number three
times per format at least if also the platform type (drawing, part,
assembly, other files?) are unique. After three years of testing the
system, our customer was about to abort licensing Windchill for this one
reason!!



I'll provide what we did below using SQL.



Could someone as an admin move it to another organization? Possibly, but you
couldn't move everything easily until 10.1 M030 when all revision and
iterations aka the entire mastered object. Basically, this wasn't a business
case for us. Each org could see the other's data, but neither could move
data to the other organization or modify any means (Exception: unreported
bug - if user creates workspace under container which they have read
permission to. Newly created object pick up other org on upload to server
workspace. Not number specific though.)



I think PTC changing this in 10.x is a response to the increasing popularity
of windchill systems utilizing multiple organizations.



Final NOTE: We had to revert this SQL PRIOR TO UPGRADE - essentially by
appending the ida2a2 with a hyphen to wtkey and post upgrade removing it via
SQL.





Here is the 10.1 M040 SQL used to control things (not sure if any code was
added in 10.x):



CREATE UNIQUE INDEX "WINDAPP"."EPMDOCUMENTMASTERKEY$UNIQUE50" ON
"WINDAPP"."EPMDOCUMENTMASTERKEY" ("WTKEY", "IDA3ORGANIZATIONREFERENCE",
"IDA3NAMESPACEREFERENCE")

PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS

STORAGE(INITIAL 24576 NEXT 24576 MINEXTENTS 1 MAXEXTENTS 2147483645

PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT
FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)

TABLESPACE "INDX" ;





Here is the 9.1 SQL modified:



DROP INDEX wcm050db.EPMDOCUMENTMASTERKEY$UNIQUE;



CREATE UNIQUE INDEX wcm050db.EPMDocumentMaster$UNIQUE ON
wcm050db.EPMDocumentMaster(documentnumber,doctype,authoringapplication,idA3o
rganizationReference);



CREATE UNIQUE INDEX wcm050db.EPMDocumentMasterFile$UNIQUE ON
wcm050db.EPMDocumentMaster(cadname,authoringapplication,idA3organizationRefe
rence);



commit;







Regards,

David DeMay