Treasury Setup Checklist

Setting Up Oracle Treasury

This section contains a checklist for use when installing and setting up your Oracle Treasury (Treasury)
system.

Before you set up Treasury, perform the following task:

 Set up Oracle Application responsibilities and users for the implementation. You must set up the
Treasury Superuser responsibility to implement Treasury. See: Defining a Responsibility, Oracle E-
Business Suite System Administrator's Guide.

Treasury provides these responsibilities:

 Treasury Foreign Exchange Dealer. This responsibility allows the user to access foreign exchange
and basic money market deal types, as well as view position windows and market data.
 Treasury Money Market Dealer. This responsibility allows the user to access all money market
deal types, as well as view position windows and market data.
 Treasury Equity Market Dealer. This responsibility allows the user to access all equity market
transaction types, as well as view position windows and market data.
 Treasury Dealer. This responsibility allows the user to access all deal types, as well as view
position windows and market data.
 Treasury Settlements Administrator. This responsibility allows the user to process deal
settlements, reconcile bank statements, generate accounting entries, perform limited setup functions,
and view position windows and market data.
 Treasury Hedging Manager. This responsibility allows the user to access hedging windows and
deal types available as hedging instruments, as well as view position windows and market data.
 Treasury Inquiry. This responsibility allows the user to access all Treasury data in view-only mode.
 Treasury Back Office Administrator. This responsibility allows the user to process deal
settlements, reconcile bank statements, generate accounting entries, perform limited setup functions,
and view position windows and market data.

The bank statement reconciliation and clearing functionality under this responsibility come from
Oracle Cash Management. Please refer to the Oracle Cash Management User Guide for more
information.

 Treasury Cash Manager. This responsibility allows the user to access cash positioning and cash
forecasting windows, as well as the cash management related deal types.

The cash positioning, cash forecasting, and bank statement interface functionality under this
responsibility come from Oracle Cash Management. Please refer to the Oracle Cash Management
User Guide for more information.

 Treasury Middle Office Administrator. This responsibility allows the user to access calculators
and risk management tools, as well as view all Treasury data.
 Treasury Setup Administrator. This responsibility allows the user to access all functional setup in
Oracle Treasury.
 Treasury Superuser. This responsibility allows the user to access all functionality in Oracle
Treasury.
 Treasury, Cash and Risk Management Superuser. This responsibility allows the user to access all
functionality in Oracle Treasury, Oracle Cash Management and Oracle Risk Management.
 Please refer to the Oracle Cash Management User Guide for information about using Oracle Cash
Management. Please refer to the Oracle Risk Management User Guide for information about using
Oracle Risk Management.

If you want to use the Oracle E-Business Suite Multiple Organizations Support Feature with Treasury,
additional setup steps are required. For detailed information on setting up Treasury for multiple
organizations, see: Multiple Organizations in Oracle E-Business Suite.

Related Product Setup Steps

The following steps may need to be performed to implement Treasury. These steps are discussed in detail in
the Setting Up sections of other Oracle product user guides. The following tables list the setup steps

Set Up Underlying Oracle E-Business Suite Technology

See the Oracle E-Business Suite System Administrator's Guide to complete other setup steps, including:

 performing system-wide setup tasks such as configuring concurrent managers and printers
 managing data security, which includes setting up responsibilities to allow access to a specific set of
business data and complete a specific set of transactions, and assigning individual users to one or
more of these responsibilities.

General Ledger Setup Steps

See Setting Up Oracle General Ledger, Oracle General Ledger User Guide to complete the following setup
steps.

Step
Step
Number
Step 1 Define your chart of accounts.
Step 2 Enable the currencies that you plan to use.
Step 3 Define your accounting period types and accounting calendar periods.
Step 4 Define a ledger. Specify the name for the ledger and assign it a calendar, ledger currency,
and a chart of accounts structure.
Step 5 If you want to enter foreign currency transactions, define your additional rate types.
Step 6 Define a transaction calendar to determine which days are business days to be used in
cash forecasting.

Multiple Organization Support Setup Steps

Use the Setting Up Multiple Organizations section in Multiple Organizations in Oracle E-Business Suite to
complete the following setup step.

Step Number Step

Step 1 Define the legal entities for your companies.

Oracle Workflow Setup Steps

Use the Setting Up Oracle Workflow section in the Oracle Workflow User Guide to complete the following
setup step.

Step Number Step

Step 1 If you want to use the Limits Notification workflow process, then set up Oracle
Workflow.

Setup Flowchart
Some of the steps outlined in this flowchart and setup checklist are Required and some are Optional. Some
optional steps have default values that are pre-seeded in the database; however, you should review those
defaults and decide whether to change them to suit your business needs. If you want or need to change them,
you should perform that setup step. You need to perform Optional steps only if you plan to use the related
feature or complete certain business functions.
Treasury Setup Checklist
The following table lists the Treasury setup steps and whether the step is optional or required. After you log
on to Oracle E-Business Suite, complete these steps to implement Treasury.

Some steps build upon information defined in other steps, so you must perform them in the order listed.

Step
Required? Step Description Window Name(s)
Number
Step 1 Required Create application user sign-ons and passwords. System Administrator
Context: Perform this step once per installation. responsibility:
See: Users Window, Oracle E-Business Suite System Users
Administrator's Guide or online help.
Step 2 Required Define your chart of accounts. General Ledger
Context: Perform this step once per installation. responsibility:
See: Defining Your Chart of Accounts and Defining Your multiple windows
Account Structure Oracle General Ledger User Guide or
online help.
Step 3 Required Define your accounting period types and accounting General Ledger
calendar periods. responsibility:
Context: Perform this step once per installation. Period Types,
See: Defining Period Types and Defining Calendars Accounting Calendar
Oracle General Ledger User Guide or online help.
Step 4 Required Enable the currencies that you plan to use. General Ledger
Context: Perform this step once per installation. responsibility:
See: Defining Currencies, Oracle General Ledger User Currencies
Guide or online help.
Step 5 Required Define a ledger. Specify the name for the ledger and General Ledger
assign it a calendar, ledger currency, and a chart of responsibility:
accounts structure. (Define) Ledger
Context: Perform this step once per installation.
See: Defining Ledgers, Oracle General Ledger User
Guide or online help.
Step 6 Required If you want to enter foreign currency transactions, General Ledger
define your additional rate types. responsibility:
Context: Perform this step once per installation. Conversion Rate Types
See: Defining Conversion Rate Types and Entering Daily
Rates, Oracle General Ledger User Guide or online help.
Step 7 Required Use the System Administrator responsibility to set the System Administrator
GL Ledger Name profile option. responsibility:
Context: Perform this step once per installation. System Profile Values
See: Overview of User Profiles and Setting User Profile
Options, Oracle E-Business Suite System Administrator's
Guide or online help.
Step 8 Optional Define a transaction calendar to determine which days General Ledger
are business days to be used in cash forecasting. responsibility:
Context: Perform this step once per installation. Transaction Calendar
See: Defining Transaction Calendars, Oracle General
Ledger User Guide or online help.
Step 9 Required Define the legal entities for your companies. Organization
Context: Perform this step once per business group.
See: Implementing Multiple Organization Support,
Multiple Organizations in Oracle E-Business Suite.
Step 10 Required Define your user access levels. User Access Levels
Context: Perform this step once per installation.
See: User Access Levels
Step 11 Required Define your system parameters. System Parameters
Context: Perform this step once per installation.
Defaults: Each parameter has a default value. See the
System Parameters section for a detailed description of the
parameters and their default values.
See: System Parameters
Step 12 Required Define your currency details. Currency Details
Context: Perform this step once per installation.
See: Currency Details
Step 13 Required Define your counterparty profiles. Counterparty Profiles
Context: Perform this step once per installation.
See: Counterparty Profiles
Step 14 Required Define your company profiles, including the accounting Company Profiles
process that you want to use for your company.
Context: Perform this step once per installation.
See: Company Profiles
Step 15 Required Run the Cash Management Security Wizard
Step 16 Required Banks, Bank Branches and Bank Accounts
Step 17 Required Define your deal types/product types. Deal Types/Product
Context: Perform this step once per installation. T+ypes
See: Deal Types and Product Types
Step 18 Required Assign companies to and authorize deals for your users. User Access Levels

Context: Perform this step once per installation.

See: User Access Levels
Step 19 Optional Define your currency holiday rules. Currency Holiday
Context: Perform this step once per installation. Rules
See: Currency Holiday Rules
Step 20 Required Define your portfolios. Portfolio Codes
Context: Perform this step once per installation.
See: Portfolio Codes
Step 21 Optional If you want to use journals with Treasury, you must Journal Entry Actions
define your journal entry actions.
Context: Perform this step once per installation.
See: Journal Entry Actions
Step 22 Optional Define your audit requirements. Audit Requirements
Context: Perform this step once per installation.
See: Audit Requirements
Step 23 Optional If you want to buy or sell equities, you must define your Stock Issues
stock issues.
Context: Perform this step once per installation.
See: Stock Issues
Step 24 Optional If you want to buy, issue, or sell fixed income securities, Bond Issues
you must define your bond issues.
Context: Perform this step once per installation.
See: Bond Issues
Step 25 Optional If you want to issue fixed income securities, define your Bill/Bond Issue
bill/bond issue numbers. Numbers
Context: Perform this step once per installation.
See: Bill/Bond Issue Numbers
Step 26 Required Define your exposure types. Exposure Types
Context: Perform this step once per installation.
See: Exposure Types
Step 27 Optional If you want to enter into deals for hedging purposes, Hedge Policies and
perform the necessary setup for hedging. Hedge Strategies
Context: Perform this step once per installation.
See: +Hedging
Step 28 Optional Define your settlement accounts. Default Settlement
Context: Perform this step once per installation. Accounts
See: Default Settlement Accounts
Step 29 Optional Define your default settlement actions. Settlement Actions
Context: Perform this step once per installation.
See: Settlement Actions
Step 30 Optional Define your party groups. Party Group Codes
Context: Perform this step once per installation.
See: Party Groups
Step 31 Required Define “CE: Bank Account Transfers” System Profile
Step 32 Optional Define your notional cash pools. Notional Cash Pools
Context: Perform this step once per installation.
See: Cash Leveling, Oracle Cash Management User
Guide.
Step 33 Required Define your deal rate tolerances. Deal Rate Tolerances
Context: Perform this step once per installation.
See: Deal Rate Tolerances
Step 34 Optional Define your interest rate policies. Interest Rate Policies
Context: Perform this step once per installation.
See: Interest Rate Policy
Step 35 Optional If you want to use limit checking in Treasury, you must Limits
define your limits policy.
Context: Perform this step once per installation.
See: Limits
Step 36 Optional Define your deal confirmation groups. Deal Confirmation
Context: Perform this step once per installation. Groups
See: Confirmation Groups
Step 37 Optional If you want to use Treasury to generate deal Confirmation
confirmations, you must define your deal confirmation Templates and User
template. Views
Context: Perform this step once per installation.
See: Confirmation Template
Step 38 Optional If you want to reconcile your bank statements in Import Sources
Treasury, you must define your import sources.
Context: Perform this step once per installation.
See: Import Sources and Reconciliation
Step 39 Optional If you want to create payment schedules for your retail Payment Schedules
term money deals, you must define your payment
schedules.
Context: Perform this step once per installation.
See: Payment Schedules
Step 40 Optional Define your brokerage schedule and details. Brokerage Schedule &
Context: Perform this step once per installation. Details
See: Brokerage Schedule and Details
Step 41 Optional Define your tax schedule and details. Tax Schedule &
Context: Perform this step once per installation. Details
See: Tax Schedule and Details
Step 42 Optional Define your current system rates. Current System Rates
Context: Perform this step once per installation.
See: Current System Rates
Step 43 Optional If you want to theoretically price or revalue deals, you Market Data Curves
must define your market data curves and market data Market Data Sets
sets.
Context: Perform this step once per installation.
 See: Market Data Curves and Market Data Sets
Step 44 Optional Define your system languages. System Languages
Context: Perform this step once per installation.
See: System Languages
Step 45 Optional Define your request sets. Request Set
Context: Perform this step once per installation.
See: Request Set Windows, Oracle E-Business Suite User
Guide or online help.
Step 46 Optional Define your descriptive flexfields. System Administrator
Context: Perform this step once per installation. responsibility:
See: Defining Descriptive Flexfields, Oracle E-Business multiple windows
Suite Flexfields Guide or online help.
Step 47 Optional If you want to use the Limits Notification workflow System Administrator
process, then set up Oracle Workflow. responsibility:
Context: Perform this step once per installation. multiple windows
See: Setting Up Oracle Workflow, Oracle Workflow User
Guide or online help.

System Setup
This section contains information that you need to set up the system-related aspects of Treasury. It includes
information for setting up system parameters, user access, and other general codes and options.

Currency Holiday Rules

Holidays can significantly affect the timing of your deal cashflows. If you enter into a deal that has a start,
maturity, or settlement date that falls on a holiday, your company's deal cashflow could be delayed by one or
more days because banks, brokerages, or counterparty offices are closed. To prevent your company from
dealing with delayed cashflows, use the Currency Holiday Rules window to define the holiday dates for
each of your authorized currencies.

Once you define your currency holidays, Treasury automatically checks the start, maturity, and settlement
dates for each deal against the holiday dates for each currency in the deal. If any deal dates fall on a holiday,
you receive a warning, which you can dismiss. The warning does not prevent you from entering the deal, but
it does remind you that the deal date can impact your company's cashflow.

In Treasury, you can define three types of holidays:

 Constant holidays: Holidays that occur on a fixed date. For example, in countries using USD, New
Year's Day is always on January 1.
 Rule holidays: Holidays that change from year to year based on a rule. For example, in countries
using USD, Labor Day is always the first Monday in September.
 One off holidays: Holidays that occur one time only. For example, in countries using GBP, the
government may declare a holiday to celebrate the coronation of a new king or queen.

Once you define a constant or rule holiday, the date of that holiday is automatically calculated five years
into the future from the current system date. For example, if you define a constant holiday for January 1,
2000, a holiday is automatically created for each January 1 between 2001 and 2004. If you want to calculate
the holiday more or less than five years into the future, in the Calculated Date field you can enter another
date to which you want the holiday calculated (for example, January 1, 2003). The holiday dates are
calculated up to the date you specify.
In Treasury, Saturday and Sunday are considered non-business days. If a holiday falls on a Saturday or a
Sunday, the holiday automatically moves to the following Monday. You must edit the calculated holiday
dates to accommodate your specific workday adjustments. For example, if you want to move a holiday to
the preceding Friday instead of the following Monday, you must edit the date of the calculated holiday
accordingly.

Some rule-based holidays, such as those based on the phases of the moon, cannot be calculated and must be
defined as a unique, one off, holidays.

GL Calendar

Use the (General Ledger) Transaction Calendar window to define any day of the week as a non-business
day. For more information on defining a transaction calendar, see Oracle General Ledger User Guide.

Once you define a GL calendar, you can import the GL calendar into Treasury. Importing the GL calendar
lets you use the holidays that have already been defined in General Ledger so you don't have to define the
holidays again in Treasury.

To import the GL calendar into Treasury

1. Navigate to the Currency Details window.

2. Assign the GL calendar to a currency. Treasury uses the weekend definition of the GL calendar
instead of assuming Saturday/Sunday weekend days.

Once you assign a GL calendar to a currency, you have the option to import holidays from the GL
calendar associated with that currency into the Holiday Dates window. This option is only available
if a GL calendar is assigned to the currency.

3. Navigate to the Currency Holiday Rules window.

4. Select the currency that you want to import holidays into.
5. Choose the Review Actual Holiday Dates button.

The Holiday Dates window appears.

6. Choose the Import GL Holidays button.

Defining Currency Holiday Rules

Use the Currency Holiday Rules window to define the holiday rules for each of your authorized currencies.

To define a holiday for a currency

1. In the Currency Holiday Rules window, choose a currency for the holiday that you want to define.
2. In the Description field, enter a description for the holiday.
3. In the Type field, choose a holiday type and do the following:
o If you choose the Constant holiday type, in the Date field enter a holiday date and in the
Month field choose a month. If the holiday is observed for more than one day a year, in the
Extra Days field enter the number of additional days that the holiday is observed.
o If you choose the Rule holiday type, do the following:
 In the Month field, choose the month for the holiday.
 In the Num field, enter the week of the month for the holiday. For example, if the
holiday occurs in the third week of the month, enter 3.
 In the Day field, enter the day of the week that the holiday falls on.
 In the Extra Days field, enter the number of additional days, if any, that the holiday is
observed.
  If the holiday occurs on a weekend, but is observed on a business day, enter the day of
the week that the holiday is observed in the Wkd Adj field.
o If you choose the One-Off holiday type, enter the date, month, and year of the holiday. If the
holiday is observed for more than one day, in the Extra Days field enter the number of
additional days that the holiday is observed.
4. If you want to calculate the future date of the holiday to a specific date, in the Calculated Date field
enter the date. If you do not enter a date, Treasury automatically calculates the holiday date five
years into the future from the current system date.
5. Review the list of calculated dates for the holiday by choosing the Review Actual Holiday Dates
button. The Holiday Dates window appears.
6. If you want to adjust a holiday date (for example, to move a holiday from a Monday to the preceding
Friday), in the Date field adjust the holiday dates as needed.
7. If you want to import holidays from the GL calendar assigned to that currency into the Holiday Dates
window, choose the Import GL Holidays button. For more information, see GL calendar.
8. Save your work.

Portfolio Codes
Use portfolios to group your deals according to deal activity or according to your company accounting or
reporting structure. For example, you might create a portfolio for the following deal activities: operating,
service, capital, trading, equities, and hedging.

You must create at least one portfolio for each company that you set up.

Portfolios are essential to the Treasury accounting structure. For each portfolio you create, you must set up
an entirely separate set of deals, deal subtypes, and product types within your journal structure. Therefore,
adding a new portfolio adds a new level of complexity to your Treasury system.

Tip: Minimize the number of portfolios you create. To make it easier for you to maintain your deals, deal
subtypes, and product types, you should only create as many portfolios as you need to support your
company accounting practices.

You can create two types of portfolios. Internal portfolios are portfolios that are managed directly by your
company. External portfolios are portfolios that are managed by your company for a third party. External
portfolios appear in the Portfolio Codes window only for the counterparties that have the external portfolio.

After you create a portfolio, you must create journal entries for each combination of deal type, deal subtype
and product type that uses the portfolio. See: Journal Entry Actions.

Setting up Portfolios

Use the Portfolios window to set up portfolios for your various companies.

To set up a portfolio

1. Navigate to the Portfolios window.

2. Query or enter the Company code that you want.

3. Enter a unique Code and Name for the portfolio.

4. If the portfolio is for an external party, select the External Portfolio check box and enter the external
party in the Ext Party field.
 5. If you want to set this portfolio as the default internal portfolio, select the Internal check box.

6. Save your work.

Confirmation Templates
You can produce one-page confirmations for most deal-related actions and send a print or file version of the
confirmation to counterparty. You can print confirmation letters manually or choose to produce them
automatically when you confirm a deal.

Confirmation templates define the layout of your deal confirmations. You can create your own template,
copy an existing template, or use the standard templates provided with Treasury (FX Initial, NI Initial, FRA
Settlement).

You can create different confirmation templates for a particular deal type or deal action. For example, you
can create a confirmation template to confirm an initial option deal and another template to confirm the
exercise details for the option deal.

You can create more than one template for a deal action, but you can set only one template as the default.

Creating Confirmation Templates

You use the Confirmation Templates and User Views window to create confirmation templates.

To create a confirmation template

1. In the Template Name field of the Confirmation Templates and User Views window, enter a unique
template name

2. In the Action Type field, select the deal action that you want to apply the template to. For a complete
list of deal actions by deal type, see: Deal Amount Types and Deal Actions by Deal Type.

3. In the Column Description fields, enter the text of the confirmation template. Each row in the column
description field corresponds to a row of text in the confirmation template. For example, the text that
you enter in row one appears on the first line of the confirmation template.

4. If you want to insert common variables, such as the counterparty account number, into your
confirmation template, follow these steps:

o Insert your cursor where you want to insert the variable and choose the list of values.

o Select the variable that you want from the list in the Select Columns to Copy window, and
then choose the Copy button.

5. If you want to copy one line of information to another, select the line that you want to copy and
choose the Copy Layout Fields button.

6. If you want to erase all the information in the Column Description fields and start again, choose the
Delete Template Details button.

7. If you want the template font to be fixed-width, choose the Fixed option. If you want the font to be
proportional, choose the Proportional option.

8. When you have entered all the information for your template, choose the Make Template button.
 9. If you want this template to be the default for the selected deal action type, select the Default
Template check box.

10. Save your work.

11. To view a list of your default templates, choose the Show Default Templates button. The Default
Templates window appears.

Copying Existing Confirmation Templates

Use the Confirmation Templates and User View window to copy an existing confirmation template and use
it as the basis for a new template.

To copy an existing confirmation template

1. In the Confirmation Templates and User View window, enter a template name and an action type for
the template you want to create.

2. Choose the Copy Existing Template button. A warning appears, stating that all of the existing
template details will be deleted. Select Yes to proceed. The Choose an Existing Template to Copy
window appears.

3. Select the template you want to copy and choose the Copy button.

4. Change the template as needed and choose the Make Template button.

5. Save your work.

Journal Entry Actions

Use the Journal Entry Actions window to define the General Ledger accounts that are used to generate
accounting entries for each combination of deal type, deal subtype, product type, and portfolio within a
company. To ensure a balanced ledger, it is critical that accounts and journals are set up completely and
correctly.

Note: For some miscellaneous cashflows reported by your bank, you may find the Journal Entry Creation
program useful to create journal entries automatically based on information provided in the bank statement.
For more information, see: Creating Journal Entries from Bank File, Oracle Cash Management User Guide.

Defining General Ledger Accounts

Use the GL Accounts tabbed region of the Journal Entry Actions window to define General Ledger accounts
for each company. You can add new accounts and review existing accounts, but you cannot change or delete
existing accounts.

The available General Ledger accounts derive from the ledger associated with the company.

To review and define general ledger accounts

1. Navigate to the Journal Entry Actions window.

2. Query the Company that you want.

 3. If you want to define a new General Ledger account, enter a General Ledger account alias in the GL
Account column. Treasury populates the fields with the General Ledger account number and
description.

4. In the Treasury Reference field, you can enter your own description to identify this GL account. The
Treasury reference that you enter appears alongside the GL account number in the list of values
throughout Treasury.

5. Save your work.

System Parameters
System parameters define various settings for the operation and control of Treasury. Set your system
parameters at implementation time using the Treasury Superuser ID. You can update them after
implementation as needed. The database administrator is responsible for setting and maintaining system
parameters.

The following system parameters appear on the System Parameters window:

Parameter Value Description

Accrual Days Forward or Sets the range of dates for accruals to either all dates prior to the
Adjustment Type Arrears accrual date (Forward), or to all dates up to and including the
(default). accrual date (Arrears).
Days Forwards as Numeric. The The number of days that Treasury uses as a default for the spot
Default FX Value Date default is 2. date on foreign exchange deals.
Default Company as Drawer If the deal subtype is Issue, Treasury uses Acceptor, Drawer, or
Drawer, Acceptor, or (default), Endorser as the default for the company code.
Endorser Acceptor, or
Endorser.
Display Warning After Yes or No Displays a warning if you exceed a limit.
Limit Check (default).
Validate Deal Input Yes or No Validates deal input for correctness before any settlements can be
(default). authorized.
Validation Required for Yes or No Determines whether validated deals or all deals are available for
Confirmations (default). generating confirmation letters.
Validation Required for Yes or No Determines whether the journal process creates journals for
Accounting (default). validated deals and transactions only or all deals and transactions.
Use Period End Rates Yes or No Uses the end-of-month rate for performing settlements rather
for FX Realized Deals (default). than the actual rate on the date the deal matures. If you select No,
you must maintain your daily GL rates tables.
Settlements: Yes or No Determines whether inter-account transfers are manually or
Automatically automatically authorized. If set to Yes, the system automatically
Authorize Interaccount authorizes inter-account transfers for settlement. If set to No, you
Transfers must manually authorize inter-account transfers for settlement.
Limit Checks on Quick Yes (default) or Performs limit checks when creating deals by using the Quick
Input No. Deal Input window.
Settle to Other than Yes or No If set to Yes, allows settlements to be paid to parties other than
Counterparty Bank (default). the counterparty.
Account
Receive to Other Than Yes or No Allows settlements to be received from or settled to
Company Bank (default). parties/accounts other than the company accounts.
Account
Treasury Report Currency short Sets the standard currency used in Treasury reports.
Currency form. USD
(default).

Deal Setup
This section contains information on how to set up particular deal types in Treasury. It includes information
on setting up stocks, bonds, registering certificates available for issue, setting up payment schedules,
defining your exposure types, and setting up hedges.

Stock Issues
Use the Stock Issues window to define basic information for your company's stock investments. You can
define a stock issue for any stock that your company either trades in or wants to track.

Once you define your stock issues in the Stock Issues window, use the Stocks window to enter your buy and
sell stock deals. See: Equities.

You can navigate to the Stocks window directly from the Stock Issues window to enter a deal for the active
stock issue by choosing the Deal Input button. The Deal Input button is available if:

 the stock issue is authorized for use;

 your user responsibility includes access to the Stocks window; and
 you accessed the Stock Issues window using Entry mode.

Defining Stock Issues

Set up a stock issue to define the key attributes of a stock. A stock issue definition can, for example, save
you time when you enter several deals for the same stock. The stock issue also enables you to track a stock's
performance, even if you are not trading that stock.

You must define a stock issue for any stock that you want to purchase.

Prerequisites

 Set up stock issuers as Risk Party counterparties in the Counterparty Profiles window. See:
Counterparty Profiles.
 Authorize the currency of the stock issue in the Currency Details window. See: Currency Details.
 (Optional) Use the Application Object Library Lookups window to create additional business sector
lookup codes for the lookup type XTR_SECTOR. Oracle Treasury contains a list of seeded lookups
for business sectors, based on the global industry classification standard (GICS).
 (Optional) Define and authorize stock product types, and authorize pricing models. See: Deal Types
and Product Types.
 (Optional) Define current system rates for stock prices. See: Current System Rates.
 (Optional) Define and authorize market data sets for stock revaluation. See: Market Data Sets.

To enter a stock issue

1. Navigate to the Stock Issues window.
2. Enter a unique Issue Code for this stock issue.
3. In the Issuer Code field, enter the counterparty that issued the stock.
4. To authorize the stock issue for use, enable the Authorized check box.
5. Navigate to the Issue Details region.
6. Enter the Currency of the stock.
7. Enter the Ticker Symbol for the stock. Ticker symbols are assigned by the exchange that trades the
stock.
8. If the stock has an ID assigned by an international organization, such as a CUSIP number, enter this
number in the Security ID field.
9. In the Exchange field, enter the name of the stock exchange that the stock is traded on.
10. In the Issue Date field, enter the date that the stock was issued to investors (for example, the stock's
initial public offering date).

Note: To enter a stock deal for this stock, the deal date must be on or after the Issue Date.

11. In the Sector field, enter the business sector that the stock belongs to.
12. Enter the stock Product Type.
13. Navigate to the Revaluation Details region to enter revaluation information for stock deals based on
this stock issue code.
14. In the Rate Reference field, enter a current system rate for the stock.

Treasury uses the rate you enter to revalue deals based on this stock issue code and to perform
tolerance checks when a deal is saved.

15. Enter the Market Data Set to use to revalue deals based on this stock issue code.
16. Enter the Pricing Model to use to revalue deals based on this stock issue code.
17. Save your work.
18. If available, you can choose the Deal Input button to enter a stock deal based on the issue that you
just defined.