3 Process Integration for Item Attributes and Cost Updates

This chapter provides an overview of the process integration for item attributes and cost updates and discusses:

• Item attributes and cost updates process integration

• Solution assumptions and constraints

• Agile Product Lifecycle Management (PLM) interfaces

• JD Edwards EnterpriseOne interfaces

• Core Application Integration Architecture (AIA) components

• Integration services

3.1 Overview

You complete the update of item attribute and unit cost information from JD Edwards EnterpriseOne to Agile PLM as a batch process. You run a new Universal Batch Engine (UBE) program to extract a list of items (including obsolete items if not filtered in data selection) whose attribute values and unit cost must be updated in Agile PLM. Obsolete items shall be marked as obsolete in the item life cycle field of Agile PLM.

You schedule the execution of the Item data extract UBE R4102D program. This program generates an XML file that contains item data as well as values for all the attributes and unit cost information, which is updated to Agile PLM.

Because this is an update to Agile PLM, the items in the XML input file should already exist in Agile PLM; check the cross-reference record to verify this. If a cross-reference record exists for the item, then Agile PLM updates the corresponding item record with item attribute information from JD Edwards EnterpriseOne. If no cross-reference record exists for the item, then Agile PLM does not update the item record (it is skipped).

The extract includes basic and additional item information, units of measure (UOMs), sales, purchasing classifications, inventory processing information, and so forth, from Item Master (F4101), Item Branch (F4102), and Unit Cost information (F4105).

Item cost information flows one way, from JD Edwards EnterpriseOne to Agile PLM. Agile PLM uses this data strictly for informational purposes to help with product design. You should not change costs in Agile PLM, but if you do, then they are not sent back to JD Edwards EnterpriseOne. R4102D only retrieves items that changed since the last successful run (the last successful run date and time are stored in an IntegrationTimeStamp table, F0095 for this UBE) or the As of Date specified in the processing option.

The system writes this file to a folder on the JD Edwards EnterpriseOne Enterprise server. You specify the location of this folder in the processing options of the extract program. Details about the extract programs and files are discussed in later sections of this chapter.

After creating the XML files, you can use one of two methods to pass that data to Agile PLM:

• File Transfer Protocol (FTP)

• Weblogic Server

If you use the FTP method, you must configure an FTP adapter for the Update Item Attributes and Unit Cost process to monitor the JDEE1 Enterprise Server folders for newly created extract files. When the FTP adapter locates a new file, the appropriate Mediator process debatches the files into separate instances. Debatching is used to split large XML files into several smaller XML files.

Alternatively, you can move the XML files to the JD Edwards EnterpriseOne JDEE1In folder on the Weblogic Server. If you use this method, the appropriate Mediator process detects the file and debatches it into separate instances.

After the system debatches the XML files, routing services route each XML file to UpdateItemListJDEE1ReqABCSImpl, which then performs the following actions:

• Transforms Item application business message (ABM) to Item enterprise business message (EBM)

• Invokes ItemEBSV2, which does the routing to the provider Application Business Connector Services (ABCS): UpdateItemListAgileProvABCSImpl

• The Agile ABCS provides a call back response to ItemResponseEBSV2. UpdateItemListJDEE1ReqABCSImpl receives this response and updates the IntegrationTimeStamp table with the last successful run date and time.

Note:

If you use the FTP method, you must configure an FTP server on the JD Edwards EnterpriseOne Enterprise server. Configure the FTP adapter to use the FTP connection that is set up on the Enterprise server.

3.2 Item Attributes and Cost Updates Process Integration

This section discusses:

• Update item attribute flow

• Update item attribute orchestration

3.2.1 Update Item Attribute Flow

To extract the updated item attribute and unit cost information in JD Edwards EnterpriseOne, users should run the Item and Cost Extract batch program (R4102D). R4102D retrieves items that have changed since the last successful run (the last successful run date and time is stored in an IntegrationTimeStamp table - F0095 for this UBE) or the As Of date specified in the processing options.

This program retrieves these items and creates an XML file. If it completes successfully, it also creates a PDF with a successful completion message and the number of items extracted. The system stores the XML file in a folder on the JD Edwards EnterpriseOne Enterprise server. Users should specify the location of the folder in the processing options of the R4102D program.

After the files are written to the JD Edwards EnterpriseOne server, one of these consumer services retrieves and debatches the XML files:

• ItemListExtractJDEE1FTPConsumer_ep

  Use this consumer service to configure the FTP adapter to locate files.

• ItemListExtractJDEE1FileConsumer_ep

  Use this consumer service to move your files to the JD EE1In file on the Weblogic Server.

XML debatching allows the large XML file that the extract program creates to be split into several smaller XML files. The routing service then routes each XML file to UpdateItemListJDEE1ReqABCSImpl. This BPEL service transforms UpdateItemListABM to UpdateItemListEBM. As part of this transformation, if the BPEL service finds any items that were created in JD Edwards EnterpriseOne, it checks them against the cross-reference table and drops them if found.

The BPEL service then makes an asynchronous request-delayed response call to ItemEBSV2 with UpdateItemListEBM. This call is routed to UpdateItemListAgileProvABCSImpl.

UpdateItemListAgileProvABCSImpl updates the item in Agile PLM and sends response UpdateItemListResponseEBM.

UpdateItemListJDEE1ReqABCSImpl receives the response, uses DynamicPartnerlink to determine TargetEndpointLocation, and invokes the IntegrationTimeStampManager web service. IntegrationTimeStampManager web service updates the last successful run date and time in the IntegrationTimeStamp table, F0095 for this batch program (R4102D).

Figure 3-1 illustrates the update item attribute process flow from JD Edwards EnterpriseOne to Agile PLM:

Figure 3-1 Update Item Attribute process flow

3.2.2 Update Item Attribute Orchestration

Table 3-1 lists the activities involved in the update item attribute orchestration:

Table 3-1 Activities for Update Item Attribute Orchestration

Step	Activity	Remarks
1	Run R4102D to export items	This activity occurs when you update item-related information in JD Edwards EnterpriseOne
2	ItemListExtractJDEE1FTPConsumer or ItemListExtractJDEE1FIleConsumer reads and debatches the file	ItemListExtractJDEE1Consumer is triggered.
3	Activate JD Edwards EnterpriseOne Item Operational Attribute Update Action trigger	JD Edwards EnterpriseOne Item Operational Attribute Update Action trigger invokes the UpdateItemListJDEE1ReqABCSImpl
4	UpdateItemListJDEE1ReqABCSImpl invokes ItemEBSV2	An invoke activity in UpdateItemListJDEE1ReqABCSImpl invokes the UpdateItemList operation on ItemEBSV2 with UpdateItemListEBM as input
5	ItemEBSV2 routes the UpdateItemListEBM to UpdateItemListAgileProvABCSImpl	ItemEBSV2 routes UpdateItemListEBM as input to UpdateItemListAgileProvABCSImpl
6	UpdateItemListAgileProvABCSImpl invokes the Agile PLM Item Operational Attribute Update web service	ItemEBSV2 routes UpdateItemListEBM as input to UpdateItemListAgileProvABCSImpl. UpdateItemListAgileProvABCSImpl transforms the UpdateItemListEBM to AgileUpdateItemListABM and invokes the UpdateItem service operation on Agile web service to update item cost-related attribute information from JD Edwards EnterpriseOne to Agile PLM. Note: The UpdateItemListAgileProvABCSImpl composite uses the oracle/wss_http_token_client_policy client security policy while calling ItemABS Service hosted on the Agile server. The security credentials for this are stored in the csf-key AgileWebServicesKey on Fusion Middleware (FMW). The Agile username and password must be setup correctly so that the Agile service is invoked successfully from the AIA composite in the FMW layer. The AgileUpdateItemListResponseABM is returned to UpdateItemListAgileProvABCSImpl
7	UpdateItemListAgileProvABCSImpl sends a response to ItemResponseEBSV2	UpdateItemListAgileProvABCSImpl transforms the AgileUpdateItemListResponseABM to UpdateItemListResponseEBM and sends a response to ItemResponseEBSV2
8	ItemResponseEBSV2 sends the UpdateItemListResponseEBM to UpdateItemListJDEE1ReqABCSImpl	ItemResponseEBSV2 sends the UpdateItemListResponseEBM to UpdateItemListJDEE1ReqABCSImpl

3.3 Solution Assumptions and Constraints

This design assumes that the following statements are true:

1. If item information needs to be retrieved from multiple branch/plants in JD Edwards EnterpriseOne, the following constraints should be met to support this process:

   • Configure Agile PLM multi-sites

   • Set up one-to-one mapping between Agile PLM sites and JD Edwards EnterpriseOne branch/plants. Use domain value maps (DVMs) to accomplish this mapping.

   Locate the attributes to be updated with JD Edwards EnterpriseOne data on the Sites tab of the item if multi-site is configured.

2. Agile PLM multi-sites are required when item information needs to be retrieved from multiple branch/plants in JD Edwards EnterpriseOne. You can update any Title Block or Page Two attribute with the JD Edwards EnterpriseOne data.

3. Multiple item cost records can be retrieved for any item when the item cost level is 3.

   In such a case, the UBE extracts the first record to XML and suppresses the processing of subsequent records.

4. If Currency processing is enabled in JD Edwards EnterpriseOne and if the unit cost is not zero, then the currency code is sent back to Agile PLM

5. If the cost is maintained at Item Level, then the Default Company Currency code is sent back to Agile PLM.

6. The JD Edwards EnterpriseOne IntegrationTimeStampManager business service updates the last batch extract date/time as the Enterprise Server Date/Time

Note:

If you use the FTP method, you must configure an FTP server on the JD Edwards EnterpriseOne Enterprise server. Configure the FTP adapter to use the FTP connection that is set up on the Enterprise server.

3.4 Agile PLM Interfaces

Table 3-2 lists the Agile PLM Web Services Definition Language (WSDL) files:

Table 3-2 Agile PLM Web Services Definition Language (WSDL) files

Interface	Description
UpdateItemListAgileProvABCSImpl
ItemABS.wsdl	ItemABS.wsdl

Table 3-3 lists the Agile PLM XML Schema Definition (XSD) files:

Table 3-3 Agile PLM XML Schema Definition (XSD) files

Interface	Description
UpdateItemListAgileProvABCSImpl
ItemABM.xsd	Contains the Update Item List Request and Response ABM
ItemABO.xsd	Contains the Update Item List Request and Response ABM

3.5 JD Edwards EnterpriseOne Interfaces

Table 3-4 lists the JD Edwards EnterpriseOne WSDL files:

Table 3-4 JD Edwards EnterpriseOne WSDL files

Interfaces	Description
UpdateItemListJDEE1ReqABCSImpl
IntegrationTimeStampManager.wsdl	IntegrationTimeStampManager.wsdl

Table 3-5 lists the JD Edwards EnterpriseOne XSD files:

Table 3-5 JD Edwards EnterpriseOne XSD files

Interface	Description
UpdateItemListJDEE1ReqABCSImpl
R4102D.xsd	Contains the Update Item List Request ABM

3.6 Core AIA Components

Table 3-6 lists the industry components of process integration for update item attributes:

Table 3-6 Industry Components for Update Item Attributes

Component	Name
EBO	ItemEBO
EBMs	UpdateItemListEBM UpdateItemListResponseEBM
EBS	ItemEBSV2 ItemResponseEBSV2

Table 3-7 lists the locations of components:

Table 3-7 Location of Components

Component	Location
EBO and EBM XSD files	$AIA_HOME/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Core/EBO/
WSDL files	$AIA_HOME/AIAMetaData/AIAComponents/EnterpriseBusinessServiceLibrary/Core/EBO/

For detailed documentation of individual EBOs and EBMs, click the AIA Reference Doc link, EBO, and EBM detail pages in Oracle Enterprise Repository.

For more information about using the Oracle Enterprise Repository and configuring it to provide the AIA Reference Doc link, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1, "Configuring and Using Oracle Enterprise Repository as the Oracle AIA SOA Repository."

EBOs can be extended, for instance, to add new data elements. These extensions are protected, and remains intact after a patch or an upgrade.

For more information, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1.

3.7 Agile PLM and JD Edwards EnterpriseOne Components for Update Item Attributes

Table 3-8 lists the requester and provider for each service:

Table 3-8 Requester and Provider for each service

Service	JD Edwards EnterpriseOne (Requester)	Agile PLM (Provider)
ABM	R4102D	AgileUpdateItemListABM AgileUpdateItemListResponseABM
ABCS	UpdateItemListJDEE1ReqABCS	UpdateItemListAgileProvABCSImpl
EBS	ItemEBSV2	ItemResponseEBSV2

Table 3-9 lists the locations of components:

Table 3-9 Location of components

Component	Location
Application Business Objects, ABM, and Common XSD files	$AIA_HOME/AIAMetaData/AIAComponents/ApplicationObjectLibrary/Agile/V1/schemas/
WSDL files	$AIA_HOME/AIAMetaData/AIAComponents/ApplicationObjectLibrary/Agile/V1/wsdls/

3.8 Integration Services

The process integration for item attributes and cost updates from JD Edwards EnterpriseOne to Agile PLM uses these industry components:

• ItemEBSV2

• UpdateItemListJDEE1ReqABCSImpl

• UpdateItemListAgileProvABCSImpl

3.8.1 ItemEBSV2

ItemEBSV2 is the EBS that exposes the operations related to the item integration on the Item EBO.

The routing rules are:

• ItemEBSV2 Mediator service

  UpdateItemListJDEE1ReqABCSImpl :Route UpdateItemListEBM to UpdateItemListAgileProvABCSImpl

• ItemResponseEBSV2 Mediator service

  UpdateItemListAgileProvABCSImpl Route UpdateItemResponseEBM to UpdateItemJDEE1ReqABCSImpl

3.8.2 UpdateItemListJDEE1ReqABCSImpl

UpdateItemListJDEE1ReqABCSImpl transforms the JD Edwards EnterpriseOne message (UpdateItemListABM) into UpdateItemListEBM and calls the routing service to update item list attributes and item cost attributes. It then gets the UpdateItemListResponseEBM response from Agile PLM and invokes the Integration Time Stamp Manager service to update the Integration Time Stamp table with the last runtime and date.

Process flow:

1. Picks up the xml file based on the properties set in the file and ftp consumer.

2. Receives UpdateItemListABM from file and ftp consumer

3. Transforms JD Edwards EnterpriseOne-specific UpdateItemListABM into UpdateItemListEBM

4. Populates the EBM header

5. Calls the ItemEBSV2 service to send message UpdateItemListEBM to UpdateItemListAgileProvABCSImpl

6. Receives UpdateItemListResponseEBM from ItemResponseEBSV2

7. Calls the Integration Time Stamp Manager service to update the Integration Time Stamp table with the last runtime and date

8. Transforms UpdateItemListJDEE1ReqABCSImpl using this transformation:

Xform_ItemListABMReqMsg_To_ItemListEBMReqMsg

3.8.3 UpdateItemListAgileProvABCSImpl

You use UpdateItemListAgileProvABCSImpl to facilitate communications between ItemEBSV2 and Agile PLM web service used for updating the cost information for an item in batch mode in Agile PLM.

It performs the following actions:

1. Receives UpdateItemListReqMsg, which contains UpdateItemListEBM

2. Calls a transform operation to convert the UpdateItemListEBM into AgileUpdateItemListABM

3. Sends AgileUpdateItemListABM as input to the web service operation UpdateItems (coarse-grained application programming interfaces (APIs) on the Agile PLM side) to update items in Agile PLM

4. Receives AgileUpdateItemListResponseABM on successful execution of coarse-grained API

5. Calls a transform operation to convert the AgileUpdateItemListABM to UpdateItemListResponseEBM, which is returned as an output of this BPEL process

   If the UpdateItems service operation fails on the Agile PLM side, the system generates a new fault and sends it across with the appropriate error message.