This chapter discusses how to configure the process integration for Agile Project LifeCycle Management (PLM) Oracle E-Business Suite.
This chapter includes the following sections:
Before integration, you must set up Agile Product Lifecycle Management (PLM) and Oracle E-Business Suite.
After installation of Agile PLM - Oracle E-Business Suite integration, the system administrator must setup Agile PLM Content Services (ACS).
The following set ups are required:
Create new destinations.
Create new events for engineering change order (ECO), manufacturing change order (MCO), and site change order (SCO).
Define filters.
Create new subscribers ECO, MCO, and SCO.
Set privileges.
Set up Agile item quantity attributes
Create auto number PX for NPR
Create action menu based PX for NPR
Create action menu based PX for Sync Item
Set up CHANGE_STATUS table, if using workflow
Set up Agile notification
Variant Management: Enable Notification
These set ups are performed in the Agile PLM Java client.
Navigate to Agile Java client
Go to the following settings to enable the Sites:
Admin node, Server Settings, Licenses, Modules, Sites=Yes
If Agile PLM is deployed on Oracle Application Server (OAS)
Copy the wlthint3client.jar file (this file is located at FMW's $WLS_HOME/Middleware/wlserver_10.3/server/lib) put under the OAS j2ee\home\applib directory in the Agile PLM environment.
Bounce the Agile Oracle Application Server (OAS).
Restart the complete SOA.
For more information, see Quick Start Guide for Oracle SOA Suite, Starting and stopping servers.
If Agile PLM is deployed on the Weblogic server (WLS), no need to copy the wlthint3client.jar file, it should work fine as it is.
On the Admin tab, navigate to System Settings > Agile Content Service > Destinations.
Select Protocol JMS.
Enter or set the following essential values:
Table 11-1 Setting for Configuring JMS
Field | Value/Setting |
---|---|
Name |
Define your own |
Response Expected |
No |
User Name |
weblogic (SOA server admin user name) |
Password |
weblogic#1 (SOA server admin password) |
Provider Context Factory |
weblogic.jndi.WLInitialContextFactory |
Connection Factory |
jms/aia/AIAAgilePLMECOCF |
Default Provider URL |
t3://<SOAServer>:<SOAServerPort> |
Destination Name |
jms/aia/AIAAgilePLMECOJMSQueue |
Note:
If you are pointing Agile to a clustered FMW environment, the Default Provider URL needs to contain all possible URLs in the cluster separated by a comma.
For example, t3://<SOAServer1>:<SOAServerPort1>,<SOAServer2>:<SOAServerPort2>
Click Test to validate.
Note:
Create separate Events for CO Release and CO Validation.
In the Admin tab, go to System Settings > Agile Content Service > Events.
Enter or set the following:
Table 11-2 Values for Creating New Events for ECO, MCO, and SCO
Field |
Value/Setting |
||
---|---|---|---|
For ECO |
For MCO |
For SCO |
|
Name |
Define your own |
||
Event Type |
Workflow |
||
Workflow |
Default Change Order |
Default Manufacturer Orders |
Default Site Change Orders |
Workflow Status |
For CO Release Process - Released For CO Validation Process - Any status other than Released. Preferred status is Submitted. |
In the Admin tab, go to System Settings > Agile Content Service > Filters.
Modify Default Item Filter to set the following:
Table 11-3 Values for Defining Default Item Filters
Field |
Value/Setting |
---|---|
View Tabs |
Add Sites, Title Block, Page Two, Page Three, BOM, Manufacturers |
BOM Options |
Tabs and Items |
BOM Levels |
1 (Ensure Select All Levels check box is unchecked) |
AML Options |
Tabs and Manufacturer Parts |
Attachment Options |
Tab only |
Modify the following filters to set the given fields:
Table 11-4 Values for Modifying Filters
Field |
Value/Setting |
||
---|---|---|---|
For ECO |
For MCO |
For SCO |
|
Filter |
Default Change Order Filter |
Default Manufacturer Order Filter |
Default Site Change Order Filter |
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 |
Tab, Redline Content, and Items |
Tab, Redline Content, and Items |
Tab, Redline Content, and Items |
Redline Changes only |
No |
No |
No |
Note:
Create separate Subscribers for CO Release and CO Validation.
In the Admin tab, go to System Settings > Agile Content Service > Subscribers.
Create new Subscribers, one each for ECO, MCO and SCO, and set the following:
Table 11-5 Values for Creating New Subscribers
Field | Value/Setting | ||
---|---|---|---|
For ECO |
For MCO |
For SCO |
|
Name |
Define your own |
||
Subclass |
ATO |
||
Workflow |
Default ATOs |
||
Criteria |
All Change Orders |
All Manufacturer Orders |
All Site Change Orders |
AutoNumber |
ATO Number |
ATO Number |
ATO Number |
Event |
Select the Name of the Event that you created #2 for ECO |
Select the Name of the Event that you created #2 for MCO |
Select the Name of the Event that you created #2 for SCO |
Enter or set the Subscriber Details for each (ECO, MCO, SCO), by adding a new row, as follows:
Table 11-6 Values for Setting Up Subscriber Details
Field | Value/Setting | ||
---|---|---|---|
For ECO |
For MCO |
For SCO |
|
Destinations |
Select the JMS Destinations that you created for each |
||
Filter |
Default Change Order Filter |
Default Manufacturer Order Filter |
Default Site Change Order Filter |
Default Item Filter |
Default Item Filter |
Default Item Filter |
|
Roles |
All |
||
Format |
aXML |
||
Language |
English |
||
Site |
All |
Enable all the newly created Subscribers.
In the Admin tab, go to User Settings > Privileges > Modify.
Create new Modify Privileges for ECO, MCO, and SCO.
Set privilege to Modify.
Select the Criteria that correspond to each ECO, MCO, and SCO.
Select all the Attributes, including the invisible/disabled attributes in the Applied to field and Save them.
In the Where Used tab, add Roles to all the created privileges. Default role is Admin user.
Create new Read privileges for MCO.
Select All Manufacturer Orders in the Criteria.
Choose both visible and invisible/disabled attributes in the Applied to field.
Modify the Read Changes and Read Items to get the Admin user in the Where Used tab.
Note:
The user should have privileges to modify the 'released' items and 'released' changes.
In the Admin tab, go to User Settings > Privileges > Read.
Create new Modify Privileges for ECO, MCO, and SCO.
Set privilege to Read.
Set Enabled to Yes and Privilege to Modify.
Select All Manufacturer Orders in the Criteria.
Choose both visible and invisible/disabled attributes in the Applied to field.
Modify the Read Changes and Read Items to get the Admin user in the Where Used tab.
Note:
The user should have privileges to modify the 'released' items and 'released' changes.
In the Admin tab, go to Data Settings > Classes.
For both Parts and Document classes under items, enable the flexfields on Page2, Page3 or Site tab according to the MultiSite_Enabled property value in the AIAConfigurationProperties.xml file, located at AIA_HOME>/aia_instances/$INSTANCE_NAME/AIAMetaData/config, for the Agile PLM module.
Go to User Interface Tab to select Sites or Page 2.
These field names in Agile reflect the following fields from the Oracle E-Business Suite:
Manufacturer Cost
Available Quantity
On Hand Quantity
Reserved Quantity
The values of these fields should be the same as those entered for the following properties:
Item.UnitCostAttribute
Item.AvailableQuantityAttribute
Item.OnHandQuantityAttribute
Item.ReservedQuantityAttribute
Set the created fields to Visible on the General Tab:
Note:
Ensure that these attributes have Read and Modify privileges.
Similarly, enable a Page2 or Page3 flex field on the ECO, MCO, and SCO to reflect Change.TransferStatusAttribute property value in the AIAconfigProperties.xml file.
Oracle recommends that this field:
Should be a Page Two field on the change orders, manufacturer orders, and site change orders classes.
The field should have the same display name on all three classes.
Have a default value of Not Processed.
Should be editable only by the user of the ID used by the integration to log in to Agile PLM, and be editable for all status (if the change is not released after its initial release).
If a value is not specified for this parameter, the implication is that a status update back to a change order flex-field in Agile PLM is not required
The field identified by this parameter will also be used by the integration to update the change implementation status into Agile PLM.
Add Change.TransferStatusDetailedMessageAttribute property.
Note:
In Agile PLM, you can modify maximum length of the attribute of this property up to 1000 characters.
Note:
Create separate Auto Number PX each sub class with appropriate names. This is used to identify the sub class for which a particular Auto number PX is triggered.
In the Admin tab, go to Data Settings > AutoNumbers.
Click Create to create auto numbers for a subclass.
Enter the following fields in the Define the AutoNumber screen.
Enter name for AutoNumber.
Choose Yes for Enabled.
Choose Custom for Type.
Choose the Part subclass name for Where Used.
Choose com.oracle.aia.npr.V2.NPRAutoNumber for Custom AutoNumber.
Click OK.
In the Admin tab, navigate to Data Settings > Process Extensions.
Click Create to create the process extension.
Enter the following details in the Define the AutoNumber screen:
Enter name as NPR Number
Choose Internal Custom Action for Type.
Choose com.oracle.aia.npr.V2.UpdateNPRNumber for Internal Custom Action.
Select Actions Menu from the Initiate From field.
Choose Yes for Enabled.
Click OK.
Navigate to Admin > Data Settings.
Double click Classes.
Double click Items in the Classes window.
Navigate to the Process Extensions tab.
Click Open to open the Assign Process Extensions window.
Select NPR Number from the choices.
Click OK.
In the Admin tab, navigate to Data Settings > Process Extensions.
Click Create to create the process extension.
Enter the following details in the Add Process Extensions window:
Enter name as Sync Item.
Select Internal Custom Action for Type.
Select com.oracle.aia.syncitem.SyncItem for Internal Custom Action.
Select Actions Menu from the Initiate From field.
Select Yes for Enabled.
Click OK.
Navigate to Admin > Data Settings.
Double-click Classes.
Double-click Items in the Classes window.
Navigate to the Process Extensions tab.
Click Open to open the Assign Process Extensions window.
Select Sync Item from the choices.
Click OK.
Log on to the Agile Java Client.
In the console tree (left pane), click the Admin tab.
In the left pane of the Admin view, click the + next to Data Settings. Click Classes.
In the fields section of the field list, in the list view, click the ECO field. This opens the Subclass ECO window.
Click the User Interface Tabs tab.
In the fields section of the field list, in the list view, click the Cover Page field. This opens the Subclass Tabs:ECO window.
Click the Attributes:CoverPage tab.
In the fields section of the field list, in the list view, click the Change Category field. This opens the Attributes-Change Category window.
Under the List Detail Box column, click the View Details button. This opens the List Change Category window.
Click the List tab.
Click the + icon, and then enter the value CLASS A::CLASS_A::CLASS A in the Add batch list values editor window.
Click Ok, and then click Save.
Because the change status name depends on the workflow being used, the CHANGE_STATUS configuration table is provided as part of the integration setup. The CHANGE_STATUS table is located in the AIA schema created on the Service-Oriented Architecture (SOA) server. The default user ID is plmpip. The password will be the same password that the customer has setup for the FP AIA database. This value is the same as the property fp.db.aia.password, which can be found in the AIAInstallProperties.xml file. The DB details, such as URL, port, server ID, and so on can be found in the AIAInstallProperties.xml file at <AIA_INSTANCE>/config/AIAInstallProperties.xml.
This table allows the administrators to specify the next status for each possible combination of change object type and the workflow being used for each event that qualifies for the change status operation. The administrators can add as many rows as required. The number of sub-classes of change objects and the number of workflows is unlimited in Agile PLM.
Table 11-7 illustrates how a partially configured table looks:
Table 11-7 Partially Configured Change Status and Workflow Table
EVENT |
OUTCOME |
SUBCLASS |
WORKFLOW |
NEXT_STAUS |
---|---|---|---|---|
Change Implemented |
SUCCESS |
ECO |
Default Change Orders |
Implemented |
In a new installation, this table will be empty. The integration administrator must add rows in this table if the change status process must be supported for any of the given processes.
The EVENT column key is Change Implemented.
The OUTCOME column key is SUCCESS.
In the SUBCLASS column, set up the change order subclass as ECO, MCO, etc.
In the WORKFLOW column, set up the workflows. For example, if you are using Default Change Order workflow for ECO, then enter Default Change Order in this column. These values can be picked up from Agile PLM Java client.
In the NEXT_STATUS column, enter the status of the workflow you want it to move to when the conditions are met. For example, when a Change is implemented (identified by event - this is a key. do not change it) and the OUTCOME is SUCCESS (identified by outcome, gets checked while changing status here), and the WORKFLOW chosen is Default Change Orders, the set up requesting the Change to be moved to the Implemented status (NEXT_STATUS).
Notifications can be setup in Agile PLM to send email when any 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.
In the Admin Tab, go to Server Settings > Database.
In the Notification Enabled field, select Yes.
Navigate to System Settings > Notifications.
In the Filter By field, select Name.
In the Value field enter Part.
Click Apply.
Open Parts - Part Send.
In the Notification Type field, select Inbox.
In the Enabled field, select Yes.
The following settings are user specific settings.
Go to User Settings > Privileges > Send.
In the Filter By field select Name.
In the Value field, enter Send Item.
Click Apply.
Open Send Items.
In the Enabled field, select Yes.
The current user has to have a role assigned that contains the privilege 'Send Item'.
Navigate to User Settings > Users.
Make sure the current user has roles assigned to him that contain the privilege Send Item.
Applies to all Agile versions.
Go to Admin > User Settings > Privileges > Modify.
Create a new privilege for Modify called Modify Model. Use the first icon on the top left.
Set Enabled to Yes and Privilege to Modify.
For the Privilege Criteria column, select All Models. If you cannot find All Models, create an All Models criteria by using the second icon next to the Criteria field.
Once the Criteria is complete, go to the Applied to field icon and deselect the box at the bottom.
Drag all choices to the Selected column.
Click OK, and Close.
Applies to all Agile versions:
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
.
Click OK and close.
For more information, see Agile PLM Content Service User Guide and Agile Product Lifecycle Management Administrator Guide.
Applies to all Agile versions:
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 not, drag it to the appropriate location.
Click OK and close.
For more information, see Agile PLM Content Service User Guide and Agile Product Lifecycle Management Administrator Guide.
Applies to all Agile versions:
Go to Admin > User Settings > Settings > Roles
Enter a name.
Set Enabled to Yes and Privilege to Modify.
Specify User/Groups = Search for Administrator/admin and drag that to the right side column.
Click OK and close.
Applies to all Agile versions:
Go to Admin > User Settings > Settings > Roles
Go to the newly created VM role.
Select the Users tab and go into the user that has Administrator as the last name.
In the General Info tab, enter a name and an email address.
Save.
If you are using Oracle Configurator:
Go into the Preferences tab.
For the BOM Variant Configuration Preference, select External Configurator.
Click OK and close.
If the Agile is on OAS application server:
Using the remote desktop, logon to the Agile server with the proper credentials.
Two agile.properties files need to be modified with the SOA_host/port in the following locations:
<AGILE_DOMAIN>\config\agile.properties
<SOA_HOME>\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 as shown in the example below:
aia.cfg.endpoint.getURL=http://<<SOA_HOST>>:<<SOA_PORT>>/orabpel/default/GetConfiguratorURLAgileReqABCSImpl
Restart the Agile server using the following commands from the <SOA_HOME>/opmn/bin directory:
For Linux (x86), Solaris SPARC (64-bit), IBM AIX Based Systems (64-bit), and HP-UX 11i (64 bit):
./opmnctl.exe stopall
./opmnctl.exe startall
For Microsoft Windows (32-bit):
opmnctl.exe stopall
opmnctl.exe startall
If the Agile is on Weblogic Server (WLS):
Using the remote desktop, logon to the Agile server with the proper credentials.
The agile.properties files need to be modified with the SOA_host/port in the following location: <AGILE_DOMAIN>\config\agile.properties. In these files, 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 as shown in the example below:
aia.cfg.endpoint.getURL=http://<<SOA_HOST>>:<<SOA_PORT>>/soa-infra/services/default/GetConfiguratorURLAgileReqABCSImpl/client
aia.cfg.endpoint.intusername and modify the line by replacing the tokens for SOA_LOGIN_USERNAME with the valid values as shown in the example below:
aia.cfg.endpoint.intusername=<<SOA_LOGIN_USERNAME>>
aia.cfg.endpoint.intuserpasswd and modify the line by replacing the tokens for SOA_LOGIN_PASSWORD with the valid values as shown in the example below:
aia.cfg.endpoint.intuserpasswd=<<SOA_LOGIN_PASSWORD>>
Note:
The password must be encrypted. To encrypt the password:
In the Agile Server, navigate to <AgileHome>/agileDomain/bin
Run the encryption script "./encryptpwd.sh" and enter the Password to get encrypted password.
Restart the Agile server.
For more information, see Agile Product Lifecycle Management Installing Oracle for WebLogic Server Guide.
After you are done setting up Variant Management on the Agile side, additional set up must be completed on the Ebiz side. Refer to Section 11.1.2, "Setting Up Oracle E-Business Suite"to complete the E-business setups.
For more information, see Agile PLM Content Service User Guide and Agile Product Lifecycle Management Administrator Guide.
Enable Actions Items in Automated Transfer Orders (ATO)
Go to Admin > Data Settings > Classes > ATO.
Click User Interface tab.
Click Action Items.
Modify Visible = Yes.
Save all the changes.
Read privileges for ATO Action Item Object
Go to Admin > User Settings > Privileges > Read
Search for Read ATO.
Click Read ATO.
Go to Applied to.
Uncheck Show visible attributes only check box.
Move Status, Subject, Description, Due Date, Notes and Assigned To to Selected column.
Save all the changes.
Modify privileges for ATO Action Item Object
Go to Admin > User Settings > Privileges > Modify.
Search for Modify ATO.
Click Modify ATO.
Go to Applied to.
Uncheck Show visible attributes only check box.
Move Status, Subject, Description, Due Date, Notes and Assigned To to Selected column.
Save all the changes.
Default values for ATO Action Item attributes
Go to Admin > Data Settings > Classes > ATO.
Click User Interface tab.
Click Action Item > Attributes.
Select Attributes:Action Items tab
Enter default values for Notes and Due Date.
For Due Date, we recommend you to enter value "$NOW". For Notes, we recommend you to provide a wiki link for Business User to refer various known errors and their resolutions provided with the PIP out-of-the-box (OOTB) listed in Appendix G, "Error Handling"
Save all the changes.
This section includes the following topics:
Profile settings
Oracle Configurator setup
Table 11-8 lists the profile option settings that need to be configured for Oracle E-Business Suite to support the integration flow from Oracle E-Business Suite to Agile PLM:
Table 11-8 Oracle E-Business Suite Profile Settings
Setting | Description |
---|---|
BOM:Configurator URL of UI Manager |
Configurator URL |
CZ: Publication Lookup Mode |
For Variant Management, set this profile option to define the desired publication look up mode. During a UI launch from Agile, the values in this profile decide which UI to launch, if multiple UIs are published to Agile PLM with different publication lookup modes and usages. |
CZ: Publication Usage |
For Variant Management, set this profile option to define the desired publication usage. During a UI launch from Agile, the values in this profile decide which UI to launch, if multiple UIs are published to Agile PLM with different publication lookup modes and usages. |
EBS Integration Batch Count |
Many entities (items or ECO) will be sent out in buckets based on the number that is set in this profile option. For example, if the reverse flow from Oracle E-Business Suite to Agile PLM has 22 items to be synched up based on this many items having been updated since the last run of the concurrent program and the profile has been set to 10, then 3 BPEL instances will be created to send out 10 + 10 + 2 items. If too many items have been updated after the last run, then BPEL may not be able to handle a very large payload causing memory issues. To prevent this, Oracle has introduced this profile. In such cases, the batch is split and sent. |
EBS Integration Debug Directory |
This profile option has VALUE as the path where the log file will be generated. This folder or directory should have read and write permission. |
EBS Integration Debug Option |
This profile option enables and disables logging. If the value is yes, then logging is enabled; if no, then it is disabled. |
EBS Integration Language Codes |
This profile option is used for returning the user language code through a concurrent program to the requestor BPEL process for identifying the integration user based on the language code received. Depending on this language code, APPS Context is set for that particular integration user and Oracle E-Business Suite will return the data in that particular language to Agile PLM. |
EBS Integration: PIM Spoke Source System Name |
This profile option is used for specifying multiple source systems based on which items will be filtered and updated back to Agile PLM. This source system should be a comma-separated value. |
EBS Integration Proxy Server Host |
Set it to the <SOA server /host name/>. |
EBS Integration Proxy Server Port |
Set it to the <SOA server http /port number/>. |
EBS Integration: Server Endpoint URL |
Endpoint of Managed SOA server on Fusion Middleware (FMW). For example, http://<host>:<port>/soa-infra/services/default |
ENG: Require Revised Item New Revision |
This profile indicates whether it is mandatory to assign a new revision to revised items on Oracle E-Business Suite ECOs. A blank (or "null") value is equivalent to No. This profile option should be set to No for the change order release process. |
EBS profile option: EGO: Enable Stats Collection |
For Agile-EBS integration to work, this profile option must be disabled. |
Enable PIM for Telco Features |
The value of this profile must be 'No'. By default, if there is no value in this profile, it works as 'No'. You should not change this to 'Yes'. If this profile is set to 'Yes', PIM code expects the ICC to be in released status. For this PIP, the ICC Part is not released. |
Note:
If the ECO update is event based, then setup for Subscribers and Events has to be done.
To navigate to the profiles interface:
Log in to the application with sysadmin credentials.
Navigate to System Administrator > responsibility.
Select System > Profile.
Search for the profiles given in the table and set the values.
For more information about the concurrent programs, see Oracle E-Business Suite Developer's Guide and Oracle E-Business Suite System Administrator's Guide - Maintenance.
To use the Variant Management with Oracle Configurator, you will need to create a custom application in Oracle E-Business Suite (for example, Agile_PLM), which would be a onetime job during this integration. From then, for every BOM model to be launched using the Configurator UI from the Agile UI, the flow is to have the model structure released from Agile PLM to Oracle E-Business Suite and import the model into Oracle Configurator Developer. If required, create certain rules and UI for the model and publish the UI from Oracle Configurator Developer to the newly created custom application. This would make the Configurator UI available for Agile PLM users.
Creation process of a custom application in Oracle E-Business Suite includes:
Log in to Oracle E-Business Suite as a user with the Application Developer responsibility.
Navigate to Application Developer > Application > Register function.
Provide the values for Application, Short Name, Basepath, and Description.
For example, Agile_PLM, APLM, APLM_TOP, and Agile Integration with Configurator respectively.
Save.
When saved, the application details like application_id can be fetched from database using the query:
SELECT * From fnd_application_vl WHERE application_short_name = 'APLM';
After obtaining the application_id for the application created in this step, update the property CONFIGURATOR_APPLICATION_ID under the GetConfiguratorURLEbizProvABCSImpl service in the AIAConfigurationProperties.xml file to reflect this new custom application.
For subsequent launches of the Oracle Configurator UI from Agile PLM, the application_id set in this parameter will be passed in the initialization message to Oracle Configurator.
To make this application available for publishing a UI from Oracle Configurator (CZ) to Agile PLM, add it to the publication applicability list.
To do this, navigate to Oracle Configurator Administrator > Concurrent programs > Schedule and run the concurrent program Add Application to Publication Applicability List.
For more information about how to access the Oracle E-Business Suite APPS database schema without requiring sharing of the password for the APPS schema, see Oracle E-Business Suite Software Development Kit for Java (includes AppsDataSource, Java Authentication and Authorization Service) Readme - Patch 9863609 (My Oracle Support document: 974949.1).
Depending on the volume of transactions, an index can be created on the LAST_UPDATE_DATE column in the base tables CST_ITEM_COSTS, MTL_SYSTEM_ITEMS, and CST_QUANTITY_LAYERS, which will improve performance in the publish item and publish item balance flows originating from Oracle E-Business Suite.
Three flows from Oracle E-Business Suite to Agile PLM are scheduled for data to be sent at regular intervals. This is done by means of Oracle E-Business Suite concurrent programs (CP), which can be run at various intervals and scheduled with user interface options. The programs are:
Publish Item Attributes Updates
Publish Item Balance Updates
Publish Engineering Change Order Updates
Concurrent programs are configured as a periodic or scheduled publication or triggered ad hoc for On-Demand publication.
First Scheduled Run
When the concurrent program is scheduled, it sends all those entities that have been updated. However, for the very first run, the last run date is not available. Hence, it is defaulted to the last 30 days. This may result in an enormous number of items being picked up. Hence, the customer may choose to first perform an ad hoc publish (this is after the this integration is installed and a few items are transferred from Agile PLM to Oracle E-Business Suite based on the implementation).
In addition, specific organizations can be specified along with from date and to date in the ad hoc request parameters, from a performance perspective, to send the data in multiple requests. After this, the customer can set up a scheduled process and the first run of the scheduled process will pick up the ad hoc request run time as the last run date. Another option is that the customer can just schedule the request to be run with the Updated within the last X hours parameter set. This will pick up items, even for the first run, that have been updated in the last x hours.
Subsequent Scheduled Run
Oracle recommends that you set the Updated in the last X hrs parameter with a default value for the concurrent programs that you set up to run at a schedule frequency. Specify this parameter value apart from the schedule frequency that is set up in the Concurrent Program setup. Oracle suggests that you set the same x hours for the Concurrent Program Schedule setup. Alternatively, you can leave all the parameters empty and schedule the concurrent program to run at a particular schedule frequency that you want.
Concurrent Program Parameters
Item/ECO names:
The items/ECOs that are to be published should be entered separated by double semicolons.
This is a text parameter of maximum length 240.
Examples:
ItemName1;;ItemName2;;ItemName3 ChangeOrderName1;;ChangeOrderName2;; ChangeOrderName3
Organization codes:
Organization codes must be specified separated by double semicolons.
This is a text parameter of maximum length 240.
Example1:
Item Names - Item1;;Item2;;Item3 Organization Codes - Org1;;Org2 If Item1 exists in Org1, Item2 in Org2 and Item3 in both Org1 & Org2 then, Items Published: Item1:Org1, Item2:Org2, Item3:Org1, Item3:Org2
Example2:
Organization Codes - Org1;;Org2 Updated in the last X Hrs - 10 Items/ECOs Published: Items/ECOs that got updated in the last 10 hours from Org 1 & Org2.
From Date:
This is a standard date time parameter.
To Date:
This is a standard date time parameter. This parameter should be entered only if the From Date parameter is given a value.
Updated in the last X hrs:
This is a number parameter of maximum length 15. If this parameter is provided a value, then the From Date and To Date parameter values will not be considered.
Supported Functionalities
Scheduled request with no value provided to all parameters
Items/ECOs that were updated from the last completed or scheduled request will be picked for publication. The items/ECOs with errors from the previous run will not be automatically picked for the publication. All the items/ECOs with errors need to be published by using ad hoc CP request functionality and providing appropriate CP request parameters for such ad hoc requests.
Ad hoc request with no value provided to any of the parameters
Oracle recommends that customers provide appropriate parameter values for the CP ad hoc requests. If no value is provided, then items/ECOs that were updated from the last completed or scheduled request will be published. If no scheduled requests are prior to the current request, then it will pick all the items/ECOs that were updated from the last completed request. If no completed requests are prior to the current one (first request of CP), then it will choose the data that was updated in the last 30 days.
Expected Behaviors
Table 11-9 lists the expected behavior of the requests based on the input values provided. A tick mark (x) implies that the values are specified, while a dash (-) implies they are not.
Table 11-9 Expected Behavior of Requests
Item/ECO Names | Organization Codes | From Date | To Date | Updated in last X hrs | Expected Items/ECOs to be published |
---|---|---|---|---|---|
x |
- |
- |
- |
- |
Specified items/ECOs from all assigned Organization |
- |
x |
- |
- |
- |
Items/ECOs updated from the last completed request from the specified organization (If no last completed request then last 30 days). This is done in order to maintain the performance of the system. |
- |
- |
x |
- |
- |
Items/ECOs updated between the specified From Date and System Date from all Organizations |
- |
- |
- |
x |
- |
Error (From Date cannot be empty when to Date is specified) |
- |
- |
- |
- |
x |
Items/ECOs updated in the last X Hours from all organizations |
x |
x |
- |
- |
- |
Specified Items/ECOs from specified organizations if they exist |
- |
x |
x |
- |
- |
Items/ECOs updated between the specified From Date and System Date from specified organizations |
- |
x |
- |
- |
x |
Items/ECOs updated in the last X hours from specified organizations |
x |
- |
x |
- |
- |
Specified items/ECOs updated between the specified From Date and System Date from all assigned organizations |
x |
- |
- |
x |
- |
Error (From Date cannot be missing when To Date is specified) |
x |
- |
- |
- |
x |
Specified items/ECOs updated in the last X hours specified from all assigned organizations |
x |
- |
x |
x |
- |
Specified items/ECOs updated between the specified From Date and To Date from all assigned organizations |
x |
- |
x |
x |
x |
Specified items/ECOs updated in the last X hours specified from all assigned organizations. The specified From Date and To Date will be ignored |
x |
x |
- |
x |
x |
Specified items/ECOs from specified organizations if they exist and are updated in the last X hours specified. The specified To Date will be ignored |
x |
x |
x |
x |
x |
Specified items/ECOs from specified organizations if they exist and were updated in the last X hrs specified. The specified From Date and To Date will be ignored |
On Demand/Ad Hoc
After the integration setup is complete, perform the following tasks:
Initial publication of items and ECOs from Oracle E-Business Suite
Run an ad hoc request specifying from date and to date. (If this is not done, the CP will pick all the items and ECOs that were updated in the last 30 days.) In addition, specific organizations can be specified along with from date and to date in the CP parameters, from a performance perspective, to send the data in multiple CP requests as part of Implementation setup.
Periodic and scheduled publication of items and ECOs from Oracle E-Business Suite
Oracle recommends that customers set the updates in the last X hrs parameter with a reasonable value for CPs that are being set up to run at a schedule frequency. This parameter value should be specified apart from the schedule frequency setup in the Concurrent Program setup. Oracle suggests that customers set the same X number of hours for the Concurrent Program Schedule setup (OR). Customers can leave all the parameters empty and schedule the CP to run at a particular schedule frequency that they desire.
On Demand/Ad-hoc publication of items and ECOs from Oracle E-Business Suite
The items and ECOs that failed during the scheduled run must be sent as separate ad hoc requests by specifying appropriate value to the parameters. The items and ECOs of the organizations that failed during the scheduled publication can be obtained from the log information to provide input parameters for the ad hoc concurrent request to synchronize the data between Oracle E-Business Suite and Agile PLM after resolving the reported publication error.
Product Information Management (PIM) Spoke Source System setup must be done before you run the New Part Request (NPR) flow for Oracle E-Business Suite 12.1.x and 12.2.x (where x>=1) release. This setup is required so that after creation of an item in Oracle E-Business Suite, it can appear in the Association Tab of the source system.
Note:
The PIM Spoke Source System setup is required if the integration is installed with the PIM option enabled.
For more information about how to set up the PIM Spoke Source System, see Oracle Product Information Management Implementation Guide, "Setting Up Inbound Product Data Synchronization and Data Quality Management," Defining Source Systems.
There is no utility in 11g to load cross-reference records similar to 10g. However, this can be accomplished with an SQL script.
The following is an example of a SQL script that loads cross-reference records for the XRef table, ITEM_ITEMID with columns AGILE_01 and EBIZ_01. This sample scripts allows you to build XREF records for a single item.You can modify this SQL script to suit your specific requirements.
DECLARE
XrefTableName_vc2 VARCHAR2 (2000);
XrefColumnName1_vc2 VARCHAR2 (2000);
XrefColumnName2_vc2 VARCHAR2 (2000);
XrefColumnName3_vc2 VARCHAR2 (2000);
Value_vc2 VARCHAR2 (2000);
RowNumber_vc2 VARCHAR2 (48);
IsDeleted_vc2 VARCHAR2 (1);
LastModified_ts TIMESTAMP (6);
BEGIN
/* The following values need to be set just once per load*/
XrefTableName_vc2:= 'oramds:/apps/AIAMetaData/xref/ITEM_ITEMID.xref';
IsDeleted_vc2:= 'N';
XrefColumnName1_vc2:= 'COMMON';
XrefColumnName2_vc2:= 'AGILE_01';
XrefColumnName3_vc2:= 'EBIZ_01';
/* You'll just need to change the Value_vc2 variable for your specific edge app values */
/* Row Number is unique to a group of three inserts and ties them together. Its a system generated guid in all cases */
/* Copy this section as many times as needed for each set of three records you need inserted */
/********************************************** Begin set of 3 inserts ******************************************/
RowNumber_vc2:= SYS_GUID;
/* Common row should have a guid for its value */
Value_vc2:= SYS_GUID;
LastModified_ts:= SYSTIMESTAMP;
Insert into XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) values
(XrefTableName_vc2, XrefColumnName1_vc2, RowNumber_vc2, Value_vc2, IsDeleted_vc2, LastModified_ts);
/* Value specific to each application, for Agile value generation please check XREF_Instructions.doc */
Value_vc2:= 'AgileValue1';
LastModified_ts:= SYSTIMESTAMP;
Insert into XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) values
(XrefTableName_vc2, XrefColumnName2_vc2, RowNumber_vc2, Value_vc2, IsDeleted_vc2, LastModified_ts);
/* Value specific to each application, for Ebiz value generation please check XREF_Instructions.doc */
Value_vc2:= 'EbizValue1';
LastModified_ts:= SYSTIMESTAMP;
Insert into XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) values
(XrefTableName_vc2, XrefColumnName3_vc2, RowNumber_vc2, Value_vc2, IsDeleted_vc2, LastModified_ts);
/************************************************** End of set of 3 inserts ******************************************/
END;
The following is an example of a SQL script that loads cross-reference records for the XRef table, CHANGE_CHANGEID with columns AGILE_01 and EBIZ_01. You can modify this SQL script to suit your specific requirements.
DECLARE
XrefTableName_vc2 VARCHAR2 (2000);
XrefColumnName1_vc2 VARCHAR2 (2000);
XrefColumnName2_vc2 VARCHAR2 (2000);
XrefColumnName3_vc2 VARCHAR2 (2000);
Value_vc2 VARCHAR2 (2000);
RowNumber_vc2 VARCHAR2 (48);
IsDeleted_vc2 VARCHAR2 (1);
LastModified_ts TIMESTAMP (6);
BEGIN
/* The following values need to be set just once per load*/
XrefTableName_vc2:= 'oramds:/apps/AIAMetaData/xref/CHANGE_CHANGEID.xref';
IsDeleted_vc2:= 'N';
XrefColumnName1_vc2:= 'COMMON';
XrefColumnName2_vc2:= 'AGILE_01';
XrefColumnName3_vc2:= 'EBIZ_01';
/* You'll just need to change the Value_vc2 variable for your specific edge app values */
/* Row Number is unique to a group of three inserts and ties them together. Its a system generated guid in all cases */
/* Copy this section as many times as needed for each set of three records you need inserted */
/********************************************** Begin set of 3 inserts ******************************************/
RowNumber_vc2:= SYS_GUID;
/* Common row should have a guid for its value */
Value_vc2:= SYS_GUID;
LastModified_ts:= SYSTIMESTAMP;
Insert into XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) values
(XrefTableName_vc2, XrefColumnName1_vc2, RowNumber_vc2, Value_vc2, IsDeleted_vc2, LastModified_ts);
/* Value specific to each application, for Agile value generation please check XREF_Instructions.doc */
Value_vc2:= 'AgileValue1';
LastModified_ts:= SYSTIMESTAMP;
Insert into XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) values
(XrefTableName_vc2, XrefColumnName2_vc2, RowNumber_vc2, Value_vc2, IsDeleted_vc2, LastModified_ts);
/* Value specific to each application, for Ebiz value generation please check XREF_Instructions.doc */
Value_vc2:= 'EbizValue1';
LastModified_ts:= SYSTIMESTAMP;
Insert into XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) values
(XrefTableName_vc2, XrefColumnName3_vc2, RowNumber_vc2, Value_vc2, IsDeleted_vc2, LastModified_ts);
/************************************************** End of set of 3 inserts ******************************************/
END;
This integration uses the xref_data table present in Application Integration Architecture (AIA) schema to maintain a cross-reference between Agile PLM and Oracle E-Business Suite. This cross-reference information helps map Agile PLM Parts/ Documents/ Change Orders to Oracle E-Business Suite Items/ Change Orders.
Two virtual tables in the AIA XREF schema's XREF_DATA table maintain this cross-reference information.
CHANGE_CHANGEID: maintains all the change order information.
ITEM_ITEMID: maintains item information.
Example:
A change order ECO001 contains two revised items:
P0001 in site V1
P0002 in site V2
Both these revised items have component items:
P0001 has component items C0001 and C0002
P0002 has component items C0003 and C0004
When this change order is released from Agile PLM to Oracle E-Business Suite, the following entries are made in the CHANGE_CHANGEID virtual table:
Table 11-10 Entries in CHANGE_CHANGEID Virtual Table
XREF_TABLE | XREF_COLUMN | ROW_NUMBER | VALUE |
---|---|---|---|
CHANGE_CHANGEID |
AGILE_01 |
E45E015046AF11DD9F2E436FB39961A8 |
ECO001::V1 |
CHANGE_CHANGEID |
COMMON |
E45E015046AF11DD9F2E436FB39961A8 |
2d373833303237303132383837353631 |
CHANGE_CHANGEID |
EBIZ_01 |
E45E015046AF11DD9F2E436FB39961A8 |
11075 |
CHANGE_CHANGEID |
AGILE_01 |
E45E015046AF11DD9F2E436FB39961A9 |
ECO001::V2 |
CHANGE_CHANGEID |
COMMON |
E45E015046AF11DD9F2E436FB39961A9 |
2d373833303237303132383837353632 |
CHANGE_CHANGEID |
EBIZ_01 |
E45E015046AF11DD9F2E436FB39961A9 |
11076 |
The CHANGE_CHANGEID table is located at this location: $AIA_HOME/AIAMetaData/xref/CHANGE_CHANGEID.xref
The first row entry is made by the Agile PLM BPEL flow for change order ECO001. This change order belongs to an Agile PLM site that is mapped to site V1. The value entered is a concatenation of change order number and the Oracle E-Business Suite organization code (for example, CONumber::OrganizationCode).
The second entry (Common) is also created by the Agile PLM BPEL flow. It indicates the common business component ID for this particular integration entity. It is used for linking change orders to Oracle E-Business Suite change orders.
The third row entry represents the Oracle E-Business Suite Engineering Change Order ID corresponding to the item ECO001 and the organization ID for the Change Order (for example, ChangeOrderID::Organization_Code).
For each revised item and component items in the change order, entries are made into the ITEM_ITEMID virtual table.
Example: For ECO001, the following entries will be made in the ITEM_ITEMID table.
Table 11-11 Entries in ITEM_ITEMID Table
XREF_TABLE | XREF_COLUMN | ROW_NUMBER | VALUE |
---|---|---|---|
ITEM_ITEMID |
AGILE_01 |
0078BE703EC711DDBF9CA7AA7FE3BDFB |
P0001::V1 |
ITEM_ITEMID |
COMMON |
0078BE703EC711DDBF9CA7AA7FE3BDFB |
35313835373739353732383638303435 |
ITEM_ITEMID |
EBIZ_01 |
0078BE703EC711DDBF9CA7AA7FE3BDFB |
66247::204::<operating unit ID> |
ITEM_ITEMID |
AGILE_01 |
0078BE703EC711DDBF9CA7AA7FE3BDFC |
P0002::V2 |
ITEM_ITEMID |
COMMON |
0078BE703EC711DDBF9CA7AA7FE3BDFC |
35313835373739353732383638303436 |
ITEM_ITEMID |
EBIZ_01 |
0078BE703EC711DDBF9CA7AA7FE3BDFC |
66248::207::<operating unit ID> |
ITEM_ITEMID |
AGILE_01 |
0078BE703EC711DDBF9CA7AA7FE3BDFD |
C0001::V1 |
ITEM_ITEMID |
COMMON |
0078BE703EC711DDBF9CA7AA7FE3BDFD |
35313835373739353732383638303437 |
ITEM_ITEMID |
EBIZ_01 |
0078BE703EC711DDBF9CA7AA7FE3BDFD |
66249::204::<operating unit ID> |
ITEM_ITEMID |
AGILE_01 |
0078BE703EC711DDBF9CA7AA7FE3BDFE |
C0002::V1 |
ITEM_ITEMID |
COMMON |
0078BE703EC711DDBF9CA7AA7FE3BDFE |
35313835373739353732383638303438 |
ITEM_ITEMID |
EBIZ_01 |
0078BE703EC711DDBF9CA7AA7FE3BDFE |
66250::204::<operating unit ID> |
ITEM_ITEMID |
AGILE_01 |
0078BE703EC711DDBF9CA7AA7FE3BDFF |
C0003::V2 |
ITEM_ITEMID |
COMMON |
0078BE703EC711DDBF9CA7AA7FE3BDFF |
35313835373739353732383638303439 |
ITEM_ITEMID |
EBIZ_01 |
0078BE703EC711DDBF9CA7AA7FE3BDFF |
66251::207::<operating unit ID> |
ITEM_ITEMID |
AGILE_01 |
0078BE703EC711DDBF9CA7AA7FE3BDFG |
C0004::V2 |
ITEM_ITEMID |
COMMON |
0078BE703EC711DDBF9CA7AA7FE3BDFG |
35313835373739353732383638303440 |
ITEM_ITEMID |
EBIZ_01 |
0078BE703EC711DDBF9CA7AA7FE3BDFG |
66252::207::<operating unit ID> |
The ITEM_ITEMID table is located at this location: $AIA_HOME/AIAMetaData/xref/ITEM_ITEMID.xref
The first row entry is made by the Agile PLM BPEL flow for part P0001. This part belongs to an Agile PLM site that is mapped to site V1. The value entered is a concatenation of part number and E-Business OrganizationCode (for example, Partnumber::OrganizationCode).
The second entry (Common) is also created by the Agile PLM BPEL flow. It indicates the common business component ID for this particular integration entity. It is used to link Agile PLM Parts/ Documents/ Change orders to Oracle E-Business Suite Items/Change Orders.
The third row entry represents the Oracle E-Business Suite inventory item ID corresponding to the item P1B and the organization ID for the item (for example, Inventory_Item_id::Organization_id::Operating_Unit_Id). The rest of the entries represent the revised and component items for the ECO001.
The ITEM_ITEMID virtual table contains the similar cross-reference entries for each item and part created through the new part request process.
If data needs to be ported from other existing integrations to the Agile PLM integration, you should first establish the relationship between Agile PLM entities and Oracle E-Business Suite entities by inserting the relevant data in the xref_data table.
Load the required integration data manually in the xref_data table to establish the link between Agile PLM and Oracle E-Business Suite. This data will map the Agile PLM entities to the Oracle EBS entities as described in the previous section.
Even for existing Agile PLM integration integrations, if an item or change order needs to be created in Oracle E-Business Suite and then is created in Agile PLM, the cross-reference entry is made for the integration to process the item. All the update (reverse) flows for the integration will update the item attributes in Agile PLM if an entry exists in the xref_data table for that particular item.
The data that has to be inserted in the xref_data table can be retrieved by the following means:
The value for the XREF_TABLE column in the xref_data table is oramds:/apps/AIAMetaData/xref/<xref-name>.xref, where xref-name is ITEM_ITEMID or CHANGE_CHANGEID.
The change ID number that is inserted in the EBIZ_01 column for a particular change order can be obtained by means of the following query:
select change_id from eng_engineering_changeswherechange_notice=<AgileChangeOrder>
The business component ID that is inserted in the COMMON column can be any unique number.
The Agile PLM change order number and the Oracle E-business Suite organization corresponding to an Agile PLM site are inserted into the AGILE_01 column separated by "::".
The Item inventory number, the organization ID, and the operating unit ID are inserted in the EBIZ_01 column separated by "::"
The inventory item ID for a particular item can be obtained by means of the following query:
select inventory_item_id from mtl_system_items_bwheresegment1='<AgileItem>' select organization_id from mtl_parameterswhereorganization_code=<EbizOrgMappedtotheItemAgileSite>
The organization ID for the given item can be obtained by means of the following query:
select organization_id from mtl_parameters where organization_code=<EbizOrgMappedtotheItemAgileSite>
The business component ID that is inserted in the COMMON column can be any unique number.
The operating unit ID for the given item can be obtained by means of the following query:
SELECT operating_unit FROM ORG_ORGANIZATION_DEFINITIONS orgdef, HR_OPERATING_UNITS hrou WHERE orgdef.organization_id = <Organization id of EbizOrgMappedtotheItemAgileSite> AND hrou.organization_id=orgdef.operating_unit;
The Agile PLM item number and Oracle EBS organization corresponding to the Agile PLM site are inserted into the AGILE_01 column separated by "::".
Note:
Before you run the pre-built integration flows, the item revisions in Agile PLM and Oracle E-Business Suite should be synchronized after the manual data load is performed.
If you want to perform an initial data load yourself, after the data load is performed in edge applications, then you must manually populate the ITEM_ITEMID and CHANGE_CHANGEID cross-reference (XRef) tables after installing and configuring the PIP.
You must manually add the cross-reference data into the ITEM_ITEMID and CHANGE_CHANGEID XRef tables by using SQL insert statements.
For each Oracle E-Business Suite item processed through initial loads, the following rows need to be created in the XRef data table:
One row for Agile: AGILE_01
One row for Oracle E-Business Suite: EBIZ_01
One row for Common: COMMON
The physical XREF table (XREF_DATA) can be located in the database configured for FMW/SOA and contains the following columns:
Column Name | Description |
---|---|
XREF_TABLE_NAME |
This column stores the XREF data types. For example:
|
XREF_COLUMN_NAME |
This column stores the values indicating the edge applications and COMMON value:
|
ROW_NUMBER |
This column stores the GUID. |
VALUE |
This column stores the actual data that is cross-referenced. |
IS_DELETED |
This column indicates whether the column is deleted or not. For example, 'N'. |
LAST_MODIFIED |
This column stores last modified time. |
Table 11-13 ITEM_ITEMID XRef Table Value Format
XRef_Column_Name | Value |
---|---|
COMMON |
GUID |
AGILE_01 |
Agile ItemID::SiteFor example, Part1::V1 |
EBIZ_01 |
Ebiz ItemID::Organization ID::Operating Unit IDFor example, 60031::204::204 |
Sample SQL Insert Statements for ITEM_ITEMID Table:
For EBIZ_01:
INSERT INTO XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) VALUES (' oramds:/apps/AIAMetaData/xref/ITEM_ITEMID.xref ', 'EBIZ_01', 'BD618D40B30C11DEBFA5D9490F57512E ', '532922::204::204', 'N', SYSTIMESTAMP)
For AGILE_01:
INSERT INTO XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) VALUES (' oramds:/apps/AIAMetaData/xref/ITEM_ITEMID.xref ', ' AGILE_01', 'BD618D40B30C11DEBFA5D9490F57512E', ' TM0101P::V1', 'N', SYSTIMESTAMP)
For COMMON:
INSERT INTO XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) VALUES (' oramds:/apps/AIAMetaData/xref/ITEM_ITEMID.xref ', ' COMMON ', 'BD618D40B30C11DEBFA5D9490F57512E', '2d373037303636323539363632323735', 'N', SYSTIMESTAMP)
Table 11-14 Sample Data for XRef ITEM_ITEMID Table
XRef_Table | XRef_Column | Row_Number | Value | IS_Deleted | Last_Modified |
---|---|---|---|---|---|
oramds:/apps/AIAMetaData/xref/ITEM_ITEMID.xref |
EBIZ_01 |
BD618D40B30C11DEBFA5D9490F57512E |
532922::204::204 |
N |
2012-4-11.11.29. 54. 210000000 |
oramds:/apps/AIAMetaData/xref/ITEM_ITEMID.xref |
AGILE_01 |
BD618D40B30C11DEBFA5D9490F57512E |
TM0101P::V1 |
N |
2012-4-11.11.29. 54. 210000000 |
oramds:/apps/AIAMetaData/xref/ITEM_ITEMID.xref |
COMMON |
BD618D40B30C11DEBFA5D9490F57512E |
2d373037303636323539363632323735 |
N |
2012-4-11.11.29. 54. 210000000 |
Table 11-15 CHANGE_CHANGEID XRef Table Value Format
XRef_Column_Name | Value |
---|---|
COMMON |
GUID |
AGILE_01 |
Agile ItemID::SiteFor example, Part1::V1 |
EBIZ_01 |
Ebiz ChangeIDFor example, 60031 |
Sample SQL Insert Statements for CHANGE_CHANGEID Table
For EBIZ_01:
INSERT INTO XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) VALUES (' oramds:/apps/AIAMetaData/xref/CHANGE_CHANGEID.xref ', ' EBIZ_01', 'C7D0C3D0740D11E1BFF50FA2D024BE6E', '92219', 'N', SYSTIMESTAMP)
For AGILE_01:
INSERT INTO XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) VALUES (' oramds:/apps/AIAMetaData/xref/CHANGE_CHANGEID.xref ', ' AGILE_01', 'C7D0C3D0740D11E1BFF50FA2D024BE6E ', ' C00374::V1', 'N', SYSTIMESTAMP)
For COMMON:
INSERT INTO XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) VALUES (' oramds:/apps/AIAMetaData/xref/CHANGE_CHANGEID.xref ', ' COMMON', ' C7D0C3D0740D11E1BFF50FA2D024BE6E ', '2d383932333633343735363134363035', 'N', SYSTIMESTAMP)
Table 11-16 Sample Data for CHANGE_CHANGEID Table
XRef_Table | XRef_Column | Row_Number | Value | IS_Deleted | Last_Modified |
---|---|---|---|---|---|
oramds:/apps/AIAMetaData/xref/CHANGE_CHANGEID.xref |
EBIZ_01 |
C7D0C3D0740D11E1BFF50FA2D024BE6E |
92219 |
N |
2012-4-11.11.29. 54. 210000000 |
oramds:/apps/AIAMetaData/xref/CHANGE_CHANGEID.xref |
AGILE_01 |
C7D0C3D0740D11E1BFF50FA2D024BE6E |
C00374::V1 |
N |
2012-4-11.11.29. 54. 210000000 |
oramds:/apps/AIAMetaData/xref/CHANGE_CHANGEID.xref |
COMMON |
C7D0C3D0740D11E1BFF50FA2D024BE6E |
2d383932333633343735363134363035 |
N |
2012-4-11.11.29. 54. 210000000 |
DVMs are a standard feature of the Oracle SOA Suite. They enable you to equate lookup codes and other static values across applications, for example, FOOT and FT or US and USA.
DVMs are static in nature, though administrators can add additional maps as needed. Transactional business processes never update DVMs; they only read from them. DVMs are stored in XML files and cached in memory at run time.
DVM types are seeded for the Oracle Design to Release: Agile Product Lifecycle Management - JD Edwards EnterpriseOne flows and administrators can extend the list of mapped values by adding more maps. The DVM data should be synchronized with what the participating applications use. This synchronization should occur before any initial loads are run or any incremental transactional flows are initiated.
During installation, the DVMs used for the integration are imported with default data mappings. The values mapped by these DVMs must be changed as needed. Many DVMs are seeded and do not need to be changed. Because most of the Agile PLM attributes being mapped are list values, the Agile PLM data is not seeded and should be changed accordingly.
Note:
The ICC and manufacturers must be configured, before the DVMs are called. In addition, Orgs DVM must already be configured.
Note:
You can modify the values according to your requirements. You can add rows of value mappings, but you cannot change the DVM name, column name, or number of columns.
Table 11-17 lists DVMs used for this integration and their description:
Note:
Based on the custom environment, appropriate values must be updated in the following list of DVM's:
AGILE_SITE_TARGET
AGILE_TARGET_SITE
ECO_TYPECODE
ITEM_STATUS_CODE
ECO_STATUS_CODE
ITEM_UOM_CODE
Table 11-17 Domain Value Maps (DVM)
DVM | Description |
---|---|
AGILE_INTEGRATION_USERS |
The Agile PLM Change originator users are mapped to the RequesterPartyReference in the EBM. |
AGILE_SITE_TARGET_MAPPING |
DEFAULT_MASTER_ORG in Oracle E-Business Suite is specified here. This is used when the Multisite_Enabled property is set to False and no organization associated with the item in Agile. When the Multisite_Enabled property is True, the sites in Agile PLM are mapped to various orgs in Oracle E-Business Suite. A site could be mapped to multiple orgs in the Oracle E-Business Suite column with "|" delimiter. |
AGILE_TARGET_SITE_MAPPING |
The Oracle E-Business Suite orgs to Agile PLM sites are mapped. This is used for Oracle E-Business Suite to Agile PLM flows. A one-to-one mapping exists between the Oracle E-Business Suite org to Agile PLM site. |
EBIZ_AGILE_APPS_USER |
Used in mapping the user name depending on the Language code DVM. |
ECO_CLASSIFICATION_CODE |
Used for Oracle E-Business Suite attribute ECO_ATTR/ECO_CHANGE_ORDER_TYPE/CHANGE_MANAGEMENT_TYPE Query: SELECT change_mgmt_type_code FROM eng_change_order_types_VL where type_classification = 'CATEGORY' This DVM is needed for the CO Update flow. |
ECO_ENGINEERINGCHANGEORDERLINE_AVAILABLETOMRPINDICATOR |
Used for Oracle E-Business Suite attribute ECO_ATTR/ECO_REVISED_ITEM_TYPE/ECO_REVISED_ITEM_TYPE_ITEM/MRP_ACTIVE |
ECO_ENGINEERINGCHANGEORDERLINE_DISPOSITION_TYPE_CODE |
Used for Oracle E-Business Suite attribute ECO_REVISED_ITEM_TYPE/DISPOSITION_TYPE |
ECO_ENGINEERINGCHANGEORDERLINE_REVISEDBILLOFMATERIALS_BILLOFMATERIALSCOMPONENTITEM_ATPCHECKREQUIREDINDICATOR |
Used for Oracle E-Business Suite attribute ECO_REVISED_ITEM_TYPE/COMPONENT_ITEM_TBL/CHECK_ATP |
ECO_ENGINEERINGCHANGEORDERLINE_REVISEDBILLOFMATERIALS_BILLOFMATERIALSCOMPONENTITEM_BILLOFMATERIALSSUBSTITUTECOMPONENTITEM_CHANGETYPECODE |
Used for Oracle E-Business Suite attribute ECO_REVISED_ITEM_TYPE/COMPONENT_ITEM_TBL/COMPONENT_ITEM_TBL_ITEM/SUBSTITUTE_COMPONENT_TBL/SUBSTITUTE_COMPONENT_TBL_ITEM/ACD_TYPE |
ECO_ENGINEERINGCHANGEORDERLINE_REVISEDBILLOFMATERIALS_BILLOFMATERIALSCOMPONENTITEM_COSTROLLUPINCLUSIONINDICATOR |
Used for Oracle E-Business Suite attribute ECO_REVISED_ITEM_TYPE/COMPONENT_ITEM_TBL/ INCLUDE_IN_COST_ROLLUP |
ECO_ENGINEERINGCHANGEORDERLINE_REVISEDBILLOFMATERIALS_BILLOFMATERIALSCOMPONENTITEM_FRACTIONALLOWEDINDICATOR |
Used for Oracle E-Business Suite attribute ECO_REVISED_ITEM_TYPE/COMPONENT_ITEM_TBL/ENFORCE_INT_REQUIREMENTS |
ECO_ENGINEERINGCHANGEORDERLINE_REVISEDBILLOFMATERIALS_BILLOFMATERIALSCOMPONENTITEM_MUTUALLYEXCLUSIVEOPTIONINDICATOR |
Used for Oracle E-Business Suite attribute ECO_REVISED_ITEM_TYPE/COMPONENT_ITEM_TBL/MUTUALLY_EXCLUSIVE |
ECO_ENGINEERINGCHANGEORDERLINE_REVISEDBILLOFMATERIALS_BILLOFMATERIALSCOMPONENTITEM_OPTIONALINDICATOR |
Used for Oracle E-Business Suite attribute ECO_REVISED_ITEM_TYPE/COMPONENT_ITEM_TBL/OPTIONAL |
ECO_ENGINEERINGCHANGEORDERLINE_REVISEDBILLOFMATERIALS_BILLOFMATERIALSCOMPONENTITEM_REQUIREDFORREVENUEINDICATOR |
Used for Oracle E-Business Suite attribute ECO_REVISED_ITEM_TYPE/COMPONENT_ITEM_TBL/REQUIRED_FOR_REVENUE |
ECO_ENGINEERINGCHANGEORDERLINE_REVISEDBILLOFMATERIALS_BILLOFMATERIALSCOMPONENTITEM_REQUIREDTOSHIPINDICATOR |
Used for Oracle E-Business Suite attribute ECO_REVISED_ITEM_TYPE/COMPONENT_ITEM_TBL/REQUIRED_TO_SHIP |
ECO_ENGINEERINGCHANGEORDERLINE_REVISEDBILLOFMATERIALS_BILLOFMATERIALSCOMPONENTITEM_SHIPPINGALLOWEDINDICATOR |
Used for Oracle E-Business Suite attribute ECO_REVISED_ITEM_TYPE/COMPONENT_ITEM_TBL/SHIPPING_ALLOWED |
ECO_ENGINEERINGCHANGEORDERLINE_REVISEDBILLOFMATERIALS_BILLOFMATERIALSCOMPONENTITEM_SHIPPINGDOCUMENTVISIBILITYINDICATOR |
Used for Oracle E-Business Suite attribute ECO_REVISED_ITEM_TYPE/COMPONENT_ITEM_TBL/INCLUDE_ON_SHIP_DOCS |
ECO_ENGINEERINGCHANGEORDERLINE_REVISEDBILLOFMATERIALS_ENGINEERINGINDICATOR |
Used for Oracle E-Business Suite attribute ECO_REVISED_ITEM_TYPE/STRUCTURE_HEADER/ASSEMBLY_TYPE |
ECO_ENGINEERINGCHANGEORDERLINE_REVISEDBILLOFMATERIALS_NAME |
Used for Oracle E-Business Suite attribute ECO_REVISED_ITEM_TYPE / ALTERNATE_BOM_CODE |
ECO_ENGINEERINGCHANGEORDERLINE_REVISEDBILLOFMATERIALS_TYPECODE |
Used for Oracle E-Business Suite attribute ECO_REVISED_ITEM_TYPE/STRUCTURE_HEADER/STRUCTURE_TYPE_NAME, ECO_REVISED_ITEM_TYPE/STRUCTURE_TYPE_NAME |
ECO_ENGINEERINGCHANGEORDERLINE_UPDATEWIPINDICATOR |
Used for Oracle E-Business Suite attribute ECO_REVISED_ITEM_TYPE/UP_WIP |
ECO_PRIORITY_CODE |
Used for Oracle E-Business Suite attribute ECO_CHANGE_ORDER_TYPE/PRIORITY_CODE |
ECO_REASON_CODE |
Used for Oracle E-Business Suite attribute ECO_CHANGE_ORDER_TYPE/REASON_CODE. Used for Agile PLM's Reason Code attribute of a Change. |
ECO_STATUS_CODE |
Used for Oracle E-Business Suite attribute ECO_CHANGE_ORDER_TYPE/STATUS_CODE, ECO_REVISED_ITEM_TYPE/STATUS_CODE. Use for an Agile PLM Status attribute of a change. Here, the Oracle E-Business Suite values are language-independent. The query used for retrieving corresponding DVM values from Oracle E-Business Suite tables is: SELECT status_code FROM eng_change_statuses_vl WHERE status_name = <p_status_name>; |
ECO_TYPECODE |
Used for Oracle E-Business Suite attribute CHANGE_ORDER_TYPE_ID. Used for the Agile PLM Change Type attribute of a Change. Here, the Oracle E-Business Suite values are language-independent. The query used for retrieving corresponding DVM values from Oracle E-Business Suite tables is: SELECT change_order_type_id FROM eng_change_order_types_vl WHERE type_name = p_change_order_type AND change_mgmt_type_code = 'CHANGE_ORDER' AND type_classification='HEADER'; |
ITEM_BILLING_TYPE_CODE |
Used for Oracle E-Business Suite Item attribute ITEM_OBJ/SERVICE_OBJ_TYPE/MATERIAL_BILLABLE_FLAG |
ITEM_BOM_ITEM_TYPE_CODE |
Used for Oracle E-Business Suite Item attribute ITEM_OBJ/BOM_OBJ_TYPE/BOM_ITEM_TYPE |
ITEM_CONSIGNMENT_ITEM_INDICATOR |
Used for Oracle E-Business Suite Item attribute ITEM_OBJ/GPLANNING_OBJ_TYPE/CONSIGNED_FLAG |
ITEM_CONTRACT_TYPE_CODE |
Used for Oracle E-Business Suite Item attribute ITEM_OBJ/ASSET_OBJ_TYPE/CONTRACT_ITEM_TYPE_CODE |
ITEM_CREATE_FIXED_ASSET_INDICATOR |
Used for Oracle E-Business Suite Item attribute ITEM_OBJ/SERVICE_OBJ_TYPE/ASSET_CREATION_CODE |
ITEM_DUAL_UOM_TRACKING_INDICATOR |
Used for Oracle E-Business Suite Item attribute ITEM_OBJ/MAIN_OBJ_TYPE/TRACKING_QUANTITY_IND |
ITEM_EFFECTIVITY_CONTROL_CODE |
Used for Oracle E-Business Suite Item attribute ITEM_OBJ/BOM_OBJ_TYPE/EFFECTIVITY_CONTROL |
ITEM_INDICATOR |
YES/NO DVM used for multiple Item attributes ITEM_OBJ/INVENTORY_OBJ_TYPE/SERIAL_STATUS_ENABLED, ITEM_OBJ/INVENTORY_OBJ_TYPE/LOT_STATUS_ENABLED, ITEM_OBJ/INVENTORY_OBJ_TYPE/CYCLE_COUNT_ENABLED_FLAG, ITEM_OBJ/INVENTORY_OBJ_TYPE/LOT_MERGE_ENABLED, ITEM_OBJ/INVENTORY_OBJ_TYPE/LOT_SPLIT_ENABLED, ITEM_OBJ/INVENTORY_OBJ_TYPE/STOCK_ENABLED_FLAG, ITEM_OBJ/PURCHASING_OBJ_TYPE/INSPECTION_REQUIRED_FLAG, ITEM_OBJ/PURCHASING_OBJ_TYPE/PURCHASING_ENABLED_FLAG, ITEM_OBJ/PURCHASING_OBJ_TYPE/RECEIPT_REQUIRED_FLAG, ITEM_OBJ/PURCHASING_OBJ_TYPE/RFQ_REQUIRED_FLAG, ITEM_OBJ/PURCHASING_OBJ_TYPE/TAXABLE_FLAG, ITEM_OBJ/PURCHASING_OBJ_TYPE/MUST_USE_APPROVED_VENDOR_FL, ITEM_OBJ/RECEIVING_OBJ_TYPE/ALLOW_SUBSTITUTE_RECEIPTS_F, ITEM_OBJ/RECEIVING_OBJ_TYPE/ALLOW_UNORDERED_RECEIPTS_FL, ITEM_OBJ/BOM_OBJ_TYPE/BOM_ENABLED_FLAG, ITEM_OBJ/BOM_OBJ_TYPE/ENG_ITEM_FLAG, ITEM_OBJ/COSTING_OBJ_TYPE/COSTING_ENABLED_FLAG, ITEM_OBJ/COSTING_OBJ_TYPE/INVENTORY_ASSET_FLAG, ITEM_OBJ/ORDER_OBJ_TYPE/CUSTOMER_ORDER_FLAG, ITEM_OBJ/ORDER_OBJ_TYPE/RETURNABLE_FLAG |
ITEM_INVENTORY_PLANNING_CODE |
Used for Oracle E-Business Suite Item attribute ITEM_OBJ/GPLANNING_OBJ_TYPE/INVENTORY_PLANNING_CODE |
ITEM_LOTEXPIRATION_ON_RECEIPT_INDICATOR |
Used for Oracle E-Business Suite Item attribute ITEM_OBJ/INVENTORY_OBJ_TYPE/LOT_CONTROL_CODE |
ITEM_MAKEORBUY_CODE |
Used for Oracle E-Business Suite Item attribute ITEM_OBJ/GPLANNING_OBJ_TYPE/PLANNING_MAKE_BUY_CODE |
ITEM_PRIMARYCLASSIFICATIONCODE |
Used for Oracle E-Business Suite Item attributes ITEM_OBJ/MAIN_OBJ_TYPE/ITEM_CATALOG_GROUP_CODE. The Agile PLM PartType of an item is mapped to the Oracle E-Business Suite item catalog category (ICC). |
ITEM_RECEIVING_ROUTING_CODE |
Used for Oracle E-Business Suite Item attribute ITEM_OBJ/RECEIVING_OBJ_TYPE/RECEIVING_ROUTING_ID |
ITEM_REPLENISHMENT_SOURCE_CODE |
Used for Oracle E-Business Suite Item attribute ITEM_OBJ/GPLANNING_OBJ_TYPE/SOURCE_TYPE |
ITEM_RESERVATION_ALLOWED_INDICATOR |
Used for Oracle E-Business Suite Item attribute ITEM_OBJ/INVENTORY_OBJ_TYPE/RESERVABLE_TYPE |
ITEM_RETURN_INSPECTION_REQUIRED_INDICATOR |
Used for Oracle E-Business Suite Item attribute ITEM_OBJ/PURCHASING_OBJ_TYPE/INSPECTION_REQUIRED_FLAG |
ITEM_SERIALIZATION_EVENT_CODE |
Used for Oracle E-Business Suite Item attribute ITEM_OBJ/INVENTORY_OBJ_TYPE/SERIAL_NUMBER_CONTROL_CODE |
ITEM_SERVICE_REQUEST_ENABLED_INDICATOR |
Used for Oracle E-Business Suite Item attribute ITEM_OBJ/ASSET_OBJ_TYPE/SERV_REQ_ENABLED_CODE |
ITEM_STATUS_CODE |
Used for Oracle E-Business Suite Item attributes ITEM_OBJ/MAIN_OBJ_TYPE/INVENTORY_ITEM_STATUS_CODE. The Agile PLM Item Lifecycle phase attribute is mapped. |
ITEM_TRACK_INSTANCE_INDICATOR |
Used for Oracle E-Business Suite Item attribute ITEM_OBJ/SERVICE_OBJ_TYPE/COMMS_NL_TRACKABLE_FLAG |
ITEM_UOM_CODE |
Unit of Measure DVM for Item attributes ITEM_OBJ/PHYSICAL_OBJ_TYPE/VOLUME_UOM_CODE, ITEM_OBJ/PHYSICAL_OBJ_TYPE/WEIGHT_UOM_CODE In the VM flow, for the row in column COMMON that has value 'EACH', you must update the column AGILE_01 with the value 'Each'. |
ITEM_UOM_CONVERSION_USAGE_CODE |
Used for Oracle E-Business Suite Item attribute ITEM_OBJ/MAIN_OBJ_TYPE/ALLOWED_UNITS_LOOKUP_CODE |
ITEM_WIP_SUPPLY_CODE |
Used for Oracle E-Business Suite Item attribute ITEM_OBJ/WIP_OBJ_TYPE/WIP_SUPPLY_TYPE |
LANGUAGE_CODE |
Language Code DVM for common and system-specific language code names are mapped. |
This integration uses various configuration parameters that control the behavior of the flow. AIAConfigurationProperties.xml, a standard AIA XML configuration file, is used for capturing the configuration parameters. The AIAConfigurationProperties.xml file is located at $AIA_HOME/aia_instances/$INSTANCE_NAME/AIAMetaData/config. This AIA configuration file supports the system-level configuration parameters, service-level parameters, and module configuration parameters.
System-level parameters apply to all integrations running on the Service-Oriented Architecture (SOA) suite. Service-level parameters can be configured at the individual service level, such as Application Business Connector Service (ABCS).
Note:
The configuration properties from Agile PLM and Oracle E-Business Suite are listed separately in this section, only for the purpose of identification. The actual AIAConfigurationProperties.xml file on the AIA server is a merge of the two.
This integration uses the following types of configuration parameters:
Pre-built integration level configuration parameters: Pre-built integration configuration parameters are implemented by means of the AIA module configuration entry. The module configuration entry has a name and can contain any number of configuration parameters. A naming convention of pre-built integrations, PIPName is used for naming modules. The parameters inside the module are named with a cascaded naming convention, where individual words are separated with dots.
For example, agile.replicate.item
Service-level configuration parameters: While most configuration requirements are satisfied by the PIP level configuration parameters, sometimes the behavior of a flow needs to be controlled at the service level. These parameters can be captured by means of AIA service configuration parameters. Service configuration entry is identified by the service name such as CreateItemAgileReqABCSImpl. The parameter names themselves are named with a cascaded naming convention as explained previously.
For more information about requirements for working with AIAConfigurationProperties.xml, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1, How to Set Up AIA Workstation.
Table 11-18 lists the configuration parameters for Agile PLM:
Table 11-18 Agile PLM Configuration Properties
Properties | Default Value/Setting | Description |
---|---|---|
ModuleName |
Agile |
|
LANG_LOCALE |
English |
Specifies the language locale information |
MULTISITE_ENABLED |
TRUE |
When set to TRUE, the sites specified in Sites Tab of Items are used to determine the organizations in Oracle E-Business Suite to which they are mapped. When set to FALSE, the Page2 Multilist01attribute is used to determine the organizations in Oracle E-Business Suite to which the item will be extended. |
Item.UnitCostAttribute |
Site.Numeric01 |
Determines the attribute to which the unit cost from Oracle E-Business Suite will be updated in Agile PLM. |
Item.AvailableQuantityAttribute |
Site.Numeric02 |
Determines the attribute to which the available quantity from Oracle E-Business Suite will be updated in Agile PLM. |
Item.OnHandQuantityAttribute |
Site.Numeric03 |
Determines the attribute to which the on-hand quantity from Oracle E-Business Suite will be updated in Agile PLM. |
Item.ReservedQuantityAttribute |
Site.Numeric04 |
Determines the attribute to which the reserved quantity from Oracle E-Business Suite will be updated in Agile PLM. |
Change.TransferStatusAttribute |
PageTwo.Text02 |
Determines the attribute of the transfer status of a change. When the change flow is from Agile PLM to Oracle E-Business Suite, the possible values are Transferred and Errored. When the change flow is from Oracle E-Business Suite to Agile PLM, the value will be the same as that of the status of the change in all the organizations of Oracle E-Business Suite. |
REPLICATE_BOM_ENABLED |
FALSE |
Used for sample replicate BOM customization. |
Change.TransferStatusDetailedMessageAttribute |
PageTwo.Multitext35 |
Contains detailed error message in case of Transfer Validation failure |
COMMON_BOM_ENABLED |
FALSE |
Used for sample common BOM customization. |
AgileATOActionItemStatus |
Not Accepted |
Determine the value of Status in Action Item row in an ATO in Agile PLM. Default value is the recommended value. This can be updated with valid Status value available in Agile PLM. |
AgileATOActionItemSubject |
Integration Error |
Determine the value of Subject in Action Item row in an ATO in Agile PLM. |
EnableAgileATOActionItemIntegration |
TRUE |
This value can be updated to FALSE to disable Error Landing Feature. |
User |
Agile PLM user provided at the time of PIP installation. |
Action Item gets assigned to User provided here in case Change Analyst information is not available in a Change Order. |
Note:
Multisite enabled property is governed by distributed processing aspects in Agile PLM. When it is set to TRUE (default), the Item.UnitCostAttribute, Item.AvailableQuantityAttribute, Item.OnHandQuantityAttribute, and Item.ReservedQuantityAttribute can be set to Site Tab Flex Attributes. You can use Numeric, Text, or Money flex-fields on the Site tab for these settings, and it is denoted by the first element, Site. For example, Site.Numeric01. When it is set to FALSE, all these attributes need to be set to Page2 or Page3 flex-fields. Hence, the settings will need to be changed to PageTwo.Numeric01 or PageThree.Numeric01 accordingly. The names of the attributes can be derived from the ItemABM Schema, which can be found in Agile PLM Interfaces.
Note:
The Composite Application Validation System (CAVS) feature is not supported for the flows in this release. However, the CAVS enabling properties for the flows are deployed.
Table 11-19 lists the properties of the UpdateEngineeringChangeOrderListAgileProvABCSImpl service:
Table 11-19 Properties of UpdateEngineringChangeOrderListAgileProvABCSImpl service
Property | Default Value/Setting | Description |
---|---|---|
ABCSExtension.PreProcessABM |
false |
User exit for the pre-process Application Business Message (ABM) should be called or not |
ABCSExtension.PreProcessEBM |
false |
User exit for the pre-process Enterprise Business Message (EBM) should be called or not |
ABCSExtension.PostProcessEBM |
false |
User exit for the post-process EBM should be called or not |
ABCSExtension.PostProcessABM |
false |
User exit for the post-process ABM should be called or not |
TRACE.LOG.ENABLED |
true |
Use tracelog for the flow |
Default.SystemID |
AGILE_01 |
System ID of Agile PLM application instance |
Routing.ChangeABSService.AGILE_01.EndpointURI |
http://${agile.host}:${agile.port}/AgilePLM/integration/services/ChangeABS |
ChangeABS URL: When the RouteToCAVS property is set to false, use the URL mentioned to connect to the Agile PLM ChangeABS Service for the ChangeABSService partnerlink. This can be modified to point it to some other service where message should be routed like CAVS service. This is the default value. This can be modified to point it to some other service where message should be routed like CAVS service. |
Routing.MergeABSService.AGILE_01.EndpointURI |
http://${agile.host}:${agile.port}/AgilePLM/integration/services/MergeABSService_Port |
MergeABS URL: When the RouteToCAVS property is set to false, use the URL mentioned to connect to the Agile PLM MergeABS Service for the MergeABSService partnerlink. This is the default value. This can be modified to point it to some other service where message should be routed like CAVS service. |
Routing.ChangeStatusService.AGILE_01.EndpointURI |
http://${agile.host}:${agile.port}/AgilePLM/integration/services/ChangeABS |
ChangeABS URL: When the RouteToCAVS property is set to False, use the URL mentioned to connect to the Agile PLM ChangeABS Service for the ChangeStatusService partnerlink. This is the default value. This can be modified to point it to some other service where message should be routed like CAVS service. |
Routing.ChangeStatusDBAdapter.AGILE_01.EndpointURI |
http://${agile.host}:${agile.port}/ soa-infra/services/default/ChangeStatusDBAdapter/AIASystem.Agile.ABCSImpl.ChangeStatusDBAdapter_RS_ep?WSDL |
ChangeABS URL: When the RouteToCAVS property is set to False, use the URL mentioned to connect to the Agile PLM ChangeABS Service for the EDB Adapter partnerlink. This is the default value. This can be modified to point it to some other service where message should be routed like CAVS service. |
Routing.EngineeringChangeOrderResponseEBS.UpdateEngineeringChangeOrderListResponse.RouteToCAVS |
false |
|
Routing.EngineeringChangeOrderResponseEBS.UpdateEngineeringChangeOrderListResponse.CAVS.EndpointURI |
http://${http.hostname}:${http.port}/AIAValidationSystemServlet/asyncresponsesimulator |
CAVS SOAP URL When the RouteToCAVS property is set to true, use the URL mentioned to connect to CAVS. This invocation relates to the ECO response EBS |
Routing.EngineeringChangeOrderResponseEBS.UpdateEngineeringChangeOrderListResponse.MessageProcessingInstruction.EnvironmentCode |
PRODUCTION |
Environment code such as 'PRODUCTION'/ 'CAVS'. Identifies the installation environment |
Routing.ChangeStatusService.AGILE_01.EndpointURI |
http://${agile.host}:${agile.port}/AgilePLM/integration/services/ChangeABS |
ChangeABS URL: When the RouteToCAVS property is set to False, use the URL mentioned to connect to the Agile PLM ChangeABS Service for the ChangeStatusService partnerlink. |
Routing.ChangeStatusDBAdapter.AGILE_01.EndpointURI |
http://${agile.host}:${agile.port}/ soa-infra/services/default/ChangeStatusDBAdapter/AIASystem.Agile.ABCSImpl.ChangeStatusDBAdapter_RS_ep?WSDL |
ChangeABS URL: When the RouteToCAVS property is set to False, use the URL mentioned to connect to the Agile PLM ChangeABS Service for the EDB Adapter partnerlink. |
Table 11-20 lists the properties of the UpdateItemBalanceListAgileProvABCSImpl service:
Table 11-20 UpdateItemBalanceListAgileProvABCSImpl service
Property | Default Value/Setting | Description |
---|---|---|
ABCSExtension.PreProcessABM |
false |
User exit for the pre-process ABM should be called |
ABCSExtension.PreProcessEBM |
false |
User exit for the pre-process EBM should be called |
ABCSExtension.PostProcessEBM |
false |
User exit for the post-process EBM should be called |
ABCSExtension.PostProcessABM |
false |
User exit for the post-process ABM should be called |
TRACE.LOG.ENABLED |
false |
Use tracelog for the flow |
Default.SystemID |
AGILE_01 |
System ID of the Agile PLM instance |
Routing.ItemABSService.AGILE_01.EndpointURI |
http://${agile.host}:${agile.port}/Agile/integration/services/ItemABS |
ItemABS URL: When the RouteToCAVS property is set to False, use the URL mentioned to connect to the Agile PLM ItemABS Service. This is the default value. This can be modified to point it to some other service where message should be routed like CAVS service. |
Routing.ItemBalanceResponseEBS.UpdateItemBalanceListResponse.MessageProcessingInstruction.EnvironmentCode |
PRODUCTION |
Environment code such as 'PRODUCTION'/ 'CAVS'. Identifies the installation environment. |
Table 11-21 lists the properties of the UpdateItemListAgileProvABCSImpl service:
Table 11-21 UpdateItemListAgileProvABCSImpl service
Property | Default Value/Setting | Description |
---|---|---|
ABCSExtension.PreProcessABM |
false |
Decides whether the user exit for the pre-process ABM should be called |
ABCSExtension.PreProcessEBM |
false |
Decides whether the user exit for the pre-process EBM should be called |
ABCSExtension.PostProcessEBM |
false |
Decides whether the user exit for the post-process EBM should be called |
ABCSExtension.PostProcessABM |
false |
Decides whether the user exit for the post-process ABM should be called |
TRACE.LOG.ENABLED |
false |
Use tracelog for the flow |
Default.SystemID |
AGILE_01 |
System ID of the Agile PLM application instance |
Routing.ItemResponseEBS.UpdateItemListResponse.MessageProcessingInstruction.EnvironmentCode |
PRODUCTION |
Environment code such as 'PRODUCTION'/ 'CAVS' and so on. Identifies the installation environment. |
Routing.ItemABSService.AGILE_01.EndpointURI |
http://${agile.host}:${agile.port}/Agile/integration/services/ItemABS |
ItemABS URL: When the RouteToCAVS property is set to False, use the URL mentioned to connect to the Agile PLM ItemABS Service. This is the default value. This can be modified to point it to some other service where message should be routed like CAVS service. |
Routing.ItemResponseEBS.UpdateItemListResponse.RouteToCAVS |
false |
If set to True, it is route to CAVS; otherwise, routed to response item EBS. This invocation is regarding the item response EBS |
Routing.ItemResponseEBS.UpdateItemListResponse.CAVS.EndpointURI |
http://${http.hostname}:${http.port}/AIAValidationSystemServlet/asyncresponsesimulator |
CAVS URL; When the RouteToCAVS property is set to True, use the URL mentioned to connect to CAVS. This invocation is regarding item response EBS |
Table 11-22 lists the properties of the SyncBillOfMaterialsConfigurationListAgileProvABCSImpl service:
Table 11-22 SyncBillOfMaterialsConfigurationListAgileProvABCSImpl service
Property | Default Value/Setting | Description |
---|---|---|
Default.SystemID |
AGILE_01 |
System ID for mapping |
Routing.BillOfMaterialsConfigurationEBS.SyncBillOfMaterilasConfigurationList.RouteToCAVS |
false |
NA |
Routing.ConfiguratorTerminationService.AGILE_01.EndpointURI |
http://${agile.host}:${agile.port}/${agiag.path}/vm/services/ConfiguratorTerminationService |
Partner link end point URL This is the default value. This can be modified to point it to some other service where message should be routed like CAVS service. |
Routing.BillOfMaterialsConfigurationEBS.SyncBillOfMaterialsConfigurationList.CAVS.EndpointURI |
http://${http.hostname}:${http.port}/AIAValidationSystemServlet/asyncresquestrecipient |
When RouteToCAVS property is set to true, use the URL mentioned to connect to CAVS |
ABCSExtension.PreXformEBMtoABM |
false |
User exit for the pre-process EBM should be called or not |
ABCSExtension.PostXformEBMtoABM |
false |
User exit for the post-process EBM should be called or not |
ABCSExtension.PreInvokeConfiguratorTerminationMessage |
false |
User exit for the pre-process invoke partner link should be called or not |
ABCSExtension.PostInvokeConfiguratorTerminationMessage |
false |
User exit for the post-process invoke partner link should be called or not |
Table 11-23 lists the properties of the ProcessEngineeringChangeOrderAgileReqABCSImpl service:
Table 11-23 ProcessEngineeringChangeOrderAgileReqABCSImpl service
Property | Default Value/Setting | Description |
---|---|---|
ABCSExtension.PreProcessABM |
false |
User exit for the pre-process ABM should be called |
ABCSExtension.PreProcessEBM |
false |
User exit for the pre-process EBM should be called |
ABCSExtension.PostProcessEBM |
false |
User exit for the post-process EBM should be called |
ABCSExtension.PostProcessABM |
false |
User exit for the post-process ABM should be called |
TRACE.LOG.ENABLED |
false |
Use tracelog for the flow |
Default.SystemID |
AGILE_01 |
System ID of the Agile PLM application instance |
Routing.ChangeABSService.AGILE_01.EndpointURI |
http://${agile.host}:${agile.port}/AgilePLM/integration/services/ChangeABS |
ChangeABS URL: When the RouteToCAVS property is set to false, use the URL mentioned to connect to the Agile PLM ChangeABS Service for the ChangeABSService partnerlink. This is the default value. This can be modified to point it to some other service where message should be routed like CAVS service. |
Routing.EngineeringChangeOrderEBS.CreateEngineeringChangeOrderList.RouteToCAVS |
false |
If set to True, route to CAVS; otherwise, route to EngineeringChangeOrder EBS (Enterprise Business Service) |
Routing.EngineeringChangeOrderEBS.CreateEngineeringChangeOrderList.CAVS.EndpointURI |
http://${http.hostname}:${http.port}/AIAValidationSystemServlet/asyncresponsesimulator |
CAVS URL When the RouteToCAVS property is set to True, use the URL mentioned to connect to CAVS |
Routing.EngineeringChangeOrderEBS.CreateEngineeringChangeOrderList.MessageProcessingInstruction.EnvironmentCode |
PRODUCTION |
Environment code such as 'PRODUCTION'/ 'CAVS'. Identifies the installation environment |
Routing.TableService.AGILE_01.EndpointURI |
http://${agile.host}:${agile.port}/CoreService/services/Table |
This is the default value. This can be modified to point it to some other service where message should be routed like CAVS service. |
Table 11-24 lists the properties of the SyncItemListAgileReqABCS service:
Table 11-24 SyncItemListAgileReqABCS service
Property | Default Value/Setting | Description |
---|---|---|
TRACE.LOG.ENABLED |
false |
NA |
Default.SystemID |
AGILE_01 |
System ID of the Agile PLM instance. |
Table 11-25 lists the properties of the SyncItemListAgileReqABCSImpl service:
Table 11-25 SyncItemListAgileReqABCSImpl service
Property | Default Value/Setting | Description |
---|---|---|
ABCSExtension.PreProcessABM |
false |
NA |
ABCSExtension.PreProcessEBM |
false |
NA |
ABCSExtension.PostProcessEBM |
false |
NA |
ABCSExtension.PostProcessABM |
false |
NA |
TRACE.LOG.ENABLED |
false |
NA |
Default.SystemID |
AGILE_01 |
System ID of the Agile PLM application instance |
Routing.ItemEBS.SyncItemList.RouteToCAVS |
false |
If set to True, route to CAVS; otherwise, route to Item EBS |
Routing.ItemEBS.SyncItemList.CAVS.EndpointURI |
http://${http.hostname}:${http.port}/AIAValidationSystemServlet/asyncresponsesimulator |
CAVS URL; When the RouteToCAVS property is set to True, use the URL mentioned to connect to CAVS |
Routing.ItemEBS.SyncItemList.MessageProcessingInstruction.EnvironmentCode |
PRODUCTION |
Environment code such as 'PRODUCTION'/ 'CAVS' and so on. Identifies the installation environment |
Table 11-26 lists the properties of the ValidateEngineeringChangeOrderListAgileReqABCSImpl service:
Table 11-26 ValidateEngineeringChangeOrderListAgileReqABCSImpl service
Property | Default Value/Setting | Description |
---|---|---|
ABCSExtension.PreProcessABM |
false |
NA |
ABCSExtension.PreProcessEBM |
false |
NA |
ABCSExtension.PostProcessEBM |
false |
NA |
ABCSExtension.PostProcessABM |
false |
NA |
TRACE.LOG.ENABLED |
false |
NA |
Default.SystemID |
AGILE_01 |
NA |
Routing.ChangeABSService.AGILE_01.EndpointURI |
http://${agile.host}:${agile.port}/AgilePLM/integration/services/ChangeABS |
ChangeABS URL: When the RouteToCAVS property is set to false, use the URL mentioned to connect to the Agile PLM ChangeABS Service for the ChangeABSService partnerlink. This is the default value. This can be modified to point it to some other service where message should be routed like CAVS service. |
Routing.EngineeringChangeOrderEBS.ValidateEngineeringChangeOrderList.RouteToCAVS |
false |
If set to True, route to CAVS; otherwise, route to EngineeringChangeOrder EBS (Enterprise Business Service) |
Routing.EngineeringChangeOrderEBS.ValidateEngineeringChangeOrderList.CAVS.EndpointURI |
http://${http.hostname}:${http.port}/AIAValidationSystemServlet/asyncresponsesimulator |
CAVS URL When the RouteToCAVS property is set to True, use the URL mentioned to connect to CAVS |
Routing.EngineeringChangeOrderEBS.ValidateEngineeringChangeOrderList.MessageProcessingInstruction.EnvironmentCode |
PRODUCTION |
Environment code such as 'PRODUCTION'/ 'CAVS'. Identifies the installation environment |
Routing.TableService.AGILE_01.EndpointURI |
http://${agile.host}:${agile.port}/CoreService/services/Table |
This is the default value. This can be modified to point it to some other service where message should be routed like CAVS service. |
Table 11-27 lists the properties of the GetConfiguratorURLAgileReqABCSImpl service:
Table 11-27 GetConfiguratorURLAgileReqABCSImpl service
Property | Default Value/Setting | Description |
---|---|---|
Default.SystemID |
AGILE_01 |
System ID for mapping |
Agile _site.ColumnName |
AGILE_SITE |
The Agile PLM site column name in the DVM |
Agile _site.TargetColumnName |
TARGET_VALUE |
The Agile PLM site target column name in the DVM |
Agile _site.DefaultOrgPropertyName |
DEFAULT_MASTER_ORG |
The Agile PLM site default property name in the DVM |
Routing.BillOfMaterialsConfigurationEBS.GetConfiguratorURL.RouteToCAVS |
false |
NA |
Routing.BillofMaterialsConfigurationEBS.GetConfiguratorURL.CAVS.EndpointURI |
http://${http.hostname}:${http.port}/AIAValidationSystemServlet/asyncresponserecipient |
When the RouteToCAVS property is set to True, use the URL mentioned to connect to CAVS |
ABCSExtension.PreXformABMtoEBM |
false |
User exit for the pre-process ABM should be called |
ABCSExtension.PreInvokeEBS |
false |
User exit for the pre-process Invoke should be called |
ABCSExtension.PostXformABMtoEBM |
false |
User exit for the post-process ABM should be called |
ABCSExtensionPostReceiveGetURLResponse |
false |
User exit for the post-process EBM should be called |
Return_URL |
http://${http.hostname}:${http.port}/AGILE_PATH/default/actionDialogs/FinishExternalConfigurator.jsp |
The Return URL to be used by the Oracle E-Business Suite for returning after configuration |
Table 11-28 lists configuration properties for Oracle E-Business Suite:
Table 11-28 E-Business Suite Configuration Properties
Property | Default Value/Setting | Description |
---|---|---|
ModuleName |
Ebiz |
|
FIXED_ORG_FOR_INBOUND_DATA_TRANSFER |
If set, Oracle E-Business Suite to Agile PLM flows will publish data only for this particular organization code |
|
IS_PIM_INSTALLED |
false |
If set to True, PIM is installed; False indicates a non-PIM scenario. It should be left as False for this release with Oracle E-Business Suite 11i. |
DEFAULT_MASTER_ORG |
Default organization when the incoming one is empty for New Part Request |
|
RESPONSIBILITY |
System Administrator |
Responsibility for setting FND Apps Context |
USER |
mfg |
User for setting FND Apps Context (User must be a valid user in Ebiz with system administrator privileges). |
EBIZ_01.SERVER_TIMEZONE |
GMT-08:00 |
Corresponds to GMT offset of Oracle E-Business Suite instance Please refer to Oracle E-Business profile SERVER_TIMEZONE_ID to configure this property, for example, '-07:00' or 'GMT-07:00' or 'PST' |
EBIZ_01.LANG |
ENG |
|
UNIMPLEMENTED_BOM_UPDATES_ALLOWED |
True/False |
If this property is set to 'T' redlining of unimplemented BOMs can be done from Agile. If it is 'F' only implemented BOMs can be redlined. |
ALLOW_LIFECYCLE_PHASE_SKIP |
True/False |
If this property is set to 'T', life cycle phases in Ebiz can be skipped, if it is 'F', life cycle phase skip is not possible. |
Table 11-29 lists the properties of the CreateEngineeringChangeOrderListEbizProvABCSImpl service:
Table 11-29 CreateEngineeringChangeOrderListEbizProvABCSImpl service
Property | Default Value/Settings | Description |
---|---|---|
Default.SystemID |
EBIZ_01 |
Used to get the default XREF target column name when TargetId is empty in the incoming EBM |
ROUTING.ECOSERVICE.EBIZ_01.ENDPOINTURI |
http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default/CreateEngineeringChangeOrderListEbizAdapter/CreateEngineeringChangeOrderListEbizAdapter_ep |
ECOService run-time target endpoint URI |
ROUTING.ECOSERVICE.EBIZ_01.ENDPOINTURI |
http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default/CreateEngineeringChangeOrderListEbizAdapter/CreateEngineeringChangeOrderListEbizAdapter_ep |
ECOService run-time target endpoint URI This is the default value. This can be modified to point it to some other service where message should be routed like CAVS service. |
Routing.EngineeringChangeOrderResponseEBS.RouteToCAVS |
false |
Use CAVS for EngineeringChangeOrderResponseEBS |
ROUTING.ENGINEERINGCHANGEORDERRESPONSEEBS.CAVS.ENDPOINTURI |
http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/AIAValidationSystemServlet/asyncresponsesimulator |
EngineeringChangeOrderResponseEBS endpoint URI when set to CAVS |
ABCSEXTENSION.PREPROCESSABM |
false |
User exit for the pre-process ABM should be called or not |
ABCSEXTENSION.POSTPROCESSABM |
false |
User exit for the post-process ABM should be called or not |
ABCSEXTENSION.PREPROCESSEBM |
false |
User exit for the pre-process EBM should be called or not |
ABCSEXTENSION.POSTPROCESSEBM |
false |
User exit for the post-process EBM should be called or not |
CUSTOM.TRANSFORMATIONS.EBM_TO_ABM |
false |
Use Custom transformation for EBM to ABM |
CUSTOM.TRANSFORMATIONS.ABM_TO_EBM |
false |
Use Custom transformation for ABM to EBM |
ASSIGN_ITEM_TO_CHILD_ORG |
T |
Indicates that if Components and SubstituteComponenst coming in do not exist in context, org should be assigned from master org |
TEMPLATE_FOR_ITEM_UPDATE_ALLOWED |
F |
During item update, if this config value is T, then the item template can be updated; if it is F item, the template cannot be changed |
VALIDATE_REVISED_ITEM_REVISION |
F |
If this Config value is set to T, then in the MCO and SCO case, the incoming revision is either the Current or a Future implemented revision T to validate current item revision, F not to validate current item revision |
DEFAULT_STRUCTURE_TYPE |
EBOM |
This parameter is only for the R12 case. If the incoming payload does not have any value for structure type, then the value specified for this config parameter will be supplied by default. The default value provided for this property in the AIAConfig file should be a valid structure_type in the Oracle E-Business Suite database. Use this script to retrieve a valid structure type from Oracle E-Business Suite: SELECT STRUCTURE_TYPE_NAME FROM BOM_STRUCTURE_TYPES_B, where disable_date is null or disable_date > sysdate |
CREATE_ERP_CHANGE_ORDER |
T |
If the value of this property is T, an ERP change order is created. If the value of this property is F, an Agile PLM change order is created. If users have set up some predefined workflow set for the change order type in Oracle E-Business Suite, then that will be effective only for the Agile PLM type of change orders. |
REPLICATE_BOM_VIEW_SCOPE |
CURRENT_AND_FUTURE |
Indicates the BOM view scope for the replicate BOM case 'ALL' -- All the BOMs should be considered for replicating BOM from source org to destination org 'CURRENT' -- BOM that is effective currently should be considered 'CURRENT_AND_FUTURE' -- BOM that is effective currently and also those with future effective dates should be considered |
REPLICATE_BOM_IMPLEMENTATION_SCOPE |
All |
Indicates the BOM implementation scope for a replicate BOM case All - implemented and unimplemented BOMs 'IMPLEMENTED' -- Implemented BOMs in the source org will be considered for replicating BOM from source org to destination org 'UNIMPLEMENTED' -- Only unimplemented BOMs will be considered |
TRACE.LOG.ENABLED |
false |
Use tracelog for the flow |
STANDALONE_BOM_UPDATES_ALLOWED |
true |
The default value for this property is set to true so that by default, legacy BOM data can be updated by the integration. If only the BOMs created by this integration need to be updated (not including legacy BOMs), this property should be set to false. |
ASSIGN_DEFAULT_TEMPLATE_FROM_ICC |
false |
If this property is set to true and the user does not pass a template, then the ICC has a default template attached to it that will be applied to the item. If this property is set to false, the default template attached to the ICC will not be considered. |
UNIMPLEMENTED_BOM_UPDATES_ALLOWED |
T or F |
If this property is set to 'T' redlining of unimplemented BOM's can be done from Agile. If it is set to 'F' then only implemented BOM's can be redlined. |
ALLOW_LIFECYCLE_PHASE_SKIP |
T or F |
If this property is set to T, the life cycle phases in EBS can be skipped. if it is set to F, the life cycle phase skip is not possible. |
Table 11-30 lists the properties of the ValidateEngineeringChangeOrderListEbizProvABCSImpl service:
Table 11-30 ValidateEngineeringChangeOrderListEbizProvABCSImpl service
Property | Default Value/Setting | Description |
---|---|---|
Default.SystemID |
EBIZ_01 |
Used to get the default XREF target column name when TargetId is missing in the incoming EBM |
Routing.EngineeringChangeOrderResponseEBS.RouteToCAVS |
false |
Use CAVS for EngineeringChangeOrderResponseEBS |
Routing.ValidateECOService.EBIZ_01.EndpointURI |
http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default/ValidateEngineeringChangeOrderListEbizAdapter/ValidateEngineeringChangeOrderListEbizAdapter_ep |
ValidateECOService EndpointURI when set to CAVS This is the default value. This can be modified to point it to some other service where message should be routed like CAVS service. |
Routing.EngineeringChangeOrderResponseEBS.CAVS.EndpointURI |
http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/AIAValidationSystemServlet/asyncresponsesimulator |
EngineeringChangeOrderEBS EndpointURI when set to CAVS |
ABCSEXTENSION.PREPROCESSABM |
false |
User exit for the pre-process ABM should be called |
ABCSEXTENSION.POSTPROCESSABM |
false |
User exit for the post-process ABM should be called |
ABCSEXTENSION.PREPROCESSEBM |
false |
User exit for the pre-process EBM should be called |
ABCSEXTENSION.POSTPROCESSEBM |
false |
User exit for the post-process EBM should be called |
CUSTOM.TRANSFORMATIONS.EBM_TO_ABM |
false |
Use Custom transformation for EBM to ABM |
CUSTOM.TRANSFORMATIONS.ABM_TO_EBM |
false |
Use Custom transformation for ABM to EBM |
ASSIGN_ITEM_TO_CHILD_ORG |
T |
Indicates that if Components,SubstituteComponents coming in does not exist in context, whether org should be assigned from master org. |
TEMPLATE_FOR_ITEM_UPDATE_ALLOWED |
F |
During Item Update, if this config value is T, then the item template can be updated; if it is F, the item template cannot be changed |
VALIDATE_REVISED_ITEM_REVISION |
F |
If this Config value is set to T, then in MCO/SCO case, the incoming revision is either the current or a future-implemented revision |
DEFAULT_STRUCTURE_TYPE |
EBOM |
This parameter is only for the R12 case. If the incoming payload does not have any value for structure type, then the value specified for this config parameter will be supplied by default. The default value provided for this property in the AIAConfig file should be a valid structure_type in the Oracle E-Business Suite database. Use this script to retrieve a valid structure type from Oracle E-Business Suite: SELECT STRUCTURE_TYPE_NAME FROM BOM_STRUCTURE_TYPES_B, where disable_date is null or disable_date > sysdate |
CREATE_ERP_CHANGE_ORDER |
T |
If the value of this property is T, an Enterprise Resource Planning (ERP) change order is created. If the value of this property is F, an Agile PLM change order is created. If users have set up some predefined workflow set for the change order type in Oracle E-Business Suite, then that will be effective only for the Agile PLM type of change orders. |
REPLICATE_BOM_VIEW_SCOPE |
CURRENT_AND_FUTURE |
Indicates the BOM view scope for the replicate BOM case 'ALL' -- All the BOMs should be considered for replicating BOM from source org to destination org 'CURRENT' -- BOM that is effective currently should be considered 'CURRENT_AND_FUTURE' -- BOM that is effective currently and also those with future effective dates should be considered |
REPLICATE_BOM_IMPLEMENTATION_SCOPE |
ALL |
Indicates BOM implementation scope for the replicate BOM case All - implemented and unimplemented BOMs 'IMPLEMENTED' -- Implemented BOMs in source org will be considered for replicating BOM from source org to destination org 'UNIMPLEMENTED' -- Only unimplemented BOMs will be considered |
TRACE.LOG.ENABLED |
false |
Use tracelog for the flow |
STANDALONE_BOM_UPDATES_ALLOWED |
true |
The default value for this property is set to true so that by default, legacy BOM data can be updated by the integration. If only the BOMs created by this integration need to be updated (not including legacy BOMs), this property should be set to false. |
ASSIGN_DEFAULT_TEMPLATE_FROM_ICC |
F |
If this property is set to true and the user does not pass a template, then the ICC has a default template attached to it that will be applied to the item. If this property is set to false, the default template attached to the ICC will not be considered. |
UNIMPLEMENTED_BOM_UPDATES_ALLOWED |
T or F |
If this property is set to 'T' redlining of unimplemented BOM's can be done from Agile. If it is set to 'F' then only implemented BOM's can be redlined. |
ALLOW_LIFECYCLE_PHASE_SKIP |
T or F |
If this property is set to T, the life cycle phases in EBS can be skipped. if it is set to F, the life cycle phase skip is not possible. |
Table 11-31 lists the properties of the SyncItemListEbizProvABCSImpl service:
Table 11-31 SyncItemListEbizProvABCSImpl service
Property | Default Value / Settings | Description |
---|---|---|
Default.SystemID |
EBIZ_01 |
Default target system to be invoked |
Routing.ItemResponseEBSV2.SyncItemListResponse.RouteToCAVS |
false |
Controls whether SyncItemListEbizProvABCSImpl should route response messages to the Agile PLM system or to CAVS |
Routing.ItemResponseEBSV2.SyncItemListResponse.MessageProcessingInstruction.EnvironmentCode |
PRODUCTION |
Environment Code to be supplied in the Response EBM Header |
Routing.SyncItemListEbizAdapter.EBIZ_01.EndpointURI |
http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/ soa-infra/services/default/SyncItemListEbizAdapter/SyncItemListEbizAdapter_ep |
URL of Adapter Service that invokes process_item_list api on Ebiz instance This is the default value. This can be modified to point it to some other service where message should be routed like CAVS service. |
Routing.ItemResponseEBSV2.SyncItemListResponse.CAVS.EndpointURI |
http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/ AIAValidationSystemServlet/asyncresponserecipient |
URL to which response messages should be routed if Routing.ItemResponseEBSV2.SyncItemListResponse.RouteToCAVS is set to True |
ABCSExtension.PreXformEBMtoABMEBM |
false |
UserExit for PreProcess EBM |
ABCSExtension.PreInvokeSyncItemListABM |
false |
UserExit for PreProcess AM |
ABCSExtension.PostInvokeSyncItemListABM |
false |
UserExit for PostProcess ABM |
ABCSExtension.PostXformABMtoEBMEBM |
false |
UserExit for PostProcess EBM |
TRACE.LOG.ENABLED |
false |
Specifies whether logging is enabled |
DEFAULT.TEMPLATE.NAME |
No Default Value |
|
TEMPLATE_FOR_ITEM_UPDATE_ALLOWED |
F |
During item update, if this config value is T, then the item template can be updated; if it is F item, the template cannot be changed |
DEFAULT.CATEGORYSET.NAME |
NA |
|
DEFAULT.MASTER.ORG.CODE |
Default organization code |
|
ASSIGN_DEFAULT_TEMPLATE_FROM_ICC |
F |
If this property is set to true and the user does not pass a template, then if the ICC has a default template attached to it, which will be applied to the item. If this property is set to false, the default template attached to ICC will not be considered. |
Table 11-32 lists the properties of the GetConfiguratorURLEbizProvABCSImpl service:
Table 11-32 GetConfiguratorURLEbizProvABCSImpl service
Property | Default Value/Settings | Description |
---|---|---|
Default.SystemID |
EBIZ_01 |
|
ABCSEXTENSION.PREPROCESSABM |
false |
|
ABCSEXTENSION.POSTPROCESSABM |
false |
|
ABCSEXTENSION.PREPROCESSEBM |
false |
|
ABCSEXTENSION.POSTPROCESSEBM |
false |
|
CUSTOM.TRANSFORMATIONS.EBM_TO_ABM |
false |
|
CUSTOM.TRANSFORMATIONS.ABM_TO_EBM |
false |
|
Routing.ProcessInitMsgService.EBIZ_01.EndpointURI |
http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default/GetConfiguratorURLEbizAdapter/GetConfiguratorURLEbizAdapter_ep |
This is the default value. This can be modified to point it to some other service where message should be routed like CAVS service. |
Routing.BillOfMaterialsConfigurationEBS.GetConfiguratorURL.RouteToCAVS |
false |
|
Routing.BillOfMaterialsConfigurationEBS.GetConfiguratorURL.CAVS.EndpointURI |
http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/AIAValidationSystemServlet/asyncresponserecipient |
|
CONFIGURATOR_RETURN_URL |
http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/EBIBOMConfigurator/ebibomconfigreturnservlet |
|
CONFIGURATOR_APPLICATION_ID |
401 |
|
CONFIGURATOR_RESPONSIBILITY_ID |
66935 |
|
TERMINATE_MSG_BEHAVIOUR |
full |
|
TRACE.LOG.ENABLED |
false |
Table 11-33 lists the properties of the UpdateItemListEbizReqABCSImpl service:
Table 11-33 UpdateItemListEbizReqABCSImpl service
Property | Default Value/Setting | Description |
---|---|---|
Default.SystemID |
EBIZ_01 |
Used to get the default XREF target column name when TargetId is empty in the incoming EBM |
Routing.ItemEBS.UpdateItemListEBM.RouteToCAVS |
false |
ItemEBSV2 run-time target endpoint URI |
Routing.ItemEBS.UpdateItemListEBM.CAVS.EndpointURI |
http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/AIAValidationSystemServlet/asyncresponsesimulator |
getItemAttrListService endpoint URI when set to CAVS |
Routing.GetItemAttrListService.EBIZ_01.EndpointURI |
http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default/QueryItemListEbizAdapter/QueryItemListEbizAdapter_ep |
getItemAttrListService run-time target endpoint URI This is the default value. This can be modified to point it to some other service where message should be routed like CAVS service. |
Routing.ItemEBS.EBIZ_01.EndpointURI |
http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default/ItemEBSV2/ItemEBSV2_ep |
ItemEBSV2 endpoint URI when set to CAVS |
CUSTOM_TRANSFORMATIONS |
false |
Used to determine whether custom transformations should be used |
ASSET_ATTRS |
T |
When the property is set to T, all Asset attributes will be published in output EBM |
BOM_ATTRS |
T |
When the property is set to true, all BOM attributes will be published in output EBM |
COSTING_ATTRS |
T |
When the property is set to true, all Costing attributes will be published in output EBM |
GPLAN_ATTRS |
T |
When the property is set to T, all Planning attributes will be published in output EBM |
INVENTORY_ATTRS |
T |
When the property is set to T, all Inventory attributes will be published in output EBM |
INVOICE_ATTRS |
T |
When the property is set to T, all Invoice attributes will be published in output EBM |
LEAD_TIME_ATTRS |
T |
When the property is set to T, all Lead Times attributes will be published in output EBM |
MPSMRP_ATTRS |
T |
When the property is set to T, all MPS/MRP Planning attributes will be published in output EBM |
ORDER_ATTRS |
T |
When the property is set to T, all Order attributes will be published in output EBM |
PHYSICAL_ATTRS |
T |
When the property is set to T, all Physical attributes will be published in output EBM |
PROCESS_ATTRS |
T |
When the property is set to T, all Process attributes will be published in output EBM |
PURCHASING_ATTRS |
T |
When the property is set to T, all Purchasing attributes will be published in output EBM |
RECEIVING_ATTRS |
T |
When the property is set to T, all Receiving attributes will be published in output EBM |
SERVICE_ATTRS |
T |
When the property is set to T, all Service attributes will be published in output EBM |
WEB_OPTION_ATTRS |
T |
When the property is set to T, all Web Option attributes will be published in output EBM |
WIP_ATTRS |
T |
When the property is set to T, all Work In progress attributes will be published in output EBM |
ITEM_ATTRS |
T |
When the property is set to T, all Item attributes will be published in output EBM |
DEFAULT_ITEM_COST_GROUP |
If this value is given, then the cost will be derived based on this value Note: Either DEFAULT_ITEM_COST_TYPE or DEFAULT_ITEM_COST_GROUP should be set but not both |
|
DEFAULT_ITEM_COST_TYPE |
1 |
If this value is given, the cost will be derived based on this value Note: Either DEFAULT_ITEM_COST_TYPE or DEFAULT_ITEM_COST_GROUP should be set but not both |
TRACE.LOG.ENABLED |
false |
Use tracelog for the flow |
ABCSEXTENSION.PREPROCESSABM |
false |
User exit for the pre-process ABM should be called |
ABCSEXTENSION.POSTPROCESSABM |
false |
User exit for the post-process ABM should be called |
ABCSEXTENSION.PREPROCESSEBM |
false |
User exit for the pre-process EBM should be called |
ABCSEXTENSION.POSTPROCESSEBM |
false |
User exit for the post-process EBM should be called |
Table 11-34 lists the properties of the UpdateEngineeringChangeOrderEbizReqABCSImpl service:
Table 11-34 UpdateEngineeringChangeOrderEbizReqABCSImpl service
Property | Default Value/Setting | Description |
---|---|---|
Default.SystemID |
EBIZ_01 |
Used to get the default XREF target column name when TargetId is missing in incoming EBM |
Routing.GetUpdateEngineeringChangeOrderListService.EBIZ_01.EndpointURI |
http://${fp.server.soaserverhostname}:${fp.server.soaserverport}//soa-infra/services/default/QueryEngineeringChangeOrderListEbizAdapter/QueryEngineeringChangeOrderListEbizAdapter_ep |
getUpdateEngineeringChangeOrderListService run-time target endpoint URI This is the default value. This can be modified to point it to some other service where message should be routed like CAVS service. |
Routing.ECOEngineeringChangeOrderEBS.UpdateEngineeringChangeOrderList.RouteToCAVS |
false |
EngineeringChangeOrderEBS run-time target endpoint URI |
Routing.ECOEngineeringChangeOrderEBS.UpdateEngineeringChangeOrderList.CAVS.EndpointURI |
http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/AIAValidationSystemServlet/asyncresponsesimulator |
getUpdateEngineeringChangeOrderListService endpoint URI when set to CAVS |
Routing.ECOEngineeringChangeOrderEBS.EBIZ_01.EndpointURI |
http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default/EngineeringChangeOrderEBS/EngineeringChangeOrderEBS_ep |
EngineeringChangeOrderEBS endpoint URI when set to CAVS |
CUSTOM_TRANSFORMATIONS |
false |
Used to determine whether custom transformations should be used |
INCLUDE_REVISED_ITEMS |
T |
Having a single Boolean Char value (T/F), this property is passed to the Pl/Sql API based on the value of the property Revised Item details are supplied in the output ABM |
INCLUDE_COMPONENT_ITEMS |
T |
Having with a Boolean Char value (T/F), this property is passed to the Pl/Sql Application Programming Interface (API) based on the value of the property Component. Item details are supplied in the output ABM |
INCLUDE_SUBSTITUTE_COMPONENTS |
T |
Having a single Boolean Char value (T/F), this property is passed to the Pl/Sql API based on the value of the property Substitute item details are supplied in the output ABM |
INCLUDE_REFERENCE_DESIGNATORS |
T |
Having a single Boolean Char value (T/F), this property is passed to the Pl/Sql API based on the value of the property Reference Designators of the Component item details are supplied in the output ABM |
ABCSEXTENSION.PREPROCESSABM |
false |
User exit for the pre-process ABM should be called |
ABCSEXTENSION.POSTPROCESSABM |
false |
User exit for the post-process ABM should be called |
ABCSEXTENSION.PREPROCESSEBM |
false |
User exit for the pre-process EBM should be called |
ABCSEXTENSION.POSTPROCESSEBM |
false |
User exit for the post-process EBM should be called |
TRACE.LOG.ENABLED |
false |
Use tracelog for the flow |
Table 11-35 lists the properties of the UpdateItemBalanceListEbizReqABCSImpl service:
Table 11-35 UpdateItemBalanceListEbizReqABCSImpl service
Property | Value/Setting | Description |
---|---|---|
Default.SystemID |
EBIZ_01 |
Used to get the default XREF target column name when TargetId is missing in incoming EBM |
Routing.ItemBalanceEBS.UpdateItemBalanceList.RouteToCAVS |
false |
Use CAVS for ItemBalanceEBS |
ItemBalanceService.EBIZ_01.Default.Target.EndpointURI |
http://${fp.server.soaserverhostname}:${fp.server.soaserverport}//soa-infra/services/default/QueryItemBalanceListEbizAdapter/QueryItemBalanceListEbizAdapter_ep |
ItemBalanceService run-time target endpoint URI This is the default value. This can be modified to point it to some other service where message should be routed like CAVS service. |
Routing.ItemBalanceEBS.UpdateItemBalanceList.CAVS.EndpointURI |
http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/AIAValidationSystemServlet/asyncresponsesimulator |
ItemBalanceEBS endpoint URI when set to CAVS |
ItemBalanceEBS.EBIZ_01.Default.Target.EndpointURI |
http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default/ItemBalanceEBS/ItemBalanceEBS_ep |
ItemBalanceEBS run-time target endpoint URI |
CUSTOM_TRANSFORMATIONS |
false |
Used to determine whether custom transformations should be used |
TRACE.LOG.ENABLED |
false |
Use tracelog for the flow |
ABCSEXTENSION.PREPROCESSABM |
false |
User exit for the pre-process ABM should be called |
ABCSEXTENSION.POSTPROCESSABM |
false |
User exit for the post-process ABM should be called |
ABCSEXTENSION.PREPROCESSEBM |
false |
User exit for the pre-process EBM should be called |
ABCSEXTENSION.POSTPROCESSEBM |
false |
User exit for the post-process EBM should be called |
Table 11-36 lists the properties of the SyncBillOfMaterialsConfigurationListEbizReqABCSImpl service:
Table 11-36 SyncBillOfMaterialsConfigurationListEbizReqABCSImpl service
Property | Default Value/Setting |
---|---|
Default.SystemID |
EBIZ_01 |
ABCSEXTENSION.PREPPROCESSABM |
false |
ABCSEXTENSION.PREPROCESSEBM |
false |
CUSTOM.TRANSFORMATIONS.ABM_TO_EBM |
false |
Routing.BillOfMaterialsConfigurationEBS.SyncBillOfMaterialsConfigurationList.RouteToCAVS |
false |
Routing.BillOfMaterialsConfigurationEBS.SyncBillOfMaterialsConfigurationList.CAVSEndpointURI |
http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/AIAValidationSystemServlet/asyncresponserecipient |
GenerateItemNumberService service:
Table 11-37 GenerateItemNumberService
Property | Value/Setting | Description |
---|---|---|
Routing.GenerateItemNumberService.EBIZ_01.EndpointURI |
http://${ebiz.host}:${ebiz.port}/webservices/AppsWSProvider/oracle/apps/inv/ebi/item/GenerateItemNumberService |
This is the default value. This can be modified to point it to some other service where message should be routed like CAVS service. |
National language support (NLS) has been implemented in the pre-built integration for Agile PLM to Oracle E-Business Suite integration.
In all the Oracle E-business Suite initiated flows, the language code is managed from the concurrent program.
Configure the profile option called EBS Integration Language Codes with the language for AIA Integration, for example, US.
Note:
In AIA, only one language is supported in the Oracle E-Business Suite Integration profile option for reverse flow. This is because in Agile PLM, the filtering and routing is carried out based on the language code in the EBS layer. Agile PLM does not send any response to Oracle E-Business Suite Integration Requester ABCS for the language that is not the same as the one configured on the Agile PLM side.
In AIA Release 2.3 PIP, the value of the Apps User is set from the Configuration file. However, from AIA Release 2.4 PIP onwards, a new DVM EBIZ_AGILE_APPS_USER, with the columns LANG_CODE and USER_NAME, is used.
The value of the Apps User is set based on the language code returned by the concurrent program using DVM EBIZ_AGILE_APPS_USER. The DVM has two columns LANG_CODE and USER_NAME. If DVM does not have match, the default user is picked from AIA Configuration file, using the module level configuration property (called USER) for Oracle E-Business Suite. The language code of Oracle E-Business Suite is converted to common value in the EBM using the DVM LANGUAGE_CODE
Note:
Ensure that the values are configured for the DVM LANGUAGE_CODE and EBIZ_AGILE_APPS_USER before the flows are triggered.
For the Update Engineering change order, you can use two ways to invoke the Requester ABCS. One is through the concurrent program and the other is through the inbound adapter Events, called the Business Events. A change in ECO status returns the SID, the Change ID and Language Code as input to the Requester ABCS. The Language Code has a default value as US. If you want to update this for different Languages, you must run the Publish Engineering Change Order concurrent program with appropriate language code.
The language code for Agile requester services is picked up from AIA configuration file using Agile Module level property "LANG_LOCALE". This language code value is then used for setting up the APPS user in Ebiz Providers through EBIZ_AGILE_APPS_USER DVM. If the language code does not exist in this DVM, then default user is set from the AIA configuration file using the Ebiz Module level configuration property "USER".
In Agile PLM Java Client, for each subscriber of MCO, SCO, and ECO, navigate to the subscriber details page and set the language.
Change the language preference of all users who are creating change orders and items, including integration users, to Japanese.
Note:
For easy comprehension, we are using Japanese as a sample language.
Editing Transformations
Edit the following eXtensible Stylesheet Language (XSL) file and replace the hard-coded string Preliminary to the Japanese equivalent coming from the Agile PLM list values.
<AIA_HOME>/services/core/Agile/UtilityServices/QueueProcessorServiceImpl/Agile Data_to_AgileCreateEngineeringChangeOrderListABM_Impl.xsl
Edit the following XSL file and replace the following values:
<AIA_HOME>/services/core/Agile/RequesterABCS/ProcessEngineeringChangeOrderAgileReqABCS/AgileCreateEngineeringChangeOrderListABM_to_CreateEngineeringChangeOrderListEBM.xsl
Replace the hard-coded string Preliminary to the Japanese equivalent coming from the Agile PLM list values.
Edit the following XSL file and replace hard-coded strings Errored with the Japanese equivalent:
<AIA_HOME>/services/core/Agile/RequesterABCS/ProcessEngineeringChangeOrderAgileReqABCS/AgileCreateEngineeringChangeOrderListABM_to_AgileUpdateEngineeringChangeOrderListABM_Impl.xsl
Edit the following XSL file and replace the following values:
<AIA_HOME>/services/core/Agile/RequesterABCS/ProcessEngineeringChangeOrderAgileReqABCS/UpdateEngineeringChangeOrderListEBM_to_AgileUpdateEngineeringChangeOrderListABM_Impl.xsl
Replace the hard-coded string Transferred with its Japanese equivalent.
Replace the hard-coded string Errored with its Japanese equivalent.
Note:
Use a UTF -8 based editor such as JEdit to perform these changes. Choose UTF-8 as the character set while loading the file to edit. Set FTP transfer mode to Binary while uploading these files to AIA components.
Editing AIA Configurations
Edit the property LANG_LOCALE under module Agile to Japanese. Its language value is available under the column COMMON in the LANGUAGE_CODE DVM at this path:
AIA_HOME>/aia_instances/$INSTANCE_NAME/AIAMetaData/config
For more information about requirements for working with AIAConfigurationProperties.xml, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1, Building AIA Integration Flow, How to Set Up AIA Workstation.
Setting Up DVMs
Set up the required DVMs using SOA Composer. Enter the Japanese language values under the Agile PLM column AGILE_01 in the following DVMs:
ITEM_PRIMARYCLASSIFICATIONCODE
ITEM_STATUS_CODE
ITEM_UOM_CODE
ECO_REASON_CODE
ECO_TYPECODE
ECO_CLASSIFICATION_CODE
ECO_STATUS_CODE
Log in to Oracle E-Business Suite.
Navigate to User Preferences.
Change the current session language and default language to the language that is configured in Agile PLM.
Navigate to System Administrator Responsibility in Oracle E-Business Suite and navigate to the following path:
System Administrator > Profile Options > System
Query for profile option EBS Integration Language Codes.
Set the language code to the corresponding Agile PLM language.
Based on the roles defined for the services, email notifications are sent if an error occurs. The roles can be assigned at various levels in a hierarchy (service, process, and domain) so that when a service ends due to error, the Error Handling Framework uses the role value to derive the users who have to be notified. The Error Handling Framework then notifies the users through their preferred notification method, puts the error in the user's Oracle Worklist, and records the error in the error log.
Role: Actor role associated with the error notification. Actor roles receive notifications for and are assigned to error scenarios occurring in Oracle AIA integration flows. The task is editable in the Error Console and is meant to be worked on and resolved by the actor assigned to the task.
FYI Role: FYI role associated with the error notification. This role receives for-your-information (FYI) notifications for error scenarios occurring in Oracle AIA integration flows. An example of an FYI role is a customer service representative. The task is displayed in read-only view in the Error Console.
For more information about the errors caused by the applications Agile PLM and Oracle E-Business Suite, see the documentation for the respective product.
For more information about AIA error handling, see Oracle Fusion Middleware Infrastructure Components and Utilities User's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1, "Setting Up Error Handling."
Any failure in the processing of a change order is captured by Queue Manager. This Errored process can be identified in Queue Monitor, symbolized by.
To see the reason for the error, click the link Errored in the Process Status column.
This Error Message comprises two parts:
Error Text - This is the description of the error source, which can be from any of the participating ABCS services that faulted.
Details - The error details consist of:
Service Name: The name of the service where an instance failed to run
Instance ID: The identification number of the instance that failed
Multiple faults generated by the service are captured and displayed in this UI. In addition to this, any failures in the flows are captured in the AIA Error Logs. These can be seen from the Enterprise Manager Console logs section.
In an event in which a certain service is down and the error is not related to the payload, users can resubmit the change in the Queue Manager UI.
This section provides an overview of the error-handling and recovery options available for initial load of items and discusses:
Transaction Handling
Recovery Options
Errors raised either by an item extract process or an item load process due to a system error are logged by the AIAAsyncErrorHandling process as a failure and no error files are created. You need to restart the process when the system is functional. The BPEL process is marked as a failure in the Enterprise Manager (EM) console.
While loading item data into Agile PLM, if an error occurs when one or more items in the input file are added or updated, then an error file is created which contains only erroneous item rows. The process continues with the remaining correct items in the file and eventually the processed file is archived. The BPEL process is marked as successful in the EM console.
The XML file with erroneous item rows must be corrected, and resubmitted, depending on the kind of error.
If the items are successfully added in the Agile PLM but subsequent cross-references updates fails, then the AIAAsyncErrorHandling process is invoked and no error files are created. The item load processed file is not archived and is marked as a failure in the EM console.
The item extract process is a read-only process and therefore no transactions are associated with it. For item load process, the transactions associated with BPEL and Agile web service are different. For example, the Agile web service uses SOAP/ HTTP and acts as a communication interface for loading items into Agile PLM. Therefore, the item extract process does not participate in the transaction of the BPEL process.
The item extract process can be run multiple times even after a failure as it just overwrites the current file if it exists.
The item load process may fail under different scenarios and the error recovery options for these failures differ accordingly. The following table lists different error recovery options made available for different types of item load failures.
Type of Item Load Failures | Recovery Options |
---|---|
System error |
Resubmission of the processing file is the recovery option. |
Cross-reference update failure when you update item details. |
Retrieve the processing file from the archiving folder and resubmit it for processing |
Synchronization failure. When you update item details, if the Agile web service fails to synchronize the item data with Agile PLM, then erroneous item rows are written to a separate file in the failed message folder. |
You must select the error file, correct the item data and resubmit for recovery. |
For more information about using XSL Mapping Analyzer (XMAN), see Oracle Fusion Middleware Infrastructure Components and Utilities User's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1, Using the XSL Mapping Analyzer.
For more information about how services are mapped, see the My Oracle Support document: EBO Implementation Maps (EIMs) 1095494.1.
OOTB ECO will be released from Agile in Released status and it must be created in Scheduled status, so that ECO_STATUS_CODE DVM Released status of Agile is mapped to the SCHEDULED value of the COMMON Column.
To create a change order in EBS in Released status:
Apply EBS patch 12895719:R12.ENG.C on EBS host.
In Fusion Middleware, update the COMMON and AGILE_01 columns of the ECO_STATUS_CODE DVM.
Table 11-39 shows the old settings.
Table 11-40 shows the new settings.
Save the DVM changes.
After completing these steps, you can create change orders in Released status in EBS using the Agile Product Lifecycle Management (PLM) integration for Oracle E-Business Suite.