Hi Vikekkumar,

thank you for your reply,

here are some questions:

1. About the substance repository:

– What are the steps that are mandatory for the approval of a flow of implementation / review of a chemical composition linked to a product?

– What are the business requirements (Ex: during the product development project)?

– Access restrictions: how access segmentation of sensitive information was implemented?

– What type of report is extracted, by CAS number or substance?

1. About Compliance:

– Who updates the information, given the number of applications for a product and countries of sale? Is there any intelligence behind that can streamline regulatory analysis?

– How long did it take to implement the module and the main areas involved?

Hi Surya, 

are you importing into a Change Order? If the items are approved you should use a change order.

My best
Carlos

Hi Laura,

you`ll need some sort of process extension for this validation, it`s a simple one, when you add an item to the BOM, an event called “update table”, it should trigger the validation process extension (groovy code) that will prevent that an item in the wrong lifecycle phase to added to a BOM.
Smart rule only validates if the BOM item is released or not, so it`s just part of the solution.

My best
Carlos

Hi Vaibhav,

there is a type of list, called cascade, where you can create validations for possible attribute values. It`s different from Oracle EBS where you have two attributes, the first attribute value validates the possible values in the second, in Agile PLM you have basicaly the same feature, but in one list type attribute, called cascade list.

My Best
Carlos

Hi Kraig,

I don’t believe you`ll find a way to change part’s number systematically based that the import tool uses the part number as an unique identifier for items, I don’t recommend you update database tables as well. So, I`d suggest you proceed this way:
– create an attribute called, let`s say, legacy code, and using export/import tool update all new attribute with the old part number, just for audit and traceability purposes.
– Build some sort of robot, perhaps using DataLoader tool, to change “manually” all the part numbers as required, it`ll take some time but is low cost and secure.

Though, you always can write a process extension to do so, I didn’t mentioned it before because you asked for a systemic approach.

My best
Carlos

Hi Kshama,

you’ll need to write an process extension that will validate the kind of item been adding to the BOM.
It has to not proceed if the validation criteria is not met, it can show the error to help users figure out what’s going on.

My best
Carlos

Mathison,

just explaining the Patrick’s suggestion a little bit further, in the workflow step criteria there’s a filed called “Notify upon entry”, there you can add user groups or users and every time a change reaches that step all the users will be notified. Please refer to the attached file for details.

My best
Carlos

Hi PDASANAPU,

phantom parts are created because a business need, the majority of the phantom parts are assemblies used to facilitate some process step like planning, purchasing, assembling or any other specific reason that a particular business have. I agree with you that, in general, fastenings and piping elements are purchased parts in business those use these parts, not manufacturer them.
I`d suggest you to ask for the reason, probably it`s a business specific need or procedure.
My best
Carlos

Hi Is09

with Authority transfered, the destinatary should receive all the needed permissions, so it’s not necessary to both users to have the same roles previously. Anyway, the important to consider is that the destinatary should be able to approve changes submitted after the Authority has been granted.
So verify dates  when the changes were submitted and compare to date when the authority was granted.
If it matches, I’d suggest you to raise an Oracle SR.

My best

Carlos

Hi newbie,

here comes some questions that you must answer before any movement towards the execution of the integration.
– What do you intend to do, are you decommissioning the legacy PLM or do you intend to keep both in parallel?
– is there 3D files?
– is there project execution data to integrate?
– Have you a way to extract metadata and data from the legacy?

My best
Carlos