7 Configuring Design to Release: Agile PLM - JDE E1

This chapter discusses:

Prerequisites
Setting up participating applications
Setting up batch processing information
SQL Script for Loading Cross-Reference Records
Identifying cross-references
Populating cross-references
Describing Domain Value Maps (DVMs)
Setting configuration properties
Handling error
Viewing EBO Implementation Maps (EIMs)

7.1 Prerequisites

This section discusses the prerequisites for the following integration flows:

Initial load of items and Bill of Materials (BOM)
Product design Changes
ECO implementation
Item attributes and cost updates
Item balance updates

7.1.1 Prerequisites for Initial Load of Items and BOM

Before running an initial load, complete the following actions:

Set up versions of each extract program in JD Edwards EnterpriseOne.
Set up batch processing information and invoke utilities for an initial load.
Create a new workflow for initial load change orders and set privileges.

7.1.2 Prerequisites for Product Design Changes

Before running the Create ECO flow, complete the following actions:

Set up user-defined codes (UDCs).
Set up JD Edwards EnterpriseOne web services.
Set up Oracle Web Services Manager (OWSM) security information.

7.1.3 Prerequisites for ECO Implementation

Before running the Update ECO flow, complete the following steps:

Set up versions of each extract program in JD Edwards EnterpriseOne.
Set up batch processing information.

7.1.4 Prerequisites for Item Attributes and Cost Updates

Before running the update item flow, you must complete these steps:

Set up versions of each extract program in JD Edwards EnterpriseOne.
Set up the batch processing information.

7.1.5 Prerequisites for Item Balance Updates

Before running the update item balance flow, complete the following actions:

Set up versions of each extract program in JD Edwards EnterpriseOne.
Set up batch processing information.

7.2 Setting Up Participating Applications

Before integration, you must set up Agile Product Lifecycle Management (PLM), JD Edwards EnterpriseOne, Oracle Web Services Manager Security Information (OWSM), and Application Integration Architecture (AIA).

7.2.1 Setting Up Agile Content Services

The following set ups are required using the Agile PLM Java client:

Create new destinations
Create new events for Engineering Change Order (ECO) and Site Change Order (SCO)
Define filters
Create new subscribers for ECO and SCO
Set ECO and SCO privileges
Set up Agile item quantity attributes
Create a new ECO workflow for initial load change orders
Set ECO workflow privileges
Set up Change_Status table for workflow
Setup Agile notifications

7.2.1.1 Create New Destinations

To create a new JMS destination:

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.
Restart the complete SOA server using the 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 Agile PLM is deployed on the Weblogic server (WLS), no need to copy the wlthint3client.jar file, it should work fine as it is.

For more information on how to restart Agile PLM deployed on the Weblogic server (WLS), refer to the Agile Product Lifecycle Management Installing Agile PLM on WebLogic Server Guide.

On the Admin tab, navigate to System Settings > Agile Content Service > Destinations.
Select Protocol JMS.

Enter or set the essential values as illustrated in Table 7-1:

Table 7-1 Parameters to Define Default Filters

Field	Value/Setting
View Tabs	Add Sites, Title Block, Page Two, Page Three, BOM, Manufacturers
BOM Options	Tabs and Items
BOM Levels	Select the All Levels check box
AML Options	Tabs and Manufacturer Parts
Attachment Options	Tab only

Click Test to validate.

7.2.1.2 Create New Events for ECO and SCO

To create new events for ECO and SCO:

On the Admin tab, navigate to System Settings > Agile Content Service > Events.

Set the essential values as illustrated in Table 7-2:

Table 7-2 Values to create new events for ECO and SCO

Field	Value/Setting
	For ECO	For SCO
Name	Define your own
Event Type	Workflow
Workflow	Default Change Order	Default Site Change Orders
Workflow Status	Released

7.2.1.3 Define Filters

To define filters:

On the Admin tab, navigate to System Settings > Agile Content Service > Filters.

Modify the default item filter to set the parameters as illustrated in Table 7-3:

Table 7-3 Parameters to Define Default Filters

Field	Value/Setting
View Tabs	Add Sites, Title Block, Page Two, Page Three, BOM, Manufacturers
BOM Options	Tabs and Items
BOM Levels	Select the All Levels check box
AML Options	Tabs and Manufacturer Parts
Attachment Options	Tab only

Modify the filters to set the given fields as illustrated in Table 7-4:

Table 7-4 Parameters to modify fields

Field	Value/Setting
	For ECO	For SCO
Filter	Default Change Order Filter	Default Site Change Order Filter
Affected Items Options	Tab and Items	Tabs and Items
Redline Changes only	No	No

7.2.1.4 Create New Subscribers for ECO and SCO

To create new subscribers for ECO and SCO:

On the Admin tab, navigate to System Settings > Agile Content Service > Subscribers

Create new subscribers, one each for ECO and SCO, and set the parameters as illustrated in Table 7-5:

Table 7-5 Values for Creating New Subscribers

Field	Value/Setting
	For ECO	For SCO
Name	Define your own ATO Default ATOs
Subclass
Workflow
Criteria	All Site Change Orders	All Change Orders
AutoNumber	ATO Number	ATO Number
Event	Select the Name of the Event that you created in step 2 for ECO	Select the Name of the Event that you created in step 2 for SCO

Enter or set the subscriber details for each ECO and SCO by adding a new row.

Use the information listed in Table 7-6 for creating a new row:

Table 7-6 Values for Creating a New Row

Field	Value/Setting
	For ECO	For SCO
Filter	Default Change Order Filter	Default Site Change Order Filter
	Default Item Filter	Default Item Filter
Roles	All
Format	aXML
Language	English
Site	All

Enable all the newly created subscribers

7.2.1.5 Set ECO and SCO Privileges

To set ECO and SCO privileges:

On the Admin tab, navigate to User Settings > Privileges > Modify
Create new Modify Privileges for ECO and SCO
Set privilege to Modify
Select the criteria that correspond to each ECO and SCO
Select all the attributes, including the invisible and disabled attributes in the Applied to field and save them
On the Where Used tab, add roles to all the privileges you created

The default role is Admin user.

Note:

The user should have privileges to modify the Released items and the Released changes.

7.2.1.6 Set up Agile Item Quantity Attributes

To set up Agile item quantity attributes:

On the Admin tab, navigate to Data Settings > Classes
For both Parts and Document classes, enable the flex fields on Page2, Page3, or Site tab according to the MultiSite_Enabled property value in AIAConfigProperties.xml for Agile Product Lifecycle Management (PLM)
The field names, listed in Step 2, in Agile PLM reflect the following fields from JD Edwards EnterpriseOne:
- Unit Cost
- Available Quantity
- On Hand Quantity
- Reserved Quantity
  
  The flex fields should be the same as those entered as values for the following properties:
- Item.UnitCostAttribute
- Item.AvailableQuantityAttribute
- Item.OnHandQuantityAttribute
- Item.ReservedQuantityAttribute
Select Visible for the fields you created.

Note:

Ensure that these attributes have Read and Modify privileges.
Click OK.

7.2.1.7 Create a New Workflow for Initial Load Change Orders

To create a new workflow for initial load change orders:

On the Admin tab, navigate to Workflow Settings > Workflows

Create new workflow for the initial load change orders and set the values as illustrated in Table 7-7:

Table 7-7 Values for creating new workflow

Field	Value/Setting
Name	Define your own
Workflow Criteria matching Type	All
Status Criteria Matching Type	Same
Object Type	Changes
Matching Criteria	All Change Orders

Go to the Status tab and add two new workflow statuses and set the values as illustrated in Table 7-8 and Table 7-9:

Table 7-8 Values for workflow status 1

Field Value/Setting

Name

Define your own

Status Type

Pending

Status Stamp Color

Define your own

Table 7-9 Values for workflow status 2

Field Value/Setting

Name

Define your own

Status Type

Released

Status Stamp Color

Define your own
Add workflow criteria for each of the statuses created earlier and set the select criteria as All Change Orders
Enable the newly created workflow

7.2.1.8 Set ECO Workflow Privileges

To set ECO workflow privileges:

On the Admin tab, navigate to User Settings > Privileges > Change Status

Create new change status privileges for initial load change orders workflow and set the values as illustrated in Table 7-10:

Table 7-10 Values for creating new workflow

Field	Value/Setting
Name	Define your own
Description	Define your own
Enabled	Yes
Privilege	Change Status
Criteria	All Change Orders
Workflow	New workflow created in Step 9
Status - From	Status defined in Step 9 with Status type of Pending
Status - To	Status defined in Step 9 with Status type of Released

On the Where Used tab, add roles to all the privileges you created.

The default role is Admin user.

7.2.1.9 Setup Change_Status Table for Workflow

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 is 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 7-11 illustrates how a partially configured table looks:

Table 7-11 A partially configured table

EVENT	OUTCOME	SUBCLASS	WORKFLOW	NEXT_STAUS
New Part Request	Success	ECR	Default Change Requests	Completed
New Part Request	Failure	ECR	Default Change Requests	Pending
Pre-release Audit	Failure	ECO	Default Change Orders	Submitted
Pre-release Audit	Failure	ECO	Fast-track Change Orders	Pending
Change Implementation	Success	ECO	Default Change Orders	Implemented
Change Implementation	Success	ECO	Fast-track Change Orders	Implemented

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).

In a new installation, this table is empty. The integration administrator needs to add rows in this table if the change status process needs to be supported for any of the given processes.

The value of the EVENT column must be limited to the values corresponding to the processes supported: New Part Request, Pre-release Audit, and Change Implementation. The change implementation process can also be associated with a status update back to a flexfield on the change order.
The value of the OUTCOME column must be limited to Success and Failure.
The value of the SUBCLASS column must be limited to the set of subclasses of the Change Requests Class, Change Orders Class, Manufacturing Orders Class, and Site Change Orders Class.
The value of the WORKFLOW column must be limited to the set of workflows for the selected subclass. For example, if you are using the default change order workflow for ECO, then enter the default change order in this column. These values can be picked up from the Agile PLM Java client.
In the NEXT_STATUS column, enter the status of the workflow to move to when the conditions are met. For example, when a change is implemented (identified by event; this is a key, so do not change it) and the OUTCOME is SUCCESS (identified by outcome; this is checked while changing status here) and the WORKFLOW chosen is Default Change Orders, the setup requesting the change to be moved to the implemented status (NEXT_STATUS).

7.2.1.10 Set Up Agile Notifications

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 must be notified on failure of ACS transfer.
Save the changes.

7.2.2 Setting Up JD Edwards EnterpriseOne

Before you can use the Design to Release Agile PLM - JD Edwards EnterpriseOne integration; you must set up several applications in JD Edwards EnterpriseOne that the integration uses. The integration processes and flows supported in this integration require that JD Edwards EnterpriseOne is set up correctly before any initial load or updates occur in Agile PLM.

This section discusses:

Setting up batch programs
Setting up integration user-defined codes (UDCs)
Setting up JD Edwards EnterpriseOne web services
Setting up business services (BSSVs)
Configuration parameters for creating Engineering Change order (ECO) flow

7.2.2.1 Setting Up Batch Programs

Setting up batch programs includes:

Setting up the item initial load extract to XML program (R4101D3)
Setting up the Bill of Material (BOM) initial load extract to XML program (R3002D)
Setting up ECO batch extract programs
Setting up the ECO extract to XML program (R3013D)
Setting up item list batch extract programs
Setting up the item list extract to XML program (R4102D)
Setting up item balance batch extract programs
Setting up the item balance extract to XML program (R41021D)

For more information, see JD Edwards EnterpriseOne Tools Development Tools: Batch Versions Guide.

Setting Up Item Initial Load Extract to XML Program (R4101D3)

Use this program to extract the initial load item data from JD Edwards EnterpriseOne to Agile PLM. Before running this program, you must set the processing options to ensure that data is extracted correctly.

On the Processing Options tab, set up the path where the xml file is written.

Use this processing option to specify the file location that the system uses for storing the resulting XML file. The name of the resulting XML file is in the format of R4101D3_MMDDYY_hhmmss.xml. The file name is appended to the value entered in this processing option to determine the fully qualified path and name. All directories specified in the path should exist. Also, ensure that the value ends with '\' or '/' as required by the operating system. If you leave this processing option blank, the system writes the resulting XML file to the directory where this report is running.

Setting Up BOM Initial Load Extract to XML Program (R3002D)

Use this program to extract initial load BOM data from JD Edwards EnterpriseOne to Agile PLM. Before running this program, you must set the processing options to ensure that data is extracted correctly.

This program has two default versions:

XJDE0001 - BOM Initial Load Extract to XML

We recommend this version for Agile PLM with Multi-Site OFF.

Figure 7-1 illustrates an example of the recommended data selection for the Universal Batch Engine (UBE) program:

Figure 7-1 Example of data selection for the batch program
XJDE0002 - BOM Initial Load - Exclude Non-Stock Components

We recommend this version for Agile PLM 39 with Multi-Site ON.

Figure 7-2 illustrates the recommended data selection:

Figure 7-2 Example of data selection

Set the following processing options on the Processing Options tab:

Path where the XML file is written

Use this processing option to specify the file location that the system uses for storing the resulting XML file.

The name of the resulting XML file is in the format of R3002D_MMDDYY_hhmmss.xml.

The system appends the file name to the value entered in this processing option to determine the fully qualified path and name. All directories specified in the path should already exist. If you leave this processing option blank, the system writes the resulting XML file to the directory where this report is running.
As of Date

This date is used for effectivity checking. Enter a specific date to display documents (orders, BOMs, and routings, as applicable) that are effective on or after that date. The current system date is the default, but you can enter any future or past date.
Selection for Components

Use this processing option to specify if the system selects all the components associated with a selected BOM. If you leave this processing option blank, the system only selects components with the same branch/plant as the parent. The system writes skipped components details to the report output. The system selects all associated components for the BOMs selected if set to the value 1.
Extract Parent Item Revision Level

Use this processing option to indicate whether the system extracts the BOM parent item revision level from the item master (F4101). If you leave this processing option blank, the system does not extract the parent item revision level. The system extracts the parent item revision level if the value is set to 1.

Setting Up ECO Batch Extract Programs

The ECO batch extract program extracts ECO changes from JD Edwards EnterpriseOne to Agile PLM. Before the ECOs are processed using batch programs, you must configure versions for each of them.

The Update ECO program includes the Update ECO Extract to XML program (R3013D).

For more information, see JD Edwards EnterpriseOne Tools Development Tools: Batch Versions Guide.

Setting Up ECO Extract to XML Program (R3013D)

Before running this program, set the processing options to ensure that data is extracted correctly.

This program has one default version: XJDE0001 - ECO Extract to XML

ECO Extract R3013D has no default data selection.

Set the following processing options on the Processing Options tab:

Path where the XML File is written

Use this processing option to specify the file location that the system uses for storing the resulting XML file. The name of the resulting XML file is in the format of R3013D_MMDDYY_hhmmss.xml. All directories specified in the path should already exist. If you leave this processing option blank, the system writes the resulting XML file to the default JD Edwards EnterpriseOne system directory.
As of Date

This date is used for effectivity checking. Enter a specific date to extract the updated ECOs from JD Edwards EnterpriseOne that are effective on or after that date. If you leave this processing option blank, the system uses the integration time stamp date.
Integration Code

Use this processing option to specify the integration code, which is a mandatory field in UDC (00/IE). If you leave this processing option blank, the system will not process any data or write the XML file.

Setting Up Item List Batch Extract Programs

The item list batch extract program extracts item attribute and cost changes from JD Edwards EnterpriseOne to Agile PLM.

Before the Item List can be processed using batch programs, you should configure versions for each program.

Item list programs include the Item List Extract to XML program (R4102D).

For more information, see JD Edwards EnterpriseOne Tools Development Tools: Batch Versions Guide.

Setting Up Item List Extract to XML Program (R4102D)

Use this program to extract item list data from JD Edwards EnterpriseOne to Agile PLM. Before running this program, set the processing options to ensure that data is extracted correctly.

This program has one default version: XJDE0001 - Item List Extract to XML.

This program has no default data selection.

Set the following processing options on the Processing Options tab:

Path where the XML File is written

Use this processing option to specify the file location that the system uses for storing the resulting XML file. The name of the resulting XML file is in the format of R4102D_MMDDYY_hhmmss.xml. All directories specified in the path should already exist. If you leave this processing option blank, the system will write the resulting XML file to the default JD Edwards EnterpriseOne system directory.
As of Date

This date is used for effectivity checking. Enter a specific date to extract the updated ECOs from JD Edwards EnterpriseOne that are effective on or after that date. If you leave this processing option blank, the system will use the integration time stamp date.
Integration Code

Use this processing option to specify the integration code, which is a mandatory field in UDC (00/IE). If you leave this processing option blank, the system will not process any data and it will not write an XML file.
Ledger Type

Use this processing option to specify the costing method. If you leave this processing option blank, the system will use the cost method from branch/plant constants. If you do not set the cost method in branch/plant constants, then the system will use the default value of data dictionary item CSMT.

Setting Up Item Balance Batch Extract Programs

The item balance list batch extract program extracts item availability changes from JD Edwards EnterpriseOne to Agile PLM.

Before the item balance can be processed using batch programs, you should configure versions for each program.

Item balance programs include the Item Balance Extract to XML program (R41021D).

For more information, see JD Edwards EnterpriseOne Tools Development Tools: Batch Versions Guide.

Setting Up Item Balance Extract to XML Program (R41021D)

Use this program to extract item balance data from JD Edwards EnterpriseOne to Agile PLM. Before running this program, set the processing options to ensure that data is extracted correctly.

This program has a default version:

XJDE0001 - Item Balance Extract to XML

Item Balance Extract R41021D has no default data selection.

Set the following processing options on the Processing Options tab:

Path where the XML File is written

Use this processing option to specify the file location that the system uses for storing the resulting XML file. The name of the resulting XML file is in the format of R41021D_MMDDYY_hhmmss.xml. All directories specified in the path should already exist. If you leave this processing option blank, the system will write the resulting XML file to the default JD Edwards EnterpriseOne system directory.
As of Date

This date is used for effectivity checking. Enter a specific date to extract the updated ECOs from JD Edwards EnterpriseOne that are effective on or after that date. If you leave this processing option blank, the system will use the integration time stamp date.
Integration Code

Use this processing option to specify the integration code, which is a mandatory field in UDC (00/IE). If you leave this processing option blank, the system will not process any data and it will not write the XML file.

7.2.2.2 Setting Up UDCs

You set up UDCs to store the information about the types of integration codes used.

UDC: 00/IE - Integration Code

To set up a UDC, complete the following steps:

Navigate to the Work With User Defined Codes page using the Fast Path. See Figure 7-3
Figure 7-3 Work with User Defined Code Page
Enter Product Code as 00 and User Defined Codes as IE. See Figure 7-4

Figure 7-4 User Defined Codes
Click Add.

Enter the code and description as AGILEJDE and Agile to JDE Integration, respectively. See Figure 7-5

Figure 7-5 Entering Code for UDC
Click OK to save the UDC values. See Figure 7-6

Figure 7-6 Saving the UDC values

7.2.2.3 Setting Up JD Edwards EnterpriseOne Web Services

You use these JD Edwards EnterpriseOne web services, also called business services, in the Design to Release integration:

EngineeringChangeOrderManager (JP300000)
IntegrationTimeStampManager (JP300010)
EngineeringChangeOrdersProcessor (J3000010)
EngineeringChangeOrderPartsListProcessor (J3000020)
ProcessIntegrationTimeStamp (J3000030)
InventoryItemsProcessor (J4100020)
nventoryItemBranchProcessor (J4100030)

For more information about JD Edwards EnterpriseOne business services, see JD Edwards EnterpriseOne Business Services Reference Guide.

Note:

JD Edwards EnterpriseOne business services must be built with the option for migration from 10g to 11g turned on.

For more information about the migration option, see JD Edwards EnterpriseOne Release 8.98.3 Building Business Services Packages with Migration (My Oracle Support Document ID 1233332.1).

EngineeringChangeOrderManager (JP300000)

The EngineeringChangeOrderManager Published Business Service (PBSSV) manages the processing of the following:

Table 7-12 lists and describes the web service operations:

Table 7-12 Web service operations

Operation	Description
EngineeringChangeOrdersProcessor (J3000010)	Use this operation to call other processors internally to add records into Item, Item Branch, and ECO files.
EngineeringChangeOrderPartsListProcessor (J3000020)	Use this operation to add ECOs in the ECO file.
InventoryItemsProcessor (J4100020)	Use this operation to add or modify item records.
InventoryItemBranchProcessor (J4100030)	Use this operation to add or modify item branch records.

For more information about the web services, see JD Edwards EnterpriseOne Business Services Reference Guide.

IntegrationTimeStampManager (JP300010)

The IntegrationTimeStampManager PBSSV manages the processing of the following web service operation:

Table 7-13 lists and describes the web service operations:

Table 7-13 Web service operations

Operation	Description
ProcessIntegrationTimeStamp (J3000030)	Use this operation to add and modify the Integration Time Stamp table.

For more information, see JD Edwards EnterpriseOne Business Services Reference Guide, "IntegrationTimeStampManager."

EngineeringChangeOrdersProcessor (J3000010)

The EngineeringChangeOrderManager PBSSV calls the EngineeringChangeOrdersProcessor BSSV from the provider when a user creates an ECO. For the Design to Release integration, the external system is Agile PLM. The user creates an ECO in Agile PLM and releases the same to JD Edwards EnterpriseOne. This processor calls the create ECO (B3004100) business function to add a header record in F4801. This action generates an ECO number, which the system uses to create a BOM in JD Edwards EnterpriseOne.

The EngineeringChangeOrdersProcessor PBSSV manages the processing of the following web service operations:

Table 7-14 lists and describes the web service operations:

Table 7-14 Web service operations

Operation	Description
EngineeringChangeOrderPartsListProcessor (J3000020)	Use this operation to add ECOs.
InventoryItemsProcessor (J4100020)	Use this operation to add or modify item records.
InventoryItemBranchProcessor (J4100030)	Use this operation to add or modify item branch records.

For more information, see JD Edwards EnterpriseOne Business Services Reference Guide, "EngineeringChangeOrdersProcessor."

EngineeringChangeOrderPartsListProcessor (J3000020)

The EngineeringChangeOrdersProcessor calls the EngineeringChangeOrderPartsListProcessor web service. This processor calls the create ECO (B3004100) business function to add a parts list and related items in JD Edwards EnterpriseOne.

For more information, see JD Edwards EnterpriseOne Business Services Reference Guide, "EngineeringChangeOrderPartsListProcessor."

ProcessIntegrationTimeStamp (J3000030)

The IntegrationTimeStampManager PBSSV calls the ProcessIntegrationTimeStamp web service. This processor adds and modifies the Integration Time Stamp table (F0095) with the last successful runtime.

For more information, see JD Edwards EnterpriseOne Business Services Reference Guide, "ProcessIntegrationTimeStamp."

InventoryItemsProcessor (J4100020)

The EngineeringChangeOrdersProcessor calls the InventoryItemsProcessor web service This processor calls the F4101 ItemMasterAddition (B4101062) business function to add items in JD Edwards EnterpriseOne.

For more information, see JD Edwards EnterpriseOne Business Services Reference Guide, "InventoryItemsProcessor."

InventoryItemBranchProcessor (J4100030)

The EngineeringChangeOrdersProcessor calls the InventoryItemsProcessor web service is called. This processor calls the F4102 ItemBranchAddition (B4101072) business function to add item branch records in JD Edwards EnterpriseOne.

For more information, see JD Edwards EnterpriseOne Business Services Reference Guide, "InventoryItemsProcessor."

Table 7-15 lists and describes the operations:

Table 7-15 Web service operations

Operation	Description
EngineeringChangeOrdersProcessor (J3000010)	Use this operation to call other processors internally to add records into item, item branch, and ECO files.
EngineeringChangeOrderPartsListProcessor (J3000020)	Use this operation to add ECOs in the ECO file.
InventoryItemsProcessor (J4100020)	Use this operation to add or modify item records.
InventoryItemBranchProcessor (J4100030)	Use this operation to add or modify item branch records.

7.2.2.4 Setting Up BSSVs

Complete the following steps to set up BSSVs:

Enter P951000 in the Fast Path field.
Click Add.

The Work with Business Service Property page appears, see Figure 7-7.

Figure 7-7 Work with Business Property Page
Enter the values in the Key and Group fields as listed in Table 7-16

Table 7-16 Values for Key and Group fields

Key Value

J4100003_ITEM_MBF_VERSION

ZJDE0001

J4100003_ITEM_STOCKING_TYPE_CODE

S

J3000010_ECO_MBF_VERSION

ZJDE0001
Enter values in the Value and Description fields according to your requirements.

Key	Value
J4100003_ITEM_MBF_VERSION	ZJDE0001
J4100003_ITEM_STOCKING_TYPE_CODE	S
J3000010_ECO_MBF_VERSION	ZJDE0001

7.2.2.5 Configuration Parameters for Creating ECO Flow

The configuration parameters include:

Enter the UDC value of the implemented state in JD Edwards EnterpriseOne into the ECO_Implemented status configuration property.

This status is updated in the ECO, which is created for an ECO that does not hold any BOM information. Such ECOs carry only the items, which are created and updated from Agile PLM.
Set the Default_ECO_Branch_Plant in the AIA configuration property to specify the branch plant under which the ECO should be created for facilitating the modification of nonstock items from Agile PLM.
Ideally, nonstock items are not created in Agile PLM. However, because nonstock items flow in from JD Edwards EnterpriseOne to Agile PLM as part of initial loads, any changes made to these items are brought back as ECOs from Agile PLM, and they hold no branch plant information. Because the integration demands that ECOs be created with branch plant information, the system uses the default branch plant in this scenario.

7.2.3 Setting Up OWSM

You must set up the OWSM client agent to store the security credentials that are used by the JD Edwards EnterpriseOne web services.

This section discusses how to create credential maps and credential keys

7.2.3.1 Creating Credential Maps and Credential Keys

WLS stores the user name and password for web service (BSSV) calls here.

In FMW Control, navigate to WebLogic Domain >soa_domains and select Security > Credentials from the available options. See Figure 7-0.

Figure 7-8 Selecting security credentials
If the oracle.wsm.security map does not exist, click Create Map.
Enter the map name as oracle.wsm.security. You must not change this name. See Figure 7-0.

Figure 7-9 Create map
Highlight the new map.
Click Create Key.
Enter the key as JDEE1_BSSV.
Enter the E1 user name and password

You can also use the special E1 user name that includes environment and role as DN=JDE, ENV=DV900, ROLE=*ALL. See Figure 7-10.

Figure 7-10 Creating a key

7.2.4 Setting Up AIA

In the AIA config file, set a module-level property, DEFAULT_BOM_TYPE, which enables users to specify the BOM type that should be passed to JD Edwards EnterpriseOne. This information does not flow in from Agile PLM.

If you do not set this property for the forward flow from Agile PLM to JD Edwards EnterpriseOne, then JD Edwards EnterpriseOne will select the default BOM type from the Data Dictionary default value for the item.

Note:

his property is maintained at the module level because the BOM initial load uses the same property.

7.3 Setting Up Batch Processing Information

To use the Initial Load and Update flows from JD Edwards EnterpriseOne, you must first set up batch information. This section discusses how to:

Set up FTP adapter information
Set up batch consumer properties in the Enterprise Manager (EM) console
Set up resequencer for batch processing
Adjust timeout settings

7.3.1 Setting Up FTP Adapter Information

Setting up FTP adapter information includes configuring the JNDI name for the FTP adapter.

To set up FTP Adapter information, complete these steps:

Access the Weblogic console.

Navigate to Deployments and look for FtpAdapter.
Click the FtpAdapter link.
Navigate to Configuration tab > Outbound Connection Pools and click New.
Select the javax.resource.cci.ConnectionFactory group.
Click Next.
Enter the JNDI name as eis/Ftp/JDEE1FtpAdapter.
Click Finish.
Make sure the JNDI name was created on the Outbound Connection Pools tab.
Click the JNDI name that you created.

The Outbound Connection Properties page appears.
Edit the ftpAbsolutePathBegin, such as /slot/ems4309/appmgr, and press Enter.
Click Next to edit host, password, port, serverType, and username.
After you set the properties, click Save.
To update the deployment plan, navigate to the deployments page and select the FtpAdapter check box.
Click Update.
Click Next.
Click Finish.
Restart the soa_server to effect the FtpAdapter changes.

7.3.2 Setting Up Batch Consumer Properties

Complete the following steps to set up batch consumer properties:

For the initial load processes and other update processes to work correctly, set up properties from the Oracle Enterprise Manager console for these batch consumer services:

ItemInitialLoadExtractJDEE1Consumer
BillOfMaterialsInitialLoadExtractJDEE1Consumer

To set these properties, access the Oracle Enterprise Manager console, locate the services, and select the Properties tab. The Properties tab becomes available when you click <Consumer>_ep.

The PhysicalDirectory property for the ItemInitialLoadExtractJDEE1FTPConsumer_ep should match the path specified in the R4101D3 processing option relative to the FTP server default directory. If the files are written to D:\JDEdwards\E900\DDP\PrintQueue\ and the FTP server default directory is D:\JDEdwards, then the PhysicalDirectory property should be \E900\DDP\PrintQueue. The PhysicalDirectory property for the BillOfMaterialsInitialLoadExtractJDEE1FTPConsumer_ep should match the path specified in the processing options for R3002D relative to the FTP server default directory.

The PhysicalDirectory property for the ItemInitialLoadExtractJDEE1FileConsumer_ep and BillOfMaterialsInitialLoadExtractJDEE1FileConsumer_ep should match the location of <ORACLE_HOME>/JDEE1In/. These services are delivered with an example path that should be updated to reflect the implementation. After the extract programs execute in JD Edwards EnterpriseOne, move the files to the JDEE1 In folder arranged in the order for these file consumer services to find and process the files.

All consumer services discussed in this section have the following two properties, which you can configure as listed in Table 7-17:

Table 7-17 Consumer services properties

Property	Description
BatchSize	This property determines how many records to include in each batch. The default value for this property is 50. If you use a value larger than 50, the consumer services will not function properly because Agile Integration Services (AIS) would consume more time and cause a middleware timeout. We recommend that you do not change this value.
PollingFrequency	This property specifies the time interval, in seconds, when the file consumers check the PhysicalDirectory property for new files to process. The default value for this property is 30. Note: We recommend that you do not change the pollingFrequency or batchSize properties for the FTP adapter.

Property

Description

BatchSize

This property determines how many records to include in each batch. The default value for this property is 50. If you use a value larger than 50, the consumer services will not function properly because Agile Integration Services (AIS) would consume more time and cause a middleware timeout. We recommend that you do not change this value.

PollingFrequency

This property specifies the time interval, in seconds, when the file consumers check the PhysicalDirectory property for new files to process. The default value for this property is 30.

Note: We recommend that you do not change the pollingFrequency or batchSize properties for the FTP adapter.

For ECO, item list, item balance processes, and other update processes to work correctly, set up properties from the Oracle Enterprise Manager console for these batch consumer:

EngineeringChangeOrderListExtractJDEE1Consumer
ItemListExtractJDEE1Consumer
ItemBalanceListExtractJDEE1Consumer

To set up these properties, access the Oracle Enterprise Manager console, locate the services, and select the Properties tab, which becomes available when you click <Consumer> _ep. The PhysicalDirectory property for the EngineeringChangeOrderListExtractJDEE1FTPConsumer_ep should match the path specified in the R3013D processing option. The physicalDirectory property for the ItemListExtractJDEE1FTPConsumer_ep should match the path specified in the processing options for R4102D. The physicalDirectory property for the ItemBalanceListExtractJDEE1FTPConsumer_ep should match the path specified in the processing options for R41021D. These paths should be relative to the FTP setup path on the EnterpriseOne Enterprise Server.

The PhysicalDirectory property for the EngineeringChangeOrderListExtractJDEE1FileConsumer_ep, ItemListExtractJDEE1FileConsumer_ep, and ItemBalanceListExtractJDEE1FileConsumer_ep should match the location of <ORACLE_HOME>/JDEE1In/. These services are delivered with an example path, which is /slot/ems2593/oracle/Middleware/Oracle_SOA1/JDEE1In. Update this path to reflect your implementation. After the extract programs execute in JD Edwards EnterpriseOne, move the files to the JDEE1 In folder so that these file consumer services can find and process the files.

All of these consumer services have the following two properties, which you can configure as listed in Table 7-18:

Table 7-18 Consumer service properties

Property	Description
BatchSize	This property determines how many records to include in each batch. The default value for this property is 40.
PollingFrequency	This property specifies the time interval, in seconds, when the file consumers check the PhysicalDirectory property for new files to process. The default value for this property is 10. Note: We recommend that you do not change the pollingFrequency or batchSize properties for the FTP adapter.

Property

Description

BatchSize

This property determines how many records to include in each batch. The default value for this property is 40.

PollingFrequency

This property specifies the time interval, in seconds, when the file consumers check the PhysicalDirectory property for new files to process. The default value for this property is 10.

Note: We recommend that you do not change the pollingFrequency or batchSize properties for the FTP adapter.

For more information, see Enterprise Service Bus Quick Start Guide, "Creating, Configuring, and Managing an Oracle Enterprise Service Bus."

7.3.3 Setting Up Resequencer for Batch Processing

Log in to the Oracle Enterprise Manager console.
Select Soa Infrastructure and navigate to Administration > System MBean Browser. See Figure 7-0

Figure 7-11 System Mbean browser
Navigate to oracle.as.soainfra.config > Server:soa_server1 > MediatorConfig > mediator
On the right side, set the value of the attribute ResequencerWorkerThreadCount to 6. See Figure 7-6

Figure 7-12 Resequencer attribute

7.3.4 Adjusting Timeout Settings

You must set up the transaction timeout values using the Weblogic console and SyncMaxWaitTime using the Oracle Enterprise Manager console.

7.3.4.1 Setting SyncMaxWaitTime Value

Log in to the Oracle Enterprise Manager console.
Select Soa Infrastructure > navigate to Administration > System MBean Browser.
Navigate to oracle.as.soainfra.config > Server:soa_server1 > BPELConfig > bpel
On the right side, set the value of the SyncMaxWaitTime attribute to 360.

By default, the value is 45 and you should increase it to at least 360 to accommodate batch processing.

7.3.4.2 Setting Transaction Timeout Values

Log in to the Weblogic console.
Navigate to Services > JTA.
On the configuration page set the Timeout Seconds to 420.
Save the setting and restart the server.

7.4 SQL Script for Loading Cross-Reference Records

There is no utility in 11g to load cross-reference (XRef) 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 XRef table, ITEM_ITEMID with columns AGILE_01 and JDEE1_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/ITEM_ITEMID.xref';

IsDeleted_vc2 := 'N';

XrefColumnName1_vc2 := 'COMMON';

XrefColumnName2_vc2 := 'AGILE_01';

XrefColumnName3_vc2 := 'JDEE1_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 */

/********************************************** 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 JDEE1 value generation please check XREF_Instructions.doc */

7.5 Identifying Cross-References

Cross-references map and connect records within the application network, and they enable these applications to communicate in the same language. The integration server stores the relationship in a persistent way so that others can refer to it.

The three virtual tables in the AIA XRef schema's XREF_DATA table that maintain this cross-reference information are as follows:

CHANGE_CHANGEID: Includes change order information.
ITEM_ITEMID: Includes item information with branch/plant.
JDEE1_ITEMID: Includes item information without branch/plant.

Table 7-19 lists the cross-references:

Table 7-19 Cross reference

Name	Purpose	Columns
ITEM_ITEMID	Query/Create	JDEE1_01, COMMON, AGILE_01
CHANGE_CHANGEID	Query/Create	JDEE1_01, COMMON, AGILE_01
JDEE1_ITEMID	Query/Create	JDEE1_01, COMMON, AGILE_01

7.6 Populating Cross-References

If item and BOM initial loads are not used to synchronize item and BOM data between Agile and JDE, then you must manually populate the ITEM_ITEMID and JDEE1_ITEMID cross-reference (XRef) tables after installing and configuring the PIP.

You must manually add the cross-reference data into the ITEM_ITEMID and JDEE1_ITEMID XRef tables by using SQL insert statements. These tables hold item information for common value in edge applications.

For each JD Edwards EnterpriseOne 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 JD Edwards EnterpriseOne: JDEE1_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:

Table 7-20 XRef Table Format

Column Name	Description
XREF_TABLE_NAME	This column stores the XREF data types. For example: oramds:/apps/AIAMetaData/xref/ITEM_ITEMID.xref oramds:/apps/AIAMetaData/xref/JDEE1_ITEMID.xref
XREF_COLUMN_NAME	This column stores the values indicating the edge applications and COMMON value: AGILE_01 JDEE1_01 COMMON
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 7-21 ITEM_ITEMID XRef Table Value Format

XRef_Column_Name	Value
COMMON	GUID
AGILE_01	Agile ItemID::Site For example, 60031::M30
EBIZ_01	JDE ItemID::Branch/ Plant For example, 60031::M30

XRef_Column_Name

Value

COMMON

GUID

AGILE_01

Agile ItemID::Site

For example, 60031::M30

EBIZ_01

JDE ItemID::Branch/ Plant

For example, 60031::M30

Sample SQL Insert Statements for ITEM_ITEMID Table

For JDEE1_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', 'JDEE1_01', 'ROWNUM_ITEM_1', '204::BP', 'N', SYSTIMESTAMP)

Note:

The value for branch/plant in the value field varies depending on the JDE item type and Agile multi-site setup. For example, branch/plant that has disabled multi-site and non-stock item will have a value, "NOT_FOUND".

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', 'ROWNUM_ ITEM _1', '88-JKO29::BP', 'N', SYSTIMESTAMP)

Note:

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', 'ROWNUM_ ITEM _1', '1001001', 'N', SYSTIMESTAMP)

Note:

For the COMMON row, the value field will store a unique ID, for example, GUID. For each set, which includes JDEE1_01, AGILE _01, and COMMON, the row numbers must be identical to link these records to each other.

Table 7-22 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	JDEE1_01	B396F6CE586111E6E040F00A5B097CBF	60031::M30	N	08-DEC-11 08.14.34.028279000 AM
oramds:/apps/AIAMetaData/xref/ITEM_ITEMID.xref	AGILE_01	B396F6CE586111E6E040F00A5B097CBF	60031::M30	N	08-DEC-11 08.14.34.028279000 AM
oramds:/apps/AIAMetaData/xref/ITEM_ITEMID.xref	COMMON	B396F6CE586111E6E040F00A5B097CBF	B396F6CE586211E6E040F00A5B097CBF	N	08-DEC-11 08.14.34.028279000 AM

Table 7-23 JDEE1_ITEMID XRef Table Value Format

XRef_Column_Name	Value
COMMON	GUID
AGILE_01	Agile ItemID::Site For example, 60031
JDEE1_01	JDE ItemID For example, 60031

XRef_Column_Name

Value

COMMON

GUID

AGILE_01

Agile ItemID::Site

For example, 60031

JDEE1_01

JDE ItemID

For example, 60031

Sample SQL Insert statements for JDEE1_ITEMID Table

For JDEE1_01

INSERT INTO XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) VALUES ('oramds:/apps/AIAMetaData/xref/JDEE1_ITEMID.xref', 'JDEE1_01', 'ROWNUM_ITEM_1', '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/JDEE1_ITEMID.xref', 'AGILE _01', 'ROWNUM_ ITEM _1', '88-JKO29', '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/JDEE1_ITEMID.xref','COMMON', 'ROWNUM_ ITEM _1', '1001001', 'N', SYSTIMESTAMP)

Note:

For the COMMON row, the value field will store a unique ID, for example, GUID.

For more information about how to populate cross-references, see Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite, "Working with Cross References".

Table 7-24 Sample Data for XRef JDEE1 _ITEMID Table

XRef_Table	XRef_Column	Row_Number	Value	IS_Deleted	Last_Modified
oramds:/apps/AIAMetaData/xref/ JDEE1_ITEMID.xref	JDEE1_01	9C2518503F8211E0BFC94F4D51304781	60031	N	09-DEC-11 08.14.34.028279000 AM
oramds:/apps/AIAMetaData/xref/ JDEE1_ITEMID.xref	AGILE_01	9C2518503F8211E0BFC94F4D51304781	60031	N	09-DEC-11 08.14.34.028279000 AM
oramds:/apps/AIAMetaData/xref/ JDEE1_ITEMID.xref	COMMON	9C2518503F8211E0BFC94F4D51304781	2d353536363933353835353533303931	N	09-DEC-11 08.14.34.028279000 AM

7.7 Describing DVMs

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 runtime.

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.

Table 7-25 lists DVMs used for this integration and their delivered values:

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 the number of columns.

Table 7-25 Domain Value Mapping

DVM	Delivered Value
ECO_CLASSIFICATION_CODE.xml	ECO_OBJ/ClassificationCode
ECO_ECOSPECIFICATIONGROUP_CATEGORYCODE1.xml	ECO_OBJ/EngineeringChangeOrderSpecificationGroup/SpecificationGroup/Specification
ECO_ECOSPECIFICATIONGROUP_CATEGORYCODE10.xml	ECO_OBJ/EngineeringChangeOrderSpecificationGroup/SpecificationGroup/Specification
ECO_ECOSPECIFICATIONGROUP_CATEGORYCODE2.xml	ECO_OBJ/EngineeringChangeOrderSpecificationGroup/SpecificationGroup/Specification
ECO_ECOSPECIFICATIONGROUP_CATEGORYCODE3.xml	ECO_OBJ/EngineeringChangeOrderSpecificationGroup/SpecificationGroup/Specification
ECO_ECOSPECIFICATIONGROUP_CATEGORYCODE4.xml	ECO_OBJ/EngineeringChangeOrderSpecificationGroup/SpecificationGroup/Specification
ECO_ECOSPECIFICATIONGROUP_CATEGORYCODE5.xml	ECO_OBJ/EngineeringChangeOrderSpecificationGroup/SpecificationGroup/Specification
ECO_ECOSPECIFICATIONGROUP_CATEGORYCODE6.xml	ECO_OBJ/EngineeringChangeOrderSpecificationGroup/SpecificationGroup/Specification
ECO_ECOSPECIFICATIONGROUP_CATEGORYCODE7.xml	ECO_OBJ/EngineeringChangeOrderSpecificationGroup/SpecificationGroup/Specification
ECO_ECOSPECIFICATIONGROUP_CATEGORYCODE8.xml	ECO_OBJ/EngineeringChangeOrderSpecificationGroup/SpecificationGroup/Specification
ECO_ECOSPECIFICATIONGROUP_CATEGORYCODE9.xml	ECO_OBJ/EngineeringChangeOrderSpecificationGroup/SpecificationGroup/Specification
ECO_PRIORITY_CODE.xml	ECO_OBJ/PriorityCode
ECO_REASON_CODE.xml	ECO_OBJ/ReasonCode
ECO_STATUS_CODE.xml	ECO_OBJ/Status/Code
ECO_TYPECODE.xml	ECO_OBJ/TypeCode
ITEM_DUAL_UOM_TRACKING_INDICATOR.xml	ITEM_OBJ/DualUOMTrackingIndicator
ITEM_INDICATOR.xml	ITEM_OBJ/ItemPurchasingCharacteristics/TaxableIndicator ITEM_OBJ/ItemManufacturingCharacteristics/StructureAllowedIndicator
ITEM_INVENTORY_PLANNING_CODE.xml	ITEM_OBJ/ItemPlanningCharacteristics/InventoryPlanningCode
ITEM_INVOICINGENABLEDINDICATOR.xml	ITEM_OBJ/ItemOrderManagementCharacteristics/InvoicingEnabledIndicator
ITEM_ITEMSPECIFICATIONGROUP_CYCLECOUNTCATEGORY.xml	ITEM_OBJ/ItemSpecificationGroup/SpecificationGroup/Specification
ITEM_ITEMSPECIFICATIONGROUP_PURCHASINGREPORTCODE1.xml	ITEM_OBJ/ItemSpecificationGroup/SpecificationGroup/Specification
ITEM_ITEMSPECIFICATIONGROUP_PURCHASINGREPORTCODE10.xml	ITEM_OBJ/ItemSpecificationGroup/SpecificationGroup/Specification
ITEM_ITEMSPECIFICATIONGROUP_PURCHASINGREPORTCODE2.xml	ITEM_OBJ/ItemSpecificationGroup/SpecificationGroup/Specification
ITEM_ITEMSPECIFICATIONGROUP_PURCHASINGREPORTCODE3.xml	ITEM_OBJ/ItemSpecificationGroup/SpecificationGroup/Specification
ITEM_ITEMSPECIFICATIONGROUP_PURCHASINGREPORTCODE4.xml	ITEM_OBJ/ItemSpecificationGroup/SpecificationGroup/Specification
ITEM_ITEMSPECIFICATIONGROUP_PURCHASINGREPORTCODE5.xml	ITEM_OBJ/ItemSpecificationGroup/SpecificationGroup/Specification
ITEM_ITEMSPECIFICATIONGROUP_PURCHASINGREPORTCODE6.xml	ITEM_OBJ/ItemSpecificationGroup/SpecificationGroup/Specification
ITEM_ITEMSPECIFICATIONGROUP_PURCHASINGREPORTCODE7.xml	ITEM_OBJ/ItemSpecificationGroup/SpecificationGroup/Specification
ITEM_ITEMSPECIFICATIONGROUP_PURCHASINGREPORTCODE8.xml	ITEM_OBJ/ItemSpecificationGroup/SpecificationGroup/Specification
ITEM_ITEMSPECIFICATIONGROUP_PURCHASINGREPORTCODE9.xml	ITEM_OBJ/ItemSpecificationGroup/SpecificationGroup/Specification
ITEM_ITEMSPECIFICATIONGROUP_SALESREPORTINGCODE1.xml	ITEM_OBJ/ItemSpecificationGroup/SpecificationGroup/Specification
ITEM_ITEMSPECIFICATIONGROUP_SALESREPORTINGCODE10.xml	ITEM_OBJ/ItemSpecificationGroup/SpecificationGroup/Specification
ITEM_ITEMSPECIFICATIONGROUP_SALESREPORTINGCODE2.xml	ITEM_OBJ/ItemSpecificationGroup/SpecificationGroup/Specification
ITEM_ITEMSPECIFICATIONGROUP_SALESREPORTINGCODE3.xml	ITEM_OBJ/ItemSpecificationGroup/SpecificationGroup/Specification
ITEM_ITEMSPECIFICATIONGROUP_SALESREPORTINGCODE4.xml	ITEM_OBJ/ItemSpecificationGroup/SpecificationGroup/Specification
ITEM_ITEMSPECIFICATIONGROUP_SALESREPORTINGCODE5.xml	ITEM_OBJ/ItemSpecificationGroup/SpecificationGroup/Specification
ITEM_ITEMSPECIFICATIONGROUP_SALESREPORTINGCODE6.xml	ITEM_OBJ/ItemSpecificationGroup/SpecificationGroup/Specification
ITEM_ITEMSPECIFICATIONGROUP_SALESREPORTINGCODE7.xml	ITEM_OBJ/ItemSpecificationGroup/SpecificationGroup/Specification
ITEM_ITEMSPECIFICATIONGROUP_SALESREPORTINGCODE8.xml	ITEM_OBJ/ItemSpecificationGroup/SpecificationGroup/Specification
ITEM_ITEMSPECIFICATIONGROUP_SALESREPORTINGCODE9.xml	ITEM_OBJ/ItemSpecificationGroup/SpecificationGroup/Specification
ITEM_ITEMSPECIFICATIONGROUP_SHIPPINGCOMMODITYCLASS.xml	ITEM_OBJ/ItemSpecificationGroup/SpecificationGroup/Specification
ITEM_ITEMSPECIFICATIONGROUP_SHIPPINGCONDITIONSCODE.xml	ITEM_OBJ/ItemSpecificationGroup/SpecificationGroup/Specification
ITEM_MAKEORBUY_CODE.xml	ITEM_OBJ/ItemPlanningCharacteristics/MakeOrBuyCode
ITEM_PURCHASINGALLOWEDINDICATOR.xml	ITEM_OBJ/ItemPurchasingCharacteristics/PurchasingAllowedIndicator
ITEM_REPLENISHMENT_SOURCE_CODE.xml	ITEM_OBJ/ItemPlanningCharacteristics/ReplenishmentSourceCode
ITEM_SERIALIZATION_EVENT_CODE.xml	ITEM_OBJ/InventoryCharacteristics/SerializationEventCode
ITEM_STATUS_CODE	ITEM_OBJ/Status/Code
ITEM_STOCKINGALLOWEDINDICATOR.xml	ITEM_OBJ/InventoryCharacteristics/StockingAllowedIndicator
ITEM_TYPE.xml	ITEM_OBJ/TypeCode
ITEM_UOM_CODE.xml	ITEM_OBJ/BaseUOMCode ITEM_OBJ/ShippingUOMCode ITEM_OBJ/SecondaryUOMCode ITEM_OBJ/ItemPhysicalCharacteristics/VolumeMeasure ITEM_OBJ/ItemPurchasingCharacteristics/IssueUOMCode ITEM_OBJ/ItemPhysicalCharacteristics/WeightMeasure
AGILE_SITE_TARGET_MAPPING	DEFAULT_MASTER_ORG in JD Edwards EnterpriseOne is used when the Multisite_Enabled property is set to False and no branch/plant is associated with the item in Agile.
AGILE_TARGET_SITE_MAPPING	The JD Edwards EnterpriseOne branch/plant to Agile PLM sites is mapped. A one-to-one mapping exists between the EnterpriseOne branch/plant to Agile PLM site.

7.8 Viewing EIMs

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.

7.9 Setting Configuration Properties

This integration uses various configuration parameters that control the behavior of the flow. You use the Standard AIA XML configuration file and the AIAConfigurationProperties.xml file for capturing configuration parameters. AIA configuration file supports system-level configuration parameters, service-level parameters, and module configuration parameters. System-level parameters apply to all integrations running on the SOA suite. You can configure service-level parameters at the individual service level, such as ABCS.

Note: This section lists the configuration properties from the Agile PLM Module and the JD Edwards EnterpriseOne Module separately only for the purpose of identification. The actual AIAConfigurationProperties.xml file on the AIA Server is a merge of both.

Formoreinformation about updating SOA MDS with AIA metadata, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1, "How to Set Up AIA Workstation," Updating SOA MDS with AIA MetaData.

Configuration Parameters

This integration uses the following configuration parameters:

PIP level configuration parameters: PIP Configuration parameters are implemented using AIA module configuration entry.

The module configuration entry has a name and can contain any number of configuration parameters. A naming convention of PIPS.PIPName is used for naming modules. The parameters inside the module are named using with 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 using AIA service configuration parameters. Service configuration entry is identified by the service name such as CreateItemAgileReqABCSImpl. The parameter names themselves are named using cascaded naming convention as explained earlier.

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 Flows," How to Set Up AIA Workstation.

For more information about updating SOA MDS with AIA metadata, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1, "How to Set Up AIA Workstation," Updating MDS.

Table 7-26 lists the Agile PLM configuration properties, value/setting default values, and descriptions:

Table 7-26 Agile PLM configuration properties

Property	Value/Setting (default)	Description
moduleName	Agile
MULTISITE_ENABLED	TRUE	When set to True, the sites specified on Sites tab of items are used to determine the Orgs in JD Edwards EnterpriseOne to which they are mapped. When set to False, Page2 Multilist01attribute is used to determine the Orgs in JD Edwards EnterpriseOne to which the Item is extended.
Item.UnitCostAttribute	Site.Numeric01	Determines the attribute to which the unit cost from JD Edwards EnterpriseOne is updated in Agile PLM.
Item.AvailableQuantityAttribute	Site.Numeric02	Determines the attribute to which the available quantity from JD Edwards EnterpriseOne is updated in Agile PLM.
Item.OnHandQuantityAttribute	Site.Numeric03	Determines the attribute to which the on-hand quantity from JD Edwards EnterpriseOne is updated in Agile PLM.
Item.ReservedQuantityAttribute	Site.Numeric04	Determines the attribute to which the reserved quantity from JD Edwards EnterpriseOne is updated in Agile PLM.
REPLICATE_BOM_ENABLED	FALSE	Used for sample replicate BOM customization.
COMMON_BOM_ENABLED	FALSE	Used for sample common BOM customization.

Note:

Multisite_Enabled property is governed by Distributed Processing aspects covered in Release of Change Order in Agile PLM. When it is set to TRUE (default), the Item.UnitCostAttribute, Item.AvailableQuantityAttribute, Item.OnHandQuantityAttribute, and Item.ReservedQuantityAttribute are set to Site tab flex attributes.

You can use Numeric, Text, or Money flex fields of Site tab for these settings, and it is denoted by the first element, Site. For example, Site.Numeric01

When set to FALSE; all these attributes are set to Page2 or Page3 Flex Fields. Therefore, you must change the settings to PageTwo.Numeric01 or PageThree.Numeric01, accordingly. Derive the names of the attributes from the ItemABM Schema, which you can find in Agile PLM Interfaces.

Table 7-27 lists the setting for the CreateQueueService service property:

Table 7-27 Settings CreateQueueService service property

Property	Value/Setting (default)	Description
TRACE.LOG.ENABLED	False	Use tracelog for the flow.

Table 7-28 lists the setting for the QueueProcessorServiceImpl service property:

Table 7-28 Settings for QueueProcessorServiceImpl service property

Property	Value/Setting (default)	Description
TRACE.LOG.ENABLED	False	Use tracelog for the flow.

Table 7-29 lists the settings for the UpdateEngineeringChangeOrderListAgileProvABCSImpl service properties:

Table 7-29 Settings for UpdateEnginneringChangeOrder property

Property	Default Value/Setting	Description
ABCSExtension.PreProcessABM	false	User exit for the preprocess Application Business Message (ABM) should be called or not
ABCSExtension.PreProcessEBM	false	User exit for the preprocess 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.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.ChangeABSService.RouteToCAVS	false	If set to True route to CAVS; otherwise, route to the Agile PLM application. This invocation relates to the change ABS service
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.
Routing.ChangeABSService.CAVS.EndpointURI	http://${http.hostname}:${http.port}/AIAValidationSystemServlet/syncresponsesimulator	CAVS SOAP URL When the RouteToCAVS property is set to true, use the URL mentioned to connect to CAVS. This invocation relates to the change ABS service
Routing.MergeABSService.RouteToCAVS	false	If set to True, route to CAVS; otherwise, route to the Agile PLM application. This invocation relates to the change merge ABS service
Routing.MergeABSService.CAVS.EndpointURI	http://${http.hostname}:${http.port}/AIAValidationSystemServlet/syncresponsesimulator	CAVS Simple Object Access Protocol (SOAP) URL When the RouteToCAVS property is set to true, use the URL mentioned to connect to CAVS. This invocation relates to the change merge ABS 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.
Routing.ChangeStatusService.RouteToCAVS	false	If set to true, it is routed to CAVS; otherwise, routed to the Agile PLM application. This invocation relates to the change status ABS service
Routing.ChangeStatusService.CAVS.EndpointURI	http://${http.hostname}:${http.oort}/AIAValidationSystemServlet/syncresponsesimulator	CAVS URL When the RouteToCAVS property is set to true, use the URL mentioned to connect to CAVS. This invocation relates to the change status ABS 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.
Routing.ChangeStatusDBAdapter.RouteToCAVS	false	If set to true, it is routed to CAVS; otherwise, routed to the Agile PLM application. This invocation relates to the change status EDB Adapter
Routing.ChangeStatusDBAdapter.CAVS.EndpointURI	http://${http.hostname}:${http.port}/AIAValidationSystemServlet/syncresponsesimulator	CAVS URL When the RouteToCAVS property is set to true, use the URL mentioned to connect to CAVS. This invocation relates to the change status EDB Adapter
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 7-30 lists the settings for the UpdateItemBalanceListAgileProvABCSImpl service properties:

Table 7-30 Settings for UpdateItemBalance property

Property	Value/Setting (default)	Description
Default.SystemID	AGILE_01	System ID of Agile PLM application instance
Routing.ItemABSService.RouteToCAVS	FALSE	If set to True, route to CAVS; otherwise, route to Agile PLM application. This invocation is for Item ABS
Routing.ItemABSService.CAVS.EndpointURI	http://${http.hostname}:${http.port}/AIAValidationSystemServlet/syncresponsesimulator Routing.ItemBalanceResponseEBS.UpdateItemBalanceListResponse.RouteToCAVS	CAVS URL; When RouteToCAVS property is set to True, use the URL mentioned to connect to CAVS. This invocation is for item ABS
Routing.ItemABSService.AGILE_01.EndpointURI	http:// ${agile.host}:${agile.port}/Agile/integration/services/ItemABS	ItemABS URL. When RouteToCAVS property is set to False, use the URL mentioned to connect to the Agile ItemABS service
Routing.ItemBalanceResponseEBS.UpdateItemBalanceListResponse.CAVS.EndpointURI	http://${http.hostname}:${http.port}/AIAValidationSystemServlet/asyncresponsesimulator	CAVS URL; When RouteToCAVS property is set to True, use the URL mentioned to connect to CAVS. This invocation is for Itembalance response EBS
Routing.ItemBalanceResponseEBS.UpdateItemBalanceListResponse.MessageProcessingInstruction.EnvironmentCode	Environment code such as 'PRODUCTION'/ 'CAVS' and so on. Identifies the installation environment
ABCSExtension.PreProcessABM	FALSE	Decides whether user exit for the preprocess ABM should be called or not
ABCSExtension.PreProcessEBM	FALSE	Decides whether user exit for the preprocess EBM should be called or not
ABCSExtension.PostProcessEBM	FALSE	Decides whether user exit for the post-process EBM should be called or not
ABCSExtension.PostProcessABM	FALSE	Decides whether user exit for the post-process ABM should be called or not
TRACE.LOG.ENABLED	FALSE	Use tracelog for the flow
ROUTE_TO_CAVS	FALSE	Route to CAVS if set as True
DEFAULT_TARGET_ENDPOINT_URI	http://<host>:<port>/event/CoreAgile/ItemBalanceResponseEBS	ItemBalanceResponseEBS runtime target endpoint URI

Table 7-31 lists the settings for the UpdateItemListAgileProvABCSImpl service properties:

Table 7-31 Settings for UpdateItemListAgile Property

Property	Value/Setting (default)	Description
Default.SystemID	AGILE_01	System ID of Agile PLM application instance
Routing.ItemResponseEBSV2.UpdateItemListResponse.MessageProcessingInstruction.EnvironmentCode	Environment code such as 'PRODUCTION'/ 'CAVS' and so on. Identifies the installation environment
Routing.ItemABSService.RouteToCAVS	FALSE	If set to True, route to CAVS; otherwise, route to Agile PLM application. This invocation is for Agile Item ABS service.
Routing.ItemABSService.AGILE_01.EndpointURI	http://${agile.host}:${agile.port}/${agiag.path}/integration/services/ItemABS	ItemABS URL. When RouteToCAVS property is set to False, use the URL mentioned to connect to the Agile ItemABS Service.
Routing.ItemABSService.CAVS.EndpointURI	http://${http.hostname}:${http.port}/AIAValidationSystemServlet/syncresponsesimulator	Agile Item ABS service SOAP URL. When RouteToCAVS property is set to True, use the URL mentioned to connect to CAVS. This invocation is for Agile Item ABS service
Routing.ItemResponseEBSV2.UpdateItemListResponse.RouteToCAVS	FALSE	If set to True, route to CAVS; otherwise, route to response item EBS. This invocation is for response item EBS
Routing.ItemResponseEBSV2.UpdateItemListResponse.CAVS.EndpointURI	http://${http.hostname}:${http.port}/AIAValidationSystemServlet/asyncresponsesimulator	CAVS URL; When RouteToCAVS property is set to True, use the URL mentioned to connect to CAVS. This invocation is for Item response EBS
ABCSExtension.PreProcessABM	FALSE	Decides whether user exit for the preprocess ABM should be called or not
ABCSExtension.PreProcessEBM	FALSE	Decides whether user exit for the preprocess EBM should be called or not
ABCSExtension.PostProcessEBM	FALSE	Decides whether user exit for the post-process EBM should be called or not
ABCSExtension.PostProcessABM	FALSE	Decides whether user exit for the post-process ABM should be called or not
TRACE.LOG.ENABLED	FALSE	Use tracelog for the flow
ROUTE_TO_CAVS	FALSE	Route to CAVS if set as True
DEFAULT_TARGET_ENDPOINT_URI	http://localhost:8888/event/CoreAgile/ItemResponseEBSV2	ItemResponseEBSV2 runtime target endpoint URI

Table 7-32 lists the settings for the ProcessEngineeringChangeOrderAgileReqABCSImpl service properties:

Table 7-32 Settings for ProcessEngineeringChangeOrder Property

Property	Value/Setting (default)	Description
Default.SystemID	AGILE_01	System ID of Agile PLM application instance
Routing.EngineeringChangeOrderEBS.CreateEngineeringChangeOrderList.RouteToCAVS	FALSE	If set to True, route to CAVS; otherwise, route to EngineeringChangeOrder EBS
Routing.EngineeringChangeOrderEBS.CreateEngineeringChangeOrderList.CAVS.EndpointURI	http://${http.hostname}:${http.port}/AIAValidationSystemServlet/asyncresponsesimulator	CAVS URL When 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' and so on. Identifies the installation environment
ABCSExtension.PreProcessABM	FALSE	Decides whether user exit for the preprocess ABM should be called or not
ABCSExtension.PreProcessEBM	FALSE	Decides whether user exit for the preprocess EBM should be called or not
ABCSExtension.PostProcessEBM	FALSE	Decides whether user exit for the post-process EBM should be called or not
ABCSExtension.PostProcessABM	FALSE	Decides whether user exit for the post-process ABM should be called or not
TRACE.LOG.ENABLED	FALSE	Use tracelog for the flow
ROUTE_TO_CAVS	FALSE	Route to CAVS, if set as True
DEFAULT_TARGET_ENDPOINT_URI	http://<host>:<port>/event/CoreAgile/EngineeringChangeOrderEBS	EngineeringChangeOrderEBS runtime target endpoint URI
Default.SystemID	AGILE_01	System ID of Agile PLM application instance
Routing.ItemEBSV2.CreateItem.RouteToCAVS	FALSE	If set to rue, route to CAVS; otherwise, route to Item EBS
Routing.ItemEBSV2.CreateItem.CAVS.EndpointURI	http://${http.hostname}:${http.port}/AIAValidationSystemServlet/asyncresponsesimulator	CAVS SOAP URL; when RouteToCAVS property is set to True, use the URL mentioned to connect to CAVS
Routing.ItemEBSV2.CreateItem.MessageProcessingInstruction.EnvironmentCode	PRODUCTION	Environment code such as 'PRODUCTION'/ 'CAVS' and so on. Identifies the installation environment
Routing.ChangeABSService.RouteToCAVS	False	If set to True, route to CAVS, otherwise, route to Agile application. This invocation is for Change ABS
Routing.ChangeABSService.AGILE_01.EndpointURI	http:// ${agile.host}:${agile.port}//Agile/integration/services/ChangeABS	ChangeABS URL When RouteToCAVS property is set to false, use the URL mentioned to connect to the Agile ChangeABS service
Routing.ChangeABSService.CAVS.EndpointURI	http://${http.hostname}:${http.port}/AIAValidationSystemServlet/asyncresponsesimulator	CAVS URL When RouteToCAVS property is set to True, use the URL mentioned to connect to CAVS. This invocation is for Change ABS

Table 7-33 lists the settings for the JD Edwards EnterpriseOne properties:

Table 7-33 Settings for JDEE1 Property

Property	Value/Setting (default)	Description
AGILE_NAMESPACE	AGILE_AXML_SCHEMA_NAMESPACE	This property is used in initial loads. The token AGILE_AXML_SCHEMA_NAMESPACE is replaced automatically with the Agile namespace corresponding to the versions of Agile PLM during PIP Installation.
DEFAULT_BOM_TYPE	M	Default BOM type
INITIALLOAD.DEFAULT.SOURCE	JDEE1_01	System ID of JD Edwards EnterpriseOne instance
INITIALLOAD.DEFAULT.TARGET	AGILE_01	System ID of Agile PLM application instance
AGILE_USERNAME	admin	Username used for invoking an Agile Integration Service (AIS) operation or creating a session for Agile PLM Server Instance while using Agile PLM Agile Software Development Kit (SDK)
AGILE.PASSWORD	participatingapplications.agile.password	Encrypted password used for invoking an AIS operation or creating a session for Agile PLM Server Instance while using Agile SDK Note: Because this is an encrypted password, it is automatically populated during PIP Installation. If required, populate with the ${participatingapplications.agile.password} value from the AIAInstall.properties file in AIA_HOME/aia_instances/<aiainstance name>/config
AGILE_CHANGE_TYPE	ECO	The ChangeType option used by AIS when importing items/BOM in the redline mode This is the subclass name of the change order for the ECO.
AGILE_CHANGE_WORKFLOW	JD Edwards EnterpriseOne Initial Load Change Orders	The name of the change order workflow used to advance the change order directly from Pending to Released status Note: This workflow name should match the workflow created in Chapter 7 - Setting Up Agile PLM Applications, Create New Workflow for Initial Load Change Orders section.

Table 7-34 lists the settings for the CreateEngineeringChangeOrderListJDEE1ProvABCSImpl service properties:

Table 7-34 Settings for CreateEngineeringChangeOrder property

Property	Value/Setting (default)	Description
Default.SystemID	JDEE1_01	System ID of JD Edwards EnterpriseOne instance
Routing.EngineeringChangeOrderManager.RouteToCAVS	False	If set to True, route to CAVS otherwise, route to JD Edwards EnterpriseOne. This invocation is for the EngineeringChangeOrderManager ABS service
Routing.EngineeringChangeOrderResponseEBS.RouteToCAVS	False	If set to True, route to CAVS; otherwise, route to ECO Response EBS. This invocation is for ECO response EBS
Routing.EngineeringChangeOrderManager.CAVS.EndpointURI	http://${http.hostname}:${http.port}//AIAValidationSystemServlet/syncresponsesimulator	CAVS SOAP URL When RouteToCAVS property is set to True, use the URL mentioned to connect to CAVS. This invocation is for the EngineeringChangeOrderManager ABS service
Routing.EngineeringChangeOrderResponseEBS.CAVS.EndpointURI	http://${http.hostname}:${http.port}//AIAValidationSystemServlet/asyncresponsesimulator	CAVS SOAP URL When RouteToCAVS property is set to True, use the URL mentioned to connect to CAVS. This invocation is for ECO response EBS
Routing.EngineeringChangeOrderManager.JDEE1_01.EndpointURI	${participatingapplications.jdee1.ws.url}/EngineeringChangeOrderManager	JD Edwards EnterpriseOne EngineeringChangeOrderManager ABS service URL. When RouteToCAVS property is set to False, use the URL mentioned to connect to JD Edwards EnterpriseOne This invocation is for the EngineeringChangeOrderManager ABS service
ABCSExtension.PreProcessABM	False	Decides whether user exit for the preprocess ABM should be called or not
ABCSExtension.PostProcessABM	False	Decides whether user exit for the preprocess EBM should be called or not
ABCSExtension.PreProcessEBM	False	Decides whether user exit for the post-process EBM should be called or not
ABCSExtension.PostProcessEBM	False	Decides whether user exit for the post-process ABM should be called or not
Trace.Log.Enabled	False	Use tracelog for the flow
Routing.EngineeringChangeOrderResponseEBS.MessageProcessingInstruction.EnvironmentCode	PRODUCTION	Environment code such as 'PRODUCTION'/ 'CAVS' and so on. Identifies the installation environment
ECO_Implemented_Status	E5
Default_ECO_Branch_Plant

Table 7-35 lists the settings for the UpdateEngineeringChangeOrderListJDEE1ReqABCSImpl service properties:

Table 7-35 Settings for UpdateEngineeringChangeOrder property

Property	Value/Setting (default)	Description
Default.SystemID	JDEE1_01	System ID of JD Edwards EnterpriseOne instance
ABCSExtension.PreXformABMtoEBM	False	Decides whether user exit for the preprocess ABM should be called or not
ABCSExtension.PostXformABMtoEBM	False	Decides whether user exit for the preprocess EBM should be called or not
ABCSExtension.PreInvokeEBS	False	Decides whether user exit for the post-process EBM should be called or not
ABCSExtension.PostInvokeEBS	false	Decides whether user exit for the post-process ABM should be called or not
Routing.TimeStampManager.RouteToCAVS	false	If set to true route to CAVS else route to JD Edwards EnterpriseOne. This invocation is for IntegrationTimeStampManager ABS service
Routing.TimeStampManager.CAVS.EndpointURI	http://${http.hostname}:${http.port}/AIAValidationSystemServlet/syncresponsesimulator	CAVS SOAP URL When RouteToCAVS property is set to True, use the URL mentioned to connect to CAVS. This invocation is for IntegrationTimeStampManager ABS service
Routing.EngineeringChangeOrderEBS.UpdateEngineeringChangeOrderList.RouteToCAVS	false	If set to True, route to CAVS; otherwise, route to ECO EBS. This invocation is for ECO EBS
Routing.EngineeringChangeOrderEBS.UpdateEngineeringChangeOrderList.CAVS.EndpointURI	http://${http.hostname}:${http.port}/AIAValidationSystemServlet/asyncresponsesimulator	CAVS SOAP URL When RouteToCAVS property is set to true, use the URL mentioned to connect to CAVS. This invocation is for ECO EBS
Routing.EngineeringChangeOrderEBS.UpdateEngineeringChangeOrderList.MessageProcessingInstruction.EnvironmentCode	PRODUCTION	Environment code such as 'PRODUCTION'/ 'CAVS' and so on. Identifies the installation environment
Routing.TimeStampManager.JDEE1_01.EndpointURI	${participatingapplications.jdee1.ws.url}/IntegrationTimeStampManager	JD Edwards EnterpriseOne IntegrationTimeStampManager ABS service URL. When RouteToCAVS property is set to False, use the URL mentioned to connect to JD Edwards EnterpriseOne. This invocation is for IntegrationTimeStampManager ABS service
TRACE.LOG.ENABLED	false	Use tracelog for the flow

Table 7-36 lists the settings for the UpdateItemBalanceListJDEE1ReqABCSImpl service properties:

Table 7-36 Settings for UpdateItemBalance property

Property	Value/Setting (default)	Description
Default.SystemID	JDEE1_01	System ID of JD Edwards EnterpriseOne instance
ABCSExtension.PreXformABMtoEBM	False	Decides whether user exit for the preprocess ABM should be called or not
ABCSExtension.PostXformABMtoEBM	False	Decides whether user exit for the preprocess EBM should be called or not
ABCSExtension.PreInvokeEBS	False	Decides whether user exit for the post-process EBM should be called or not
ABCSExtension.PostInvokeEBS	False	Decides whether user exit for the post-process ABM should be called or not
Routing.TimeStampManager.RouteToCAVS	False	If set to True, route to CAVS; otherwise, route to JD Edwards EnterpriseOne. This invocation is for IntegrationTimeStampManager ABS service
Routing.TimeStampManager.CAVS.EndpointURI	http://${http.hostname}:${http.port}/AIAValidationSystemServlet/syncresponsesimulator	CAVS SOAP URL: when RouteToCAVS property is set to True, use the URL mentioned to connect to CAVS. This invocation is for IntegrationTimeStampManager ABS service
Routing.ItemBalanceEBS.UpdateItemBalanceList.RouteToCAVS	FALSE	If set to True, route to CAVS; otherwise, route to ItemBalance EBS. This invocation is for ItemBalance EBS
Routing.ItemBalanceEBS.UpdateItemBalanceList.CAVS.EndpointURI	http://${http.hostname}:${http.port}/AIAValidationSystemServlet/asyncresponsesimulator	CAVS SOAP URL When RouteToCAVS property is set to True, use the URL mentioned to connect to CAVS. This invocation is for ItemBalance EBS.
Routing.ItemBalanceEBS.UpdateItemBalanceList.MessageProcessingInstruction.EnvironmentCode	PRODUCTION	Environment code such as 'PRODUCTION'/ 'CAVS' and so on. Identifies the installation environment
Routing.TimeStampManager.JDEE1_01.EndpointURI	${participatingapplications.jdee1.ws.url}/IntegrationTimeStampManager	JD Edwards EnterpriseOne IntegrationTimeStampManager ABS service URL. When RouteToCAVS property is set to False, use the URL mentioned to connect to JD Edwards EnterpriseOne. This invocation is for IntegrationTimeStampManager ABS service
TRACE.LOG.ENABLED	false	Use tracelog for the flow

Table 7-37 lists the settings for the UpdateItemListJDEE1ReqABCSImpl service properties:

Table 7-37 Settings for UpdateItemlist property

Property	Value/Setting (default)	Description
Default.SystemID	JDEE1_01	System ID of JD Edwards EnterpriseOne instance
ABCSExtension.PreXformABMtoEBM	False	Decides whether user exit for the preprocess ABM should be called or not
ABCSExtension.PostXformABMtoEBM	false	Decides whether user exit for the preprocess EBM should be called or not
ABCSExtension.PreInvokeEBS	False	Decides whether user exit for the post-process EBM should be called or not
ABCSExtension.PostInvokeEBS	False	Decides whether user exit for the post-process ABM should be called or not
Routing.TimeStampManager.RouteToCAVS	False	If set to True, route to CAVS; otherwise, route to JD Edwards EnterpriseOne. This invocation is for IntegrationTimeStampManager ABS service
Routing.TimeStampManager.CAVS.EndpointURI	http://${http.hostname}:${http.port}/AIAValidationSystemServlet/syncresponsesimulator	CAVS SOAP URL When RouteToCAVS property is set to True, use the URL mentioned to connect to CAVS. This invocation is for IntegrationTimeStampManager ABS service
Routing.ItemEBSV2.UpdateItemList.RouteToCAVS	FALSE	If set to True, route to CAVS; otherwise, route to ItemBalance EBS. This invocation is for ItemBalance EBS
Routing.ItemEBSV2.UpdateItemList.CAVS.EndpointURI	http://${http.hostname}:${http.port}/AIAValidationSystemServlet/asyncresponsesimulator	CAVS SOAP URL When RouteToCAVS property is set to True, use the URL mentioned to connect to CAVS. This invocation is for ItemBalance EBS
Routing.ItemEBSV2.UpdateItemList.MessageProcessingInstruction.EnvironmentCode	PRODUCTION	Environment code such as 'PRODUCTION'/ 'CAVS' and so on. Identifies the installation environment
Routing.TimeStampManager.JDEE1_01.EndpointURI	${participatingapplications.jdee1.ws.url}/IntegrationTimeStampManager	JD Edwards EnterpriseOne IntegrationTimeStampManager ABS service URL. When RouteToCAVS property is set to False, use the URL mentioned to connect to JD Edwards EnterpriseOne. This invocation is for IntegrationTimeStampManager ABS service
TRACE.LOG.ENABLED	false	Use tracelog for the flow

Table 7-38 lists the settings for the InitialLoadBillOfMaterialsListJDEE1toAgileImpl service properties:

Table 7-38 Settings for InitialLoadBillofMaterial property

Property	Value/Setting (default)	Description
Default.SystemID	JDEE1_01	System ID of JD Edwards EnterpriseOne instance
TRACE.LOG.ENABLED	False	Use tracelog for the flow
ABCSExtension.PreXformABMtoAXML	False	Decides whether user exit for the preprocess ABM should be called or not
ABCSExtension.PreInvokeAIS	False	Decides whether user exit for the preprocess Agile aXML should be called or not
PARENT_ITEM_REVISION_LEVEL	B01	The item revision that is used in Agile PLM for the parent items updated Note: If the BOM Extract UBE is not set up to retrieve the BOM Parent Item Revision level, then this needs to be populated with the non-blank value; otherwise, the BOM initial load will not function correctly.
RELEASE_CHANGE_ORDER_REASON	JD Edwards EnterpriseOne to Agile PLM BOM Initial Load	The Change Order Reason to add to the Change Order created in Agile PLM
RELEASE_CHANGE_ORDER_DESCRIPTION	JDEE1 to Agile PLM BOM Initial Load	The Change Order Description to add to the Change Order created in Agile PLM

Table 7-39 lists the settings for the InitialLoadItemListJDEE1toAgileImpl service properties:

Table 7-39 Settings for InitialLoadItemList property

Property	Value/Setting (default)	Description
Default.SystemID	JDEE1_01	System ID of JD Edwards EnterpriseOne instance
TRACE.LOG.ENABLED	False	Use tracelog for the flow
ABCSExtension.PreXformABMtoAXML	False	Decides whether user exit for the preprocess ABM should be called or not
ABCSExtension.PreInvokeAIS	False	Decides whether user exit for the preprocess Agile aXML should be called or not.
PRIMARY_ITEM_ID	2ndItemNumber	Property that determines which JD Edwards EnterpriseOne Item Number to use in Agile PLM
ITEM_REVISION_LEVEL	A01	The item revision that is used in Agile PLM for all items imported Note: This field needs to be populated with the non-blank value; otherwise, the item initial load will not be processed.
RELEASE_CHANGE_ORDER_REASON	JD Edwards EnterpriseOne to Agile PLM Item Initial Load	The Change Order Reason to add to the Change Order created in Agile PLM
RELEASE_CHANGE_ORDER_DESCRIPTION	JD Edwards EnterpriseOne to Agile PLM Item Initial Load	The Change Order Description to add to the Change Order created in Agile PLM

Multisite_Enabled property is governed by distributed processing aspects.

When it is set to TRUE (default), the Item.UnitCostAttribute, Item.AvailableQuantityAttribute, Item.OnHandQuantityAttribute, and Item.ReservedQuantityAttribute are set to the Site tab flex attributes.

You can use the Numeric, Text, or Money flex fields of the Site tab for these settings, and it is denoted by the first element, Site. For example, Site.Numeric01

When set to FALSE, these attributes are set to Page2 or Page3 flex fields, requiring you to change the setting to PageTwo.Numeric01 or PageThree.Numeric01, accordingly. Derive the names of the attributes from the ItemABM schema, which you can find in the Agile PLM Interfaces section.

For more information, see Release of Change Order in Agile PLM and Agile PLM Interfaces sections of this document.

7.10 Handling Errors

The Design to Release integration uses the Mediator resequencer to manage errors and failures during web service processing. No PIP-specific errors are issued by the Design to Release services within the AIA system.

For more information about the errors caused by Agile PLM or JD Edwards EnterpriseOne, see the product-specific documentation.

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 and Using Error Handling and Logging."

7.10.1 Resequencing and Error Handling

The initial load flow in the Design to Release Agile PLM - JD Edwards EnterpriseOne integration uses the Mediator resequencer feature to manage errors and failures. The resequencer introduces a data store that stores failed messages until the system successfully processes them. If the message fails, it remains in the resequencer store and blocks any other messages that belong to the same group.

These services have resequencing enabled:

ItemInitialLoadExtractJDEE1FileConsumer_RS
ItemInitialLoadExtractJDEE1FTPConsumer_RS
BillOfMaterialsInitialLoadExtractJDEE1FileConsumer_RS
BillOfMaterialsInitialLoadExtractJDEE1FTPConsumer_RS

ItemInitialLoadExtractJDEE1FileConsumer_RS/ItemInitialLoadExtractJDEE1FTPConsumer_RS and BillOfMaterialsInitialLoadExtractJDEE1FileConsumer_RS/BillOfMaterialsInitialLoadExtractJDEE1FTPConsumer_RS are initiated before the initial load item and BillOfMaterials JDEE1toAgile PLM services in their respective flows, and they protect the item and BOMs flows from JD Edwards EnterpriseOne to Agile PLM. If an error occurs in either of these flows, the message remains in the resequencer store that is associated with Mediator, and the system locks the group.

For item processing, the group is defined by the first short item number in the batch. For BOM processing, the group is defined by a first parent short item number in the batch. For example, if an item message for short item 61021 fails and the system then attempts to process item message for item 61021, then the second message will not be processed. It remains in the resequencer store along with the first message until the system successfully processes the first message.

The main purpose of the resequencer during initial load processing is to regulate the initial load processing so that all messages are split into a number of threads defined in the Mediator resequencing configuration. By default, the system creates four groups, which are called 1, 2, 3, and 4.

After unlocking the group, the message that contained the failed record is reprocessed. Therefore, the error should be identified and corrected before unlocking the group. After the failed message is successfully processed, the system processes any messages that follow it in the same group.

You can unlock a group by connecting to the WLS database with the appropriate user name and password and running the following script:

pdate mediator_group_status set status = '0'
where status!=0 and group_id='844334' and component_dn = 'default/ItemInitialLoadExtractJDEE1Consumer!1.0/ItemInitialLoadExtractJDEE1FileConsumer_RS'
commit;

Note:

Obtain the user name and password from your SOA administrator.

Note:

The values associated with group_id and name should be changed to the appropriate values, where group_id is the name of the group to unlock, and name is the name of the mediator routing service with the resequencer. Then, the message that failed is reprocessed. If it passes, any other messages in that group is processed one at a time until the system encounters another failure or all messages are processed successfully.

7.10.1.1 Logic Used to Determine Notification Roles for an Error

The Error Handling Framework uses runtime values and the data you enter on this page to execute the following hierarchical logic to determine the appropriate notification roles for an error:

If all four runtime values (SYSTEM_CODE, ERROR_CODE, SERVICE_NAME, and PROCESS_NAME) are available and they map to an error notification entry in this table, use the specified notification roles.
If the ERROR_CODE, SERVICE_NAME, and PROCESS_NAME are available and map to an error notification entry in this table, use the specified notification roles.
If the SERVICE_NAME and PROCESS_NAME are available and map to an error notification entry in this table, use the specified notification roles.
If the SERVICE_NAME is available and maps to an error notification entry in this table, use the specified notification roles.
If none of these values is available, the system fetches default values from the AIAConfigurationProperties.xml file.

7.10.2 Error Handling in PIP Queue Manager

You can review processes that fail during the change order flow using the Queue Manager. To see why a process failed, click the Errored link for detailed information.

Figure 7-13illustrates how errors appear on the Change Order Queue page:

Figure 7-13 Change Order Queue

This image is described in surrounding text

Figure 7-14 illustrates a sample error message:

Figure 7-14 Example of sample error message

The sample error message has two parts:

Error Text: Text of error source, which can be from any participating ABCS that may have faulted.
Details: Error Details consist of:

Service Name: The name of the service where an instance failed to process

Instance ID: The identification number of the instance that failed

Multiple faults generated by the service are captured and appeared in this error message. In addition, any failures in the flows are captured in the AIA error logs. You can see these from the Oracle Enterprise Manager console logs section.

If a service is down and the error is not related to the payload, then users can resubmit the change in the Queue Manager.

Table 7-40 lists the errors generated by the PIP services and the message text of each:

Table 7-40 Errors generated by PIP services

Error Code	Message Text
AIA_ERR_AIAAGILEJDEE1_0003	No error message has been specified for the input key
AIA_ERR_AIAAGILEJDEE1_0004	None of the ECOs selected have been integrated

Table 7-41 lists the errors generated by initial load and the message text for each:

Table 7-41 Errors generated by initial load

Error Code	Message Text
Invoke AIS Design
AIA_ERR_AIAAGILEJDEE1_0013	File does not exist:
Release ECO Design
AIA_ERR_AIAAGILEJDEE1_0010	Failed
AIA_ERR_AIAAGILEJDEE1_0011	Release ECO SDK Execution Failed:
AIA_ERR_AIAAGILEJDEE1_0012	Could not find Change Order workflow:
AIA_ERR_AIAAGILEJDEE1_0015	The Change Order Not found -
Initial Load BOM JD Edwards EnterpriseOne to Agile PLM design
AIA_ERR_AIAAGILEJDEE1_0001	For additional information navigate to <SOA_HOME>/agile/ais/fileResult and review the following file:
AIA_ERR_AIAAGILEJDEE1_0006	All Bill Of Materials Batch Quantity should be equal to Zero.
AIA_ERR_AIAAGILEJDEE1_0007	All Bill Of Materials Type should be equal to 'DEFAULT_BOM_TYPE' AIA Configuration Property value.
AIA_ERR_AIAAGILEJDEE1_0008	Multiple Bill Of Materials for the same Parent Item is not allowed when 'MULTISITE_ENABLED' property is set to 'FALSE'
AIA_ERR_AIAAGILEJDEE1_0009	Bill Of Materials Components with 'Non-Stock' Stocking Type is not allowed when 'MULTISITE_ENABLED' property is set to 'TRUE'.
Initial Load Item JD Edwards EnterpriseOne to Agile PLM Design
AIA_ERR_AIAAGILEJDEE1_0001	For additional information navigate to <SOA_HOME>/agile/ais/fileResult and review the following file:
AIA_ERR_AIAAGILEJDEE1_0002	The Branch Plants in the input message do not have a mapped value in the AGILE_TARGET_SITE_MAPPING DVM
AIA_ERR_AIAAGILEJDEE1_0014	None of the Items selected have associated Branch Plants
AIA_ERR_AIAAGILEJDEE1_0016	Invalid Item Revision Level: Make sure 'ITEM_REVISION_LEVEL' Property in AIA Configuration Properties is not Blank

For more information about the errors generated by Agile PLM or JD Edwards Enterprise Business Service (EBS), see the product-specific documentation.

7.10.2.1 Mechanism for Error Handling and Reporting

Log in to the Oracle Enterprise Manager console.
Click Farm_soa_domain > SOA > soa_infra (<server instance>).
Select the Instances tab. See Figure 7-6

Figure 7-15 Path to navigate to faulted instance
Click the faulted instance (each faulted instance has the symbol in the State field).
Click the faulted instance again in the next window. See Figure 7-16

Figure 7-16 Fault Instance
The next window displays the details of the flow trace; click the component that faulted. See Figure 7-17

Figure 7-17 Flow Trace
The next window displays details of the flow; select either the Audit Trail or the Flow tab from this window.

Figure 7-18 illustrates the example of the Audit Trail window:

Figure 7-18 Audit Trial

Figure 7-19 illustrates the example of Flow window:

Figure 7-19 Flow Tab

7.11 Viewing EIMs

For more information about how services are mapped, see the My Oracle Support document: EBO Implementation Maps (EIMs) 881022.1.

Field	Value/Setting
Name	Define your own
Status Type	Pending
Status Stamp Color	Define your own