Agile Product Lifecycle Management Integration Pack for Oracle E … · Management Integration Pack...

© 2008 Oracle Corporation – Proprietary and Confidential1

Agile Product Lifecycle Management Integration Pack for Oracle E-Business Suite: Design to Release 2.5

PIP Installation and Configuration Procedures – Part 2


Disclaimer:This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Software License and Service Agreement or other applicable contract with Oracle, with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced ordistributed to anyone outside Oracle without Oracle‟s prior written consent. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

This document is for informational purposes only and is intended solely to assist you in planning for theimplementation and upgrade of the product features described. This is not a commitment to deliver any material,code, or functionality, and should not be relied upon in making purchasing decisions. The development, release,and timing of any features or functionality is always at Oracle‟s sole discretion. This document is not consideredpart of the applicable program documentation.

Due to the nature of the product architecture, it may not be possible to safely include all features described in this document without risking significant destabilization of the code.

Purpose:This document provides an overview of install procedures for the Agile Product LifecycleManagement Integration Pack for Oracle E-Business Suite: Design to Release 2.5. It is intended solely to help you assess the business benefits of upgrading your existing Oracle products to Release 2.5, or implementing completely new Oracle developed products, and planning your I.T. Projects.


Agenda

PART 1

• Software Pre-Requisites

• Pre-Requisites and Patches

• Pre-Installation Configurations for Foundation Pack (FP) and PIP Installs

• Foundation Pack and PIP install

• Post Install Instructions and Validations

• Applying Patches Post FP and PIP Install

• Setting up Participating Applications – Ebiz

• Resources

• Questions

PART 2

• Setting up Participating Applications – Agile

• Create new JMS destination

• Create events

• Define and modify filters

• Create and enable new subscribers

• Set privileges

• Modify flex fields

• Setting up Auto number process extensions

• Variant management set up

• Resources

• Glossary

• Questions


PIP Installation and Configuration

Setting Up Participating Applications - Agile

The following settings need to be done on the Agile java client

As always, please follow Implementation Guide 2.5, Setting Up Participating Applications as well

The values in the table will be used to set up JMS destinations

Field Value/Setting

Name Define your own

API Name Same as the name, without spaces

Response Expected No

User Nameoc4jadmin (SOA server admin user name)

Password welcome1

Provider Context Factory

com.evermind.server.rmi.RMIInitialContextFactory

Connection Factoryjava:comp/resource/EcoRP/QueueConnectionFactories/QCF

Default Provider URL opmn:ormi://<SOAServer>:<OPMNPort>:<instance-name

Destination Namejava:comp/resource/EcoRP/Queues/PLM_ECO_QUEUE



Setting Up Participating Applications – Agile, cont.,

Create a new JMS Destination:

Log into the Agile java clientIn the Admin tab, go to System Settings > Agile Content Service > DestinationsClick on the icon to create a new destination

Create a new JMS Destination:Log into the Agile java clientIn the Admin tab, go to System Settings > Agile Content Service > DestinationsClick on the icon to create a new destination




For the Protocol, select JMS Enter the values as seen on the slide

Make sure to test the destination (use second icon on top of page)

Leave certain fields blank, as seen on the slide

Save




Create Events:

• In the Admin tab, go to System Settings > Agile Content Service > Events

• Create New Events for ECO, MCO and SCO

• Create separate Events for CO Release and CO Validation

• Enter the following as seen in the table:

Note: Please see examples in the next several slides. The example is for ECO, you will need to do the same set up for MCO and SCO

ECO MCO SCO

Name Define your own Define your own Define your own

Event Type Workflow Workflow Workflow

Workflow Default Change Order

Default Manufacturer Orders

Default Site Change Orders

Field Value/Settings

Workflow Status For CO Release Process - Released

For CO Validation Process - Any status other than 'Released'. Preferred status is 'Submitted'.




Leave the Frequency default value







Define and Modify Filters:

• In the Admin tab, go to System Settings > Agile Content Service > Filters

• Modify default Item filter as described in the table

Field Value/Setting

Object Type Items

View Tabs Add Sites, Title Block, Page Two,

Page Three, BOM, Manufacturers

BOM Options Tabs and Items

BOM LevelsSelect All Levels checkbox

AML Options Tabs and Manufacturer Parts

Attachment Options Tab only

Include File Attachments

Leave blank




Modify the following filters:

• Still On the filter tab, go to the following additional filters for modification:

• Default Change Order Filter

• Default Manufacturer Order Filter

• Default Site Change Order Filter

• Please see examples on the following next 3 slides

Change Order Filter

Manufacturer Order Filter

Site Change Order Filter

Object Type Change Orders Manufacturer Orders Site Change Orders

View Tabs Page Two, Attachments, Page Three, Affected Items, Cover Page

Page Two, Attachments, Page Three, Affected Items, Cover Page

Page Two, Attachments, Page Three, Affected Items, Cover Page

Affected Items Options Tabs and Items Tabs and Items Tabs and Items

Redline Changes Only No No No





Modify ECO filter

Leave “Include File Extensions” blank




Modify MCO Filter





Modify SCO Filter



PIP Installation and Configuration Setting Up Participating Applications – Agile, cont.,

Create New Subscribers:

• In the Admin tab, go to System Settings > Agile Content Service > Subscribers

• Create 6 new subscribers (2 ECOs, 2 MCOs and 2 SCOs)

• For each ECO, MCO and SCO, create subscribers for Validate and Release

• Follow the table on the next slide for the correct settings

• For all the subscribers you set up, leave the “Include modified objects” field with the default value of “no”




Create New Subscribers, cont.,

For ECO For MCO For SCO

Name ECO-Validate or ECO-Release MCO-Validate or MCO-Release SCO-Validate or MCO-Release

API Name ECOValidate or ECORelease MCOValidate or MCORelease SCOValidate or MCORelease

Description For ECO Validate or For ECO Release For MCO Validate or For MCO

Release

For SCO Validate or For

SCO Release

Subclass ATO ATO ATO

Workflow Default ATOs Default ATOs Default ATOs

AutoNumber ATO Number ATO Number ATO Number

Criteria All Change Orders All Manufacturer Orders All Site Change Orders

Event ECO-Validate or ECO-Release MCO-Validate or MCO-Release SCO-Validate or MCO-Release


The next 6 slides are examples of the settings in the table




Create New Subscribers, cont., - ECO




Create New Subscribers, cont., - MCO




Create New Subscribers, cont., - SCO




Enter the Subscriber Details:

The detail portion of the Subscribers needs to be completed:

• In the Admin tab, go to System Settings > Agile Content Service > Subscribers

• Go into the 6 subscribers for ECO, MCO and SCO that you just created

• For each one, go into the Subscriber Details Tab

• After you are done with the detail section, go back and enable the newly created subscribers

• See the next 3 slides for examples

• The first slide is a table with all the values

• The next two slides are examples for ECO

• Make sure to complete the subscriber details for MCO and SCO in the same manner

NOTE: The only difference is the values in the “Filter” field




Enter Subscriber Details, cont.,

For ECO For MCO For SCO

Destinations Select the JMS Destination that you created. (your FMW box)

Select the JMS Destination that you created. (your FMW box)

Select the JMS Destination that you created. (your FMW box)

Filter Default Change Order Filter and Default Item Filter

Default Manufacturer Order Filter and Default Item Filter

Default Site Change Order Filter and Default Item Filter

Roles All All All

Format aXML aXML aXML

Language English English English

Site All All All




Enter Subscriber Details - ECO-Release




Enter Subscriber Details - ECO-Validate




Enable Subscribers:In the Admin tab, go to System Settings > Agile Content Service > SubscribersHighlight each subscriber and click on the third icon (right side of the delete icon) to enable the subscriber. Close the page, it will be saved



Set privileges: ECOs

In the Admin tab, go to User Settings > Privileges > Under the Privileges, you will see lots of existing privileges Click on the “Modify” privilege, then click the apply buttonThis will display all the different “Modify” privileges in existenceA new Modify privilege needs to be created for ECO, MCO and SCOTo create a new privilege, click on the first icon on the top leftThe criteria field is different for each privilege: (they were created in the Subscribers)

ECO - All Change OrdersMCO - All Manufacturer OrdersSCO - All Site Change Orders

In the “Applied to” field, click on the icon to bring up a screen with Choices and Selected columns

Uncheck the “show visible attributes only” checkboxHighlight all the choices and click on the right arrow to place them under the Selected columnClick OK and then OK again Other than the name and the criteria everything is the same for the ECO, MCO and SCOPlease see next slide for the Creation of the ECO privilege example and make sure to create a privilege for MCOs and SCOs



Set Privileges: ECOs, cont.,

• After you hit OK twice from the previous slide, you will be taken to another screen; go into the “Where Used” tab

• In here, you will create roles to the new privileges

• Select the first icon on top to add roles



Set Privileges for ECOs

• Select the Administrator role and put it under the Selected column

• Click OK and close the page

Next, create a privilege for MCOs and SCOs in the same manner



Create new read privilege –MCO

After the privileges have been created for ECOs, MCOs and SCOs, a new “Read” privilege for MCO needs to be created

In the Admin tab, go to User Settings > Privileges > Read

Click on the “Apply” button to see the existing privileges (top right, not shown)

To create a new privilege, click on the first icon on the top left



Create new read privilege – MCO, cont.,

Give it a name, such as “ReadMCOs”, complete the API and descriptions Enabled: yesPrivilege: Select “Read” Criteria: All Manufacturer Orders

In the “Applied to” field, click on the icon on the rightThis brings up a screen with Choices and Selected columns

Uncheck the “show visible attributes only” checkboxHighlight all the choices and click on the right arrow to place them under the Selected columnClick OK and then OK again



Add a new role for the Read Changes privilege

Go into the existing Read Changes privilege under: Admin tab > Settings > User Settings > Privileges > Read



Add a new role for the Read Changes privilege, cont.,

Go into the “Where Used” tabGo to the icon to add roles (first icon on left)Select the Administrator role from the Choices column and put it under the Selected columnClick OK and close the page

Add a new role for the Read Items privilegePlease follow the above procedures for Read Changes, beginning with slide 30

NOTE: The user should have privileges to modify the “released” items



Modify Flex Fields - Agile Attribute Configuration

A few attributes have to be configured in Agile which will be updated by the Reverse Flow

process

• Look in the AIAConfigurationProperties.xml file, located in the Fusion Middleware Box under:$AIA_HOME/config

<ModuleConfiguration moduleName="Agile">

<Property name="LANG_LOCALE">English</Property>

<Property name="MULTISITE_ENABLED">TRUE</Property>

<Property name="Item.UnitCostAttribute">Site.Numeric01</Property>

<Property name="Item.AvailableQuantityAttribute">Site.Numeric02</Property>

<Property name="Item.OnHandQuantityAttribute">Site.Numeric03</Property>

<Property name="Item.ReservedQuantityAttribute">Site.Numeric04</Property>

<Property name="Change.TransferStatusAttribute">PageTwo.Text02</Property>

<Property name="REPLICATE_BOM_ENABLED">FALSE</Property>

<Property name="COMMON_BOM_ENABLED">FALSE</Property>

</ModuleConfiguration>

The highlighted values will be used to set up the flex fields

NOTE: If MULTISITE_ENABLED“ = TRUE, the property for Item attributes will be using Site.

If Single site implementation is being used (value = false), the same attributes have to be configured on

Page Two/Page Three of Parts and Documents. This power point gives examples of Site only.



Modify Flex Fields - Agile Attribute Configuration, cont.,

The table below reflects the comparable Ebiz EBO fields (informational)

Agile Ebiz

Item.UnitCostAttribute Manufacturer Cost

Item.AvailableQuantityAttribute Available Quantity

Item.OnHandQuantityAttribute On Hand Quantity

Item.ReservedQuantityAttribute Reserved Quantity



Modify Flex Fields - Agile Item Attribute Configuration

• In the Agile Java client, go to the Admin tab > Data Settings > Classes > Items > Parts



Modify Flex Fields - Agile Item Attribute Configuration, cont.,

Go to the User Interface Tabs and click on Sites




On the Sites page, go to the Attributes:Sites tabOn the Filter by Type, choose NumericThis will bring up all the Numeric fields that are available

You will see Numeric01, Numeric02, etc., under Site

These are the values in the AIAConfigurationProperties.xml file, as mentioned in slide 32 (in this slide, the names have already been modified)




Select Numeric01 and modify as follows:

Name = UnitCostAttributeAPI Name = UnitCostAttributeDescription = Unit Cost AttributeVisible = yesUse defaulted values for the restClick Save

The next slide has values for the next 3 numeric flex fields





• Select Numeric02 and modify as seen below• Name = AvailableQuantity

• API Name = AvailableQuantity

• Description = Available Quantity

• Visible = yes

• Use defaulted values for the rest

• Click Save

• Select Numeric03 and modify as seen below• Name = OnHandQuantity

• API Name = OnHandQuantity

• Description = OnHand Quantity

• Visible = yes


• Click Save

• Select Numeric04 and modify as seen below• Name = ReservedQuantity

• API Name = ReservedQuantity

• Description = Reserved Quantity

• Visible = yes


• Click Save




• While still in the Agile java client, go to Admin Tab > Settings > Data Settings > Classes > Items

• Select Documents

• Do the exact same thing for Documents as you did for Parts in the previous slides

• Go to the User Interface Tabs and select Sites

• Go to the Attributes: Sites tab

• For the Filter by Type: select Numeric

• Again, you will see field names of Numeric01, Numeric02, Numeric03, Numeric04



Modify Flex Fields, cont., - Change Transfer Status Attribute Configuration

AIAConfigurationAttributes.xml file <Property name="Item.UnitCostAttribute">Site.Numeric01</Property>

<Property name="Item.AvailableQuantityAttribute">Site.Numeric02</Property><Property name="Item.OnHandQuantityAttribute">Site.Numeric03</Property><Property name="Item.ReservedQuantityAttribute">Site.Numeric04</Property><Property name="Change.TransferStatusAttribute">PageTwo.Text02</Property>

Note: The text attribute which will be enabled should be same in Page Two of all the three classes –Manufacturer Orders, Site Change Orders and Change Orders.( i.e. if Text02 is enabled in Change Orders Page Two, Text02 should be used for the other two classes also.

Steps to Configure for Manufacturer Orders (example): Log on to Agile Java Client

See next several slides



Modify Flex Fields, cont., - Change Transfer Status Attribute Configuration, cont.,

Manufacturer Orders - Go to Admin > Data Settings > Classes > Changes Tag > Manufacturer Orders (for MCO) > User Interface Tabs




Manufacturer Orders – Select Page Two



Modify Flex Fields, cont., - Change Transfer Status Attribute Configuration, cont.,Manufacturer Orders

Go into the Attributes:Page Two tab

Filter by: Text

Select: Text02



Modify Flex Fields, cont., - Change Transfer Status Attribute Configuration, cont.,Manufacturer Orders

Rename it to „Transfer Status‟

Set the “Visible” field to Yes

Leave the rest with the values that defaulted




Steps to Configure – Site Change Orders:

• Log on to Agile Java Client

• Go to Admin > Data Settings > Classes > Changes Tag > Site Change Orders (for SCO) > User Interface Tabs

• Follow the steps for Manufacturing Order (previous slides)

Steps to Configure – Change Orders:

• Log on to Agile Java Client

• Go to Admin > Data Settings > Classes > Changes Tag > Change Orders (for ECO) > User Interface Tabs

• Follow the steps for Manufacturing Order (previous slides)



• Create Auto Number Process Extensions for New Part Request (NPR):

• Go into the Agile java client

• Admin tab > DataSettings > AutoNumbers

• Click on the first icon on top left to create auto numbers for subclass

Make sure that patch 10378928 was applied, before you create the Auto Numbers



Create Auto Number Process Extensions for NPR, cont.,Complete the Define AutoNumber screen as shows below

In the “Where Used” field select: Part Click OK.

For the Custom AutoNumber select: “com.oracle.aia.npr.V2.NPRAutoNumber and click OK



Create Action Menu based Process Extensions for NPR:

• Navigate to Admin > Data Settings > Process Extensions

• Click the top left icon to create the process extension

• Enter the details as seen in the screen shot, Click OK



• Navigate to Admin > Data Settings > Classes

• Double click on Items in the

Classes window

• Select the Process Extensions tab

• Click the icon on top left to open Assign Process Extensions window

• Select NPR Number from the choices and drag it to the Selected List column

• Click OK, and close the window

Create Action Menu based Process Extensions for NPR, cont.,



• Navigate back to Admin > Data Settings > Process Extensions

• Double click on “NPR Number” that you created in the previous slides

• Select the Where Used tab

• You should see Base Class under Type

• Close window

Create Action Menu based Process Extensions for NPR, cont.,



• Navigate to Admin > Data Settings > Process Extensions

• Click on top left icon to create the Process extension

• Complete the fields as shown in the screen shot

• Click OK

Create Action Menu based Process Extensions for Sync Item



• Navigate to Admin > Data Settings > Classes

• Double click Items in the Classes window

• Go to the Process Extensions tab

• Click on the icon to open Assign Process Extension

• Select Sync Item and drag it under the Selected List column

• Click OK and close the window

Create Action Menu based Process Extensions for Sync Item, cont.,



• Navigate back to Admin > Data Settings > Process Extensions

• Double click on “Sync Item” that you created in the previous slides

• Select the Where Used tab

• You should see Base Class under Type

• Close window

Create Action Menu based Process Extensions for Sync Item, cont.,



Notifications can be setup in Agile PLM to send email when error occurs during ACS processing in the change order release process integration flow

To set up the notifications:

• Log in to Agile Java Client

• In the Admin tab, navigate to System Settings > Agile Content Service > Destinations

• Open the destination that was configured for the change order release flow to send the data to the JMS queue

• In the Notification User field, add the users and user groups who need to be notified on failure of ACS transfer

• Save the changes

Set Up Agile Notifications



Variant Management: Enable Notification

If Agile 9.3 with VM or 9.3.1 with VM was used during the PIP install, the following set up needs to be completed

From the Agile java client go to: Admin Tab > Server Settings > Database

Notification Enabled = Yes



Variant Management: Enable Notification, cont.,

Navigate to System Settings > Notifications

In the Filter By field, select Name

In the Value field enter Part

Click ApplyOpen Parts - Part Send




In the Part Send window:Enabled = Yes

Notification Type = Inbox




The following settings are user specific settings

Go to Admin Tab > User Settings > Privileges > Send

In the Filter By field select Name

In the Value field, enter Send Item

Click Apply (top right, not shown)

Open Send Items




Enabled = Yes

The current user has to have a role assigned that contains the privilege 'Send Item'

Go to User Settings > UsersMake sure the current user has roles assigned that contain the privilege 'Send Item„

Save and Close




The instructions on this page are not needed for Agile 9.3.1

Go to Admin > User Settings > Privileges > Read

Search on Read Items

Once Read Items is displayed, drill into it




The instructions on this page are not needed for Agile 9.3.1

In the “Applied to” field, uncheck the “Show Visible Attributes Only”

Drag “Items.Relationships.Relationships.Type” to the Selected column

Click OK, and Close




Go to Admin > User Settings > Privileges > Modify

Create a new privilege for Modify called “Modify Model(first icon on the top left)

Enabled = YesPrivilege = ModifyFor the Privilege Criteria column select All Models. If you cannot find this, you will need to create All Models criteria (the second icon by the Criteria field will let you create a new criteria (see next slide)

Once the Criteria is complete, go into the “Applied to” field icon and uncheck the box at the bottomDrag all the choices to the Selected columnOK, and Close




How to create a new Criteria, if needed




Go to Admin >User Settings > Privileges > Read > Read Users

In the Applied To field, drag over to the Select column “users.Preferences.BOM Variant Configuration Preference”

OK, and Close




Go to Admin > User Settings > Privileges > Modify > Modify Users

In the “Applied To” field, make sure that the “users.Preferences.BOM Variant Configuration Preference” value is in the Select column. If it isn‟t, drag it over

OK, and Close




Go to Admin > User Settings > Roles

Create a new Role for VM called “VM Role1”(first icon on the top left)

Enabled = YesPrivilege = Modify ModelUser/Groups = Search for Administrator/admin and drag that to the right side column

OK, and Close




Go to User Admin > Settings > Roles

Go into the new VM role that was just created

Select the Users tab and go into the User that has Administrator as the last name

In the General Info tab, make sure there is a first name and something under e-mail address. ( you can use “a” for both the first name and for the e-mail). Save

Go into the Preferences tab;For the BOM Variant Configuration Preference, select “External Configurator”

OK, and Close




Variant Management, cont.,

• Using the remote desktop, logon to the Agile server with the proper credentials

• 2 agile.properties file need to be modified with the SOA_host/port in the following locations:

• C:\Agile\Agile931\agileDomain\config\agile.properties

• C:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\Agile\APP-INF\classes\agile.properties

• In each file, search for: aia.cfg.endpoint.getURL and modify the line by replacing the tokens for SOA_HOST, SOA_PORT and the variable for the Configurator with the valid values (see example below)

• aia.cfg.endpoint.getURL=http://adcxxxxxfems.us.oracle.com:xxxx/orabpel/default/GetConfiguratorURLAgileReqABCSImpl

• Bounce the Agile server

• Go to: C:\product\10.1.3.1\OracleAS_1\opmn\bin

• Run the commands:

• opmnctl.exe stopall

• opmnctl.exe startall

This concludes the set up portion for the Agile participating application


(Found in E-Delivery under the 2.5 Media Pack)

• Agile Product Lifecycle Management Integration Pack for Oracle E-Business Suite: Design to Release 2.5 - Implementation Guidehttps://edelivery.oracle.com/EPD/Download/get_form?egroup_aru_number=12840305 (V20889-01) – very specific details about the implementation of this pip, including setting up the participating applications. The appendix has valuable troubleshooting ideas

• Oracle Application Integration Architecture 2.5: Installation and Upgrade Guide –https://edelivery.oracle.com/EPD/Download/get_form?egroup_aru_number=12840305 (V24719-01 ) has very specific instructions on installing the Foundation Pack and the Pip, along with the patches

Other Resources:• Oracle E-Business Suite Developer‟s Guide and Oracle E-Business

Suite System Administrator‟s Guide

• Oracle E-Business Suite Integrated SOA Gateway Troubleshooting Guide:https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=726414.1

PIP Installation and ConfigurationResources

https://edelivery.oracle.com/EPD/Download/get_form?egroup_aru_number=12840305




https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=726414.1

https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=726414.1


Ebiz Oracle E-Business Suite - A fully integrated, comprehensive suite of business applications for the enterprise.

AIA Application Integration Architecture - A set of pre-built and pre-packaged open standards based business process integrations that leverage the Oracle BPEL Process Manager to connect multiple Oracle and non-Oracle applications

OFM Oracle Fusion Middleware - A portfolio of software products, that spans multiple services, including J2EE and developer tools, integration services, business intelligence, collaboration, and content management. OFM is based on open standards.

BPEL Business Process Execution Language - A XML-based workflow definition language

that allows businesses to describe inter or intra enterprise business processes that

are connected via Web services.

ESB Enterprise Service Bus - A software architecture for middleware that provides

fundamental services for more complex architectures

SOA Services-Oriented Architecture - A software architecture where functionality is grouped around business processes and packaged as interoperable services

OSR Oracle Service Registry - Provides a UDDI v3-compliant platform for publishing, categorizing and discovering Web services and related resources across the enterprise


Glossary


DVM Domain value maps - Are maintained using the ESB Console user interface. Domain values are to used for static lookups. DVMs are used for mapping parameters between PLM and eBiz

ABO Application Business Object. It represents an object of the edge system (Agile,eBiz in this case)

ABM Application Business Message. It represents an action on an object of the edge system (Agile,eBiz in this case)

EBO Enterprise Business Object. It represents an object of the OFM.

EBM Enterprise Business Message. It represents an action on an object of the OFM.

ABCS Application Business Connector Service. Is a BPEL process in the OFM which provides

an interface between the edge system (Agile,eBiz in this case) and OFM

EBS Enterprise Business Service. These are services which are exposed by the AIA as wsdls in the enterprise business library

Agile PLM

Agile Product Lifecycle Management - Manages the enterprise product record, the single system of record for product information required to maximize profitability throughout the lifecycle

ECO Engineering Change Order - It is an object that carries with it all the proposed changes to a product and/or its BOM. It can be approved and implemented to make the proposed changes effective.

MCO Manufacturing Change Order - a change order used to release product manufacturability changes without rolling up a revision

Glossary, cont.,


SCO Site Change Order - A change order used to release site-specific product

design/manufacturability changes without rolling up the global revision

JMS Java Message Service - An application program interface from Sun Microsystems that

provides a common interface to standard messaging protocols

ATO Automated Transfer Order - A routable object that triggers and tracks automated transfer of product content information from Agile to XML via ACS

ACS Agile Content Service – Agiles1 event-driven XML-based publishing service

WSX Web Service Extensions - A Web service engine enabling communication between Agile PLM and disparate systems

AML Approved Manufacturer List – List of approved manufacturer parts associated with an item

BOM Bill of Materials - Hierarchical representation of a product that is made up of other products.

XSLT Extensible Stylesheet Language Transformations - A programming language specialized for the transformation of XML documents

Glossary [Cntd.]


Disclaimer:

There are some differences between this PowerPoint presentation and the documents found in E-Delivery. This is due to the various patches and the timing of the updates for the documentation guides. This PowerPoint is accurate as of March 25th, 2011. Please see differences below:

• This PowerPoint is meant to be a guide and you will need to refer to the documents mentioned for other details as suggested throughout the slides

• The 2.5 Implementation Guide does not include configurations for “Create Action Menu Based Process Extensions for Sync Item



Questions

Date post:	23-May-2020
Category:	Documents
Upload:	others
View:	7 times
Download:	0 times