Oracle Engineering setups for deploying the Design to Release PIP
By Anurag Batra on Apr 09, 2009
One of the most common questions that customers ask us before deploying the Agile PLM - e-Business Suite integration using the Design to Release Process Integration Pack (PIP) is - Do I need to implement Oracle Engineering? The answer is - not really. All you need to do is a few very simple setups that can be done in matter of minutes.
First, you need to make sure that the Engineering application is available, and assign access to Engineering functions through a responsibility such as "Engineering" to at least one Engineering Manager. Now, this manager is not expected to get trained on anything, or even use this set of functions heavily, if at all. It'd at least give him access to the screens that he needs to do the very basic setup described below. You should also give this access to the user that'd be used by the e-Business Suite ABCS to post data to the application.
Next, you need to define Change Types corresponding each of the subclasses of change orders that shall be pushed to ERP from the PLM system. This'd typically include setting up an ECO and MCO change type, and maybe others depending on your Agile setup and mappings to e-Business Suite. This is a simple setup as you can see in the illustration here.
Another setup that needs to be done in most cases is that of the profile option "ENG: Require Revised Item New Revision", which should be set to "No" if you'd be transferring any type of MCOs or SCOs (changes that don't allow rev rollup in Agile).
The final setup that needs to be done (again, in most cases) is to schedule the concurrent program "Engineering Change Order Implementation" (aka auto-implemention manager) at a convenient frequency. You should do this if you've configured the integration to interface change orders from PLM in a "Scheduled" status, and if you'd like change order lines to be automatically implemented when the mapped effectivity date arrives. You don't need to do this setup if you've configured the integration to publish ECOs in an "Open" status, or if you'd like to manually control the implementation of ECOs in e-Business Suite. You can schedule this concurrent task to run at a frequency in-line with your ECO volume and desired turnaround time. Large corporations with tens of ECOs every day may run it every 5 minutes. Smaller companies with only a few ECOs every day or week may run it every 15 minutes or hourly.
That's it - you're now ready to configure the PIP to start publishing to Oracle Engineering.