Vertex O2C Tax Link For Oracle R12 Integration Guide

Integration Guide
Vertex® O2C Tax Link for Oracle R12
February 2015
May 2014
Copyright and legal notices
Copyright © 2014 Vertex Global Tax Solutions Ireland Holdings. All rights reserved.
This documentation may not be reproduced, displayed, distributed, modified, posted, republished, or
transmitted in any form or by any means, without the prior written consent of Vertex Global Tax
Solutions Ireland Holdings or its affiliates (collectively, “Vertex”), except as otherwise specified in a valid,
current Vertex license agreement or allowed by law.
Disclaimers
The information contained in this documentation is designed to help users in regard to the subject
matter covered. Some of it may be based upon interpretations of federal, state, foreign and other tax
laws and regulations. Each entity is responsible for making its own determination of how such laws and
regulations apply to its own circumstances and for evaluating the capabilities of, and all data and results
generated by, any product that is described in this documentation. Vertex is not engaged in providing
legal, tax or accounting advice or services and the information contained in this documentation or in any
product cannot replace the advice of competent legal counsel. Further, the information in this
documentation 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.
Trademarks and Service Marks

The trademarks, logos and service marks ("marks") displayed in this documentation are the property of
Vertex or third parties. Users are not permitted to use these marks without the prior written consent of
Vertex or the third party that may own the mark.
Third Party Products

Copies of the licenses for some third-party products included with a Vertex product may be found in or
with the installation materials for that product.
Contents
Preface .................................................................................................................................................... v
Vertex corporate offices ......................................................................................................................... v
Vertex Services and Products ................................................................................................................ vi
About this guide ................................................................................................................................... viii
Purpose ................................................................................................................................................ viii
Scope ............................................................................................................................................. viii

Audience ........................................................................................................................................ viii
Organization .................................................................................................................................. viii
Chapter 1................................................................................................................................................. 1
Overview........................................................................................................................................... 1
Vertex Tax Links for R12 ................................................................................................................... 1
The data flow between Oracle R12 and O Series ............................................................................. 2
Chapter 2................................................................................................................................................. 4
Configuration and Installation .......................................................................................................... 4

Prerequisites..................................................................................................................................... 5
Oracle Patches .................................................................................................................................. 6
Configuring Tax Regime .................................................................................................................... 7
Setting up the Operating Unit/Legal Entity and Service Subscription.............................................. 8
Delete Service Mappings .................................................................................................................. 9
Instances .........................................................................................................................................11
Architecture ....................................................................................................................................11
The Vertex OIC objects ...................................................................................................................11
Database Tier Installation Section ........................................................................................................12
R12.2 Additional Permissions .........................................................................................................13

Service Subscription .......................................................................................................................16
Delete Scripts for Oracle Customized Procedures .........................................................................17
Vertex Reconciliation Installation...................................................................................................18
APP Tier Installation Section .................................................................................................................21
Loading O2C Objects Using FNDLOAD ............................................................................................22

Assigning Vertex Custom Application to the Standard Data Group ...............................................23
Applying Vertex Tax Link 7.1 Upgrade Patch: .......................................................................................24
Applying Vertex Tax Link 7.x TAID / RTAID Patch: ................................................................................24
Applying Vertex Tax Link 7.x AR Recon Patch: ......................................................................................24
Importing the ORAMAST file ..........................................................................................................25
Feb 2015  iii 3/13/2015

Vertex Tax Links for Oracle R12 O2C Integration Guide
Configuring EBTAX ................................................................................................................................26
Configuration overview ..................................................................................................................26

Application Tax Options .................................................................................................................58
Concurrent Requests ............................................................................................................................59
Setting the username and password for webservice XML .............................................................60

Setup of System Profile Options.....................................................................................................62
Vertex Flexible Field Setup .............................................................................................................63
Vertex AR Reconciliation Program .................................................................................................65
Configuring SSL with Vertex O Series On Premise Solution (Local installation) ...................................78
Testing DB to TCPIP / HTTPS Connectivity......................................................................................79

Executing Sample Tests: .................................................................................................................80
Common Errors: ....................................................................................................................................81
Encrypting Passwords ...........................................................................................................................82
Feb 2015  iv
Preface
This preface contains the following information:
• Contacting Vertex®, which includes how to contact us about services and products
• About this guide, which includes its purpose, scope, and audience
Vertex corporate offices

Vertex is a privately held company with offices in these locations:
Global headquarters European headquarters
1041 Old Cassatt Road Vertex Global Tax Solutions, LTD

Berwyn, PA 19312 1 Furzeground Way, Stockley Park
USA Uxbridge, UB11 1EZ
Phone: 610.640.4200 United Kingdom
Toll-free (United States only): Phone: +44 (0)20 8622 3053
800.355.3500 Fax:+44 (0)20 8622 3200
Fax: 610.640.2761
www.vertexinc.com/
Sarasota office Tax Returns processing center
101 Arthur Andersen Parkway 40 Shuman Blvd.

Suite 340 Suite 218
Sarasota, FL 34232 Naperville, IL 60563
USA USA
Phone: 866.829.8324 Phone: 630.328.2600
Feb 2015  v
Vertex Services and Products

The following table provides contact information for Vertex services and products:
For assistance with... Contact...

Technical questions about Vertex Product Support
products you have licensed Phone: 800-281-1900 (Monday through Friday, 8:15 A.M. to
8:00 P.M. United States Eastern Time)
Fax: 610-640-1207
Web: https://my.vertexinc.com/
Up-to-the-minute information Vertex Critical Changes page

about tax rate, tax rule, and Web: https://my.vertexinc.com/category/type/immediate-
jurisdiction changes in Vertex data attention
Questions about your licensing Vertex Account Services

agreement, license renewal, Phone: 800-355-3500 or 610-640-4200
invoicing arrangements, or
Fax: 610-640-5892
obtaining a license file for a
Email: [email protected]
product you have purchased
Web: www.vertexinc.com/ContactUs/web-inquiry-form.asp
Purchasing Vertex services and Vertex Global Headquarters

products Phone: 800-355-3500 or 610-640-4200
Fax: 610-640-5892
Vertex European Headquarters

Vertex Global Tax Solutions Ltd.
Phone: +44 (0) 20 8622 3053
Fax: +44 (0) 20 8622 3200
Regional training classes, Web- Vertex Training

based training classes, or on-site Phone: 800-281-1900 (Monday through Friday, 8:15 A.M. to
training at your facility 8:00 P.M. United States Eastern Time) option #2
Fax: 610-640-5892
Email: [email protected]
Feb 2015  vi
Tax References
Vertex offers a variety of references for tax compliance information as well as
jurisdiction and postal code information. To learn more, see the Reference Products
section of the Web site at www.vertexinc.com/Products/reference_solutions.asp.
Vertex Consulting
Vertex Consulting provides specialized knowledge and experience to help you configure
your Vertex software and ensure that it's integrated correctly with your host system. We
tailor the consulting service to complement your company's internal resources and skills
to address your unique needs.
For more information about the service options available, see the Services/Vertex
Consulting section of our Web site at www.vertexinc.com/Services/onsite.asp.
Feb 2015  vii

About this guide

This guide applies to the Vertex O2C Tax Link for R12 Application.
Purpose
This guide applies to Vertex users who also use Oracle R12 Application. This document is
for those Oracle R12 users who want to install and use the Vertex Tax Links with their
Oracle R12 Application.
Scope
This guide describes what you need to know to:
• Understand how the Vertex Tax Links work with Oracle R12 and Vertex O Series®.
• Install and configure the Vertex Tax Links
Audience
Organization
This guide contains the following chapters:
Chapter 1. Overview
Provides an overview of the Vertex Tax Links, including its functions and the Vertex O
Series and Oracle R12 with which it interfaces.
Chapter 2. Configuration and Installation
Feb 2015  viii

Chapter 1
Overview
This chapter provides an overview of the Vertex Tax Link for R12 and how it acts to
facilitate communication between Oracle R12 business applications and Vertex O Series
software.
In this chapter
Vertex Tax Links for R12 Overview ........................................................... 1
Vertex Tax Links for R12

The Vertex Tax Links is a solution that provides tax functionality to facilitate the
calculation of sales tax. The links comprise multiple groups of related database
representing several layers of functionality between the Oracle R12 Application and the
Vertex O Series Calculation Engine. Vertex Tax Link facilitates communication between
the R12 applications and O Series products.
Vertex Tax Link is a PL/SQL-based implementation. To begin, register and plug in the tax
service for integration. The Vertex Tax Link takes the information passed from R12 and:
1. Translates it to XML.
2. Maps it to the appropriate O Series parameters for processing by the O Series
tax calculation.
The result is returned in a format that Oracle R12 can use. Vertex Tax Link allows Oracle
R12 software to use O Series software to:
• Retrieve and apply proper tax to sales transactions.
• Retrieve tax quotations for a transaction before the transaction is complete.
• Adjust existing transactions and recalculate correct sales tax.
Feb 2015  1 3/13/2015

The data flow between Oracle R12 and O Series

The following figure illustrates the flow of data between the Oracle R12, Vertex Tax Link,
OIC, and O Series for a tax calculation.
Tax Link functionality

The Tax Link encompasses all processes related to determining the necessary
information for and performing tax calculations using Vertex O Series. The solution is
made up of tax calculation and Tax Link components, described in the following sections:
Tax calculation
Tax calculation is the main purpose of this solution. This solution is responsible for
integrating O Series with the Oracle Applications for sales tax calculation at the proper
touch points, gathering the necessary input data, calling the applicable Vertex interface
calls, and processing the results. This functionality includes various database and
application objects, including a Tax Extension. The Tax Extension consists of database
objects that are provided to the customer. These database objects are responsible for
handling certain tasks that usually require customizations to meet each individual
company’s needs.
Tax Link components

Tax Link consists of the following three components:
Oracle Integration Component (OIC)
This component converts the call from EBTax to the O Series XML requests and maps the
parameters to the appropriate XML elements and attributes. The component also
converts the returned O Series XML responses to the format that EBTax can accept.
A debug flag can also be set in an OIC table to capture the XML requests and response.
Feb 2015  2
Vertex R12 Link component

This is the major component of the Tax Link and contains all of the core integration logic.
Vertex APPS Link component
This component creates the service registration and service execution entries that are
required in Oracle to enable calls to Vertex. This component creates grants and
synonyms for the apps database user.
Integration notes
Vertex recommends that users define taxability exemptions and exceptions in O Series,
using its flexibility and functionality to the fullest.
Do not purge the O Series journal records on a regular basis. Because Oracle permits
ongoing changes to existing invoices, O Series continues to synchronize the transactions
residing in the journal.
Oracle requires that Address Validation be turned on in order to call to O Series.
Imported invoices with tax into Oracle will not call Vertex for tax calculation.
Feb 2015  3
Chapter 2
Configuration and Installation
This chapter provides an overview of the Vertex Tax Link for Oracle R12 and how it
facilitates communication between Oracle Financials R12 business applications and
Vertex O Series tax software.
In this chapter
Configuring R12 Tax Regime. ………………………………….….... 5
Installing Vertex Tax Link for Oracle R12 ...……………………...…. 8
Importing ORAMAST file …….. ... …………………………….……… 14
Configuring EBTAX.. ...... …………………………………………….…. 15
Submitting requests .. …………………….……………………….……. 51
Standard order to cash Vertex/Oracle EBtax field mapping….………56
Feb 2015  4 3/13/2015

Prerequisites
To install this product, you must meet the following prerequisites:
• The database in which you are installing the product must be Oracle version 10.2 or
higher.
• You must have installed Vertex O Series TPS 5.0 or 6.0 in a database that is accessible
from the instance in which you are installing the Tax Link.
• You must have write access to the server directory where the custom files reside and
SQL*Plus access to the destination databases, with the proper users and passwords
for the designated database users.
• You must set up the Tax Regime Code in EBtax before installing Vertex Tax Link.
Steps are on following page.
• A tablespace will need to be created prior to the install. We provide a script to create
a user and grant required permissions.
• The Linux/Unix user performing the Vertex Tax Link install will need permission for
the java home directory.
• Create CUSTOM_TOP/reports/US directory for Vertex reports
Feb 2015  5
Oracle Patches
Oracle patches that are required to be applied in order for a successful integration with
Vertex O Series. We recommend you search Metalink site for any new patches. These
patches also could be superseded by a new patch.
12.0 / 12.1
Oracle Patch Description

9173819 and 9724954 E-Business US Sales and Use tax Import program –
Oramast upload
18347471 E-Business US Sales and Use tax Import program –
Oramast upload (password required)
7642411 Vertex Consolidated
8877828 O2C Error Handling
9778817 Exemption handling
9967675 O2C Corrects OK button in AR Tax Details form
11694368 AutoInvoice Error handling
11874052 AutoInvoice document number update
13404939 Return Multiple Tax Jurisdiction Results
13946483 and 13974260 AutoInvoice handling invoice failures
13972505 Sales Order Attribute update processing
17202262 Consolidated patch
12.2
Oracle Patch Description
18347471 E-Business US Sales and Use tax Import program –
Oramast upload (password required)
Feb 2015  6
Configuring Tax Regime

Before installing the Vertex Tax Link, you must create and configure a Tax Regime Code
and an Operating Unit in EBTax. During the Tax Link installation, you are prompted to
enter the Tax Regime Code value. Then complete the following steps:
1. Log into your Oracle R12 application and access the Tax Manager responsibility.
2. Go to Tax Regime and click Create.
3. Enter the Tax Regime Code and Name value that you desire.
4. Select United States in the Country Name field.
5. Verify that the Effective From date is 01-Jan-1952.
6. Click Continue.
Feb 2015  7
Setting up the Operating Unit/Legal Entity and Service Subscription

To set up the Operating Unit and Service Subscription, complete the following steps:
1. In the Party Name field, enter your Operating Unit or Legal Entity
2. In the Party Type field, select Operating Unit owning Tax Content.
3. In the Configuration for Taxes and Rules field, select Common Configuration
with Party Overrides.
4. In the Configuration for Product Exceptions field, select Common Configuration.
5. In the Effective From field, enter 01-Jan-1952.
6. Click Service Subscription.

7. In the Service Provider field, select Vertex Inc.
8. In the Business Flow field, select Order to Cash.
9. In the Effective From field, enter the current date.
10. In the Enabled field, select Yes.
11. Click Apply.
Feb 2015  8
Delete Service Mappings
1. Click on Home and then Provider Services.
2. Search for Vertex Inc and click Go.
3. Three records display. Delete each record by selecting one at a time.
After the Vertex Tax Link installation is complete, each record is recreated with the
Vertex database package and procedure. The Tax Regime Code also displays.
Feb 2015  9
Registering Custom Application

The Vertex Tax Link solution includes several different types of Oracle Application FND
objects, including concurrent programs and exception reports. Most of the objects must
be assigned to a corresponding Oracle Application. Per Oracle Application standards, this
should be a custom application. Before you install the Vertex Tax Link, you should
determine the custom application you would like to use. You will need the related
application short name at certain parts of the installations. In order to use the Vertex Tax
Link you should register the application in Oracle R 12 by performing the following steps:
1. Log into the Oracle R 12 application as user with access to System Administrator
responsibility
2. Navigate to System Administrator>Application>Register
3. Create an Application, Shortname, and Basepath.
This screen shot is for reference.
Note: If you previously installed Vertex P2P you can skip the above step
as you have already Registered the Custom Application.
Feb 2015  10
Installing Vertex Tax Link for Oracle R12

The following section describes the process of installing the Vertex Tax Link for Oracle
R12.
Instances
The Vertex Tax Link should always be installed in the same instance as the ERP system
that it is being used by. However, it does support both one-tier and two-tier
implementation. A two-tier implementation is where the Vertex server is installed in a
different database than the Vertex Tax Link. A single-tier implementation is where they
both reside in the same instance.
Architecture
The installation scripts are designed using general Oracle Application standards because
they are used by all products in the Vertex Tax Links that integrate with the Oracle
Applications. These standards recommend that you create the tables, indexes, and
sequences under a custom schema, and create synonyms to these objects with all views
and packages under the APPS schema.
The Vertex OIC objects

The Vertex OIC module is part of the Vertex Tax Link, and includes the related code as
part of the installation. OIC is designed to create all objects, including views and
packages in the same schema. Adhering to standard Oracle Application standards, the
Vertex Tax Link installs all of these OIC objects in a custom schema.
Feb 2015  11
Database Tier Installation Section

Set up the Code Files for Database Tier.
Before you can install the component, you should move the
vertex_o2c_db_5.1.10.15.02.tar file onto the file system from which you plan to do the
installation. For best results, Vertex recommends storing them in a directory associated with
the instance in which you are installing the Vertex Tax Link, so that the code is cloned with
the database.
Creating the Vertex Tax Link filesystem
To create the Vertex Link filesystem, complete the following steps:
1. Create a directory (for example,vertex) and copy the
vertex_o2c_db_5.1.10.15.02.tar file to that directory.
2. Type tar –xvf vertex_o2c_db_5.1.10.15.02.tar.

Note: If your database tier and app server tier are separate, you need to create the
directory and expand the vertex. tar file on both tiers.
The following steps for creating user, installing OIC and installing Tax Link must be
performed in the database tier. The steps for fndload must be performed in the app
server tier.
Creating a custom user

You must already have a tablespace. If you already have a custom schema, please skip
this step and provide the grants listed in the next step. If you have already installed
Vertex P2P Tax Link, you do not create a separate custom schema for the Vertex O2C Tax
Link. Both tax links reside in the same custom schema. When creating a custom user,
complete the following steps:
as you have already created the Custom User.
1. Change the directory to /vertex_o2c_db/code/scripts.

2. Log into SQL*Plus as the user (sys) who has privileges to create a custom user and
grant access.
3. Type @install_custom_user.sql. The script prompts you for schema username,
password, and tablespace.
The schema username and password can be whatever you want (for example,
vertex/vertex). The tablespace would be an already existing tablespace.
4. For more detail on the install_custom_user results, review the custom_user.lst
file.
Feb 2015  12
Grants for Existing user

If you already have the custom user created and therefore did not run our
create_custom_user script, then the following grants need to be provided to that user.
GRANT ALTER ANY PROCEDURE TO &&username;
GRANT CREATE ANY INDEX TO &&username;
GRANT CREATE ANY PROCEDURE TO &&username;
GRANT CREATE ANY SYNONYM TO &&username;
GRANT CREATE ANY TABLE TO &&username;
GRANT CREATE SEQUENCE TO &&username;
GRANT CREATE SESSION TO &&username;
GRANT CREATE TRIGGER TO &&username;
GRANT CREATE VIEW TO &&username;
GRANT "CONNECT" TO &&username;
R12.2 Additional Permissions

If you are using R12.2 then the following additional grants are required for a successful
tax link install. Substitute xxvertex with your tax link custom schema username.
Log into sqlplus as sysdba

alter user xxvertex enable editions;
grant execute on utl_http to xxvertex;
grant execute on DBMS_OBFUSCATION_TOOLKIT to xxvertex;
grant execute on dbms_lob to xxvertex;
grant execute on dbms_sql to xxvertex;
Feb 2015  13
Access Control List Privileges

For Oracle 11g database user you will need to provide additional privileges for access
control list (acl). If you already provided ACL privileges for the tax link custom schema
during Vertex P2P Tax Link install you do not perform this step again for the Vertex O2C
Tax Link.
1. Change the directory to /vertex_o2c_db/install_acl

2. For granting ACL privileges the first time, please open the first.sql file to edit,
comment out the drop_acl line and save.
--dbms_network_acl_admin.drop_acl(acl => 'utlpkg.xml');
3. Log into SQL*Plus as sysdba
4. Type @install_acl.sql
5. The script will prompt you for custom schema username.
PROMPT Enter the custom user name
Note: It is required the custom username value be entered in uppercase.
as you have already configured the Access Control List (ACL).
Installing Vertex OIC Objects

If you already installed OIC during Vertex P2P Tax Link install you do not install OIC again.
To install Vertex OIC, complete the following steps:
1. Change the directory to …/vertex_o2c_db/vertex_o_series_integration/oic.
2. Log into SQL*Plus as the tax link custom schema user.
Run spool vertex_oic_install.lst
Type @vertex_oic_install.sql.
The script prompts for ‘Enter value for 1: ‘ Enter the full directory path to the
vertex_oic_install.sql file.
Run spool off

3. Review the vertex_install.lst file
Feb 2015  14
Installing Vertex Tax Link database objects

To install the Vertex Tax Link, complete the following steps:
1. Change to the …/vertex_o2c_db/install directory.
2. Log into SQL*Plus as apps user.
3. Type @install_tax_link.sql
4. The script prompts you for the custom schema user and password as well as apps
username and password. Enter these values when you are prompted.
Example:
PROMPT Enter the custom user name
XXVERTEX
PROMPT Enter the custom password.
XXVERTEX
Example:
PROMPT Enter the apps user name (apps)
APPS
PROMPT Enter the apps user password
Enter the password

The script creates the various database objects related to the Vertex Tax Link. It logs
in under the schemas you provided as needed.
5. When the script completes successfully, you may now exit SQL*Plus. You have
successfully installed the Vertex Tax Link database objects.
6. For more detail on the install results, review the tax_link_install.lst file.
Feb 2015  15
Service Subscription
To subscribe your Tax Regime and create the correct service mappings perform the
following steps:
1. Change to the …/vertex_o2c_db/install directory.

2. Log into SQL*Plus as apps user.
3. Type @install_service_subscription.sql
4. The script prompts you for the apps username and password. Enter these values
when you are prompted.
Example:
PROMPT Enter the apps user name (apps)
apps
PROMPT Enter the apps password
apps password
5. The script prompts you for the Vertex Tax Regime code you set up in Oracle R12.
Include single quotes before and after the regime code.
Example:
‘VERTEX REGIME’
6. Review install_service_subscr.lst file
Feb 2015  16
Delete Scripts for Oracle Customized Procedures
Note: This step applies if you are not using Vertex QSeries after the Vertex O2C Tax Link
installation. If you will continue to use Vertex Q Series for any Operating Units, then do
not run the delete scripts noted below. Contact vertex Product Support.
Oracle has provided the following delete scripts to run to clear records for customized
procedures from the subscription setup.
Log in as apps user and run following scripts:
DELETE FROM ZX_API_CODE_COMBINATIONS
WHERE CODE_COMBINATION_ID IN (SELECT DISTINCT CONTEXT_CCID
FROM ZX_API_REGISTRATIONS
WHERE PACKAGE_NAME LIKE 'ZX%');
COMMIT;
DELETE FROM ZX_API_REGISTRATIONS WHERE PACKAGE_NAME LIKE 'ZX%';

COMMIT:
Feb 2015  17
Vertex Reconciliation Installation

If the Vertex O Series database is on a different instance then the Vertex Tax Link
database, this is considered a two tier environment and a public database link is required. If the Vertex O
Series database resides on the same instance as the Vertex Tax Link database, this is considered a one
tier environment and a database link is not needed, please skip to one tier install steps. If you created a
db link during Vertex P2P Tax Link install, you do not create another db link for the O2C Tax Link just use
the existing db link.
Two tier install steps:
1. Change to the vertex_o2c_db/code/scripts
2. Open and edit the install_db_link.sql with the name of the database and the
connection information to the Vertex O Series Tax Journal database.
CREATE DATABASE LINK "Name of the databaselink”
CONNECT TO {db user}
IDENTIFIED BY {db pwd}
USING {'service name’}
3. Log into SQLPlus as apps and run the install_db_link.sql
Note: If you previously installed Vertex P2P you can skip the Create
Database Link step as you have already configured the database link
during the P2P installation.
4. If your db link is connected to the OSeries Journal schema you need to grant
select for the Journal schema user to the OSeries appuser table. If your db link is
connected to the OSeries schema where the appuser table resides, then you
need to grant select for that schema user to the vtx_rec view in the Oseries
Journal schema.
5. Create the following two synonyms as apps
create synonym VTX_REC for oseries_journal_schema_user.vtx_rec@db_link_name
create synonym APPUSER for oseries_schema_user.appuser@db_link_name
6. In the EBS database server create a tnsnames.ora entry for the Vertex O Series
schema you created the db link to access.
oseries_journal_schema_user - The VTX_REC object is an OSeries view, which would be in your

OSeries Journal Schema. Enter the schema user for this value.
Feb 2015  18
oseries_schema_user - The APPUSER object is a table in OSeries. Depending on your OSeries

installation this table could be in a separate schema then the VTX_REC view or it could be in the
same schema. Enter the schema user for this value.
Installing AR Reconciliation Program for Two tier

For a two tier environment follow these steps:
1. Change to the vertex_o2c_db/install directory

2. Log into SQL Plus as apps
3. Run @install_twotier.sql
You will be prompted for the following information:
Enter the Vertex Tax Link custom schema user: - i.e. xxvertex
Enter the Vertex Tax Link custom schema password:
Enter the app user (apps): – i.e. apps
Enter the app user password:
Enter the db link name:
Enter the database name of O Series:
Enter the O Series appuser name:
Enter the O Series appuser password:
Enter the O Series Journal database owner name:
Enter O Series Journal database owner password:
4. Review the install_ar_recon_twotier.lst file
Feb 2015  19
Installing AR Reconciliation Program for One tier

For a one tier environment follow these steps:
1. Change to the vertex_o2c_db/install directory

2. Log into SQL Plus as apps
3. Run @install_onetier.sql
You will be prompted for the following information:
Enter the custom table schema user: - i.e. xxvertex
Enter the custom table schema password:
Enter the app user (apps): – i.e. apps
Enter the apps password
Enter the O Series appuser name:
Enter the O Series appuser password:
Enter the O Series Journal user name:
Enter O Series Journal password:
4. Review the install_ar_recon_onetier.lst file
Feb 2015  20
APP Tier Installation Section
Set up the Code Files for APP Server Tier

Before you can install the link, you should move the vertex_o2c_apps_5.1.10.15.02.tar
file onto the file system from which you plan to do the installation.
Multiple App Servers
If you have multiple application servers and they have a shared library then you only
need to install the tax link on one app server, if they do not have a shared library then
you need to install the tax link on each app server.
To create Vertex Tax Link file system perform the following steps:
1. Create a directory (for example, vertex) and copy the
vertex_o2c_apps_5.1.10.15.02.tar file to that directory.
2. Type tar –xvf vertex_o2c_apps_5.1.10.15.02.tar.
Application Setup
After installing the database objects, you need to set up the Oracle Application objects.
This equates to installing numerous FND objects.
1. Make sure that all *.sh scripts in the /vertex_o2c_apps/fndload directory are
executable – chmod 755 *.sh
Feb 2015  21
Loading O2C Objects Using FNDLOAD

We provide a shell script for Linux, AIX and Solaris. Please use the shell script for your
operating system. To generate the definition files, do the following:
1. Change to the vertex_o2c_apps/code/loaders directory.
2. Run the following command for a Linux OS: ./upload_linux.sh
For AIX and Solaris OS run the following: ./update_ldt_with_customer_vals.sh
Note: This file can be located in the /vertex_o2c_patch_5.1.10.15.xx/vertex_o2c_apps/code/loaders
directory
3. Enter the following prompts:

PROMPT Application User Name
<is an Oracle ERP Applications active and valid user name >
PROMPT Custom Application Short Name
<is the short name defined in Registering Custom Application>
The script will generate the necessary text files to load the FND objects for your system.
4. Review the resulting .txt files to verify they were generated successfully.
Upload O2C Source Files

After you have generated the proper definition files, to create the FND objects using
FNDLOAD, do the following:
1. Change to vertex_o2c_apps/fndload directory.
2. Run the following command: ./fnd_upload.sh
You will be prompt for the following:
Enter apps password - apps db password
Enter machine name - EBS application servername
Enter port number - R12 application tier port (not your db port)
The script will upload the FND objects into your new system.
3. Review the resulting .log files to verify the objects were imported successfully.
Feb 2015  22
Upload AR Recon Application

1. From /vertex_o2c_apps/fndload directory run the following command:
./fnd_upload_recon.sh
You will be prompt for the following:
Enter apps password - apps db password
2. Review the resulting .log files to verify the objects were imported successfully.
Copying RDF Files
1. Permissions are need to copy .rdf files from vertex_o2c_apps/code/loaders to

$CUSTOM_TOP/reports/US directory of custom application. After you set the correct
permissions, please copy the .rdf files from the vertex_o2c_apps/code/loaders
directory to the $CUSTOM_TOP/reports/US directory. These reports run as
concurrent processes.
2. Set the base path for the CUSTOM_TOP directory in the environment variable file.
Assigning Vertex Custom Application to the Standard Data Group

To assign Vertex Custom Application to the Standard Data Group, complete the following
steps:
1. Navigate to System Administrator Responsibility > Security:Oracle > Data
Group.
2. For Standard DataGroup, create the following record:
Application = Vertex Custom Application
Oracle ID = APPS
as you have already Assigned the Vertex Custom Application to the
Standard Data Group.
Feb 2015  23
Applying Vertex Tax Link 7.1 Upgrade Patch:

If you are integrating with Vertex O Series 7.0 then you should patch the Vertex O2C Tax
Link to 7.1.1.16.xx. The latest Vertex O2C Tax Link Patch 7.1.1.16.xx is available on
myVertex to download and has release notes which includes installation steps.
This patch will upgrade to the latest Tax Link code and upgrade to process 7.0 XML
schemas.
Applying Vertex Tax Link 7.x TAID / RTAID Patch:

If upgrading to Vertex O2C Tax Link 7.1.1.16, you will also need to apply the latest Tax Link
Vertex TAID Patch 7.1.x.
This patch is also available on myVertex to download.
Applying Vertex Tax Link 7.x AR Recon Patch:

Another patch that you will need to apply when patching the Vertex O2C Tax Link to 7.1.1.16 is
the Vertex AR Recon. This patch is also available on myVertex to download.
Note: If you are integrating to Vertex O Series in our hosted Vertex OnDemand environment
then you would not apply the Vertex AR Recon patch.
Feb 2015  24
Importing the ORAMAST file

Prior to importing the oramast file, please first review Metalink note 779544.1 and apply the appropriate
patches. The import can be run for a single Regime. The Oramast file can be found on the My Vertex
Support Download site : https://my.vertexinc.com/
as you have already imported the Oramast file.
To import the ORAMAST.dat file, complete the following steps:

1. Copy oramast.dat file to a Linux or UNIX directory in ASCII mode to the R12 app
server. Log into Oracle R12 and select the Tax Managers responsibility. Submit a
Request Set.
2. Select E-Business US Sales and Use Tax Import Program.
3. Enter the directory and filename in which the oramast.dat datafile has been placed
in the File Location and Name field, for example, /ora/ORAMAST.dat.
4. Select 1 (for Vertex) for the Tax Content Source field.
5. Select a Tax Regime Code for the Tax Content Source Tax Regime Code field.
6. Click OK and submit the request.
Feb 2015  25
Configuring EBTAX
Configuration overview
The following section provides steps necessary to enable and use O Series with Oracle
R12. O Series returns multiple jurisdictional tax levels per line item. These tax levels must
be defined and configured in EBtax in order for the tax results to be correctly processed
by Oracle R12.
When importing the oramast.dat file, the CITY, COUNTY, and STATE tax levels are
automatically created and configured. The steps provided in this guide are repeated for
each jurisdictional tax level and only illustrated for DISTRICT and LOCATION. The
additional tax levels that are required to be set up must be entered in the order they are
shown below. You set them up in the Tax field, located in the Tax Manager > Tax
Configuration >Taxes window. They include the following:
DISTRICT
LOCATION
PARISH
TERRITORY
APO
FPO
TRANSIT_DISTRICT
SPECIAL_PURPOSE_DISTRICT
LOCAL_IMPROVEMENT_DISTRICT
COUNTRY
There are several concurrent requests that must be submitted to enable Oracle R12 to
process transactions to O Series. Oracle provides the Tax Service Plug-in request. Vertex
provides a request to set the Web Service endpoint and another request to set the
username and password for the calculation and Tax Area ID calls to be correctly directed
to O Series.
Feb 2015  26
Configuration steps
Note: For the following configuration steps, you use the Tax Configuration, Defaults
and Controls, and Provider Services tabs.
To configure EBTAX, complete the following steps:
1. Log into your Oracle R12 application.
2. Navigate to Tax Managers > Home > Defaults and Controls.
3. Search for the configuration owner, which is your operating unit.
4. Select the correct party name with the party type of Operating Unit owning Tax
Content.
5. Click Go.
The following figure illustrates this using a Vision Operations operating unit:
Feb 2015  27
Configuring Invoice settings

To configure your Invoice settings, complete the following steps:
1. In the Configuration Owner field, select your Configuration Owner.
2. In the Event Class field, select Invoice.
3. Enter the Effective From date. This should be the same date as Tax Regime.
4. Leave all additional fields as default values.
5. Click Apply.
Feb 2015  28
Configuring Credit Memo settings

To configure your Credit Memo settings, complete the following steps:
2. In the Event Class field, select Credit Memo.
3. Enter the Effective Date value.
4. Leave all additional fields as default values.
5. Click Apply.
Feb 2015  29
Configuring Debit Memo settings

To configure your Debit Memo settings, complete the following steps:
2. Select Receivables for the Application Name.
3. In the Event Class field, select Debit Memo.
4. Enter the Effective From value.
5. Leave all additional fields at their default values.
6. Click Apply.
Feb 2015  30
Configuring Transaction Types

To allow the transaction data to flow to the tax partner you must set the Default tax
classification.
1. Navigation to Receivables Manager > Setup > Transaction Types

2. Search for the Transaction Type Name you want to call Vertex
3. Select Default tax classification check box
Feb 2015  31
Configuring Tax Rates

Use the following procedures to configure tax rates for state, county, and city taxing
jurisdictions.
Note: Depending on patch levels, the Oracle program that loads the oramast data may
create the zero rate Tax Rate setup outlined below. Query the Tax Rates to
confirm this. If the zero rate is not present, then create it. If it is already set up,
then do not complete the following steps. This setup assumes that Oramst was
loaded using the O2C regime.
Configuring Tax Rates - State

To configure state tax rates, complete the following steps:
1. Navigate to Tax Manager > Tax Configuration > Tax Rates.
2. Click Create.
3. In the Tax Regime Code field, select your Tax Regime Code.
5. In the Tax field, select STATE.
6. In the Tax Status Code field, select STANDARD.
7. In the Tax Rate Code field, select STATERATECD.
8. In the Percentage Rate field, enter 0.
9. Enter 01-Jan-1952 for the Effective From date.
Feb 2015  32
10. Click Rate Details. The following window displays.
11. After clicking Rate Details, select Set as Default Rate.

12. Enter 01-Jan-1952 for the Default Effective Rate.
13. Click Apply. This displays the first window. Click Apply again.
Configuring Tax Rates – County

Note: Depending on patch levels, the Oracle program that loads the Oramast data may
create the zero rate Tax Rate setup outlined below. Query the Tax Rates to
then do not complete the following steps.
To configure the COUNTY tax, complete the following steps:
2. Click Create.
5. In the Tax field, select COUNTY.
7. In the Tax Rate Code field, enter COUNTYRATE.

Feb 2015  33
10. Click Rate Details. The following window displays:
11. Select Set as Default Rate.

13. Click Apply. The first window displays. Click Apply again.
Note: Depending on patch levels, the Oracle program that loads the Oramast data
may create the zero rate Tax Rate setup outlined below. Query the Tax Rates to
then do not complete the following steps.
Configuring Tax Rates - City
To configure CITY tax, complete the following steps:
2. Click Create.
5. In the Tax field, select CITY.
7. In the Tax Rate Code field, enter CITYRATE.
Feb 2015  34

10. Click Rate Details. The following window displays.
11. After clicking Rate Details, select Set as Default Rate.

13. Click Apply. The first window displays. Click Apply again.
Feb 2015  35
Configuring District Tax

To configure the DISTRICT tax, complete the following steps:
1. Navigate to Tax Manager > Tax Configuration > Taxes.

2. Click Create.
4. In the Configuration Owner field, select your Global Configuration Owner.
5. In the Tax field, enter DISTRICT.
6. In the Tax Name field, enter District Tax.
7. In the Tax Type field, select LOCATION.

8. In the Geography Type field, select COUNTRY.
9. In the Parent Geography Type field, select COUNTRY.
10. In the Parent Geography Name field, select United States.
11. In the Tax Currency field, select USD.
12. Clear the Allow Tax Recovery check box.
Note: You may have to first click the Show Controls and Defaults link.
13. Click Apply.
Feb 2015  36
Configuring District Tax Status

To configure the tax status, complete the following steps:
1. Navigate to Tax Manager > Tax Configuration > Tax Statuses.

2. Click Create.
3. In the Tax Regime Code field, select a Tax Regime Code.
4. In the Configuration Owner field, select a Configuration Owner.
5. Select DISTRICT in the Tax field.
6. Select STANDARD in the Tax Status Code field.
7. In the Name field, enter District Status.
8. In the Effective From field, enter 01-Jan-1952.

9. Select the check box for Set as Default Tax Status.
10. Click Apply.
Feb 2015  37
Configuring District Tax Jurisdictions

To configure tax jurisdictions, complete the following steps:
1. Navigate to Tax Manager > Tax Configuration > Tax Jurisdiction.

2. Enter DISTJURCODE in the Tax Jurisdiction Code field.
3. Enter District Jurisdiction Code in the Tax Jurisdiction Name field.
4. In the Tax Regime Code field, select a Tax Regime.

6. Select COUNTRY in the Geography Type field.
7. Enter the Effective From date.
8. Select United States in the Geography Name field.
The Precedence level defaults to 300.
9. Select the Set as default Tax Jurisdiction check box.
10. Enter the Default Effective From date.
11. Click Apply.
Feb 2015  38
Configuring District Tax Rates

To configure tax rates, complete the following steps:

2. Click Create.
6. Select STANDARD in the Tax Status Code field.
7. Enter DISTRATECODE in the Tax Rate Code field.
8. Under Rate Periods, enter 0 for Percentage Rate.
9. Enter 01-Jan-1952 as the Effective From date.
10. Click Rate Details.
Feb 2015  39
11. Select the Set as Default Rate check box.

12. Enter 01-Jan-1952 as the Default Effective From date.
13. Click Apply.
14. When the previous window displays, click Apply.
Feb 2015  40
Configuring District Tax Rules

To configure tax rules, complete the following steps:
1. Navigate to Tax Manager > Tax Configuration > Tax Rules.

2. Select Configuration Owner.
3. Select Tax Regime Code.
4. For the Tax field, select DISTRICT.
5. Click Go.
6. Click on the Set Default icon, for each of the following Rule Types and perform the
setup illustrated on the following page.
− Determine Place of Supply
− Determine Tax Applicability
− Determine Tax Registration
− Determine Taxable Basis
− Calculate Tax Amounts
Feb 2015  41
To determine Place of Supply rule types:

1. Select Ship to, use bill to if ship to not found.
2. Click Apply.
To determine Tax Applicability rule types:

1. Select Applicable.
2. Click Apply.
To determine Tax Registration rule types:

1. Select Ship to, use Bill to if Ship to is not available.
2. Click Apply.
Feb 2015  42
To determine Taxable Basis rule types:

1. Select STANDARD_TB.
2. Click Apply.
To calculate Tax Amount rule types:

1. Select STANDARD_TC.
2. Click Apply.
Feb 2015  43
The following window displays.
Feb 2015  44
Enabling District Tax for Transactions

4. Select District for Tax.
5. Click Go.
6. When the record is returned, click Update icon.

7. In the Main Information section, select the Make Tax Available for Transactions
check box.
8. Click Apply.
Feb 2015  45
9. Click Yes.
Your DISTRICT Tax setup is now complete.
Feb 2015  46
Configuring Location Taxes

To set up ___location tax, complete the following steps:

2. From the Tax Regime Code field, select your Tax Regime Code.
3. From the Configuration Owner field, select your Global Configuration Owner.
4. Enter LOCATION in the Tax field.
5. Enter Location Tax in the Tax Name field.
6. Select LOCATION in the Tax Type field.

7. Select COUNTRY in the Geography Type field.
8. Select COUNTRY in the Parent Geography Type field.
9. Select United States in the Parent Geography Name field.
10. Select USD for Tax Currency.
11. Clear the Allow Tax Recovery check box.
12. Click Apply.
Feb 2015  47
Configuring Location Tax Statuses

To configure tax statuses, complete the following steps:
1. Navigate to Tax Manager > Tax Configuration > Tax Statuses.

2. Click Create.
3. From the Tax Regime Code field, select a Tax Regime Code.
4. From the Configuration Owner field, select your Global Configuration Owner.
5. From the Tax field, select LOCATION.
6. Enter STANDARD in the Tax Status Code field.
7. Enter Location Status in the Name field.
8. Enter 01-JAN-1952 as the Effective From date.
9. Select the check box for Set as Default Tax Status.

10. Click Apply.
Feb 2015  48
Configuring Location Tax Jurisdiction

To configure tax jurisdiction, complete the following steps:
1. Navigate to Tax Manager > Tax Configuration > Tax Jurisdiction.

2. Enter LOCJURCODE in the Tax Jurisdiction Code field.
3. Enter Location Jurisdiction Code in the Tax Jurisdiction Name field.

5. Select LOCATION from the Tax field
6. Select COUNTRY from the Geography Type field.
7. Enter 01-JAN-1952 in the Effective From field.
8. Select United States from the Geography Name field.
Precedence level defaults to 300.
9. Select the Set as default Tax Jurisdiction check box.
10. Enter 01-JAN-1952 as the Default Effective From date.
11. Click Apply.
Feb 2015  49
Configuring Location Tax Rates

To configure tax rates, complete the following steps:

2. Click Create.
5. Select LOCATION from the Tax field.
6. Select STANDARD from the Tax Status Code field.
7. Enter LOCRATECODE in the Tax Rate Code field.
8. From Rate Periods, enter 0 for Percentage Rate.
9. Enter 01-Jan-1952 as the Effective From date.
10. Click Rate Details.
Feb 2015  50
11. Select the Set as Default Rate check box.

12. Enter 01-Jan-1952 as the Default Effective From date.
13. Click Apply.
14. When the previous window displays, click Apply.
Feb 2015  51
Configuring Location Tax Rules

To configure tax rules, complete the following steps:
1. Navigate to Tax Manager > Tax Configuration > Tax Rules.

2. In the Configuration Owner field, select your Global Configuration Owner.
4. Select LOCATION from the Tax field.
5. Click Go.
Configuring rule types
Click on the Set Default icon, for each of the following Rule Types and perform the setup
illustrated on the following page.
• Determine Place of Supply

• Determine Tax Applicability
• Determine Tax Registration
• Determine Taxable Basis
• Calculate Tax Amounts
Feb 2015  52
To determine Place of Supply rule types, complete the following steps:

2. Click Apply.
For Determine Tax Applicability rule types, complete the following steps:
1. Select Applicable.
2. Click Apply.
To determine Tax Registration rule types, complete the following steps:
2. Click Apply.
To determine Taxable Basis rule types, complete the following steps:
1. Select STANDARD_TB.
2. Click Apply.
To determine the Calculate Tax Amount rule types, complete the following steps:
1. Select STANDARD_TC.
2. Click Apply.
Feb 2015  53
Note: If you would like to view windows for the preceding setup steps, please review
the windows for DISTRICT setup.
The following Tax Rule window displays:
Feb 2015  54
Enabling Location Tax for Transactions

2. Select United States for the Country Name field.
3. Select your Tax Regime Code in the Tax Regime Code field.
4. Select LOCATION for the Tax field.
5. Click Go.
6. In the LOCATION Tax record field, click the Update icon.
Feb 2015  55
From the Main Information pane, complete the following:

1. Select the Make Tax Available for Transactions check box.
2. Click Apply.
3. Click Yes.
The repeated setup steps for LOCATION and DISTRICT are completed. Follow these same steps for the
additional tax levels listed here and at the beginning of the EBTax Configuration section. Begin at
Configuring District taxes.
PARISH
TERRITORY
APO
FPO
TRANSIT_DISTRICT
SPECIAL_PURPOSE_DISTRICT
LOCAL_IMPROVEMENT_DISTRICT
COUNTRY
Feb 2015  56
Country Defaults
1. Click Country Defaults from the Defaults and Controls tab.
2. Click Create.
4. Select your Tax Regime Code in the Tax Regime Code field.
5. Select LOCATION in the Tax field.
6. Select the Set as Default for Imported Invoices check box under both Tax Regime
Code and Tax.
7. Click Apply.
Feb 2015  57
Application Tax Options

Note: Skip this step if you are using R12.2.x or higher
From the Default and Controls tab, complete the following:
1. Click Application Tax Options.
2. Click Create.
3. Select your Operating Unit.
4. From the Application Name field, select Receivables.
5. For your Default Order, select values according to your implementation. You must
select Oracle Receivables System Options as one of these first four Default Order
values.
6. Select Location from the Financial Options Tax Classification field.
7 Click Apply.
The following is an example of a completed Application Tax Options setup.
Feb 2015  58
Concurrent Requests
There are several concurrent requests that must be submitted to enable Oracle R12 to process
transactions to O Series. Oracle provides the Tax Service Plug-in request. Vertex provides a
request to set the Web Service endpoint, another request to set the username and password for
the calculation and Tax Area ID calls to be correctly directed to O Series, and the Vertex AP
Supplier Tax Area ID Assignment program to pre-assign Tax Area IDs to existing supplier records.
Registering Vertex as the third party for Tax Service

Navigation: Tax Manager > Submit New Request
1. Run the Tax Partner Services Plug-in request

2. For Service Category select Tax Partner Service
3. For Service Owner select Vertex Inc
Feb 2015  59
Setting the username and password for webservice XML

Navigation: Receivables > Submit New Request
Submit the following single request to set the username and password that will be used for all of
the XML calls to Vertex O Series:
1. For Name select Vertex Create application user for Regime Code
2. For Oracle Regime Code enter the Tax Regime subscribed to call Vertex
3. For Vertex User Name enter valid username that is setup in Vertex Central for this
instance
4. For Vertex User password enter the valid password for the user name
5. Click OK button and submit the request.
Note: The username and password are assigned to a partition in Vertex O Series. The transactions
processed with this user account will utilize the Vertex O Series setup specific to that partition.
The following screen shot is for reference only.
Feb 2015  60
Setting the Vertex Web Service End Point URL
as you have already set the Vertex Web Service endpoint.
Navigation: Receivables > Submit New Request
1. For Name select Vertex Set Service End point

2. For Oracle Instance name enter instance_name value from v$instance table.
3. For Vertex service end point enter http://hostname:port/vertex-ws/services/
The hostname is the server where Vertex O Series resides and the port is what is setup for Vertex O
Series web services to use in your application server (i.e. OC4J ,Tomcat).
This web service end point url will be stored in the tax link tables to direct the XML calls to the correct
Vertex O Series instance.
Oracle Instance name – the instance_name from v$instance table in apps schema. This is case sensitive.
Make sure what you enter matches exactly to what is in the table.
Vertex Service end point – web service url to direct the xml calls to the correct Vertex O Series instance.
For RAC environments you will need to run this concurrent program for each instance name using the
same service end point. You can query the list of instance names from gv$instance in apps schema.
Feb 2015  61
Setup of System Profile Options

Required setup for the Vertex Tax Link to process AR Invoices.
Navigate to System Administrator > Profile > System
For Organization enter your Country Operating Unit
For Profile enter VTX%
Click Find button
For VTX: TAX TYPE REGIME enter US
Click on ‘Save’ icon
All setup should be done at the Organization level.
Feb 2015  62
Vertex Flexible Field Setup

The Vertex Tax Link reserves Vertex Flexible Field Code 3 to map the R12 v$instance name for every
transaction. This requires the following setup in Vertex Central. FF11 and FF12 are only used when the
system profile "VTX: Process Registration Numbers" is set to YES
Log into Vertex Central with the correct username and password. This should be the same username and
password as used with ‘Vertex Create application user for Regime Code’ concurrent program.
From the Vertex Central / Tax Setup page click on the Flexible Fields menu.
Change the Event Category to Supplies.
Click on the radio button for FlexibleCodeField3
Double Click Flexible Code Field 3 to edit the value
Feb 2015  63
Select Edit Flexible Field
Enter a value in the Short Name field. This value will then be selected to assign the actual code.
Enter a value in the Long Name field. This is the description.
Caution: Only use the characters A to Z and 0 to 9 in Flexible File names.
Click on the Save button.
Feb 2015  64
Vertex AR Reconciliation Program

Vertex has found that there are instances where the tax amount recorded in Oracle R12 on O2C
transactions does not always match 100% with what was recorded in the Vertex O Series Tax
Journal. These differences could be one of three scenarios:
• The tax posted in Oracle R12 has a different amount than the tax recorded in the Vertex
Tax Journal.
• The Vertex Tax Journal has tax but the corresponding transaction in Oracle R12 does not
exist.
• The Oracle R12 transaction has tax but the transaction does not exist in Vertex.
• The transaction in Oracle R12 is Unposted, but exists in Vertex Tax Journal.
As a result, Vertex created a custom program to identify these variances and provide a
mechanism to synchronize and correct the differences.
Important Note: The comparison does not take into account excluded Receivables transactions.
• Excluded transactions will vary depending on what Event Types have been enabled for
tax calculation by your business or any other Vertex Tax Link setups that would exclude
certain transactions from calling Vertex. Since these transactions do not call Vertex for
tax calculation, the program does not consider them for evaluation.
Feb 2015  65
Overview
Vertex AR Tax Reconciliation compares data stored within Oracle R12, the Vertex Tax
Link tables and the Vertex O Series Tax Journal for determining which transactions are
eligible for adjustment. The program can be run in 2 modes – Preview and Sync.
Preview Mode:- Displays output of all tax variances between Oracle AR and Vertex Tax Journal
for the specified parameters. No updates are made to when run in this mode.
The program output is a report that will group the variances into 3 groups:
• Transactions present in both Oracle R12 and Vertex but with differing tax amounts.
• Transactions present in Vertex but not in Oracle R12.
• Transactions present in Oracle R12 but not in Vertex.
Transactions present in Vertex but not posted in Oracle R12.
Sync Mode:- Vertex Tax Journal is updated to true up to Oracle AR tax data. No changes will be
made to Oracle Receivables tax data.
• For Transactions present in both Oracle R12 and Vertex but with differing tax amounts.
- Transactions are rolled back and recreated in the Vertex Tax Journal with the Oracle
R12 tax amount.
• For Transactions present in Vertex but not in Oracle R12.

- Transactions are rolled back in Vertex Tax Journal.
• For Transactions present in Oracle R12 but not in Vertex.

- Transactions are re-processed into Vertex Tax Journal.
Feb 2015  66
Why Reconciliation is Necessary
During the transaction process a failure could occur in Vertex O Series, Vertex Tax Link or
Oracle that resulted in:
• Transactions present in both Oracle R12 and Vertex but with differing tax
amounts.
Inconsistencies between Oracle R12 and Vertex may result in the tax liability account(s)
within the Oracle General Ledger not supporting the amounts filed on the tax returns
exported from Vertex.
Any variance between these 2 systems could lead to potential audit issues.
It is for these reasons that Vertex strongly recommends this reconciliation process be
run at least once a month.
When to Run
Vertex recommends running this program at least once a month, first in Preview mode
and then again in Sync mode. The ideal time to submit this program would be on the day
the Receivables period is closed. o Best practice is to always run in Preview mode before
submitting Sync, to know which transactions will be updated.
• After the Sync mode completes successfully, it is optional to rerun the program
again in Preview mode to ensure there are no remaining transactions.
• Please refer to the section “Date Range Considerations” for important

information concerning how the GL date is Oracle corresponds to the posting
date in Vertex.
It is also recommended that this Reconciliation Program be run prior to performing a

Vertex O Series Returns Export, since transactions processed during the reconciliation
program will not automatically be moved to the reporting database.
Warning: You should not purge your Vertex O series Tax Journal database. We
recommend you keep at least a full 4 to 6 months in the Vertex Tax Journal for the
reconciliation program to correctly process the transactions between Oracle R12 and
Vertex O Series.
Feb 2015  67
Program Parameters
The Vertex AR Tax Reconciliation process has required parameters and additional optional fields.
Tax Regime Code: This is a required field, providing a lookup to all available tax regimes. The regime is
necessary to ensure that the reconciliation process uses the correct partition within Vertex O Series.
GL Start Date: The earliest GL date on a Receivables invoice that will be viewed during the reconciliation
process. Entered in the format of DD-MMM-YYYY (example: 01-NOV-2012).
GL End Date: The latest GL date on a Receivables invoice that will be viewed during the reconciliation
process. Entered in the format of DD-MMM-YYYY (example: 30-NOV-2012).
Transaction Start Date: The earliest transaction date on a Receivables invoice that will be viewed during
the reconciliation process. Entered in the format of DD-MMM-YYYY (example: 01-NOV-2013).
Transaction End Date: The latest transaction date on a Receivables invoice that will be viewed during the
reconciliation process. Entered in the format of DD-MMM-YYYY (example: 30-NOV-2013), this is an
optional field.
Starting Invoice Number: The first transaction number in a range for the program to process. This is an
optional user entered field.
Ending Invoice Number: The first transaction number in a range for the program to process. This is an
optional user entered field.
Mode: This is a required field, with drop down options of Preview or Sync. In PREVIEW mode, the program
will provide a report of any discrepancies between Oracle and Vertex. To view the report, click on the View
Output button in the Request form. In SYNC mode the program will perform the comparison between
Oracle and Vertex, and make any necessary corrections.
Debug: This is a required field, with drop down options of Yes or No. Setting to Yes will enable debug
logging.
Note: You must enter either a GL Start and End Date or a Transaction Start and End Date.
Feb 2015  68
Recommended parameters if only running the reconciliation process at month-end

• Run the program first in Preview Mode for your specific Tax Regime, specifying a GL date range
encompassing the first day and last day of the month that was just closed. Specify an invoice
number range only if it is applicable to your business.
• Once the program completes, review the report output (found within the Concurrent Request
manager under “View Output”). This report will list the transactions that will be updated within
the Vertex tax Journal.
• Please refer to the section “Date Range Considerations” for important information concerning
how the GL date in Oracle corresponds to the posting date in Vertex.
• Submit the program again but in Sync Mode for your specific Tax Regime, specifying a GL date
range encompassing the first day and last day of the month that was just closed. Specify an
invoice number range if it is applicable to your business.
Date Range Considerations

IMPORTANT NOTE CONCERNING GL DATE RANGE: The GL Date parameters restrict the reconciliation
program to only evaluate Oracle R12 Receivables transactions with a GL date within the range submitted.
This GL Date may not correlate directly to a specific date within the Vertex Journal depending on your
business Vertex Tax Link setups. o The date parameters passed will equate to the Posting Date in the
Vertex Journal.
• However, the Oracle date your business mapped to the Posting date could vary from the GL date.
It is possible that the document date or creation date could have been used. It is important to
know how your business has enabled this date mapping.
• The impact is transactions could be listed as only existing in Oracle or only existing in Vertex,
when in fact they do exist in both systems. Examples below.
If the GL date is mapped as the posting date in Vertex, then the reconciliation program would be
comparing like data. Example:
st th
• A Receivables invoice is entered on February 1 and it has an invoice date of January 15 and a
st
GL date of January 31 .
st
 The posting date in the Vertex Journal will be January 31 .
th
 The tax date in Vertex used for calculating the tax rate will be January 15 .
st
 The transaction processing date will be listed as February 1 .
st st
• When the reconciliation program is run with a GL date range of January 1 to January 31 , this
invoice would be found in both Oracle R12 and the Vertex Journal and the tax amounts would be
processed to look for tax variances.
If another date in Oracle (such as the invoice creation date) has been mapped as the Vertex posting date,
then the possibility exists that transactions could be picked up as having a variance when in fact they do
not. Example:
st th
• A Receivables invoice is entered on February 1 and it has an invoice date of January 15 and a
st
GL date of January 31 .
st
 The posting date in the Vertex Journal will be February 1 .
th
 The tax date in Vertex used for calculating the tax rate will be January 15 .
st
 The transaction processing date will be listed as February 1 .
Feb 2015  69
st st
• When the reconciliation program is run with a GL date range of January 1 to January 31 , this
invoice would be found to only exist in Oracle R12 and not the Vertex Journal. If the program is
then run in Sync mode for this date range, an attempt will be made to insert this invoice into the
Vertex Journal. This could result in invoice duplication within Vertex.
• In this same invoice example, had the reconciliation program be submitted with a GL date range
th
of February 1 to February 28 , this invoice would be found to only exist in the Vertex Journal and
not Oracle R12. If the program is then run in Sync mode for this date range, the invoice would be
rolled back (inactivated) in the Vertex Journal.
For businesses that have mapped something besides the GL date as the Vertex posting date, the
reconciliation program is still a valuable tool. However, considerations need to be made when reviewing
the output from the Preview mode before running the Sync.
• If the Preview mode lists invoices as either existing in one system but not the other, whether it be
transactions present in Vertex but not in Oracle R12 or transactions present in Oracle R12 but not
in Vertex, further research should be done by the user before submitting in Sync mode.
• One option would be to run the program in Preview mode with no date range but enter
the invoice number in both the starting and ending Invoice Number parameter. This
removes any date constraints.
 If the Preview mode still returns the invoice, this will confirm it as a true
variance.
 However, if the invoice is not returned it would indicate the transaction does
exist in both systems with like tax.
• Another option would be to examine the other applicable dates for those transactions.
 If creation date or document date is what is mapped as the posting date,
confirm that this date also falls within the parameter date range.
 If this date falls outside of the parameter date range, further analysis should be
done to determine if a tax variance exists.
Vertex AR Tax Reconciliation process Functionality

In Preview mode, this program will provide reporting only. All tax transactions with discrepancies
between Oracle R12 and the Vertex Tax Journal for the specified parameters will be listed.
• Transactions present in both Oracle R12 and Vertex but with differing tax amounts.
• Transactions present in Vertex but not posted in Oracle R12
In Sync mode, this program updates the transaction data in the Vertex Tax Journal and the output will
reflect if the updates were successful or if errors were encountered.
• For transactions that are present in both Oracle R12 and Vertex but with differing tax amounts,
corrections are processed in the Vertex O Series Tax Journal using a combination of Vertex O
Series Rollback and Distribute Tax messages. The end result is the Vertex transactions are
updated to reflect the amounts found in Oracle R12.
• For those transactions in Vertex but not in Oracle R12, the transaction is inactivated in Vertex
Journal using the Vertex O Series Rollback message. The end result is the transactions would be
excluded from the Vertex Tax Journal.
• For transactions in Oracle R12 but not in Vertex, the transactions are reprocessed into the Vertex
Journal using the Vertex O Series Distribute Tax message. The end result is the missing
transactions now exists in Vertex and have amounts that correspond to Oracle R12.
Feb 2015  70
Vertex AR Tax Reconciliation process - Report Output

Vertex Receivables Journal Reconciliation Report Run Date: 10-OCT-2013
Tax regime: VERTEX TEST REGIME

GL Start Date: 01-OCT-2013 GL End Date: 01-OCT-2013
Trx Start Date: Trx End Date:
Start Trx#: End Trx#:
Mode: PREVIEW
Transactions with different tax amount in Vertex Journal:
Transaction Number Transaction Date Oracle Tax Amt Vertex Tax Amt
------------------ ---------------- -------------- --------------
502563 10-OCT-2013 800.00 700.00
Mismatch Transaction count: 1
Additional Transactions in Vertex Journal:
Transaction Number Transaction Date Tax Amount

------------------ ---------------- -------------
987654 10-OCT-2013 6.00
Additional transactions in Vertex Journal count: 1
Additional Transactions in Oracle but not in Vertex Journal:
Transaction Number Transaction Date Tax Amount

------------------ ---------------- -------------
502543 03-OCT-2013 8.00
Additional Transactions in Oracle but not in Vertex Journal count: 1
Additional Transactions Unposted in Oracle existing in Vertex Journal:
Transaction Number Transaction Date Oracle Tax Amt Vertex Tax Amt
------------------ ---------------- -------------- --------------
18673 02-OCT-2013 200.00
18674 03-OCT-2013 5000.00
18680 03-OCT-2013 -8.00
212 02-OCT-2013 300.00
502544 13-SEP-2013 80.00
502545 04-OCT-2013 -80.00
502563 10-OCT-2013 800.00
Additional Transactions Unposted in Oracle existing in Vertex Journal count: 7
*** End of Report ***
This program will contain the following information in the header section of the report output
• Run date
• Parameter values entered
Detail Section of the report is split into 3 sections:

• Transactions with different amount in Vertex Journal
• Additional Transactions with Vertex Journal
• Additional Transactions in Oracle but not in Vertex Journal
• Additional Transactions unposted in Oracle existing in Vertex Journal (Preview only)
Transaction Date, Number, Oracle Tax Amount and Vertex Tax Amount are common for all sections in
Preview mode.
In addition to the sections and fields mentioned in the Preview Mode, the Sync mode has two additional
fields: Processed – Yes / No and Error- Displays an error message only if the Processed status is No.
Feb 2015  71
Known Limitation of Reconciliation Program

The Vertex Reconciliation cannot correct transactions that have duplicate records in the Vertex Tax Journal
with the same LINEITEMSYNCIDCODE. If facing this issue, contact Vertex Product Support Toll Free number
at 1-800-281-1900 (available M-F 8:15am - 8:00pm EST). You can also log requests online at
https://my.vertexinc.com.
Feb 2015  72
Standard order to cash Vertex / Oracle EBtax field mapping
Oracle Description Vertex OIC Vertex O Series

Header Level Tax Calculation Values
legal_entity_number Legal entity is a legally recognized SELLER_LEGAL_ENTITY Taxpayer
party with given rights and
responsibilities by legislation.
transaction_id Primary transaction identifier that TRANSACTION_ID TransactionId

distinguishes a
transaction/document uniquely in
the context of a document type.
trx_date Transaction date. DOCUMENT_DATE DocumentDate
gl_date General Ledger Date POSTING_DATE PostingDate
Header Level Reporting Attributes

transcation_number Transaction number of the DOCUMENT_NUMBER Invoice Number
transaction header, typically the
number that enables a user to
identify and report a specific
transaction. This value by itself does
not identify a transaction uniquely in
Oracle E-Business Suite. This is for
use in reports only.
Line Level Tax Calculation Values
transaction_line_id Primary transaction line identifier LineItemId

that recognizes a transaction line
uniquely within a transaction. LINE_ITEM_ID
transaction_line_date Date for the transaction line. TAX_DATE TaxDate
line_amount Transaction line amount. EXTENDED_PRICE ExtendedPrice
line_intended_use The purpose for which an USAGE_CODE Usage

item/product may be used.
Values for this attribute are
defined by the user.
transaction_line_quantity Transaction line quantity. QUANTITY Quantity
exempt_certificate_number Tax exemption certificate EXEMPTION_CERTIFICATE_NUMBER Exemption

number.
CertificateNumber
Feb 2015  73

exempt_reason Tax exemption reason. CUSTOMER_EXEMPT_REASON_CODE Exempt ReasonCode
uom_code Unit of measure code UNIT_OF_MEASURE UnitOfMeasure
product_code Inventory item code. PRODUCT_CODE ProductCode
Bill_to_party_id The name of the party that CUSTOMER_MAIN_CODE CustomerCode

receives products and/or services
listed on the invoice or order.
ship_to_geography_value1 The address element value DEST_COUNTRY Destination Country

belonging to the geography
type1 of the ___location that
receives the shipment.
ship_to_geography_value2 The address element value Destination

DEST_MAIN_DIVISION
MainDivision

DEST_SUB_DIVISION
Subdivision

DEST_CITY
City

type5 of the ___location that DEST_POSTAL_CODE PostalCode
ship_from_geography_value1 The address element value PhysicalOrigin Country

type1 of the ___location from which PHYS_ORIGIN_COUNTRY
the shipment is made.
ship_from_geography_value2 The address element value PhysicalOrigin

type2 of the ___location from which PHYS_ORIGIN_MAIN_DIVISION MainDivision
the shipment is made.
Feb 2015  74

type3 of the ___location from PHYS_ORIGIN_SUB_DIVISION Subdivision
which the shipment is made.

type4 of the ___location from PHYS_ORIGIN_CITY City
ship_from_geography_value5 The address element value Physicalorigin

type5 of the ___location from PHYS_ORIGIN_POSTAL_CODE PostalCode
poa_geography_value1 The address element value AdministrativeOrigin

type1 of the ___location of the ADMIN_ORIGIN_COUNTRY Country
party that accepts an order for

products and/or services.

ADMIN_ORIGIN_MAIN_DIVISION MainDivision
type2 of the ___location of the
poa_geography_value3 The address element value Administrativeorigin

ADMIN_ORIGIN_SUB_DIVISION Subdivision

type4 of the ___location of the ADMIN_ORIGIN_CITY City


ADMIN_ORIGIN_POSTAL_CODE PostalCode
Feb 2015  75

line_char1 For tax partner use only FlexibleCodeField1
FLEX_CODE_1
line_char2 For tax partner use only FlexibleCodeField2

FLEX_CODE_2
line_char3 For tax partner use only FLEX_CODE_3 *Reserved by Vertex FlexibleCodeField3
line_char4 For tax partner use only FLEX_CODE_4 FlexibleCodeField4
line_char16 For tax partner use only CUSTOMER_CLASS_CODE CustomerClassCode
line_char17 For tax partner use only PRODUCT_CLASS ProductClass
line_char18 For tax partner use only USAGE_CLASS_CODE UsageClass
line_char19 For tax partner use only STORE_LOCATION_CODE LocationCode
Feb 2015  76

line_numeric1 For tax partner use only FLEX_NUMERIC_1 FlexibleNumericField1
line_date1 For tax partner use only FLEX_DATE_1 FlexibleDateField1
Note: FlexibleCodeField3 is reserved by the Vertex Tax Link for instance_name.
Feb 2015  77
Configuring SSL with Vertex O Series On Premise

Solution (Local installation)
The Tax Link may be configured for SSL communication with Vertex O Series Web Services utilizing the
Oracle Wallet Manager and the capabilities of the Oracle package UTL_HTTP.
Use the script file vertex_oic_set_wallet.sql to set the configuration values for the Oracle Wallet Path and
Oracle Wallet Password. Setting these values enables SSL. Setting them to NULL disables SSL.
• Setup the application hosting O Series Web Services for SSL support
• Setup an Oracle Wallet with the proper certificates using Oracle Wallet Manager
• Sign on to SQL*Plus as the user with access to the proper schema and the permissions that
were listed above.
• Once in SQL*Plus execute the vertex_oic_set_wallet.sql script located in the
/vertex_p2p_db/vertex_o_series_integration/oic/utils directory to enable SSL.
1. On EBS DB tier run following query to determine where the two wallet files need to be copied.
select fnd_profile.value('FND_DB_WALLET_DIR') from dual;
2. Change to directory: /vertex_p2p_db/vertex_o_series_integration/oic/utils
3. Log into sqlplus as tax link custom schema user (i.e. XXVERTEX) and run following sql
SQL> @ vertex_oic_set_wallet.sql
Parameters:
1. Wallet Path - The path to the Oracle Wallet Folder in the form ‘file:<directory path>’
Example:
UNIX: file:/home/oracle/1203/appsutil/wallet
2. Wallet Password – The password established in Oracle Wallet Manager
Note: To Disable SSL, set both values to NULL (hit return at each prompt)
Feb 2015  78
Testing DB to TCPIP / HTTPS Connectivity

Vertex provides several test procedures to test connectivity between the Vertex OIC (database level) and
Vertex O Series (Application level)
First you will need to update the Vertex_OIC_Configuration table with the following entries:
SERVICE_END_POINT: This is the URL for the Vertex OnDemand web service
(https://yourcompanyname.ondemand.vertexinc.com/vertex-ws/services/
USERNAME: This is one a USERNAME that is active and valid in Vertex Central UI
PASSWORD: This is the PASSWORD which corresponds to the USERNAME entered above
DEBUG_MESSAGES: This should be set to T in order to capture XML requests and Responses in test
environments.
SERVICE_END_POINT USERNAME PASSWORD DEBUG_MESSAGES
https://company.ondemand.vertexinc.com/vertex-
ws/services/ Username {Password} T
Update script
UPDATE VERTEX_OIC_CONFIGURATION
SET SERVICE_END_POINT = ‘https://company.ondemand.vertexinc.com/vertex-ws/services/’,
USERNAME = ‘{username}’, PASSWORD = {Password}, DEBUG_MESSAGES = ‘T’;
Commit;
Feb 2015  79
Executing Sample Tests:

After you have updated the Vertex OIC Configuration table, you can now test the connection by running
one or more of the Vertex OIC Test Procedures.
Note: Do not Use the Vertex default sysadmin/vertex username and password. These values are not
usually available for Vertex OnDemand customers.
O2C Customers
Log into SQLPLUS as tax link custom schema user (i.e. XXVERTEX)
SQL>set serveroutput on;
SQL>exec VERTEXOICQUOEXAMPLE(‘SALE’, 1);
Expected Output
********************************************************************************
Quotation: SALE request was successfully processed.
********************************************************************************
Document Number:
Document Date: 21-APR-04
Transaction ID: T101
Trans Total Amt: 1.8
Line Item Number: 1
Total Tax: 1.8
Tax Type: SALES
Calculated Tax: 1.8
PL/SQL procedure successfully completed.
Feb 2015  80
Common Errors:
Issue: Error during sending of XML request document.:ORA-29273: HTTP request failed
ORA-06512: at "SYS.UTL_HTTP", line 1130
ORA-29248: an unrecognized WRL was used to open a wallet
Process exited.
Possible Solutions:
Verify the WRL_TYPE = file
Check the WRL_TYPE using the following: select * from v$encryption_wallet;
WRL_TYPE WRL_PARAMETER STATUS

file /ora/dev1/db/tech_st/12.2.0.2/admin/dev1/wallet CLOSED
Verify Wallet_Path within Vertex_OIC_Configuration
Select WALLET_PATH from vertex_oic_cofiguration;
Issue: Error during sending of XML request document.:ORA-29273: HTTP request failed
Verify Wallet Password is valid
Feb 2015  81
Encrypting Passwords
It is possible for the Vertex O Series passwords to be encrypted for use in the Vertex Tax Link
Regime User table using the encryption utility provided by Vertex as part of the Vertex O Series
installation. The utility can be found in the VertexRoot / lib directory. You can also refer to the Vertex O
Series Administration Guide section: Security-related components outside Vertex O Series available from
the https://My.Vertexinc.com.
Encrypting user names and passwords using the Command line
If you want to pass encrypted user names and/or passwords to any Command line utilities, or for use
with Vertex Web services, use the encryption Command line utility to perform your encryption. This
utility is contained within the vertex_util.jar file, which can be found in the Vertex Home/lib directory.
You can encrypt multiple pairs of user names and passwords each time you use the encryption utility.
User names and passwords must be separated by a single space.
Encrypting user names and passwords
Complete the following steps to run the Command line encryption utility:
1. Access the Command line.
2. Enter the following and then press Enter:
runEncryptUtil username1 password1 username2 password2 usernameN passwordN
where:
username1 is the username1 to be encrypted
password1 is the password1 to be encrypted
username2 is the username2 to be encrypted
password2 is the password2 to be encrypted
usernameN is the usernameN to be encrypted
passwordN is the passwordN to be encrypted
Feb 2015  82

Vertex O2C Tax Link For Oracle R12 Integration Guide

Uploaded by

Vertex O2C Tax Link For Oracle R12 Integration Guide

Uploaded by

Integration Guide

Vertex® O2C Tax Link for Oracle R12

Trademarks and Service Marks

Third Party Products

Vertex corporate offices ......................................................................................................................... v

Vertex Services and Products ................................................................................................................ vi

About this guide ................................................................................................................................... viii

Purpose ................................................................................................................................................ viii

Scope ............................................................................................................................................. viii

Configuration and Installation .......................................................................................................... 4

R12.2 Additional Permissions .........................................................................................................13

Loading O2C Objects Using FNDLOAD ............................................................................................22

Applying Vertex Tax Link 7.x TAID / RTAID Patch: ................................................................................24

Applying Vertex Tax Link 7.x AR Recon Patch: ......................................................................................24

Importing the ORAMAST file ..........................................................................................................25

Feb 2015  iii 3/13/2015

Configuring EBTAX ................................................................................................................................26

Configuration overview ..................................................................................................................26

Setting the username and password for webservice XML .............................................................60

Testing DB to TCPIP / HTTPS Connectivity......................................................................................79

Encrypting Passwords ...........................................................................................................................82

Vertex corporate offices

Global headquarters European headquarters

1041 Old Cassatt Road Vertex Global Tax Solutions, LTD

Sarasota office Tax Returns processing center

101 Arthur Andersen Parkway 40 Shuman Blvd.

Vertex Services and Products

For assistance with... Contact...

Up-to-the-minute information Vertex Critical Changes page

Questions about your licensing Vertex Account Services

Purchasing Vertex services and Vertex Global Headquarters

Vertex European Headquarters

Regional training classes, Web- Vertex Training

Feb 2015  vii

About this guide

Chapter 2. Configuration and Installation

Feb 2015  viii

Vertex Tax Links for R12

Feb 2015  1 3/13/2015

The data flow between Oracle R12 and O Series

Tax Link functionality

Tax Link components

Vertex R12 Link component

Installing Vertex Tax Link for Oracle R12 ...……………………...…. 8

Importing ORAMAST file …….. ... …………………………….……… 14

Configuring EBTAX.. ...... …………………………………………….…. 15

Submitting requests .. …………………….……………………….……. 51

Standard order to cash Vertex/Oracle EBtax field mapping….………56

Feb 2015  4 3/13/2015

Oracle Patch Description

Configuring Tax Regime

Setting up the Operating Unit/Legal Entity and Service Subscription

6. Click Service Subscription.

Delete Service Mappings

1. Click on Home and then Provider Services.

2. Search for Vertex Inc and click Go.

3. Three records display. Delete each record by selecting one at a time.

Registering Custom Application

This screen shot is for reference.

Installing Vertex Tax Link for Oracle R12

The Vertex OIC objects

Database Tier Installation Section

2. Type tar –xvf vertex_o2c_db_5.1.10.15.02.tar.

Creating a custom user

1. Change the directory to /vertex_o2c_db/code/scripts.

Grants for Existing user

GRANT ALTER ANY PROCEDURE TO &&username;

GRANT CREATE ANY INDEX TO &&username;

GRANT CREATE ANY PROCEDURE TO &&username;

GRANT CREATE ANY SYNONYM TO &&username;

GRANT CREATE ANY TABLE TO &&username;

GRANT CREATE SEQUENCE TO &&username;

GRANT CREATE SESSION TO &&username;

GRANT CREATE TRIGGER TO &&username;

GRANT CREATE VIEW TO &&username;

GRANT "CONNECT" TO &&username;