DWMS+ODI+whitepaper

8/16/2019 DWMS+ODI+whitepaper

1/28


2/28

EBS 11i10 to Distributed WMS integration

Page 2 of 28

TABLE OF CONTENTS

1

Integration Overview ................................................................................................. 3

1.1 SCOPE ............................................................................................................................. 3

1.2

I NTEGRATION TECHNOLOGY USED (ODI) ....................................................................... 4

2

Setting up the Integration .......................................................................................... 4

2.1 PRE REQUISITES .............................................................................................................. 4

2.2

I NSTALLATION AND CONFIGURATION ............................................................................. 4

3 Post Patch Guidelines for executing the ODI maps ............................................... 10 3.1

R EFERENCE DATA MAPS................................................................................................ 10

3.2

PROCESS DATA MAPS .................................................................................................... 13

4

Troubleshooting Tips ............................................................................................... 21

4.1 R EFERENCE DATA MAPS................................................................................................ 22

4.2

PROCESS DATA MAPS .................................................................................................... 22

5 Customizing an ODI Map ......................................................................................... 25 6

Frequently Asked Questions .................................................................................... 26


3/28


Page 3 of 28

1 . Integration Overview

Oracle provides out-of-the-box Integration between EBS 11i10 and the Distributed WMSinstance to ensure a streamlined uptake of the Distributed WMS functionality. The integration isdesigned and developed using the Oracle Data Integrator (ODI) technology

1.1 Scope

Oracle provides out-of-box integration for synchronizing the key reference and process dataelements between the host EBS 11i10 and the Distributed WMS instance. ODI maps have beendeveloped by Oracle to enable the synchronization of the data elements needed for asuccessful deployment of a Distributed WMS solution

The following key reference Data elements can be synchronized from the Host EBS 11i10instance to the Distributed WMS instance

Reference Data Operations supported viaODI maps

Direction of Synchronization

Items Create/Update EBS 11i10 to Distributed WMS

Customers Create/Update EBS 11i10 to Distributed WMS

Suppliers Create EBS 11i10 to Distributed WMS

The following key Process Data elements are part of the Integration and are listed in therecommended order of execution once deployed on a customer instance

Process Data Operations supportedvia ODI maps

Direction of Synchronization

Purchase Orders Create/Update/Cancel EBS 11i10 to Distributed WMS

RMA Create/Cancel EBS 11i10 to Distributed WMS

ASN Create/Cancel EBS 11i10 to Distributed WMS

Receipt Confirmation Support for PO Receipt,RMAs, Corrections

Distributed WMS to EBS 11i10

Shipment Request Create EBS 11i10 to Distributed WMS

InventoryAdjustments

Adjustment Transactions(e.g. cycle counts,

physical Count),Stagingtransfers, Interogtransfer, Miscellaneoustransactions

Distributed WMS to EBS 11i10

ShipmentConfirmation

Create Distributed WMS to EBS 11i10

Additional details and implementation considerations about each of the maps are detailed out inthe Section 3.1 and 3.2


4/28


Page 4 of 28

1.2 Integration Technology used (ODI)

Oracle Data Integrator employs a powerful declarative design approach to ETL, whichseparates the declarative rules from the implementation details. Oracle Data Integrator is alsobased on a unique “E-LT” architecture which eliminates the need for a standalone ETL serverand proprietary engine, and instead leverages the inherent power of your RDBMS engines. This

combination provides the greatest productivity for both development and maintenance, and thehighest performance for the execution of data transformation and validation processes. Foradditional details, please refer to ODI documentation on Oracle Metalink.

2 . Setting up the Integration

Integration between EBS 11i10 to Distributed WMS instances is designed and developedusing the Oracle Data Integrator (ODI) technology.

2.1 Pre requisites

Oracle Data Integrator (ODI) v10.1.3.5.0o Please refer to the ODI installation guide to understand the system requirements

to deploy ODI Apache Ant Distributed WMS instance

o EBS release12.1.2 or higher (Customers on EBS release 12.1.1 need to applypatch 8454295:R12:WMS:B)

EBS 11i10 instance

2.2 Installation and Configuration

2.2.1 Summary of steps

1. Install ODI on the networka. Download and Install ODI v10.1.3.5.0 or higherb. Please refer to Oracle Technology Network (OTN) site for ODI related

documentation2. Install ODI Master and Work repository

a. Identify a database instance for installing these repositories It can be the Distributed WMS Instance, 11i10 EBS instance or any other

Oracle 11g database instance on the network with read/write access.b. Using the ODI client, install the Master and Work repository on the database

identified in 2(a)

3. Install ANT4. Apply Distributed WMS Integrations Patch 9310256:R12.WMS.B . Please follow the

instructions mentioned in the readme.a. Extract the XML files shipped as part of the patchb. Import all the XMLs in the Master and Work repository created as per 2(b).

5. Schedule the Deployed ODI mapsa. Run the ODI agent setb. Refer to Section 4 for Implementation considerations for each map c. Schedule the ODI maps using shell/bat scripts as per business requirements


5/28


Page 5 of 28

2.2.2 Details for each of the summary steps listed in Section 2.2.1

1. Install ODI on the network

Download ODI version 10.1.3.5.0 for the applicable platform from the OTN website

(http://www.oracle.com/technology/software/products/odi/index.html) Please follow the instructions in the Installation guide to install the ODI client on the network.

Once installed, please set following two environment variables:ODI_HOME (must point to the oracledi folder under installed ODI directory)JAVA_HOME (preferably should point to a jdk1.4 or higher)

2. Install ODI Master and Work Repository

Please refer to the ODI installation guide to create the Master and Work Reposirity. Oraclerecommends using a repository id greater than 500

3. Install ANT

Download ant from http://ant.apache.org/bindownload.cgi (Recommended version:apache-ant-1.7.1-bin.zip)

Create an ant directory in the path of your choice (for example, /usr/local/ant). Copy apache-ant-1.7.1-bin.zip to your ant directory. Extract the file apache-ant-1.7.1-bin.zip using the unzip command. This command

extracts the content of the zip file and creates a new directory, apache-ant-1.7.1. Download ant-contrib from

http://sourceforge.net/project/showfiles.php?group_id=36177&package_id=28636(Version ant-contrib-0.3).

Unzip the downloaded file. This file creates an ant-contrib-0.3 folder and a libsubfolder.

Copy the file /ant-contrib-0.3/lib/ant-contrib-0.3.jar to the ant/apache-ant-1.7.1/libdirectory. This jar file must exist in the lib directory.

4. Apply Distributed WMS Integrations Patch

Download the patch 9310256:R12.WMS.B. Unzip the ODI XML artifacts shipped with thepatch to the machine on which ODI client was installed in the previous section.

Syntax in the following steps is based on Linux environment. If you choose to install the ODIclient in Windows, necessary changes will be required according to the Windowsenvironment‟s syntax.

The unzip will create the following 4 directories …/wms/patch/115/odi/US/master …/wms/patch/115/odi/US/model …/wms/patch/115/odi/US/project …/wms/patch/115/odi/US/util

The first step is to set up ODI parameters in the file odiparams.sh

($ODI_HOME/bin/odiparams.sh) file to point to the ODI work repository.

http://www.oracle.com/technology/software/products/odi/index.htmlhttp://www.oracle.com/technology/software/products/odi/index.htmlhttp://www.oracle.com/technology/software/products/odi/index.htmlhttp://www.oracle.com/technology/software/products/odi/index.html


6/28


Page 6 of 28

Sample odi parameters look like:

ODI_SECU_DRIVER=oracle.jdbc.driver.OracleDriverODI_SECU_URL=jdbc:oracle:thin:@rws60037rems.us.oracle.com:1612:mv0yd100ODI_SECU_USER=appsODI_SECU_ENCODED_PASS=eWyXyOppxoW3dQHkcl8ed

ODI_SECU_WORK_REP=WRODI_USER=SUPERVISORODI_ENCODED_PASS=LELKIELGLJMDLKMGHEHJDBGBGFDGGH

These parameters depend on the connection settings of the work repository schema. Pleasenote that the passwords are encoded. To retrieve the encoded string, execute the following in$ODI_HOME/bin/agent.sh encode (For windows, use the .bat file)

ODI is installed in the directory that was chosen during the ODI Installation procedure (forexample, /usr/local/OraHome_1/). Set the directories oracledi and jre/1.4.2 created withinODI_HOME to the following:

export ODI_HOME=/home/usr/OraHome_1/oracledi export ODI_JAVA_HOME= /local/java/jdk1.6.0_16

ANT is installed in a particular directory (for example, usr/local/ant). Set the followingenvironment variables:

export ANT_HOME=/usr/local/ant/apache-ant-1.7.1 export JAVA_HOME /local/java/jdk1.6.0_16

Set up an environment variable DIST_WMS_PATCH_HOME and point it to the location:…/wms. For instance, if the patch was unzipped at the location

/slot/ems194/appmgr/ml0yu100ora/8.0.6/ODI/WMS_Integration_Solution_Patch, set followingvariable as:

export DIST_WMS_PATCH_HOME=/slot/ems194/appmgr/ml0yu100ora/8.0.6/ODI/WMS_Integration_Solution_Patch/9119044/wms

Execute the following scripts to import master, model and project artifacts. Please maintain theorder listed below-

Run the script $ANT_HOME/bin/ant –f $DIST_WMS_PATCH_HOME /patch/115/odi/US/util/UTIL_WMS_IMPORTMASTER.xml for master ODI artifacts.

To confirm, connect to Master repository using the ODI client and navigate to Physical Architecture -> Technologies -> Oracle. You should see the following:


7/28


Page 7 of 28

Please double click on each Data Server under „Oracle‟ and configure the connection settingsas follows -

Data servers pointing to the Host EBS11i10 database WMS_ORACLE_ERP WMS_ORACLE_ERP_INV WMS_ORACLE_ERP_PO WMS_ORACLE_ERP_WSH

Data server pointing to the Distributed WMS database WMS_ORACLE_SAL

Data server pointing to the Work Repository database WMS_ORACLE_WR

Execute the script $ANT_HOME/bin/ant –f $DIST_WMS_PATCH_HOME /patch/115/odi/US/util/UTIL_WMS_IMPORTMODEL.xml for importing model ODI artifacts in the repository.

Execute the script $ANT_HOME/bin/ant –f $DIST_WMS_PATCH_HOME /patch/115/odi/US/util/UTIL_WMS_IMPORTPROJECT.xml for importing project ODI artifacts in the repository.

The above steps will import the ODI artifacts into the master as well as work repositories.

5. Schedule the Deployed ODI maps

This section will elaborate on setting up an ODI agent and how one can use it to run theIntegration ODI maps. A light weight server is required to run ODI maps. Please refer to the ODIinstallation and ODI user guide for more details.


8/28


Page 8 of 28

Check the agent in the topology manager. Connect to the master repository using the topologymanager and in the Logical Architecture, drill down on the Agents and check the importedLogical Agent –

Now, start the ODI agent. For this, navigate to $ODI_HOME/bin on command prompt andexecute:

./agentscheduler.sh "-port=20910" "-name=WMSODIAgent" (For windows, use the .bat file)

WMSODIAgent is the name of the Physical Agent; it can be seen in the Physical Architectureof Topology manager.


9/28


10/28


Page 10 of 28

3 . Post Patch Guidelines for executing the ODI maps

This section will describe the input parameters and the applicable implementation considerationsfor the all the maps developed for synchronization of reference and process data between the

host EBS 11i10 and the Distributed WMS instance

3.1 Reference data maps

Map Input Parameters for executingthe map

Implementation considerations

Customer WMS_N_RESP_ID andWMS_N_USER_ID: These variables arethe respective ids for the responsibilityand user having access to execute theConcurrent program „Customer Interface‟on the Distributed WMS instance. Thesevariables are mandatory for thesynchronization to the completedsuccessfully.

WMS_V_CUSTOMER_NAME: Variablecan be used to synchronize a specificcustomer. This can be NULL if you want tosynchronize all customers

WMS_V_HOST_ORGANIZATION_CODE:Variable should be set to the HostEBS11i10 instance‟s operating unit code.

WMS_V_STANDALONE_ORG_CODE:Variable should be set to the DistributedWMS instance‟s operating unit code

WMS_V_INSERT_UPDATE_FLAG: Thisflag will decide whether the map run is forsyncing new customers or updatingalready synchronized customers. Possiblevalues are (a) „I‟ - for synchronizing newcustomers (b) „U‟- for updating

synchronized customers

WMS_V_FROM_CREATION_DATE:Variable to pass the lower bound of thedate range to pick source data from theHost EBS 11i10 instance.

WMS_V_TO_CREATION_DATE: Variableto pass the upper bound of the date rangeto pick source data from the Host EBS11i10 instance.

Objective - This map supports thecreation and subsequent update ofthe Customer data on theDistributed WMS instance.

In order to retain the samecustomer number and site numberon the Distributed WMS instance asthe ones existing on the Host EBS11i10 instance, please disable „Theautomatic customer and sitenumbering‟ in the Receivablessetup. Addition of a new customersite or contact to an alreadysynchronized customer is notsupported.

Please ensure that the RESP_IDpassed to this map is assigned tothe application „Receivables‟ andhas access to launch the concurrentprogram „Customer Interface‟

WMS_V_FROM_UPDATE_DATEand WMS_V_TO_UPDATE_DATEvariables should not be given anyvalue whileWMS_V_INSERT_UPDATE_FLAG

should be set as „I‟ whilesynchronizing new customers.

WMS_V_FROM_CREATION_DATEandWMS_V_TO_CREATION_DATEvariables should not be given anyvalue whileWMS_V_INSERT_UPDATE_FLAGshould be set as „U‟ while updatingsynchronized customers.


11/28


Page 11 of 28

WMS_V_FROM_UPDATE_DATE:Variable to pass the lower bound of thedate range to pick source data from theHost EBS 11i10 instance.

WMS_V_TO_UPDATE_DATE. Variable topass the upper bound of the date range topick source data from the Host EBS 11i10instance.

Item WMS_N_RESP_ID andWMS_N_USER_ID: These variables arethe respective ids for the responsibilityand user having access to execute theConcurrent program „Import Items‟ on theDistributed WMS instance. Thesevariables are mandatory for the

synchronization to the completedsuccessfully.

WMS_N_BATCH_SIZE: Variable to setthe concurrent program‟s processingbatch size. The default value is 1000.

WMS_V_ITEM_ACCOUNT: Variable topass a valid charge account in thedistributed instance. This is required toimport the item into the Distributedinstance

WMS_V_HOST_ORGANIZATION_CODE:Variable should be set to the HostEBS11i10 instance‟s or ganization code.

WMS_V_STANDALONE_ORG_CODE:Variable should be set to the DistributedWMS instance‟s organization code


WMS_V_TO_UPDATE_DATE: Variable topass the upper bound of the date range topick source data from the Host EBS 11i10instance.

Objective - This map supports thecreation and subsequent update ofthe Item data on the DistributedWMS instance.

Items should be synchronized forthe master organization on theDistributed WMS organization

before any child organizationsynchronization

The following reference elementsmust be synchronized manuallyprior to item synchronization - UOM,UOM classes, Material Statusesand User item types.

Please ensure that the RESP_IDpassed to this map should beassigned to the application„Inventory‟ and should have accessto launch the concurrent program„Import Items‟

Supplier WMS_N_RESP_ID andWMS_N_USER_ID: These variables arethe respective ids for the responsibilityand user having access to execute the„Supplier Open Interface Request Set (1)‟on the Distributed WMS instance. These

variables are mandatory for the

Objective - This map supports thecreation of Suppliers on theDistributed WMS instance.

Ship to location code should besynchronized manually beforeexecuting this map.


12/28


Page 12 of 28

synchronization to the completedsuccessfully.

WMS_V_STANDALONE_ORG_CODE:Variable should be set to the DistributedWMS instance‟s operating unit code.

WMS_V_SHIP_TO_LOCATION_CODE:Variable should contain the ship tolocation code. This is used to filter thedata from the Host EBS 11i10 instance

WMS_V_VENDOR_NAME: Variable canbe used to synchronize a specific supplier.

WMS_V_FROM_CREATION_DATE:Variable to pass the lower bound of thedate range to pick source data from the

Host EBS 11i10 instance. Pass „NULL‟ fornot considering the lower bound.

WMS_V_TO_CREATION_DATE: Variableto pass the upper bound of the date rangeto pick source data from the Host EBS11i10 instance. Pass „NULL‟ for notconsidering the upper bound.

Make sure that the RESP_IDpassed to this map should beassigned to the application„Payables‟ and should have accessto launch the concurrent program.

Once a Supplier has beensynchronized on the DistributedWMS instance, any changes on theHost instance need to be mademanually on the Distributed WMSinstance

Generic Guidelines:

Maps can be scheduled to run as shell scripts (sh) or batch files (bat)o A sample script has been provided in section 2.2.2. Using the input parameters

listed above and providing the relevant values, customers needs to create theirbusiness and platform specific shell/batch scripts

All the date fields should be passed in the format „mm/dd/yyyy hh24:mi:ss‟. If no value isprovided to any date, then NULL value will be assumed for the same

For all the above reference data elements, only fields relevant to support DistributedWMS transactions will be synchronized between the Distributed WMS instance and theEBS 11i10 instance

For the initial synchronization, the shell/bat scripts can be executed with NULL 'FromDate', „To Date' as SYSDATE. For subsequent runs, please modify the bat/sh file as per

business requirements. For the maps that support creation and updation modes (e.g, Customer) please ensure

that creation happens before updating any data. This can be achieved by scheduling theInsert mode before the Update mode map.


13/28


Page 13 of 28

3.2 Process data maps

Map Input Parameters for executingthe map

Implementation considerations

AdvanceShipmentNotification(ASNcreation)

WMS_N_RESP_ID andWMS_N_USER_ID:

These variables are the respective ids forthe responsibility and user having accessto execute the Concurrent program„Receiving Transaction Processor‟ on theDistributed WMS instance. Thesevariables are mandatory for thesynchronization to the completed

successfully

WMS_V_STANDALONE_ORG_CODE:Variable should be set to the DistributedWMS instance‟s organization code. Thisis used to filter the data from the HostEBS 11i10 instance

WMS_V_STANDALONE_OP_CODE:Variable should be set to the DistributedWMS instance‟s operating unit


WMS_V_TO_CREATION_DATE:Variable to pass the upper bound of thedate range to pick source data from theHost EBS 11i10 instance.

Objective - This map supports thecreation of ASN on the DistributedWMS instance

The design is based on the businessprocess that ASNs are created in thehost instance (e.g. through iSupplierPortal or by populating ROI tables)and synchronized to the Distributed

instance by executing this map.

Please ensure that the RESP_IDpassed to this map should beassigned to the application„Purchasing‟ and should have accessto launch the concurrent program„Receiving Transaction Processor‟

AdvanceShipmentNotification(ASNcancellation)

WMS_N_RESP_ID, WMS_N_USER_ID:

These variables are the respective ids forthe responsibility and user having accessto execute the Concurrent program„Receiving Transaction Processor‟ on theDistributed WMS instance. Thesevariables are mandatory for thesynchronization to the completedsuccessfully.

WMS_V_FROM_UPDATE_DATE:

Variable to pass the lower bound of the

Objective - This map supports thecancellation of ASN on theDistributed WMS instance

The design is based on the businessprocess that ASNs are cancelled inthe host instance and synchronizedto the Distributed instance byexecuting this map

Please ensure that the RESP_ID

passed to this map should be


14/28


Page 14 of 28

date range to pick source data from theHost EBS 11i10 instance.

WMS_V_TO_UPDATE_DATE: Variableto pass the upper bound of the daterange to pick source data from the HostEBS 11i10 instance.

WMS_V_STANDALONE_ORG_CODE:This variable should contain theDistributed WMS instance‟s operating unitcode.

assigned to the application„Purchasing‟ and should have accessto launch the concurrent program„Receiving Transaction Processor‟

PurchaseOrder

WMS_V_AGENT_NAME: Variable mustcontain the Agent‟s name having theaccess to execute „Import StandardPurchase Orders‟ on the the DistributedWMS instance

WMS_V_STANDALONE_OP_CODE:Variable should be set to the DistributedWMS instance‟s operating unit code.

WMS_N_PO_USER_ID,WMS_N_PO_RESP_ID: These variablesare the respective ids for theresponsibility and user having access toexecute the Concurrent program „ImportStandard Purchase Orders‟ on theDistributed WMS instance. These

variables are mandatory for thesynchronization to the completedsuccessfully.

WMS_V_GL_SET_OF_BOOKS: Thisvariable must be passed and shouldcontain a valid set of books id on thedistributed instance.

WMS_V_PO_CHARGE_ACCOUNT: Thisvariable must be passed and shouldcontain a valid charge account on the

distributed instance.

WMS_V_SHIP_TO_LOCATION_CODE:This variable should contain the ship_tolocation code. This is used to filter thedata from the Host EBS 11i10 instance

WMS_V_SHIP_TO_ORG_NAME: Thisvariable should contain the ship_toorganization name. This is used to filterthe data from the Host EBS 11i10instance

Objective - POs created on the EBS11i10 instance are synchronized withthe Distributed instance by executingthis map.

Creation of a new PO and addition ofa line to an existing PO is supportedvia the PO map Cancellation issupported only at shipment andheader level. Line level cancellationneed to be synchronized manuallyUpdate is supported only at line levelfor the following four elements:Price, Quantity, Need by date andPromised Date.

Attribute15 of the table –

PO_HEADERS_ARCHIVE_ALL onthe EBS11i10 host instance will bemarked as „Y‟ for the successfullysynchronized POs, „E‟ for errored outPOs and „P‟ for the „processing inprogress‟ POs.

Please ensure that the RESP_IDpassed to this map should beassigned to the application„Purchasing‟ and should have accessto launch the concurrent program.


15/28


Page 15 of 28


WMS_V_TO_UPDATE_DATE: Variableto pass the upper bound of the daterange to pick source data from the HostEBS 11i10 instance

ReceiptConfirmation



WMS_V_STANDALONE_ORG_CODE:Variable should be set to the DistributedWMS instance‟s organization code.

Objective – Executing this map willplayback PO receipts, ASN receiptsand RMA receipts on the EBS 11i10instance . The design is based on thebusiness process that all the abovereceipts are physically done on the

Distributed instance and are playedback on the EBS instance

The profile option 'RCV: AllowRouting Override' should be set to„Yes‟ on the host instance.

The receipt_confirmation_extractedflag of RCV_TRANSACTIONS will bemarked as „Y‟ for pr ocessed records,„E‟ for errored out records and „P‟ for„in progress‟ records.

Please ensure that the RESP_IDpassed to this map should beassigned to the application„Purchasing‟ and should have accessto launch the concurrent program.

ShipmentRequest(Creation)

WMS_N_RESP_ID, WMS_N_USER_ID:These variables should contain therespective ids for responsibility and userneeded for access to execute „Process

Shipment Requests‟ Concurrent Progamin Distributed WMS Instance.

WMS_V_PENDING_FLAG:Variable to pick Pending (Unprocessed)or Errored SR Transactions from HostEBS 11i10 Instance. Possible values areNULL (Pending), Y (Pending), E (Errored)Default value is Y

WMS_V_HOST_ORGANIZATION_CODEVariable to pick Shipment Requestscorresponding to Organization passed. Ifvalue passed is NULL then it will pick

Objective – Shipment Requestscreated on the EBS 11i10 instanceare synchronized as Sales orders inthe Distributed instance by executingthis map.

Host EBS 11i10 Instance:Pending Request flag inWSH_SHIPMENT_BATCHES tableswill be updated as „NULL‟,Transaction Status inWSH_TRANSACTIONS_HISTORYtable will be updated as „ST‟ forsuccessfully processed records.

For errored out records, TransactionStatus inWSH_TRANSACTIONS_HISTORY


16/28


17/28


Page 17 of 28

WMS_V_PENDING_FLAG: Variable to pick Pending (Unprocessed)or Errored SA Transactions fromDistributed WMS Instance.Possible values are NULL (Pending), Y

(Pending), E (Errored)Default value is Y

WMS_V_ENABLE_CP_DEBUG: Variable to enable debugging for „ProcessShipment Advices‟ concurrent programtriggered in EBS 11i10 Instance.If value is „Y‟ then debugging will be enabled, for any value other than „Y‟debugging is disabled.Default value is „N‟.

WMS_V_FROM_CREATION_DATE:Variable to pass the lower bound of thedate range to pick source data from theDistributed WMS instance.

WMS_V_TO_CREATION_DATE:Variable to pass the upper bound of thedate range to pick source data from theDistributed WMS instance.

WSH_TRANSACTIONS_HISTORYtable is update to „ER‟.

InventoryTransactions

WMS_N_RESP_ID andWMS_N_USER_ID:These variables should contain therespective ids for responsibility and userneeded for access to execute the„Inventory transaction worker‟ ConcurrentProgram in Host EBS 11i10 Instance.These variables must not be NULL.

WMS_V_TRX_EXTRACTED_FLAG:Variable to pick UnExtracted or ErroredInventory Transactions, which needs tobe Synced from Distributed WMSInstance.Possible values are NULL (Unextracted),E (Errored)Default value is NULL

WMS_V_STANDALONE_ORG_CODE: Variable to pass the Warehouse Code, topick source data corresponding to thatWarehouse from Distributed WMSInstance. Variable value should NOT beNULL.

WMS_V_TRX_CATEGORY:Variable to pass the Transaction

Category to pick source data from

Objective – The inventorytransactions will executed in theDistributed instance as part of the

warehousing flows and played backto the EBS 11i10 instance byexecuting this map.

Transaction_Extracted column inMTL_MATERIALS_TRANSACTIONStable on the Distributed Instance willbe updated to „Y‟ for records playedback on the EBS 11i10 instance.

Picking transactions are played backas Subinventory transfers on the

Host instance. Any adjustmenttransactions or Move Order issuesare played back as Account Aliastransactions. This is done tominimize redundant warehousingrelated setup on the EBS hostinstance


18/28


Page 18 of 28

Distributed WMS Instance.Default value for this is NULL. If the userwants to process the transactions forparticular category then he can pass theappropriate value to the variable.

WMS_N_DIST_ACCOUNT_ID:Variable to pass the Distribution AccountId of Host EBS 11i10 instance.Variable value should NOT be NULL.

WMS_V_FROM_TRX_DATE:Variable to pass the lower bound of thedate range to pick source data from theDistributed WMS instance.Variable value should NOT be NULL

WMS_V_TO_TRX_DATE:

Variable to pass the upper bound of thedate range to pick source data from theDistributed WMS instance.Variable value should NOT be NULL

RMA WMS_V_STANDALONE_OP_CODE:Variable should be set to the DistributedWMS instance‟s operating unit code.

WMS_V_STANDALONE_ORG_CODE:Variable should be set to the Distributed

WMS instance‟s organization code

WMS_N_USER_ID, WMS_N_RESP_ID:These variables are the respective ids forthe responsibility and user having accessto execute the Concurrent program „OrderImport‟ on the Distributed WMS instance.These variables are mandatory for thesynchronization to the completedsuccessfully.

WMS_V_RMA_MODE:

Values can either be „I‟ or „CH‟ for insertand cancellation at header levelrespectively.

WMS_V_CHANGE_REASON:This needs to be the reason code on whythe RMA is getting cancelled

WMS_V_FROM_CREATION_DATE:Variable to pass the lower bound of thedate range to pick source data from thehost EBS 11i10 instance.

Objective - RMAs will be created inthe EBS 11i10 instance andsynchronized to the Distributedinstance by executing this map.

Following entities needs to be

manually synchronized prior tosynchronizing the RMAs:Order type, ship to location, bill tolocation, payment terms, returnreason and line type.

In EBS 11i10 Instance Attribute15 of oe_order_headers_alland oe_order_lines_all will beupdated to „I‟ and „CH‟ forinsertion/cancellation of the RMArespectively after inserting the

interface records in distributed WMSinstance.


19/28


Page 19 of 28



WMS_V_TO_UPDATE_DATE: Variableto pass the upper bound of the daterange to pick source data from the HostEBS 11i10 instance.

Material movement between Warehouses

Inter-organization Transferso These are primarily inventory transactions where material is moved from one

organization to another without any documentation. This is also used in casewhere material is manufactured in one organization and transferred to another – typical of a scenario where manufacturing and distribution centers are in closeproximity and each being modeled as a separate organization in the sameinstance

o Inventory Transactions map will synchronize the Inter-organization transfer ofmaterial between 2 organizations defined on the same Distributed instance aswell as on the EBS 11i10 instance. Support is provided for both Directorganization transfer as well as Intransit Shipment process.

Inter-organization Transfers via Internal Orderso This are transactions where material is moved from one organization to another

based via Internal orders based on Internal requisitions between two organizationo Please refer to the Architecture and Solution Overview Whitepaper on metalink

Note - 821294.1 (section 3.3) which explains the different approaches to addressInternal Order flow integration. The Shipment request and Shipment confirmation,maps provided can be leveraged when adopting a solution as per your businessrequirement.

Generic Guidelines: Maps can be scheduled to run as shell scripts (sh) or batch files (bat)

o A sample script has been provided in section 2.2.2. Using the input parameterslisted above and providing the relevant values, customers needs to create theirbusiness and platform specific shell/batch scripts

All the date fields should be passed in the format „mm/dd/yyyy hh24:mi:ss‟ For the initial synchronization, the shell/bat scripts can be executed with NULL 'From

Date', „To Date' as SYSDATE. For subsequent runs, please modify the bat/sh file as perbusiness requirements

All reference data must be synchronized between the EBS 11i10 and the DistributedWMS instance before process data maps

For all the above process data elements, only fields relevant to support Distributed WMStransactions will be synchronized between the Distributed WMS instance and the Host

Instance


20/28


Page 20 of 28


21/28


Page 21 of 28

4 . Troubleshooting Tips

This section provides tips on common error handling situations involved with the execution ofthe ODI maps

A. Symptom- Data is picked update from source but is not inserted into the Target instanceInterface table or the Target instance master data table. Source data is effectively „skipped‟ byODI. This problem can manifest in many ways (e.g., a new item created on the EBS 11i10instance is not synchronized due to this problem. A subsequent synchronization of a Purchaseorder on the same item will fail and raise a red flag when the PO is executed)

Potential Root Cause – This will happen only in a case where the ODI map violates adatabase constraint (insert NULL into a NOT NULL column, insert string into NUMBER columnetc)

Course of action - Operator log will clearly show that a particular ODI scenario errored out.

The ODI operator log will show a red dot against the step which failed during executionDebugging can be done by reviewing each step of the scenario by using ODI provideddiagnostics. If the maps have not been customized, please log a tar against Oracle (ProductWMS) with the details from the Operator log along with the details about the map involved

B. Symptom -Data is inserted into applicable Open Interface and errors out during processing

Potential Root Cause - Setup mismatch between Host and Distributed instance data – (e.g.,trying to import a Item without synchronization of the UOMs ).

Course of action 1. Please refer to the Metalink Note 821294.1 for Setup White Paper the setup

required. Ensure that all recommended setup is done on the Host and DistributedInstance before executing the maps

2. Please ensure that maps are scheduled as per the order recommended byOracle. Please also refer to the map specific troubleshooting tips provided insection 4.1 and 4.2 in this document

3. If all setup looks fine, please log a service request against Oracle (Product WMS)


22/28


Page 22 of 28

4.1 Reference data maps

The following section provides relevant details about the Open Interface tables leveraged aspart of the integration and should help in understanding why the reference datasynchronization failed during the processing from the interface tables

Map Name Troubleshooting Tips

Customer The records might be stuck in RA_CUSTOMERS_INTERFACE_ALLand/or RA_CONTACT_PHONES_INT_ALL interface tables on theDistributed instance, which will need a manual update for re-processing

Item The records might be stuck in MTL_SYSTEM_ITEMS_INTERFACEinterface table on the Distributed Instance which will need manualupdate for re-processing or the ODI operator log will point to the errorstep

Supplier The records might be stuck in AP_SUPPLIERS_INT, AP_SUPPLIERS_SITES_INT and/or

AP_SUP_SITE_CONTACT_INT interface tables on the Distributedinstance or the ODI operator log will point to the error step

4.2 Process data maps

The following section provides relevant details about the Open Interface tables leveraged aspart of the integration and should help in understanding why the process datasynchronization failed during the processing from the interface tables

Map Name Troubleshooting Tips AdvanceShipmentNotification(ASNcreation)

The records will be inserted in the RHI (RCV_HEADERS_INTERFACE)and RTI (RCV_TRANSACTIONS_INTERFACE) interface tables of thedistributed instance. If one does not see the expected ASNs being createdon the distributed instance, the records might be stuck in these interfacetables due to some validation failure. It will need a manual update of therecords in RHI, RTI to fix the errors.

AdvanceShipmentNotification(ASNcancellation)

The records will be inserted in the RTI(RCV_TRANSACTIONS_INTERFACE) interface table of the distributedinstance. If one does not see the expected ASNs being created on thedistributed instance, the records might be stuck in this interface tables dueto some validation failure. It will need a manual update of the records in

RTI to fix the errors.PurchaseOrder

ATTRIBUTE15 of the table PO_HEADERS_ARCHIVE_ALL on the hostinstance is used to mark the processed rows. In case of failure,appropriate rows will be marked as „E‟ to indicate that the record wasprocessed with error. „E‟ denotes that ODI session did not finish asexpected. If the ATTRIBUTE15 is mar ked as „I‟ and POs are not created inthe distributed instance, then the records must be stuck in the interfacetables During execution, PO_HEADERS_INTERFACE,PO_LINES_INTERFACE and PO_DISTRIBUTIONS_INTERFACE will bepopulated and the column PROCESS_CODE will be marked as either„REJECTED‟ or „ACCEPTED‟. In case of „REJECTED‟ status, one needsto manually update the records in these tables and resubmit the „Import

Standard PO‟ concurrent program


23/28


Page 23 of 28

ReceiptConfirmation

The column RECEIPT_CONFIRMATION_EXTRACTED of the tableRCV_TRANSACTION on the distributed instance is used to mark theprocessed rows. Value „E‟ for this column indicates that the record wasprocessed with errors. If the columnRECEIPT_CONFIRMATION_EXTRACTED is marked as „Y‟ and receivingtransactions are not created in the host instance, then the records must bestuck in the interface tables. During the execution of the map, records willbe inserted in the RHI (RCV_HEADERS_INTERFACE), RTI(RCV_TRANSACTIONS_INTERFACE), MTLI(MTL_TRANSACTION_LOTS_INTERFACE) and MSNI(MTL_SERIAL_NUMBERS_INTERFACE) interface tables of the hostinstance. It will need a manual update of the records in RHI, RTI, MTLI orMSNI to fix the errors.

ShipmentRequest(Creation)

Column WSH_SHIPMENT_BATCHES.Pending_Request_Flag andWSH_TRANSACTIONS_HISTORY.Transaction_Status can used toidentify whether Shipment Request data was Synchronized from Host toDistributed WMS Instance. Successfully Synchronized:

Pending_Request_Flag will be NULL, Transaction_Status will be „ST‟(Sent). Errored Out: Pending_Request_Flag will be „Y‟, Transaction_Statuswill be „ER‟ (Error). In order to Synchronize the Shipment Request data,lines should belong to Organization which is „Distributed Enabled‟ andprofile „WSH: Distributed Source Entity‟ should be set to „Fulfillment Batch‟at SITE level.If Shipment Request is synchronized to Distributed WMS instance howeverSales Order is NOT created in Distributed WMS Instance for the Documentthen check the status of Transaction History for the Document from„Interface Message Corrections‟ form Navigation: Shipping -> Interfaces -> Interface Message CorrectionsIf status is „Awaiting Processing‟ then submit „Process Shipment Requests‟

concurrent program or process it manually from „Interface MessageCor rections‟ form. Possible reasons for records stuck in Interface tablesare -) Apps credential passed is invalid, due to which „Process ShipmentRequests‟ Concurrent request was not triggered from ODI Map. 2) Setup issue in Distributed WMS Instance. If status „Error‟ then check forerror message and correct the interface data and then submit „ProcessShipment Requests‟ concurrent program or process it manually from„Interface Message Corrections‟ form. 'Shipment Message Corrections'form can be used to view Shipment Request data in Dist. WMS Instance.Navigation: Shipping => Interfaces => Interface Message Corrections.If the SR interface data is processed successfully by Process ShipmentRequests concurrent process then the data cannot be queried/viewed from

SMC form.Shipment Advice(Creation)

Column WSH_TRANSACTIONS_HISTORY.Transaction_Status can usedto identify whether Shipment Advice data was Synchronized fromDistributed WMS to Host Instance.Successfully Synchronized: Transaction_Status will be „ST‟ (Sent)Errored Out: Transaction_Status will be „ER‟ (Error).In order toSynchronize the Shipment Advices data, action „Send Outbound Message‟should have been performed for Shipped deliveries from ShippingTransaction Form or „Automated Shipment Request/Shipment Advice‟concurrent program should have been submitted for Shipped deliveries.If Shipment Advice is synchronized to Host instance however DeliveryLines still remain in „Ready to Release‟ then check the status ofTransaction History for the Document from „Interface Message Corrections‟


24/28


Page 24 of 28

form. Navigation: Shipping -> Interfaces -> Interface Message CorrectionsIf status is „Awaiting Processing‟ then submit „Process Shipment Advices‟concurrent program or process it manually from „Interface MessageCorr ections‟ form. Possible reason for records stuck in Interface tables is- Apps credential passed is invalid, due to which „Process Shipment Advices‟ Concurrent request was not triggered from ODI Map. If status „Error‟ then check for error message and correct the interface dataand then submit „Process Shipment Advices‟ concurrent program orprocess it manually from „Interface Message Corrections‟ form. 'Shipment Message Corrections' form can be used to view Shipment Advice data in Host Instance. Navigation: Shipping => Interfaces =>Interface Message Corrections. If the SA interface data is processedsuccessfully by Process Shipment Requests concurrent process then thedata cannot be queried/viewed from SMC form.

InventoryTransactions

Data will be inserted into the following tables on the Host Instance – MTL_TRANSACTIONS_INTERFACE (for all items)MLT_LOT_NUMBERS_INTERFACE (for lot controlled items),

MTL_SERIAL_NUMBERS INTERFACE (for serial controlled items). Theerror_code and error_explanation columns on the MTI table will point toany potential root cause of the error.

„Transaction Open Interface‟ form will allow users to query the transactioninterface data which is a useful debugging setup.

RMA Attribute 15 of the oe_order_headers_all and oe_order_lines_all will beupdated to „I‟ if the records are picked up for synchronizing (creation).Picked records will be inserted into oe_headers_iface_all andoe_lines_iface_all in the distributed instance. Attribute 15 of theoe_order_headers_all will be updated to „C‟ if the records have beenpicked up for synchronization (RMA cancellation at header level). These

records would have been inserted in oe_headers_iface_all table indistributed instance. Error_flag column in oe_headers_iface_all andoe_lines_iface_all can be checked to see if the interface record errorredout in distributed instance.


25/28


Page 25 of 28

5 Customizing an ODI MapBased on specific business needs, customers can customize the ODI maps shipped by Oracle.In this section, we will review the approach needed to customize the Items ODI map by adding anew field in the mappings supported by this map. Please refer to Metalink for additional ODIrelated documentation

Steps to be followed for customization-

A. Start the ODI designer. Create a new connection to the work repository in which theIntegration maps were imported.

B. Access the ODI maps through the designerC. Open the appropriate interface under the „WMS Import Items‟ folder in the designer .

D. Add the additional field and re-generate the scenario. This scenario is ready to beexecuted with the customisation.

Recommendation – Oracle recommends that customized maps be deployed in a separaterepository than the one which holds the Oracle shipped maps. Any subsequent ODI map patcheswill be successfully applied only on the repository which stores the non-customized ODI maps.The customisation has to be redone on the latest version of the ODI maps provided by Oracle.


26/28


27/28


Page 27 of 28

6. Can I use BPEL to integrate Distributed WMS with my host system?

Yes, BPEL or any other middleware can be used for integrating to the Distributed WMS. CurrentOracle out-of-the-box solution is based on ODI.

7 .Can multiple Distributed WMS instances integrate to a single ERP instance?

Yes, multiple Distributed WMS instances can be successfully integrated to a single ERPinstance. The current out of the box integration can be used to integrate multiple DistributedWMS instances to a single EBS 11i10 ERP instance by following the steps in section 2.2 foreach Distributed WMS instance .Similar integration can be developed for integrating multipleDistributed WMS to a non EBS ERP instance

8. I have a non-E-Business Suite ERP system and want to integrate distributed WMS as awarehousing solution. Is it possible?

Yes, Distributed WMS is the distributed deployment of WMS irrespective of the host ERPsystem. ODI can be used to integrate a non-EBS suite to the distributed WMS instance. ODIsupports technologies such as Teradata, IBM DB2, Netezza, Sybase IQ ,SAP java connector,flat

files, LDAP, XML etc and can be used to integrate a non-EBS ERP system to distributed WMSPlease refer to ODI documentation for more details about the complete list of technologiessupported

9. Are changes/updates in-and-out of the application driven using an EDA (event drivenarchitecture) or are most interfaces setup in batch mode? What is the best-practice youprescribe/suggest given other successful customer deployments?

Oracle WMS provides the flexibility of event driven as well as batch mode processing for data.Decision needs to be made to leverage the appropriate mode based on the businessrequirement. Please refer to the Integration and Technical implementation Whitepaper for

additional details.

10. Can I customize the maps provided by Oracle to support my Business requirements?

Yes, you can customize the shipped maps as part of the Oracle Integration. Please refer toSection 5 about customization related guidelines. Please note that customized maps will not besupported by Oracle

11. Can I contact Oracle support for any deployment or execution related issues with themaps?

Please ensure that all the maps are deployed as per the processes explained in this document.Please also review the Troubleshooting tips in section 4 to address any execution related issuewith the maps. In case the issue is still not resolved, please log a service request against Oracle(Product WMS)


28/28


Page 28 of 28

EBS 11i10 to Distributed WMS IntegrationJanuary 2010 Authors: Snehal Fulzele, Puneet Sood ([email protected],[email protected])

Oracle CorporationWorld Headquarters500 Oracle ParkwayRedwood Shores, CA 94065U.S.A.

Worldwide Inquiries:Phone: +1.650.506.7000Fax: +1.650.506.7200www.oracle.com

Oracle Corporation provides the software that powers the Internet.

Oracle is a registered trademark of Oracle Corporation. Various product and service names referenced hereinmay be trademarks of Oracle Corporation. All other product and service names mentioned may be trademarksof their respective owners.

Copyright © 2009 Oracle Corporation

All rights reserved.
mailto:[email protected]:[email protected]://www-apps.us.oracle.com:1100/~sfulzele/[email protected]://www-apps.us.oracle.com:1100/~sfulzele/[email protected]://www-apps.us.oracle.com:1100/~sfulzele/[email protected]://www.oracle.com/http://www.oracle.com/http://www.oracle.com/http://www-apps.us.oracle.com:1100/~sfulzele/[email protected]:[email protected]

DWMS+ODI+whitepaper

Documents

Transcript of DWMS+ODI+whitepaper