You could do this directly in the tables BUT PLEASE PLEASE PLEASE thoroughly before doing any of this in production…. just need to say that just cause I have seen so many issues….  best of luck.

On a mass scale?  Please give it a shot and let us know what you think?

Unreleased is not the way to go here.  Once you change release an item there really is no ‘good’ way to delete it.  

Here’s the catch.  Although unreleasing the item can in fact allow you to delete you raise risk to other processes.  In the database itself, the release process will populate the data in different tables.  Additionally, in a mature environment we quite usually have event processes that trigger PX’ and unreleasing can in essence break these processes and you would have bad data and subsequent issues downstream.

The only option you have now it to raise another change order and OBSOLETE this item.

I believe you may be seeking an out-of-box report and the answer is…. well, I have never seen one.

I suggest sql query to find this info.  Additionally, note this will be looking at the history information which is difficult to query at times.

Are you trying to dynamically run this report?  Or are there certain changes you wish to achieve?  What changes are you seeking?

Many different ways… depends on how deep your pockets are and to what level of control of data you want to achieve.

For MES I have achieved the following;
PN release information feeds MES to control WIP stock into tools and through tools.
Additionally PN release information feeds LMS (learning management system), subsequently feeding MES to control technician login to tool.

For ERP,
PN release information feeds ERP to trigger various events;
Costing cycles
Procurement
Stock
Sales
etc….

There are so many different ways to sketch this out.  Perhaps start with your basic company processes and explore where the enterprise systems touch.  Then you can seek to understand the automation and collaboration they bring to your model.

To be clear, you want your view in Agile PLM BOM tab to be the same as that in the ERP?  If yes, then, although it won’t be exactly the same, you can change the columns in the JAVA Admin client to be as close as possible.

Forums and blogs will not be a good path to success on this.  You will need to have an experienced resource help you out.  This will help to alleviate any potential issues and prove to be quickest path to success.  You can of course do this on your own, but time and time again I have seen problems and the additional resource is well worth the cost.

Because the process is totally up to you.

Your company policies and practices would dictate it.

Do you have contractual obligations?  Regulatory requirements?  Warranties? etc….

As a standard default I would say the following lifecycle is most common…

UNRELEASED
ENGINEERING
NPI (New Product Introduction or Beta trials, limited release)
RELEASE (full scale production)
END OF LIFE (no further procurement or production)
OBSOLETE (no further support)

In reference to technical terms…. Agile PLM only should not allow END OF LIFE or OBSOLETE items on new BOMs.  The rest of the functionality would most likely be driven in the ERP EBS.