« BI Publisher licensing options for Agile PLM | Main | Enabling seamless processes between Agile PLM and SAP ERP »

Storing outbound compliance information in PGC

You obviously know that you can use a Declaration to gather compliance information from your suppliers. Those are inbound Declarations where the data is submitted by Suppliers or content providers. But, did you know you can also use a Declaration for storing "outbound" compliance to be shared with your Customers?

In PLM's 9.2.2.4 release, you can make use of the attribute Exclude from Compliance Check in Declaration-Items or Declaration-Mfr Parts or Declaration-Part Groups tabs. This is a list field with values of "Yes" and "No" and the purpose of this field is to use for "outbound" Declarations. Note that this is different from the Exclude from Rollup flag in the cover page of an Item. The Exclude from Rollup field flags the entire Item to be excluded from compliance rollup, while the Exclude from Compliance Check flags just that particular Declaration/Composition to be excluded from compliance rollup.

Here are the steps you can follow to create an "outbound" Declaration:

• Create a Declaration and add the top level assembly to that declaration. This is assuming that, you would have got compliance information for the components within that top level assembly.
• In the Declaration-Items tab, set the value of Exclude from Compliance Check to be "Yes" for that part. If this field is not vislble, you might need to make it visible in Java Client (Classes-->Declaration-->Items). You can also rename the field to something different (like "is outbound", "is for customer" etc) based on your use case. Make the same attribute visible in Java Client-->Classes-->Items-->Compliance-->Composition.

PGC1_1.jpg

• Add material/substance information for this top level product, based on the data in the components.
• Release the Declaration.
• Now, if you view the Item-Compliance tab, you would see the newly released Declaration but the Exclude from Compliance Check (if turned on) would have a value of "Yes" which indicates that this is an outbound Declaration.

PGC1_2.jpg

With this, you can store a Declaration specifically for outbound purposes and the 9.2.2.4 application will treat those Declarations differently during Compliance Rollup, when compared to regular Supplier Declarations.

TrackBack

TrackBack URL for this entry:
http://blogs.oracle.com/mte1521/mt-tb.cgi/6137

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

About This Entry

This page contains a single entry from the blog posted on September 22, 2008 8:00 AM.

The previous post in this blog was BI Publisher licensing options for Agile PLM .

The next post in this blog is Enabling seamless processes between Agile PLM and SAP ERP.

Many more can be found on the main index page or by looking through the archives.

Powered by
Movable Type and Oracle