Oracle Enterprise Data Quality for Product Data R12 PIM Connector Installation Guide, Release 11g R1 (11.1.1.6)

Release 11g R1 (11.1.1.6)

E29141-02

Contents

Title and Copyright Information

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Introduction

2 Getting Started

- Installation Path

- Installation Prerequisites

- Preparing for Installation

- R12 PIM Connector Package Contents

3 Creating the dls User and Schema

- Creating the dls User

- Installing the Database Schema

4 Installing the Application Sample Files

- Installing the R12 PIM Connector Application Server Sample Files

- Installing the R12 PIM Connector Application Client Sample Files

- Enterprise DQ for Product DSA Sample Files Overview

- Default Entries in DSAs

- Creating and Updating Semantic Models from PIM Metadata Import

- Importing Alternate Catalog Metadata

- Creating and Updating the Semantic Cache

- Creating Production Batches

- Processing a Batch of Data Thorough the Cleansing and Matching Process

- Preconfigured Governance Studio Projects

- Preconfigured Excel Spreadsheet Sample

Oracle® Enterprise Data Quality for Product Data

R12 PIM Connector Installation Guide

Release 11g R1 (11.1.1.6)

E29141-02

January 2013

Oracle Enterprise Data Quality for Product Data R12 PIM Connector Installation Guide, Release 11g R1 (11.1.1.6)

E29141-02

Copyright © 2001, 2013,  Oracle and/or its affiliates. All rights reserved.

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, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

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

Preface

This manual highlights the installation and configuration of Oracle Enterprise Data Quality for Product Data R12 PIM Connector.

By extending Enterprise DQ for Product capabilities, Oracle enables customers to improve the accuracy, completeness, and integrity of their master product data.

To understand the concepts presented, you must use this reference guide in conjunction with the Enterprise DQ for Product documents listed in "Related Documents".

The guide uses the Vision Demo Database as a means to provide access to a common set of data, which is available to use as examples and validate the setup and configuration of the server. The guide will use the Item Class Category Name of Capacitors under the Item Class of Passives.

Note:
Enterprise DQ for Product is only certified with the Oracle Site Hub and Oracle Product Hub for Retail Media Pack.

Audience

You should have a basic understanding of the DataLens Technology.

This document is intended for IT administrators.

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 visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For more information, see the following documents in the documentation set:

- The Oracle Enterprise Data Quality for Product Data R12 PIM Connector User's Guide provides highlights of the core process steps and features of Enterprise DQ for Product R12 PIM Connector.

- The Oracle Enterprise Data Quality for Product Data R12 PIM Connector API Interface Guide provides information about installing and using the R12 PIM Connector API.

- The Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Installation Guide provides detailed Oracle DataLens Server installation instructions.

- The Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Administration Guide provides information about installing and managing an Oracle DataLens Server.

- The Oracle Enterprise Data Quality for Product Data R12 PIM Connector API Interface Guide provides information about using the R12 PIM Connector API.

- The Oracle Enterprise Data Quality for Product Data Application Studio Reference Guide provides information about creating and maintaining Data Service Applications (DSAs).

- The Oracle Enterprise Data Quality for Product Data AutoBuild Reference Guide provides information about creating an initial data lens based on existing product information and data lens knowledge.

- The Oracle Enterprise Data Quality for Product Data Knowledge Studio Reference Guide provides information about creating and maintaining data lenses.

- The Oracle Enterprise Data Quality for Product Data Governance Studio Reference Guide provides information about building projects to analyze your transformed data, create reports to show the quality of your data, and identify missing attributes.

- The Oracle Enterprise Data Quality for Product Data Services for Excel Reference Guide provides information about creating a DSA based on data contained in a Microsoft Excel worksheet.

See the latest version of this and all documents in the Oracle Enterprise Data Quality for Product Data Documentation web site at

http://docs.oracle.com/cd/E35636_01/index.htm

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, text that you enter, or a file, directory, or path name.

monospace

Boldface, monospace type indicates commands or text that you enter.

1 Introduction

The Oracle DataLens Server can be configured to run with multiple servers:

- Oracle DataLens Administration Server

- Oracle DataLens Transform Server

The administration of all servers in a multi-server configuration is controlled with the Oracle DataLens Administration Server. The purpose of the Administration Server is to manage the various administrative tasks of the servers for the server groups (referred to as Transform Servers) and can itself serve as its own Transform Server when installed alone in a single node configuration. By spreading the data processing load across multiple servers the Oracle DataLens Server system provides scalability and configuration control over the various functional areas involved in developing, testing, and ultimately executing Oracle DataLens jobs.

The type of Oracle DataLens Server Group that a Transform Server belongs to controls the individual server functionality. A server group may contain one or many physical servers. There are three server groups:

- Development Server Group

- Production Server Group

- Quality Assurance Server Group

The Server Groups contain individual Oracle DataLens Servers on physical machines that can load balance among servers within the group. The data lenses and DataLens Service Applications (DSAs) are deployed from one group to the next beginning with the development group, then migrating to the Quality Assurance Group for testing before arriving in the Production Group for deployment to production. This multiple group migration function facilitates an enterprise business process where multiple functional areas work on data lens objects in stages before releasing them to production.

The integration of Oracle R12 Product Information Management (PIM) and Enterprise DQ for Product (EDQP) adds a package called the "R12 PIM Connector" to the Enterprise DQ for Product solution upload package.

2 Getting Started

This chapter provides information you need to get started installing the R12 PIM Connector, including installation prerequisites, preparing to install, and the components in the product package.

Installation Path

The R12 PIM Connector installation involves three main stages as follows:

Installation Prerequisites

The following components need to be installed before installing the Enterprise DQ for Product R12 PIM Connector:

1. Install the Oracle E-Business Suite (EBS) server including the latest patch sets.
For 12.1 you must install the Oracle Batch Creation API patch (number 8401045:R12.EGO.C).

You can check the patch version from the Applications Manager as follows:

2. Install and configure Enterprise DQ for Product release 11g (11.1.1.6) For more information, see Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Installation Guide and Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Administration Guide.
The R12 PIM Connector product is included in the EDQP installation as a tar file.

3. Install Enterprise DQ for Product Services for Excel release 11g (11.1.1.6) on your client machines. For more information, see Oracle Enterprise Data Quality for Product Data Services for Excel Reference Guide.

Preparing for Installation

Locate and unzip the R12 PIM Connector release 11g (11.1.1.6) product:

1. Locate and change directories to the Middleware home directory into which you installed EDQP. The default directories are the following:
On Linux and UNIX:

/opt/Middleware/Oracle

On Windows:

C:\Oracle\Middleware

This directory is referenced as MW_HOME in Fusion Middleware documentation.

2. Unzip MW_HOME/edqp_template1/opdq-connectors-11-1-1-6.zip in the same directory to extract all files.

3. Create a directory named R12_PIM, and then change directories to it.

4. Untar the opdq-connector-r12_pim.tar file to the R12_PIM directory to extract all files using the following command.
tar -xvf opdq-connector-r12_pim.tar

R12 PIM Connector Package Contents

The R12 PIM Connector product directory, MW_HOME/edqp_template1/R12_PIM, contains the following directory structure:

- dls_pim_connector_install - R12 PIM Connector EBS installation script and integration files.

- pdqcms_application_templates - Governance Studio and Services for Excel client sample files.

- serverLocal - R12 PIM Connector data lens and DSA sample files that can be automatically deployed to your Oracle DataLens Server.

3 Creating the dls User and Schema

This chapter describes how to create the dls user, install the R12 PIM Connector database schema, and associate the installed database schema with the dls user.

Note:
This chapter presents one EBS environment. Your EBS environment may be different so the computer responses will differ though the commands you execute do not.

Creating the dls User

The R12 PIM Connector API components are installed on the EBS using Oracle Database user account, dls. Create the dls user:

1. Log into your EBS database server as user, applmgr or the user that installed the original EBS instance.

2. Ensure that your login user environment is sourced.
Following is an example of how to source the applmgr environment file:

. /d01/oracle/VIS/apps/apps_st/appl/APPSVIS_system1.env

3. Check that the environment is set correctly:
echo $TWO_TASK

The return value should be the SID of the EBS database server.

4. From the system that you installed EDQP, copy the dls_pim_connector_install folder that you extracted from the product package to a temporary directory on your EBS database server.

5. On your EBS database server, change directories to the dls_pim_connector_install directory.
For example, cd MW_HOME/edqp_template1/R12_PIM/dls_pim_connector_install

6. Create the R12 PIM Connector dls user in the EBS database server:
sqlplus system/manager@VIS < dls_user_creation.sql

Ensure that the dls user creation successfully completes and no errors are displayed.

7. For EBS 12.2.x servers, the dls user must have the "editions" feature enabled. To enable editions for the dls user, enter the following command from SQL*Plus:
ALTER USER dls ENABLE editions FORCE;

Installing the Database Schema

The PIM Connector database schema which includes tables, views, and packages that implement the PIM Connector API is installed using the dls_pim_connector_install.sh script into the EBS dls database user previously created. The necessary grants and privileges to the tables accessed by the Enterprise DQ for Product R12 PIM Connector are configured in the apps/apps schema.

- The installation script uses the existing Transaction tablespace and for the installation of the DLS tables in indexes such as the semantic key cache. This is consistent with current Oracle practice (see MetaLink note 248857.1 under the Product tablespaces link).

- The temporary tables used by the Enterprise DQ for Product will be written to the Interface tablespace (see MetaLink note 248857.1 under the Product tablespaces link).

- The installation script creates a new schema called dls that is granted quota on the Transaction and Interface table spaces.

1. While still logged into the EBS Server as applmgr and in the dls_pim_connector_install directory, change the file permissions of the R12 PIM Connector installation script:
chmod +x *.sh

2. Install the database schema:
./dls_pim_connector_install.sh

Please enter Apps Schema Name for VIS:

3. Enter:
apps

Please enter Apps Password for VIS:

4. Enter:
apps

Please enter DLS Schema Name for VIS:

5. Enter:
dls

Please enter DLS Password for VIS:

6. Enter:
dls

The dls database schema has now been populated with the tables, views, packages, synonyms and triggers. The apps schema has also been populated with the grants and synonyms needed to call the Enterprise DQ for Product R12 PIM Connector.

A log file is written to the tmp directory of the applmgr user.

7. Review the installation log file, dls_inst_####.log, and ensure that there were no errors.
The following erroneous error message should be ignored:

Warning: Package created with compilation errors.
.
Errors for PACKAGE DLS_CONNECTOR_PVT:
.
LINE/COL ERROR
-------- -----------------------------------------------------------------
49/3     PL/SQL: Declaration ignored
51/66    PLS-00201: identifier 'DLS_CONNECTOR_PUB.G_SEMANTICATTR' must be
declared

4 Installing the Application Sample Files

The R12 PIM ConnectorApplication Server sample files are a collection of DSAs that are delivered with EDQP so that you can install them on your Oracle DataLens Server as an example of how you could process your data, using the R12 PIM sample data. These include a set of DSAs, Governance Studio Projects, and AutoBuild application samples. Each of these is described in this chapter.

Installing the R12 PIM Connector Application Server Sample Files

The R12 PIM Connector Application Server sample files are a collection of DSAs that are delivered with EDQP so that you can install them on your Oracle DataLens Server to see how you could process your data.

Install the R12 PIM Connector application server sample files:

1. On your Oracle DataLens Administration Server system, log in using the administrator user you established when installing the server in preparation to copy files.

Note:
This step does not refer to the Oracle DataLens Administration Server web page.

2. Copy the MW_HOME\edqp_template1\autodeploy directory that you extracted from the product package to the WebLogic dls_domain directory on your Oracle DataLens Administration Server. By default, these directories are:
On Linux and UNIX: MW_HOME/user_projects/domains/dls_domain/opdq/autodeploy

On Windows: MW_HOME\user_projects\domains\dls_domain\opdq\autodeploy

Note:
The preceding directories are the defaults when installing your Oracle DataLens Server; your installation directory may vary.

This automatically deploys (autodeploys) the DSA sample files to your Oracle DataLens Server. The Oracle DataLens Administration Server polls the autodeploy directory every 10 minutes and attempts to autodeploy the DSA sample files that are placed in the autodeploy parent folder.

3. Log out of the Oracle DataLens Administration Server system.

4. Wait 10 minutes to ensure that the server samples have been autodeployed.

5. Log into the Oracle DataLens Server Administration web page.
For more information about these web pages, see Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Administration Guide.

6. Verify that the AUPIM_ DSAs and AUPIM_Capacitors.project data lens have been autodeployed.

Installing the R12 PIM Connector Application Client Sample Files

Install the R12 PIM Connector application client sample files:

1. On your Enterprise DQ for Product client system, copy the pdqcms_application_templates folder from the directory on the server where you unzipped the product package to your client Desktop. By default, these directories are:
On Linux and UNIX: /opt/Oracle/Middleware/edqp_template1/R12_PIM

On Windows: C:\Oracle\Middleware\edqp_template1\R12_PIM

The preconfigured AutoBuild Excel workbook in the spreadsheet_templates folder. For more information about these workbook, see "Preconfigured Excel Spreadsheet Sample".

The preconfigured Governance Studio projects are in the gov_studio_projects folder.

2. Start the Governance Studio and import each project file (*.ams) in the .../desktop/pdqcms_application_template/gov_studio_projects directory.
For more information about importing, see Oracle Enterprise Data Quality for Product Data Governance Studio Reference Guide. For more information about these projects, see "Preconfigured Governance Studio Projects".

3. Start the Knowledge Studio and check out the DLS_Import_Template data lens.

Note:
Before using the AutoBuild application, delivered in Services for Excel, the DLS_Import_Template data lens must be checked out from the Oracle DataLens Server. For information about checking data lenses in and out of the Enterprise DQ for Product, see Oracle Enterprise Data Quality for Product Data Knowledge Studio Reference Guide.

Enterprise DQ for Product DSA Sample Files Overview

There are four main categories of samples DSAs that illustrate the overall integration capabilities between the R12 PIM Connector and PIM.

- Metadata Import

- Semantic Model build from PIM metadata extract.

- Alternate Catalog build from PIM metadata extract.

- Creating and updating the semantic cache information that is used by the integration services to perform semantic matches.

- Creating a new batch from a query of Production data.

- Processing interface table batches thorough the Integration Services DSA and updating the results back in the interface tables.

Default Entries in DSAs

All DSAs shipped as part of the Enterprise DQ for Product R12 PIM Connector have default entries that allow for a quick configuration. The following default entries will need to be reviewed and configuration changes may be required. These changes are outlined in the Oracle Enterprise Data Quality for Product Data R12 PIM Connector User's Guide.

Default Database Connection

The default database connection name for all DSAs is, PIM_Connector. This database connection will be pointing to a fictitious server name with a fictitious user and password that will need to be configured as part of the initial server configuration.

Default Data Lens

The default data lens for all DSAs that process items in Enterprise DQ for Product is AUPIM_Capacitors.project. This data lens contains semantic models that work with the Capacitors Item Class category in the Vision Database installed with most R12 PIM Connector systems. A process of testing the system using this sample lens and then updating this data lens with actual customer specific data lenses is documented in Enterprise DQ for Product.

Creating and Updating Semantic Models from PIM Metadata Import

AUPIM_CREATE_SEMANTIC_MODEL

This DSA retrieves the semantic model metadata for a given ICC from the PIM system. AutoBuild uses this semantic model metadata to build a data lens that as a starting point for the cleansing and enrichment process. This DSA is typically run using the Enterprise DQ for Product Services for Excel to create the data needed by the AutoBuild application. This data includes attributes and sample descriptions.

Importing Alternate Catalog Metadata

AUPIM_EXTRACT_ALT_CATALOGS

This DSA is used by the AutoBuild application to import one or more alternate catalogs and create classification schemas inside a selected data lens. This DSA is typically run using the Services for Excel to create the data needed by the AutoBuild application. This data includes the metadata for the Alternate Catalog entered during the run including the id and parent information.

Creating and Updating the Semantic Cache

AUPIM_CREATE_SEMANTIC_CACHE

This DSA is run as a nightly job to update the Semantic Index from Oracle PIM Production data; this semantic index is used for matching and checking for duplicates.

Creating Production Batches

Oracle PIM System users will be able to process data from the interface tables where the source system is an external source system or where the source system is the PIM Data Hub. In order to process data from external source systems, the PIM users will continue to use the existing methods of loading data into the interface tables, usually the Excel import samples or a direct database load. The PIM users will also have a new feature to load data directly from PIM Production tables into the interface tables using a batch creation process that is included in this application.

AUPIM_PROCESS_EXTERNAL_DATA

This DSA is run to insert your external data into interface tables by the Oracle DataLens Server.

AUPIM_CREATE_PRODUCTION_BATCH

This DSA is run to create a new batch of data from the PIM Production tables. This batch will then be processed by the Oracle DataLens Server and updated back into interface tables.

Processing a Batch of Data Thorough the Cleansing and Matching Process

AUPIM_MAIN_PROCESS

This DSA is run as the main DSA from the DGS. This will take an Oracle PIM batch and clean/standardize/classify/extract attrs/etc from the description and load it into the DGS for further processing. The batches are populated with data from external systems or as pulls from the PIM Production data.

Secondary Data Service Applications for Reprocess and Apply

Secondary DSAs called by the main process as previously described that Reprocess or Apply the changes to the interface table.

DSA Name

Notes

AUPIM_REPROCESS

Reprocesses rows from the following outputs of the Main Process DSA:

- Dups within Batch

- Match on Mfg Part

- Match Against PIM

- Items for Enrichment

- Exceptions

Based on specific process flags, this DSA will reroute the items back to the Governance Studio Main project, or will update the rows back in the interface tables with the correct match_status.

AUPIM_APPLY_RESULTS

Applies rows from the Ready for Load step and updates all pertinent fields in the interface tables.

AUPIM_EXTRACT_ALT_CATALOGS

Applies rows from the Alternate Catalog Review and updates all pertinent fields related to Alternate Catalogs

AUPIM_SET_BATCH_TO_ACTIVE

Updated the batch status from Pending to Active so that the PIM user can go into the Import Workbench UI and invoke the import process.

Preconfigured Governance Studio Projects

Enterprise DQ for Product R12 PIM Connector includes the following Governance Studio project. This project is used by users to create batch specific Governance Studio projects to process interface batch data. The process is documented in the Oracle Enterprise Data Quality for Product Data R12 PIM Connector User's Guide.

AUPIM_Cleansing_and_Matching

The main process that runs the main Data Service Applications that cleanse and match the items in the interface tables.

AUPIM_Create_Production_Batch

The process that automatically creates a new Import Workbench batch from a set of production items.

AUPIM_CREATE_SEMANTIC_CACHE

This administrative process can be run thorough the Governance Studio or can be scheduled to run as a nightly or weekly process. This should be run by System Administrators when not batches are being processed.

For information about how these project samples are used, see Oracle Enterprise Data Quality for Product Data R12 PIM Connector User's Guide.

Preconfigured Excel Spreadsheet Sample

The Enterprise DQ for Product R12 PIM Connector includes the following Excel workbook for use with the AutoBuild application. This preconfigured workbook contain VBA applications that are used to export PIM metadata and to create a set of semantic models with one or more associated alternate catalogs for use in cleansing and matching your specific product data.

CapacitorsExternalBatchTestInput.xlsx

Use this workbook to test your input data prior to executing a PIM external batch load.

For information about how the AutoBuild sample workbook is used to create a data lens and add an alternate catalog to the data lens, see Oracle Enterprise Data Quality for Product Data R12 PIM Connector User's Guide.

Copyright © 2001, 2013, Oracle and/or its affiliates. All rights reserved.