Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning

Implementation Guide

Release 2.1.1

E63504-03

August 2016(Updated February 2019)

Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning Implementation Guide for Release 2.1.1

Copyright © 2000, 2019, Oracle and/or its affiliates. All rights reserved.

Primary Author: Oracle Corporation

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Integration Overview

This document provides configuration and administration information for the Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning, including:

•

About the Integration Product

•

Supported Business Processes

Note : All participating applications must be installed, set up, and working properly. Please refer to the installation guide for more information.

About the Integration Product

The Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning enables integration of Oracle Utilities Work and Asset Management with a generic set of business processes and data exchanges for implementations with Enterprise Resource Planning systems such as Oracle E-Business Suite, PeopleSoft, JD Edwards EnterpriseOne, Fusion Applications or Enterprise Resource Planning Cloud.

This integration product enables Oracle Utilities Work and Asset Management to work with typical functions for purchasing, financials, inventory, human resources and other work. This enables organizations to perform work in the preferred application, but have the ability for different types of users to access the relevant information in either system.

The following process integration points are included with this integration pack:

• The master data processes that synchronize data that has been created or updated in the system of record.

• The business transaction processes that are triggered based on the appropriate status transitions (such as approved, complete or frozen) to send and process in the other system.

• For both the master data and transaction processes:

•

The common EBO definitions are used to share information in a generic format that is independent of specific enterprise applications.

•

The connector provides transformations to and from the Oracle Utilities Work and Asset Management application business messages.

•

The connector allows for extension points to include additional data elements or enrich the messages as needed for custom requirements.

•

An error handling process logs any errors that occur during data integration.

•

Email notification process that notifies identified users, by email, of any errors and the details associated with those errors

•

The integration’s common error handling process handles all errors, however if your implementation also wants to use the SOA Suite 12c error hospital feature, you can implement it using the guidelines provided in the installation guide. For more information about error hospital and error notifications, see the section "Recovering From Faults in the Error Hospital" in Oracle® Fusion Middleware Administering Oracle SOA Suite and Oracle Business Process Management Suite documentation.

About the Participating Products

The following products are involved in the integration:

•

Oracle Utilities Work and Asset Management (WAM)

•

Enterprise Resource Planning System (ERP)

•

Oracle SOA Suite

Refer to the installation guide for current application version details.

Oracle Utilities Work and Asset Management (WAM)

Oracle Utilities Work and Asset Management efficiently manages asset lifecycles, streamlines maintenance operations, maximizes supply chain performance, enhances safety, and improves regulatory compliance.

Oracle Utilities Work and Asset Management is an industry-specific solution that allows organizations to improve work efficiency and infrastructure reliability, while reducing maintenance cost and capital requirements. Oracle Utilities Work and Asset Management captures the maintenance and the failure history of the assets in the enterprise and allows users to plan project work and estimate effort, resources, and materials.

Enterprise Resource Planning System (ERP)

The Enterprise Resource Planning system is a resource-planning software, which enforces industry best-practice controls on data input and processes as tasks are completed within the system. The processes are typically separated into modules, and each module consists of a collection of user interfaces where data is entered at each stage of the business process.

Oracle SOA Suite

The Oracle Fusion Middleware product, Oracle SOA Suite, coordinates the data processing and data mapping of the integration connections. Used as an Oracle standard across most pre-built integrated solutions, Oracle SOA Suite provides a comprehensive solution for creating, deploying, and managing cross-application business processes with both automated and manual workflow steps. It supports open technology standards such as BPEL, XML, XSLT, XPATH, JMS, JCA, and Web Services.

Supported Business Processes

This integration of systems enables key functionality in the areas of purchasing, financials, inventory, human resources, and work to facilitate the transfer of information between related applications. Data is sent from Oracle Utilities Work and Asset Management to Enterprise Resource Planning systems and vice versa to support the data synchronization, transactions and actions.

There are two primary business models supported by this Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning product:

•

Model 1 - Oracle Utilities Work and Asset Management Supply Chain Business Model

•

Model 2 - Enterprise Resource Planning System Supply Chain Business Model (ESC)

In either business model, the Enterprise Resource Planning system is a system of record for general ledger and accounts payable information as well as human resources and project financial information; and Oracle Utilities Work and Asset Management is the system of record for asset-related and work-related information and functions such as cost accounting associated with assets and work. What often changes, between the business models chosen, is which system owns the information and processes related to inventory and purchasing (the supply chain functions).

The configuration of the systems and their integration points can be different for each business model. This section of the document is intended to help you decide, which business model you implement, and therefore which technical configuration you should utilize for your organization.

Model 1 - Oracle Utilities Work and Asset Management Supply Chain Business Model

Use Oracle Utilities Work and Asset Management to manage most supply chain functions and Enterprise Resource Planning system to manage accounts payable invoice and payment functions.

Application Product

Managed Functions

Business Model to

Configure

Enterprise Resource Planning system

All corporate functions including General Ledger, Accounts Payable invoice and payment functions plus Human Resources employee and employee craft wages.

Oracle Utilities Work and Asset Management

All supply chain functions in addition to work management, cost accounting, and asset management functions.

Work and Asset Management Supply Chain Model

Note : Invoice sync from WAM to ERP is performed through a batch process.

The following diagram provides a visual representation of this processing:

Integration Processes for WSC Business Model

Model 2 - Enterprise Resource Planning System Supply Chain Business Model (ESC)

Use Enterprise Resource Planning system to manage all the supply chain functions and Oracle Utilities Work and Asset Management for cost accounting, work and asset management functions .

Application Product

Managed Functions

Business Model to

Configure

Enterprise Resource Planning system

All the supply chain functions including General Ledger, inventory, purchasing, vendor management, employee, employee craft wages, accounts payable, and paying AP invoices.

Enterprise Resource Planning system Supply Chain model

Oracle Utilities Work and Asset Management

All work management, asset management and cost accounting functions.

The following diagram provides a visual representation of this processing:

Integration Processes for ESC Business Model

Technical Overview

This section provides a technical overview of the integration, including:

•

Introduction

•

Enterprise Resource Planning System Initiated Messages

•

Oracle Utilities Work and Asset Management Initiated Messages

Introduction

This connector is an Integration Accelerator Pack which provides integration of Oracle Utilities Work and Asset Management interfaces with a generic Enterprise Resource Planning system.

XML messages are exchanged between Oracle Utilities Work and Asset Management and Enterprise Resource Planning system and the message can either be initiated from Oracle Utilities Work and Asset Management or from the Enterprise Resource Planning system.

The existing AIA foundation Pack’s common Enterprise Business Objects (EBOs) message format is used to exchange XML messages between the Integration Accelerator Pack and the Enterprise Resource Planning system. The EBOs used in this integration are part of installation.

Oracle SOA Suite installed on WebLogic server is used to host SOA composites, which are used for the integration between the two systems.

Oracle SOA Suite uses the standard data mapping to extract, transform and load the data taken from the source system and insert into the target system.

If the source system is the Oracle Utilities Work and Asset Management system:

•

Oracle Utilities Work and Asset Management generates the request data and calls the integration web service.

•

The SOA composite accepts the XML data in the Oracle Utilities Work and Asset Management system format.

•

BPEL transforms the data into the appropriate EBO format.

•

The XML message is inserted in the JMS queue in EBO format. The JMS queues are used to store messages and provide guaranteed delivery.

•

A custom connector process transforms the data from EBO format into an appropriate ERP format.

If the source system is the Enterprise Resource Planning system:

•

The Enterprise Resource Planning system generates the request data and calls the integration web service.

•

The SOA composite accepts the XML data in the ERP format.

•

A custom connector process transforms the data in ERP format into EBO format.

•

The XML message is inserted in the JMS queue in EBO format. The JMS queues are used to store messages and provide guaranteed delivery.

•

BPEL transforms the data into the appropriate Oracle Utilities Work and Asset Management format.

•

The integration invokes the appropriate Oracle Utilities Work and Asset Management web service.

Process Diagram

The following diagram provides a high level representation of the complete integration.

High Level Diagram

Enterprise Resource Planning System Initiated Messages

This section describes technical processing when the Enterprise Resource Planning system generates the request data and calls the integration web service. The following diagram provides a visual representation of this processing:

Enterprise Resource Planning Initiated Message Request/Response Process

Enterprise Resource Planning System Initiated Request Process

The request process includes:

•

Custom implementation process

•

Integration ERP requestor process

•

Integration WAM provider process

Request processing is completed as described below:

•

The Custom Implementation process should perform the following:

•

Receives the message sent by the Enterprise Resource Planning system in the object's ERP schema format.

•

Creates the request message in the EBO format; transforms the data from ERP format to EBO format.

•

Invokes the Integration ERP Requestor BPEL Web Service to send the message

•

The Integration ERP Requestor BPEL process performs the following:

•

Receive the message in EBO format sent by the custom implementation process.

•

Store the EBO message in a request queue.

•

The Integration WAM Provider BPEL process performs the following:

•

Consumes the EBO message.

•

Transforms the message to Oracle Utilities Work and Asset Management format and applies the DVMs if needed.

•

Invokes Oracle Utilities Work and Asset Management inbound service.

Enterprise Resource Planning System Initiated Response Process

The response process includes:

•

Integration WAM response requestor process

•

Custom implementation process

Response processing is completed as described below:

•

Oracle Utilities Work and Asset Management system invokes the Integration WAM Response Requestor BPEL Web Service to send the response message. Message received by the service is in Oracle Utilities Work and Asset Management schema format.

•

The Integration WAM Response Requestor BPEL process can perform the following:

•

Transforms the message to EBO format and applies the DVMs if needed.

•

Posts the EBO message to a queue.

•

The Custom Implementation process should perform the following (Optional):

•

Consume the message in EBO format from the response queue.

•

Transforms the data from EBO format to ERP format.

•

Pass the message to the ERP system for processing.

Oracle Utilities Work and Asset Management Initiated Messages

This section describes technical processing when Oracle Utilities Work and Asset Management generates the request data and calls the integration web service. The following diagram provides a visual representation of this processing:

Oracle Utilities Work and Asset Management Initiated Message Process

Oracle Utilities Work and Asset Management Initiated Request Process

The request process includes:

•

Integration WAM requestor process

•

Custom implementation process

Response processing is completed as described below:

•

The Oracle Utilities Work and Asset Management system invokes an Integration WAM Requestor BPEL Web Service to send the message.

•

The message sent to the service is in Oracle Utilities Work and Asset

•

Management schema format.

•

The Integration WAM Requestor BPEL process performs the following:

•

Transforms the message to EBO format and applies DVM's if needed.

•

Posts the EBO message in a queue.

•

The Custom Implementation process should perform the following:

•

Consume the message in EBO format from the request queue.

•

Transforms the data from EBO format to ERP format.

•

Pass the message to the ERP system for processing.

Oracle Utilities Work and Asset Management Initiated Response Process

The response process has:

•

Custom implementation process

•

Integration ERP Response Requestor process

•

Integration WAM Response Provider process

Response processing is completed as described below.

•

The Custom Implementation process should perform the following:

•

Receives the message sent by the Enterprise Resource Planning system in the object's ERP schema format.

•

Creates the response message in the EBO format; transforms the data from ERP format to EBO format.

•

Invokes the Integration ERP Response Requestor BPEL Web Service to send the message. The BPEL process will insert the message into a JMS queue to allow for guaranteed delivery. Alternatively, implementations can insert directly to this JMS queue.

•

The Integration ERP Response Requestor BPEL process performs the following:

•

Receive the message in EBO format sent by the custom implementation process.

•

Insert the EBO message in a response queue.

•

The Integration WAM Response Provider BPEL process performs the following:

•

Consumes the EBO message.

•

Transforms the message to Oracle Utilities Work and Asset Management format and applies the DVMs if needed.

•

Invokes Oracle Utilities Work and Asset Management inbound service.

Integration Processes

This section provides overviews of the business processes facilitated by this integration. The integration supports the following business models:

•

Model 1 - Oracle Utilities Work and Asset Management Supply Chain Business Model

•

Model 2 - Enterprise Resource Planning System Supply Chain Business Model (ESC)

The integration points used for both business models can be either Enterprise Resource Planning Initiated or Oracle Utilities Work and Asset Management Initiated.

•

Enterprise Resource Planning Initiated Processes

•

Oracle Utilities Work and Asset Management Initiated Processes

Please refer to Appendix A : Data Mapping for detailed integration mapping information.

Enterprise Resource Planning Initiated Processes

This section provides information on processing when processing is initiated from Enterprise Resource Planning, including:

•

High Level Processing Overview

•

Integration Points

High Level Processing Overview

The following diagrams show the integration processes from Enterprise Resource Planning to Oracle Utilities Work and Asset Management.

Enterprise Resource Planning to Oracle Utilities Work and Asset Management Master Data Synchronization Processes

Enterprise Resource Planning to Oracle Utilities Work and Asset Management Transactional Processes

Integration Points

The following integration points are Enterprise Resource Planning initiated:

#

Integration Point

Process Type

Comments

1

Worker (Employee) Synchronization Process

Master Data Sync

•

Employee information sync

•

Worker EBO used for transformation.

2

Supplier Party (Vendor/Vendor Location) Synchronization Process (ERP to WAM)

Master Data Sync

•

Vendor and Vendor location information sync

•

Supplier Party EBO used for transformation.

3

Chart of Accounts (Cost Center) Synchronization Process

Master Data Sync

•

Chart of Accounts sent from the ERP system

•

Chart of Accounts EBO used for transformation.

•

Oracle Utilities Work and Asset Management stores cost center information.

4

Stock Item Synchronization Process

Master Data Sync

•

Stock Item information sync

•

Item EBO used for transformation.

5

Storeroom Item (Stock Item Detail) Synchronization Process

Master Data Sync

•

Stock Item details/Storeroom sync

•

Item EBO used for transformation.

6

Item Balance (Stock Transaction) Synchronization Process

Transactional

•

Stock Transaction sent from the ERP system

•

Item Balance EBO used for transformation.

7

Blanket Contract (Purchase Agreement) Synchronization Process

Transactional

•

Blanket contracts information from the ERP system.

•

Blanket Purchase Agreement EBO used for transformation.

8

Purchase Order Synchronization Process

Transactional

•

Purchase Order and Change Order sent from the ERP system

•

Purchase Order EBO used for transformation

•

Oracle Utilities Work and Asset Management stores Purchase Order information.

9

Shipment Receipt (Purchase Receipt) Synchronization Process

Transactional

•

Purchase Receipt Information from the ERP system.

•

Shipment Receipt EBO used for transformation.

10

Purchase Return - Inventory Transaction Synchronization Process

Transactional

•

Purchase Return Information from the ERP system.

•

Inventory Transaction EBO used for transformation.

11

Material Issue - Inventory Transaction Synchronization Process

Transactional

•

Material Issue or Checkout Information from the ERP system.

•

Inventory Transaction EBO used for transformation.

12

Material Return - Inventory Transaction Synchronization Process

Transactional

•

Material Return Information from the ERP system.

•

Inventory Transaction EBO used for transformation.

13

Invoice Synchronization Process

Transactional

•

Invoice information from the ERP system.

•

Invoice EBO used for transformation.

14

Invoice Payment (Disbursement) Synchronization Process

Transactional

•

Invoice Payment information sent from the ERP system.

•

Disbursed Payment EBO used for transformation.

15

GL Transaction (Accounting Entry) Synchronization Process

Transactional

•

GL Transaction information sync from the ERP system to WAM Accounting Entry EBO used for transformation.

Worker (Employee) Synchronization Process

The Worker process is a master data sync process triggered from the Enterprise Resource Planning system.

Refer to the Worker (Employee) Synchronization Process Mapping Details section for data mapping information for this integration point.

The following diagram provides a graphical representation of this processing:

Worker (Employee) Business Process Diagram

Worker (Employee) Processing Details

This process is triggered on create/update of Employee information in the Enterprise Resource Planning system.

•

The Enterprise Resource Planning system sends employee information to the integration in ERP format.

•

A custom implementation connector can be developed to integrate with the ERP system to transform information into a message using the Worker EBO format and invoke the requestor process to publish to the Worker request queue.

•

The WAM-ERP connector consumes this message, transforms it from EBO to Oracle Utilities Work and Asset Management format and invokes the inbound web service in Oracle Utilities Work and Asset Management.

•

Oracle Utilities Work and Asset Management processes this message and sends a response.

•

The integration response requestor transforms this message from Oracle Utilities Work and Asset Management format to Worker EBO format and adds it to the Worker response queue.

•

A custom implementation connector transforms the response and integrates with the ERP system.

Worker (Employee) Process WAM and ERP System Services

Requestor ABCS

Provider ABCS

Enterpr ise Resource Planning Specific Integration Services

SyncWorkerERPReqABCSImpl

n/a

Oracle Utilities Work and Asset Management Specific Integration Services

SyncWorkerRespOUWAMUtilitiesReqABCSImpl

SyncWorkerOUWAMUtilitiesProvABCSImpl

Worker (Employee) Process Adapter Services

Name

Description

SyncWorkerERPJMSProducer

This adapter is used by SyncWorkerERPReqABCSImpl to write the EBO message coming from the Enterprise Resource Planning system to the Worker queue.

SyncWorkerOUWAMUtilitiesJMSConsumer

This adapter is used by the SyncWorkerOUWAMUtilitiesProvABCSImpl process to consume EBO message from the Worker queue.

SyncWorkerRespOUWAMUtilitiesJMSProducer

This adapter is used by SyncWorkerRespOUWAMUtilitiesReqABCSImpl to write the EBO message coming from Oracle Utilities Work and Asset Management to the Worker response queue.

Worker (Employee) Process EBO and EBM Details

EBO

EBM

Worker EBO

SyncWorkerListEBM

SyncWorkerListResponseEBM

Worker (Employee) Process JMS Queue Details

Queue Name

JNDI Name

Description

OUWAMERP

WorkerRequest

jms/OUWAMERP

WorkerRequest

Used to store Enterprise Resource Planning system Worker sync request.

OUWAMERP

WorkerResponse

jms/OUWAMERP

WorkerResponse

Used to store Oracle Utilities Work and Asset Management Worker sync response.

OUWAMERP

WorkerRequestError

jms/OUWAMERP

WorkerRequestError

Corresponding Error Queue For Enterprise Resource Planning system Worker sync request queue.

OUWAMERP

WorkerResponseError

jms/OUWAMERP

WorkerResponse

Error

Corresponding Error Queue Oracle Utilities Work and Asset Management Worker response queue.

Worker (Employee) Process External Web Service Call

Application

Inbound Web Service

Description

WAM

W1-SyncRequestInbound

The Sync Request inbound service used for Master Data Sync in WAM.

Supplier Party (Vendor/Vendor Location) Synchronization Process (ERP to WAM)

The Supplier Party process is a master data sync process triggered from the Enterprise Resource Planning system. This process is only used with Model 2 - ESC.

Note : There is another Supplier Party process triggered from Oracle Utilities Work and Asset Management which is only used with Model 1 - WSC.

Refer to the Supplier Party (Vendor/Vendor Location) Synchronization Process Mapping Details section for data mapping information for this integration point.

The following diagram provides a graphical representation of this processing:

Supplier Party Business Process Diagram

Supplier Party (Vendor/Vendor Location) Processing Details

This process is triggered on create/update of Vendor and/or Vendor Location information in the Enterprise Resource Planning system.

•

The Enterprise Resource Planning system sends vendor location information to the integration in ERP format.

•

A custom implementation connector can be developed to integrate with the ERP system to transform information into a message using the Supplier Party EBO format and invoke the requestor process to publish to the Supplier Party request queue.

•

The WAM-ERP connector consumes this message, transforms it from EBO to Oracle Utilities Work and Asset Management format, and invokes the inbound web service in Oracle Utilities Work and Asset Management.

•

Oracle Utilities Work and Asset Management processes this message and sends a response.

•

The integration response requestor transforms this message from Oracle Utilities Work and Asset Management format to Supplier Party EBO format and adds it to the Supplier Party response queue.

•

A custom implementation connector transforms the response and integrates with the ERP system.

Supplier Party (Vendor/Vendor Location) Process WAM and ERP System Services

Requestor ABCS

Provider ABCS

Enterpr ise Resource Planning Specific Integration Service

SyncSupplierPartyERPReqABCSImpl

n/a

Oracle Utilities Work and Asset Management Specific Integration Services

SyncSupplierPartyRespOUWAMUtilitiesReqABCSImpl

SyncSupplierPartyOUWA MUtilitiesProvABCSImpl

Supplier Party (Vendor/Vendor Location) Process Adapter Services

Name

Description

SyncSupplierPartyERPJMSProducer

This adapter is used by SyncSupplierPartyERPReqABCSImpl to write the EBO message coming from the Enterprise Resource Planning system to the Supplier Party queue.

SyncSupplierPartyOUWAMUtilitiesJMSConsumer

This adapter is used by the SyncSupplierPartyOUWAMUtilitiesProvABCSImpl process to consume EBO message from Supplier Party queue.

SyncSupplierPartyespOUWAMUtilitiesJMSProducer

This adapter is used by SyncSupplierPartyRespOUWAMUtilitiesReqABCSImpl to write the EBO message coming from Oracle Utilities Work and Asset Management to the Supplier Party response queue.

Supplier Party (Vendor/Vendor Location) Process EBO and EBM Details

EBO

EBM

Supplier Party EBO

SyncSupplierPartyListEBM

SyncSupplierPartyListResponseEBM

Supplier Party (Vendor/Vendor Location) Process JMS Queue Details

Queue Name

JNDI Name

Description

OUWAMERPSupplierPartyRequest

jms/OUWAMERPSupplierPartyRequest

Used to store Enterprise Resource Planning system Supplier party sync.

OUWAMERPSupplierPartyResponse

jms/OUWAMERPSupplierPartyResponse

Used to store Oracle Utilities Work and Asset Management Supplier Party sync response.

OUWAMERPSupplierPartyRequestError

jms/OUWAMERPSupplierPart yRequestError

Corresponding Error Queue For Enterprise For Resource Planning system Supplier party request queue.

OUWAMERPSupplierPartyResponseError

jms/OUWAMERPSupplierPart yResponseError

Corresponding Error Queue For Oracle Utilities Work and Asset Management Supplier Party response queue.

Supplier Party (Vendor/Vendor Location) Process External Web Service Call

Application

Inbound Web Service

Description

WAM

W1-SyncRequestInbound

The Sync Request inbound service used for Master Data Sync in WAM.

Chart of Accounts (Cost Center) Synchronization Process

The Chart of Accounts process is a master data sync process triggered from the Enterprise Resource Planning system.

Refer to the Chart of Accounts (Cost Center) Synchronization Process Mapping Details section for data mapping information for this integration point.

The following diagram provides a graphical representation of this processing:

Chart of Accounts (Cost Center) Business Process Diagram

Chart of Accounts (Cost Center) Processing Details

This process is triggered on create/update of Chart of Accounts information in the Enterprise Resource Planning system.

•

The Enterprise Resource Planning system sends Chart of Accounts information to the integration in ERP format.

•

A custom implementation connector can be developed to integrate with the ERP system to transform information into a message using the Chart of Accounts EBO format and invoke the requestor process to publish to the Chart of Accounts request queue.

•

The WAM-ERP connector consumes this message, transforms it from EBO to Oracle Utilities Work and Asset Management format and invokes the inbound web service in Oracle Utilities Work and Asset Management.

•

Oracle Utilities Work and Asset Management processes this message and sends a response.

•

The integration response requestor transforms this message from Oracle Utilities Work and Asset Management format to the Chart of Accounts EBO format and adds it to the Chart of Accounts response queue.

•

A custom implementation connector transforms the response and integrates with the ERP system.

Chart of Accounts (Cost Center) Process WAM and ERP System Services

Requestor ABCS

Provider ABCS

Enterpr ise Resource Planning Specific Integration Service

SyncChartOfAccountsERPReqABCSImpl

n/a

Oracle Utilities Work and Asset Management Specific Integration Services

SyncChartOfAccountsRespOUWAMUtilitiesReqABCSImpl

SyncChartofAccountsOUWAMUtilitiesProvABCSImpl

Chart of Accounts (Cost Center) Process Adapter Services

Name

Description

SyncChartOfAccountsERPJMSProducer

This adapter is used by SyncChartOfAccountsERPReqABCSImpl to write the EBO message coming from the Enterprise Resource Planning system to the Chart of Accounts queue.

SyncChartOfAccountsOUWAMUtilitiesJMSConsumer

This adapter is used by the SyncChartOfAccountsOUWAMUtilitiesProvABCSImpl process to consume EBO message from Chart of Accounts.

SyncChartOfAccountsRespOUWAMUtilitiesJMSProducer

This adapter is used by SyncChartOfAccountsRespOUWAMUtilitiesReqABCSImpl to write the EBO message coming from Oracle Utilities Work and Asset Management to the Chart of Accounts response queue.

Chart of Accounts (Cost Center) Process EBO and EBM Details

EBO

EBM

Chart of Accounts EBO

SyncChartOfAccountsListEBM

SyncChartOfAccountsListResponseEBM

Chart of Accounts (Cost Center) Process JMS Queue Details

Queue Name

JNDI Name

Description

OUWAMERPChartOfAccountsRequest

jms/OUWAMERPChartOfAccountsRequest

Used to store Enterprise Resource Planning system Chart of accounts sync request.

OUWAMERPChartOfAccountsResponse

jms/OUWAMERPChartOfAccountsResponse

Used to store Oracle Utilities Work and Asset Management Chart of Accounts sync response.

OUWAMERPChartOfAccountsRequestError

jms/OUWAMERPChartOfAcc ountsRequestError

Corresponding Error Queue For Enterprise Resource Planning system Chart of accounts request queue.

OUWAMERPChartOfAccountsResponseError

jms/OUWAMERPChartOfAcc ountsResponseError

Corresponding Error Queue For Oracle Utilities Work and Asset Management Chart of Accounts response queue.

Chart of Accounts (Cost Center) Process External Web Service Call

Application

Inbound Web Service

Description

WAM

W1-SyncRequestInbound

The sync request inbound service used for Master Data Sync in WAM.

Stock Item Synchronization Process

The Stock Item process is a master data sync process triggered from the Enterprise Resource Planning system.

Refer to the Stock Item Synchronization Process Mapping Details section for data mapping information for this integration point.

The following diagram provides a graphical representation of this processing:

Stock Item Business Process Diagram

Stock Item Processing Details

This process is triggered on create/update of Stock Item information in the Enterprise Resource Planning system.

•

The Enterprise Resource Planning system sends Master Item information to the integration ERP format.

•

A custom implementation connector can be developed to integrate with the ERP system to transform information into a message using the Stock Item EBO format and invoke the requestor process to publish to the Stock Item request queue.

•

The WAM-ERP connector consumes this message, transforms it from EBO to Oracle Utilities Work and Asset Management format and invokes inbound web service in Oracle Utilities Work and Asset Management.

•

Oracle Utilities Work and Asset Management processes this message and sends a response.

•

The integration response requestor transforms this message from Oracle Utilities Work and Asset Management format to Stock Item EBO format and adds it to the Stock Item response queue.

•

A custom implementation connector transforms this response and integrates with the ERP system.

Stock Item Process WAM and ERP System Services

Requestor ABCS

Provider ABCS

Enterpr ise Resource Planning Specific Integration Service

SyncStockItemERPReqABCSImpl

n/a

Oracle Utilities Work and Asset Management Specific Integration Services

SyncStockItemRespOUWAMUtilitiesReqABCSImpl

SyncStockItemOUWAMUtilitiesProvABCSImpl

Stock Item Process Adapter Services

Name

Description

SyncStockItemERPJMSProducer

This adapter is used by SyncStockItemERPReqABCSImpl to write the EBO message coming from the ERP system to the Item queue.

SyncStockItemOUWAMUtilitiesJMSConsumer

This adapter is used by the SyncStockItemOUWAMUtilitiesProvABCSImpl process to consume EBO message from the Stock Item queue.

SyncStockItemRespOUWAMUtilitiesJMSProducer

This adapter is used by SyncStockItemRespOUWAMUtilitiesReqABCSImpl to write the EBO message coming from WAM to the Stock Item response queue.

Stock Item Process EBO and EBM Details

EBO

EBM

Item EBO

SyncItemListEBM

SyncItemListResponseEBM

Stock Item Process JMS Queue Details

Queue Name

JNDI Name

Description

OUWAMERPStockItem

Request

jms/OUWAMERPStockItem

Request

Used to store Enterprise Resource Planning system Stock Item sync request.

OUWAMERPStockItem

Response

jms/OUWAMERPStockItem

Response

Used to store Oracle Utilities Work and Asset Management Stock Item sync response.

OUWAMERPStockItem

RequestError

jms/OUWAMERPStockItem

RequestError

Corresponding Error Queue For Enterprise For Resource Planning system Stock Item request queue.

OUWAMERPStockItem

ResponseError

jms/OUWAMERPStockItem

ResponseError

Corresponding Error Queue For Oracle Utilities Work and Asset Management Stock Item response queue.

Stock Item Process External Web Service Call

Application

Inbound Web Service

Description

WAM

W1-SyncRequestInbound

The sync request inbound service used for Master Data Sync in WAM.

Storeroom Item (Stock Item Detail) Synchronization Process

The Storeroom Item process is a master data sync process triggered from the Enterprise Resource Planning system.

Refer to the Storeroom Item (Stock Item Detail) Synchronization Process Mapping Details section for data mapping information for this integration point.

The following diagram provides a graphical representation of this processing:

Storeroom Item (Stock Item Detail) Business Process Diagram

Storeroom Item (Stock Item Detail) Processing Details

This process is triggered on create/update of Storeroom Item information in the Enterprise Resource Planning system.

•

The Enterprise Resource Planning system sends Storeroom information to the integration in ERP format.

•

A custom implementation connector can be developed to integrate with the ERP system to transform information into a message using the Storeroom Item EBO format and invoke the requestor process to publish to the Storeroom Item request queue.

•

The WAM-ERP connector consumes this message, transforms it from EBO to Oracle Utilities Work and Asset Management format and invokes inbound web service in Oracle Utilities Work and Asset Management.

•

Oracle Utilities Work and Asset Management processes this message and sends a response.

•

The integration response requestor transforms this message from Oracle Utilities Work and Asset Management format to the Storeroom Item EBO format and adds it to the Storeroom Item response queue.

•

A custom implementation connector transforms this response and integrates with the ERP system.

Storeroom Item (Stock Item Detail) Process WAM and ERP System Services

Requestor ABCS

Provider ABCS

Enterpr ise Resource Planning Specific Integration Service

SyncStoreroomItemERPReqABCSImpl

n/a

Oracle Utilities Work and Asset Management Specific Integration Services

SyncStoreroomItemRespOUWAMUtilitiesReqABCSImpl

SyncStoreroomItemOUWAMUtilitiesProvABCSImpl

Storeroom Item (Stock Item Detail) Process Adapter Services

Name

Description

SyncStoreroomItemERPJMSProducer

This adapter is used by SyncStoreroomItemERPReqABCSImpl to write the EBO message coming from the ERP system to the Storeroom Item queue.

SyncStoreroomItemOUWAMUtilitiesJMSConsumer

This adapter is used by the SyncStoreroomItemOUWAMUtilitiesProvABCSImpl process to consume EBO message from StoreroomItem queue.

SyncStoreroomItemRespOUWAMUtilitiesJMSProducer

This adapter is used by SyncStoreroomItemRespOUWAMUtilitiesReqABCSImpl to write the EBO message coming from WAM to the Storeroom Item response queue.

Storeroom Item (Stock Item Detail) Process EBO and EBM Details

EBO

EBM

Storeroom Item EBO

SyncItemListEBM

SyncItemListResponseEBM

Storeroom Item (Stock Item Detail) Process JMS Queue Details

Queue Name

JNDI Name

Description

OUWAMERPStoreroom

ItemRequest

jms/OUWAMERPStoreroom

ItemRequest

Used to store Enterprise Resource Planning system Storeroom Item sync request.

OUWAMERPStoreroom

ItemResponse

jms/OUWAMERPStoreroom

ItemResponse

Used to store Oracle Utilities Work and Asset Management Storeroom Item sync response.

OUWAMERPStoreroom

ItemRequestError

jms/OUWAMERPStoreroom

ItemRequestError

Corresponding Error Queue For Enterprise For Resource Planning system Storeroom Item request queue.

OUWAMERPStoreroom

ItemResponseError

jms/OUWAMERPStoreroom

ItemResponseError

Corresponding Error Queue For Oracle Utilities Work and Asset Management Storeroom Item response queue.

Storeroom Item (Stock Item Detail) Process External Web Service Call

Application

Inbound Web Service

Description

WAM

W1-SyncRequestInbound

The sync request inbound service used for Master Data Sync in WAM.

Item Balance (Stock Transaction) Synchronization Process

The Item Balance process is a transactional sync process triggered from the Enterprise Resource Planning system.

Refer to the Item Balance (Stock Transaction) Synchronization Process Mapping Details section for data mapping information for this integration point.

The following diagram provides a graphical representation of this processing:

Item Balance Business Process Diagram

Item Balance Processing Details

This process is triggered whenever the storeroom inventory is updated in the Enterprise Resource Planning system. Storeroom inventory is updated during purchase receipt, purchase return, material issue and material return.

•

The Enterprise Resource Planning system sends Item Balance information to the integration in ERP format.

•

A custom implementation connector can be developed to integrate with the ERP system to transform information into a message using the Item Balance EBO format and invoke the requestor process to publish to the Item Balance request queue.

•

The WAM-ERP connector consumes this message, transforms it from EBO to Oracle Utilities Work and Asset Management format and invokes inbound web service in Oracle Utilities Work and Asset Management.

•

Oracle Utilities Work and Asset Management processes this message and sends a response.

•

The integration response requestor transforms this message from Oracle Utilities Work and Asset Management format to Item Balance EBO format and adds it to the Item Balance response queue.

•

A custom implementation connector transforms this response and integrates with the ERP system.

Item Balance Process WAM and ERP System Services

Requestor ABCS

Provider ABCS

Enterpr ise Resource Planning Specific Integration Service

SyncItemBalanceERPReqABCSImpl

n/a

Oracle Utilities Work and Asset Management Specific Integration Services

SyncItemBalanceRespOUWAMUtilities

ReqABCSImpl

SyncItemBalanceOUWAMUtilitiesProvABCSImpl

Item Balance Process Adapter Services

Name

Description

SyncItemBalanceERP

JMSProducer

This adapter is used by SyncItemBalanceERPReqABCSImpl to write the EBO message coming from the ERP system to the Item Balance request queue.

SyncItemBalanceItemOUWAMUtilities

JMSConsumer

This adapter is used by the SyncItemBalanceOUWAMUtilitiesProvABCSImpl process to consume EBO message from Item Balance request queue.

SyncItemBalanceItemRespOUWAMUtilities

JMSProducer

This adapter is used by SyncItem BalanceRespOUWAMUtilitiesReqABCSImpl to write the EBO message coming from WAM to the Item Balance response queue.

Item Balance Process EBO and EBM Details

EBO

EBM

Item Balance EBO

SyncItemBalanceListEBM

SyncItemBalanceListResponseEBM

Item Balance Process JMS Queue Details

Queue Name

JNDI Name

Description

OUWAMERPItem

BalanceRequest

jms/OUWAMERPItem

BalanceRequest

Used to store Enterprise Resource Planning system Item Balance sync request.

OUWAMERPItem

BalanceResponse

jms/OUWAMERPItem

BalanceResponse

Used to store Oracle Utilities Work and Asset Management Item Balance sync response

OUWAMERPItem

BalanceRequestError

jms/

OUWAMERPItem

BalanceRequestError

Corresponding Error Queue For Enterprise For Resource Planning system Item Balance request queue.

OUWAMERPItem

BalanceResponseError

jms/OUWAMERPItem

BalanceResponseError

Corresponding Error Queue For Oracle Utilities Work and Asset Management Item Balance response queue.

Item Balance Process External Web Service Call

Application

Inbound Web Service

Description

WAM

W1-StockTransIntegInbound

The Stock Transaction inbound integration web service in WAM.

Blanket Contract (Purchase Agreement) Synchronization Process

The Blanket Contract (Purchase Agreement) process is a transactional sync process triggered from the Enterprise Resource Planning system.

Refer to the Blanket Contract (Purchase Agreement) Synchronization Process Mapping Details section for data mapping information for this integration point.

The following diagram provides a graphical representation of this processing:

Blanket Contract (Purchase Agreement) Business Process Diagram

Blanket Contract (Purchase Agreement) Processing Details

This process is triggered when the Blanket Purchase Agreement is approved in the Enterprise Resource Planning system.

•

The Enterprise Resource Planning system sends Blanket Purchase Agreement information to the integration in ERP format.

•

A custom implementation connector can be developed to integrate with the ERP system to transform information into a message using the Blanket Purchase Agreement EBO format and invoke the requestor process to publish to the Blanket Purchase Agreement request queue.

•

The WAM-ERP connector consumes this message, transforms it from EBO to Oracle Utilities Work and Asset Management format and invokes inbound web service in Oracle Utilities Work and Asset Management.

•

Oracle Utilities Work and Asset Management processes this message and sends a response.

•

The integration response requestor transforms this message from Oracle Utilities Work and Asset Management format to Blanket Purchase Agreement EBO format and adds it to the Blanket Purchase Agreement response queue.

•

A custom implementation connector transforms the response and integrates with the ERP system.

Blanket Contract (Purchase Agreement) Process WAM and ERP System Services

Requestor ABCS

Provider ABCS

Enterpr ise Resource Planning Specific Integration Service

SyncBlanketPurchaseAgreementERP

ReqABCSImpl

n/a

Oracle Utilities Work and Asset Management Specific Integration Services

SyncBlanketPurchaseAgreementRespOUWAM

UtilitiesReqABCSImpl

SyncBlanketPurchaseAgreementOUWAMUtilitiesProvABCSImpl

Blanket Contract (Purchase Agreement) Process Adapter Services

Name

Description

SyncBlanketPurchaseAgreement

ERPJMSProducer

This adapter is used by SyncBlanketPurchaseAgreementERPReqABCSImpl to write the EBO message coming from the ERP system to the Blanket Purchase Agreement queue.

SyncBlanketPurchaseAgreement

OUWAMUtilitiesJMSConsumer

This adapter is used by the SyncBlanketPurchaseAgreementOUWAMUtilitiesProvABCSImpl process to consume EBO message from Blanket Purchase Agreement queue.

SyncBlanketPurchaseAgreement

RespOUWAMUtilitiesJMSProducer

This adapter is used by SyncBlanketPurchaseAgreementRespOUWAMUtilitiesReqABCSImpl to write the EBO message coming from WAM to the Receipt Inventory Transaction response queue.

Blanket Contract (Purchase Agreement) Process EBO and EBM Details

EBO

EBM

Blanket Purchase Agreement EBO

SyncBlanketPurchaseAgreementListEBM

SyncBlanketPurchaseAgreementListResponseEBM

Blanket Contract (Purchase Agreement) Process JMS Queue Details

Queue Name

JNDI Name

Description

OUWAMERPBlanket

PurchaseAgreementRequest

jms/OUWAMERPBlanket

PurchaseAgreementRequest

Used to store Enterprise Resource Planning system Blanket Purchase Agreement sync request.

OUWAMERPBlanket

PurchaseAgreementResponse

jms/OUWAMERPBlanket

PurchaseAgreementResponse

Used to store Oracle Utilities Work and Asset Management Blanket Purchase Agreement sync response.

OUWAMERPBlanket

PurchaseAgreementRequestError

jms/OUWAMERPBlanket

PurchaseAgreementRequestError

Corresponding Error Queue For Enterprise For Resource Planning Blanket Purchase Agreement request queue.

OUWAMERPBlanket

PurchaseAgreementResponseError

jms/OUWAMERPBlanket

PurchaseAgreementResponseError

Corresponding Error Queue For Oracle Utilities Work and Asset Management Blanket Purchase Agreement response queue.

Blanket Contract (Purchase Agreement) Process External Web Service Call

Application

Inbound Web Service

Description

WAM

W1-BlanketContractIntegInbound

The Blanket Contract inbound integration web service in WAM.

Purchase Order Synchronization Process

The Purchase Order process is a transactional sync process triggered from the Enterprise Resource Planning system.

Refer to the Purchase Order Synchronization Process Mapping Details section for data mapping information for this integration point.

The following diagram provides a graphical representation of this processing:

Purchase Order Business Process Diagram

Purchase Order Processing Details

This process is triggered when the Purchase Order (PO) is in the ‘ Approved ’ or ‘Issued’ status or when the PO is in ‘ Closed’ status in the Enterprise Resource Planning system.

•

The Enterprise Resource Planning system sends Purchase Order information to the integration in ERP format.

•

A custom implementation connector can be developed to integrate with the ERP system and transform information into a message using the Purchase Order EBO format and invoke the requestor process to publish to the Purchase Order request queue.

•

The WAM-ERP connector consumes this message, transforms it from EBO to Oracle Utilities Work and Asset Management format and invokes inbound web service in Oracle Utilities Work and Asset Management.

•

Oracle Utilities Work and Asset Management processes this message and sends a response.

•

The integration response requestor transforms this message from Oracle Utilities Work and Asset Management format to the Purchase Order EBO format and adds it to the Purchase Order response queue.

•

A custom implementation connector transforms this response and integrates with the ERP system.When the Enterprise Resource Planning system updates a PO, most of the time, it creates a new PO record with the same PO Number with a new revision number. This new updated PO record will be in ‘Pending Approval’ status. Once this updated PO record is ‘Approved’, it will be sent to Oracle Utilities Work and Asset Management. Some minor updates, like description changes, in the Enterprise Resource Planning system do not create a new PO record. These changes are sent to Oracle Utilities Work and Asset Management using the same PO record’s PO Number and revision number.When Oracle Utilities Work and Asset Management processes the PO record coming from the Enterprise Resource Planning system, it has to first validate if that PO Number exists in Oracle Utilities Work and Asset Management. Based on validation the Oracle Utilities Work and Asset Management system completes the following:

•

If the PO Number does not exist, it will create that PO in Oracle Utilities Work and Asset Management.

•

If the PO Number exists in Oracle Utilities Work and Asset Management, the system validates the revision number.

•

If the Revision number in Oracle Utilities Work and Asset Management and in the PO request message are the same, updates the PO record in Oracle Utilities Work and Asset Management.

•

If the Revision number in Oracle Utilities Work and Asset Management is different from the revision number of the PO request message, creates a new PO record using the data in the PO request message and changes the status of the old PO in Oracle Utilities Work and Asset Management to ‘Closed’. Note: Different Enterprise Resource Planning systems may vary in processing their PO.

Purchase Order Process WAM and ERP System Services

Requestor ABCS

Provider ABCS

Enterpr ise Resource Planning Specific Integration Service

SyncPurchaseOrderERPReqABCSImpl

n/a

Oracle Utilities Work and Asset Management Specific Integration Services

SyncPurchase OrderRespOUWAMUtilitiesReqABCSImpl

SyncPurchaseOrderOUWAMUtilitiesProvABCSImpl

Purchase Order Process Adapter Services

Name

Description

SyncPurchaseOrderERP

JMSProducer

This adapter is used by SyncPurchaseOrderERPReqABCSImpl to write the EBO message coming from the ERP system to the Purchase Order request queue.

SyncPurchaseOrderOUWAMUtilities

JMSConsumer

This adapter is used by the SyncPurchaseOrderOUWAMUtilitiesProvABCSImpl process to consume EBO message from Purchase Order request queue.

SyncPurchaseOrderRespOUWAMUtilities

JMSProducer

This adapter is used by SyncPurchaseOrderRespOUWAMUtilitiesReqABCSImpl to write the EBO message coming from WAM to the Purchase Order response queue.

Purchase Order Process EBO and EBM Details

EBO

EBM

Purchase Order EBO

SyncPurchaseOrderListEBM

SyncPurchaseOrderListResponseEBM

Purchase Order Process JMS Queue Details

Queue Name

JNDI Name

Description

OUWAMERPPurchaseOrder

Request

jms/OUWAMERPPurchaseOrder

Request

Used to store Enterprise Resource Planning system Purchase Order sync request

OUWAMERPPurchaseOrder

Response

jms/OUWAMERPPurchase

Orde Response

Used to store Oracle Utilities Work and Asset Management Purchase Order sync response

OUWAMERPPurchaseOrder

RequestError

jms/OUWAMERPPurchaseOrder

RequestError

Corresponding Error Queue For Enterprise For Resource Planning system Purchase Order request queue.

OUWAMERPPurchase

ResponseError

jms/OUWAMERPPurchaseOrde

ResponseError

Corresponding Error Queue For Oracle Utilities Work and Asset Management Purchase Order response queue.

Purchase Order Process External Web Service Call

Application

Inbound Web Service

Description

WAM

W1-PurchaseOrderIntegInbound

The Purchase Order inbound integration web service in WAM.

Shipment Receipt (Purchase Receipt) Synchronization Process

The Shipment Receipt process is a transactional sync process triggered from the Enterprise Resource Planning system.

Refer to the Shipment Receipt (Purchase Receipt) Synchronization Process Mapping Details section for data mapping information for this integration point.

The following diagram provides a graphical representation of this processing:

Shipment Receipt Business Process Diagram

Shipment Receipt Processing Details

This process is triggered when the Receipt of a Purchase Order (PO) is in the ‘ Completed ’ status in the Enterprise Resource Planning system.

•

The Enterprise Resource Planning system sends Purchase Receipt information to the integration in ERP format.

•

A custom implementation connector can be developed to integrate with the ERP system to transform information into a message using the Shipment Receipt EBO format and invoke the requestor process to publish to the Shipment Receipt request queue.

•

The WAM-ERP connector consumes this message, transforms it from EBO to Oracle Utilities Work and Asset Management format and invokes inbound web service in Oracle Utilities Work and Asset Management.

•

Oracle Utilities Work and Asset Management processes this message and sends a response.

•

The integration response requestor transforms this message from Oracle Utilities Work and Asset Management format to Shipment Receipt EBO format and adds it to the Shipment Receipt response queue.

•

A custom implementation connector transforms the response and integrates with the ERP system.

Shipment Receipt Process WAM and ERP System Services

Requestor ABCS

Provider ABCS

Enterpr ise Resource Planning Specific Integration Service

SyncShipmentReceiptERPReqABCSImpl

n/a

Oracle Utilities Work and Asset Management Specific Integration Services

SyncShipmentReceiptRespOUWAMUtilitiesReqABCSImpl

SyncShipmentReceiptOUWAMUtilitiesProvABCSImpl

Shipment Receipt Process Adapter Services

Name

Description

SyncShipmentReceiptERPJMSProducer

This adapter is used by SyncShipment ReceiptERPReqABCSImpl to write the EBO message coming from the ERP system to the Shipment Receipt request queue.

SyncShipmentReceiptOUWAM

UtilitiesJMSConsumer

This adapter is used by the SyncReceiptInvTransOUWAMUtilitiesProvABCSImpl process to consume EBO message from Shipment Receipt request queue.

SyncShipmentReceiptRespOUWAM

UtilitiesJMSProducer

This adapter is used by SyncReceiptInvTransRespOUWAMUtilitiesReqABCSImpl to write the EBO message coming from WAM to the Shipment Receipt response queue.

Shipment Receipt Process EBO and EBM Details

EBO

EBM

Shipment Receipt EBO

SyncShipment ReceiptListEBM

SyncShipmentReceiptListResponseEBM

Shipment Receipt Process JMS Queue Details

Queue Name

JNDI Name

Description

OUWAMERP

ShipmenReceiptRequest

j ms/OUWAMERP

ShipmenReceiptRequest

Used to store Enterprise Resource Planning system Shipment Receipt sync request

OUWAMERP

ShipmenReceiptResponse

jms/OUWAMERP

ShipmenReceiptResponse

Used to store Oracle Utilities Work and Asset Shipment Receipt sync response

OUWAMERP

ShipmenReceiptRequestError

jms/

OUWAMERP

ShipmenReceiptRequestError

Corresponding Error Queue For Enterprise For Resource Planning system Shipment Receipt request queue.

OUWAMERP

ShipmenReceiptResponseError

jms/OUWAMERP

ShipmenReceiptResponseError

Corresponding Error Queue For Oracle Utilities Work and Asset Management Shipment Receipt response queue.

Shipment Receipt Process External Web Service Call

Application

Inbound Web Service

Description

WAM

W1-ReceiptIntegInbound

The Receipt inbound integration web service in WAM.

Purchase Return - Inventory Transaction Synchronization Process

The Purchase Return Inventory transaction process is a transactional sync process triggered from the Enterprise Resource Planning system.

Refer to the Purchase Return Synchronization Process Mapping Details section for data mapping information for this integration point.

The following diagram provides a graphical representation of this processing:

Purchase Return Business Process Diagram

Purchase Return - Inventory Transaction Processing Details

This process is triggered when a purchased item is returned in the Enterprise Resource Planning system.

•

The Enterprise Resource Planning system sends Purchase Return Inventory Transaction information to the integration in ERP format.

•

A custom implementation connector can be developed to integrate with the ERP system to transform information into a message using the Inventory transaction EBO format and invoke the requestor process to publish to the Purchase Return Inventory Transaction request queue.

•

The WAM-ERP connector consumes this message, transforms it from EBO to Oracle Utilities Work and Asset Management format and invokes inbound web service in Oracle Utilities Work and Asset Management.

•

Oracle Utilities Work and Asset Management processes this message and sends a response.

•

The integration response requestor transforms this message from Oracle Utilities Work and Asset Management format to Inventory transaction EBO format and adds it to the Purchase Return Inventory Transaction response queue.

•

A custom implementation connector transforms the response and integrates with the ERP system.

Purchase Return - Inventory Transaction Process WAM and ERP System Services

Requestor ABCS

Provider ABCS

Enterpr ise Resource Planning Specific Integration Service

SyncPurReturnInventoryTxnERPReqABCSImpl

n/a

Oracle Utilities Work and Asset Management Specific Integration Services

SyncPurReturnInventoryTxnRespOUWAMUtilitiesReqABCSImpl

SyncPurReturnInventoryTxnOUWAMUtilitiesProvABCSImpl

Purchase Return - Inventory Transaction Process Adapter Services

Name

Description

SyncPurReturnInventoryTxnERPJMSProducer

This adapter is used by SyncPurReturnInventoryTxnERPReqABCSImpl to write the EBO message coming from the ERP system to the PurReturnInventoryTxn queue

SyncPurReturnInventoryTxnOUWAMUtilitiesJMSConsumer

This adapter is used by the SyncPurReturnInventoryTxnOUWAMUtilitiesProvABCSImpl process to consume EBO message from PurReturnInventoryTxn queue

SyncPurReturnInventoryTxnRespOUWAMUtilitiesJMSProducer

This adapter is used by SyncPurReturnInventoryTxnRespOUWAMUtilitiesReqABCSImpl to write the EBO message coming from WAM to the PurReturnInventoryTxn response queue.

Purchase Return - Inventory Transaction Process EBO and EBM Details

EBO

EBM

Inventory Transaction EBO

SyncInventoryTransactionListEBM

SyncInventoryTransactionListResponseEBM

Purchase Return - Inventory Transaction Process JMS Queue Details

Queue Name

JNDI Name

Description

OUWAMERPPurReturn

InventoryTxnRequest

jms/OUWAMERPPurReturn

InventoryTxnRequest

Used to store Enterprise Resource Planning system Purchase Return sync request.

OUWAMERPPurReturn

InventoryTxnResponse

jms/OUWAMERPPurReturn

InventoryTxnResponse

Used to store Oracle Utilities Work and Asset Management Purchase Return sync response.

OUWAMERPPurReturn

InventoryTxnRequestError

jms/OUWAMERPPurReturn

InventoryTxnRequestError

Corresponding Error Queue For Enterprise For Resource Planning system Purchase Return request queue.

OUWAMERPPurReturn

InventoryTxnResponseError

jms/OUWAMERPPurReturn

InventoryTxnResponseError

Corresponding Error Queue For Oracle Utilities Work and Asset Management Purchase Return response queue.

Purchase Return - Inventory Transaction Process External Web Service Call

Application

Inbound Web Service

Description

WAM

W1-PurchaseReturnIntegInbound

The Purchase Return inbound integration web service in WAM.

Material Issue - Inventory Transaction Synchronization Process

The Material Issue Inventory Transaction process is a transactional sync process triggered from the Enterprise Resource Planning system.

Refer to the Material Issue Synchronization Process Mapping Details section for data mapping information for this integration point.

The following diagram provides a graphical representation of this processing:

Material Issue Business Process Diagram

Material Issue - Inventory Transaction Processing Details

This process is triggered when a stock item is checked out or issued from inventory in the Enterprise Resource Planning system.

•

The Enterprise Resource Planning system sends Material Issue information to the integration in ERP format.

•

A custom implementation connector can be developed to integrate with the ERP system to transform information into a message using the Inventory Transaction EBO format and invoke the requestor process to publish to the Material Issue Inventory Transaction request queue.

•

The WAM-ERP connector consumes this message, transforms it from EBO to Oracle Utilities Work and Asset Management format and invokes inbound web service in Oracle Utilities Work and Asset Management.

•

Oracle Utilities Work and Asset Management processes this message and sends a response.

•

The integration response requestor transforms this message from Oracle Utilities Work and Asset Management format to Inventory Transaction EBO format and adds it to the Material Issue Inventory Transaction response queue.

•

A custom implementation connector transforms the response and integrates with the ERP system.

Material Issue - Inventory Transaction Process WAM and ERP System Services

Requestor ABCS

Provider ABCS

Enterpr ise Resource Planning Specific Integration Service

SyncMatIssueInventoryTxnERPReqABCSImpl

n/a

Oracle Utilities Work and Asset Management Specific Integration Services

SyncMatIssueInventoryTxnRespOUWAMUtilitiesReqABCSImpl

SyncMatIssueInventoryTxnOUWAMUtilitiesProvABCSImpl

Material Issue - Inventory Transaction Process Adapter Services

Name

Description

SyncMatIssueInventoryTxnERPJMSProducer

This adapter is used by SyncMatIssueInventoryTxnERPReqABCSImpl to write the EBO message coming from the ERP system to the MatIssueInventoryTxn queue

SyncMatIssueInventoryTxnOUWAMUtilitiesJMSConsumer

This adapter is used by the SyncMatIssueInventoryTxnOUWAMUtilitiesProvABCSImpl process to consume EBO message from MatIssueInventoryTxn queue

SyncMatIssueInventoryTxnRespOUWAMUtilitiesJMSProducer

This adapter is used by SyncMatIssueInventoryTxnRespOUWAMUtilitiesReqABCSImpl to write the EBO message coming from WAM to the MatIssueInventoryTxn response queue.

Material Issue - Inventory Transaction Process EBO and EBM Details

EBO

EBM

Inventory Transaction EBO

SyncInventoryTransactionListEBM

SyncInventoryTransactionListResponseEBM

Material Issue - Inventory Transaction Process JMS Queue Details

Queue Name

JNDI Name

Description

OUWAMERPMatIssue

InventoryTxnRequest

jms/OUWAMERPMatIssue

InventoryTxnRequest

Used to store Enterprise Resource Planning system Material Issue sync request

OUWAMERPMatIssue

InventoryTxnResponse

jms/OUWAMERPMatIssue

InventoryTxnResponse

Used to store Oracle Utilities Work and Asset Management Material Issue sync response

OUWAMERPMatIssue

InventoryTxnRequestError

jms/OUWAMERPMatIssue

InventoryTxnRequesError

Corresponding Error Queue For Enterprise For Resource Planning system Material Issue request queue.

OUWAMERPMatIssue

InventoryTxnResponseError

jms/OUWAMERPMatIssue

InventoryTxnResponseError

Corresponding Error Queue For Oracle Utilities Work and Asset Management Material Issue response queue.

Material Issue - Inventory Transaction Process External Web Service Call

Application

Inbound Web Service

Description

WAM

W1-MaterialIssueIntegInbound

The Material Issue inbound integration web service in WAM.

Material Return - Inventory Transaction Synchronization Process

The Material Return Inventory transaction process is a transactional sync process triggered from the Enterprise Resource Planning system.

Refer to the Material Return Synchronization Process Mapping Details section for data mapping information for this integration point.

The following diagram provides a graphical representation of this processing:

Material Return Business Process Diagram

Material Return - Inventory Transaction Processing Details

The Material Return Inventory transaction process is triggered from the ERP system when a stock item is returned to inventory.

•

The ERP system sends Material Return information to the integration requestor process in ERP format.

•

A custom implementation connector can be developed to integrate with the ERP system to transform information into a message using the Inventory Transaction EBO format and invoke the requestor process to publish to the Material Return Inventory Transaction request queue.

•

The WAM-ERP connector consumes this message, transforms it from EBO to WAM, formats it, and calls the WAM inbound service for Material Return.

•

WAM processes this message and sends a response.

•

The integration response requestor transforms this message from WAM format to the Inventory Transaction EBO format and adds it to the Material Return Inventory Transaction response queue.

•

A custom implementation connector transforms the response and integrates with the ERP system.

Material Return - Inventory Transaction Process WAM and ERP System Services

Requestor ABCS

Provider ABCS

Enterpr ise Resource Planning Specific Integration Service

SyncMatReturnInventoryTxnERPReqABCSImpl

n/a

Oracle Utilities Work and Asset Management Specific Integration Services

SyncMatReturnInventoryTxnRespOUWAMUtilitiesReqABCSImpl

SyncMatReturnInventoryTxnOUWAMUtilitiesProvABCSImpl

Material Return - Inventory Transaction Process Adapter Services

Name

Description

SyncMatReturnInventoryTxnERPJMSProducer

This adapter is used by SyncMatReturnInventoryTxnERPReqABCSImpl to write the EBO message coming from the ERP system to the MatReturnInventoryTxn queue

SyncMatReturnInventoryTxnOUWAMUtilitiesJMSConsumer

This adapter is used by the SyncMatReturnInventoryTxnOUWAMUtilitiesProvABCSImpl process to consume EBO message from MatReturnInventoryTxn queue

SyncMatReturnInventoryTxnRespOUWAMUtilitiesJMSProducer

This adapter is used by SyncMatReturnInventoryTxnRespOUWAMUtilitiesReqABCSImpl to write the EBO message coming from WAM to the MatReturnInventoryTxn response queue.

Material Return - Inventory Transaction Process EBO and EBM Details

EBO

EBM

Inventory Transaction EBO

SyncInventoryTransactionListEBM

SyncInventoryTransactionListResponseEBM

Material Return - Inventory Transaction Process JMS Queue Details

Queue Name

JNDI Name

Description

OUWAMERPMatReturn

InventoryTxnRequest

jms/OUWAMERPMatReturn

InventoryTxnRequest

Used to store Enterprise Resource Planning system Material Return sync request

OUWAMERPMatReturn

InventoryTxnResponse

jms/OUWAMERPMatReturn

InventoryTxnResponse

Used to store Oracle Utilities Work and Asset Management Material Return sync response

OUWAMERPMatReturn

InventoryTxnRequestError

jms/OUWAMERPMatReturn

InventoryTxnRequestError

Corresponding Error Queue For Enterprise For Resource Planning system Material Return request queue.

OUWAMERPMatReturn

InventoryTxnResponse

jms/OUWAMERPMatReturn

InventoryTxnResponseErrpr

Corresponding Error Queue For Oracle Utilities Work and Asset Management Material Return response queue.

Material Return - Inventory Transaction Process External Web Service Call

Application

Inbound Web Service

Description

WAM

W1-MaterialReturnIntegInbound

The Material Return Line inbound integration web service in WAM.

Invoice Synchronization Process

The Invoice process is a transactional sync process triggered from the Enterprise Resource Planning system. This process is only used with Model 2 - ESC.

Refer to the Invoice Synchronization Process Mapping Details section for data mapping information for this integration point.

The following diagram provides a graphical representation of this processing:

Invoice Business Process Diagram

Invoice Processing Details

This process is triggered when the invoice is validated or approved in the Enterprise Resource Planning system.

•

The Enterprise Resource Planning system sends Invoice information to the integration in ERP format.

•

A custom implementation connector can be developed to integrate with the ERP system to transform information into a message using the Invoice EBO format and invoke the requestor process to publish to the Invoice request queue.

•

The WAM-ERP connector consumes this message, transforms it from EBO to Oracle Utilities Work and Asset Management format and invokes inbound web service in Oracle Utilities Work and Asset Management.

•

Oracle Utilities Work and Asset Management processes this message and sends a response.

•

The integration response requestor transforms this message from Oracle Utilities Work and Asset Management format to Invoice EBO format and adds it to the Invoice response queue.

•

A custom implementation connector transforms the response and integrates with the ERP system.

Invoice Process WAM and ERP System Services

Requestor ABCS

Provider ABCS

Enterprise Resource Planning Specific Integration Service

SyncInvoiceERPReqABCSImpl

n/a

Oracle Utilities Work and Asset Management Specific Integration Services

SyncInvoiceRespOUWAMUtilitiesReqABCSImpl

SyncInvoiceOUWAMUtilitiesProvABCSImpl

Invoice Process Adapter Services

Name

Description

SyncInvoiceERPJMSProducer

This adapter is used by SyncInvoiceERPReqABCSImpl to write the EBO message coming from the ERP system to the Invoice queue

SyncInvoiceOUWAMUtilitiesJMSConsumer

This adapter is used by the SyncInvoiceOUWAMUtilitiesProvABCSImpl process to consume EBO message from Invoice queue

SyncInvoiceRespOUWAMUtilitiesJMSProducer

This adapter is used by SyncInvoiceRespOUWAMUtilitiesReqABCSImpl to write the EBO message coming from WAM to the Invoice response queue.

Invoice Process EBO and EBM Details

EBO

EBM

Invoice EBO

SyncInvoiceListEBM

SyncInvoiceListResponseEBM

Invoice Process JMS Queue Details

Queue Name

JNDI Name

Description

OUWAMERPInvoiceFromERPRequest

jms/OUWAMERPInvoiceFromERPRequest

Used to store Enterprise Resource Planning system Invoice sync request

OUWAMERPInvoiceFromERPResponse

jms/OUWAMERPInvoiceFromERPResponse

Used to store Oracle Utilities Work and Asset Management Invoice sync response

OUWAMERPInvoiceFromERPRequestError

jms/OUWAMERPInvoiceFromERPRequestError

Corresponding Error Queue For Enterprise For Resource Planning system Invoice request queue.

OUWAMERPInvoiceFromERPResponse

jms/OUWAMERPInvoiceFromERPResponseError

Corresponding Error Queue For Oracle Utilities Work and Asset Management Invoice response queue.

Invoice Process External Web Service Call

Application

Inbound Web Service

Description

WAM

W1-InvoiceIntegInbound

The Invoice inbound integration web service in WAM.

Invoice Payment (Disbursement) Synchronization Process

The Invoice Payment (Disbursement) process is a transactional sync process triggered from the Enterprise Resource Planning system. This Invoice Payment (Disbursement) process is use in both business models. Whether invoice is coming from the Enterprise Resource Planning or Oracle Utilities Work and Asset Management, Invoice payment is always coming from the Enterprise Resource Planning system.

Refer to the Invoice Payment (Disbursement) Synchronization Process Mapping Details section for data mapping information for this integration point.

The following diagram provides a graphical representation of this processing:

Invoice Payment Business Process Diagram

Invoice Payment (Disbursement) Processing Details

This process is triggered when a check is cut or payment for the invoice is made by the Enterprise Resource Planning system.

•

The Enterprise Resource Planning system sends Invoice Payment information to the integration in ERP format.

•

A custom implementation connector can be developed to integrate with the ERP system to transform information into a message using the Disbursed Payment EBO format and invoke the requestor process to publish to the Disbursed Payment request queue.

•

The WAM-ERP connector consumes this message, transforms it from EBO to Oracle Utilities Work and Asset Management format and invokes inbound web service in Oracle Utilities Work and Asset Management.

•

Oracle Utilities Work and Asset Management processes this message and sends a response.

•

The integration response requestor transforms this message from Oracle Utilities Work and Asset Management format to Disbursed Payment EBO format and adds it to the Disbursed Payment response queue.

•

A custom implementation connector transforms the response and integrates with the ERP system.

Invoice Payment (Disbursement) Process WAM and ERP System Services

Requestor ABCS

Provider ABCS

Enterpr ise Resource Planning Specific Integration Service

SyncDisbursementPaymentERPReqABCSImpl

n/a

Oracle Utilities Work and Asset Management Specific Integration Services

SyncDisbursementPaymentRespOUWAMUtilitiesReqABCSImpl

SyncDisbursementPaymentOUWAMUtilitiesProvABCSImpl

Invoice Payment (Disbursement) Process Adapter Services

Name

Description

SyncDisbursementPaymentERPJMSProducer

This adapter is used by SyncDisbursementPaymentERPReqABCSImpl to write the EBO message coming from the ERP system to the DisbursementPayment queue

SyncDisbursementPaymentOUWAMUtilitiesJMSConsumer

This adapter is used by the SyncDisbursementPaymentOUWAMUtilitiesProvABCSImpl process to consume EBO message from DisbursementPayment queue

SyncDisbursementPaymentRespOUWAMUtilitiesJMSProducer

This adapter is used by SyncDisbursementPaymentRespOUWAMUtilitiesReqABCSImpl to write the EBO message coming from WAM to the DisbursementPayment response queue.

Invoice Payment (Disbursement) Process EBO and EBM Details

EBO

EBM

DisbursementPayment EBO

SyncDisbursementPaymentListEBM

SyncDisbursementPaymentListResponseEBM

Invoice Payment (Disbursement) Process JMS Queue Details

Queue Name

JNDI Name

Description

OUWAMERPDisbursement

PaymentRequest

jms/OUWAMERPDisbursement

PaymentRequest

Used to store Enterprise Resource Planning system Disbursed Payment sync request

OUWAMERPDisbursement

PaymentResponse

jms/OUWAMERPDisbursement

PaymentResponse

Used to store Oracle Utilities Work and Asset Management Disbursed Payment sync response

OUWAMERPDisbursement

PaymentRequestError

jms/OUWAMERPDisbursement

PaymentRequestError

Corresponding Error Queue For Enterprise For Resource Planning system Disbursed Payment request queue.

OUWAMERPDisbursement

PaymentResponseError

jms/OUWAMERPDisbursement

PaymentResponseError

Corresponding Error Queue For Oracle Utilities Work and Asset Management Disbursed Payment response queue.

Invoice Payment (Disbursement) Process External Web Service Call

Application

Inbound Web Service

Description

WAM

W1-InvoicePaymentIntegInbound

The Invoice Payment inbound integration web service in WAM.

GL Transaction (Accounting Entry) Synchronization Process

The GL Transaction (Accounting Entry) process is a master data sync process triggered from the Enterprise Resource Planning system. This process is only used when the your implementation uses Model 2 - ESC.

Note : There is another Accounting Entry synchronization process triggered from Oracle Utilities Work and Asset Management which is only used with Model 1 - WSC.

Refer to the GL Transaction (Accounting Entry) Synchronization Process Mapping Details section for data mapping information for this integration point.

The following diagram provides a graphical representation of this processing:

GL Transaction (Accounting Entry) Business Process Diagram

GL Transaction (Accounting Entry) Processing Details

This process is triggered on create/update of the general ledger (GL) Transaction information in the Enterprise Resource Planning system.

•

The Enterprise Resource Planning system sends GL transaction information to the integration in ERP format.

•

A custom implementation connector can be developed to integrate with the ERP system to transform information into a message using the Accounting Entry EBO format and invoke the requestor process to publish to the Accounting Entry request queue.

•

The WAM-ERP connector consumes this message, transforms it from EBO to Oracle Utilities Work and Asset Management format and invokes inbound web service in Oracle Utilities Work and Asset Management.

•

Oracle Utilities Work and Asset Management processes this message and sends a response.

•

The integration response requestor transforms this message from Oracle Utilities Work and Asset Management format to Accounting Entry EBO format and adds it to the Accounting Entry From Enterprise Resource Planning response queue.

•

A custom implementation connector transforms the response and integrates with the ERP system.

GL Transaction (Accounting Entry) Process WAM and ERP System Services

Requestor ABCS

Provider ABCS

Enterpr ise Resource Planning Specific Integration Service

SyncAccountingEntryERPReqABCSImpl

n/a

Oracle Utilities Work and Asset Management Specific Integration Services

SyncAccountingEntryRespOUWAMUtilitiesReqABCSImpl

SyncAccountingEntryOUWAMUtilitiesProvABCSImpl

GL Transaction (Accounting Entry) Process Adapter Services

Name

Description

SyncAccountingEntryERP

JMSProducer

This adapter is used by SyncAccountingEntryERPReqABCSImpl to write the EBO message coming from the ERP system to the Accounting Entry request queue.

SyncAccountingEntryOUWAMUtilities

JMSConsumer

This adapter is used by the SyncAccountingEntryOUWAMUtilitiesProvABCSImpl process to consume EBO message from Accounting Entry request queue.

SyncAccountingEntryRespOUWAMUtilities

JMSProducer

This adapter is used by SyncAccountingEntryRespOUWAMUtilitiesReqABCSImpl to write the EBO message coming from WAM to the Accounting Entry response queue.

GL Transaction (Accounting Entry) Process EBO and EBM Details

EBO

EBM

Accounting Entry EBO

SyncAccountingEntryListEBM

SyncAccountingEntryListResponseEBM

GL Transaction (Accounting Entry) Process JMS Queue Details

Queue Name

JNDI Name

Description

OUWAMERPAccounting

EntryFromERPRequest

jms/OUWAMERPAccounting

EntryFromERPRequest

Used to store Enterprise Resource Planning system Accounting Entry sync request

OUWAMERPAccounting

EntryFromERPResponse

jms/OUWAMERPAccounting

EntryFromERPResponse

Used to store Oracle Utilities Work and Asset Management Accounting Entry sync response

OUWAMERPAccounting

EntryFromERPRequestError

jms/OUWAMERPAccounting

EntryFromERPRequestError

Corresponding Error Queue For Enterprise For Resource Planning system Accounting Entry request queue.

OUWAMERPAccounting

EntryFromERPResponseError

jms/OUWAMERPAccounting

EntryFromERPResponseError

Corresponding Error Queue For Oracle Utilities Work and Asset Management Accounting Entry response queue.

GL Transaction (Accounting Entry) Process External Web Service Call

Application

Inbound Web Service

Description

WAM

W1-FinancialTransIntegInbound

The Financial Transaction inbound integration web service in WAM.

Oracle Utilities Work and Asset Management Initiated Processes

This section provides information on processing when processing is initiated from Oracle Utilities Work and Asset Management , including:

•

High Level Processing Overview

•

Integration Points

High Level Processing Overview

The following diagrams show the integration processes from Oracle Utilities Work and Asset Management to Enterprise Resource Planning.

WAM to the ERP System Master Data Synchronization Processes

Oracle Utilities Work and Asset Management to the ERP System Transactional Processes

Integration Points

The following integration points are Oracle Utilities Work and Asset Management initiated:

#

Integration Point

Process Type

Comments

1

Supplier Party (Vendor/Vendor Location) Synchronization Process (WAM to ERP)

Master Data Sync

Vendor and Vendor location information sync Supplier Party EBO used for transformation

2

GL Transaction (Accounting Entry) Synchronization Process (WAM to ERP)

Transactional

GL Transaction information sync from WAM to the ERP system Accounting Entry EBO used for transformation

3

Purchase Requisition Synchronization Process

Transactional

Purchase Requisition information sync Requisition EBO used for transformation

4

Material Requisition Synchronization Process

Transactional

Materials Request information from WAM to the ERP system. Inventory Reservation EBO used for transformation

Supplier Party (Vendor/Vendor Location) Synchronization Process (WAM to ERP)

The Supplier Party process is a master data sync process triggered from the Oracle Utilities Work and Asset Management system. This process is only used with Model 2 - WSC.

Note : There is another Supplier Party process triggered from Enterprise Resource Planning which is only used with ESC.

Refer to the Supplier Party (Vendor/Vendor Location) Synchronization Process Mapping Details section for data mapping information for this integration point.

The following diagram provides a graphical representation of this processing:

Supplier Party Business Process Diagram

Supplier Party (Vendor/Vendor Location) Processing Details

This process is triggered when the vendor location is activated in the Oracle Utilities Work and Asset Management system.

•

The Oracle Utilities Work and Asset Management system sends vendor and vendor location information to the integration requestor process. Oracle Utilities Work and Asset Management sends only one vendor location information per message.

•

The WAM-ERP connector transforms this message to the Supplier Party EBO format and saves this message to the Supplier Party queue.

•

A custom implementation connector can be developed to consume and transform the information in EBO format to ERP format and integrate with the ERP system

•

The Enterprise Resource Planning system sends a response back to the Integration Response Requestor process in the ERP format to indicate whether the record was successfully created in the Enterprise Resource Planning system.

•

A custom implementation connector transforms this message into Supplier Party EBO format.

•

The WAM-ERP connector transforms response from EBO to WAM format and invokes WAM inbound service.

•

Note : Implementers must provide the code to consuming or retrieving the message from the queue and processing the message in the Enterprise Resource Planning system

•

Integration Response Requestor adds the Supplier Party EBO format message to the Supplier Party from the Oracle Utilities Work and Asset Management response queue.

•

The Integration Response Provider will consume the message from the response queue; transform the message from Supplier Party EBO format to Oracle Utilities Work and Asset Management format and call the Oracle Utilities Work and Asset Management system inbound service to process the response.

Supplier Party (Vendor/Vendor Location) Process WAM and ERP System Services

Requestor ABCS

Provider ABCS

Enterpr ise Resource Planning Specific Integration Service

SyncSupplierPartyRespERPReqABCSImpl

n/a

Oracle Utilities Work and Asset Management Specific Integration Services

SyncSupplierPartyOUWAMUtilitiesReqABCSImpl

SyncSupplierpartyRespOUWAMUtilitiesProvABCSImpl

Supplier Party Process Adapter Services

Name

Description

SyncSupplierPartyOUWAMUtilities

JMSProducer

This adapter is used by SyncSupplierPartyOUWAMUtilitiesReqABCSImpl to write the EBO message coming from WAM to the Supplier Party request queue.

SyncSupplierPartyRespERP

JMSProducer

This adapter is used by the SyncSupplierPartyRespERPReqABCSImpl process to write the EBO message from the ERP system to the Supplier Party response queue.

SyncSupplierPartyRespOUWAMUtilities

JMSConsumer

This adapter is used by SyncSupplierPartyRespOUWAMUtilitiesProvABCSImpl to consume EBO message coming from the ERP system from the Supplier Party response queue.

Supplier Party Process JMS Queue Details

Queue Name

JNDI Name

Description

OUWAMERPSupplierPartyFromWAMRequest

jms/OUWAMERPSupplierPartyFromWAMRequest

Used to store Oracle Utilities Work and Asset Management Supplier Party sync request

OUWAMERPSupplierPartyFromWAMResponse

jms/OUWAMERPSupplierPartyFromWAMResponse

Used to store Enterprise Resource Planning system Supplier Party sync response

OUWAMERPSupplierPartyFromWAMRequest Error

jms/OUWAMERPSupplierPartyFromWAMRequestError

Corresponding Error Queue For Oracle Utilities Work and Asset Management Supplier Party request queue.

OUWAMERPSupplierPartyFromWAMResponseError

jms/OUWAMERPSupplierPartyFromWAMResponseError

Corresponding Error Queue For Enterprise Resource Planning System Supplier Party response queue.

Supplier Party Process EBO and EBM Details

EBO

EBM

Supplier Party EBO

SyncSupplierPartyListEBM

SyncSupplierPartyListResponseEBM

Supplier Party Process External Web Service Call

Application

Inbound Web Service

Description

WAM

F1-UpdateAndTransitionSyncRequest

This inbound web service updates and transitions sync requests in WAM.

GL Transaction (Accounting Entry) Synchronization Process (WAM to ERP)

The Accounting Entry process is a transactional process triggered from the Oracle Utilities Work and Asset Management system.

Refer to the GL Transaction (Accounting Entry) Synchronization Process Mapping Details section for data mapping information for this integration point.

The following diagram provides a graphical representation of this processing:

Accounting Entry Business Process Diagram

Accounting Entry Processing Details

This process is triggered on create/update of GL Transaction information in the Oracle Utilities Work and Asset Management system.

•

Oracle Utilities Work and Asset Management system sends Accounting Entry information to the integration requestor process.

•

The WAM-ERP connector transforms this message to the Accounting Entry EBO format and saves this message to the Accounting Entry queue.

•

A custom implementation connector can be developed to consume and transform the information in EBO format to ERP format and integrate with the ERP system.

•

The Enterprise Resource Planning system processes the message and sends a response back to the Integration Response Requestor process in the ERP format to indicate whether the record was successfully created in the Enterprise Resource Planning system. Note: Implementers must provide the code to consuming or retrieving the message from the queue and processing the message in the Enterprise Resource Planning system.

•

A custom implementation connector transforms this message into the Accounting Entry EBO format.

•

The WAM-ERP connector transforms response from EBO to WAM format and invokes WAM inbound service.

Accounting Entry Process WAM and ERP System Services

Requestor ABCS

Provider ABCS

Enterpr ise Resource Planning Specific Integration Service

SyncAccountingEntryRespERPReqABCSImpl

n/a

Oracle Utilities Work and Asset Management Specific Integration Services

SyncAccountingEntryOUWAMUtilitiesReqABCSImpl

SyncAccountingEntryRespOUWAMUtilitiesProvABCSImpl

Accounting Entry Process Adapter Services

Name

Description

SyncAccountingEntryOUWAMUtilitiesJMSProducer

This adapter is used by SyncAccountingEntryOUWAMUtilitiesReqAB CSImpl to write the EBO message coming from Oracle Utilities Work and Asset Management to the Accounting Entry queue.

Accounting Entry Process EBO and EBM Details

EBO

EBM

Accounting Entry EBO

SyncAccountingEntryListEBM SyncAccountingEntryListResponseEBM

Accounting Entry Process JMS Queue Details

Queue Name

JNDI Name

Description

OUWAMERPAccounting

EntryRequest

jms/OUWAMERPAccounting

EntryRequest

Used to store Oracle Utilities Work and Asset Management GL Transaction request.

OUWAMERPAccounting

EntryResponse

jms/OUWAMERPAccounting

EntryResponse

Used to store Enterprise Resource Planning system Accounting Entry response.

OUWAMERPAccounting

EntryRequestError

jms/OUWAMERPAccounting

EntryRequestError

Corresponding Oracle Utilities Work and Asset Management GL Transaction request queue.

OUWAMERPAccounting

EntryResponseError

jms/OUWAMERPAccounting

EntryResponseError

Corresponding Enterprise Resource Planning system Accounting Entry response queue.

Accounting Entry Processing External Web Service Call

Application

Inbound Web Service

Description

WAM

F1-UpdateAndTransitionSyncRequest

This inbound web service updates and transitions sync requests in WAM.

Purchase Requisition Synchronization Process

The Purchase Requisition process is a transactional sync process triggered from the Oracle Utilities Work and Asset Management system.

Refer to the Purchase Requisition Synchronization Process Mapping Details section for data mapping information for this integration point.

The following diagram provides a graphical representation of this processing:

Purchase Requisition Business Process Diagram

Purchase Requisition Processing Details

This process is triggered when purchase requisition is ‘ Approved’ in the Oracle Utilities Work and Asset Management system.

•

Oracle Utilities Work and Asset Management system sends purchase requisition information to the integration requestor process.

•

The WAM-ERP connector transforms this message to the Requisition EBO format and save this message to the Requisition request queue.

•

A custom implementation connector can be developed to consume and transform the information in EBO format to ERP format and integrate with the ERP system

•

The Enterprise Resource Planning system sends a response back to the Integration Response Requestor process in the ERP format to indicate whether the record was successfully created in the Enterprise Resource Planning system. Note: Implementers must provide the code to consuming or retrieving the message from the queue and processing the message in the Enterprise Resource Planning system.

•

A custom implementation connector transforms this message into Requisition EBO format.

•

The WAM-ERP connector transforms response from EBO to WAM format and invokes WAM inbound service. When Oracle Utilities Work and Asset Management sends the Requisition to the Enterprise Resource Planning system, the requisition line will either contain the Enterprise Resource Planning stock item system generated ID (resourceTypeExternalId) or the item description when the item or resource is not in the Enterprise Resource Planning system. It passes either the item ID or the item description.Purchase Requisition cancellation and updates are completed in the Enterprise Resource Planning system and not in Oracle Utilities Work and Asset Management. Additionally, the Enterprise Resource Planning system does not send any Purchase Requisition updates back to Oracle Utilities Work and Asset Management. Only acknowledgements on whether or not the Requisition was received.If Requisition status updates need to be synchronized with Oracle Utilities Work and Asset Management, your implementation will need to write an extension. Note: Enterprise Resource Planning needs to store the Oracle Utilities Work and Asset Management system Requisition Header and Line Ids to send back in the PO.

Purchase Requisition Process WAM and ERP System Services

Requestor ABCS

Provider ABCS

Enterpr ise Resource Planning Specific Integration Service

SyncRequisitionRespERPReqABCSImpl

n/a

Oracle Utilities Work and Asset Management Specific Integration Services

SyncRequisitionOUWAMUtilitiesReqABCSImpl

SyncRequisitionRespOUWAMUtilitiesProvABCSImpl

Purchase Requisition Process Adapter Services

Name

Description

SyncRequisitionOUWAMUtilitiesJMSProducer

This adapter is used by SyncRequisitionOUWAMUtilitiesReqABCSImpl to write the EBO message coming from WAM to the Requisition request queue.

SyncRequisitionRespERPJMSProducer

This adapter is used by the SyncRequisitionRespERPReqABCSImpl process to write the EBO message from the ERP system to the Requisition response queue.

SyncRequisitionRespOUWAMUtilitiesJMSConsumer

This adapter is used by SyncRequisitionRespOUWAMUtilitiesProvABCSImpl to consume EBO message coming from the ERP system from the Requisition response queue.

Purchase Requisition Process EBO and EBM Details

EBO

EBM

Requisition EBO

SyncRequisitionListEBM

SyncRequisitionListResponseEBM

Purchase Requisition Process JMS Queue Details

Queue Name

JNDI Name

Description

OUWAMERP

RequisitionRequest

jms/OUWAMERP

RequisitionRequest

Used to store Oracle Utilities Work and Asset Management Purchase Requisition sync request.

OUWAMERP

RequisitionResponse

jms/OUWAMERP

RequisitionResponse

Used to store Enterprise Resource Planning system Purchase Requisition sync response.

OUWAMERP

RequisitionRequestError

jms/OUWAMERP

RequisitionRequestError

Corresponding Oracle Utilities Work and Asset Management Purchase Requisition request queue.

OUWAMERP

RequisitionResponseError

jms/OUWAMERP

RequisitionResponseError

Corresponding Enterprise Resource Planning system Purchase Requisition response queue.

Purchase Requisition Process External Web Service Call

Application

Inbound Web Service

Description

WAM

F1-UpdateAndTransitionSyncRequest

This inbound web service updates and transitions sync requests in WAM.

Material Requisition Synchronization Process

The Material Requisition process is a transactional process triggered from the Oracle Utilities Work and Asset Management system.

Refer to the Materials Requisition Synchronization Process Mapping Details section for data mapping information for this integration point.

The following diagram provides a graphical representation of this processing:

Material Requisition Business Process Diagram

Material Requisition Processing Details

This process is triggered when the Material Request is in ‘ Ready for Issue’ in the Oracle Utilities Work and Asset Management system.

•

Oracle Utilities Work and Asset Management system sends material requisition information to the integration requestor process.

•

The WAM-ERP connector transforms this message to the Requisition EBO format and saves this message to the Material Requisition request queue.

•

A custom implementation connector can be developed to consume and transform the information in EBO format to ERP format and integrate with the ERP system

•

The Enterprise Resource Planning system sends a response back to the Integration Response Requestor process in the ERP format to indicate whether the record was successfully created in the Enterprise Resource Planning system. Note: Implementers must provide the code to consuming or retrieving the message from the queue and processing the message in the Enterprise Resource Planning system.

•

A custom implementation connector transforms this message into Requisition EBO format.

•

The WAM-ERP connector transforms response from EBO to WAM format and invokes WAM inbound service. When Oracle Utilities Work and Asset Management sends the Materials Request to the Enterprise Resource Planning system, the material request line will contain the Enterprise Resource Planning stock item system generated ID (resourceTypeExternalId).All updates to the materials request are completed in the Enterprise Resource Planning system, not in Oracle Utilities Work and Asset Management. Additionally, the ERP system does not send Material Request updates back to Oracle Utilities Work and Asset Management. Only acknowledgments on whether or not the Materials Request was received.If Materials Request status updates need to be synchronized with Oracle Utilities Work and Asset Management, your implementation will need to write an extension. Note: Enterprise Resource Planning needs to store the Oracle Utilities Work and Asset Management system Material Request Header and Line Ids to send back in the Material Issue Inventory Transaction sync.

Material Requisition Process WAM and ERP System Services

Requestor ABCS

Provider ABCS

Enterpr ise Resource Planning Specific Integration Service

SyncMaterialRequisitionRespERPReqABCSImpl

n/a

Oracle Utilities Work and Asset Management Specific Integration Services

SyncMaterialRequisitionOUWAMUtilitiesReqABCSImpl

SyncMaterialRequisitionRespOUWAMUtilitiesProvABCSImpl

Material Requisition Process Adapter Services

Name

Description

SyncMaterialRequisitionOUWAM

UtilitiesJMSProducer

This adapter is used by SyncMaterialRequisitionOUWAMUtilitiesReqABCSImpl to write the EBO message coming from WAM to the Material Requisition queue

SyncMaterialRequisitionRespERP

JMSProducer

This adapter is used by the SyncMaterialRequisitionRespERPReqABCSImpl process to write the EBO message from the ERP system to the Material Requisition response queue.

SyncMaterialRequisitionRespOUWAM

UtilitiesJMSConsumer

This adapter is used by SyncMaterialRequisitionRespOUWAMUtilitiesProvABCSImpl to consume EBO message coming from the ERP system from the Material Requisition response queue.

Material Requisition Process EBO and EBM Details

EBO

EBM

Requisition EBO

SyncRequisitionListEBM

SyncRequisitionListResponseEBM

Material Requisition Process JMS Queue Details

Queue Name

JNDI Name

Description

OUWAMERPMateria

RequisitionRequest

jms/OUWAMERPMateria

RequisitionRequest

Used to store Oracle Utilities Work and Asset Management Material Requisition sync request

OUWAMERPMateria

RequisitionResponse

jms/OUWAMERPMateria

RequisitionResponse

Used to store Enterprise Resource Planning system Material Requisition sync response

OUWAMERPMateria

RequisitionRequestError

jms/OUWAMERPMateria

RequisitionRequestError

Corresponding Oracle Utilities Work and Asset Management Material Requisition request queue.

OUWAMERPMateria

RequisitionResponseError

jms/OUWAMERPMateria

RequisitionResponseError

Corresponding Enterprise Resource Planning system Purchase Material response queue.

Material Requisition Process External Web Service Call

Application

Inbound Web Service

Description

WAM

F1-UpdateAndTransitionSyncRequest

This inbound web service updates and transitions sync requests in WAM.

Configuration Guidelines

This chapter provides details on the required configuration settings for the integration, and provides post-install configuration instructions. It discusses the following:

•

Setting Up Oracle Utilities Work and Asset Management

•

Setting Up Enterprise Resource Planning System

•

Setting up the Integration

Setting Up Oracle Utilities Work and Asset Management

This section describes the required configurations in Oracle Utilities Work and Asset Management, including:

•

Admin Data Tables

•

Master Configuration

•

ERP Integration Master Configuration

•

System Data Tables

•

Web Services

For more information on configuring Oracle Utilities Work and Asset Management, refer to Oracle Utilities Work and Asset Management Administration Guide.

Note : Some configurations described may be required for general functionality and do not necessarily relate directly to the integration; however these are called out as particularly significant configuration items. The inclusion of such items does not mean that other general items that are not mentioned do not need to be configured.

Admin Data Tables

This section describes the unique setup issues specifically related to configuring your system for the integration.

This section provides information on the following admin data configurations:

•

Bin Type

•

Buyer

•

Characteristic Type/Value

•

Commodity Name

•

Commodity Category

•

Commodity Composition

•

Commodity Type

•

Country

•

Currency

•

Expense Usage Code

•

Free On Board (FOB)

•

Hazardous Code

•

Location

•

Organization Unit

•

Payment Term

•

Phone Type

•

State

•

Stock Type

•

UOM Code

•

Vendor Location Priority

•

Worker Type

Bin Type

Bin Type Details for Oracle Utilities Work and Asset Management

Navigation

Guideline

Corresponding DVM

Admin Menu > Lookup (BIN_TYPE_FLG)

Modify or add values to the lookup.

OUWAMERP_BinType

Buyer

Buyer Details for Oracle Utilities Work and Asset Management

Navigation

Guideline

Corresponding DVM

Admin Menu > Buyer

Create/Modify the Buyer.

OUWAMERP_Buyer

Characteristic Type/Value

Tax Type and Value for Oracle Utilities Work and Asset Management

1.

Create a characteristic type with description and Type of Char Value as Predefined Value in Oracle Utilities Work and Asset Management.

2.

Add one or more Characteristic Value to the Characteristic Type.

Navigation

Guideline

Corresponding DVM

Admin Menu > Characteristic Type

Create/Modify the Characteristic Type. Add Characteristic Value to the Characteristic Type.

OUWAMERP_TaxTypeOUWAMERP_TaxTypeValue

Commodity Name

Commodity Name Details for Oracle Utilities Work and Asset Management

Navigation

Guideline

Corresponding DVM

Admin Menu > Commodity Codes

Create/Modify the Commodity Codes.

OUWAMERP_ CommodityName

Commodity Category

Commodity Category Details for Oracle Utilities Work and Asset Management

Navigation

Guideline

Corresponding DVM

(see Commodity Name)

(see Commodity Name)

OUWAMERP_CommodityCategory

Commodity Composition

Commodity Composition Details for Oracle Utilities Work and Asset Management

Navigation

Guideline

Corresponding DVM

(see Commodity Name)

(see Commodity Name)

OUWAMERP_CommodityComposition

Commodity Type

Commodity Type Details for Oracle Utilities Work and Asset Management

Navigation

Guideline

Corresponding DVM

(see Commodity Name)

(see Commodity Name)

OUWAMERP_CommodityType

Country

Country Details for Oracle Utilities Work and Asset Management

Navigation

Guideline

Corresponding DVM

Admin Menu > Country

Create the Country codes.

OUWAMERP_Country

Country Code

Create a country code in Oracle Utilities Work and Asset Management.

The Main page is used to customize the fields and field descriptions that are displayed where addresses are used in the system. This ensures that all addresses conform to the customary address format and conventions of the particular country you have defined. The codes defined here must exactly match values in the DVM indicated.

Country Code Details for Oracle Utilities Work and Asset Management

Navigation

Guideline

Corresponding DVM

Admin Menu > Country

Create the Country codes.

OUWAMERP_Country

Currency

Currency Details for Oracle Utilities Work and Asset Management

Navigation

Guideline

Corresponding DVM

Admin Menu > Currency

Create/Modify the Currency Code and Description.

OUWAMERP_Currency

Expense Usage Code

Expense UsageCode Details for Oracle Utilities Work and Asset Management

Navigation

Guideline

Corresponding DVM

Admin Menu > Expense Code

Create the Expense Code and Description or modify the Expense Code after searching.

OUWAMERP_UsageExpenseCode (EXPENSE_CD)

Free On Board (FOB)

FOB Details for Oracle Utilities Work and Asset Management

Navigation

Guideline

Corresponding DVM

Admin Menu > FOB

Create the FOB code.

OUWAMERP_FOB (FOB_CD)

Hazardous Code

Hazardous Code Details for Oracle Utilities Work and Asset Management

Navigation

Guideline

Corresponding DVM

Admin Menu > Lookup (HAZARD_TYPE_FLG)

Modify or add values to the lookup.

OUWAMERP_HazardousType

Location

Location Details for Oracle Utilities Work and Asset Management

Navigation

Guideline

Corresponding DVM

Main Menu > Location > Contact

Create/Modify a location.

OUWAMERP_LocationId

Organization Unit

Organization Unit Details for Oracle Utilities Work and Asset Management

Navigation

Guideline

Corresponding DVM

Admin Menu > Business Unit

Create a Business Unit

OUWAMERP_OrganizationUnitID

Payment Term

Payment Term Details for Oracle Utilities Work and Asset Management

Navigation

Guideline

Corresponding DVM

Admin Menu > Payment Terms

Create the Payment Terms.

OUWAMERP_PaymentTerm (PAYMENT_TERM_CD)

Phone Type

Phone Type Details for Oracle Utilities Work and Asset Management

Navigation

Guideline

Corresponding DVM

Admin Menu > Phone Type

Create the Phone Type

OUWAMERP_PhoneType

State

State Details for Oracle Utilities Work and Asset Management

Navigation

Guideline

Corresponding DVM

Admin Menu > Country (State tab)

Create the codes for the states

OUWAMERP_State

Stock Type

Stock Type Details for Oracle Utilities Work and Asset Management

Navigation

Guideline

Corresponding DVM

Admin Menu > Lookup (STOCK_TYPE_FLG)

Modify or add values to the lookup.

OUWAMERP_ StockType

UOM Code

UOM Code Details for Oracle Utilities Work and Asset Management

Navigation

Guideline

Corresponding DVM

Admin > Unit of Measure - Resource

Create the UOM Code

OUWAMERP_UOMCode

Vendor Location Priority

Vendor Location Priority Details for Oracle Utilities Work and Asset Management

Navigation

Guideline

Corresponding DVM

Admin Menu > Lookup (VENDOR_PRI_FLG)

Modify or add values to the lookup.

OUWAMERP_VendoryLocPriority

Worker Type

Worker Type Details for Oracle Utilities Work and Asset Management

Navigation

Guideline

Corresponding DVM

Admin > Employee Type

Create the Employee Type.

OUWAMERP_WorkerType

(EMPLOYEE_TYPE_CD)

Master Configuration

Only the Seeder Sync Request Master Configuration needs to be configured:

This Master Configuration data determines the Sync BO that will process the master data sync request. This Master Configuration also provides the reference view to determine of the record exists or not. The Sync BO reference is based on the MO.

To help populate this data, we provide the sample script W1-ERPPreSdr (ERP Integration Pre-Populate Seeder Sync Master Config). This adds ERP Integration values to the Seeder Sync Master Configuration.

Master Data Synchronization

This Master Data Configuration provides external reference information based on the Foreign Key Reference (FK Ref) keys. This allows external IDs to be converted to existing Oracle Utilities Work and Asset Management IDs.

To help populate this data, we provide the sample script W1-ERPPreMCf (ERP Integration Pre-Populate Master Configuration). This adds ERP Integration values to the Master Data Synchronization Master Configuration.

ERP Integration Master Configuration

The Enterprise Resource Planning URL, the Timeout Threshold for retries, the default Contact Type for inbound Vendor Location syncs, and the default Resource Type for Blanket Contracts are defined here.

The Financial Configuration section of the ERP Integration Master Configuration defines the mapping between Enterprise Resource Planning Account Segments and Oracle Utilities Work and Asset Management cost centers. The cost center in Oracle Utilities Work and Asset Management may equate to multiple account segments in Enterprise Resource Planning. The Enterprise Resource Planning integration includes information about all the segments that make up a GL account distribution. Each of these segments (except expense code) is stored on the Oracle Utilities Work and Asset Management cost center. Not all of these segments may be used for the cost center account string in Oracle Utilities Work and Asset Management. If some segments are excluded from the Oracle Utilities Work and Asset Management account string, they need to be put back into the GL account string when cost information needs to be sent from Oracle Utilities Work and Asset Management to the Enterprise Resource Planning system. The master configuration above controls how these segments are used in Oracle Utilities Work and Asset Management.

In order for the segments to be stored properly on the cost center, however, the implementation needs to perform the following:

1.

To allow the code to reference these new elements using the existing Cost Center BO, create a data area, DA, and in your DA, map each account segment to a data location on the cost center maintenance object W1-COSTCTR. For example: To map a segment to a characteristic, it should be mapped to the characteristic child table of cost center W1_COST_CENTER_CHAR. On the DA, make sure to specify the W1-CostCenterAccountSegments value in the Extended Data Area field. This allows the system to automatically include those account segments in the base Cost Center business object, which includes the W1-CostCenterAccountSegments DA. Follow the standard naming conventions to name those elements in the DA. For example: No space or special characters. Also, prefix the DA and its elements with "cm". This reduces the chance of an upgrade conflict when new element(s) are added by base product with the same name. Finally, for each account segment element in the DA, there must be a corresponding description element using the naming convention by suffixing "Description". For example: To add the cmDepartment element to a department account segment, add the cmDepartmentDescription element also.

2.

The element names in the DA, only the account segment elements, not those for descriptions, are then cross referenced with the sequential account segments within the ERP Master Configuration Financial section. Note that the system expects the sequence number to start with 1 and incremental by 1. For example: 1, 2, 3, so on up to 10. Each Element Name in the Financial section must be the xpath to the corresponding elements. For example: cmDepartment, cmCompany. The easiest way to get the xpath is to click "View Schema" on the page/portal of your DA, click the element and copy the xpath at the top.

When the account segments are received from the Enterprise Resource Planning system, each segment is written to the corresponding business object elements. When a GL Account string needs to be send to the Enterprise Resource Planning system, each business object element is read and concatenated in the order of the Account Segments defined in the ERP Master Config. The delimiter defined in the ERP Master Config separates each Account Segment in the GL Account string.

3.

The ERP Integration Master Configuration includes a Key Reference Mapping section to define the mapping between Key Reference Views and Identifier Types for each integration maintenance object. This is used to find the External IDs for Integration objects not sent via the Seeder Syncs. This is similar to the Seeder Sync and Master Data Sync Master Configurations. The following Views have been created for these references.

View

Description

W1_ON_BLANKET_CONTRACT_LINE_VW

Integration Key Blanket Contract View

W1_ON_BLANKET_CONTRACT_VW

Integration Key Blanket Contract View

W1_ON_COST_CENTER_VW

Ongoing Sync Key Cost Center View

W1_ON_FINANCIAL_TRANS_VW

Integration Key Financial Transaction View

W1_ON_INVOICE_LINE_VW

Integration Key Invoice Line View

W1_ON_INVOICE_VW

Integration Key Invoice View

W1_ON_MATERIAL_ISSUE_VW

Integration Key Material Issue View

W1_ON_MATERIAL_RETURN_LINE_VW

Integration Key Material Return Line View

W1_ON_MATERIAL_RETURN_VW

Integration Key Material Return View

W1_ON_PURCHASE_ORDER_LINE_VW

Integration Key Purchase Order Line

W1_ON_PURCHASE_ORDER_VW

Integration Key Purchase Order View

W1_ON_RECEIPT_LINE_VW

Integration Key Receipt Line View

W1_ON_RECEIPT_VW

Integration Key Receipt View

W1_ON_RETURN_LINE_VW

Integration Key Material Return Line View

W1_ON_STOCK_TRANS_VW

Integration Key Stock Transaction View

Enterprise Resource Planning Administrative Records

The Enterprise Resource Planning Admin business object was created to define ownership between of the different maintenance objects available for the integration.

Each maintenance object that can be integrated contains the integration maintenance object option to signify that the maintenance object is available for the integration. An Enterprise Resource Planning Admin object can be created for each of these maintenance objects. The Enterprise Resource Planning Admin object not only defines ownership (Oracle Utilities Work and Asset Management or Enterprise Resource Planning), but also defines the applicable integration business object or Oracle Utilities Work or Asset Management business object to use. The Integration business object is used to send out an integration request to the Enterprise Resource Planning system. The Oracle Utilities Work and Asset Management business object is used to create the Oracle Utilities Work and Asset Management objects.

The Outbound Message Types used to send outbound integration requests are also defined in these admin records. Outbound Message Types for acknowledgments are defined in the BO options of the Integration BO.

It is assumed that if Enterprise Resource Planning owns Purchasing maintenance objects (such as; Accept Line, Blanket Contract, Invoice, Purchase Order, Receipts, Purchase Returns, Vendor Location), then they will own all the Inventory related maintenance objects (Material Issue, Material Return). It’s also assumed that if the Enterprise Resource Planning system owns one Purchasing maintenance object, then they own all the associated Purchasing maintenance objects. Or if the Enterprise Resource Planning system owns one Inventory maintenance object, they own all the associated Inventory maintenance objects. The exceptions are Material Request (W1-MATREQHDR, W1-MATREQLIN), Purchase Requisition (W1-PRHDR, W1-PRLINE), and Material Return Header (W1-MATRTNHDR). These exceptions must originate from Oracle Utilities Work and Asset Management in order to initiate the relationship between the requests and a Work Order or Activity. Also, if the Enterprise Resource Planning system owns the Header maintenance object, they should also own the Line maintenance object. They are separate Enterprise Resource Planning Admin objects so that the business object information can be configured.

This table provides a list of integration business objects and Oracle Utilities Work and Asset Management business objects delivered for this integration.

Maintenance Object

Outbound Integration Business Object

WAM Business Object

W1-ACPTLINE

W1-AcceptLineIntegration

W1-BCHEADER

W1-BCHeaderIntegration

W1-BCLINE

W1-BCLineIntegration

*W1-FT

W1-FinancialTransIntegOutbound

W1-FinancialTransaction

W1-INVCHDR

W1-InvoiceHeaderIntegration

W1-INVCLINE

W1-InvoiceLineIntegration

W1-MATISSLIN

W1-MaterialIssueLineInteg

W1-MATREQHDR

W1-MaterialReqIntegOutbound

W1-MATRTNHDR

W1-MaterialReturnHeaderInteg

W1-MATRTNLIN

W1-MaterialReturnLineInteg

W1-POHDR

W1-POHeaderIntegration

W1-POLINE

W1-POLineIntegration

W1-PRHDR

W1-PurchaseReqIntegOutbound

W1-RCPTHDR

W1-ReceiptHeaderIntegration

W1-RCPTLINE

W1-ReceiptLineIntegration

W1-RTNLINE

W1-PurchaseReturnLineInteg

W1-VENDORLOC

W1-VendorLocIntegOutbound

In the context of this ERP integration, there is no ownership for the FT maintenance object, or to be more specific, the system ignores the owning system on a record here for FT. An FT inherits the owning system from the object that creates it. For example: Material Issue Line

A record here for FT is simply to define the Outbound Integration business object, Outbound Message Type and Oracle Utilities Work and Asset Management business object. Since FT could go either direction, the record for FT should have all three defined: Outbound Integration business object, Outbound Message Type, and Oracle Utilities Work and Asset Management business object. The system checks the owning system of the object that directly creates the FT. If ownership is Oracle Utilities Work and Asset Management, then the FTs are sent via integration. If the owning system is ERP, the assumption is that ERP sends that object and its FT to Oracle Utilities Work and Asset Management, thus Oracle Utilities Work and Asset Management does no further processing on the FT. No Enterprise Resource Planning Admin record for an object indicates that FT records created by that object are sent as batch as defined in the Financial Master Configuration information. For implementations that do not use this integration or use Oracle Utilities Work and Asset Management for both Inventory and Purchasing, they can always use the batch option.

This table provides a list of maintenance objects that create FTs. Some of them are discussed in the table above. For objects that are not directly involved in ERP integration, (Timesheet Detail) implementations should still configure a record for applicable one(s) so their FTs will be sent to ERP through integration as well. There is no reason for some FTs to go through integration while others go through batch flat file.

Maintenance Object

Description

Comments

W1-ACPTLINE

Accept Line

W1-MATISSLIN

Material Issue Line

W1-MATRTNLIN

Material Return Line

W1-TIMSHTDTL

Timesheet Detail

W1-ODCDETAIL

Other Direct Charge Detail

W1-PILINE

Physical Inventory Count Line

W1-INVADJ

Inventory Adjustmentt

W1-RTNLINE

Return Line

Also referred to as Purchase Return

W1-INVCHDR

Invoice Header

Invoice header creates FTs for Freight Charge, Extra Cost, and Discount only when they are not allocated/prorated to invoice lines.

W1-INVCLINE

Invoice Line

W1-ACTRECON

Activity Reconciliation

Reconciliation process for Construction Work Management

Please note the following:

1.

The table is a complete list. You may not need to set up an ERP Admin record for some. For example: If ERP owns inventory, WAM doesn't perform Physical Inventoty and Inventory Adjustment (thus no FT to send out) and there is no need to interface them from ERP to WAM, then there is no need for ERP Admin records for them.

2.

If only the FT needs to be sent to ERP, not the object that creates the FT, on the ERP Admin record, you just need to specifiy WAM as the owing system, no need to specify Outbound Integration business object and Outbound Message Type. For example: If WAM owns inventory, you only need to send the FTs from Inventory Adjustment to ERP, not the Inventory Adjustment itself.

System Data Tables

To configure the System Data tables, you need the following:

•

Business Objects

•

Batch Scheduling

Business Objects

This section describes unique setup issues specifically related to configuring your system for the integration.

Business Object

Description

W1-OngoingSyncRequestCostCtr

W1-OngoingSyncRequestEmployee

W1-OngoingSyncRequestVendorLoc

W1-OngoingSyncRequestStockItem

W1-SIDIntegInbound

These business objects define the behavior of inbound sync requests. The schema elements define information required to maintain the master data in Oracle Utilities Work and Asset Management. These are ongoing sync requests and rely on the W1-SyncRequestInbound web service and IWS service to receive the sync request into WAM. Use the Seeder Sync Master Configurations to define which Ongoing Sync BO to use based on the incoming target MO.

As a part of sync request processing, an acknowledgement message is sent to the external system (either positive or negative). The "Outbound Message Type" business object option contains a reference to the outbound message business object to use for this purpose. The base package includes business object W1- OutboundAcknolwledgeMessage to be used on the outbound message type configuration. Refer to Outbound Configuration in this section for more

information.

The Vendor Location ongoing synchronization requires a default Contact Type in order to create the Main Contact for the Vendor Location. This is defined within the ERP Master Configuration.

The Stock Item Detail ongoing synchronizations require storeroom locations. These locations need to be defined within WAM and attached to the Stock Item Detail before the synchronization can be started. The storeroom location definition will also need the external identifier from the Enterprise Resource Planning system. The external identifier can then be referenced on the sync request. The format of the external identifier is the concatenated string of Inventory Organization Number and Subinventory Name, separated by a "-" character.

The Stock Item Detail ongoing synchronization specifies the target business object using the business object algorithm parameters defined for the Data Transformed state. The target business object depends on the Stock Item Detail Class submitted. W1-SIDExpensedAtReceipt for W1ER, W1-SIDInventory for W1IN, and W1-SIDInventory for W1IL.

The error states in the ongoing sync requests contain automatic To Do creation and automatic retry. The parameters relevant to these processes (To Do Retry Frequency and To Do Maximum Retries) are captured as business object status options. If your implementation needs to introduce your own values, simply add a higher sequenced row for the option you intend to modify. The algorithms automatically use these values.

The Create To Do algorithm (W1-CRE-SRITD) is present to use the base package supplied To Do Type W1-SYRQI for this process. If your implementation needs to use a different To Do Type, you will need to configure your own algorithm and supply the value in its parameters.

The monitor process on the initial states of these business objects may be removed by the implementation if immediate processing of the sync requests as they are received is desired.

W1-FinancialTransIntegOutbound

This business object defines the property of an outbound sync request. The schema elements define the information needed by Enterprise Resource Planning system to consolidate the financial data.

The Create To Do algorithm (W1-FTTDCRE) is present to

use the base package supplied To Do Type W1-FTERR for this process. If your implementation needs to use a different To Do Type, you will need to configure your own algorithm and supply the value in its parameters.

Purchase Requisition

Outbound Integration

This business object defines the property of an outbound sync request. The schema elements define the information needed by Enterprise Resource Planning system Purchase Requisitions.

Material Requisition

Outbound Integration

This business object defines the property of an outbound sync request. The schema elements define the information needed by Enterprise Resource Planning system for Material Requisitions.

Vendor Location

Outbound Integration

This business object defines the property of an outbound sync request. The schema elements define the information needed by Enterprise Resource Planning system to receive Vendor Locations for Invoice Payments.

W1-ReceiptIntegInbound

W1-BlanketContractIntegInbound

W1-PurchaseOrderIntegInbound

W1-InvoiceIntegInbound

W1-MaterialIssueIntegInbound

W1-MaterialReturnIntegInbound

W1-PurchaseReturnIntegInbound

W1-FinancialTransIntegInbound

W1-StockTransIntegInbound

W1-InvoicePaymentIntegInbound

These business objects define the behavior of inbound sync requests. The schema elements define information required to maintain the master data in Oracle Utilities Work and Asset Management.

As a part of sync request processing, an acknowledgement message is sent to the external system (either positive or negative). The "Outbound Message Type" business object option contains a reference to the outbound message business object to use for this purpose. The base package includes business object W1-OutboundAcknolwledgeMessage to be used on the outbound message type configuration. Refer to Outbound Configuration in this section for more information.

The error states in the ongoing sync requests contain automatic To Do creation and automatic retry. The parameters relevant to these processes (To Do Retry Frequency and To Do Maximum Retries) are captured as business object status options. If your implementation needs to introduce your own values, simply add a higher sequenced row for the option you intend to modify. The algorithms automatically use these values.

The Create To Do algorithm (W1-CRE-SRITD) is present to

use the base package supplied To Do Type W1-SYRQI for this process. If your implementation needs to use a different To Do Type, you will need to configure your own algorithm and supply the value in its parameters.

W1-FinancialTransaction

The POPGLDTL state of this business object will create an outbound integration request object if the relevant maintenance object for the FT is owned by ERP (e.g., W1-MATREQHDR for Material Request). The base includes W1- FinancialTransIntegOutbound for this purpose.

W1-PRHeader

Algorithm W1-INTCREPR has been included to create an outbound integration request based on the Purchase Requisition business object when the Purchase Request is Approved. Base code includes W1-PurchaseReqIntegOutbound to capture the information and send to the external system. The outbound request is only created if ownership is set to the Enterprise Resource Planning system for this maintenance object.

W1-MaterialRequestHeader

Algorithms W1- INTSNDMR and W1-INTCREMR have been included to create an outbound integration request based on the Material Request business object when the Material Request is Ready for Issue. Base code includes W1-MaterialReqIntegOutbound to capture the information and send to the external system. The outbound request is only created if ownership is set to the Enterprise Resource Planning system for this maintenance object.

W1-VendorLoc

Algorithm W1- INTCREVLO has been included to create an outbound integration request based on the Vendor Location business object when the Vendor Location is Active. Base code includes W1- VendorLocIntegOutbound to capture the information and send to the external system. The outbound request is only created if ownership is set to the Enterprise Resource Planning system for this maintenance object. An additional algorithm has been added for the Inactive state to capture the status change and send the integration request to the Enterprise Resource Planning system. If a change is required for an Active Vendor Location, then the Vendor Location should be inactivated, updated, then re-activated again.

Batch Scheduling

This is the batch process to run the sync request. It is a generic batch process that is used for different sync processes. It has a couple of parameters that can be used to control which sync request business objects to process.

Batch Processes for Ongoing Sync Requests

Batch Code

Description

W1-SIOPE

The batch process to transition ongoing sync request out of the PENDING state. It is a generic batch process that is used for different sync processes. It has a couple of parameters that can be used to control which sync request business objects to process.

W1-SIOER

The batch process to transition ongoing sync request out of the ERROR state.

Batch Processes for Outbound Sync Requests

Batch Code

Description

F1-SYNRQ

Sync Request Monitor Process : The batch process to run the sync request. It is a generic batch process that is used for different sync processes. It has a couple of parameters that can be used to control which sync request business objects to process.

For more information about the sync request process, the business objects, maintenance objects, and other components used for this process, refer to the section "Data Synchronization" in Oracle Utilities Framework User Guide.

Web Services

This configuration includes the following:

•

Message Senders

•

Outbound Message Types

•

External System

Message Senders

Create a new real-time Message Sender for each Oracle Utilities Work and Asset Management Outbound Message.

To Create a Message Sender:

1.

In the Admin menu, navigate to Message Sender.

2.

Enter a unique Message Sender and its description.

3.

Populate the following values:

•

Message Sender - Sender name in Oracle Utilities Work and Asset Management.

•

Description - Sender’s description.

•

Invocation Type - Real-time

•

XAI Class - RTHTTPSNDR (Sender routes messages via HTTP real-time).

•

Active - Select the check box

•

MSG Encoding - UTF-8 message encoding

4.

Select the Context tab and set values for the following context types:

•

HTTP Header - SOAPAction: "process"

•

HTTP Login User - User ID to access Integration BPEL process

•

HTTP Login Password - Password to access Integration BPEL process

•

HTTP Method (POST/GET) - POST

•

HTTP Timeout - 60

•

HTTP Transport Method - SendReceive

•

HTTP URL 1 - Set the URL to be accessed. If the URL value does not fit, use the additional HTTP URL types to set the complete URL.

The following tables provide examples of the Message Senders that need to be configured. Please note, the message sender names provided are examples only, and are not delivered as part of the integration:

Blanket Contract - Blanket Purchase Agreement Process

Message Sender

Description

HTTP URL

BCBlnktPurAgrSndr

Blanket Contract - Blanket Purchase Agreement Msg

Sender to send the response to the ERP system.

http://soaserver:soaport/soa-infra/services/ OUWAMERP/ SyncBlanketPurchaseAgreementRespOUWAMUtilitiesReqABCSImpl/WAMSyncBlanketPurchaseAgreementResponse_ep

Cost Center - Chart of Accounts Process

Message Sender

Description

HTTP URL

CCChAcctSndr

Cost Center - Chart of Acct message sender that sends the response to the ERP system.

http://soaserver:soaport/soa-infra/services/OUWAMERP/SyncChartOfAccountsRespOUWAMUtilitiesReqABCSImpl/WAMSyncChartOfAccountsResponseService_ep

Employee - Worker Process

Message Sender

Description

HTTP URL

EmpWrkMSndr

Employee - Worker Msg

Sender to send the response to the ERP system.

http://soaserver:soaport/soa-infra/services/OUWAMERP/SyncWorkerRespOUWAMUtilitiesReqABCSImpl/WAMSyncWorkerResponseService_ep

Financial Transaction - Accounting Entry Process

Message Sender

Description

HTTP URL

FTActEnSndr

Financial Transaction - Account Entry Msg

Sender to send the request to the ERP system.

http://soaserver:soaport/soa-infra/services/OUWAMERP/SyncAccountingEntryOUWAMUtilitiesReqAB

CSImplWAMSyncAccountingEntryRequestService_ep

Financial Transaction - Accounting Entry Response Process

Message Sender

Description

HTTP URL

FTActRspEnSndr

Financial Transaction - Account Entry message sender that sends the response to the ERP system.

http://soaserver:soaport/soa-infra/services/OUWAMERP/SyncAccountingEntryRespOUWAMUtilitiesReqABCSImpl/WAMSyncAccountingEntry

Invoice Payment - Disbursement Payment Process

Message Sender

Description

HTTP URL

InvPmtDisbPmtSndr

Invoice Payment - Disbursement Payment Msg

Sender to send the response to the ERP system.

http://soaserver:soaport/soa-infra/services/ OUWAMERP/ SyncDisbursementPaymentRespOUWAMUtilitiesReqABCSImpl/WAMSyncDisbursementPaymentResponse_ep

Invoicing - Invoice Process

Message Sender

Description

HTTP URL

InvoiceSndr

Invoice - Invoice Msg

Sender to send the response to the ERP system.

http://soaserver:soaport/soa-infra/services/

OUWAMERP/ SyncInvoiceRespOUWAMUtilitiesReqABCSImpl/WAMSyncInvoiceFromERPResponse_ep

Material Issue - Material Issue Process

Message Sender

Description

HTTP URL

MatlIssSndr

Material Issue message sender that sends the response to the ERP system.

http://soaserver:soaport/soa-infra/services/

OUWAMERP/ SyncMatIssueInventoryTxnRespOUWAMUtilitiesReqABCSImpl/WAMSyncMaterialIssue

Material Return

Message Sender

Description

HTTP URL

MatlReturnSndr

Material Return message sender that sends the response to the ERP system.

http://soaserver:soaport/soa-infra/OUWAMERP/SyncMatIssueInventoryTxnRespOUWAMUtilitiesReqABCSImpl/WAMSyncMaterialIssue

Material Request - Material Requisition Process

Message Sender

Description

HTTP URL

MatlReqSndr

Material Request - Material Requisition message sender that sends the response to the ERP system.

http://soaserver:soaport/soa-infra/services/OUWAMERP/SyncMaterialRequisitionOUWAMUtilitiesReqABCSImpl/WAMSyncMaterialRequisitonRequestService_ep

Purchase Order Process

Message Sender

Description

HTTP URL

PurOrdrSndr

Purchase Order message sender that sends the response to the ERP system.

http://soaserver:soaport/soa-infra/services/

OUWAMERP/ SyncPurchaseOrderRespOUWAMUtilitiesReqABCSImpl/WAMSyncPurchaseOrderResponse_ep

Purchase Request Process

Message Sender

Description

HTTP URL

PurReqSndr

Purchase Request -Requisition message sender that sends the response to the ERP system.

http://soaserver:soaport/soa-infra/services/

OUWAMERP/ SyncRequisitionOUWAMUtilitiesReqABCSImpl/WAMSyncRequisitionRequestService_ep

Purchase Return Process

Message Sender

Description

HTTP URL

PurRtnSndr

Purchase Return message sender that sends the response to the ERP system.

http://soaserver:soaport/soa-infra/services/

OUWAMERP/ SyncPurReturnInventoryTxnRespOUWAMUtilitiesReqABCSImpl/WAMSyncPurReturnInvTxnResponse

Receipt - Shipment Receipt Process

Message Sender

Description

HTTP URL

RcptShpRcptSndr

Receipt - Shipment Receipt message sender that sends the response to the ERP system.

http://soaserver:soaport/soa-infra/services/

OUWAMERP/ SyncShipmentReceiptRespOUWAMUtilitiesReqABCSImpl/WAMSyncShipmentReceiptResponse_ep

Stock Item Process

Message Sender

Description

HTTP URL

StockItemSndr

Stock Item message sender that sends the response to the ERP system.

http://soaserver:soaport/soa-infra/services/

OUWAMERP/ SyncStockItemRespOUWAMUtilitiesReqABCSImpl/WAMSyncStockItemResponseService_ep

Stock Item Detail - Storeroom Item Process

Message Sender

Description

HTTP URL

StkItmDtlStrmItmSndr

Stock Item Detail - Storeroom Item message sender that sends the response to the ERP system.

http://soaserver:soaport/soa-infra/services/

OUWAMERP/ SyncStoreroomItemRespOUWAMUtilitiesReqABCSImpl/WAMSyncStoreroomResponse_ep

Stock Transaction - Item Balance Process

Message Sender

Description

HTTP URL

STItmBalSndr

Stock Transaction - Item Balance message sender that sends the response to the ERP system.

http://soaserver:soaport/soa-infra/services/

OUWAMERP/ SyncItemBalanceRespOUWAMUtilitiesReqABCSImpl/WAMSyncItemBalanceResponse_ep

Vendor Location - Supplier Party Process

Message Sender

Description

HTTP URL

VndrLcSPSndr

Vendor Location - Supplier Party message sender that sends the response to the ERP system.

http://soaserver:soaport/soa-infra/services/OUWAMERP/SyncSupplierPartyRespOUWAMUtilitiesReqABCSImpl/WAMSyncSupplierPartyResponseService_ep

Vendor Location - Supplier Party Request Process

Message Sender

Description

HTTP URL

VndrLocSupPrtySndr

Vendor Location - Supplier Party message sender that sends the response to the ERP system.

http://soaserver:soaport/soa-infra/services/

OUWAMERP/ SyncSupplierPartyOUWAMUtilitiesReqABCSImpl/WAMSyncSupplierPartyRequestService_ep

Outbound Message Types

Create a new outbound message type for each Oracle Utilities Work and Asset Management outbound message.

To create new outbound message types:

1.

In the Admin menu, navigate to Outbound Message Type.

2.

Enter an outbound message type, description, and detailed description.

3.

Select the outbound message business object created for a specific outbound message.

The following tables provide examples of the Outbound Message Types that need to be configured. Please note, the outbound message type names provided are examples only, and are not delivered as part of the integration:

Blanket Contract Process Acknowledgment Outbound Message

Outbound Message Type

Description

HTTP URL

BCOuMsg

Blanket Contract - message sender that sends the response to the ERP system.

http://soaserver:soaport/soa-infra//services/OUWAMERP/SyncBlanketPurchaseAgreementRespOUWAMUtilitiesReqABCSImpl/WAMSyncBlanketPurchaseAgreementResponse_ep

Cost Center - Chart of Accounts Process Acknowledgment Outbound Message

Outbound Message Type

Description

Business Object

CCChActOuMsg

Cost Center - Charter of Accounts Out Msg

W1- OutboundAcknowledgeMessage

Employee - Worker Process Acknowledgment Outbound Message

Outbound Message Type

Description

Business Object

EmpWrkOutMsg

Employee - Worker Out Msg

W1-OutboundAcknowledgeMessage

Financial Transaction - Accounting Entry Process Outbound Message

Outbound Message Type

Description

Business Object

FTActEnOuMsg

FT - Accounting Entry Out Msg

W1-FinancialTransIntegOutMsg

Financial Transaction - Accounting Entry Process Acknowledgment Outbound Message

Outbound Message Type

Description

Business Object

FTActEnAckOuMsg

FT - Accounting Entry Acknowledgement Out Msg

W1-OutboundAcknowledgeMessage

Invoice - Invoice Process Acknowledgment Outbound Message

Outbound Message Type

Description

Business Object

InvoiceOuMsg

Invoice Acknowledgement Out Msg

W1-OutboundAcknowledgeMessage

Invoice Payment - Invoice Payment Process Acknowledgment Outbound Message

Outbound Message Type

Description

Business Object

InvoicePmtOuMsg

Invoice Payment Out Msg

W1-OutboundAcknowledgeMessage

Material Issue Line - Inventory Issue Process Acknowledgment Outbound Message

Outbound Message Type

Description

Business Object

MtlIssInvIssOuMsg

Material Issue Line - Inventory Issue Out Msg

W1-OutboundAcknowledgeMessage

Material Request - Material Requisition Process Outbound Message

Outbound Message Type

Description

Business Object

MtlReqOuMsg

MR - Material Requisition Out Msg

W1-MatlReqIntegOutMsg

Material Return -Inventory Return Process Acknowledgment Outbound Message

Outbound Message Type

Description

Business Object

MtlRtnInvRtnOuMsg

Material Return - Inventory Return Out Msg

W1-OutboundAcknowledgeMessage

Purchase Order - Purchase Order Process Acknowledgment Outbound Message

Outbound Message Type

Description

Business Object

PurchaseOrderOuMsg

PO - Purchase Order Out Msg

W1-OutboundAcknowledgeMessage

Purchase Request - Requisition Process Outbound Message

Outbound Message Type

Description

Business Object

PurReqReqOuMsg

PR - Requisition Out Msg

W1-PurReqIntegOutMsg

Purchase Return - Purchase Return Process Acknowledgment Outbound Message

Outbound Message Type

Description

Business Object

PurRtnOuMsg

Purchase Return Out Msg

W1-OutboundAcknowledgeMessage

Receipt - Receipt Process Acknowledgment Outbound Message

Outbound Message Type

Description

Business Object

ReceiptOuMsg

Receipt Out Msg

W1-OutboundAcknowledgeMessage

Stock Item - Stock Item Process Acknowledgment Outbound Message

Outbound Message Type

Description

Business Object

StockItemOuMsg

Stock Item Out Msg

W1-OutboundAcknowledgeMessage

Stock Item Detail - Storeroom Item Process Acknowledgment Outbound Message

Outbound Message Type

Description

Business Object

SIDStrmItmOuMsg

SID - Storeroom Item Out Msg

W1-OutboundAcknowledgeMessage

Stock Transaction - Item Balance Process Acknowledgment Outbound Message

Outbound Message Type

Description

Business Object

StkTrnItemBalOuMsg

ST - Item Balance Out Msg

W1-OutboundAcknowledgeMessage

Vendor Location - Supplier Party Process Outbound Message

Outbound Message Type

Description

Business Object

VndrLocSupplierOuMsg

VL - Supplier Party Out Msg

W1-VendorLocIntegOutMsg

Vendor Location - Supplier Party Process Acknowledgment Outbound Message

Outbound Message Type

Description

Business Object

VdrLcSPOuMsg

Vendor Location - Supplier Party Out Msg

W1- OutboundAcknowledgeMessage

External System

Create a new external system to support the integration.

To create the external system:

1.

In the Admin menu, navigate to External System.

2.

Search for Enterprise Resource Planning system.

3.

Associate the outbound message types created to the external system. For each outbound message type, set the following:

•

Outbound Message Type - Set the outbound message type created for Oracle Utilities Work and Asset Management outbound message.

•

Processing Method - Real-time.

•

Message Sender - Set the Message Sender created for the integration web service to be invoked by Oracle Utilities Work and Asset Management.

•

Message XSL - W1-AddSOAPEnvMessage.xslFor example: External System - ERP

External System Details

Outbound Message Type

Processing Method

Message Sender

Message XSL

EmpWrkOutMsg

Real-time

EmpWrkMSndr

W1-AddSOAPEnvMessage.xsl

VdrLcSPOuMsg

Real-time

VndrLcSPSndr

W1-AddSOAPEnvMessage.xsl

CCChActOuMsg

Real-time

CCChAcctSndr

W1-AddSOAPEnvMessage.xsl

FTActEnOuMsg

Real-time

FTActEnOuMsg

W1-AddSOAPEnvMessage.xsl

For more information regarding configuration guidelines, refer to the Oracle Utilities Work and Asset Management documentation.

Setting Up Enterprise Resource Planning System

The Enterprise Resource Planning system is setup by the implementation team. The configuration depends on the Enterprise Resource Planning system being used for the integration.

Setting up the Integration

The following areas need to be configured for the Oracle Utilities Work and Asset Management and Enterprise Resource Planning system integration:

•

Configuration Properties

•

Domain Value Maps

•

Error Handling

Configuration Properties

Various configurations that apply to the entire integration system and specific process integration services are stored in the ConfigurationProperties.xml file located in <PRODUCT.HOME>/MDS-Artifacts/OUWAMERP/config/ and the ConfigurationProperties.xml is stored in Metadata Service (MDS).

These configurations hold several configurable values that are picked up by the integration at runtime.

Please refer to Appendix B for more information on the Configuration Properties File setup.

Domain Value Maps

The Domain Value Maps (DVMs) are a standard feature of the Oracle Service-Oriented Architecture (SOA) Suite which maps codes and other static values across applications. The DVMs are stored in Metadata Service (MDS).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. They are stored in XML files and cached in memory at runtime.

Please refer to Appendix C - Domain Value Maps (DVMs) for a listing of the DVMs included for the integration.

To add DVM maps:

1.

Open a browser and access the SOA Composer (http://soa-server:soa-port/soa/composer) for your installation.

2.

On the SOA Composer application, switch to Types View.

3.

Under Domain Value Maps, select the relevant DVM. Search option is also available to find a DVM.

4.

To set up the required values for each integrated application, click the Edit Session button. Add or modify the values in the relevant DVMs, save the changes and click the Publish button. The new DVM values are available to the deployed composites.

For more information about DVMs, see the section "Working with Domain Value Maps" in Oracle® Fusion Middleware Developing SOA Applications with Oracle SOA Suite documentation.

Updating MDS with AIA Meta Data

If the new artifacts are created, if extensions or customizations are made on the artifacts, or if changes are made to the DVM /or the ConfigurationProperties.xml, you must upload the artifacts to the Oracle Metadata Services (MDS).

Oracle Metadata Services (MDS) repository contains all the metadata. The contents under <PRODUCT_HOME>/MDS-Artifacts are uploaded to <SOA-MDS > apps/OUWAMERP. This includes specific schemas, WSDLS, DVMs and ConfigurationProperties.xml.

For more information about updating MDS, see the section "Deployment of MDS Artifacts" in Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning Installation Guide.

Error Handling

This section provides information on the following:

•

Integration Error Handling Setup

•

Error Notifications Setup

•

Error Hospital Setup

Integration Error Handling Setup

INTEGRATION_ERROR_STORE

The INTEGRATION_ERROR_STORE table is used to store all the error details for each message failure. The table is populated for each integration point based on the BusinessError.NotificationFlag and TechnicalError.NotificationFlag properties for each service in the ConfigurationProperties.xml file.

INTEGRATION_ERR_LOOKUP

The error handling module configuration is governed by the Integration_err_lookup table. This table contains processing instructions for each composite. The Error_Processing_Parent composite picks data for one composite and calls error_Processing_Detail for processing. The configuration in this table is used to process the error records stored in the INTEGRATION_ERROR_STORE table.

S. No.

Column Name

Description

Default/ Suggested Values

1

LookUp_ID

Sequence ID of entry in this table. Auto generated.

Auto generated.

2

IP_Name

Name of the composite processed.

Example: SyncWorkerOUWAMUtilitiesProvABCSImpl

Do not modify . This column is pre-populated with the individual enterprise business process name. Modifying this value will cause critical errors.

3

Processing_Status

Current status of processing. It has to be one of the following:

•

HALTED (waiting for manual intervention),

•

NOT REQUIRED

•

ALIVE

Default: NOT REQUIRED

In order to process the error records, this value must be set to ALIVE.

4

Run_Flag

Processing flag status, Y or N. Unread value = N, read value =Y

N

5

Next_Runtime

Next runtime when the error record should be processed for this composite needs to be set for the current day when they turn the @ environment on (or in the past).

Default: SYSDATE+200

This value needs to be set to the current date or past date to process the error records.

6

Halt_For_Error

Allowed values are Y or N.

When set to Y, manual intervention is required after one successful error record processing and any future errors for that composite will not be processed until some action is taken on that task. When set to N, processing continues without halting.

Actions that can be performed include:

•

ALIVE - This will resume the error processing for all unprocessed records in the INTEGRATION_ERROR_STORE table.

•

ALIVE_FOR_FUTURE_PROCESSING- This will resume the error processing ,only for future error records for the composite.

N

7

RunTime_Interval

Runtime interval after which the next error processing should be done.

This value must be updated based on the business requirement. Setting fewer intervals may have impact on performance.

Example: P0Y0M0DT0H5M0S Next processing is done after 5 minutes.

Default : P 10 Y 0M0DT0H0M0S

8

Email_ID

This value needs to be set to the EMAIL ID of the person who should get the emails & who should be notified about the error.

To add multiple Email Ids provide comma separated values.

This value can be different or same for all the Composites.

Default : email@email.com

9

Email_Content_Type

•

GENERIC - One Email is sent for all errors. No detail information is included.

•

SINGLE - One Email is sent for all errors with details included in the attachment.

•

MULTIPLE - Multiple Emails are sent and each email has information equal to the value specified in Error_Count_Per_Notification column. Values are case sensitive and must always be given in upper case.

Default : GENERIC

10

Email_XSL

XSL to be applied for creating Email Content which includes subject/body and attachment. Look and feel can be modified here.

Default file is provided for all the composites and present under the xsl folder of composite.

Example: xsl/ Transformation_Create_Email.xsl

Copy this to the mds folder and enter the mds path in this column for additional configuration.

11

Error_Count_Per_Processing

A notification is sent after the number of records set here is processed.

Example: If this is set to 50, then an email notification containing 50 records is sent after 50 records are created in the error store. For every 50 records an email notification is sent.

Default : 100

12

Email_Sent_For_First_Error

On initial install this is set to N. this value gets updated to Y or N while processing. This field does not need to be updated by the user.

Default : N

13

Ema il_Attachment_Location

Location where the Email attachment is created on the server.

This value should point to the location/ folder where the attachment should be stored. This is used to create the attachment file in the following format. INTEGRATION_ERR_LOOKUP.Email_Attac hment_Location + IP_Name + Date (in YYYYMMDDHH24MMSS)

14

Email_Attachment_Flag

Y - Send Email with attachment. In this case, it is not mandatory to have Email_Attachment_Location specified. N - Send Email without attachment, but send the attachment location. In this case, Email_Attachment_Location has to be specified. ServerName +INTEGRATION_ERR_LOOKUP.Email_Att achment_Location + IntegrationPoint_Name + Date in YYYYMMDDHH24MMSS

N

15

Publish_Human_Task_Flag

Y - Publish human task

N - Don’t publish human task

If Halt_For_Error value is set to Y and Publish_Human_Task_Flag is also Y, then human task is published and the user can take action from worklist application.

N

16

ID_Human_Task

User/ Group ID to which human task should be published in case Halt_For_Error is set to Y. This ID must be present in the WebLogic realm pointed by fusion middleware.

Weblogic

17

Last_Updated_Date

Last updated date time

SYSDATE

18

Purge_Error_Store_Flag

Y - Purge data

N - No purge require

The process PurgeIntegrationErrorStore is deployed when the flag, purge.process.deploy=true (in the deploy.properties file) is set to true duringinstallation.If flag.purge.process = false, then value of this column Purge_Error_Store_Flag will always beN.

Default : N

19

Purge_Processing_Status_Flag

Y - Purge Processing in process

N - Purge processing not happening

The process PurgeIntegrationErrorStore is only

deployed when the flag,

purge.process.deploy=true (in the

deploy.properties file) is set to true during

installation.

If flag.purge.process = false then value of this

column Purge_Error_Store_Flag will always be

N.

Default : N

21

Next_Purge_Date

Next purge date. Format: Next_Purge_date +

Purge_Frequency

Applicable only when flag.purge.process = true in

deploy.properties file during installation and the

process PurgeIntegrationErrorStore ID

deployed.

SYSDATE+100

22

Purge_File_Name

Directory name where the purge file should be stored.

Applicable only when flag.purge.process = true in

deploy.properties file during installation and the

process PurgeIntegrationErrorStore ID

deployed.

'location on server where purge record

should be persisted'

To Customize Error Email Notifications for Individual Integration Points

The values can be directly updated in the INTEGRATION_ERR_LOOKUP table. Alternatively, the composite can be used as follows:

1.

Use the composite: UpdateIntegrationErrorLookupTable.

2.

Open the following URL in a browser to get the screen that provides options to update the contents of table.http://<hostname>:<soa server port>/soa-infra/services/OUWAMERP/UpdateIntegrationErrorLookupTable/ updateintegrationerrorlookuptablebpel_client_ep?

•

Expand WS-Security and provide authentication information.This username and password are going to be same as that used to log in to WebLogic Enterprise Manager console.

•

Expand the paylod section. This displays several editable text fields. Only the ipName field is mandatory and should be entered as one of the values from INTEGRATION_ERR_LOOKUP.IP_NAME field.By default all the checkboxes appearing next to the text fields are checked.

•

Provide values in the text field. If you do not want to have a particular value updated, then uncheck the box.

Error Notifications Setup

This integration uses the SOA 12c Error Hospital to manage the errors. For getting error notifications, the following setups are required:

•

Email Configuration

•

ESS (Oracle Enterprise Scheduler Service) Schedule

•

Error Notification Rules

Email Configuration

The email configuration needs to be done for emails to be sent as error notification.

For more information about the email configuration settings, refer to the Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning Installation Guide.

ESS (Oracle Enterprise Scheduler Service) Schedule

The ESS Schedule defines the frequency for executing the error notification rules. The ESS schedule is created during the installation process. If required, you can also create an ESS schedule manually and use this for the Error Notification setup. You must define the schedule names in the Create Schedule page of Oracle Enterprise Manager Fusion Middleware Control.

To define the schedule, perform the following steps:

1.

In the Navigator, expand Scheduling Services > ESSAPP, or right-click soa-infra (server_name) and select Define Schedules.

2.

From the Scheduling Service menu, select Job Requests > Define Schedules.The schedules available for selection in the Schedule Names list are displayed.

3.

Click Create to create additional schedules and their execution frequency.

Note : While defining a schedule name, ensure that you specify the schedule package name of /oracle/apps/ess/custom/soa. Otherwise, created schedule will not be accessible on the Create or Edit Error Notification Rule page.

Error Notification Rules

Error notification rule(s) can be created on the OUWAMERP partition. The error notification rule uses the ESS schedule to get the frequency of the error notification rule execution.

For more information about the setup, see the section "Configuration of Error Notification Rules", refer to Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning Installation Guide.

For more information about error hospital and error notifications, see the section "Recovering From Faults in the Error Hospital." in Oracle® Fusion Middleware Administering Oracle SOA Suite and Oracle Business Process Management Suite documentation.

Error Hospital Setup

This Integration uses the SOA 12c Error Hospital to manage the errors. You can manage all the faults occurring within Oracle SOA Suite and view aggregated statistics associated with the faults data on the Error Hospital page.

Recoverable instances such as if Oracle Utilities Work and Asset Management is down when the inbound web service is invoked, can be re-tried from the Error Hospital page.

If the error notification rule criteria are satisfied, error notification email can be sent to the administrator. The administrator can then go to the Error Hospital page and start a bulk recovery of the error instances from the Error Hospital page after correcting the error conditions.

For bulk recovery of recoverable instance, perform the following steps:

1.

Login into the Enterprise Manager.

2.

Navigate to SOA > soa-infra > OUWAMERP partition.

3.

Click the Error Hospital tab and search for the faulted instances.

4.

In the Search Results table, identify instances with faults labeled as "Recovery" in the Flow State column. The faults in this state await for recovery.

5.

Select the record of recoverable faulted instances and click on the Bulk Recovery button and retry the instances again.

For more information about error hospital and error notifications, see the section "Recovering From Faults in the Error Hospital" in Oracle® Fusion Middleware Administering Oracle SOA Suite and Oracle Business Process Management Suite documentation.

Monitoring and Troubleshooting

This chapter provides detail on monitoring, error handling, and troubleshooting and discusses how to perform:

•

Monitoring from Oracle Utilities Work and Asset Management

•

Monitoring from the Enterprise Resource Planning System

•

Monitoring from the Integration

•

Troubleshooting

Monitoring from Oracle Utilities Work and Asset Management

This section discusses:

•

Notifications in Oracle Utilities Work and Asset Management

•

Oracle Utilities Work and Asset Management Error Logs

Notifications in Oracle Utilities Work and Asset Management

When the products are published from Oracle Utilities Work and Asset Management, the Sync Requests are transitioned immediately. If the integration layer is down and the message cannot be published to the queue, then the Sync Request is moved to a 'Pending' state. The 'Sync Request Monitor Process' batch program 'F1-SYNRQ' is configured to run periodically to transition the pending Sync Requests for Product Offer.

Once the message is published to the queue, the Sync Requests is in 'Awaiting Acknowledgment' state.

If a positive response is received from the Enterprise Resource Planning system, then the Sync Request is moved to 'Synchronized' state.

If a negative response is received from the Enterprise Resource Planning system or if a time out occurs, then the Sync Request is moved to 'Error' state.

Implementation can plug an algorithm on 'Error' state to create a To Do.

Note : The inbound web service is invoked to process the response message. Regardless of whether To Do was set up or not, the errors are logged in spl-service.log file.

Oracle Utilities Work and Asset Management Error Logs

The Oracle Utilities Work and Asset Management error logs consist of:

•

Errors related to the online sync request transition are stored in the WAM_ENVIRONMENT_NAME/logs/system folder.For example: V231_WAM_PERF_BLD10_LIN_ORA_WLS/logs/system

•

Errors related to the batch sync request transition are stored in the $SPLOUTPUT/ WAM_ENVIRONMENT_NAME folder. For example: /spl/sploutput/V231_WAM_PERF_BLD10_LIN_ORA_WLS

For more information about errors and notifications, see the Oracle Utilities Work and Asset Management documentation.

Monitoring from the Enterprise Resource Planning System

The implementation team has to monitor the messages coming from the Enterprise Resource Planning system.

Monitoring from the Integration

To monitor the integration process using the Integration, use any of the following:

•

Monitoring using SOA Enterprise Manager

•

Monitoring using WebLogic Logs

•

Monitoring the Queues using WebLogic Console

Monitoring using SOA Enterprise Manager

To monitor through the SOA Enterprise Manager Console, following actions are performed:

1.

The Administrator receives a notification email for any failure in integration processes. The notification email includes an error text and description and a link to the failed instance of the composite on Oracle Enterprise Manager (EM) console.

2.

After logging into the Enterprise Manager console, the user can see additional details about the instance.

3.

The status of the Application Business Connector Services (ABCS) instance, payload and child processes can be monitored from the Oracle Enterprise Manager console.

4.

The recoverable error instances can be re-tried one by one or in bulk from the Error Hospital page.

For more information about error hospital and error notifications; see the section "Recovering From Faults in the Error Hospital" in Oracle® Fusion Middleware Administering Oracle SOA Suite and Oracle Business Process Management Suite documentation.

Monitoring using WebLogic Logs

Login to the machine where the SOA server is installed. The SOA logs are stored in: <WebLogic installation folder>/user_projects/domains/<SOA Domain name>/servers/<SOA Server name>/logs

Monitoring the Queues using WebLogic Console

To monitor the queues using the WebLogic console, perform the following steps:

1.

Log into the WebLogic console, and then go to the Services > Messaging > JMS Modules.

2.

All queues used for the integration are available in the "OUWAMERPJMSModule" JMS Module.

3.

Select the appropriate queue on the list and go to the Monitor tab. In the Monitor tab, you can check if the message still exists in the queue. This can happen if there are no consumers listening to the queue in which case, the Consumers Current column is 0.

4.

In the Monitor tab, you can view the message details.

Troubleshooting

This section explains the actions that can be taken to fix transactions failing in the edge applications. This section explains how the failed messages can be resubmitted, in case if there are any error messages.

The following table provides common error scenarios and their resolutions:

S. No.

Message Coming From

Error in SOA

Composite

Error Resolution

1

Enterprise Resource

Planning System

ERP Requestor

process

The Synchronous fault is sent back to Enterprise Resource Planning system. Message can be re-tried from the Enterprise Resource Planning system.

2

Request Queue

WAM Provider

process

Recoverable error instance created in Error Hospital page. Message can be re-tried from the SOA Error Hospital page.

3

Oracle Utilities Work

and Asset Management

WAM Requestor

process

This can be Oracle Utilities Work and Asset Management originated request or response to a previous message from the Enterprise Resource Planning system. Synchronous fault is sent back to Oracle Utilities Work and Asset Management. Message can be re-tried from the Oracle Utilities Work and Asset Management application.

Note : To retry recoverable error instances, follow steps provide in section Error Hospital Setup .

Error Handling Scenarios - More Information

The following sections provide more information on common errors and their resolutions, including:

•

ERP Initiated Message (Integration ERP Requestor or Response Requestor BPEL Process)

•

Integration Reading from the Queue (Integration WAM Provider or Response Provider BPEL Process)

•

WAM Initiated Message (Integration WAM Requestor or Response Requestor BPEL Process

ERP Initiated Message (Integration ERP Requestor or Response Requestor BPEL Process)

Enterprise Resource Planning calls the integration requestor web service to send a request or response message to Oracle Utilities Work and Asset Management.

1.

Integration is down

•

Return fault to Enterprise Resource Planning

•

Enterprise Resource Planning has to resend the message when integration is available.

2.

Queue is down

•

Return fault to Enterprise Resource Planning.

•

Enterprise Resource Planning has to resend the message when queue is available.

Integration Reading from the Queue (Integration WAM Provider or Response Provider BPEL Process)

The integration consumes the message from the queue and calls the Oracle Utilities Work and Asset Management web service.

1.

WAM is down

•

BPEL process issues a rollback and move the message to the ERP JMS Error Queue.

•

Invoke Common Error Handling Process to log the error in the integration error table and send email notification if configured.

•

Once Oracle Utilities Work and Asset Management is up, move the message(s) back to the request or response queue to retry the message(s).

2.

Error in integration process

•

BPEL process moves the message to the ERP JMS Error Queue.

•

Invoke Common Error Handling Process to log the error in the integration error table and send email notification if configured.

•

If the integration configuration issue is fixed, move message back to the queue. Examples, missing entry in configuration properties file or mapping a required field and the field is missing.

3.

Oracle Utilities Work and Asset Management sends fault back to integration

•

BPEL process moves the message to the ERP JMS Error Queue.

•

Invoke Common Error Handling Process to log the error in the integration error table and send email notification if configured.

•

If DVM issue or Oracle Utilities Work and Asset Management configuration issue is fixed, move message back to the queue.

WAM Initiated Message (Integration WAM Requestor or Response Requestor BPEL Process

Oracle Utilities Work and Asset Management calls the integration requestor or response requestor web service to send a message to Enterprise Resource Planning.

1.

Integration is down

•

Return fault to Oracle Utilities Work and Asset Management

•

Oracle Utilities Work and Asset Management has to resend the message when integration is available.

2.

Queue is down

•

Return fault to Oracle Utilities Work and Asset Management.

•

Oracle Utilities Work and Asset Management has to resend the message when queue is available.

3.

Error in integration process

•

BPEL process moves the message to the ERP JMS Error Queue.

•

Invoke Common Error Handling Process to log the error in the integration error table and send email notification if configured.

•

If Integration configuration issue is fixed, move message back to the queue. Examples, missing entry in configuration properties file or mapping a required field and the field is missing.

Error Scenarios

The following table provides an overview of error scenarios.

#

Message Coming From

Error Type

Error Log in Error Table

Error Retry

from Error Queue

Error Notification

Fault Sent To

Comments

1

ERP

Integration Down

N

N

N

ERP

Resend Message from ERP

2

ERP

Queue Down

N

N

N

ERP

Resend Message ERP

3

ERP Request Queue

WAM Down

Y

Y

Y

None

Move message back to Request or response queue

4

ERP Request Queue

Integration Error

Y

Y

Y

None

If Integration configuration issue is fixed, move message back to the queue.

If message has an issue, correct data and resend from ERP

5

ERP Request Queue

WAM returns Fault

Y

Y

None

If DVM issue or WAM configuration issue is fixed, move message back to the queue.

If message has an issue, like missing require fields, correct data and resend from ERP.

6

WAM

Integration Down

N

N

N

WAM

Resend Message from WAM

7

WAM

Queue Down

N

N

N

WAM

Resend Message from WAM

8

WAM

Integration Error

Y

N

Y

WAM

Correct Integration issue and resend from WAM

Extensibility Options

Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning offers extensibility in different ways.

•

EBOs - The design of the Enterprise Business Objects (EBOs) includes mechanisms to extend generic objects in an upgrade-safe manner by providing hooks to plug in additional industry-specific or customer-specific information.

•

XSLs/ABCS - The transformations (XSLs) provided with ABCS have custom transformation templates available to map to and from customer specific elements. The ABCS also provide extensible scopes to extend their own functionality.

This chapter provides guidelines on extending this integration, and discusses how to:

•

Extending EBOs

•

Extending ABC Services

•

Passing Data without Extending the EBOs

Extending EBOs

The EBOs provided with the integration are carefully defined to represent a typical business process; however, these definitions do not contain any specific attributes. To meet the specific needs with more tailored processing, the integration pack provides the means to extend EBOs in a non-intrusive way.

For example, if your business process requires more information when creating a work order, you can extend EBOs to include the additional information.

A custom schema definition file (XSD) is provided for every EBO that is shipped with the integration. The EBO can be modified by changing these custom files. The XSDs are incorporated into the EBOs so that any custom extensions that are added to the EBOs are protected when patches or upgrades are applied.

EBO Customization

The following sections describe a sample scenario of when and how to customize EBOs. To extend EBOs, add custom elements to the EBO then complete custom mapping for the requestor and for the provider:

•

Adding and Mapping Custom Elements to the EBO

•

Mapping Custom Elements to the EBO

•

Mapping the EBO to the Provider

Adding and Mapping Custom Elements to the EBO

Perform the following steps:

1.

From the EBO, identify which section or EBO Type needs to be extended.

2.

Add the custom elements to the correct custom EBO Type section in the custom xsd file.

For more information about Extending EBOs, see the "Extensibility for Oracle AIA Artifacts - Extending EBOs" in Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack.

Mapping Custom Elements to the EBO

The ABCS Requestor processes on the Oracle Utilities Work and Asset Management side are the ones where the Oracle Utilities Work and Asset Management message is translated to the EBO format. In these processes, the custom XSL can be used to map the fields in the Oracle Utilities Work and Asset Management message to the custom EBO fields. Perform the following steps using the Accounting Entry process as an example:

1.

Navigate to the Oracle Utilities Work and Asset Management Accounting Entry Requestor process BPEL composite SyncAccountingEntryOUWAMUtilitiesReqABCSImpland open the custom Oracle Utilities Work and Asset Management message to Enterprise Business Messages (EBM) transformation. (For example, Xform_WAMGLTransaction_to_AccountingEntryRequestEBM_Custom.xsl).

2.

Map the elements from Oracle Utilities Work and Asset Management to the custom EBO elements.

3.

Ensure that the elements are added to the correct section or extension type that needs to be extended. Sample code in the Xform_WAMGLTransaction_to_AccountingEntryRequestEBM_Custom.xsl:

<xsl:template name="SyncAccountingEntryListEBM" xml:id="id_2">

<!-- this template is used for Xformation of SyncAccountingEntryListEBM in Request Message-->

<ns7:AlternateObjectKey xml:id="id_29">

<xsl:if test="/ns0:sendDetails/ns0:integrationDetails/ns0:financialTransactionId">

<ns7:ID>

<xsl:value-of select="/ns0:sendDetails/ns0:integrationDetails/ns0:financialTransactionId"/>

</ns7:ID>

</xsl:if>

</ns7:AlternateObjectKey>

</xsl:template>

Mapping the EBO to the Provider

The ABCS Provider processes on the Oracle Utilities Work and Asset Management side are the ones where the EBM message is translated to Oracle Utilities Work and Asset Management format. In these processes, the custom XSL can be used to map fields in the EBM message to Oracle Utilities Work and Asset Management fields.

Perform the following steps using the Sync Worker Provider as an example:

1.

Navigate to the Oracle Utilities Work and Asset Management Sync Worker Provider process BPEL composite SyncWorkerOUWAMUtilitiesProvABCSImpl and open the custom EBM to Oracle Utilities Work and Asset Management transformation.For example: Xform_SyncWorkerEBM_to_OUWAMEmployee_Custom.xsl

2.

Map the elements from the custom EBO elements to the Oracle Utilities Work and Asset Management message.

3.

Make sure the elements are added to the correct section or extension type that needs to be extended.

4.

Copy the modified EBO xsd file(s) to the correct location on the application server. Ex:<PRODUCT_HOME>/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/<Path_to_xsd>

5.

Update the modified xsd in the above step to the MDS repository for the changes to take effect.

For more information on updating the MDS artifacts, refer to Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning Installation Guide.

6.

Redeploy the modified SOA Composite process.

For more information on redeploying processes, refer to Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning Installation Guide.

7.

Test to make sure the mapping is correct and the information is passed from one application to the other.

Extending ABC Services

All Requestor and Provider ABC Services provided with this integration have extensible scopes available to extend the functionality. The extensible scopes can be used for additional data enrichment, if required.

There exist two extensible scopes within ABCS depending service with Transformations. There is a pre extensible scope before the transformation and a post extensible scope after the transformation.

You can add custom code in these extensible scopes. These customer-developed extensible scopes behave as an extension to the delivered ABC service.

For more information about Extending ABCS, see the section "Customizing SOA Composite Applications" in Oracle® Fusion Middleware Developing SOA Applications with Oracle SOA Suite documentation.

Passing Data without Extending the EBOs

In some cases, it is necessary to map the additional fields provided by the base transformation. Here the required fields may already be available in the EBO schema but not available in Oracle Utilities Work and Asset Management. Oracle Utilities Work and Asset Management provides xsd element of type raw called customElements which can be used to pass additional data to Oracle Utilities Work and Asset Management. In this case, the Custom XSL files provided along with the main transformation in the Oracle Utilities Work and Asset Management Requestor and the Provider processes can be used to map the additional fields in the EBO to Oracle Utilities Work and Asset Management customElements element.

Perform the following steps using the Sync Worker Provider as an example:

1.

Navigate to the Oracle Utilities Work and Asset Management Sync Worker Provider process BPEL composite SyncWorkerOUWAMUtilitiesProvABCSImpl and open the custom EBM to Oracle Utilities Work and Asset Management transformation (For example, Xform_SyncWorkerEBM_to_OUWAMEmployee_Custom.xsl).

2.

Map the elements from the custom EBO elements to the Oracle Utilities Work and Asset Management message.Make sure that the elements are added to the correct section or extension type that needs to be extended.

3.

Copy the modified EBO xsd file(s) to the correct location on the application server.

For example, <PRODUCT_HOME>/AIAMetaData/AIAComponents/ EnterpriseObjectLibrary/<Path_to_xsd>

4.

Update the modified xsd in the above step to the MDS Repository for the changes to take effect.

For more information on updating the MDS artifacts, refer to Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning Installation Guide.

5.

Redeploy the modified SOA Composite process.

For more information on redeploying processes, refer to Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning Installation Guide.

6.

Test to make sure that the mapping is correct and the information is passed from one application to the other. Sample code in Xform_SyncWorkerEBM_to_OUWAMEmployee_Custom.xsl:

<xsl:template name="W1-OngoingSyncRequestEmployee">

<!-- this template is used for Xformation of W1-OngoingSyncRequestEmployee in Request Message-->

<externalPkValue2>

<xsl:value-of select="/ns0:SyncWorkerListEBM/ns0:DataArea/ns0:SyncWorkerList/ns9:Identification/ns9:AlternateObjectKey/ns9:ContextID"/>

</externalPkValue2>

</xsl:template>

Application Security

This chapter describes the different security policies used for different services.

Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning is enhanced with Oracle Web Services Manager (OWSM) to provide the following security features:

•

Attach security policies to services.

•

Pass username/password information through csf-keys.

Applied Security Policies

This section identifies the security policies used for various services:

•

Service Policy

•

Client Policy

•

CSF Key

Service Policy

By default, all Services - Application Business Connector Services (ABCS) are secured with the following service policy:

oracle/wss_http_token_service_policy

The applications invoking secured web services need to send credentials to the service.

Client Policy

The Oracle Utilities Work and Asset Management client services invoked from the integration are secured with the following client policy:

•

oracle/wss_http_token_client_policy for XAI Services

•

oracle/wss_username_token_client_policy for IWS Services

CSF Key

The integration invoking secured Oracle Utilities Work and Asset Management web services send the credentials to the service using the csf-key "OUWAM_01". If the credentials for the Oracle Utilities Work and Asset Management service are changed, then csf-key user/password needs to be updated.

Perform the following steps for changing credentials in the csf-key:

1.

Login into the Enterprise Manager.

2.

Navigate to WebLogic Domain > <Domain_Name> and right click on it.

3.

From the menu, click Security > Credentials.

4.

From the Credentials table, select oracle.wsm.security >OUWAM_01 and click on the Edit button.

5.

On the Key dialog, change the user/password for the Oracle Utilities Work and Asset Management service and save it.

For more information about Extending ABCS, see the section "Enabling Security with Policies and Message Encryption" in Oracle® Fusion Middleware Developing SOA Applications with Oracle SOA Suite documentation.

Appendix A - Data Mapping

Data Mapping

This section provides mapping details for each integration point, including:

Enterprise Resource Planning Initiated Processes

•

Blanket Contract (Purchase Agreement) Synchronization Process Mapping Details

•

Chart of Accounts (Cost Center) Synchronization Process Mapping Details

•

GL Transaction (Accounting Entry) Synchronization Process Mapping Details

•

Invoice Synchronization Process Mapping Details

•

Item Balance (Stock Transaction) Synchronization Process Mapping Details

•

Material Issue Synchronization Process Mapping Details

•

Purchase Order Synchronization Process Mapping Details

•

Shipment Receipt (Purchase Receipt) Synchronization Process Mapping Details

•

Purchase Return Synchronization Process Mapping Details

•

Stock Item Synchronization Process Mapping Details

•

Storeroom Item (Stock Item Detail) Synchronization Process Mapping Details

•

Supplier Party (Vendor/Vendor Location) Synchronization Process Mapping Details

•

Worker (Employee) Synchronization Process Mapping Details

Oracle Utilities Work and Asset Management Initiated Processes

•

GL Transaction (Accounting Entry) Synchronization Process Mapping Details

•

Materials Requisition Synchronization Process Mapping Details

•

Purchase Requisition Synchronization Process Mapping Details

•

Supplier Party (Vendor/Vendor Location) Synchronization Process Mapping Details

Enterprise Resource Planning Initiated Processes

Blanket Contract (Purchase Agreement) Synchronization Process Mapping Details

This section provides data mapping details for the following:

•

Blanket Contract (Purchase Agreement) Request Mapping Details

•

Blanket Contract (Purchase Agreement) Response Mapping Details

Refer to the Blanket Contract (Purchase Agreement) Synchronization Process description for processing details on this integration point.

Blanket Contract (Purchase Agreement) Request Mapping Details

ERP Blanket Purchase Agreement Request EBO Message

IWS: W1-BlanketContractIntegInbound

DVM Mapping

Comments

Full Path

Element Name

Parent Element

Type

W1-BlanketContractIntegInbound

Outermost

Tag

integrationId

W1-BlanketContractIntegInbound

Field

Not Mapped. Created internally in WAM on Add.

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/Identification/BusinessComponentID

externalReferenceId

W1-BlanketContractIntegInbound

Field

ERP Sync Request ID. This is a unique ID sent as part of the request message by the external system (ERP) initiating the sync request. This ID is used by the external system to tie together the response coming back to ERP from WAM.

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/Identification/ApplicationObjectKey/ID

externalPkValue1

W1-BlanketContractIntegInbound

Field

ERP Blanket Purchase Agreement Header ID. This is the Blanket Purchase Agreement Table's unique system generated ID.

externalSystem

W1-BlanketContractIntegInbound

Field

Defaulted by Integration using property name OUWAM.External.System in the ConfigurationProperties file.

targetMo

W1-BlanketContractIntegInbound

Field

Defaulted by Integration using property name OUWAM.BlanketContract.Target.MO in the ConfigurationProperties file.

integrationDetails

W1-BlanketContractIntegInbound

Group

headerInformation

integrationDetails

Group

blanketContractHeaderId

headerInformation

Field

WAM Blanket Contract Header ID. This is a system generated ID created on Add in WAM.

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/Identification/ApplicationObjectKey/ID

blanketContractHeaderExternalId

headerInformation

Field

ERP Blanket Purchase Agreement Header ID. This is the Blanket Purchase Agreement Table's unique system generated ID.

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/Status/Code

boStatus

headerInformation

Field

OUWAMERP_BlanketContractStatus

ERP sends the Blanket Purchase Agreement to WAM when the status is APPROVED.

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/Comment

description

headerInformation

Field

Blanket Purchase Agreement Description

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/Identification/ID

blanketContractNumber

headerInformation

Field

Blanket Contract Number or Blanket Purchase Agreement Number

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/Identification/Revision/Number

revisionNumber

headerInformation

Field

Blanket Purchase Agreement Revision Number

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/Identification/Revision/EffectiveDate

creationDateTime

headerInformation

Field

ERP Blanket Purchase Agreement Creation date time

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/TotalAmount

limitAmount

headerInformation

Field

This is the amount agreed for the blanket agreement

enforceLimit

headerInformation

Group

Not Mapped. Default to No in WAM.

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/EffectiveTimePeriod/StartDateTime

initiationDate

headerInformation

Field

Blanket Purchase Agreement Start Date. Only map the date portion.

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/EffectiveTimePeriod/EndDateTime

expirationDate

headerInformation

Field

Blanket Purchase Agreement End Date. Only map the date portion.

vendorLocationId

headerInformation

Field

Not Mapped WAM Vendor Location ID.

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/SupplierPartyReference/LocationReference/LocationIdentification/ApplicationObjectKey/ID

vendorLocationExternalId

headerInformation

Field

ERP Vendor Location ID or ERP Vendor Site ID.

vendorLocationContactId

headerInformation

Field

Not Mapped. This will be populated in WAM. The value will be obtained from the vendor location.

carrierLocation

headerInformation

Field

Not Mapped

exchangeRate

headerInformation

Field

Not Mapped. This will be populated in WAM. The value will be obtained from the vendor location.

currency

headerInformation

Field

Not Mapped. This will be populated in WAM. The value will be obtained from the vendor location.

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/FOBCode

fob

headerInformation

Field

OUWAMERP_FOB

Freight On Board Code

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/PaymentTerm/Code

paymentTerms

headerInformation

Field

OUWAMERP_PaymentTerm

Payment Term

autoPay

headerInformation

Field

Not Mapped

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/PurchaseAgreementReference/PurchaseAgreementIdentification/ApplicationObjectKey/ID

blanketContractAccessList

headerInformation

Field

Not Mapped

restrictToAccessList

headerInformation

Field

Not Mapped. Default to No in WAM.

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/TotalAmount

defaultLimit

headerInformation

Field

Same value as the limitAmount

lineInfomation

integrationDetails

Group

lineInfomationList

lineInfomation

List

blanketContractLineId

lineInfomationList

Field

Not Mapped. Created internally in WAM on Add.

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/BlanketPurchaseAgreementLine/Identification/ApplicationObjectKey/ID

blanketContractLineExternalId

lineInfomationList

Field

ERP Blanket Purchase Agreement Line ID. This is the Blanket Purchase Agreement Line Table's unique system generated ID.

blanketContractHeaderId

lineInfomationList

Field

Not Mapped.

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/BlanketPurchaseAgreementLine/Status/Code

boStatus

lineInfomationList

Field

OUWAMERP_BlanketContractLineStatus

creationDateTime

lineInfomationList

Field

Not Mapped

lastUpdateRevision

lineInfomationList

Field

Not Mapped

itemNumber

lineInfomationList

Field

Not Mapped. This is an item sequence in WAM.

resourceTypeId

lineInfomationList

Field

Not Mapped. WAM Stock Item Code

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/BlanketPurchaseAgreementLine/ItemReference/ItemIdentification/ApplicationObjectKey/ID

resourceTypeExternalId

lineInfomationList

ERP's system generated stock Item code/ID. This is the Item Table's unique identifier.

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/BlanketPurchaseAgreementLine/ItemReference/ItemIdentification/Description

description

lineInfomationList

Field

Item description

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/BlanketPurchaseAgreementLine/OrderLeadTime

leadTime

lineInfomationList

Field

Number of lead days it takes to receive an item after ordering it

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/BlanketPurchaseAgreementLine/ItemReference/TypeCode

stockType

lineInfomationList

Field

OUWAMERP_StockType

Type of Stock Item

requisitionInfo

lineInfomationList

Group

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/BlanketPurchaseAgreementLine/UnitPrice/Amount

unitprice

requisitionInfo

Field

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/BlanketPurchaseAgreementLine/UnitPrice/PerQuantity (attribute name = unitCode)

unitOfPurchase

requisitionInfo

Field

OUWAMERP_UOMCode

piRatio

requisitionInfo

Not Mapped. Defaulted to 1 in WAM.

manufacturers

lineInfomationList

Field

manufacturersList

manufacturers

Field

Not Mapped

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/BlanketPurchaseAgreementLine/ItemReference/SpecificationGroup/Specification/Identification/ID

Although this is not mapped to WAM, ERP can pass a value here like 'Manufaturer' to specify the field. (Optional)

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/BlanketPurchaseAgreementLine/ItemReference/SpecificationGroup/Specification/Name

Although this is not mapped to WAM, ERP can pass the value description here like 'Manufacturer' to describe the field. (Optional)

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/BlanketPurchaseAgreementLine/ItemReference/SpecificationGroup/Specification/ValueCode

manufacturer

manufacturersList

Field

OUWAMERP_ManufacturerCode

Manufacture Code

/SyncBlanketPurchaseAgreementListEBM/DataArea/SyncBlanketPurchaseAgreementList/BlanketPurchaseAgreementLine/ItemReference/ItemIdentification/ManufacturerItemID

manufacturerPartNumber

manufacturersList

Field

Blanket Contract (Purchase Agreement) Response Mapping Details

WAM Blanket Contract (Purchase Agreement) Response Message

ERP Blanket Contract (Purchase Agreement) List Response Message

Comments

Element Name

Parent Element

Type

Full Path

sendDetails

Outermost

Tag

externalReferenceId

sendDetails

Field

/SyncBlanketPurchaseAgreementListResponseEBM/DataArea/SyncBlanketPurchaseAgreementListResponse/Identification/BusinessComponentID

ERP Sync Request ID. This is the unique ID sent as part of the response message to tie it together to the request. When WAM process the request successfully, it only sends back the externalReferenceId, which is the ERP Sync Request ID.

externalIds

sendDetails

Group

entityIdList

externalIds

List

entity

entityIdList

externalPkValue1

entityIdList

Field

externalPkValue2

entityIdList

Field

externalPkValue3

entityIdList

Field

externalPkValue4

entityIdList

Field

externalPkValue5

entityIdList

Field

exceptionInformation

sendDetails

Group

When WAM encounteres an error while process the request, it sends back the externalReferenceId and the exeptionInformation.

exceptionInformationList

exceptionInformation

List

sequence

exceptionInformationList

Field

messageCategory

exceptionInformationList

Field

/SyncBlanketPurchaseAgreementListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

messageNumber

exceptionInformationList

Field

/SyncBlanketPurchaseAgreementListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

comments

exceptionInformationList

Field

SyncBlanketPurchaseAgreementListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Text

Error comments or error message

messageParameters

exceptionInformationList

List

parameterSequence

messageParameters

Field

messageParameterType

messageParameters

Field

messageParameterValue

messageParameters

Field

Chart of Accounts (Cost Center) Synchronization Process Mapping Details

This section provides data mapping details for the following:

•

Chart of Accounts (Cost Center) Request Mapping Details

•

Chart of Accounts (Cost Center) Response Mapping Details

Refer to the Chart of Accounts (Cost Center) Synchronization Process description for processing details on this integration point.

Chart of Accounts (Cost Center) Request Mapping Details

ERP System(Chart of Accounts (Cost Center) EBO Message)

WAM

(W1-OngoingSyncRequestCostCtr Business Object Message)

DVM Mapping

Comments

Full Path

Element Name

Parent Element

Type

W1-SyncRequestInbound

Outermost

Tag

syncRequestId

W1-SyncRequestInbound

Field

Not Mapped. Created internally in WAM on add.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/Identification/BusinessComponentID

externalReferenceId

W1-SyncRequestInbound

Field

ERP System Sync Request ID : This is a unique ID sent as part of the request message by the external system (ERP system) initiating the sync request. This ID is used by the external system to tie together the response coming back to ERP from WAM.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/Identification/BusinessComponentID

externalPkValue1

W1-SyncRequestInbound

Field

ERP System Sync Request ID: Same value as WAM externalReferenceID.

externalSystem

W1-SyncRequestInbound

Field

Defaulted by the integration using the property name OUWAM.External.System in the ConfigurationProperties file.

targetMo

W1-SyncRequestInbound

Field

Defaulted by the integration using the property name OUWAM.CostCenter.Target.MO in the ConfigurationProperties file.

initialLoad

W1-SyncRequestInbound

Field

Defaulted by the integration using the property name OUWAM.InitialLoad.Flag in the ConfigurationProperties file.

syncRequestDetails

W1-SyncRequestInbound

Group

original

syncRequestDetails

Group

finalSnapshot

original

Group

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/Identification/ApplicationObjectKey/ID

ERP System GL Account String combination is mapped to the EBO Chart Of Accounts ApplicationObjectKey ID, but this value is not mapped to WAM.

externalId

finalSnapshot

Field

This is not mapped from ERP to WAM.

costCenter

finalSnapshot

Field

Not Mapped. Created internally in WAM on Add. WAM derives the cost center from the ERP system segments provided in the message.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/Description

description

finalSnapshot

Field

ERP system Chart of Accounts description.

budgetAmount

finalSnapshot

Field

This is not mapped from ERP to WAM.

allowUserCharge

finalSnapshot

Field

This is not mapped from ERP to WAM.

expenseCodeExternalId

finalSnapshot

Field

This is not mapped from ERP to WAM.

resourceClass

finalSnapshot

Field

Not mapped. The resource class in WAM has one of four values: Materials, Craft, Equipment or Other. This is used so that certain expense codes can only be used on certain items.

costCategory

finalSnapshot

Field

Not mapped. The cost category is an admin value in WAM that is used to group expense codes to more granular levels than just the Resource Class.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/EnabledIndicator

boStatus

finalSnapshot

Field

OUWAMERP_ChartofAccountStatus

ERP system sends an indicator to specify if the account is active or inactive. The integration uses DVM to translate the ERP system indicator to the equivalent WAM Status.

/SyncChartOfAccountsListEBM/DataArea/ SyncChartOfAccountsList/Identification/ ContextID

capitalAccount

finalSnapshot

Field

OUWAMERP_CapitalAccountFlag

ERP system sends an indicator to specify if this is a capital account. The integration uses DVM to translate the ERP system indicator to the equivalent WAM value.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/GLElement(1)/CodeIdentification/ApplicationObjectKey/ID

segment1

finalSnapshot

Field

ERP Segment 1 : ERP system Segments are mapped to the EBO Chart of Accounts GL Elements List and passed to the WAM segment elements.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/GLElement(2)/CodeIdentification/ApplicationObjectKey/ID

segment2

finalSnapshot

Field

ERP System Segment 2.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/GLElement(3)/CodeIdentification/ApplicationObjectKey/ID

segment3

finalSnapshot

Field

ERP System Segment 3.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/GLElement(4)/CodeIdentification/ApplicationObjectKey/ID

segment4

finalSnapshot

Field

ERP System Segment 4.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/GLElement(5)/CodeIdentification/ApplicationObjectKey/ID

segment5

finalSnapshot

Field

ERP System Segment 5.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/GLElement(6)/CodeIdentification/ApplicationObjectKey/ID

segment6

finalSnapshot

Field

ERP System Segment 6.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/GLElement(7)/CodeIdentification/ApplicationObjectKey/ID

segment7

finalSnapshot

Field

ERP System Segment 7.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/GLElement(8)/CodeIdentification/ApplicationObjectKey/ID

segment8

finalSnapshot

Field

ERP System Segment 8.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/GLElement(9)/CodeIdentification/ApplicationObjectKey/ID

segment9

finalSnapshot

Field

ERP System Segment 9.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/GLElement(10)/CodeIdentification/ApplicationObjectKey/ID

segment10

finalSnapshot

Field

ERP System Segment 10.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/GLElement(1)/Description

segment1Description

ERP Segment 1 Descriptions : ERP system Segment descriptions are mapped to the EBO Chart of Accounts GL Element Description List and passed to the WAM segment description elements.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/GLElement(2)/Description

segment2Description

ERP System Segment 2 Descriptions.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/GLElement(3)/Description

segment3Description

ERP System Segment 3 Descriptions.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/GLElement(4)/Description

segment4Description

ERP System Segment 4 Descriptions.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/GLElement(5)/Description

segment5Description

ERP System Segment 5 Descriptions.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/GLElement(6)/Description

segment6Description

ERP System Segment 6 Descriptions.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/GLElement(7)/Description

segment7Description

ERP System Segment 7 Descriptions.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/GLElement(8)/Description

segment8Description

ERP System Segment 8 Descriptions.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/GLElement(9)/Description

segment9Description

ERP System Segment 9 Descriptions.

/SyncChartOfAccountsListEBM/DataArea/SyncChartOfAccountsList/GLElement(10)/Description

segment10Description

ERP System Segment 10 Descriptions.

Chart of Accounts (Cost Center) Response Mapping Details

WAM (Cost Center Sync Response Message)

ERP (Sync Chart Of Accounts List Response Message)

Comments

Element Name

Parent Name

Type

sendDetails

Outermost

Tag

externalReferenceId

sendDetails

Field

/SyncChartOfAccountsListResponseEBM/DataArea/SyncChartOfAccountsListResponse/Identification/BusinessComponentID

ERP System Sync Request ID : The unique ID sent as part of the response message to tie it together to the request. When WAM processes the request successfully, it only sends back the externalReferenceID, which is the ERP system sync request ID.

externalIds

sendDetails

Group

entityIdList

externalIds

List

entity

entityIdList

externalPkValue1

entityIdList

Field

externalPkValue2

entityIdList

Field

externalPkValue3

entityIdList

Field

externalPkValue4

entityIdList

Field

externalPkValue5

entityIdList

Field

exceptionInformation

sendDetails

Group

When WAM encounters an error while processing the request, it sends back the externalReferenceID and the exeptionInformation.

exceptionInformationList

exceptionInformation

List

sequence

exceptionInformationList

Field

messageCategory

exceptionInformationList

Field

/SyncChartOfAccountsListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code contains a concatenation of the WAM Message Category and Message Number.

messageNumber

exceptionInformationList

Field

/SyncChartOfAccountsListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code contains a concatenation of the WAM Message Category and Message Number.

comments

exceptionInformationList

Field

/SyncChartOfAccountsListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Text

Error comments or error message.

messageParameters

exceptionInformationList

List

parameterSequence

messageParameters

Field

messageParameterType

messageParameters

Field

messageParameterValue

messageParameters

Field

GL Transaction (Accounting Entry) Synchronization Process Mapping Details

This section provides data mapping details for the following:

•

GL Transaction (Accounting Entry) Request Mapping Details (ERP to WAM)

•

GL Transaction (Accounting Entry) Response Mapping Details (ERP to WAM)

Refer to the GL Transaction (Accounting Entry) Synchronization Process description for processing details on this integration point.

GL Transaction (Accounting Entry) Request Mapping Details (ERP to WAM)

ERP Accounting Entry Request EBO Message

WAM Financial Transaction Outbound Message Business Object (W1-FinancialTransIntegInbound)

DVM Mapping

Comments

Full Path

Element Name

Parent Element

Type

W1-FinancialTransIntegInbound

Outermost

Tag

syncRequestId

W1-FinancialTransIntegInbound

Field

Not Mapped. Created internally in WAM on Add.

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/Identification/BusinessComponentID

externalReferenceId

W1-FinancialTransIntegInbound

Field

ERP Sync Request ID. This is a unique ID sent as part of the request message by the external system (ERP) initiating the sync request. This ID is used by the external system to tie together the response coming back to ERP from WAM.

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/Identification/ApplicationObjectKey/ID

externalPkValue1

W1-FinancialTransIntegInbound

Field

ERP system generated Financial Transaction (FT) ID.

externalSystem

W1-FinancialTransIntegInbound

Field

Defaulted by Integration using property name OUWAM.External.System in the ConfigurationProperties file.

bo

W1-FinancialTransIntegInbound

Field

Defaulted by Integration using property name OUWAM.FT.BO in the ConfigurationProperties file.

targetMo

W1-FinancialTransIntegInbound

Field

Defaulted by Integration using property name OUWAM.FT.Target.MO in the ConfigurationProperties file.

integrationDetails

W1-FinancialTransIntegInbound

Group

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/TypeCode

financialTransactionType

integrationDetails

Field

OUWAMERP_AccountingEntryType

Indicates the type of accounting entry.WAM Values: Regular or Tax. Use DVM to translate the ERP financial transaction type to the equivalent WAM Accounting Entry Type.

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/Identification/ApplicationObjectKey/ID

financialTransactionExternalId

ERP system generated Financial Transaction (FT) ID.

financialTransactionId

integrationDetails

Field

Not Mapped

boStatus

Not Mapped

amount

integrationDetails

Field

Not Mapped.

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/CurrencyExchange/SourceCurrencyCode

currency

integrationDetails

Field

OUWAMERP_CurrencyCode

The currency of the FT.

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AccountingDate

accountingDate

integrationDetails

Field

The date on which the FT occurred.

activityId

integrationDetails

Field

Not Mapped

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/JournalSourceCode

ERP passes one charge ID per request message. Base on the ID being pass, ERP should set this field according to the values below to specify what type of ID it is.

•

TimesheetDetailId - pass TSD

•

OtherDirectChargesId - pass ODC

•

InventoryCountLineId- pass ICL

•

AcceptLineId - pass ACL

•

MaterialIssueLineId - pass MIL

•

MaterialReturnLineId

•

pass MRL

•

ReturnId - pass RTN

•

InventoryAdjustmentId - pass IAD

•

InvoiceLineId - pass INL

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/LedgerReference/LedgerIdentification/ID

timesheetDetailId

integrationDetails

Field

ERP passes one charge ID per request message. For example: Timehseet ID, Direct Charges ID, Materials Issued ID Invoice Line ID, etc. Base on the value of the EBO's JournalSourceCode, integration will map the ID to the appropriate field in WAM.

otherDirectChargesId

integrationDetails

Field

inventoryCountLineId

integrationDetails

Field

acceptLineId

integrationDetails

Field

materialIssueLineId

integrationDetails

Field

materialReturnLineId

integrationDetails

Field

returnId

integrationDetails

Field

inventoryAdjustmentId

integrationDetails

Field

invoiceLineId

integrationDetails

Field

invoiceHeaderId

integrationDetails

Field

Not Mapped

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AccountingEntryLine/

financialTransactionGlDetails

integrationDetails

List

List mapping in a loop

sequenceNumber

financialTransactionGl

Details

Field

Default by integration base on the list record counter. This is a required field in WAM.

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AccountingEntryLine/DebitAmount

amount

financialTransactionGl

Details

Field

ERP passes debit and credit amount in the EBO DebitAmount field only. Amount is a positve number for debit and a negative number for credit.

distributionCode

financialTransactionGl

Details

Field

Defaulted by Integration using property name OUWAM.Distribustion.Code in the ConfigurationProperties file. The distribution Code defined in the ConfigurationProperties file must exist in WAM; this is used on all ERP based Accounting Entry requests.

project

financialTransactionGl

Details

Field

Not Mapped

costCenter

financialTransactionGl

Details

Field

Not Mapped

expenseCode

financialTransactionGl

Details

Field

Not Mapped

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AccountingEntryLine/GLAccount/Identification/ID

glAccount

financialTransactionGl

Details

Field

GL Account

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AccountingEntryLine/GLAccount/GLElement(1)/GLElement

segment1

financialTransactionGl

Details

Field

GL elements are a sequenced set of account codes that form a Chart Of Accounts Code or GL Account

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AccountingEntryLine/GLAccount/GLElement(2)/GLElement

segment2

financialTransactionGl

Details

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AccountingEntryLine/GLAccount/GLElement(3)/GLElement

segment3

financialTransactionGl

Details

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AccountingEntryLine/GLAccount/GLElement(4)/GLElement

segment4

financialTransactionGl

Details

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AccountingEntryLine/GLAccount/GLElement(5)/GLElement

segment5

financialTransactionGl

Details

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AccountingEntryLine/GLAccount/GLElement(6)/GLElement

segment6

financialTransactionGl

Details

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AccountingEntryLine/GLAccount/GLElement(7)/GLElement

segment7

financialTransactionGl

Details

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AccountingEntryLine/GLAccount/GLElement(8)/GLElement

segment8

financialTransactionGl

Details

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AccountingEntryLine/GLAccount/GLElement(9)/GLElement

segment9

financialTransactionGl

Details

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AccountingEntryLine/GLAccount/GLElement(10)/GLElement

segment10

financialTransactionGl

Details

Field

characteristicType

financialTransactionGl

Details

Field

Not Mapped

characteristicValue

financialTransactionGl

Details

Field

Not Mapped

GL Transaction (Accounting Entry) Response Mapping Details (ERP to WAM)

WAM Financial Transaction Response Message

ERP Accounting Entry Response Message

Comments

Element Name

Parent Element

Type

Full Path

sendDetails

Outermost

Tag

externalReferenceId

sendDetails

Field

/SyncAccountingEntryListResponseEBM/DataArea/SyncAccountingEntryListResponse/Identification/BusinessComponentID

ERP Sync Request ID. The unique ID sent as part of the response message to tie it together to the request. When WAM processes the request successfully, it only sends back the externalReferenceId, which is the ERP Sync Request ID.

externalIds

sendDetails

Group

entityIdList

externalIds

List

entity

entityIdList

externalPkValue1

entityIdList

Field

externalPkValue2

entityIdList

Field

externalPkValue3

entityIdList

Field

externalPkValue4

entityIdList

Field

externalPkValue5

entityIdList

Field

exceptionInformation

sendDetails

Group

When WAM encounters an error while processing the request, it sends back the externalReferenceId and the exeptionInformation.

exceptionInformationList

exceptionInformation

List

sequence

exceptionInformationList

Field

messageCategory

exceptionInformationList

Field

/SyncAccountingEntryListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

messageNumber

exceptionInformationList

Field

/SyncAccountingEntryListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

comments

exceptionInformationList

Field

SyncAccountingEntryListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Text

Error comments or error message

messageParameters

exceptionInformationList

List

parameterSequence

messageParameters

Field

messageParameterType

messageParameters

Field

messageParameterValue

messageParameters

Field

Invoice Synchronization Process Mapping Details

This section provides data mapping details for the following:

•

Invoice Request Mapping Details

•

Invoice Response Mapping Details

Refer to the Invoice Synchronization Process description for processing details on this integration point.

Invoice Request Mapping Details

ERP Invoice Request EBO Message

WAM Web Service Name : W1-InvoiceIntegInbound

DVM Mapping

Comments

Full Path

Element Name

Parent Element

Type

W1-InvoiceIntegInbound

Outermost

Tag

syncRequestId

W1-InvoiceIntegInbound

Field

Not Mapped. Created internally in WAM on Add.

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/Identification/BusinessComponentID

externalReferenceId

W1-InvoiceIntegInbound

Field

ERP Sync Request ID. This is a unique ID sent as part of the request message by the external system (ERP) initiating the sync request. This ID is used by the external system to tie together the response coming back to ERP from WAM.

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/Identification/ApplicationObjectKey/ID

externalPkValue1

W1-InvoiceIntegInbound

Field

ERP system generated Invoice Header ID. This is the Invoice Table's unique system generated ID.

externalSystem

W1-InvoiceIntegInbound

Field

Defaulted by Integration using property name OUWAM.External.System in the ConfigurationProperties file.

bo

W1-InvoiceIntegInbound

Field

Defaulted by Integration using property name OUWAM.Invoice.BO in the ConfigurationProperties file.

targetMo

W1-InvoiceIntegInbound

Field

Defaulted by Integration using property name OUWAM.Invoice.Target.MO in the ConfigurationProperties file.

integrationDetails

W1-InvoiceIntegInbound

Group

ERP system generated Invoice Header ID. This is the Invoice Table's unique system generated ID.

headerInformation

integrationDetails

Group

invoiceHeaderId

headerInformation

Field

Not Mapped. Internal WAM system generated Invoice Header ID created on Add.

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/Identification/ApplicationObjectKey/ID

invoiceHeaderExternalId

headerInformation

Field

ERP system generated Invoice Header ID. This is the Invoice Table's unique system generated ID.

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/Status/Code

boStatus

headerInformation

Field

OUWAMERP_InvoiceStatusCode

ERP sends the Invoice to WAM when the invoice is validated or approved. ERP will also send Paid and Cancel or Void and system can pass other status for update.

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/Identification/ID

invoiceNumber

headerInformation

Field

Invoice Number is the same for both WAM and ERP system

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/Description

description

headerInformation

Field

Invoice Description

clerk

headerInformation

Field

Not Mapped

creationDateTime

headerInformation

Field

Not Mapped

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/AutomaticPaymentIndicator

autopay

headerInformation

Field

OUWAMERP_InvoiceAutoPayIndicator

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/BillToPartyReference/PartyIdentification/ApplicationObjectKey/ID

buyer

headerInformation

Field

OUWAMERP_Buyer

ERP will pass a valid ERP Buyer code or ID to the integration. Integration will use dvm to map the ERP Buyer Code/ID to the Valid WAM Buyer Code/ID. Use existing Buyer.dvm

vendorLocationId

headerInformation

Field

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/BillFromPartyReference/LocationReference/LocationIdentification/ApplicationObjectKey/ID

vendorLocationExternalId

Pass ERP Vendor Location ID or ERP Vendor Site ID. This has to be a valid vendor location in WAM. Supplier Party Sync from ERP to WAM must be done first.

payToVendorLocation

headerInformation

Field

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/RemitToPartyReference/LocationReference/LocationIdentification/ApplicationObjectKey/ID

payToVendorLocationExternalId

headerInformation

Pass ERP Pay To Vendor Location ID or ERP Pay To Vendor Site ID. This has to be a valid vendor location in WAM. Supplier Party Sync from ERP to WAM must be done first.

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/PaymentTerm/Code

paymentTerms

headerInformation

Field

OUWAMERP_PaymentTerms

This is the payment term code. Use existign Payment Term dvm

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/PaymentTerm/Duration

numberOfDays

headerInformation

Field

Number of Days to add to get the due date if it is calculated

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceDateTime

vendorDate

headerInformation

Field

Date printed on invoice, basis of due date calculation. Pass only the date portion.

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/DueDate

invoiceDueDate

headerInformation

Field

Invoice due date

invoiceReceivedDate

headerInformation

Field

Not Mapped. When the Client receive the invoice from the vendor.

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceStatusHistory/StatusHistory/ToStatusCode

ERP should pass hardcoded value ' CREATED'

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceStatusHistory/StatusHistory/EffectiveDateTime

invoiceEnteredDate

headerInformation

Field

Invoice creation date or Invoice enter date when AP clerk entered the invoice into the system. Pass only date portion.

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/CurrencyExchange/SourceCurrencyCode

currency

headerInformation

Field

OUWAMERP_CurrencyCode

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/CurrencyExchange/ConversionRate

exchangeRate

headerInformation

Field

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/PaymentTerm/DiscountPercent

discountRate

headerInformation

Field

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/TotalAmount

manuallyEnteredTotal

headerInformation

Field

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceTaxTotal/Amount

manuallyEnteredTaxTotal

headerInformation

Field

voucherNumber

headerInformation

Field

Not mapped

payImmediate

headerInformation

Field

Not mapped

separateCheck

headerInformation

Field

Not mapped

reviewDate

headerInformation

Field

Not mapped

paymentDate

headerInformation

Field

Not mapped

checkNumber

headerInformation

Field

Not mapped

checkType

headerInformation

Field

Not mapped

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceAllowanceTotal/TypeCode

ERP should pass an allowance type code (default value is DISC) to pass discount amount to WAM. This is not mapped to WAM but is used by the integration to map the discount amount to WAM.

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceAllowanceTotal/Amount

overrideDiscountAmount

headerInformation

Field

OUWAMERP_AllowanceCode

Override Discount Amount for the invoice. This should contain a negative amount.

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceChargeTotal[1]/TypeCode

ERP should pass a charge type code (default value is FRGT) when passing freight amount to WAM. This is not mapped to WAM but is used by the integration to map freight amount to WAM.

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceChargeTotal[1]/Amount

freightAmount

headerInformation

Field

OUWAMERP_ChargeCode

Freight Amount for the invoice

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceChargeTotal[2]/TypeCode

ERP should pass a charge type code (default value is EXCT) when passing extra cost amount to WAM. This is not mapped to WAM but is used by the integration to map extra cost amount to WAM.

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceChargeTotal[2]/Amount

extraCostAmount

headerInformation

Field

OUWAMERP_

ChargeCode

Extra Cost for the invoice.

lineInformation

integrationDetails

Group

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine

lineInformationList

lineInformation

List

Loop through the InvoiceLine List if there is more that one Invoice Line.

invoiceLineId

lineInformationList

Field

Not Mapped. Internal WAM system generated Invoice Line ID created on Add.

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/Identification/ApplicationObjectKey/ID

invoiceLineExternalId

lineInformationList

Field

ERP system generated Invoice Line ID. This is the Invoice Line Table's unique system generated ID.

invoiceHeaderId

lineInformationList

Field

Not Mapped. Derived in WAM

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/Status/Code

boStatus

lineInformationList

Field

OUWAMERP_InvoiceLineStatusCode

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/PurchaseOrderReference/Identification/ApplicationObjectKey/ID

Purchase Order referenced in the invoice. This is the ERP system generated Purchase Order Header ID

purchaseOrderLineId

Not Mapped. Internal WAM system generated Purchase Order Line ID

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/PurchaseOrderReference/Identification/ApplicationObjectKey/ContextID

purchaseOrderLineExternalId

lineInformationList

Field

Purchase Order Line referenced in the invoice. This is the ERP system generated Purchase Order Line ID

activityId

Not Mapped. Activity ID is System generated ID for the Task.

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/WorkOrderLineReference/WorkOrderIdentification/ID

workOrderNumber

WAM Work Order Number. If not provided, derive the value from WAM.

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/WorkOrderLineReference/WorkOrderIdentification/ContextID

activityNumber

lineInformationList

Field

WAM Activity Number. If not provided, derive the value from WAM.

creationDateTime

lineInformationList

Field

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/ItemReference/TypeCode

itemType

lineInformationList

Field

OUWAMERP_ItemType

itemNumber

lineInformationList

Field

Not Mapped Item sequence number

resourceTypeId

lineInformationList

Field

Not Mapped. Internal WAM system generated Stock Item ID

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/ItemReference/ItemIdentification/ApplicationObjectKey/ID

resourceTypeExternalId

ERP's system generated stock Item code/ID. This is the Item Table's unique identifier.

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/ItemReference/Description

description

lineInformationList

Field

item description.

detailedDescription

lineInformationList

Field

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/OrderQuantity

quantity

lineInformationList

Field

currency

lineInformationList

Field

Not Mapped

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/UnitPrice/Amount

unitPrice

lineInformationList

Field

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/UnitPrice/PerQuantity (attribute name = unitCode)

unitOfPurchase

lineInformationList

Field

OUWAMERP_UOMCode

taxRateSchedule

lineInformationList

Field

Not mapped

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/TotalAmount

lineTotal

lineInformationList

Field

Total amount of the invoice line, including the line amount and the total of all the charges, allowances and taxes.

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/ExtendedAmount

lineAmount

lineInformationList

Field

The amount of the invoice line not including taxes or charges. This generally equals the Unit Price times the Order Quantity.

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/InvoiceLineAllowanceTotal/TypeCode

ERP should pass an allowance type code (default value is DISC) when passing line discount amount to WAM. This is not mapped to WAM but is used by the integration to map the line discount amount to WAM.

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/InvoiceLineAllowanceTotal/Amount

proratedDiscount

lineInformationList

Field

OUWAMERP_AllowanceCode

Discount amount per invoice line. This should contain a negative amount.

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/InvoiceLineChargeTotal[1]/TypeCode

ERP should pass a charge type code (default value is FRGT) when passing line freight amount to WAM. This is not mapped to WAM but is used by the integration to map line freight amount to WAM.

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/InvoiceLineChargeTotal[1]/Amount

proratedFreight

lineInformationList

Field

OUWAMERP_

ChargeCode

Freight Amount per invoice line

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/InvoiceLineChargeTotal[2]/TypeCode

ERP should pass a charge type code (default value is EXCT) when passing line extra cost amount to WAM. This is not mapped to WAM but is used by the integration to map line extra cost amount to WAM.

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/InvoiceLineChargeTotal[2]/Amount

proratedExtraCost

lineInformationList

Field

OUWAMERP_

ChargeCode

Extra Cost per invoice line

accountingInformation

lineInformationList

Group

costCenterList

accountingInformation

List

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/InvoiceLineAccountingDistribution/AccountingDistribution/GLAccount/Identification/ID

glAccount

costCenterList

Field

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/InvoiceLineAccountingDistribution/AccountingDistribution/GLAccount/GLElement(1)/GLElement

segment1

costCenterList

Field

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/InvoiceLineAccountingDistribution/AccountingDistribution/GLAccount/GLElement(2)/GLElement

segment2

costCenterList

Field

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/InvoiceLineAccountingDistribution/AccountingDistribution/GLAccount/GLElement(3)/GLElement

segment3

costCenterList

Field

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/InvoiceLineAccountingDistribution/AccountingDistribution/GLAccount/GLElement(4)/GLElement

segment4

costCenterList

Field

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/InvoiceLineAccountingDistribution/AccountingDistribution/GLAccount/GLElement(5)/GLElement

segment5

costCenterList

Field

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/InvoiceLineAccountingDistribution/AccountingDistribution/GLAccount/GLElement(6)/GLElement

segment6

costCenterList

Field

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/InvoiceLineAccountingDistribution/AccountingDistribution/GLAccount/GLElement(7)/GLElement

segment7

costCenterList

Field

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/InvoiceLineAccountingDistribution/AccountingDistribution/GLAccount/GLElement(8)/GLElement

segment8

costCenterList

Field

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/InvoiceLineAccountingDistribution/AccountingDistribution/GLAccount/GLElement(9)/GLElement

segment9

costCenterList

Field

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/InvoiceLineAccountingDistribution/AccountingDistribution/GLAccount/GLElement(10)/GLElement

segment10

costCenterList

Field

costCenter

costCenterList

Field

Not mapped

expenseCode

costCenterList

Field

Not mapped

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/InvoiceLineAccountingDistribution/AccountingDistribution/Percentage

percentage

costCenterList

Field

taxLines

lineInformationList

Group

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/InvoiceLineTaxTotal

taxLinesList

taxLines

List

Loop through the InvoiceLineTaxTotal List if there are more than one Invoice Line tax total. entry

sequence

taxLinesList

Field

Defaulted by Integration

rateSchedule

taxLinesList

Field

effectiveDate

taxLinesList

Field

factor

taxLinesList

Field

factorValue

taxLinesList

Field

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/InvoiceLineTaxTotal/TypeCode

charType

taxLinesList

Field

OUWAMERP_TaxType

Identifies the type of tax (Example: State Tax)

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/InvoiceLineTaxTotal/Identification/ID

charValue

taxLinesList

Field

OUWAMERP_TaxTypeValue

Tax type value (Example: CA)

/SyncInvoiceListEBM/DataArea/SyncInvoiceList/InvoiceLine/InvoiceLineTaxTotal/Amount

taxAmount

taxLinesList

Field

Total amount for a given type of tax per invoice line.

Invoice Response Mapping Details

WAM Invoice Response Message

ERP Invoice List Response Message

Comments

Element Name

Parent Element

Type

Full Path

sendDetails

Outermost

Tag

externalReferenceId

sendDetails

Field

/SyncInvoiceListResponseEBM/DataArea/SyncInvoiceListResponse/Identification/BusinessComponentID

ERP Sync Request ID. This is the unique ID sent as part of the response message to tie it together to the request. When WAM process the request successfully, it only sends back the externalReferenceId, which is the ERP Sync Request ID.

externalIds

sendDetails

Group

entityIdList

externalIds

List

entity

entityIdList

externalPkValue1

entityIdList

Field

externalPkValue2

entityIdList

Field

externalPkValue3

entityIdList

Field

externalPkValue4

entityIdList

Field

externalPkValue5

entityIdList

Field

exceptionInformation

sendDetails

Group

When WAM encounteres an error while process the request, it sends back the externalReferenceId and the exeptionInformation.

exceptionInformationList

exceptionInformation

List

sequence

exceptionInformationList

Field

messageCategory

exceptionInformationList

Field

/SyncInvoiceListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

messageNumber

exceptionInformationList

Field

/SyncInvoiceListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

comments

exceptionInformationList

Field

SyncInvoiceListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Text

Error comments or error message

messageParameters

exceptionInformationList

List

parameterSequence

messageParameters

Field

messageParameterType

messageParameters

Field

messageParameterValue

messageParameters

Field

Invoice Payment (Disbursement) Synchronization Process Mapping Details

This section provides data mapping details for the following:

•

Invoice Payment (Disbursement) Request Mapping Details

•

Invoice Payment (Disbursement) Response Mapping Details

Refer to the Invoice Payment (Disbursement) Synchronization Process description for processing details on this integration point.

Invoice Payment (Disbursement) Request Mapping Details

ERP DisbursementPayment Request EBO Message

WAM Invoice Payment

DVM Mapping

Comments

Full Path

Element Name

Parent Element

Type

W1-InvoicePaymentIntegInbound

Outermost

Tag

This process is used for both Scenario #1 and #2.

syncRequestId

W1-InvoicePaymentIntegInbound

Field

Not Mapped. Created internally in WAM on Add.

/SyncDisbursedPaymentListEBM/DataArea/SyncDisbursedPaymentList/Identification/BusinessComponentID

externalReferenceId

W1-InvoicePaymentIntegInbound

Field

ERP Sync Request ID. This is a unique ID sent as part of the request message by the external system (ERP) initiating the sync request. This ID is used by the external system to tie together the response coming back to ERP from WAM.

/SyncDisbursedPaymentListEBM/DataArea/SyncDisbursedPaymentList/Identification/ApplicationObjectKey/ID

externalPkValue1

W1-InvoicePaymentIntegInbound

Field

This is the Invoice Header ID. If ERP owns invoice, this field contains the ERP system generated Invoice Header ID. If WAM owns invoice, this field contains the WAM system generated Invoice Header ID.

externalSystem

W1-InvoicePaymentIntegInbound

Field

Defaulted by Integration using property name OUWAM.External.System in the ConfigurationProperties file.

targetMo

W1-InvoicePaymentIntegInbound

Field

Defaulted by Integration using property name OUWAM.InvoicePayment.Target.MO in the ConfigurationProperties file.

bo

W1-InvoicePaymentIntegInbound

Field

Defaulted by Integration using property name OUWAM.InvoicePayment.BO in the ConfigurationProperties file.

integrationDetails

W1-InvoicePaymentIntegInbound

Group

/SyncDisbursedPaymentListEBM/DataArea/SyncDisbursedPaymentList/Identification/ApplicationObjectKey/ContextID

This field indicates wheter the invoice originated from WAM or ERP. If invoice orignated from WAM (Invoice owned by WAM), ERP should pass hardcoded value ' WAMINV'. If the invoice originated from the ERP system (Invoice owned by ERP), ERP should pass hardcoded value 'ERPINV'.

/SyncDisbursedPaymentListEBM/DataArea/SyncDisbursedPaymentList/Identification/ApplicationObjectKey/ID

invoiceHeaderExternalId

W1-InvoicePaymentIntegInbound

Field

If SyncDisbursedPaymentList/Identification/ApplicationObjectKey/ContextID is 'ERPINV', ERP passes the ERP system generated Invoice Header ID. WAM invoiceHeaderId field should not be mapped.

/SyncDisbursedPaymentListEBM/DataArea/SyncDisbursedPaymentList/Identification/ApplicationObjectKey/ID

invoiceHeaderId

W1-InvoicePaymentIntegInbound

Field

If SyncDisbursedPaymentList/Identification/ApplicationObjectKey/ContextID is 'WAMINV', ERP passes the WAM system generated Invoice Header ID. WAM invoiceHeaderExternalId should not be mapped.

/SyncDisbursedPaymentListEBM/DataArea/SyncDisbursedPaymentList/Identification/ContextID

voucherNumber

W1-InvoicePaymentIntegInbound

Field

/SyncDisbursedPaymentListEBM/DataArea/SyncDisbursedPaymentList/Identification/ID

invoiceNumber

W1-InvoicePaymentIntegInbound

Field

Pass as is. The Invoice Number will be the same for both the WAM and ERP systems.

/SyncDisbursedPaymentListEBM/DataArea/SyncDisbursedPaymentList/PaymentInstrument/Check/IssuedDate

paymentDate

W1-InvoicePaymentIntegInbound

Field

/SyncDisbursedPaymentListEBM/DataArea/SyncDisbursedPaymentList/PaymentInstrument/Check/Number

checkNumber

W1-InvoicePaymentIntegInbound

Field

/SyncDisbursedPaymentListEBM/DataArea/SyncDisbursedPaymentList/PaymentInstrument/Check/TypeCode

checkType

W1-InvoicePaymentIntegInbound

Field

OUWAMERP_CheckType

/SyncDisbursedPaymentListEBM/DataArea/SyncDisbursedPaymentList/Amount

paymentAmount

W1-InvoicePaymentIntegInbound

Field

Invoice Payment (Disbursement) Response Mapping Details

WAM Invoice Payment Response Message

ERP DisbursementPayment List Response Message

Comments

Element Name

Parent Element

Type

Full Path

sendDetails

Outermost

Tag

externalReferenceId

sendDetails

Field

/SyncDisbursedPaymentListResponseEBM/DataArea/SyncDisbursedPaymentListResponse/Identification/BusinessComponentID

ERP Sync Request ID. This is the unique ID sent as part of the response message to tie it together to the request. When WAM process the request successfully, it only sends back the externalReferenceId, which is the ERP Sync Request ID.

externalIds

sendDetails

Group

entityIdList

externalIds

List

entity

entityIdList

externalPkValue1

entityIdList

Field

externalPkValue2

entityIdList

Field

externalPkValue3

entityIdList

Field

externalPkValue4

entityIdList

Field

externalPkValue5

entityIdList

Field

exceptionInformation

sendDetails

Group

When WAM encounteres an error while process the request, it sends back the externalReferenceId and the exeptionInformation.

exceptionInformationList

exceptionInformation

List

sequence

exceptionInformationList

Field

messageCategory

exceptionInformationList

Field

/SyncDisbursedPaymentListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

messageNumber

exceptionInformationList

Field

/SyncDisbursedPaymentListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

comments

exceptionInformationList

Field

SyncDisbursedPaymentListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Text

Error comments or error message

messageParameters

exceptionInformationList

List

parameterSequence

messageParameters

Field

messageParameterType

messageParameters

Field

messageParameterValue

messageParameters

Field

Item Balance (Stock Transaction) Synchronization Process Mapping Details

This section provides data mapping details for the following:

•

Item Balance (Stock Transaction) Request Mapping Details

•

Item Balance (Stock Transaction) Response Mapping Details

Refer to the Item Balance (Stock Transaction) Synchronization Process description for processing details on this integration point.

Item Balance (Stock Transaction) Request Mapping Details

ERP Item Balance Request EBO Message

WAM Inbound Service: W1-StockTransIntegInbound

DVM Mapping

Comments

Full Path

Element Name

Parent Element

Type

W1-StockTransIntegInbound

Outermost

Tag

syncRequestId

W1-StockTransIntegInbound

Field

Not Mapped. This is a WAM system generated ID created internally in WAM on Add.

/SyncItemBalanceListEBM/DataArea/SyncItemBalanceList/Identification/BusinessComponentID

externalReferenceId

W1-StockTransIntegInbound

Field

ERP Sync Request ID. This is a unique ID sent as part of the request message by the external system (ERP) initiating the sync request. This ID is used by the external system to tie together the response coming back to ERP from WAM.

/SyncItemBalanceListEBM/DataArea/SyncItemBalanceList/Identification/ApplicationObjectKey/ID

externalPkValue1

W1-StockTransIntegInbound

Field

This is the ERP system’s unique system generated ItemBalance ID. The Item Balance Table's unique identifier.

externalSystem

W1-StockTransIntegInbound

Field

Defaulted by Integration using property name OUWAM.External.System in the ConfigurationProperties file.

targetMo

W1-StockTransIntegInbound

Field

Defaulted by Integration using property name OUWAM.StockTransaction.Target.MO in the ConfigurationProperties file.

bo

W1-StockTransIntegInbound

Field

Defaulted by Integration using property name OUWAM.StockTransaction.BOin the ConfigurationProperties file.

integrationDetails

W1-StockTransIntegInbound

Group

/SyncItemBalanceListEBM/DataArea/SyncItemBalanceList/Identification/ApplicationObjectKey/ID

stockTransactionExternalId

integrationDetails

Field

ERP's system generated stock transaction or item balance ID. This is the Item Balance trasnaction's unique identifier.

stockTransactionId

integrationDetails

Field

Not Mapped. WAM's system generated stock transaction ID.

/SyncItemBalanceListEBM/DataArea/SyncItemBalanceList/InventoryBalance/LocationBalance/LocationReference/LocationIdentification/ID

This is the ERP system’s organization number.

Example: In EBS, it is a unique 3 character organization number

/SyncItemBalanceListEBM/DataArea/SyncItemBalanceList/InventoryBalance/LocationBalance/LocationReference/LocationIdentification/ContextID

This is the ERP system’s subinventory name or subinventory ID

/SyncItemBalanceListEBM/DataArea/SyncItemBalanceList/InventoryBalance/ItemReference/ItemIdentification/ApplicationObjectKey/ID

ERP system generated Item ID which is the Item Table's unique identifier.

/SyncItemBalanceListEBM/DataArea/SyncItemBalanceList/InventoryBalance/LocationBalance/LocationReference/LocationIdentification/ID-/SyncItemBalanceListEBM/DataArea/SyncItemBalanceList/InventoryBalance/LocationBalance/LocationReference/LocationIdentification/ContextID-/SyncItemBalanceListEBM/DataArea/SyncItemBalanceList/InventoryBalance/ItemReference/ItemIdentification/ApplicationObjectKey/ID

stockItemDetailExternalId

Same value as externalPKValue1. This is the ERP Storeroom ID or Stock Item Detail. This ID is a concatenation of :

•

ERP's Inventory Organization Number,

•

ERP's Subinventory Name

•

ERP’s Item system generated ID with a dash (-) delimiter in between.

Example: 123-Sub1-987654321

stockItemDetailId

integrationDetails

Group

Not Mapped. WAM's system generated stock item detail ID.

boStatus

integrationDetails

Field

Not Mapped

creationDateTime

integrationDetails

Field

Not Mapped.

/SyncItemBalanceListEBM/DataArea/SyncItemBalanceList/InventoryBalance/ReportingDateTime

transactionDate

integrationDetails

Field

Date for which the item availability information is provided. Only pass the date portion to WAM.

/SyncItemBalanceListEBM/DataArea/SyncItemBalanceList/InventoryBalance/ItemReference/SpecificationGroup/Specification/ValueAmount

unitPrice

integrationDetails

Field

/SyncItemBalanceListEBM/DataArea/SyncItemBalanceList/InventoryBalance/OnHandQuantity

inventoryQty

integrationDetails

Field

The quantity of item on-hand at the reporting date time

reservedQty

integrationDetails

The quantity of item reserved (e.g., by other orders) at the reporting date time. From WAM, this field does not need to be mapped.

relevant

integrationDetails

Field

Not Mapped

Item Balance (Stock Transaction) Response Mapping Details

WAM Stock Transaction Sync Response Message

ERP Sync Item Balance List Response Message

Comments

Element Name

Parent Element

Type

Full Path

sendDetails

Outermost

Tag

externalReferenceId

sendDetails

Field

/SyncItemBalanceListResponseEBM/DataArea/SyncItemBalanceListResponse/ItemIdentification/BusinessComponentID

ERP Sync Request ID. This is the unique ID sent as part of the response message to tie it together to the request. When WAM processes the request successfully, it only sends back the externalReferenceId, which is the ERP Sync Request ID.

externalIds

sendDetails

Group

entityIdList

externalIds

List

entity

entityIdList

externalPkValue1

entityIdList

Field

externalPkValue2

entityIdList

Field

externalPkValue3

entityIdList

Field

externalPkValue4

entityIdList

Field

externalPkValue5

entityIdList

Field

exceptionInformation

sendDetails

Group

When WAM encounters an error while processing the request, it sends back the externalReferenceId and the exeptionInformation.

exceptionInformationList

exceptionInformation

List

sequence

exceptionInformationList

Field

messageCategory

exceptionInformationList

Field

/SyncItemBalanceListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

messageNumber

exceptionInformationList

Field

/SyncItemBalanceListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

comments

exceptionInformationList

Field

/SyncItemBalanceListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Text

Error comments or error message

messageParameters

exceptionInformationList

List

parameterSequence

messageParameters

Field

messageParameterType

messageParameters

Field

messageParameterValue

messageParameters

Field

Material Issue Synchronization Process Mapping Details

This section provides data mapping details for the following:

•

Material Issue Request Mapping Details

•

Material Issue Response Mapping Details

Refer to the Material Issue - Inventory Transaction Synchronization Process description for processing details on this integration point.

Material Issue Request Mapping Details

ERP InventoryTransaction Request EBO Message

WAM Material Issue Service : W1-MaterialIssueIntegInbound

DVM Mapping

Comments

Full Path

Element Name

Parent Element

Type

W1-MaterialIssueIntegInbound

Outermost

Tag

syncRequestId

W1-MaterialIssueIntegInbound

Field

Not Mapped. Created internally in WAM on Add.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList (attribute name = actionCode)

ERP passes ' Material Issue' in the actionCode to indicate this record is related to a material issue since inventory transaction EBO is also used by other processes.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/Identification/BusinessComponentID

externalReferenceId

W1-MaterialIssueIntegInbound

Field

ERP Sync Request ID. This is a unique ID sent as part of the request message by the external system (ERP) initiating the sync request. This ID is used by the external system to tie together the response coming back to the ERP system from WAM.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/Identification/ApplicationObjectKey/ID

externalPkValue1

W1-MaterialIssueIntegInbound

Field

ERP Material Issue Line system generated ID. This is the Material Issue Line unique identifier.

externalSystem

W1-MaterialIssueIntegInbound

Field

Defaulted by Integration using property name OUWAM.External.System in the ConfigurationProperties file.

targetMo

W1-MaterialIssueIntegInbound

Field

Defaulted by Integration using property name OUWAM.MaterialIssue.Target.MO in the ConfigurationProperties file.

bo

W1-MaterialIssueIntegInbound

Field

Defaulted by Integration using property name OUWAM.MaterialIssue.BO in the ConfigurationProperties file.

integrationDetails

W1-MaterialIssueIntegInbound

Group

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/Identification/ApplicationObjectKey/ID

materialIssueLineExternalId

integrationDetails

Field

ERP Material Issue Line system generated ID. This is the Material Issue Line unique identifier.

materialIssueLineId

integrationDetails

Field

Not Mapped.Internal WAM system generated Material Issue Line ID.

boStatus

integrationDetails

Field

Not Mapped

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/SourceDocumentLineReference/DocumentIdentification/ApplicationObjectKey/ID

materialRequestHeaderId

integrationDetails

Field

WAM Material Requisition ID sent out on the Material Requisition Sync.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/SourceDocumentLineReference/DocumentLineIdentification/ApplicationObjectKey/ContextID

materialRequestLineId

integrationDetails

Field

WAM Material Requisition Line ID sent out on the Material Requisition Sync.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/InventoryLocationReference/LocationIdentification/ID

This is the ERP system’s organization number where the item is stock.

Example: In EBS, it is a unique 3 character organization number

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/InventoryLocationReference/LocationIdentification/ContextID

This is the ERP system’s subinventory name or subinventory ID where the item is stock.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/ItemReference/ItemIdentification/ApplicationObjectKey/ID

ERP system generated Stock Item ID which is the Stock Item's unique identifier.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/InventoryLocationReference/LocationIdentification/ID-nventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/InventoryLocationReference/LocationIdentification/ContextID-/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/ItemReference/ItemIdentification/ApplicationObjectKey/ID

stockItemDetailExternalId

integrationDetails

Field

This is the ERP Storeroom ID or Stock Item Detail. This ID is a concatenation of:

•

ERP's Inventory Organization Number,

•

ERP's Subinventory Name

•

ERP's Stock Item unique identifier with a dash (-) delimiter in between.

Example: 123-Sub1-987654321

stockItemDetailId

integrationDetails

Field

Not Mapped. Internal WAM system generated Stock Item Detail ID

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/InventoryTransactionLine/StartingSerialNumberID

assetId

integrationDetails

Field

This can be a serial number or lot number. If provided, it has to be a valid Asset ID in WAM.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/InventoryTransactionLine/TransactionLineQuantity

issuedQuantity

integrationDetails

Field

Quantity of item issued

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/ItemReference/SpecificationGroup/Specification/ValueAmount

unitPrice

integrationDetails

Field

Unit price of the item

totalCost

integrationDetails

Field

Not Mapped

Material Issue Response Mapping Details

WAM Material Issue Response Message

ERP InventoryTransaction List Response Message

Comments

Element Name

Parent Element

Type

Full Path

sendDetails

Outermost

Tag

externalReferenceId

sendDetails

Field

/SyncInventoryTransactionListResponseEBM/DataArea/SyncInventoryTransactionListResponse/Identification/BusinessComponentID

ERP Sync Request ID. This is the unique ID sent as part of the response message to tie it together to the request. When WAM process the request successfully, it only sends back the externalReferenceId, which is the ERP Sync Request ID.

externalIds

sendDetails

Group

entityIdList

externalIds

List

entity

entityIdList

externalPkValue1

entityIdList

Field

externalPkValue2

entityIdList

Field

externalPkValue3

entityIdList

Field

externalPkValue4

entityIdList

Field

externalPkValue5

entityIdList

Field

exceptionInformation

sendDetails

Group

When WAM encounteres an error while process the request, it sends back the externalReferenceId and the exeptionInformation.

exceptionInformationList

exceptionInformation

List

sequence

exceptionInformationList

Field

messageCategory

exceptionInformationList

Field

/SyncInventoryTransactionListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

messageNumber

exceptionInformationList

Field

/SyncInventoryTransactionListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

comments

exceptionInformationList

Field

SyncInventoryTransactionListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Text

Error comments or error message

messageParameters

exceptionInformationList

List

parameterSequence

messageParameters

Field

messageParameterType

messageParameters

Field

messageParameterValue

messageParameters

Field

Material Return Synchronization Process Mapping Details

This section provides data mapping details for the following:

•

Material Return Request Mapping Details

•

Material Return Response Mapping Details

Refer to the Material Return - Inventory Transaction Synchronization Process description for processing details on this integration point.

Material Return Request Mapping Details

ERP Inventory Transaction Request EBO Message

WAM Service : W1-MaterialReturnIntegInbound

DVM Mapping

Comments

Full Path

Element Name

Parent Element

Type

W1-MaterialReturnIntegInbound

Outermost

Tag

syncRequestId

W1-MaterialReturnIntegInbound

Field

Not Mapped. Created internally in WAM on Add.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList (attribute name = actionCode)

ERP passes ' Material Return' in the actionCode to indicate this record is related to a material return since inventory transaction EBO is also used by other processes.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/Identification/BusinessComponentID

externalReferenceId

W1-MaterialReturnIntegInbound

Field

ERP Sync Request ID. This is a unique ID sent as part of the request message by the external system (ERP) initiating the sync request. This ID is used by the external system to tie together the response coming back to the ERP system from WAM.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/Identification/ApplicationObjectKey/ID

externalPkValue1

W1-MaterialReturnIntegInbound

Field

ERP Material Return Line system generated ID. This is the Material Return Line unique identifier.

externalSystem

W1-MaterialReturnIntegInbound

Field

Defaulted by Integration using property name OUWAM.External.System in the ConfigurationProperties file.

targetMo

W1-MaterialReturnIntegInbound

Field

Defaulted by Integration using property name OUWAM.MaterialReturn.Target.MO in the ConfigurationProperties file.

bo

W1-MaterialReturnIntegInbound

Field

Defaulted by Integration using property name OUWAM.MaterialReturn.BO in the ConfigurationProperties file.

integrationDetails

W1-MaterialReturnIntegInbound

Group

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/Identification/ApplicationObjectKey/ID

materialReturnLineExternalId

integrationDetails

Field

ERP Material Return Line system generated ID. This is the Material Return Line unique identifier.

materialReturnLineId

integrationDetails

Field

Not Mapped.Internal WAM system generated Material Return Line ID.

materialReturnHeaderId

integrationDetails

Field

Not Mapped. Internal WAM system generated Material Return Header ID

creationUser

integrationDetails

Field

WAM Creation User is the User ID that creates the material return in WAM. Defaulted by Integration using property name OUWAM.Integration.User in the ConfigurationProperties file. This User ID must be a valid User ID in WAM.

boStatus

integrationDetails

Field

Not Mapped.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/TransactionDateTime

returnDate

integrationDetails

Field

Item Return Date. Required field in WAM.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/Description

returnBy

integrationDetails

Field

Item Returned By, this is a text field in WAM and is required. If not passed, WAM will default it from the creationUser.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/SourceDocumentReference/DocumentIdentification/ApplicationObjectKey/ID

materialIssueLineExternalId

integrationDetails

Field

ERP Material Issue Line system generated ID. This is the Material Issue Line unique identifier.

materialIssueLineId

integrationDetails

Field

Not Mapped.Internal WAM system generated Material Issue Line ID.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/InventoryLocationReference/LocationIdentification/ID

This is the ERP system’s organization number.

Example: In EBS, it is a unique 3 character organization number

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/InventoryLocationReference/LocationIdentification/ContextID

This is the ERP system’s subinventory name or subinventory ID.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/ItemReference/ItemIdentification/ApplicationObjectKey/ID

ERP system generated Stock Item ID which is the Stock Item's unique identifier.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/InventoryLocationReference/LocationIdentification/ID-nventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/InventoryLocationReference/LocationIdentification/ContextID-/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/ItemReference/ItemIdentification/ApplicationObjectKey/ID

stockItemDetailExternalId

integrationDetails

Field

This is the ERP Storeroom ID or Stock Item Detail. This ID is a concatenation of:

•

ERP's Inventory Organization Number,

•

ERP's Subinventory Name

•

ERP's Stock Item unique identifier with a dash (-) delimiter in between.

Example: 123-Sub1-987654321

stockItemDetailId

integrationDetails

Field

Not Mapped

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/InventoryTransactionLine/StartingSerialNumberID

assetId

integrationDetails

Field

This can be a serial number or lot number.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/InventoryTransactionLine/TransactionLineQuantity

returnQuantity

integrationDetails

Field

acceptedQuantity

integrationDetails

Field

Not Mapped

expenseCode

integrationDetails

Field

Not Mapped

repaired

integrationDetails

Field

Not Mapped

totalCost

integrationDetails

Field

Not Mapped

accountingInfomation

integrationDetails

Group

costCenterList

accountingInformation

List

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/GLAccount/Identification/ID

glAccount

costCenterList

Field

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/GLAccount/GLElement(1)/GLElement

segment1

costCenterList

Field

GL elements are a sequenced set of account codes that form a Chart Of Accounts Code or GL Account

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/GLAccount/GLElement(2)/GLElement

segment2

costCenterList

Field

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/GLAccount/GLElement(3)/GLElement

segment3

costCenterList

Field

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/GLAccount/GLElement(4)/GLElement

segment4

costCenterList

Field

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/GLAccount/GLElement(5)/GLElement

segment5

costCenterList

Field

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/GLAccount/GLElement(6)/GLElement

segment6

costCenterList

Field

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/GLAccount/GLElement(7)/GLElement

segment7

costCenterList

Field

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/GLAccount/GLElement(8)/GLElement

segment8

costCenterList

Field

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/GLAccount/GLElement(9)/GLElement

segment9

costCenterList

Field

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/GLAccount/GLElement(10)/GLElement

segment10

costCenterList

Field

costCenter

costCenterList

Field

Not Mapped

expenseCode

costCenterList

Field

Not Mapped

percentage

costCenterList

Field

Defaulted by Integration using property name OUWAM.MaterialReturn.Percentage in the ConfigurationProperties file. Defaulted to 100

Material Return Response Mapping Details

WAM Material Return Response Message

ERP InventoryTransaction List Response Message

Comments

Element Name

Parent Element

Type

Full Path

sendDetails

Outermost

Tag

externalReferenceId

sendDetails

Field

/SyncInventoryTransactionListResponseEBM/DataArea/SyncInventoryTransactionListResponse/Identification/BusinessComponentID

ERP Sync Request ID. This is the unique ID sent as part of the response message to tie it together to the request. When WAM process the request successfully, it only sends back the externalReferenceId, which is the ERP Sync Request ID.

externalIds

sendDetails

Group

entityIdList

externalIds

List

entity

entityIdList

externalPkValue1

entityIdList

Field

externalPkValue2

entityIdList

Field

externalPkValue3

entityIdList

Field

externalPkValue4

entityIdList

Field

externalPkValue5

entityIdList

Field

exceptionInformation

sendDetails

Group

When WAM encounteres an error while process the request, it sends back the externalReferenceId and the exeptionInformation.

exceptionInformationList

exceptionInformation

List

sequence

exceptionInformationList

Field

messageCategory

exceptionInformationList

Field

/SyncInventoryTransactionListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

messageNumber

exceptionInformationList

Field

/SyncInventoryTransactionListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

comments

exceptionInformationList

Field

SyncInventoryTransactionListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Text

Error comments or error message

messageParameters

exceptionInformationList

List

parameterSequence

messageParameters

Field

messageParameterType

messageParameters

Field

messageParameterValue

messageParameters

Field

Purchase Order Synchronization Process Mapping Details

This section provides data mapping details for the following:

•

Purchase Order Request Mapping Details

•

Purchase Order Response Mapping Details

Refer to the Purchase Order Synchronization Process description for processing details on this integration point.

Purchase Order Request Mapping Details

ERP Purchase Order Request EBO Message

WAM BO MESSAGE: W1-PurchaseOrderIntegInbound IWS: W1-PurchaseOrderIntegInbound

DVM Mapping

Comments

Full Path

Element Name

Parent Element

Type

W1-PurchaseOrderIntegInbound

Outermost

Tag

integrationId

W1-PurchaseOrderIntegInbound

Field

Not Mapped. Created internally in WAM on Add.

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/Identification/BusinessComponentID

externalReferenceId

W1-PurchaseOrderIntegInbound

Field

ERP Sync Request ID. This is a unique ID sent as part of the request message by the external system (ERP) initiating the sync request. This ID is used by the external system to tie together the response coming back to ERP from WAM.

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/Identification/ApplicationObjectKey/ID

externalPkValue1

W1-PurchaseOrderIntegInbound

Field

ERP system generated Purchase Order Header ID. This is the Purchase Order Table's unique identifier.

externalSystem

W1-PurchaseOrderIntegInbound

Field

Defaulted by Integration using property name OUWAM.External.System in the ConfigurationProperties file.

bo

W1-PurchaseOrderIntegInbound

Field

Defaulted by Integration using property name OUWAM.PO.BO in the ConfigurationProperties file.

targetMo

W1-PurchaseOrderIntegInbound

Field

Defaulted by Integration using property name OUWAM.PO.Target.MO in the ConfigurationProperties file.

integrationDetails

W1-PurchaseOrderIntegInbound

Group

headerInformation

integrationDetails

Group

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/Identification/ApplicationObjectKey/ID

poHeaderExternalId

headerInformation

Field

ERP system generated Purchase Order Header ID. This is the Purchase Order Table's unique system generated ID.

purchaseOrderHeaderId

headerInformation

Field

Not Mapped. Internal WAM system generated Purchase Order Header ID created on Add.

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/Status/Code

boStatus

headerInformation

Field

OUWAMERP_POStatus

ERP sends the PO to WAM when the status is APPROVED/ ISSUED or when the PO status is changed to CLOSED.

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/Identification/ID

purchaseOrderNumber

headerInformation

Field

Purchase Order Number is the same for both WAM and the ERP system.

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/Identification/Revision/Number

revisionNumber

headerInformation

Field

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/SupplierPartyReference/OrganizationName

description

headerInformation

Field

This will contain the vendor contact information

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/OrderDateTIme

creationDateTime

headerInformation

Field

poCreatedBy

headerInformation

Field

Defaulted by Integration using property name OUWAM.Integration.POCreatedBy in the ConfigurationProperties file.

finalDateTime

headerInformation

Group

Not Mapped.

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/RequisitionLineReference/RequisitionIdentification/ApplicationObjectKey/ID

purchaseRequisitionHeaderId

lineInfomationList

Field

WAM Purchase Requisition ID sent in the Requisition Sync should be pass back in the PO Sync.

initiator

headerInformation

Field

Not Mapped.

requestedByUser

headerInformation

Field

Not Mapped. This is derived from The WAM Requisition. This is the requestor's name.

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/BuyerPartyReference/Contact/ContactPhoneCommunication/PhoneCommunication/CompleteNumber

buyerPhoneNumber

headerInformation

Field

This is the complete phone number without separation between country code, area code etc.

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/BuyerPartyReference/PartyIdentification/ID

buyer

headerInformation

Field

OUWAMERP_Buyer

This is the buyer ID. ERP passes a valid ERP Buyer ID.

Example: In EBS, this should be a valid HR record. Integration uses DVM to map to the valid WAM Buyer ID.

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/OrderDateTIme

requestDate

headerInformation

Field

Only the date portion is mapped

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/Status/EffectiveDateTime

issueDate

headerInformation

Field

This is the approval date or the issue date

requiredDate

headerInformation

Field

Not Mapped

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/ShipToPartyReference/LocationReference/LocationIdentification/ID

shipToLocation

headerInformation

Field

OUWAMERP_LocationId

ERP passes a valid ERP location ID. Integration uses DVM to map to the valid WAM location ID.

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/PurchaseOrderShipment/ShipmentDistribution/DeliverToPartyReference/LocationReference/LocationIdentification/ID

deliverToLocation

headerInformation

Field

OUWAMERP_LocationId

ERP passes a valid ERP location ID. Integration uses DVM to map to the valid WAM location ID. Map the first PO line's deliver to location.

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/PurchaseOrderShipment/ShipmentDistribution/DeliverToPartyReference/PartyIdentification/OrganizationName

deliverTo

headerInformation

Field

Map the first PO line's deliver to contact.

vendorLocation

headerInformation

Field

Not Mapped. WAM Vendor Location ID

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/SupplierPartyReference/LocationReference/LocationIdentification/ApplicationObjectKey/ID

vendorLocationExternalId

headerInformation

Field

ERP Vendor Location ID or ERP Vendor Site ID. This has to be a valid vendor location in WAM. Supplier Party Sync from the ERP system to WAM must be done first.

vendorContact

headerInformation

Field

Not Mapped. This has to be a valid Contact ID in WAM, the value is derived in WAM.

location

headerInformation

Group

Vendor Location Address Information.

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/SupplierPartyReference/LocationReference/Address/LineOne

address1

location

Field

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/SupplierPartyReference/LocationReference/Address/LineTwo

address2

location

Field

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/SupplierPartyReference/LocationReference/Address/LineThree

address3

location

Field

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/SupplierPartyReference/LocationReference/Address/LineFour

address4

location

Field

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/SupplierPartyReference/LocationReference/Address/CityName

city

location

Field

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/SupplierPartyReference/LocationReference/Address/StateName

state

location

Field

OUWAMERP_State

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/SupplierPartyReference/LocationReference/Address/CountyName

county

location

Field

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/SupplierPartyReference/LocationReference/Address/CountryName

country

location

Field

OUWAMERP_Country

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/SupplierPartyReference/LocationReference/Address/PostalCode

postal

location

Field

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/CurrencyExchange/ConversionRate

exchangeRate

headerInformation

Field

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/CurrencyExchange/SourceCurrencyCode

currency

headerInformation

Field

OUWAMERP_CurrencyCode

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/FOBCode

freeOnBoard

headerInformation

Field

OUWAMERP_FOB

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PaymentTerm/Code

paymentTerms

headerInformation

Field

OUWAMERP_PaymentTerm

automaticPay

headerInformation

Field

Not Mapped. Defaulted in WAM. This wil be obtained from the vendor location's autopay value.

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseAgreementReference/PurchaseAgreementIdentification/ApplicationObjectKey/ID

blanketContractHeaderId

headerInformation

Field

ERP system generated Blanket Contract or Blanket Purchase Agreement ID which is the Blanket Contract Table's unique identifier. This blanket contract should exist in the WAM system. Blanket Purchase Agreement Sync from the ERP system to WAM must be done first.

projectId

headerInformation

Field

Not Mapped

purchaseDocumentType

headerInformation

Field

lineInfomation

integrationDetails

Group

lineInfomationList

lineInfomation

List

Loop through the PurchaseOrderLine List if there is more that one PO Line.

purchaseOrderLineId

lineInfomationList

Field

Not Mapped. Internal WAM system generated Purchase Order Line ID created on Add.

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/Identification/ApplicationObjectKey/ID

poLineExternalId

lineInfomationList

Field

ERP Purchase Order Line system generated ID. This is the PO Line Table's unique identifier.

purchaseOrderHeaderId

lineInfomationList

Field

Not Mapped. Derived in WAM.

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/Status/Code

boStatus

lineInfomationList

Field

OUWAMERP_POLineStatus

ERP sends the PO Lines to WAM when the status is APPROVED/ISSUED or when the PO Line status is CLOSED. The PO Header and Lines status should match.

resourceTypeId

lineInfomationList

Field

Not Mapped. WAM's system generated resourceType ID

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/ItemReference/ItemIdentification/ApplicationObjectKey/ID

resourceTypeExternalId

lineInfomationList

Field

ERP's system generated stock Item code/ID. This is the Item Table's unique identifier. If the stock item or resource does not exist in the ERP, leave this blank and only pass the item description. If the stock item exist in the ERP, do not populate the item description.

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/ItemReference/ItemIdentification/Description

description

lineInfomationList

Field

Item description

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/RequisitionLineReference/RequisitionIdentification/ApplicationObjectKey/ID

purchaseRequisitionHeaderId

lineInfomationList

Field

WAM Purchase Requisition ID sent on the Requisition Sync.

Note: RequisitionLIneReference is a new reference added in the PO EBO.

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/RequisitionLineReference/RequisitionLineIdentification/ApplicationObjectKey/ContextID

purchaseRequisitionLineId

lineInfomationList

Field

WAM Purchase Requisition Line ID sent on the Requisition Sync. Note: RequisitionLIneReference is a new reference added in the PO EBO.

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/PurchaseAgreementPriceBreakReference/PurchaseAgreementLineIdentification/ApplicationObjectKey/ID

blanketContractLineId

lineInfomationList

Field

ERP system generated Blanket Contract Line or Blanket Purchase Agreement Line Id which is the Blanket Contract Line Table's unique identifier. This blanket contract line should exist in the WAM system. Blanket Purchase Agreement Sync from ERP to WAM must be done first.

lastUpdateRevison

lineInfomationList

Field

Not Mapped

finalDateTime

lineInfomationList

Field

Not Mapped

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/ItemReference/TypeCode

itemType

lineInfomationList

Field

OUWAMERP_ItemType

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/Quantity

quantity

lineInfomationList

Field

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/UnitPurchasePrice/Amount

unitprice

lineInfomationList

Field

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/UnitPurchasePrice/PerQuantity

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/UnitPurchasePrice/PerQuantity (attribute name = unitCode)

unitOfPurchase

lineInfomationList

Field

OUWAMERP_UOMCode

purchaseToIssueRatio

lineInfomationList

Field

Not Mapped

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLIne/PurchaseOrderShipment/RequiredByDate

requiredDate

lineInfomationList

Field

promiseDate

lineInfomationList

Field

Not Mapped

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/ItemReference/ItemIdentification/SupplierItemID

vendorpartNumber

lineInfomationList

Field

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/PurchaseOrderShipment/ShipmentDistribution/AccountingDistribution/ProjectReference/ProjectIdentfication/ApplicationObjectKey/ID

projectId

lineInfomationList

Field

WAM Project ID

accountingInfomation

lineInfomationList

Group

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/PurchaseOrderShipment/ShipmentDistribution

costCenterList

accountingInformation

List

Loop through the ShipmentDistribution List if there is more than one glAccount.

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/PurchaseOrderShipment/ShipmentDistribution/AccountingDistribution/GLAccount/Identification/ID

glAccount

costCenterList

Field

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/PurchaseOrderShipment/ShipmentDistribution/AccountingDistribution/GLAccount/GLElement(1)/GLElement

segment1

costCenterList

Field

GL elements are a sequenced set of account codes that form a Chart Of Accounts Code or GL Account

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/PurchaseOrderShipment/ShipmentDistribution/AccountingDistribution/GLAccount/GLElement(2)/GLElement

segment2

costCenterList

Field

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/PurchaseOrderShipment/ShipmentDistribution/AccountingDistribution/GLAccount/GLElement(3)/GLElement

segment3

costCenterList

Field

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/PurchaseOrderShipment/ShipmentDistribution/AccountingDistribution/GLAccount/GLElement(4)/GLElement

segment4

costCenterList

Field

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/PurchaseOrderShipment/ShipmentDistribution/AccountingDistribution/GLAccount/GLElement(5)/GLElement

segment5

costCenterList

Field

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/PurchaseOrderShipment/ShipmentDistribution/AccountingDistribution/GLAccount/GLElement(6)/GLElement

segment6

costCenterList

Field

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/PurchaseOrderShipment/ShipmentDistribution/AccountingDistribution/GLAccount/GLElement(7)/GLElement

segment7

costCenterList

Field

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/PurchaseOrderShipment/ShipmentDistribution/AccountingDistribution/GLAccount/GLElement(8)/GLElement

segment8

costCenterList

Field

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/PurchaseOrderShipment/ShipmentDistribution/AccountingDistribution/GLAccount/GLElement(9)/GLElement

segment9

costCenterList

Field

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/PurchaseOrderShipment/ShipmentDistribution/AccountingDistribution/GLAccount/GLElement(10)/GLElement

segment10

costCenterList

Field

costCenter

costCenterList

Field

Not Mapped

expenseCode

costCenterList

Field

Not Mapped

/SyncPurchaseOrderListEBM/DataArea/SyncPurchaseOrderList/PurchaseOrderLine/PurchaseOrderShipment/ShipmentDistribution/AccountingDistribution/Percentage

percentage

costCenterList

Field

taxLines

Group

/SyncPurchaseOrderListEBM/DataArea/Sync PurchaseOrderList/PurchaseOrderLine/Purchase OrderLineTaxTotal

taxLinesList

taxLines

List

Loop through the PurchaseOrderLineTaxTotal List if there are more than one Purchase Order Line tax total.

seq

taxLinesList

Field

Defaulted by the Integration

/SyncPurchaseOrderListEBM/DataArea/Sync PurchaseOrderList/PurchaseOrderLine/Purchase OrderLineTaxTotal/TypeCode

charType

taxLinesList

Field

OUWAMERP_TaxType

Identifies the type of tax (Example: State Tax)

/SyncPurchaseOrderListEBM/DataArea/Sync PurchaseOrderList/PurchaseOrderLine/Purchase OrderLineTaxTotal/Identification/ID

charValue

taxLinesList

Field

OUWAMERP_TaxType Value

Tax type value (Example: CA)

/SyncPurchaseOrderListEBM/DataArea/Sync PurchaseOrderList/PurchaseOrderLine/Purchase OrderLineTaxTotal/Amount

taxAmount

taxLinesList

Field

Total amount for a given type of tax.

/SyncPurchaseOrderListEBM/DataArea/Sync PurchaseOrderList/PurchaseOrderLine/Ordered Amount

lineAmount

lineInfomationList

Field

Purchase Order Line Ordered Amount. It can be the amount calculated based on order quantity and price or the service amount

/SyncPurchaseOrderListEBM/DataArea/Sync PurchaseOrderList/PurchaseOrderLine/Total Amount

lineTotal

lineInfomationList

Field

Total amount of the purchase order line, including the OrderedAmount and the total of all taxes

Purchase Order Response Mapping Details

WAM PO Response Message

ERP Sync Purchase Order List Response Message

Comments

Element Name

Parent Element

Type

Full Path

sendDetails

Outermost

Tag

externalReferenceId

sendDetails

Field

/SyncPurchaseOrderListResponseEBM/DataArea/SyncPurchaseOrderListResponse/Identification/BusinessComponentID

ERP Sync Request ID. This is the unique ID sent as part of the response message to tie it together to the request. When WAM processes the request successfully, it only sends back the externalReferenceId, which is the ERP Sync Request ID.

externalIds

sendDetails

Group

entityIdList

externalIds

List

entity

entityIdList

externalPkValue1

entityIdList

Field

externalPkValue2

entityIdList

Field

externalPkValue3

entityIdList

Field

externalPkValue4

entityIdList

Field

externalPkValue5

entityIdList

Field

exceptionInformation

sendDetails

Group

When WAM encounters an error while processing the request, it sends back the externalReferenceId and the exeptionInformation.

exceptionInformationList

exceptionInformation

List

sequence

exceptionInformationList

Field

messageCategory

exceptionInformationList

Field

/SyncPurchaseOrderListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

messageNumber

exceptionInformationList

Field

/SyncPurchaseOrderListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

comments

exceptionInformationList

Field

SyncPurchaseOrderListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Text

Error comments or error message

messageParameters

exceptionInformationList

List

parameterSequence

messageParameters

Field

messageParameterType

messageParameters

Field

messageParameterValue

messageParameters

Field

Shipment Receipt (Purchase Receipt) Synchronization Process Mapping Details

This section provides data mapping details for the following:

•

Shipment Receipt (Purchase Receipt) Request Mapping Details

•

Shipment Receipt (Purchase Receipt) Response Mapping Details

Refer to the Shipment Receipt (Purchase Receipt) Synchronization Process description for processing details on this integration point.

Shipment Receipt (Purchase Receipt) Request Mapping Details

ERP Shipment Receipt Request EBO Message

WAM Service: W1-ReceiptIntegInbound

DVM Mapping

Comments

Full Path

Element Name

Parent Element

Type

W1-ReceiptIntegInbound

Outermost

Tag

syncRequestId

W1-ReceiptIntegInbound

Field

Not Mapped. Created internally in WAM on Add.

/SyncShipmentReceiptListEBM/DataArea/SyncShipmentReceiptList/Identification/BusinessComponentID

externalReferenceId

W1-ReceiptIntegInbound

Field

ERP Sync Request ID. This is a unique ID sent as part of the request message by the external system (ERP) initiating the sync request. This ID is used by the external system to tie together the response coming back to ERP from WAM.

/SyncShipmentReceiptListEBM/DataArea/SyncShipmentReceiptList/Identification/ApplicationObjectKey/ID

externalPkValue1

W1-ReceiptIntegInbound

Field

ERP system generated Receipt Header ID. This is the Receipt Table's uniqueidentifier.

externalSystem

W1-ReceiptIntegInbound

Field

Defaulted by Integration using property name OUWAM.External.System in the ConfigurationProperties file.

bo

W1-ReceiptIntegInbound

Field

Defaulted by Integration using property name OUWAM.Receipt.BO in the ConfigurationProperties file.

targetMo

W1-ReceiptIntegInbound

Field

Defaulted by Integration using property name OUWAM.Receipt.Target.MO in the ConfigurationProperties file.

integrationDetails

W1-ReceiptIntegInbound

Group

headerInformation

integrationDetails

Group

/SyncShipmentReceiptListEBM/DataArea/SyncShipmentReceiptList/Identification/ApplicationObjectKey/ID

receiptHeaderExternalId

headerInformation

Field

ERP system generated Purchase Receipt Header ID. This is the Purchase Receipt Table's unique identifier.

receiptHeaderId

headerInformation

Field

Not Mapped. Internal WAM system generated Receipt Header ID created on Add.

boStatus

headerInformation

Field

Not Mapped. ERP sends the Receipt once it is completed. Status is defaulted in WAM.

/SyncShipmentReceiptListEBM/DataArea/SyncShipmentReceiptList/AuditHistory/CreatedDateTime

creationDateTime

headerInformation

Field

finalDateTime

headerInformation

Group

Not Mapped

/SyncShipmentReceiptListEBM/DataArea/SyncShipmentReceiptList/Comment

description

headerInformation

Field

Purchase Receipt description or comment

/SyncShipmentReceiptListEBM/DataArea/SyncShipmentReceiptList/ShipmentReceiptLine/PurchaseOrderReference/Identification/ApplicationObjectKey/ID

purchaseOrderHeaderExternalId

headerInformation

Field

ERP system generated Purchase Order ID which is the ERP Purchase Order Table's unique identifier. This is the Purchase Order referenced by the purchase or shipment receipt.

purchaseOrderHeaderId

headerInformation

Field

Not Mapped. Internal WAM system generated Purchase Order Header ID.

/SyncShipmentReceiptListEBM/DataArea/SyncShipmentReceiptList/ShipmentReceiptLine/PurchaseOrderReference/Identification/ID

purchaseOrderNumber

headerInformation

Field

Purchase Order Number reference by the purchase or shipment receipt. This number is the same in ERP and WAM.

/SyncShipmentReceiptListEBM/DataArea/SyncShipmentReceiptList/ShipmentReceiptLine/PurchaseOrderReference/Identification/Revision/Number

poRevisionNumber

headerInformation

Field

Purchase Order Revision Number reference by the purchase or shipment receipt.

lineInfomation

integrationDetails

Group

/SyncShipmentReceiptListEBM/DataArea/SyncShipmentReceiptList/ShipmentReceiptLine

lineInfomationList

lineInfomation

List

Loop through the ShipmentReceiptLine List if there is more that one Shipment Receipt Line.

/SyncShipmentReceiptListEBM/DataArea/SyncShipmentReceiptList/ShipmentReceiptLine/Identification/ApplicationObjectKey/ID

receiptLineExternalId

lineInfomationList

Field

ERP system generated Receipt Line ID. This is the Purchase Receipt Line Table's unique identifier.

receiptLineId

lineInfomationList

Field

Not Mapped. Internal WAM system generated Receipt Line ID created on Add.

boStatus

lineInfomationList

Field

Not Mapped

receiptHeaderExternalId

lineInfomationList

Field

receiptHeaderId

lineInfomationList

Field

Not Mapped. Derive in WAM.

/SyncShipmentReceiptListEBM/DataArea/SyncShipmentReceiptList/AuditHistory/CreatedDateTime

creationDateTime

finalDateTime

lineInfomationList

Field

Not Mapped

purchaseOrderLineExternalId

lineInfomationList

Field

ERP system generated Purchase Order Line ID which is the ERP Purchase Order Line Table's unique identifier. This is the Purchase Order Line referenced by the purchase or shipment receipt line.

purchaseOrderLineId

lineInfomationList

Field

Not Mapped. Internal WAM system generated Purchase Order Line ID.

stockItemDetailExternalId

lineInfomationList

Field

Not Mapped

stockItemDetailId

lineInfomationList

Field

Not Mapped

/SyncShipmentReceiptListEBM/DataArea/SyncShipmentReceiptList/ItemReference/ItemIdentification/ApplicationObjectKey/ID

resourceTypeExternalId

lineInfomationList

Field

ERP's system generated stock Item code/ID. This is the Item Table's unique identifier. This field is populated if the item received by the ERP is a stock item. For received non-stock items, the item description is obtained from the PO line.

resourceTypeId

lineInfomationList

Field

Not Mapped. WAM's system generated resourceType ID

storageLocationId

lineInfomationList

Field

Not mapped. This value is derived by WAM.

unitOfPurchase

lineInfomationList

Field

OUWAMERP_UOMCode

Unit of Purchase

quantity

lineInfomationList

Field

Quantity received

Shipment Receipt (Purchase Receipt) Response Mapping Details

WAM Receipt Response Message

ERP Sync Inventory Transaction List Response Message (Receipt)

Comments

Element Name

Parent Element

Type

Full Path

sendDetails

Outermost

Tag

externalReferenceId

sendDetails

Field

/SyncInventoryTransactionListResponseEBM/DataArea/SyncInventoryTransactionListResponse/Identification/BusinessComponentID

ERP Sync Request ID. This is the unique ID sent as part of the response message to tie it together to the request. When WAM processes the request successfully, it only sends back the externalReferenceId, which is the ERP Sync Request ID.

externalIds

sendDetails

Group

entityIdList

externalIds

List

entity

entityIdList

externalPkValue1

entityIdList

Field

externalPkValue2

entityIdList

Field

externalPkValue3

entityIdList

Field

externalPkValue4

entityIdList

Field

externalPkValue5

entityIdList

Field

exceptionInformation

sendDetails

Group

When WAM encounters an error while processing the request, it sends back the externalReferenceId and the exeptionInformation.

exceptionInformationList

exceptionInformation

List

sequence

exceptionInformationList

Field

messageCategory

exceptionInformationList

Field

/SyncInventoryTransactionListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

messageNumber

exceptionInformationList

Field

/SyncInventoryTransactionListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

comments

exceptionInformationList

Field

SyncInventoryTransactionListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Text

Error comments or error message

messageParameters

exceptionInformationList

List

parameterSequence

messageParameters

Field

messageParameterType

messageParameters

Field

messageParameterValue

messageParameters

Field

Purchase Return Synchronization Process Mapping Details

This section provides data mapping details for the following:

•

Purchase Return Request Mapping Details

•

Purchase Return Response Mapping Details

Refer to the Purchase Return - Inventory Transaction Synchronization Process description for processing details on this integration point.

Purchase Return Request Mapping Details

ERP Inventory Transaction Request EBO Message

WAM Service : W1-PurchaseReturnIntegInbound

DVM Mapping

Comments

Full Path

Element Name

Parent Element

Type

W1-PurchaseReturnIntegInbound

Outermost

Tag

syncRequestId

W1-PurchaseReturnIntegInbound

Field

Not Mapped. Created internally in WAM on Add.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList (attribute name = actionCode)

The ERP system passes 'Purchase Return' in the actionCode to indicate this record is related to a purchase return since inventory transaction EBO is also used by other processes.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/Identification/BusinessComponentID

externalReferenceId

W1-PurchaseReturnIntegInbound

Field

ERP Sync Request ID. This is a unique ID sent as part of the request message by the external system (ERP) initiating the sync request. This ID is used by the external system to tie together the response coming back to ERP from WAM.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/Identification/ApplicationObjectKey/ID

externalPkValue1

W1-PurchaseReturnIntegInbound

Field

ERP Purchase Return Line system generated ID. This is the Purchase Return Line unique identifier.

externalSystem

W1-PurchaseReturnIntegInbound

Field

Defaulted by Integration using property name OUWAM.External.System in the ConfigurationProperties file.

targetMo

W1-PurchaseReturnIntegInbound

Field

Defaulted by Integration using property name OUWAM.PurchaseReturn.Target.MO in the ConfigurationProperties file.

bo

W1-PurchaseReturnIntegInbound

Field

Defaulted by Integration using property name OUWAM.PurchaseReturn.BO in the ConfigurationProperties file.

integrationDetails

W1-PurchaseReturnIntegInbound

Group

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/Identification/ApplicationObjectKey/ID

returnLineExternalId

integrationDetails

Field

ERP Purchase Return Line system generated ID. This is the Purchase Return Line unique identifier.

returnLineId

integrationDetails

Field

Not Mapped.Internal WAM system generated Purchase Return Line ID.

boStatus

integrationDetails

Field

Not Mapped.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/SourceDocumentReference/DocumentIdentification/ApplicationObjectKey/ID

poLineExternalId

integrationDetails

Field

ERP system generated Purchase Order Line ID. This is the ERP Purchase Order Line Table's unique identifier. This is the Purchase Order Line referenced by the purchase return line.

purchaseOrderLineId

Not Mapped. Internal WAM system generated Purchase Order Line ID

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/SourceDocumentReference/DocumentIdentification/ApplicationObjectKey/ContextID

receiptLineExternalId

integrationDetails

Field

ERP Purchase Receipt Line system generated ID which is the Purchase receipt Line Table's unique identifier. This is the Purchase Receipt Line referenced by the purchase return line.

receiptLineId

integrationDetails

Field

Not Mapped.Internal WAM system generated Purchase Receipt Line ID.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/InventoryLocationReference/LocationIdentification/ID

This is the ERP system’s organization number.

Example: In EBS, it is a unique 3 character organization number

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/InventoryLocationReference/LocationIdentification/ContextID

This is the ERP system’s subinventory name or subinventory ID

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/ItemReference/ItemIdentification/ApplicationObjectKey/ID

ERP system generated Stock Item ID which is the Stock Item's unique identifier.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/InventoryLocationReference/LocationIdentification/ID-nventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/InventoryLocationReference/LocationIdentification/ContextID-/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/ItemReference/ItemIdentification/ApplicationObjectKey/ID

stockItemDetailExternalId

integrationDetails

Field

This is the ERP Storeroom ID or Stock Item Detail. This ID is a concatenation of:

ERP's Inventory Organization Number,

ERP's Subinventory Name and

ERP’s system's Stock Item unique identifier with a dash (-) delimiter in between.

Example: 123-Sub1-987654321. This field is not always populated. If the purchase being returned is not a stock item, then this is left blank.

stockItemDetailId

integrationDetails

Field

Not Mapped

typeOfReturn

Possible WAM values are credit or exchange. Defaulted by Integration using property name OUWAM.ReturnType in the ConfigurationProperties file. Defaulted to the Credit value.

typeOfAdjustment

Possible WAM values are Inventory (W1IN) or In Receipt (W1IR). Defaulted by Integration using property name OUWAM.AdjustmentType in the ConfigurationProperties file. Defaulted to In receipt value.

/SyncInventoryTransactionListEBM/DataArea/SyncInventoryTransactionList/InventoryTransactionLine/TransactionLineQuantity

quantity

integrationDetails

Field

assetInfo

integrationDetails

Group

Whole group not mapped

assetGroup

assetInfo

Group

rejectionLocationId

assetGroup

Field

assetList

assetGroup

List

assetId

assetList

Field

lotInfo

integrationDetails

Group

Whole group not mapped

lotGroup

lotInfo

Group

lotList

lotGroup

List

stockItemDetailExternalId

lotList

Field

stockItemDetailId

lotList

Field

quantity

lotList

Field

Purchase Return Response Mapping Details

WAM Purchase Return Response Message

ERP Inventory Transaction Response Message

Comments

Element Name

Parent Element

Type

Full Path

sendDetails

Outermost

Tag

externalReferenceId

sendDetails

Field

/SyncInventoryTransactionListResponseEBM/DataArea/SyncInventoryTransactionListResponse/Identification/BusinessComponentID

ERP Sync Request ID. This is the unique ID sent as part of the response message to tie it together to the request. When WAM processes the request successfully, it only sends back the externalReferenceId, which is the ERP Sync Request ID.

externalIds

sendDetails

Group

entityIdList

externalIds

List

entity

entityIdList

externalPkValue1

entityIdList

Field

externalPkValue2

entityIdList

Field

externalPkValue3

entityIdList

Field

externalPkValue4

entityIdList

Field

externalPkValue5

entityIdList

Field

exceptionInformation

sendDetails

Group

When WAM encounters an error while processing the request, it sends back the externalReferenceId and the exeptionInformation.

exceptionInformationList

exceptionInformation

List

sequence

exceptionInformationList

Field

messageCategory

exceptionInformationList

Field

/SyncInventoryTransactionListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

messageNumber

exceptionInformationList

Field

/SyncInventoryTransactionListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

comments

exceptionInformationList

Field

SyncInventoryTransactionListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Text

Error comments or error message

messageParameters

exceptionInformationList

List

parameterSequence

messageParameters

Field

messageParameterType

messageParameters

Field

messageParameterValue

messageParameters

Field

Stock Item Synchronization Process Mapping Details

This section provides data mapping details for the following:

•

Stock Item Request Mapping Details

•

Stock Item Response Mapping Details

Refer to the Stock Item Synchronization Process description for processing details on this integration point.

Stock Item Request Mapping Details

ERP Item Request EBO Message

WAM BO MESSAGE: W1-OngoingSyncRequestStockItem

DVM Mapping

Comments

Full Path

Element Name

Parent Element

Type

W1-SyncRequestInbound

Outermost

Tag

syncRequestId

W1-SyncRequestInbound

Field

Not Mapped. This is a WAM system generated ID created internally in WAM on Add.

/SyncItemListEBM/DataArea/SyncItemList/ItemIdentification/BusinessComponentID

externalReferenceId

W1-SyncRequestInbound

Field

ERP Sync Request ID. This is a unique ID sent as part of the request message by the external system (ERP) initiating the sync request. This ID is used by the external system to tie together the response coming back to ERP from WAM.

/SyncItemListEBM/DataArea/SyncItemList/ItemIdentification/ApplicationObjectKey/ID

externalPkValue1

W1-SyncRequestInbound

Field

ERP's unique system generated Item ID. The Item Table's unique identifier.

externalSystem

W1-SyncRequestInbound

Field

Defaulted by Integration using property name OUWAM.External.System in the ConfigurationProperties file.

targetMo

W1-SyncRequestInbound

Field

Defaulted by Integration using property name OUWAM.StockItem.Target.MO in the ConfigurationProperties file.

initialLoad

W1-SyncRequestInbound

Field

Defaulted by Integration using property name OUWAM.InitialLoad.Flag in the ConfigurationProperties file.

syncRequestDetails

W1-SyncRequestInbound

original

syncRequestDetails

Group

finalSnapshot

original

Group

/SyncItemListEBM/DataArea/SyncItemList/ItemIdentification/ApplicationObjectKey/ID

resourceTypeExternalId

finalSnapshot

Field

ERP's unique system generated Item ID. The Item Table's unique identifier.

resourceTypeId

finalSnapshot

Field

Not Mapped. This is a WAM system generated ID created internally in WAM on Add.

/SyncItemListEBM/DataArea/SyncItemList/Status/Code

boStatus

finalSnapshot

Field

OUWAMERP_StockItemStatus

Stock Item Status. Use DVM to translate the ERP status to the equivalent WAM Status.

resourceClass

finalSnapshot

Field

Not Mapped. Defaulted to Material in WAM on Add. WAM values: Craft, Material, Equipment and Others

/SyncItemListEBM/DataArea/SyncItemList/ShortDescription

description

finalSnapshot

Field

Item description

/SyncItemListEBM/DataArea/SyncItemList/Description

longDescription

finalSnapshot

Field

Item long description

/SyncItemListEBM/DataArea/SyncItemList/ItemIdentification/ID

stockItem

finalSnapshot

Field

ERP Item Number.

inventoryExpenseCode

finalSnapshot

Field

Defaulted by Integration using property name OUWAM.InventoryExpense.Code in the ConfigurationProperties file. This has to be a valid Inventory Expense Code in WAM.

/SyncItemListEBM/DataArea/SyncItemList/ItemGLAccount/UsageCode

usageExpenseCode

finalSnapshot

Field

OUWAMERP_UsageExpenseCode

This is equivalent to the Natural Account in the ERP system.

/SyncItemListEBM/DataArea/SyncItemList/ItemClassification(#)/ClassificationCode

If ERP pass commodityCategory, ERP should also pass this hard-coded value (COMCAT) to identify this entry is a commodityCategory

/SyncItemListEBM/DataArea/SyncItemList/ItemClassification(#)/Identification/ID

commodityCategory

finalSnapshot

Field

OUWAMERP_CommodityCategory

This is optional. If a value is provided, integration uses DVM to translate the ERP value to the equivalent WAM value.

/SyncItemListEBM/DataArea/SyncItemList/ItemClassification(#)/ClassificationCode

If ERP pass commodityName, ERP should also pass this hard-coded value ( COMNAME) to identify this entry is a commodityName

/SyncItemListEBM/DataArea/SyncItemList/ItemClassification(#)/Identification/ID

commodityName

finalSnapshot

Field

OUWAMERP_CommodityName

This is optional. If a value is provided, integration uses DVM to translate the ERP value to the equivalent WAM value.

/SyncItemListEBM/DataArea/SyncItemList/ItemClassification(#)/ClassificationCode

If ERP pass commodityType, ERP should also pass this hard-coded value ( COMTYPE) to identify this entry is a commodityType

/SyncItemListEBM/DataArea/SyncItemList/ItemClassification(#)/Identification/ID

commodityType

finalSnapshot

Field

OUWAMERP_CommodityType

This is optional. If a value is provided, integration uses DVM to translate the ERP value to the equivalent WAM value.

/SyncItemListEBM/DataArea/SyncItemList/ItemClassification(#)/ClassificationCode

If ERP pass commodityComposition, ERP should also pass this hard-coded value ( COMCOMP) to identify this entry is a commodityComposition

/SyncItemListEBM/DataArea/SyncItemList/ItemClassification(#)/Identification/ID

commodityComposition

finalSnapshot

Field

OUWAMERP_CommodityComposition

This is optional. If a value is provided, integration uses DVM to translate the ERP value to the equivalent WAM value.

/SyncItemListEBM/DataArea/SyncItemList/ItemClassification(#)/ClassificationCode

If ERP pass commoditySize, ERP should also pass this hard-coded value ( COMSIZE) to identify this entry is a commoditySize

/SyncItemListEBM/DataArea/SyncItemList/ItemClassification(#)/Identification/ID

commoditySize

finalSnapshot

Field

Pass a number to WAM.

/SyncItemListEBM/DataArea/SyncItemList/ItemPurchasingCharacteristics/AssetClassificationCode

stockCategory

finalSnapshot

Field

OUWAMERP_AssetClassificationCode

WAM values: Concretes, Electric Systems & Equipments, Mechanical Equipment, Surface Finishing

/SyncItemListEBM/DataArea/SyncItemList/ItemProcessManufacturingCharacteristics/HazardousIndicator

hazardous

finalSnapshot

Field

OUWAMERP_HazardousFlag

WAM Values: Yes, No

/SyncItemListEBM/DataArea/SyncItemList/ItemPurchasingCharacteristics/HazardClassificationCode

hazardousType

finalSnapshot

Field

OUWAMERP_HazardousType

lotManaged

finalSnapshot

Field

Not Mapped

/SyncItemListEBM/DataArea/SyncItemList/InventoryCharacteristics/ShelfLifeDuration

shelfLife

finalSnapshot

Field

Indicates the number of days from receipt after which the item lot expires

/SyncItemListEBM/DataArea/SyncItemList/ItemManufacturingCharacteristics/InventoryAssetIndicator

capitalSpare

finalSnapshot

Field

OUWAMERP_InventoryAssetFlag

WAM Values: Yes, No

/SyncItemListEBM/DataArea/SyncItemList/ItemServiceCharacteristics/TrackInstanceIndicator

trackable

finalSnapshot

Field

OUWAMERP_TrackIndicatorFlag

WAM Values: Yes, No

/SyncItemListEBM/DataArea/SyncItemList/ItemPlanningCharacteristics/RepairProgram

repairable

finalSnapshot

Field

OUWAMERP_RepairableFlag

WAM Values: Yes, No

/SyncItemListEBM/DataArea/SyncItemList/ItemPurchasingCharacteristics/UnitListPrice/PerQuantity (attribute name = unitCode)

unitOfPurchase

finalSnapshot

Field

OUWAMERP_UOMCode

The unit of measure used for purchasing the item. Example, unit price of an item is $1.50 each.

/SyncItemListEBM/DataArea/SyncItemList/ItemPurchasingCharacteristics/IssueUOMCode

unitOfIssue

finalSnapshot

Field

OUWAMERP_UOMCode

The unit of measure used to issue the item from inventory

purchaseToIssueRatio

finalSnapshot

Field

Not Mapped. If nothing is passed, defaulted to 1 in WAM

taxRateSchedule

finalSnapshot

Field

Not Mapped

purchaseCommodity

finalSnapshot

Field

Not Mapped

/SyncItemListEBM/DataArea/SyncItemList/ItemPurchasingCharacteristics/ReceiptSubstitutionAllowedIndicator

doNotSubstitute

finalSnapshot

Field

OUWAMERP_ReceiptSubstitutionAllowedFlag.dvm

WAM Values: Yes, No

truckStock

finalSnapshot

Field

Not Mapped

acceptOnReceipt

finalSnapshot

Field

Not Mapped. Defaulted in WAM on Add

defaultValueToActivity

finalSnapshot

Field

Not Mapped. Defaulted in WAM on Add

addToBOM

finalSnapshot

Field

Not Mapped

vendors

finalSnapshot

Group

vendorsList

vendors

List

/SyncItemListEBM/DataArea/SyncItemList/ItemSupplier/ItemSupplierLocation/Identification/ApplicationObjectKey/ID

vendorLocationExternalId

vendorsList

Field

ERP Vendor Location ID or ERP Vendor Site ID. This is the Vendor Location Table's unique identifier.

vendorLocationId

vendorsList

Field

/SyncItemListEBM/DataArea/SyncItemList/ItemSupplier/ItemSupplierLocation/ItemSupplierLocationSpecificationGroup/SpecificationGroup/Specification/Identification/ID

Although this is not mapped to WAM, ERP can pass a value here like 'VendorPartNbr' to specify the field. (Optional)

/SyncItemListEBM/DataArea/SyncItemList/ItemSupplier/ItemSupplierLocation/ItemSupplierLocationSpecificationGroup/SpecificationGroup/Specification/Name

Although this is not mapped to WAM, ERP can pass the value description here like 'Vendor Part Number' to describe the field. (Optional)

/SyncItemListEBM/DataArea/SyncItemList/ItemSupplier/ItemSupplierLocation/ItemSupplierLocationSpecificationGroup/SpecificationGroup/Specification/ValueText

vendorPartNumber

vendorsList

Field

/SyncItemListEBM/DataArea/SyncItemList/ItemSupplier/ItemSupplierLocation/PriorityCode

vendorPriority

vendorsList

Field

OUWAMERP_VendoryLocPriority

WAM Values: W1OT, W1PR

alternativeStockItemsList

finalSnapshot

List

alternateStockItem

alternativeStockItemsList

Field

Not Mapped

manufacturers

finalSnapshot

Group

/SyncItemListEBM/DataArea/SyncItemList/ItemManufacturer

manufacturersList

manufacturers

List

/SyncItemListEBM/DataArea/SyncItemList/ItemManufacturer/Identification/ID

manufacturerCode

manufacturersList

Field

OUWAMERP_Manufacturer

copyToPO

manufacturersList

Field

WAM Values: Yes, No. Flag to indicate if the manufacturer's information should be copied to the POs. Discussed this mapping with Steve on 02/15/2016. We can't find a field that match in the EBO, we think this field is more WAM specific. We decide to removed this mapping and default the field to W1NO in WAM on Add.

/SyncItemListEBM/DataArea/SyncItemList/ItemManufacturer/RelatedManufacturerItem/ManufacturerItemID

manufacturerPartNumber

manufacturersList

Field

bomId

Not Mapped

Stock Item Response Mapping Details

WAM Stock Item Sync Response Message

ERP Sync Item List Response Message

Comments

Element Name

Parent Element

Type

Full Path

sendDetails

Outermost

Tag

externalReferenceId

sendDetails

Field

/SyncItemListResponseEBM/DataArea/SyncItemListResponse/ItemIdentification/BusinessComponentID

ERP Sync Request ID. This is the unique ID sent as part of the response message to tie it together to the request. When WAM processes the request successfully, it only sends back the externalReferenceId, which is the ERP Sync Request ID.

externalIds

sendDetails

Group

entityIdList

externalIds

List

entity

entityIdList

externalPkValue1

entityIdList

Field

externalPkValue2

entityIdList

Field

externalPkValue3

entityIdList

Field

externalPkValue4

entityIdList

Field

externalPkValue5

entityIdList

Field

exceptionInformation

sendDetails

Group

When WAM encounters an error while processing the request, it sends back the externalReferenceId and the exeptionInformation.

exceptionInformationList

exceptionInformation

List

sequence

exceptionInformationList

Field

messageCategory

exceptionInformationList

Field

/SyncItemListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

messageNumber

exceptionInformationList

Field

//SyncItemListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

comments

exceptionInformationList

Field

/SyncItemListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Text

Error comments or error message

messageParameters

exceptionInformationList

List

parameterSequence

messageParameters

Field

messageParameterType

messageParameters

Field

messageParameterValue

messageParameters

Field

Storeroom Item (Stock Item Detail) Synchronization Process Mapping Details

This section provides data mapping details for the following:

•

Storeroom Item (Stock Item Detail) Request Mapping Details

•

Storeroom Item (Stock Item Detail) Response Mapping Details

Refer to the Storeroom Item (Stock Item Detail) Synchronization Process description for processing details on this integration point.

Storeroom Item (Stock Item Detail) Request Mapping Details

ERP Item Request EBO Message

WAM BO MESSAGE: W1-SIDIntegInbound

DVM Mapping

Comments

Full Path

Element Name

Parent Element

Type

W1-SyncRequestInbound

Outermost

Tag

syncRequestId

W1-SyncRequestInbound

Field

Not Mapped. This is a WAM system generated ID created internally in WAM on Add.

/SyncItemListEBM/DataArea/SyncItemList/ItemIdentification/BusinessComponentID

externalReferenceId

W1-SyncRequestInbound

Field

ERP Sync Request ID. This is a unique ID sent as part of the request message by the external system (ERP) initiating the sync request. This ID is used by the external system to tie together the response coming back to ERP from WAM.

/SyncItemListEBM/DataArea/SyncItemList/InventoryLocation/LocationReference/LocationIdentification/ID

The ERP system organization number.

Example: In EBS, it is a unique 3 character organization number

/SyncItemListEBM/DataArea/SyncItemList/InventoryLocation/LocationReference/LocationIdentification/ContextID

The ERP system subinventory name or subinventory ID

/SyncItemListEBM/DataArea/SyncItemList/InventoryLocation/LocationReference/LocationIdentification/ID- /SyncItemListEBM/DataArea/SyncItemList/InventoryLocation/LocationReference/LocationIdentification/ContextID- /SyncItemListEBM/DataArea/SyncItemList/ItemIdentification/ApplicationObjectKey/ID

externalPkValue1

W1-SyncRequestInbound

Field

Concatenation of ERP's Inventory Organization Number, ERP's Subinventory Name and the ERP system's Item system generated ID with a dash (-) delimiter in between.

Example: 123-Sub1-987654321

externalSystem

W1-SyncRequestInbound

Field

Defaulted by Integration using property name OUWAM.External.System in the ConfigurationProperties file.

targetMo

W1-SyncRequestInbound

Field

Defaulted by Integration using property name OUWAM.StoreroomItem.Target.MO in the ConfigurationProperties file.

initialLoad

W1-SyncRequestInbound

Field

Defaulted by Integration using property name OUWAM.InitialLoad.Flag in the ConfigurationProperties file.

syncRequestDetails

W1-SyncRequestInbound

original

syncRequestDetails

Group

finalSnapshot

original

Group

/SyncItemListEBM/DataArea/SyncItemList/InventoryLocation/LocationReference/LocationIdentification/ID- /SyncItemListEBM/DataArea/SyncItemList/InventoryLocation/LocationReference/LocationIdentification/ContextID- /SyncItemListEBM/DataArea/SyncItemList/ItemIdentification/ApplicationObjectKey/ID

stockItemDetailExternalId

Same value as externalPKValue1. This is the ERP Storeroom ID or Stock Item Detail. This ID is a concatenation of:

•

ERP's Inventory Organization Number

•

ERP's Subinventory Name

•

ERP’s Item system generated ID with a dash (-) delimiter in between.

Example: 123-Sub1-987654321

stockItemDetailId

finalSnapshot

Field

Not Mapped. This is a WAM system generated ID created internally in WAM on Add.

/SyncItemListEBM/DataArea/SyncItemList/Status/Code

boStatus

finalSnapshot

Field

OUWAMERP_StoreroomItemStatus

Subinventory Status. Use DVM to translate the ERP status to the equivalent WAM Status.

/SyncItemListEBM/DataArea/SyncItemList/ItemIdentification/ApplicationObjectKey/ID

resourceTypeExternalId

finalSnapshot

Field

ERP system generated Item ID which is the Item Table's unique identifier.

resourceTypeId

Not Mapped.

/SyncItemListEBM/DataArea/SyncItemList/InventoryLocation/LocationReference/LocationIdentification/ID, /SyncItemListEBM/DataArea/SyncItemList/InventoryLocation/LocationReference/LocationIdentification/ContextID

nodeExternalId

finalSnapshot

Field

Concatenation of ERP's Inventory Organization Number and the ERP system's Subinventory Namewith a dash (-) delimiter in between.

Example: 123-Sub1

nodeId

finalSnapshot

Field

/SyncItemListEBM/DataArea/SyncItemList/PrimaryClassificationCode

stockItemDetailClass

finalSnapshot

Field

OUWAMERP_StockItemClassificationCode

WAM Values: W1DP, W1ER, W1IL, W1IN, W1IT, W1SD, W1SL

masterStockItemDetailId

finalSnapshot

Field

Not Mapped

activityResourceRequirementId

finalSnapshot

Field

Not Mapped

lotId

finalSnapshot

Field

Not Mapped

expirationDate

finalSnapshot

Field

Not Mapped

vendorExpirationDate

finalSnapshot

Field

Not Mapped

deliveryDate

finalSnapshot

Field

Not Mapped

cureDate

finalSnapshot

Field

Not Mapped

costCenter

finalSnapshot

Field

Not Mapped

/SyncItemListEBM/DataArea/SyncItemList/ItemGLAcccount/GLAcccount/GLElement(1)/GLElement

segment1

finalSnapshot

Field

ERP Segment 1

/SyncItemListEBM/DataArea/SyncItemList/ItemGLAcccount/GLAcccount/GLElement(2)/GLElement

segment2

finalSnapshot

Field

ERP Segment 2

/SyncItemListEBM/DataArea/SyncItemList/ItemGLAcccount/GLAcccount/GLElement(3)/GLElement

segment3

finalSnapshot

Field

ERP Segment 3

/SyncItemListEBM/DataArea/SyncItemList/ItemGLAcccount/GLAcccount/GLElement(4)/GLElement

segment4

finalSnapshot

Field

ERP Segment 4

/SyncItemListEBM/DataArea/SyncItemList/ItemGLAcccount/GLAcccount/GLElement(5)/GLElement

segment5

finalSnapshot

Field

ERP Segment 5

/SyncItemListEBM/DataArea/SyncItemList/ItemGLAcccount/GLAcccount/GLElement(6)/GLElement

segment6

finalSnapshot

Field

ERP Segment 6

/SyncItemListEBM/DataArea/SyncItemList/ItemGLAcccount/GLAcccount/GLElement(7)/GLElement

segment7

finalSnapshot

Field

ERP Segment 7

/SyncItemListEBM/DataArea/SyncItemList/ItemGLAcccount/GLAcccount/GLElement(8)/GLElement

segment8

finalSnapshot

Field

ERP Segment 8

/SyncItemListEBM/DataArea/SyncItemList/ItemGLAcccount/GLAcccount/GLElement(9)/GLElement

segment9

finalSnapshot

Field

ERP Segment 9

/SyncItemListEBM/DataArea/SyncItemList/ItemGLAcccount/GLAcccount/GLElement(10)/GLElement

segment10

finalSnapshot

Field

ERP Segment 10

buyer

finalSnapshot

Field

Not Mapped

/SyncItemListEBM/DataArea/SyncItemList/ItemPurchasingCharacteristics/UnitListPrice/PerQuantity

unitOfPurchase

finalSnapshot

Field

OUWAMERP_UOMCode

The unit of measure used for purchasing the item. Example, unit price of an item is $1.50 each.

/SyncItemListEBM/DataArea/SyncItemList/ItemPurchasingCharacteristics/IssueUOMCode

unitOfIssue

finalSnapshot

OUWAMERP_UOMCode

The unit of measure used to issue the item from inventory

purchaseToIssueRatio

finalSnapshot

Field

Not Mapped

taxRateSchedule

finalSnapshot

Field

Not Mapped

/SyncItemListEBM/DataArea/SyncItemList/ItemPlanningCharacteristics/ReorderCharacteristics/MaximumReorderQuantity

maxQty

finalSnapshot

Field

Max Quantity in the bin. Maximum quantity allowed for replenishment reorder of the item.

/SyncItemListEBM/DataArea/SyncItemList/ItemPlanningCharacteristics/ReorderCharacteristics/MinimumInventoryQuantity

minQty

finalSnapshot

Field

Min quantity allowed before reordering occur or reorder quantity.

safetyStockQty

finalSnapshot

Field

WAM Values: Yes, No

reorderPoint

finalSnapshot

Field

reorderQty

finalSnapshot

Field

Not Mapped

autoReorder

finalSnapshot

Field

WAM Values: Yes, No

abcClass

finalSnapshot

Field

Not Mapped

ItemPlanningCharacteristics/ProcessingLeadTimeCharacteristics/PreprocessingDuration

leadTime

finalSnapshot

Field

Lead time to order in days. Number of days to added to the purchasing lead time to place an order.

sourceCode

finalSnapshot

Field

Not Mapped

defaultUnitPrice

finalSnapshot

Field

Not Mapped

priceToUse

finalSnapshot

Field

Not Mapped

markup

finalSnapshot

Field

Not Mapped

vendors

finalSnapshot

Group

vendorsList

vendors

List

/SyncItemListEBM/DataArea/SyncItemList/ItemSupplier/ItemSupplierLocation/Identification/ApplicationObjectKey/ID

vendorLocationExternalId

vendorsList

Field

ERP Vendor Location ID or ERP Vendor Site ID. This is the Vendor Location Table's unique identifier.

vendorLocationId

vendorsList

Field

/SyncItemListEBM/DataArea/SyncItemList/ItemSupplier/ItemSupplierLocation/ItemSupplierLocationSpecificationGroup/SpecificationGroup/Specification/Identification/ID

Although this is not mapped to WAM, ERP can pass a value here like 'VendorPartNbr' to specify the field. (Optional)

/SyncItemListEBM/DataArea/SyncItemList/ItemSupplier/ItemSupplierLocation/ItemSupplierLocationSpecificationGroup/SpecificationGroup/Specification/Name

Although this is not mapped to WAM, ERP can pass the value description here like 'Vendor Part Number' to describe the field. (Optional)

/SyncItemListEBM/DataArea/SyncItemList/ItemSupplier/ItemSupplierLocation/ItemSupplierLocationSpecificationGroup/SpecificationGroup/Specification/ValueText

vendorPartNumber

vendorsList

Field

/SyncItemListEBM/DataArea/SyncItemList/ItemSupplier/ItemSupplierLocation/PriorityCode

vendorPriority

vendorsList

Field

OUWAMERP_VendoryPriority

WAM Values: W1OT, W1PR. Reuse existing DVM.

bins

finalSnapshot

Optional Mapping

binList

bins

List

sequence

binList

Field

Not mapped

/SyncItemListEBM/DataArea/SyncItemList/InventoryLocation/Identification/ID

bin

binList

Field

/SyncItemListEBM/DataArea/SyncItemList/InventoryLocation/UsageCode

binType

binList

Field

OUWAMERP_BinType

WAM Values: W1OT, W1PR

Storeroom Item (Stock Item Detail) Response Mapping Details

WAM Storeroom Item (Stock Item Detail) Sync Response Message

ERP Sync Item List Response Message

DVM Mapping

Comments

Element Name

Parent Element

Type

Full Path

sendDetails

Outermost

Tag

externalReferenceId

sendDetails

Field

/SyncItemListResponseEBM/DataArea/SyncItemListResponse/ItemIdentification/BusinessComponentID

ERP Sync Request ID. This is the unique ID sent as part of the response message to tie it together to the request. When WAM processes the request successfully, it only sends back the externalReferenceId, which is the ERP Sync Request ID.

externalIds

sendDetails

Group

entityIdList

externalIds

List

entity

entityIdList

externalPkValue1

entityIdList

Field

externalPkValue2

entityIdList

Field

externalPkValue3

entityIdList

Field

externalPkValue4

entityIdList

Field

externalPkValue5

entityIdList

Field

exceptionInformation

sendDetails

Group

When WAM encounters an error while processing the request, it sends back the externalReferenceId and the exeptionInformation.

exceptionInformationList

exceptionInformation

List

sequence

exceptionInformationList

Field

messageCategory

exceptionInformationList

Field

/SyncItemListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

messageNumber

exceptionInformationList

Field

//SyncItemListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code will contain a concatination of the WAM Message Category and Message Number.

comments

exceptionInformationList

Field

/SyncItemListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Text

Error comments or error message

messageParameters

exceptionInformationList

List

parameterSequence

messageParameters

Field

messageParameterType

messageParameters

Field

messageParameterValue

messageParameters

Field

Supplier Party (Vendor/Vendor Location) Synchronization Process Mapping Details

This section provides data mapping details for the following:

•

Supplier Party Request Mapping Details (ERP to WAM)

•

Supplier Party Response Mapping Details (ERP to WAM)

Refer to the Supplier Party (Vendor/Vendor Location) Synchronization Process (ERP to WAM) description for processing details on this integration point.

Supplier Party Request Mapping Details (ERP to WAM)

ERP System

(Supplier Party Request EBO Message)

WAM

(W1-OngoingSyncRequestVendorLoc Business Object Message)

DVM Mapping

Comments

Full Path

Element Name

Parent Element

Type

W1-SyncRequestInbound

Outermost Tag

syncRequestId

W1-SyncRequestInbound

Field

Not Mapped. Created internally in WAM on add

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/Identification/BusinessComponentID

externalReferenceId

W1-SyncRequestInbound

Field

ERP System Sync Request ID : This is a unique ID sent as part of the request message by the external system (ERP system) initiating the sync request. This ID is used by the external system to tie together the response coming back to the ERP system from WAM.

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyLocation/Identification/ApplicationObjectKey/ID

externalPkValue1

W1-SyncRequestInbound

Field

ERP System Vendor Location ID or ERP System Vendor Site ID : The unique Vendor Location Table prime key.

externalSystem

W1-SyncRequestInbound

Field

Defaulted by the integration using the property name OUWAM.External.System in the ConfigurationProperties file.

targetMo

W1-SyncRequestInbound

Field

Defaulted by the integration using the property name OUWAM.VendorLoc.Target.MO in the ConfigurationProperties file.

initialLoad

W1-SyncRequestInbound

Field

Defaulted by the integration using property name OUWAM.InitialLoad.Flag in the ConfigurationProperties file.

syncRequestDetails

W1-SyncRequestInbound

original

syncRequestDetails

Group

finalSnapshot

original

Group

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/Identification/ApplicationObjectKey/ID

vendorExternalId

finalSnapshot

Field

ERP System Vendor Location ID or ERP System Vendor Site ID : The unique Vendor Location Table prime key.

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/Identification/ID

vendor

finalSnapshot

Field

Vendor number or vendor code.

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/Organization/Name

vendorName

finalSnapshot

Field

Vendor name.

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyLocation/LocationReference /LocationIdentification/ApplicationObjectKey/ID

externalId

finalSnapshot

Field

ERP system vendor location ID or ERP system vendor site ID.

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyLocation/LocationReference/Name

locationName

finalSnapshot

Field

Vendor location name

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/SupplierPartyTradingLocationProfile/Status/Code

boStatus

finalSnapshot

Field

OUWAMERP_SupplierPartyLocStatus

Vendor Location Status : Use DVM to translate the ERP system status to the equivalent WAM status. WAM statuses include Under Review, Active, Inactive.

creationDateTime

finalSnapshot

Field

Not Mapped. Created internally in WAM on add.

organization

finalSnapshot

Field

Not mapped. The organization is used to restrict access to certain records according to groups of users.

addressInformation

finalSnapshot

Group

Vendor location address information.

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyLocation/LocationReference/Address/LineOne

address1

addressInformation

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyLocation/LocationReference/Address/LineTwo

address2

addressInformation

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyLocation/LocationReference/Address/LineThree

address3

addressInformation

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyLocation/LocationReference/Address/LineFour

address4

addressInformation

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyLocation/LocationReference/Address/CityName

city

addressInformation

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyLocation/LocationReference/Address/StateName

state

addressInformation

Field

OUWAMERP_State

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyLocation/LocationReference/Address/CountyName

county

addressInformation

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyLocation/LocationReference/Address/CountryName

country

addressInformation

Field

OUWAMERP_Country

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyLocation/LocationReference/Address/PostalCode

postal

addressInformation

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/SupplierPartyTradingLocationProfile/PurchasingEnabledIndicator

orderFromFlag

finalSnapshot

Field

OUWAMERP_PurchasingEnabledFlag

Indicates whether purchasing from this Supplier/Vendor location is allowed. Use DVM to translate the ERP system Purchase Enabled Flag to the WAM Order From Flag. WAM values include Allowed/NotAllowed.

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/SupplierPartyTradingLocationProfile/PaymentRemittanceAllowedIndicator

payToFlag

finalSnapshot

Field

OUWAMERP_PmntRemittanceAllowedFlag

Indicates whether Supplier/Vendor Location handles billing and payments. Use DVM to translate the ERP system Payment Remittance Allowed Flag to the WAM Pay To Flag. WAM values include Allowed/NotAllowed.

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/SupplierPartyTradingLocationProfile/TradingLocationProfileAlternateUsage/BillToLocationReference/LocationIdentification/ApplicationObjectKey/ID

payToLocation

finalSnapshot

Field

If payToFlag is 'Not Allowed', payToLocation must be populated. A Bill To Location or Pay to Location on a procurement identifies the location where the invoice is to be sent. This value must be a valid ERP system Vendor Location ID that has already been synced to WAM.

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/SupplierPartyTradingLocationProfile/InvoiceCurrencyCode

currency

finalSnapshot

Field

Currency that the vendor location uses.

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/SupplierPartyTradingLocationProfile/PaymentTerm/Code

paymentTerm

finalSnapshot

Field

OUWAMERP_PaymentTerm

Indicates the payment term code. Use DVM to translate the ERP system Payment Term Code to the WAM Payment Term Code.

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/SupplierPartyTradingLocationProfile/FOBPointCode

fob

finalSnapshot

Field

OUWAMERP_FOB

Indicates the Free on Board (FOB) Code which identifies the delivery charge terms negotiated for the PO. Use DVM to translate the ERP system FOB Code to the WAM FOB Code.

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/MinimumOrderAmount

minimumOrderAmount

finalSnapshot

Field

Minimum purchase order amount.

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/SupplierPartyTradingLocationProfile/PaymentMethodCode

autoPayFlag

finalSnapshot

Field

OUWAMERP_AutoPayFlag

In WAM, this is the auto invoice indicator. Use DVM to translate the ERP system Payment Method Code to the WAM Auto Pay Flag. WAM values include Authorize/Not Authorize.

payTaxToVendor

finalSnapshot

Field

Not mapped. Indicates whether to pay sales tax to the vendor location or not.

carrierFlag

finalSnapshot

Field

Not mapped. Indicates whether to pay sales tax to the vendor location or not.

carrierLocationId

finalSnapshot

Field

Not mapped

insuranceExpirationDate

finalSnapshot

Field

Not mapped

emailPOFlag

finalSnapshot

Field

Indicates whether the PO can be emailed to the supplier/vendor. If the ERP system provides an email address, the integration sets the flag to Allowed. Else, it is set to Not Allowed. WAM values include Allowed/NotAllowed.

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyContact/Contact/ContactEmailCommunication/EmailCommunication/URI

poEmailAddress

finalSnapshot

Field

Email address of the contact person.

mainContact

finalSnapshot

Group

Vendor location's main contact person.

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyContact/Contact/Identification/ApplicationObjectKey/ID

contactExternalId

mainContact

Field

ERP system contact ID.

contactType

mainContact

Field

WAM populates on add. Created internally in WAM.

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyContact/Contact/PersonName/FirstName

firstName

mainContact

Field

Contact first name.

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyContact/Contact/PersonName/FamilyName

lastName

mainContact

Field

Contact last name

mainContactPhone

finalSnapshot

Group

Vendor location's phone information.

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyContact/Contact/ContactPhoneCommunication/PhoneCommunication/TypeCode

phoneType

mainContactPhone

Field

OUWAMERP_PhoneType

Phone Type : Whether it is the primary or business phone, mobile, fax, etc.

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyContact/Contact/ContactPhoneCommunication/PhoneCommunication/CountryCode

countryCode

mainContactPhone

Field

Phone country code

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyContact/Contact/ContactPhoneCommunication/PhoneCommunication/AreaCode

areaCode

mainContactPhone

Field

Phone area code

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyContact/Contact/ContactPhoneCommunication/PhoneCommunication/LocalNumber

phoneNumber

mainContactPhone

Field

Phone number

Supplier Party Response Mapping Details (ERP to WAM)

WAMVendor Location Sync Response Message

ERPSync SupplierParty List Response Message

Comments

Element Name

Parent Element

Type

sendDetails

Outermost

Tag

externalReferenceId

sendDetails

Field

/SyncSupplierPartyListResponseEBM/DataArea/SyncSupplierPartyListResponse/Identification/BusinessComponentID

ERP System Sync Request ID : The unique ID sent as part of the response message to tie it together to the request. When WAM processes the request successfully, it only sends back the externalReferenceID, which is the ERP System Sync Request ID.

externalIds

sendDetails

Group

entityIdList

externalIds

List

entity

entityIdList

externalPkValue1

entityIdList

Field

externalPkValue2

entityIdList

Field

externalPkValue3

entityIdList

Field

externalPkValue4

entityIdList

Field

externalPkValue5

entityIdList

Field

exceptionInformation

sendDetails

Group

When WAM encounters an error while processing the request, it sends back the externalReferenceID and the exeptionInformation.

exceptionInformationList

exceptionInformation

List

sequence

exceptionInformationList

Field

messageCategory

exceptionInformationList

Field

/SyncSupplierPartyListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code contains a concatenation of the WAM Message Category and Message Number.

messageNumber

exceptionInformationList

Field

/SyncSupplierPartyListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code contains a concatenation of the WAM Message Category and Message Number.

comments

exceptionInformationList

Field

SyncSupplierPartyListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Text

Error comments or error message

messageParameters

exceptionInformationList

List

parameterSequence

messageParameters

Field

messageParameterType

messageParameters

Field

messageParameterValue

messageParameters

Field

Worker (Employee) Synchronization Process Mapping Details

This section provides data mapping details for the following:

•

Worker (Employee) Request Mapping Details

•

Worker (Employee) Response Mapping Details

Refer to the Worker (Employee) Synchronization Process description for processing details on this integration point.

Worker (Employee) Request Mapping Details

ERP System(Worker Request EBO Message)

WAM

(W1-OngoingSyncRequestEmployee Business Object Message)

DVM Mapping

Comments

Full Path

Element Name

Parent Element

Type

W1-SyncRequestInbound

Outermost

Tag

syncRequestId

W1-SyncRequestInbound

Field

Not Mapped. Created internally in WAM on add.

/SyncWorkerListEBM/DataArea/SyncWorkerList/Identification/BusinessComponentID

externalReferenceId

W1-SyncRequestInbound

Field

ERP System Sync Request ID : This is a unique ID sent as a part of the request message by the external system (ERP system) initiating the sync request. This ID is used by the external system to tie together the response coming back to the ERP system from WAM.

/SyncWorkerListEBM/DataArea/SyncWorkerList/Identification/ApplicationObjectKey/ID

externalPkValue1

W1-SyncRequestInbound

Field

ERP System Employee ID or ERP System Person ID : This is the unique employee table prime key.

externalSystem

W1-SyncRequestInbound

Field

Defaulted by the integration using the property name OUWAM.External.System in the ConfigurationProperties file.

targetMo

W1-SyncRequestInbound

Field

Defaulted by the integration using the property name OUWAM.Employee.Target.MO in the ConfigurationProperties file.

initialLoad

W1-SyncRequestInbound

Field

Defaulted by the integration using the property name OUWAM.InitialLoad.Flag in the ConfigurationProperties file.

syncRequestDetails

W1-SyncRequestInbound

Group

original

syncRequestDetails

Group

finalSnapshot

original

Group

/SyncWorkerListEBM/DataArea/SyncWorkerList/Identification/ApplicationObjectKey/ID

externalId

finalSnapshot

Field

ERP System Employee ID or ERP System Person ID : This is the unique employee table prime key.

/SyncWorkerListEBM/DataArea/SyncWorkerList/WorkerEmployment/Identification/ID

hrEmployeeNumber

finalSnapshot

Field

The employee number in ERP system.

/SyncWorkerListEBM/DataArea/SyncWorkerList/WorkerEmployment/TypeCode

employeeType

finalSnapshot

Field

OUWAMERP_WorkerType

Employee Type : Use DVM to translate the ERP system employee type to the equivalent WAM employee type.

/SyncWorkerListEBM/DataArea/SyncWorkerList/WorkerEmployment/EmploymentTerm/EmploymentAssignment/DepartmentReference/OrganizationUnitIdentification/ID

businessUnit

finalSnapshot

Field

OUWAMERP_OrganizationUnitID

The business unit to which an employee belongs. It defines the employee's payroll cost center and how their labor cost is determined during work planning (either through their billable rate or through their craft rate). Use DVM to translate the ERP system HR/Project Organization to the equivalent WAM business unit.

/SyncWorkerListEBM/DataArea/SyncWorkerList/WorkerEmployment/EmploymentTerm/EmploymentAssignment/Status/Code

boStatus

finalSnapshot

Field

OUWAMERP_WorkerStatus

Employee Status : Use DVM to translate the ERP system status to the equivalent WAM Status. WAM Statuses include Active and Inactive.

creationUser

finalSnapshot

Field

WAM Creation User is the User ID that creates the employee in WAM. Defaulted by the integration using the property name OUWAM.Integration.User in the ConfigurationProperties file. This User ID must be a valid User ID in WAM.

/SyncWorkerListEBM/DataArea/SyncWorkerList/WorkerEmployment/EmploymentTerm/EmploymentAssignment/EmploymentAssignmentSupervision/RoleCode

supervisor

finalSnapshot

Field

Employee's Supervisor : The Supervisor Employee Number. This value must be a valid ERP system Employee ID or Person ID that has already been synced to WAM.

/SyncWorkerListEBM/DataArea/SyncWorkerList/WorkerEmployment/OriginalHireDate

hiredDate

finalSnapshot

Field

Employee's hire date or start date.

/SyncWorkerListEBM/DataArea/SyncWorkerList/WorkerEmployment/EmploymentTerm/EmploymentAssignment/BillingJobTitle

jobTitle

finalSnapshot

Field

Employee's job title or position.

/SyncWorkerListEBM/DataArea/SyncWorkerList/WorkerEmployment/EmploymentTerm/EmploymentAssignment/Identification/ApplicationObjectKey/ID

jobCode

finalSnapshot

Field

OUWAMERP_JobCode

Employee's Job Code : Use DVM to translate the ERP system Job Code to the WAM Job Code.

/SyncWorkerListEBM/DataArea/SyncWorkerList/ WorkerEmployment/EmploymentTerm/ EmploymentAssignment/Identification/ ApplicationObjectKey/ID

principalCraft

finalSnapshot

Field

OUWAMERP_JobCode

The craft code is used in work planning. Each employee is assigned a principal craft for work scheduling purposes. Use DVM to translate the ERP system Job Code to the WAM Principal Craft Code.

/SyncWorkerListEBM/DataArea/SyncWorkerList/Person/PersonName/PersonName/FirstName

firstName

finalSnapshot

Field

Employee's first name.

/SyncWorkerListEBM/DataArea/SyncWorkerList/Person/PersonName/PersonName/FamilyName

lastName

finalSnapshot

Field

Employee's family name or last name.

/SyncWorkerListEBM/DataArea/SyncWorkerList/WorkerEmployment/TerminationDate

terminatedDate

finalSnapshot

Field

Employee's termination date.

addressInformation

finalSnapshot

Group

Employee's address information

/SyncWorkerListEBM/DataArea/SyncWorkerList/WorkerEmployment/EmploymentTerm/EmploymentAssignment/LocationReference/Address/LineOne

address1

addressInformation

Field

/SyncWorkerListEBM/DataArea/SyncWorkerList/WorkerEmployment/EmploymentTerm/EmploymentAssignment/LocationReference/Address/LineTwo

address2

addressInformation

Field

/SyncWorkerListEBM/DataArea/SyncWorkerList/WorkerEmployment/EmploymentTerm/EmploymentAssignment/LocationReference/Address/LineThree

address3

addressInformation

Field

/SyncWorkerListEBM/DataArea/SyncWorkerList/WorkerEmployment/EmploymentTerm/EmploymentAssignment/LocationReference/Address/LineFour

address4

addressInformation

Field

/SyncWorkerListEBM/DataArea/SyncWorkerList/WorkerEmployment/EmploymentTerm/EmploymentAssignment/LocationReference/Address/CityName

city

addressInformation

Field

/SyncWorkerListEBM/DataArea/SyncWorkerList/WorkerEmployment/EmploymentTerm/EmploymentAssignment/LocationReference/Address/StateName

state

addressInformation

Field

OUWAMERP_State

/SyncWorkerListEBM/DataArea/SyncWorkerList/WorkerEmployment/EmploymentTerm/EmploymentAssignment/LocationReference/Address/CountyName

county

addressInformation

Field

/SyncWorkerListEBM/DataArea/SyncWorkerList/WorkerEmployment/EmploymentTerm/EmploymentAssignment/LocationReference/Address/CountryCode

country

addressInformation

Field

OUWAMERP_Country

/SyncWorkerListEBM/DataArea/SyncWorkerList/WorkerEmployment/EmploymentTerm/EmploymentAssignment/LocationReference/Address/PostalCode

postal

addressInformation

Field

organization

finalSnapshot

Field

Not mapped. The organization is used to restrict access to certain records according to groups of users.

phoneNumbers

Group

Employee's phone information.

phoneNumbersList

List

/SyncWorkerListEBM/DataArea/SyncWorkerList/Person/PersonPhoneCommunication/PhoneCommunication/TypeCode

phoneType

phoneNumbersList

Field

OUWAMERP_PhoneType

Phone type whether it is the home phone, mobile, fax, etc.

/SyncWorkerListEBM/DataArea/SyncWorkerList/Person/PersonPhoneCommunication/PhoneCommunication/CountryCode

countryCode

phoneNumbersList

Field

/SyncWorkerListEBM/DataArea/SyncWorkerList/Person/PersonPhoneCommunication/PhoneCommunication/AreaCode

areaCode

phoneNumbersList

Field

/SyncWorkerListEBM/DataArea/SyncWorkerList/Person/PersonPhoneCommunication/PhoneCommunication/LocalNumber

phoneNumber

phoneNumbersList

Field

employeeTrainingInformation

finalSnapshot

Group

employeeTrainingInformationList

employeeTrainingInformation

List

/SyncWorkerListEBM/DataArea/SyncWorkerList/WorkerCourseAttendance/CourseTitle

course

employeeTrainingInformationList

Field

The list of the titles of the training courses attended by an employee.

Worker (Employee) Response Mapping Details

WAM (Employee Sync Response Message)

ERP (Sync Worker List Response Message)

Comments

Element Name

Parent Element

Type

Full Path

Element Name

Parent Element

Type

sendDetails

Outermost

Tag

externalReferenceId

sendDetails

Field

/SyncWorkerListResponseEBM/DataArea/SyncWorkerListResponse/Identification/BusinessComponentID

ERP System Sync Request ID : The unique ID sent as a part of the response message to tie it together to the request. When WAM processes the request successfully, it only sends back the externalReferenceID, which is the ERP System Sync Request ID.

externalIds

sendDetails

Group

entityIdList

externalIds

List

entity

entityIdList

externalPkValue1

entityIdList

Field

externalPkValue2

entityIdList

Field

externalPkValue3

entityIdList

Field

externalPkValue4

entityIdList

Field

externalPkValue5

entityIdList

Field

exceptionInformation

sendDetails

Group

When WAM encounters an error while processing the request, it sends back the externalReferenceID and the exeptionInformation.

exceptionInformationList

exceptionInformation

List

sequence

exceptionInformationList

Field

messageCategory

exceptionInformationList

Field

/SyncWorkerListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code contains a concatenation of the WAM Message Category and Message Number.

messageNumber

exceptionInformationList

Field

/SyncWorkerListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Code

Fault Notification/FaultMessage/Code contains a concatenation of the WAM Message Category and Message Number.

comments

exceptionInformationList

Field

/SyncWorkerListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Text

Error comments or error message.

messageParameters

exceptionInformationList

List

parameterSequence

messageParameters

Field

messageParameterType

messageParameters

Field

messageParameterValue

messageParameters

Field

Oracle Utilities Work and Asset Management Initiated Processes

GL Transaction (Accounting Entry) Synchronization Process Mapping Details

This section provides data mapping details for the following:

•

GL Transaction (Accounting Entry) Request EBO Message Mapping Details (WAM to ERP)

•

GL Transaction (Accounting Entry) Response Mapping Details (WAM to ERP)

Refer to the GL Transaction (Accounting Entry) Synchronization Process (WAM to ERP) description for processing details on this integration point.

GL Transaction (Accounting Entry) Request EBO Message Mapping Details (WAM to ERP)

Oracle Utilities Work and Asset

Management Financial Transaction Outbound Message Business Object (W1-FinancialTransIntegOutbound)

ERP Accounting Entry Request EBO Message

DVM Mapping

Comments

Element Name

Parent Element

Type

Full Path

sendDetails

Outermost

Tag

syncRequestId

sendDetails

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/Identification/ID

WAM Sync Request ID : This is a unique ID sent as part of the request message by the external system (WAM). This ID can be used by the external system to tie together the response coming back from ERP, if a response message is needed. Currently, no response message is required or expected.

integrationDetails

sendDetails

Group

financialTransactionType

integrationDetails

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/TypeCode

OUWAMERP_AccountingEntryType

Indicates the type of accounting entry.WAM Values: Regular or Tax. Use DVM to translate the ERP system financial transaction type to the equivalent WAM Accounting Entry Type.

financialTransactionId

integrationDetails

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/Identification/ApplicationObjectKey/ID

WAM Financial Transaction (FT) ID. This can be stored in ERP to cross reference the WAM ID, if needed.

createdBy

integrationDetails

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AuditHistory/CreatedBy

WAM user ID that created the FT.

createDateTime

integrationDetails

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AuditHistory/CreatedDateTime

Creation date and time of the FT.

currency

integrationDetails

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/CurrencyExchange/SourceCurrencyCode

OUWAMERP_Currency

The currency of the FT.

accountingDate

integrationDetails

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AccountingDate

The date on which the FT occurred.

activityId

integrationDetails

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/LedgerReference/LedgerIdentification/AlternateObjectKey/ID

This IDentifies on which the WAM activity ID or the project, the charge is being used for.

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/LedgerReference/LedgerIdentification/AlternateObjectKey/ContextID

If WAM Activity ID is provided, the integration defaults the description using property name OUWAM.ActivityID.Code in the ConfigurationProperties file.

timesheetDetailId

integrationDetails

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/LedgerReference/LedgerIdentification/ID

This IDentifies the charge ID. For example: Timehseet ID, Direct Charges ID, Materials Issued ID, etc. WAM only passes one ID per request message. The integration maps the one passed from WAM and sets the appropriate code value.

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/LedgerReference/LedgerIdentification/BusinessComponentID

If WAM Activity ID is provided, the integration defaults the description using property name OUWAM.TimesheetDetailID.Codein the ConfigurationProperties file.

otherDirectChargesId

integrationDetails

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/LedgerReference/LedgerIdentification/ID

This IDentifies the charge ID.

Example: Timehseet ID, Direct Charges ID, Inventory Count Line ID, Accept Line ID, Materials Issued ID, etc. WAM only passes one ID per request message. The integration maps the one passed from WAM and sets the appropriate code value.

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/LedgerReference/LedgerIdentification/BusinessComponentID

If WAM Activity ID is provided, the integration defaults the description using property name OUWAM.OtherDirectChargesID.Code in the ConfigurationProperties file.

inventoryCountLineId

integrationDetails

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/LedgerReference/LedgerIdentification/ID

This IDentifies the charge ID.

Example: Timehseet ID, Direct Charges ID, Inventory Count Line ID, Accept Line ID, Materials Issued ID, etc. WAM only passes one ID per request message. The integration maps the one passed from WAM and sets the appropriate code value.

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/LedgerReference/LedgerIdentification/BusinessComponentID

If WAM Activity ID is provided, the integration defaults the description using property name OUWAM.InventoryCountLineID.Code in the ConfigurationProperties file.

acceptLineId

integrationDetails

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/LedgerReference/LedgerIdentification/ID

This IDentifies the charge ID.

Example: Timehseet ID, Direct Charges ID, Inventory Count Line ID, Accept Line ID, Materials Issued ID, etc. WAM only passes one ID per request message. The integration maps the one passed from WAM and sets the appropriate code value.

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/LedgerReference/LedgerIdentification/BusinessComponentID

If WAM Activity ID is provided, the integration defaults the description using property name OUWAM.AcceptLineId.Code in the ConfigurationProperties file.

materialIssueLineId

integrationDetails

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/LedgerReference/LedgerIdentification/ID

This IDentifies the charge ID.

Example: Timehseet ID, Direct Charges ID, Inventory Count Line ID, Accept Line ID, Materials Issued ID, etc. WAM only passes one ID per request message. The integration maps the one passed from WAM and sets the appropriate code value.

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/LedgerReference/LedgerIdentification/BusinessComponentID

If WAM Activity ID is provided, the integration defaults the description using property name OUWAM.MaterialIssueLineID.Code in the ConfigurationProperties file.

materialReturnLineId

integrationDetails

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/LedgerReference/LedgerIdentification/ID

This IDentifies the charge ID.

Example: Timehseet ID, Direct Charges ID, Materials Issued ID, etc. WAM only passes one ID per request message. The integration maps the one passed from WAM and sets the appropriate code value.

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/LedgerReference/LedgerIdentification/BusinessComponentID

If WAM Activity ID is provided, the integration defaults the description using property name OUWAM.MaterialReturnLineID.Code in the ConfigurationProperties file.

returnId

integrationDetails

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/LedgerReference/LedgerIdentification/ID

This IDentifies the charge ID.

Example: Timehseet ID, Direct Charges ID, Materials Issued ID, etc. WAM only passes one ID per request message. The integration maps the one passed from WAM and sets the appropriate code value.

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/LedgerReference/LedgerIdentification/BusinessComponentID

If WAM Activity ID is provided, the integration defaults the description using property name OUWAM.ReturnID.Code in the ConfigurationProperties file.

inventoryAdjustmentId

integrationDetails

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/LedgerReference/LedgerIdentification/ID

This IDentifies the charge ID. For example: Timehseet ID, Direct Charges ID, Inventory Count Line ID, Accept Line ID, Materials Issued ID, etc. WAM only passes one ID per request message. The integration maps the one passed from WAM and sets the appropriate code value.

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/LedgerReference/LedgerIdentification/BusinessComponentID

If WAM Activity ID is provided, the integration defaults the description using property name OUWAM.InventoryAdjustmentID.Code in the ConfigurationProperties file.

financialTransactionGlDetails

integrationDetails

List

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AccountingEntryLine/

glAccount

financialTransactionGlDetails

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AccountingEntryLine/GLAccount/Identification/ApplicationObjectKey/ID

WAM GL account.

amount

financialTransactionGlDetails

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AccountingEntryLine/DebitAmount

WAM only passes the debit amount.

costCenter

financialTransactionGlDetails

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AccountingEntryLine/GLAccount/GLElement(1)/GLElement

The cost center from WAM is mapped to the accounting entry EBO-GL account's first GLElement.

financialTransactionGlDetails

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AccountingEntryLine/GLAccount/GLElement(1)/GLElementCode

Defaulted by the integration using the property name OUWAM.CostCenter.Code in the ConfigurationProperties file.

expenseCode

financialTransactionGlDetails

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AccountingEntryLine/GLAccount/GLElement(2)/GLElement

The expense code from WAM is mapped to the accounting entry EBO-GL account's second GLElement.

financialTransactionGlDetails

Field

/SyncAccountingEntryListEBM/DataArea/SyncAccountingEntryList/AccountingEntryLine/GLAccount/GLElement(2)/GLElementCode

Defaulted by the integration using the property name OUWAM.ExpenseCode in the ConfigurationProperties file.

GL Transaction (Accounting Entry) Response Mapping Details (WAM to ERP)

ERP GL Transaction (Accounting Entry) Sync Response Message

WAM Financial Transaction Response Message Inbound Service: F1-UpdateAndTransitionSyncRequest

Comments

Full Path

Element Name

Parent Element

Type

F1-UpdateAndTransitionSyncRequest

Outermost

Tag

/SyncAccountingEntryListResponseEBM/DataArea/SyncAccountingEntryListResponse/Identification/BusinessComponentID

syncRequestId

F1-UpdateAndTransitionSyncRequest

Field

WAM Sync Request ID. The unique ID sent as part of the response message to tie it together to the request. When ERP processes the request successfully, it sends back the WAM Sync Request ID only.

externalIds

F1-UpdateAndTransitionSyncRequest

Group

entityIdList

externalIds

List

entity

entityIdList

Field

externalPkValue1

entityIdList

Field

externalPkValue2

entityIdList

Field

externalPkValue3

entityIdList

Field

externalPkValue4

entityIdList

Field

externalPkValue5

entityIdList

Field

exceptionInformation

F1-UpdateAndTransitionSyncRequest

Group

When ERP encounters an error while processing the request, it sends back the WAM Sync Request ID and the error or fault information.

exceptionInformationList

exceptionInformation

List

sequence

exceptionInformationList

Field

messageCategory

exceptionInformationList

Field

Defaulted by Integration using property name OUWAM.Generic.MessageCategory in the ConfigurationProperties file.

messageNumber

exceptionInformationList

Field

Defaulted by Integration using property name OUWAM.GenericBusinessException.MessageNumber in the ConfigurationProperties file.

SyncAccountingEntryListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Text

comments

exceptionInformationList

Field

Error comments or error message

messageParameters

exceptionInformationList

List

parameterSequence

messageParameters

Field

messageParameterValue

messageParameters

Field

Materials Requisition Synchronization Process Mapping Details

This section provides data mapping details for the following:

•

Materials Requisition Request Mapping Details

•

Materials Requisition Response Mapping Details

Refer to the Material Requisition Synchronization Process description for processing details on this integration point.

Materials Requisition Request Mapping Details

WAM Outbound BO W1-MaterialReqIntegOutbound

ERP Requisition Request EBO message

DVM Mapping

Comments

Element Name

Parent Element

Type

Full Path

sendDetails

Outermost

Tag

/SyncRequisitionListEBM/DataArea/SyncRequisitionList (attribute name = actionCode)

Put hard coded value 'Material Requisiiton'.

syncRequestId

sendDetails

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/Identification/BusinessComponentID

WAM Sync Request Id. This is a unique Id sent out as part of the request message by WAM. This Id is used by the WAM to tie together the request sent out to the ERP and the response coming back from the ERP. This id should be sent back to WAM as part of the response message.

integrationDetails

sendDetails

Group

headerInfo

integrationDetails

Group

materialRequestHeaderId

headerInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/Identification/ApplicationObjectKey/ID

WAM MaterialRequest Header Id. This is a system generated id in WAM that must be stored in the ERP system and pass back to WAM in the Issue Inventory Transaction sync.

boStatus

headerInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/Status/Code

OUWAMERP_MaterialRequestStatusCode

WAM sends the material request to the ERP system when it is in the ' READY FOR ISSUE' status. The record will be lock down in WAM when the Material Request has already been sent out to the ERP. All updates to the Material Request will be done in the ERP system. The ERP system will not send any updates, including status update, to WAM. If Material Request Status update is needed, this will be an extension.

nodeId

Not Mapped

activityId

Not Mapped. WAM's system generated activity id

requiredByDate

headerInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/RequiredDate

deliveryToLocation

headerInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/DeliverToPartyReference/LocationReference/LocationIdentification/ID

OUWAMERP_LocationId

WAM will pass a valid WAM location id. This is a lookup in WAM. Integration will use dvm to map it to the Valid EBS location id. Pass WAM Requisition Header Deliver To Location to all the EBO Requisition Lines.

deliverTo

headerInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/DeliverToPartyReference/OrganizationName

Pass WAM Material Requisition Header Deliver To Information to all the EBO Requisition Lines.

requester

headerInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequesterPartyReference/OrganizationName

Requestor Name. This is a name and not a code or an id.

phone

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequesterPartyReference/Contact/ContactPhoneCommunication/PhoneCommunication/CompleteNumber

WAM will pass the area code and phone number without delimiters.

description

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/Description

Material Requisition Description

requestCategory

Not Mapped

projectId

Not Mapped

lineInfo

integrationDetails

Group

lineInfoList

lineInfo

List

List mapping in a loop

materialRequestLineId

lineInfoList

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/Identification/ApplicationObjectKey/ID

The WAM Material Requisition Line Id needs to be stored in the ERP and pass back to WAM in the Issue Inventory Transaction Transactional Sync.

materialRequestHeaderId

lineInfoList

Field

Not Mapped. This is already mapped in the header

stockItemDetailId

Not mapped.

stockItemDetailExternalId

lineInfoList

Field

This is the ERP Storeroom ID or Stock Item Detail Id. This Id is a three part key delimited by a dash (-). The first and the second part of the stockItemDetailExternalId identifies the inventory location. The third part of the id is the ERP's system generated stock Item Id. Example: StockItemDetailExternalId: 123-Sub1-987654321

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/SuggestedSupplierPartyReference/LocationReference/LocationIdentification/ID

The first part of the stockItemDetailExternalId is the ERP's Inventory Organization Number. From the example above, 123 should be map here.

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/SuggestedSupplierPartyReference/LocationReference/LocationIdentification/ContextID

The second part of the stockItemDetailExternalId is the ERP's Subinventory Name. From the example above, Sub1 should be map here.

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/ItemReference/ItemIdentification/ApplicationObjectKey/ID

The third part of the stockItemDetailExternalId is the ERP's system generated stock Item Id which is the Item Table's unique identifier.

requestedQuantity

lineInfoList

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/OrderedQuantity

unitOfIssue

lineInfoList

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/OrderedQuantity (attribute name = unitCode)

Unit of issue for the quantities returned.

workOrderNumber

headerInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/SourceRequisitionLineIdentification/ID

WAM's Work Order Number

activityNumber

headerInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/SourceRequisitionLineIdentification/ContextID

WAM's Activity Number

accountingInformation

lineInfoList

Group

costCenterList

accountingInformation

List

glAccount

costCenterList

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/RequisitionAccountingDistribution/AccountingDistribution/GLAccount/Identification/ID

costCenter

Not Mapped

expenseCode

Not Mapped

percentage

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/RequisitionAccountingDistribution/AccountingDistribution/Percentage

Materials Requisition Response Mapping Details

ERP Sync Requisition Response Message

WAM Material Requistion Response Message IWS: F1-UpdateAndTransitionSyncRequest

Comments

Full Path

Element Name

Parent Element

Type

F1-UpdateAndTransitionSyncRequest

Outermost

Tag

/SyncRequisitionListResponseEBM/DataArea/SyncRequisitionListResponse/Identification/BusinessComponentID

syncRequestId

F1-UpdateAndTransitionSyncRequest

Field

WAM Sync Request Id. This is the unique Id sent out as part of the response message to tie it together to the request. When ERP process the request successfully, it only sends back the WAM Sync Request ID.

externalIds

F1-UpdateAndTransitionSyncRequest

Group

entityIdList

externalIds

List

entity

entityIdList

Field

externalPkValue1

entityIdList

Field

externalPkValue2

entityIdList

Field

externalPkValue3

entityIdList

Field

externalPkValue4

entityIdList

Field

externalPkValue5

entityIdList

Field

exceptionInformation

F1-UpdateAndTransitionSyncRequest

Group

When ERP encounters an error while process the request, it sends back the WAM Sync Request Id and the error or fault information.

exceptionInformationList

exceptionInformation

List

sequence

exceptionInformationList

Field

messageCategory

exceptionInformationList

Field

Defaulted by Integration using property name OUWAM.Generic.MessageCategory in the ConfigurationProperties file.

messageNumber

exceptionInformationList

Field

Defaulted by Integration using property name OUWAM.GenericBusinessException.MessageNumber in the ConfigurationProperties file.

SyncRequisitionListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Text

comments

exceptionInformationList

Field

Error comments or error message

messageParameters

exceptionInformationList

List

parameterSequence

messageParameters

Field

messageParameterValue

messageParameters

Field

messageParameterValue

messageParameters

Field

Purchase Requisition Synchronization Process Mapping Details

This section provides data mapping details for the following:

•

Purchase Requisition Request Mapping Details

•

Purchase Requisition Response Mapping Details

Refer to the Purchase Requisition Synchronization Process for details about the integration point.

Purchase Requisition Request Mapping Details

WAM Purchase Requisition Outbound Message Business Object (W1-PurchaseReqIntegOutbound)

ERP Requisition EBO Message

DVM Mapping

Comments

Element Name

Parent Element

Type

Full Path

sendDetails

Outermost

Tag

/SyncRequisitionListEBM/DataArea/SyncRequisitionList (attribute name = actionCode)

ERP pass Hardcoded value 'Purchase Requisition' as part of the message.

syncRequestId

sendDetails

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/Identification/BusinessComponentID

WAM Sync Request ID. This is a unique ID sent as part of the request message by WAM. This ID is used by the WAM system to tie together the request sent to the ERP and the response coming back from the ERP system. This ID should be sent back to WAM as part of the response message.

integrationDetails

sendDetails

Group

headerInfo

integrationDetails

Group

purchaseRequisitionHeaderId

headerInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/Identification/ApplicationObjectKey/ID

WAM Purchase Requisition Header ID. This is a system generated ID in WAM, it can be stored in the ERP system to cross reference the WAM Purchase requisition Header ID, if needed.

purchaseRequisitionNumber

headerInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/Identification/ID

Purchase Requisition Number. This is the same value in WAM and the ERP system.

boStatus

headerInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/Status/Code

OUWAMERP_RequisitionStatus

WAM sends the purchase requisition to the ERP system when it is in the ' SENT' status. The record is locked in WAM when the Requisition has already been sent to the ERP system. All updates to the Requisition are completed in the ERP system. the ERP system does not send any Requisition updates, including status updates, to WAM. If Requisition status updates need to be synchronized with WAM, your implementation will need to write an extension.

approvalProfile

headerInfo

Field

Not Mapped

initiatingBlanketContract

headerInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/SuggestedBlanketPurchaseAgreementReference/PurchaseAgreementIdentification/ApplicationObjectKey/ID

Initial Blanket Contract used for this Purchase Requisition. ERP system generated Blanket Contract or or Blanket Purchase Agreement ID which is the Blanket Contract Table's unique identifier. This blanket contract should also exist in the ERP system. Pass Requisition Header Blanket Contract ID to all the EBO Requisition Lines Blanket Contract ID.

createdBlanketContract

headerInfo

Field

Not Mapped

description

headerInfo

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/Description

Purchase Requisition Description

createdBy

headerInfo

Field

Not Mapped.

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionStatusHistory/StatusHistory/ToStatusCode

Integration default hardcoded value ' CREATED'

creationDateTime

headerInfo

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionStatusHistory/StatusHistory/EffectiveDateTime

projectId

headerInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/RequisitionAccountingDistribution/AccountingDistribution/ProjectReference/ProjectIdentfication/ID

WAM Project ID in the Requisition Header. Only use this value if the WAM Requisition Line projectId is empty.

accessControl

headerInfo

Field

Not Mapped

requisitionInfo

headerInfo

Group

initiator

requisitionInfo

Field

requester

requisitionInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequesterPartyReference/OrganizationName

Requestor Name. Thisname is a text field and not a code or an ID.

contactNumber

requisitionInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequesterPartyReference/Contact/ContactPhoneCommunication/PhoneCommunication/CompleteNumber

WAM passes the area code and phone number without delimiters.

buyer

requisitionInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/SuggestedBuyerPartyReference/PartyIdentification/ID

OUWAMERP_Buyer

This is a suggested buyer. Optional Mapping in the ERP system.

Example: In EBS, it has to be a valid HR record and the person has to be setup as a buyer. Integration uses DVM to map the WAM Buyer ID to the valid ERP Buyer ID. Pass WAM Requisition Header Buyer to all the EBO Requisition Lines.

buyerDescription

requisitionInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/SuggestedBuyerPartyReference/OrganizationName

Pass WAM Requisition Header Buyer Description to all the EBO Requisition Lines.

requiredByDate

requisitionInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/RequiredDate

Only use this value if the WAM Requisition LIne requiredDate is empty.

promiseDate

requisitionInfo

Field

Not Mapped

shipToLocation

requisitionInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequesterPartyReference/LocationReference/LocationIdentification/ID

OUWAMERP_LocationId

WAM passes a valid WAM location ID. This is a lookup in WAM. Integration uses DVM to map it to the valid ERP system location ID.

deliverToLocation

requisitionInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/DeliverToPartyReference/LocationReference/LocationIdentification/ID

OUWAMERP_LocationId

WAM passes a valid WAM location ID. This is a lookup in WAM. Integration uses DVM to map to the valid ERP system location ID. Pass WAM Requisition Header Deliver To Location to all the EBO Requisition Lines.

deliverTo

requisitionInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/DeliverToPartyReference/OrganizationName

Pass WAM Requisition Header Deliver To Information to all the EBO Requisition Lines.

vendorLocation

headerInfo

Group

Suggested Vendor Location

vendorLocationId

vendorLocation

Field

Not Mapped. WAM's internal Vendor Location ID

vendorLocationExternalId

vendorLocation

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/SuggestedSupplierPartyReference/LocationReference/LocationIdentification/ApplicationObjectKey/ID

Pass ERP Vendor Location ID or ERP Vendor Site ID. This has to be a valid vendor location in WAM. Supplier Party Sync from the ERP system to WAM must be done first.

location

vendorLocation

Group

Vendor Location Address

address1

location

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/SuggestedSupplierPartyReference/LocationReference/Address/LineOne

address2

location

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/SuggestedSupplierPartyReference/LocationReference/Address/LineTwo

address3

location

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/SuggestedSupplierPartyReference/LocationReference/Address/LineThree

address4

location

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/SuggestedSupplierPartyReference/LocationReference/Address/LineFour

geographicCode

location

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/SuggestedSupplierPartyReference/LocationReference/Address/GEOCodeID

city

location

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/SuggestedSupplierPartyReference/LocationReference/Address/CityName

suburb

location

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/SuggestedSupplierPartyReference/LocationReference/Address/ProvinceName

state

location

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/SuggestedSupplierPartyReference/LocationReference/Address/StateName

OUWAMERP_State

DVM already exist

county

location

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/SuggestedSupplierPartyReference/LocationReference/Address/CountyName

country

location

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/SuggestedSupplierPartyReference/LocationReference/Address/CountryCode

OUWAMERP_Country

DVM already exist

postal

location

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/SuggestedSupplierPartyReference/LocationReference/Address/PostalCode

exchangeRate

vendorLocation

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/RequisitionLine/CurrencyExchange/ConversionRate

currency

vendorLocation

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/RequisitionLine/CurrencyExchange/SourceCurrencyCode

OUWAMERP_Currency

DVM already exist

fob

vendorLocation

Field

Not Mapped

paymentTerms

vendorLocation

Field

Not Mapped

autoPay

vendorLocation

Field

Not Mapped

carrierLocationId

vendorLocation

Field

Not Mapped

accountingInfo

headerInfo

Group

WAM Requisition Header accountingInfo Group not mapped

costCenterList

accountingInfo

List

costCenter

costCenterList

Field

percentage

costCenterList

Field

lineInfo

integrationDetails

Group

lineInfoList

lineInfo

List

purchaseRequisitionLineId

lineInfoList

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/Identification/ApplicationObjectKey/ID

The Purchase Requisition Line ID needs to be stored in the ERP and pass back to WAM in the PO Transactional Sync.

purchaseRequisitionHeaderId

lineInfoList

Field

Not Mapped. This can also be obtained from the header.

boStatus

lineInfoList

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/Status/Code

OUWAMERP_RequisitionLineStatus

Requisition Line Status. WAM only sends the purchase requisition lines in ' SENT' status.

blanketContractLineId

lineInfoList

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/SuggestedBlanketPurchaseAgreementReference/PurchaseAgreementIdentification/ApplicationObjectKey/ContextID

projectId

lineInfoList

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/RequisitionAccountingDistribution/AccountingDistribution/ProjectReference/ProjectIdentfication/ID

WAM Project ID. Optional Mapping to the ERP system. Use the WAM Requisition Line Project ID. If it is not provided, get the value from WAM Header Project ID.

creationDateTime

lineInfoList

Field

Not Mapped

resourceTypeId

lineInfoList

Field

Not Mapped. WAM's system generated resourceType ID

resourceTypeExternalId

lineInfoList

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/ItemReference/ItemIdentification/ApplicationObjectKey/ID

ERP's system generated stock Item code/ID. This is the Item Table's unique identifier. If the stock item or resource does not exist in the ERP, leave this blank and only pass the item description. If the stock item exist in the ERP, do not populate the item description.

description

lineInfoList

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/ItemReference/Description

Item Description

workOrderNumber

lineInfoList

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/SourceRequisitionLineIdentification/ID

WAM's Work Order Number

activityNumber

lineInfoList

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/SourceRequisitionLineIdentification/ContextID

WAM's Activity Number

requisitionInfo

lineInfoList

Group

itemNumber

requisitionInfo

Field

Not Mapped Item sequence number

itemType

requisitionInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/ItemReference/TypeCode

OUWAMERP_ItemType

quantity

requisitionInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/OrderedQuantity

ERP system generated Item ID which is the Item Table's unique identifier.

unitprice

requisitionInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/UnitPrice/Amount

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/UnitPrice/PerQuantity

Pass a number. If blank default to 1

unitOfPurchase

requisitionInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/UnitPrice/PerQuantity (attribute=unitCode)

OUWAMERP_UOMCode

requiredByDate

requisitionInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/RequiredDate

If WAM Requisition LIne requiredDate is empty, get the value from WAM Requisition Header requiredDate.

promiseDate

requisitionInfo

Field

Not Mapped

vendorpartNumber

requisitionInfo

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/ItemReference/ItemIdentification/SupplierItemID

expedite

requisitionInfo

Field

Not Mapped

printPrice

requisitionInfo

Field

Not Mapped

relatedObjects

lineInfoList

Group

woId

relatedObjects

Field

Not Mapped. WAM's system generated work order ID

activityId

relatedObjects

Field

Not Mapped. WAM's system generated activity ID

activityResourceRequirementId

relatedObjects

Field

Not Mapped

rrId

relatedObjects

Field

Not Mapped

poLineId

relatedObjects

Field

Not Mapped

accountingInfo

lineInfoList

Group

costCenterList

accountingInfo

List

glAccount

costCenterList

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/RequisitionAccountingDistribution/AccountingDistribution/GLAccount/Identification/ID

costCenter

costCenterList

Field

Not Mapped

expenseCode

costCenterList

Field

Not Mapped

percentage

costCenterList

Field

/SyncRequisitionListEBM/DataArea/SyncRequisitionList/RequisitionLine/RequisitionAccountingDistribution/AccountingDistribution/Percentage

Purchase Requisition Response Mapping Details

ERP Sync Requisition Response Message

WAM Requistion Response Message IWS: F1-UpdateAndTransitionSyncRequest

Comments

Full Path

Element Name

Parent Element

Type

F1-UpdateAndTransitionSyncRequest

Outermost

Tag

/SyncRequisitionListResponseEBM/DataArea/SyncRequisitionListResponse/Identification/BusinessComponentID

syncRequestId

F1-UpdateAndTransitionSyncRequest

Field

WAM Sync Request ID. This is the unique ID sent as part of the response message to tie it together to the request. When ERP processes the request successfully, it only sends back the WAM Sync Request ID.

externalIds

F1-UpdateAndTransitionSyncRequest

Group

entityIdList

externalIds

List

entity

entityIdList

Field

externalPkValue1

entityIdList

Field

externalPkValue2

entityIdList

Field

externalPkValue3

entityIdList

Field

externalPkValue4

entityIdList

Field

externalPkValue5

entityIdList

Field

exceptionInformation

F1-UpdateAndTransitionSyncRequest

Group

When ERP encounters an error while processing the request, it sends back the WAM Sync Request ID and the error or fault information.

exceptionInformationList

exceptionInformation

List

sequence

exceptionInformationList

Field

messageCategory

exceptionInformationList

Field

Defaulted by Integration using property name OUWAM.Generic.MessageCategory in the ConfigurationProperties file.

messageNumber

exceptionInformationList

Field

Defaulted by Integration using property name OUWAM.GenericBusinessException.MessageNumber in the ConfigurationProperties file.

SyncRequisitionListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Text

comments

exceptionInformationList

Field

Error comments or error message

messageParameters

exceptionInformationList

List

parameterSequence

messageParameters

Field

messageParameterValue

messageParameters

Field

Supplier Party (Vendor/Vendor Location) Synchronization Process Mapping Details

This section provides data mapping details for the following:

•

Supplier Party (Vendor/Vendor Location) Request Mapping Details (WAM to ERP)

•

Supplier Party (Vendor/Vendor Location) Response Mapping Details (WAM to ERP)

Refer to the Supplier Party (Vendor/Vendor Location) Synchronization Process (WAM to ERP) description for processing details on this integration point.

Supplier Party (Vendor/Vendor Location) Request Mapping Details (WAM to ERP)

WAM Outbound BO W1-VendorLocIntegOutbound

ERP Supplier Party Request EBO Message

DVM Mapping

Comments

Element Name

Parent Element

Type

Full Path

sendDetails

Outermost

Tag

syncRequestId

sendDetails

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/Identification/BusinessComponentID

WAM Sync Request ID. This is a unique ID sent as part of the request message by WAM. This ID is used by the WAM system to tie together the request sent to ERP and the response coming back from the ERP system. This ID should be sent back to WAM as part of the response message.

integrationDetails

sendDetails

Group

vendor

integrationDetails

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/Identification/ID

Vendor Number or Vendor Code. This has the same value both in WAM and the ERP system.

vendorName

integrationDetails

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/Organization/Name

Vendor Name

vendorLocationId

integrationDetails

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyLocation/LocationReference/LocationIdentification/ApplicationObjectKey/ID

WAM system generated Vendor Location ID.

locationName

integrationDetails

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyLocation/LocationReference/Name

Vendor Location Name

boStatus

integrationDetails

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/SupplierPartyTradingLocationProfile/Status/Code

OUWAMERP_SupplierPartyLocStatus

Vendor Location Status. Use DVM to translate the WAM system status to the equivalent ERP Status. WAM Statuses: Under Review, Active, Inactive

creationDateTime

integrationDetails

Field

Not Mapped.

organization

integrationDetails

Field

Not mapped. The organization is used to restrict access to certain records according to groups of users.

location

integrationDetails

Group

Vendor Location Address Information

address1

addressInformation

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyLocation/LocationReference/Address/LineOne

address2

addressInformation

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyLocation/LocationReference/Address/LineTwo

address3

addressInformation

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyLocation/LocationReference/Address/LineThree

address4

addressInformation

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyLocation/LocationReference/Address/LineFour

city

addressInformation

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyLocation/LocationReference/Address/CityName

state

addressInformation

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyLocation/LocationReference/Address/StateName

OUWAMERP_State

county

addressInformation

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyLocation/LocationReference/Address/CountyName

country

addressInformation

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyLocation/LocationReference/Address/CountryCode

OUWAMERP_Country

postal

addressInformation

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyLocation/LocationReference/Address/PostalCode

orderFromFlag

integrationDetails

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/SupplierPartyTradingLocationProfile/PurchasingEnabledIndicator

OUWAMERP_PurchasingEnabledFlag

Indicates whether purchasing from this Supplier/Vendor location is allowed. Use DVM to translate the WAM Order From Flag to the ERP Purchase Enabled Flag. WAM values: Allowed/NotAllowed.

payToFlag

integrationDetails

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/SupplierPartyTradingLocationProfile/PaymentRemittanceAllowedIndicator

OUWAMERP_PmntRemittanceAllowedFlag

Indicates whether Supplier/Vendor Location handles billing and payments. Use DVM to translate the WAM Pay To Flag to the ERP Payment Remittance Allowed Flag. WAM values: Allowed/NotAllowed.

payToLocation

integrationDetails

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/SupplierPartyTradingLocationProfile/TradingLocationProfileAlternateUsage/BillToLocationReference/LocationIdentification/ApplicationObjectKey/ID

In WAM, payToLocation is only populated if payToFlag is 'Not Allowed'. A Bill To Location or Pay To Location on a procurement identifies the location where the invoice is to be sent. This value must be a valid WAM Vendor Location ID that has already been synced to the ERP system.

currency

integrationDetails

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/SupplierPartyTradingLocationProfile/InvoiceCurrencyCode

OUWAMERP_CurrencyCode.dvm

Currency that the Vendor Location use.

paymentTerm

integrationDetails

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/SupplierPartyTradingLocationProfile/PaymentTerm/Code

OUWAMERP_PaymentTerm

Indicates the payment term code. Use DVM to translate the WAM Payment Term Code to the ERPPayment Term Code.

fob

integrationDetails

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/SupplierPartyTradingLocationProfile/FOBPointCode

OUWAMERP_FOB

Indicates the Free on Board (FOB) Code which identifies the delivery charge terms negotiated for the PO. Use DVM to translate the WAM FOB Code to the ERP FOB Code.

minimumOrderAmount

integrationDetails

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/MinimumOrderAmount

Minimum purchase order amount

autoPay

integrationDetails

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/SupplierPartyTradingLocationProfile/PaymentMethodCode

OUWAMERP_AutoPayFlag

In WAM, this is the auto invoice indicator. Use DVM to translate the WAM Auto Pay Flag to the ERP Payment Method Code. WAM Values: Authorize/Not Auhorize.

carrierFlag

integrationDetails

Field

Not Mapped

carrierLocationId

integrationDetails

Field

Not Mapped

vendorLocationCapability

integrationDetails

Group

Whole Vendor Location Capability Group Not Mapped

vendorLocationCapabilityList

vendorLocationCapability

List

capabilityType

vendorLocationCapabilityList

Field

commodities

integrationDetails

Group

insuranceExpirationDate

commodities

Field

Not Mapped

emailPOFlag

commodities

Field

Not Mapped

poEmailAddress

commodities

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyContact/Contact/ContactEmailCommunication/EmailCommunication/URI

Email address of the contact person

payTaxToVendor

commodities

Field

Not Mapped. Indicates whether to pay sales tax to the vendor location or not.

mainContact

integrationDetails

Group

Vendor Location's Main Contact Person.

contactType

mainContact

Field

Not Mapped.

firstName

mainContact

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyContact/Contact/PersonName/FirstName

Contact's first name

lastName

mainContact

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyContact/Contact/PersonName/FamilyName

Contact's last name

fullName

mainContact

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyContact/Contact/PersonName/FullName

Contact's Full Name.

mainContactPhone

integrationDetails

Group

Vendor Location's Phone Information.

phoneList

mainContactPhone

List

phoneType

phoneLIst

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyContact/Contact/ContactPhoneCommunication/PhoneCommunication/TypeCode

OUWAMERP_PhoneType

Phone Type whether it's the primary or business phone, mobile, fax, etc

countryCode

phoneLIst

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyContact/Contact/ContactPhoneCommunication/PhoneCommunication/CountryCode

Country code. Keep mapping even if WAM is not passing any value.

areaCode

phoneLIst

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyContact/Contact/ContactPhoneCommunication/PhoneCommunication/AreaCode

Area code. Keep mapping even if WAM is not passing any value.

phoneNumber

phoneLIst

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyContact/Contact/ContactPhoneCommunication/PhoneCommunication/LocalNumber

Phone number. Keep mapping even if WAM is not passing any value.

completeNumber

phoneLIst

Field

/SyncSupplierPartyListEBM/DataArea/SyncSupplierPartyList/PartyContact/Contact/ContactPhoneCommunication/PhoneCommunication/CompleteNumber

Complete Phone Number passed by WAM. Can have delimiters.

Supplier Party (Vendor/Vendor Location) Response Mapping Details (WAM to ERP)

ERP Sync Supplier Party Response Message

WAM Vendor Location Response MessageIWS: F1-UpdateAndTransitionSyncRequest

Comments

Full Path

Element Name

Parent Element

Type

F1-UpdateAndTransitionSyncRequest

Outermost

Tag

/SyncSupplierPartyListResponseEBM/DataArea/SyncSupplierPartyListResponse/Identification/BusinessComponentID

syncRequestId

F1-UpdateAndTransitionSyncRequest

Field

WAM Sync Request ID. The unique ID sent as part of the response message to tie it together to the request. When ERP processes the request successfully, it only sends back the WAM Sync Request ID.

externalIds

F1-UpdateAndTransitionSyncRequest

Group

entityIdList

externalIds

List

entity

entityIdList

Field

externalPkValue1

entityIdList

Field

externalPkValue2

entityIdList

Field

externalPkValue3

entityIdList

Field

externalPkValue4

entityIdList

Field

externalPkValue5

entityIdList

Field

exceptionInformation

F1-UpdateAndTransitionSyncRequest

Group

When ERP encounters an error while processing the request, it sends back the WAM Sync Request ID and the error or fault information.

exceptionInformationList

exceptionInformation

List

sequence

exceptionInformationList

Field

messageCategory

exceptionInformationList

Field

Defaulted by Integration using property name OUWAM.Generic.MessageCategory in the ConfigurationProperties file.

messageNumber

exceptionInformationList

Field

Defaulted by Integration using property name OUWAM.GenericBusinessException.MessageNumber in the ConfigurationProperties file.

SyncRequisitionListResponseEBM/EBMHeader/FaultNotification/FaultMessage/Text

comments

exceptionInformationList

Field

Error comments or error message

messageParameters

exceptionInformationList

List

parameterSequence

messageParameters

Field

messageParameterValue

messageParameters

Field

Appendix A - Data Mapping

Configuration Properties File

This section lists the configurations stored in the ConfigurationProperties.xml file located in <PRODUCT.HOME>/MDS-Artifacts/OUWAMERP/config/ and the ConfigurationProperties.xml is stored in Metadata Service (MDS).

For information on modifying configuration properties, refer to the " Configuration Properties " section in Chapter 4 : Configuration Guidelines .

Two types of configuration properties are managed in the configuration files:

•

Module Configurations : Module configurations are the properties that are shared by multiple processes within this integration.

•

Service Configurations : Service configurations are the properties that are used by a specific ABCS.

Module Configurations

Module Configurations have application level properties which are used by all the SOA composites.

Module Name

Default / Shipped Value

Description

OUWAM.Integration.User

SYSUSER

The Oracle Utilities Work and Asset Management user ID, which is defaulted in the message going into Oracle Utilities Work and Asset Management from the integration.

OUWAM.External.System

ERP

The external system configured in Oracle Utilities Work and Asset Management. The external system is defaulted from this property into the message going into Oracle Utilities Work and Asset Management from the integration.

OUWAM.InitialLoad.Flag

F1IC

Initial load passed into message going to Oracle Utilities Work and Asset Management from the integration.

OUWAM.Allowed.ValueFlag

W1AL

Oracle Utilities Work and Asset Management Allowed Flag Value populates WAM flags in the integration and passed into message going to Oracle Utilities Work and Asset Management from the integration.

OUWAM.NotAllowed.ValueFlag

W1NA

Oracle Utilities Work and Asset Management Not Allowed Flag Value populates WAM flags in the integration and passed into message going to Oracle Utilities Work and Asset Management from the integration.

OUWAM.Generic.MessageCategory

11017

The message category that the integration layer passes to Oracle Utilities Work and Asset Management as part of the response error message.

OUWAM.GenericBusinessException.MessageNumber

11001

The message number that the integration layer passes back to Oracle Utilities Work and Asset Management as part of the response error message.

Service Configurations

Service Configuration properties are specific to SOA composites. These are used to make changes in specific composite behavior.

Service Name

Property Name

Default / Shipped Value

Default

System ID

(Initiating

System)

Description

All

All of the service names in the configuration properties file will have these two property names to control email notifications on errors.

BusinessError.NotificationFlag

false

If set to true, business error notification is sent via Email.

TechnicalError.NotificationFlag

false

If set to true, technical error notification is sent via Email.

Worker (Employee) Synchronization Process

SyncWorkerERPReqABCSImpl

Default.SystemID

ERP_01

SyncWorkerOUWAMUtilitiesProvABCSImpl

Default.SystemID

OUWAM_01

OUWAM.W1-SyncRequestInbound

.Endpoint.URL

@wam_protocol://@wam_host:

@wam_port/@wam_ctx1/W1- SyncRequestInbound

Endpoint URL for the Oracle Utilities Work and Asset Management inbound web service, which is used for Worker Sync.

OUWAM.Employee.Target.MO

W1-EMP

Maintenance object code, which is passed to Oracle Utilities Work and Asset Management for the Worker (Employee) sync.

SyncWorkerRespOUWAMUtilitiesReqABCSImpl

Default.SystemID

OUWAM_01

Supplier Party (Vendor/Vendor Location) Synchronization Process (ERP to WAM)

SyncSupplierPartyERPReqABCSImpl

Default.SystemID

ERP_01

SyncSupplierPartyOUWAMUtilitiesProvABCSImpl

Default.SystemID

OUWAM_01

Endpoint URL for the Oracle Utilities Work and Asset Management inbound web service, which is used for Supplier Party Sync.

OUWAM.W1-SyncRequestInbound

.Endpoint.URL

@wam_protocol://@wam_host:

@wam_port/@wam_ctx1/W1- SyncRequestInbound

OUWAM.VendorLoc.Target.MO

W1-VENDORLOC

Maintenance object code, which is passed to Oracle Utilities Work and Asset Management for the Supplier Party (Vendor) sync.

SyncSupplierPartyRespOUWAMUtilitiesReqABCSImpl

Default.SystemID

OUWAM_01

Chart of Accounts (Cost Center) Synchronization Process

SyncChartOfAccountsERPReqABCSImpl

Default.SystemID

ERP_01

SyncChartOfAccountsOUWAMUtilitiesProvABCSImpl

Default.SystemID

OUWAM_01

Endpoint URL for the Oracle Utilities Work and Asset Management inbound web service, which is used for Chart of Accounts Sync.

OUWAM.W1-SyncRequestInbound

.Endpoint.URL

@wam_protocol://@wam_host:

@wam_port/@wam_ctx1/W1- SyncRequestInbound

OUWAM.CostCenter.Target.MO

W1-COSTCTR

Maintenance object code, which is passed to Oracle Utilities Work and Asset Management for the Chart of Accounts (Cost Center) sync.

SyncChartOfAccountsRespOUWAMUtilitiesReq

ABCSImpl

Default.SystemID

OUWAM_01

Stock Item Synchronization Process

SyncStockItemERPReqABCSImpl

Default.SystemID

ERP_01

SyncStockItemOUWAMUtilitiesProvABCSImpl

Default.SystemID

OUWAM_01

OUWAM.W1-SyncRequestInbound

.Endpoint.URL

@wam_protocol://@wam_host/

@wam_port/@wam_ctx1/

W1-SyncRequestInbound

Endpoint URL for the WAM inbound service used for Stock Item Sync. @wam_ctx1 can be ouaf/webservices or ouaf/XAIApp/xaiserver

OUWAM.StockItem.Target.MO

W1-RESRCTYPE

Maintenance object code passed to WAM for the Stock Item sync.

OUWAM.InventoryExpense.Code

ERP_INVENTORY

ERP

SyncStockItemRespOUWAMUtilitiesReqABCSImpl

Default.SystemID

OUWAM_01

Storeroom Item (Stock Item Detail) Synchronization Process

SyncStoreroomItemERPReqABCSImpl

Default.SystemID

ERP_01

SyncStoreroomItemOUWAMUtilitiesProvABCSImpl

Default.SystemID

OUWAM_01

OUWAM.W1-SyncRequestInbound

.Endpoint.URL

@wam_protocol://@wam_host/

@wam_port/@wam_ctx1/ W1-SyncRequestInbound

Endpoint URL for the WAM inbound service used for Storeroom (Stock Item Details) Sync. @wam_ctx1 can be ouaf/webservices or ouaf/XAIApp/xaiserver

OUWAM.StoreroomItem.Target.MO

W1-SID

Maintenance object code, pass to WAM for Storeroom Item Sync.

SyncStoreroomItemRespOUWAMUtilitiesReqABCSImpl

Default.SystemID

OUWAM_01

Purchase Order Synchronization Process

SyncPurchaseOrderERPReqABCSImpl

ERP_01

SyncPurchaseOrderOUWAMUtilitiesProvABCSImpl

WAM

Endpoint URL for the WAM inbound service used for Purchase Order Transactional Sync. @wam_ctx1 can be ouaf/webservices or ouaf/XAIApp/xaiserver.

OUWAM.W1-PurchaseOrder

.Endpoint.URL

@wam_protocol://@wam_host/

@wam_port/@wam_ctx1/ /

W1-PurchaseOrderIntegInbound

OUWAM.PO.Target.MO

W1-POHDR

Maintenance object code, pass to WAM for Purchase Order Transaction Sync.

OUWAM.PO.BO

W1-PurchaseOrderIntegInbound

Business object code pass to WAM for Purchase Order Transactional Sync

OUWAM.Integration.POCreatedBy

Sample: W1IN

WAM.Integration.POInitiator

Sample: USER01

Default WAM Purchase Order Initiator. This should be a valid WAM User ID.

SyncPurchaseOrderRespOUWAMUtilitiesReqABCSImpl

Default.SystemID

OUWAM_01

Shipment Receipt (Purchase Receipt) Synchronization Process

SyncShipmentReceiptERPReqABCSImpl

Default.SystemID

ERP_01

SyncShipmentReceiptOUWAMUtilitiesProvABCSImpl

Default.SystemID

OUWAM_01

OUWAM.W1-ReceiptIntegInbound

.Endpoint.URLL

@wam_protocol://@wam_host/

@wam_port/@wam_ctx1/W1-ReceiptIntegInbound

Endpoint URL for the WAM inbound service used for Receipt Transaction Inbound Sync. @wam_ctx1 can be ouaf/webservices or ouaf/XAIApp/xaiserver

OUWAM.Receipt.Target.MO

W1-RCPTHDR

Maintenance object code, pass to WAM for Receipt Transactional Sync.

OUWAM.Receipt.BO

W1-ReceiptIntegInbound

Business object code pass to WAM for Receipt Transactional Sync

SyncShipmentReceiptRespOUWAMUtilitiesReq

ABCSImpl

Default.SystemID

OUWAM_01

Blanket Contract (Purchase Agreement) Synchronization Process

SyncBlanketPurchaseAgreementERPReqABCSImpl

ERP_01

SyncBlanketPurchaseAgreementRespOUWAMUtilitiesReqABCSImpl

Default.SystemID

OUWAM_01

SyncBlanketPurchaseAgreementOUWAMUtilitiesProv

ABCSImpl

Default.SystemID

OUWAM_01

OUWAM.W1-BlanketContractIntegInbound

.Endpoint.URL

@wam_protocol://@wam_host/

@wam_port/@wam_ctx1/

W1-BlanketContractIntegInbound

Endpoint URL for the WAM inbound service used for Blanket Contract Transaction Inbound Sync. @wam_ctx1 can be ouaf/webservices or ouaf/XAIApp/xaiserver.

OUWAM.BlanketContract.Target.MO

W1-BCHEADER

Maintenance object code, pass to WAM for Blanket Contract Transactional Sync.

OUWAM.BlanketContract.BO

W1-BlanketContractIntegInbound

Business object code pass to WAM for Blanket Contract Transactional Sync

Invoice Payment (Disbursement) Synchronization Process

SyncDisbursementPaymentERPReqABCSImpl

Default.SystemID

ERP_01

SyncDisbursementPaymentRespOUWAMUtilitiesReq

ABCSImpl

OUWAM_01

OUWAM.W1-InvoicePaymentIntegInbound.URL

@wam_protocol://@wam_host/

@wam_port/@wam_ctx1/

W1-InvoicePaymentIntegInbound

Endpoint URL for the WAM inbound service used for Invoice Transaction Inbound Sync. @wam_ctx1 can be ouaf/webservices or ouaf/XAIApp/xaiserver

OUWAM.InvoicePayment.Target.MO

W1-INVCHDR

Maintenance object code, pass to WAM for Invoice Payment Sync.

OUWAM.InvoicePayment.BO

W1-InvoicePaymentIntegInbound

Business object code pass to WAM for Invoice Payment Transactional Sync

Invoice Synchronization Process

SyncInvoiceERPReqABCSImpl

Default.SystemID

ERP_01

SyncInvoiceRespOUWAMUtilitiesReqABCSImpl

Default.SystemID

OUWAM_01

SyncInvoiceOUWAMUtilitiesProvABCSImpl

Default.SystemID

OUWAM_01

OUWAM.W1-InvoiceIntegInbound

.Endpoint.URL

@wam_protocol://@wam_host/

@wam_port/@wam_ctx1/

W1-InvoiceIntegInbound

Endpoint URL for the WAM inbound service used for Invoice Transaction. @wam_ctx1 can be ouaf/webservices or ouaf/XAIApp/xaiserver

OUWAM.Invoice.Target.MO

W1-INVCHDR

OUWAM.Invoice.BO

W1-InvoiceIntegInbound

Item Balance (Stock Transaction) Synchronization Process

SyncItemBalanceERPReqABCSImpl

Default.SystemID

ERP_01

SyncItemBalanceOUWAMUtilitiesProvABCSImpl

Default.SystemID

OUWAM_01

OUWAM.W1-StockTransIntegInbound

.Endpoint.URL

@wam_protocol://@wam_host/

@wam_port/@wam_ctx1/ W1-StockTransIntegInbound

Endpoint URL for the WAM inbound service used for Stock Transaction Transactional Inbound Sync. @wam_ctx1 can be ouaf/webservices or ouaf/XAIApp/xaiserver

OUWAM.StockTransaction.Target.MO

W1-STOCKTRAN

Maintenance object code, pass to WAM for Stock Transaction Transactional Sync.

OUWAM.StockTransaction.BO

W1-StockTransIntegInbound

Business object code pass to WAM for Stock Transaction Transactional Sync

SyncItemBalanceRespOUWAMUtilitiesReqABCSImpl

Default.SystemID

OUWAM_01

GL Transaction (Accounting Entry) Synchronization Process

SyncAccountingEntryERPReqABCSImpl (ERP to WAM)

Default.SystemID

ERP_01

SyncAccountingEntryOUWAMUtilitiesProvABCSImpl

(ERP to WAM)

Default.SystemID

OUWAM_01

OUWAM.W1-FinancialTransaction

.Endpoint.URL

@wam_protocol://@wam_host/

@wam_port/@wam_ctx1/ W1-FinancialTransIntegInbound

Endpoint URL for the WAM inbound service used for Stock Transaction Transactional Inbound Sync. @wam_ctx1 can be ouaf/webservices or ouaf/XAIApp/xaiserver

OUWAM.FT.MO

W1-FT

Maintenance object code, pass to WAM for Financial Transaction Transactional Sync.

OUWAM.FT.BO

W1-FinancialTransIntegInbound

Business object code pass to WAM for Financial Transaction Transactional Sync

OUWAM.FT.DistributionCode

DSCNT-DC

SyncAccountingEntryRespOUWAMUtilitiesReq

ABCSImpl (ERP to WAM)

Default.SystemID

OUWAM_01

Material Issue - Inventory Transaction Synchronization Process

SyncMatIssueInventoryTxnERPReqABCSImpl

Default.SystemID

ERP_01

SyncMatIssueInventoryTxnRespOUWAMUtilitiesReq

ABCSImpl

Default.SystemID

OUWAM_01

OUWAM.W1-MaterialIssueIntegInbound

.Endpoint.URL

@wam_protocol://@wam_host/

@wam_port/@wam_ctx1/ W1-MaterialIssueIntegInbound

Endpoint URL for the WAM inbound service used for Material Issue Transactional Inbound Sync. @wam_ctx1 can be ouaf/webservices or ouaf/XAIApp/xaiserver

OUWAM.MaterialIssue.Target.MO

W1-MATISSLIN

Business object code pass to WAM for Material Issue Transactional Sync

OUWAM.MaterialIssue.BO

W1-MaterialIssueIntegInbound

Maintenance object code, pass to WAM for Material Issue Transactional Sync.

SyncMatIssueInventoryTxnRespOUWAMUtilitiesReqABCSImpl

Default.SystemID

OUWAM_01

Material Return - Inventory Transaction Synchronization Process

SyncMatReturnInventoryTxnERPReqABCSImpl

Default.SystemID

ERP_01

SyncMatReturnInventoryTxnOUWAMUtilitiesProv

ABCSImpl

OUWAM_01

Endpoint URL for the WAM inbound service used for Material Return Transactional Inbound Sync. @wam_ctx1 can be ouaf/webservices or ouaf/XAIApp/xaiserver

OUWAM.W1-MaterialReturnIntegInbound

.Endpoint.URL

@wam_protocol://@wam_host/

@wam_port/@wam_ctx1/ W1-MaterialReturnIntegInbound

OUWAM.MaterialReturn.BO

W1-MATRTNLIN

Business object code pass to WAM for Material Return Transactional Sync

OUWAM.MaterialReturn.Target.MO

W1-MaterialReturnIntegInbound

Maintenance object code, pass to WAM for Material Return Transactional Sync.

OUWAM.MaterialReturn.Percentage

100

SyncMatReturnInventoryTxnRespOUWAMUtilitiesReq

ABCSImpl

Default.SystemID

OUWAM_01

Purchase Return - Inventory Transaction Synchronization Process

SyncPurReturnInventoryTxnERPReqABCSImpl

Default.SystemID

ERP_01

SyncPurReturnInventoryTxnOUWAMUtilitiesProv

ABCSImpl

Default.SystemID

OUWAM_01

OUWAM.PurchaseReturnIntegInbound

.Endpoint.URL

@wam_protocol://@wam_host/

@wam_port/@wam_ctx1/ W1-PurchaseReturnIntegInbound

Endpoint URL for the WAM inbound service used for Purchase Return Transactional Inbound Sync. @wam_ctx1 can be ouaf/webservices or ouaf/XAIApp/xaiserver

OUWAM.PurchaseReturn.BO

W1-RTNLINE

Business object code pass to WAM for Purchase Return Transactional Sync

OUWAM.PurchaseReturn.Target.MO

W1-PurchaseReturnIntegInbound

Maintenance object code, pass to WAM for Purchase Return Transactional Sync.

OUWAM.ReturnType

W1EX

Possible WAM values are credit or exchange. Defaulted to credit value.

OUWAM.AdjustmentType

W1IN

Possible WAM values are Inventory (W1IN) or In Receipt (W1IR). Defaulted to In receipt value.

SyncPurReturnInventoryTxnRespOUWAMUtilitiesReq

ABCSImpl

Default.SystemID

OUWAM_01

GL Transaction (Accounting Entry) Synchronization Process (WAM to ERP)

SyncAccountingEntryOUWAMUtilitiesReqABCSImpl

(WAM to ERP)

Default.SystemID

OUWAM_01

Code set for Activity ID coming from Oracle Utilities Work and Asset Management for the message going into Enterprise Resource Planning system.

OUWAM.ActivityId.Code

ActivityId

OUWAM.TimesheetDetailId.Code

TimesheetDetailId

Code set for Timesheet Detail ID coming from Oracle Utilities Work and Asset Management for the message going into Enterprise Resource Planning system.

OUWAM.OtherDirectChargesId.Code

OtherDirectChargesId

Code set for Other Direct Charges ID coming from Oracle Utilities Work and Asset Management for the message going into Enterprise Resource Planning system.

OUWAM.MaterialIssueLineId.Code

MaterialIssueLineId

Code set for Material Issue Line ID coming from Oracle Utilities Work and Asset Management for the message going into Enterprise Resource Planning system.

OUWAM.MaterialReturnLineId.Code

MaterialReturnLineId

Code set for Material Return Line ID coming from Oracle Utilities Work and Asset Management for the message going into Enterprise Resource Planning system.

OUWAM.InventoryCountLineId.Code

InventoryCountLineId

Code set for Inventory Count Line ID coming from Oracle Utilities Work and Asset Management for the message going into Enterprise Resource Planning system.

OUWAM.AcceptLineId.Code

AcceptLineId

Code set for Accept Line ID coming from Oracle Utilities Work and Asset Management for the message going into Enterprise Resource Planning system.

OUWAM.InvoiceLineId.Code

InvoiceLineId

Code set for Invoice Line ID

coming from Oracle Utilities Work

and Asset Management for the

message going into the Enterprise

Resource Planning system.

OUWAM.ReturnId.Code

ReturnId

Code set for Return ID coming from Oracle Utilities Work and Asset Management for the message going into Enterprise Resource Planning system.

OUWAM.InventoryAdjustmentId.Code

InventoryAdjustmentId

Code set for Inventory Adjustment ID coming from Oracle Utilities Work and Asset Management for the message going into Enterprise Resource Planning system.

OUWAM.CostCenter.Code

CostCenter

Code set GL Element value coming from Oracle Utilities Work and Asset Management for the message going into Enterprise Resource Planning system.

OUWAM.ExpenseCode.Code

ExpenseCode

Code set for Expense code value coming from Oracle Utilities Work and Asset Management for the message going into Enterprise Resource Planning system.

SyncAccountingEntryRespERPReqABCSImpl

Default.SystemID

ERP_01

SyncAccountingEntryRespOUWAMUtilitiesProv

ABCSImpl

Default.SystemID

OUWAM_01

OUWAM.

F1-UpdateAndTransitionSyncRequest

.Endpoint.URL

@wam_protocol://@wam_host/

@wam_port/@wam_ctx1/ F1-UpdateAndTransitionSyncRequest

Endpoint URL for the WAM inbound service used to handle responses. @wam_ctx1 can be ouaf/webservices or ouaf/XAIApp/xaiserver

Purchase Requisition Synchronization Process

SyncRequisitionRespERPReqABCSImpl

Default.SystemID

ERP_01

SyncRequisitionOUWAMUtilitiesReqABCSImpl

Default.SystemID

OUWAM_01

SyncRequisitionRespOUWAMUtilitiesProvABCSImpl

Default.SystemID

OUWAM_01

OUWAM.

F1-UpdateAndTransitionSyncRequest

.Endpoint.URL

@wam_protocol://@wam_host/

@wam_port/@wam_ctx1/ F1-UpdateAndTransitionSyncRequest

Endpoint URL for the WAM inbound service used to handle responses. @wam_ctx1 can be ouaf/webservices or ouaf/XAIApp/xaiserver

Supplier Party (Vendor/Vendor Location) Synchronization Process (WAM to ERP)

SyncSupplierPartyOUWAMUtilitiesReqABCSImpl

(WAM to ERP)

Default.SystemID

OUWAM_01

SyncSupplierPartyRespERPReqABCSImpl

(WAM to ERP)

Default.SystemID

ERP_01

SyncSupplierPartyRespOUWAMUtilitiesProvABCSImpl

(WAM to ERP)

Default.SystemID

OUWAM_01

OUWAM.

F1-UpdateAndTransitionSyncRequest

.Endpoint.URL

@wam_protocol://@wam_host/

@wam_port/@wam_ctx1/

F1-UpdateAndTransitionSyncRequest

Endpoint URL for the WAM inbound service used to handle responses. @wam_ctx1 can be ouaf/webservices or ouaf/XAIApp/xaiserver.

Material Requisition Synchronization Process

SyncMaterialRequisitionOUWAMUtilitiesReqABCSImpl

Default.SystemID

OUWAM_01

SyncMaterialRequisitionRespERPReqABCSImpl

Default.SystemID

ERP_01

SyncMaterialRequisitionRespOUWAMUtilitiesProv

ABCSImpl

Default.SystemID

OUWAM_01

OUWAM.

F1-UpdateAndTransitionSyncRequest

.Endpoint.URL

@wam_protocol://@wam_host/

@wam_port/@wam_ctx1/

F1-UpdateAndTransitionSyncRequest

Endpoint URL for the WAM inbound service used to handle responses. @wam_ctx1 can be ouaf/webservices or ouaf/XAIApp/xaiserver.

Domain Value Maps (DVMs)

The following table lists the DVMs included for the integration.

For information on creating DVMs refer to the " Domain Value Maps " section in Chapter 4 : Configuration Guidelines . For more information about on working with DVMs, see the section "Working with Domain Value Maps" in Oracle® Fusion Middleware Developing SOA Applications with Oracle SOA Suite documentation.

DVM

Integration Points

Description

OUWAMERP_AccountingEntryType

Sync Accounting Entry

Maps the Enterprise Resource Planning system Accounting Entry type to the Oracle Utilities Work and Asset Management Accounting Entry type (GL Transaction type) and vice versa.

OUWAMERP_AllowanceCode

Sync Invoice

Maps the Enterprise Resource Planning system Allowance Code to the Integration Allowance Code to determine where to map the corresponding Enterprise Resource Planning system allowance amount to the correct Oracle Utilities Work and Asset Management specific allowance amount fields (Example: overrideDiscountAmount).

OUWAMERP_AssetClassificationCode

Sync Stock Item

Maps the Enterprise Resource Planning system Asset Classification Code to the Oracle Utilities Work and Asset Management Stock Category and vice versa.

OUWAMERP_AutoPayFlag

Sync Supplier Party Storeroom

Maps the Enterprise Resource Planning system Payment Method Code to the Oracle Utilities Work and Asset Management Auto Pay Flag and vice versa.

OUWAMERP_BinType

Sync Storeroom Item

Maps the Enterprise Resource Planning system Payment Method Code to the Oracle Utilities Work and Asset Management Auto Pay Flag and vice versa.

OUWAMERP_BlanketContractStatusCode

Sync Blanket Contract

Maps the Enterprise Resource Planning system Blanket Contract Status to the Oracle Utilities Work and Asset Management Blanket Contract Status Code and vice versa.

OUWAMERP_BlanketContractLineStatusCode

Sync Blanket Contract

Maps the Enterprise Resource Planning system Blanket Contract Line Status to the Oracle Utilities Work and Asset Management Blanket Contract Line Status Code and vice versa.

OUWAMERP_Buyer

Sync Requisition

Sync Purchase Order

Sync Invoice

Maps Enterprise Resource Planning system Buyer to the Oracle Utilities Work and Asset Management Buyer and vice versa.

OUWAMERP_ChargeCode

Sync Invoice

Maps the Enterprise Resource Planning system Charge Code to the Integration Charge Code to determine where to map the corresponding Enterprise Resource Planning system charge amount to the correct Oracle Utilities Work and Asset Management specific charge amount fields (Example: freightAmount).

OUWAMERP_ChartOfAccountsStatus

Sync Chart of Accounts

Maps the Enterprise Resource Planning system Chart of Accounts status to the Oracle Utilities Work and Asset Management Cost Center status and vice versa

OUWAMERP_CheckType

Sync Invoice Payment

Maps Enterprise Resource Planning system Check Type to Oracle Utilities Work and Asset Management Check Type and vice versa.

OUWAMERP_CommodityCategory

Sync Item

Maps Enterprise Resource Planning system Commodity Category to the Oracle Utilities Work and Asset Management Commodity Category and vice versa.

OUWAMERP_CommodityName

Sync Item

Maps Enterprise Resource Planning system Commodity Name to the Oracle Utilities Work and Asset Management Commodity Name and vice versa.

OUWAMERP_CommodityType

Sync Item

Maps Enterprise Resource Planning system Commodity Type to the Oracle Utilities Work and Asset Management Commodity Type and vice versa. Maps Enterprise Resource

OUWAMERP_Composition

Sync Item

Maps Enterprise Resource Planning system Composition to the Oracle Utilities Work and Asset Management Composition and vice versa.

OUWAMERP_Country

Sync Supplier Party

Sync Worker

Sync Blanket Contract

Sync Purchase Requisition

Sync Purchase Order

Maps Enterprise Resource Planning system Country to Oracle Utilities Work and Asset Management Country and vice versa.

OUWAMERP_CurrencyCode

Sync Accounting Entry

Sync Supplier Party

Sync Purchase Requisition

Sync Purchase Order

Maps the Enterprise Resource Planning system currency code to the Oracle Utilities Work and Asset Management currency code and vice versa.

OUWAMERP_FOB

Sync Supplier Party

Sync Blanket Contract

Sync Purchase Order

Maps Enterprise Resource Planning system FOB code to Oracle Utilities Work and Asset Management FOB code and vice versa.

OUWAMERP_HazardousFlag

Sync Item

Maps Enterprise Resource Planning system Hazardous flag to Oracle Utilities Work and Asset Management Hazardous flag and vice versa.

OUWAMERP_HazardousType

Sync Item

Maps Enterprise Resource Planning system Hazardous Code to Oracle Utilities Work and Asset Management Hazardous Type and vice versa.

OUWAMERP_InventoryAssetFlag

Sync Item

Maps Enterprise Resource Planning system Inventory Asset Flag to Oracle Utilities Work and Asset Management Capital Spare Flag and vice versa.

OUWAMERP_InvoiceAutoPayIndicator

Sync Invoice

ERP Invoice Auto Pay Indicator to WAM Invoice Auto Pay Indicator

OUWAMERP_InvoiceItemType

Sync Invoice

ERP Invoice Item Type to WAM Invoice Item Type. The invoice line items are cost Differently and some possible Item cost types are Credit, Freight, Normal and , Extra Cost.

OUWAMERP_InvoiceLineStatusCode

Sync Invoice

Maps Enterprise Resource Planning system Invoice Line Status Code to Oracle Utilities Work and Asset Management Invoice Line Status Code and vice versa.

OUWAMERP_InvoiceStatusCode

Sync Invoice

Maps Enterprise Resource Planning system Invoice Status Code to Oracle Utilities Work and Asset Management Invoice Line Status Code and vice versa.

OUWAMERP_ItemType

Sync Requisition

Sync Purchase Order

Maps Enterprise Resource Planning system Hazardous Code to Oracle Utilities Work and Asset Management Hazardous Type and vice versa.

OUWAMERP_JobCode

Sync Worker

Maps Enterprise Resource Planning system Job code to combination of Oracle Utilities Work and Asset Management Job code and Principal craft and vice versa.

OUWAMERP_JournalSourceCode

Sync Accounting Entry

Maps the Enterprise Resource Planning system Journal Source Code to the Integration Journal Source Code to determine where to map the Enterprise Resource Planning system Ledger Indentification Id to the correct Oracle Utilities Work and Asset Management specific ledger id (invoiceLineId or materialIssueLineId).

OUWAMERP_LocationId

Sync Requisition

Sync Purchase Order

Sync Material Request

Maps Enterprise Resource Planning system Job code to combination of Oracle Utilities Work and Asset Management Job code and Principal craft and vice versa.

OUWAMERP_ManufacturerCode

Convert ERP Manufacturer Code to WAM Manufacturer Code

OUWAMERP_MaterialRequestStatusCode

Sync Material Request

Maps Enterprise Resource Planning system Material Request Status Code to Oracle Utilities Work and Asset Management Material Request Status Code and vice versa.

OUWAMERP_OrganizationUnitID

Sync Supplier Party

Sync Worker

Maps Enterprise Resource Planning system Organization unit ID to Oracle Utilities Work and Asset Management organization unit ID and vice versa

OUWAMERP_PaymentTerm

Sync Supplier Party

Sync Blanket Contract

Sync Purchase Order

Maps Enterprise Resource Planning system payment term to Oracle Utilities Work and Asset Management payment term and vice versa.

OUWAMERP_PhoneType

Sync Supplier Party

Sync Worker

Maps Enterprise Resource Planning system Phone type to Oracle Utilities Work and Asset Management phone type and vice versa.

OUWAMERP_PmntRemittanceAllowedFlag

Sync Supplier Party

Maps Enterprise Resource Planning system payment remittance allowed flag to Oracle Utilities Work and Asset Management Pay To Flag and vice versa.

OUWAMERP_POLineStatusCode

Sync Purchase Order

Maps Enterprise Resource Planning system Purchase Order Line Status Code to Oracle Utilities Work and Asset Management Purchase Order Line Status Code and vice versa.

OUWAMERP_POStatusCode

Sync Purchase Order

Maps Enterprise Resource Planning system Purchase Order Status Code to Oracle Utilities Work and Asset Management Purchase Order Status Code and vice versa.

OUWAMERP_PurchasingEnabledFlag

Sync Supplier Party

Maps Enterprise Resource Planning system purchasing enabled flag to Oracle Utilities Work and Asset Management purchasing enabled flag and vice versa.

OUWAMERP_State

Sync Supplier Party

Sync Worker

Sync Blanket Contract

Sync Purchase Requisition

Sync Purchase Order

Maps Enterprise Resource Planning system State to Oracle Utilities Work and Asset Management State and vice versa.

OUWAMERP_SupplierPartyLocStatus

Sync Supplier Party

Maps Enterprise Resource Planning system supplier party location status to Oracle Utilities Work and Asset Management supplier party (Vendor) location status and vice versa.

OUWAMERP_TaxType

Sync Purchase Order

Sync Invoice

Maps Enterprise Resource Planning tax type to Oracle Utilities Work and Asset Management (OUWAM) tax type. Example: City or State Tax Type. Tax type is defined as a characteristic type in OUWAM.

OUWAMERP_TaxTypeValue

Sync Purchase Order

Sync Invoice

Maps Enterprise Resource Planning tax type value to Oracle Utilities Work and Asset Management tax type value.

Example: SF City Tax or CA State Tax. Tax type value is defined as a characteristic type value in OUWAM.

OUWAMERP_UsageExpenseCode

Sync Item

Maps Enterprise Resource Planning system Usage Expense Code to Oracle Utilities Work t and Asse Management Usage Expense Code and vice versa.

OUWAMERP_WorkerStatus

Sync Worker

Maps Enterprise Resource Planning system Worker status to Oracle Utilities Work and Asset Management worker status and vice versa.

OUWAMERP_WorkerType

Sync Worker

Maps Enterprise Resource Planning system Worker type to Oracle Utilities Work and Asset Management worker type and vice versa.

Appendix A - Data Mapping

Part 1

About the Integration

This section provides an overview of the participating applications and information regarding the business processes addressed by this integration.

This section contains the following chapters:

•

Chapter 1 : Integration Overview

•

Chapter 2 : Technical Overview

•

Chapter 3 : Integration Processes

Part 2

Implementation Guidelines

This section provides details on how to configure the participating applications and middleware layer for this integration. It also includes information on error handling, monitoring, security and customization options.

The section contains the following chapters:

•

Chapter 4 : Configuration Guidelines

•

Chapter 5 : Monitoring and Troubleshooting

•

Chapter 6 : Extensibility Options

•

Chapter 7 : Application Security

Preface

Audience

This document is intended for anyone implementing the Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning product.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit: http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info

or

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Integration Documentation and Resources

The following additional documentation resources are available for this release:

Product Documentation

Resource

Location

Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning Installation Guide

The same folder as this document, with the distribution for this product.

The most up to date versions of these documents are available on the Oracle Utilities Global Business Unit Portal at: http://docs.oracle.com/cd/E72219_01/documentation.html

Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning Implementation Guide

Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning Release Notes

Oracle Utilities Work and Asset Management Documentation:

•

Installation Guide

•

Admin Guide

•

Business User Guide

Please also refer to Bug #2451006 which will accumulate all WAM patches required for the integration.

Refer to Oracle Utilities Work and Asset Management documentation located on the Oracle Technology Network.

http://docs.oracle.com/cd/E72219_01/documentation.html

Additional Documentation

Resource

Location

SOA Suite 12c documentation

Refer to the SOA documentation at: http://www.oracle.com/technetwork/middleware/soasuite/documentation/index.html

Oracle Support

Visit My Oracle Support at https://support.oracle.com regularly to stay informed about updates and patches.

Access the support site for the Edge Application Certification Matrix for Oracle Utilities Products (Doc ID 1454143.1) or refer to the Oracle Utilities Integrations page at http://my.oracle.com/site/tugbu/productsindustry/productinfo/utilities/integration/index.htm

Oracle Technology Network (OTN)

Latest versions of documents

http://www.oracle.com/technetwork/index.html

Oracle Universityfor training opportunities

http://education.oracle.com/

Web Services Security

For more information about Web services security using Oracle Fusion Middleware 12c refer to https://docs.oracle.com/middleware/12211/cross/webservicestasks.htm.

Oracle Fusion Middleware 12c documentation

http://docs.oracle.com/en/middleware/

Oracle Fusion Middleware "What's New In Oracle WebLogic Server"

Section: Standards Support, Supported Configurations and WebLogic Server Compatibility, Database Interoperability

For additional information on the type of database to use.

http://docs.oracle.com/middleware/1221/wls/NOTES/toc.htm

Instructions on installing this integration on non-Windows/ Linux platforms

Refer to Oracle Support Knowledge Article ID 1349320.1.

Common Terms Used in this Guide

This documentation includes the following terms:

Term

Definition

ABCS

Application Business Connector Services

A requestor ABCS accepts the request from the client application through a client-specific Application Business Message (ABM) and returns the response to the client application through a client-specific ABM. The client side ABM is the payload that is passed by the requestor application to the requestor ABCS.

AIA

Oracle Application Integration Architecture

AP

Accounts Payable

API

Application Programming Interface

AST

Application Specific Technology

BPEL

Business Process Execution Language

DVM

Domain Value Map

EBM

Enterprise Business Messages - Packets of data which the Mediator or JCA adapter accepts from requesters and routes to providers. They carry the pieces of data needed for the requests to be understood and serviced.

EBO/EBF

Enterprise Business Object

EBS

Enterprise Business Service

Edge application

The applications that are involved in the two-way integration processes - Oracle Utilities Work and Asset Management and other Enterprise Resource Planning applications.

ERP

Enterprise Resource Planning

ESC

Enterprise Resource Planning system Supply Chain business model

ESS

Oracle Enterprise Scheduler Service

GL

General Ledger

JMS

Java Message Service - The JMS producers are responsible for posting the message to the Consumer JMS Queue for the corresponding target application.

JMS Adapter Consumer

JMS adapter used in the SOA composite to read message from a queue is referred to as a Consumer. The adapter has Consumer as a part of the name. For example, SyncWorkerOUWAMUtilitiesJMSConsumer.

JMS Adapter Producer

The JMS adapter used in the SOA composite to write a message to a queue is referred to as a Producer. The adapter has Producer as a part of the name. For example, SyncWorkerERPJMSProducer.

MDS

Metadata Store

Participating Application

One of the two applications involved in the two-way integration processes- Oracle Utilities Work and Asset Management, Enterprise Resource Planning system.

PIP

Process Integration Pack

Provider Processes

All the integration processes, which are invoked by the reading message from the queue are referred to as Provider Processes. These processes transform the request message from the queue to the edge application format and execute the inbound service on the edge application with a message. These processes have ProvABCSImpl as a part of the name. For example, SyncWorkerOUWAMUtilit iesProvABCSImpl.

Requestor Processes

All the integration processes, which are invoked by the edge application initiating the request are referred to as Requestor Processes. These processes put the request message with or without transformation in the queue. These processes have ReqABCSImpl as a part of the name. For example, SyncWorkerERPReqABCSImpl.

SOA

Service-Oriented Architecture - Software modules that are provided as services can be integrated or used by several applications using SOA, even if their respective architectures are substantially different. Rather than defining an API, SOA defines the interface in terms of protocols and functionality.

SOAP

Simple Object Access Protocol. It is a protocol specification for exchanging structured information in the implementation of Web Services in computer networks.

WAM or OUWAM

Oracle Utilities Work and Asset Management

WSC

Oracle Utilities Work and Asset Management Supply Chain business model

XAI

XML Application Integration. An Oracle Utilities Framework utility used to configure the system transfer information between Oracle Utilities Work and Asset Management and external applications using XML. XAI exposes system business objects as a set of XML based web services. The service can be invoked using different methods, for example, Hypertext Transfer Protocol (HTTP) or Java Message Service (JMS). Consequently, any application or tool that can send and receive XML documents can access the rich set of system business objects.

XSD

A schema definition file.

XSL

Extensible Style Language