This chapter covers the following topics:
This chapter describes the tasks that must be performed before beginning your implementation of Oracle iStore.
The mandatory dependencies discussed in this chapter must be implemented in order for your implementation to be successful.
Oracle iStore integrates with many other Oracle applications to provide and extend its functionality; therefore, a large portion of your implementation will involve understanding, setting up, and maintaining the integrating applications.
Information about multiple organizations (multi-org), specific to Oracle iStore, is contained in the chapter, Implementing Globalization and Multi-Org Architecture. For Oracle Applications multi-org information, see Oracle E-Business Suite Multiple Organizations Implementation Guide.
Oracle iStore's dependencies and integrations range from those applications that supply an underlying structure for your sites to those that extend its functionality and capabilities. The applications that provide structure are mandatory, while ones that enhance Oracle iStore are optional integrations.
Oracle iStore mandatory dependencies are Oracle products which provide the underlying technology stack, schema, and structure.
Oracle iStore mandatory dependencies are:
Oracle CRM Technology Foundation
Oracle E-Business Tax
Oracle General Ledger
Oracle Human Resources
Oracle Inventory
Oracle Order Management
Oracle Order Capture
Oracle Trading Community Architecture
Limited setup information about these products is contained in this chapter. Refer to the product-specific implementation and user manuals for complete information.
Oracle applications that extend Oracle iStore's capabilities are considered optional integrations. Basic setup information is contained in this guide, but you will need to refer to the product-specific setup and user manuals for complete information. Setting up the optional modules is not required; however, if they are not set up, then the additional functionality provided by these modules will not be available.
See the "Optional Integrations with Oracle iStore" section of this chapter for a discussion of these applications.
The following table provides a recommended sequence for beginning your implementation and setting up the Oracle iStore mandatory dependencies.
| Step | Required | Reference |
|---|---|---|
| Install Software | Yes | "Install Software" section |
| Verify Underlying Technology Stack Installation | No | "Initial Installation Verification" section |
| Set up Oracle E-Business Tax | Yes | "Setting up Oracle E-Business Tax" section |
| Set up Oracle General Ledger | Yes | "Setting up Oracle General Ledger" section |
| Set up Oracle Human Resources | Yes | "Setting up Oracle Human Resources" section |
| Set up Oracle Inventory | Yes | "Setting up Oracle Inventory" section |
| Set up Oracle Order Management and Oracle Order Capture | Yes | "Setting up Oracle Order Management" section |
| Set up Oracle Pricing | Yes | "Setting up Pricing" section |
| Set up Oracle CRM Technology Foundation | Yes | "Setting up Oracle CRM Technology Foundation" section |
| Set up Oracle Trading Community Architecture | Yes | "Setting up Oracle Trading Community Architecture" section |
Tasks in this guide require login on the following two Oracle technology stacks:
Oracle Application Object Library (AOL):This technology stack is also known as Oracle Forms. See the "Accessing Oracle Forms" section, below.
Oracle CRM Login Servlet This is the HTML login that you access from within an Internet browser. Microsoft Internet Explorer 5.5 (with cookies enabled) is the recommended browser setup for accessing the HTML-based applications. See the "Accessing Oracle E-Business Suite HTML Applications" section, below.
Oracle Applications come with a supplied (seeded) system administrator login, with which you can access both Oracle Forms and the Oracle E-Business Suite HTML Applications. The seeded login is:
Username: sysadmin
Password: sysadmin
It is strongly recommended that you change the password at your earliest convenience after installing and accessing the applications. For more information, see:
Installing Oracle Applications
Upgrading Oracle Applications
Oracle Applications Release Notes
Visit My Oracle Support for these installation and upgrade documents.
Many setups for Oracle iStore and its dependencies require that you use Oracle Forms. Launch Oracle Forms by navigating to: http://<host>:<port>/and selecting Apps Logon Links, VIS Logon through the Forms cartridge.
Once logged into Oracle Forms, you can select from a list of responsibilities that determine the functionality you are allowed to use.
To access the Oracle E-Business Suite HTML applications, navigate to: http://<host>:<port>/oa_servlets/oracle.apps.jtf.base.session.CRMLogin. This login is known as the CRM Login Servlet.
Log in with the appropriate username and password. The seeded username/password is:
Username = sysadmin
Password = sysadmin
All Oracle applications use the concept of user responsibilities for basic user security and application mapping. The responsibility a user logs in with will determine the application (and hence, the menus) that appear. Each responsibility is mapped to a menu structure in Oracle Forms. For information on Oracle iStore responsibilities, see the chapter, Implementing User Management, and the appendix, Seeded User Data.
Install the relevant Oracle Applications Release 12 patches. See My Oracle Support for Documentation Resources (Roadmaps). These documentation roadmaps will assist you in your installation.
Oracle Applications supports the installation of Multiple Language Support, known by the acronym MLS. MLS is also known as National Language Support, or NLS.
To install more than one language, see the following:
Installing Oracle Applications
Oracle E-Business Suite Installation Guide
Oracle E-Business Suite Concepts, Globalization
Oracle iStore is fully supportive of MLS/NLS, providing you have followed the required steps to set up the additional languages.
Information on globalization and multiple organizations is contained in the chapter, Implementing Globalization and Multi-Org Architecture.
Oracle iStore integrates with Oracle E-Business Tax to display calculated tax information to customers. Following are the tax business objects supported (and displayed) in the shopping cart, order review and order details pages:
Tax codes
Tax rates
Tax amounts
By default, Oracle iStore displays only cart-level tax data, but you can configure the pages to display tax data at the item level. For more information on setting up item-level tax display, see the "Tax Display in Shopping Carts" topic in the chapter, Implementing Carts and Orders.
Note: Integration with Oracle E-Business Tax requires Oracle Financials Family Pack, and Oracle Order Capture (ASO).
For more information on setting up and using Oracle E-Business Tax, see the Oracle E-Business Tax Implementation Guide and the Oracle E-Business Tax User Guide.
Oracle Trading Community (TCA) models and manages an electronic representation of the commercial community in which you do business. Oracle Trading Community includes:
A comprehensive database schema also referred to as the Community Registry
A set of PL/SQL APIs for custom development
Access integration with content providers
A sophisticated set of data management utilities
For more information on TCA, see the Oracle Trading Community Architecture Administration Guide and the Oracle Trading Community Architecture User Guide.
Oracle iStore's address book functionality can dynamically provide address information entry fields based on the user's country, and perform address validation. Address information is stored in the Oracle TCA schema.
Keep the following guidelines in mind as you implement Oracle iStore.
Out-of-the-box, address validation is available only for U.S. addresses.
For the country, U.S., Oracle iStore uses the fixed U.S. address format. If flexible address formats are not set up for other countries, the default fixed address format is used for these as well. If flexible address formats are set up, the flexible address formats will be used.
Oracle General Ledger (GL) provides business unit information to Oracle iStore. You also set up currencies in GL.
Note: If you are implementing Oracle iStore reports, then you must create a single calendar with the periods types: Day, Week, Month, Quarter, and Year, in order for the reports to work. Or, if you do not want to add all of these periods to the GL calendar, for reporting purposes, you can create a separate calendar for Oracle iStore in GL with the required period types.
See the Oracle General Ledger User Guide for information on how to perform these tasks.
Oracle Human Resources Management System (HRMS) stores information related to your organization. Use HRMS to set up employees and bill-to and ship-to countries. See the appropriate version of Oracle HRMS documentation for more information.
Oracle Inventory serves as the repository of products that can be sold through Oracle iStore. Before you can create products in Oracle Inventory, you must set up and define the category structures within which products reside.
In addition, several Oracle Inventory flags need to be set in order for products to display in the Oracle iStore Customer Application. See the chapter, Implementing Products, for Oracle iStore-specific product setup details.
Refer to the Oracle Inventory User's Guide for complete details of inventory setup.
Oracle iStore uses the Oracle Order Management suite of applications to:
Process, record, and track customer orders and shipping details
Set up basic pricing
Set up payment and shipping options
Oracle Order Management integrates with Oracle iStore via Oracle Order Capture APIs and schema. Order information is communicated to Oracle Order Capture via the ASO_Update_Order API.
This guide contains limited information on setting up and using Oracle Order Management. See the Oracle Order Management documentation for more information:
You can set up Oracle Order Management to default certain values (following rules you set up in Oracle Order Management), for several order attributes, if no values exist for these attributes when a cart is submitted as an order. Use the profile option, ASO: OM Defaulting, to enable or disable the defaulting. To set parameters for specific attributes, use the steps below.
Prerequisites
The profile option, IBE: Default Payment Term, is blank at the iStore application level.
The profile option, ASO: OM Defaulting, is Yes.
Steps
Log into Oracle Forms with Order Management Superuser Responsibility.
Navigate to Menu, Setup, Rules, Defaulting.
Query for:
Application: Oracle Order Management
Entity: Order Header
In the Attributes area: Find the desired attribute, select it, and select the Defaulting Rules button.
In the Defaulting Sourcing Rules window, you can add (or subtract) any source/value item for the attribute.
After modifying the values, be sure to run the Build Attribute Mapping Rules concurrent program and bounce the middle-tier server.
See the "Supported Oracle Order Management Defaulting Values" section for a list of the defaulting parameters supported by Oracle iStore and Oracle Order Capture schema.
The following are the defaulting values supported by Oracle iStore:
Cart (Header) Fields:
invoice_to_org_id
invoice_to_contact_id
ship_to_org_id
ship_to_contact_id
request_date
ship_from_org_id
Only if ASO: OM Defaulting = Y:
shipping_instructions
packing_instructions
salesrep_id
payment_term_id
fob_code
freight_terms_code
shipment_priority_code
agreement_id
order_category_code
accounting_rule_id
invoicing_rule_id
Item (Line) Fields:
invoice_to_org_id
invoice_to_contact_id
line_type_id
price_list_id
ship_to_org_id
ship_to_contact_id
request_date
schedule_ship_date
promise_date
ship_from_org_id
Only if ASO: OM Defaulting = Y:
shipping_instructions
packing_instructions
payment_term_id
fob_code
freight_terms_code
shipment_priority_code
agreement_id
line_category_code
accounting_rule_id
invoicing_rule_id
See the chapter, Implementing Pricing, for information about pricing setups.
Oracle CRM Technology Foundation provides the underlying technology stack for the Oracle HTML applications. You must implement Oracle CRM Technology Foundation as described in Oracle E-Business Suite CRM System Administrator's Guide.
After this implementation, perform the Oracle iStore-related setups listed in the following sections:
Set up Host Configuration: See "Host Configuration", below
Set up Cookie Properties: See "Cookie Properties", below
Set up Look and Feel Property: See "Setting Look and Feel JTF Property", below
Set up Component Caches: See "Component Caches for Oracle iStore in JTT" in the chapter, Implementing Miscellaneous Internet-Related Features
When you build the Oracle CRM Technology Foundation deployment configuration, you must set up all middle-tier hosts. For each host on which you will deploy Oracle iStore, include iStore in the host's deployed applications list.
The user session in Oracle iStore is controlled and identified by cookies. The cookies are set on the user's browser and identify return customers. The Oracle iStore process is transparent to cookie administration, setup, and control. Cookies are managed by Oracle CRM Technology Foundation methods. If the user turns off browser cookies, Oracle CRM Technology Foundation ensures that the cookie information is available through the URL.
The cookie domain is set as the Web server domain, for example, oracle.com , for Oracle's online store. Once the user registers, the user account is created in the database and is used in the cookies to identify the customer. If the user is unregistered, a guest user account is used in the cookies.
Enabling cookie encryption is a mandatory setup step that involves specifying an encryption key while setting up cookie properties in Oracle CRM Technology Foundation.
To change the expiry settings for cookies, use the following steps:
Log in as System Administrator. Navigate to CRM HTML Administration, select Setup, and then select Settings. From Settings, select System, then select Properties and then Cookies.
Change the value for theExpires After and Expiration Unit fields. The default value is 60 days.
Click Update.
Clear your browser history to ensure that the cookies have the new expiry settings. Retest to confirm if the expiry time is set as defined in previous steps.
Ensure that the Oracle Technology Foundation property (JTF/JTT) property Look and feel.cabo is set to True, either at the JTF/JTF application level or at the IBE application level.
Use the guidelines below to determine at which level the property should be set:
When to set at JTF/JTT application level: Set it at the JTT level if you are using only Oracle iStore, or if you are using Oracle iStore in combination with other Oracle applications which have full Cabo Look and Feel in their systems.
When to set at the IBE (iStore) application level: Set it at the iStore application level if you are using other Oracle applications which have partial Cabo Look and Feel in their systems.
Note: If you are unsure of the Cabo Look and Feel level in the applications you are using, then to be safe, set the property at the iStore application level.
Steps
The steps to set this property are:
Login as System Administrator to the CRM Login Servlet.
Navigate to Settings, System, Advanced. The Advanced - Properties page appears.
To set the property at the JTF/JTT application level:
In the View droplist, select the Oracle CRM Technology Foundation application product code, JTF. (Press the Update button if necessary.)
In the list that appears, select the hyperlink of the property, LookAndFeel.cabo.
In the Key Details page, enter the following values:
Key field = LookAndFeel.cabo
Value (Sequence 0) field = true
Select the Update button to save the changes.
To set the property at the IBE (Oracle iStore) application level:
In the View droplist, select iStore's product code, IBE. If IBE is not in the list, see "Adding IBE to the View Droplist", below.
Select the Create button.
In the Create Key page, enter the following values:
Key field = LookAndFeel.cabo
Value (Sequence 0) field = true
Click the Update button to save the changes.
When you are finished making the changes, log out of the sysadmin console, and log in as the iStore Administrator.
The Cabo Look and Feel should function properly.
Also, make sure the following directories are globally writable:
/OA_HTML/cabo/images/cache
/OA_HTML/cabo/styles/cache
If Oracle iStore's product code, IBE, is not shown in the View droplist in the Advanced - Properties page, do the following:
Navigate to Settings, System, Category. In the Property Category page, select the following:
Application Name: Select iStore.
Read/update: Select Update .
Select the Next button.
In the Permission Role Mapping page, move JTF_SYSTEM_ADMIN_ROLE from the Available Roles window to the Assigned Roles window.
Select the Update button to save the changes.
See the latest Oracle E-Business Suite CRM System Administrator's Guide, for more information.
Several Oracle applications modules can be set up to provide additional functionality for your electronic sites. These are mentioned below. Refer to the relevant chapter and/or product documentation for more information.
Use Oracle Advanced Pricing to set up customer discounts, sourcing rules, pricing qualifiers, and pricing modifiers. See the chapter, Implementing Pricing, for details.
Use Oracle Advanced Supply Chain (Global ATP Server) to provide product availability information. See the chapter, Integrating Oracle iStore with Oracle Advanced Supply Chain Planning, for details.
Use Oracle Bills of Material to set up configurable items, model bundles, and items with standard warranties for sale in your sites. See the chapter, Integrating Oracle iStore with Oracle Bills of Material, for details.
Use the Oracle Call Center Technology (CCT) suite of applications to process call-me-back requests. See the chapter, Implementing Customer Assistance, for more details.
Use Oracle Configurator to enable customer configured products, provide guided selling, and perform some of the shopping cart validations. See the chapter, Integrating Oracle iStore with Oracle Configurator, for details.
Use Oracle Content Manager to provide a complete range of content item creation and management capabilities. See the chapter, Integrating Oracle iStore with Oracle Content Manager, for details.
Integrate with Oracle Service Contracts to support the selling of serviceable items and related services in the Customer Application. Integrate with Oracle Sales Contracts to provide Terms and Conditions functionality in the checkout pages of the Customer Application. See the chapters, Implementing Products, and the Integrating Oracle iStore with Oracle Sales Contracts, for details.
The Oracle Customer Care suite of applications provides a complete view of the customer by displaying relevant customer information. Customer Care allows agents to alter customer data and create interactions with the customer. See Oracle Customer Care Implementation Guide for details.
Use Oracle iSupport to provide self-service service request submission, order details views, return for credit authorizations, knowledge management, Install Base access, and user forums. Also integrate with Oracle iSupport to provide a unified Support dashboard for users of Oracle iStore and Oracle iSupport. See the chapter, Integrating Oracle iStore with Oracle iSupport, for details.
Use Oracle Install Base to maintain -- and allow customers to maintain -- a repository of purchase information, including purchase date, product attributes, and applicable service agreements. See Oracle Install Base Implementation Guide for details.
Use Oracle Marketing to create and maintain products; define, execute, and manage marketing campaigns; and to track user events. See the chapter, Integrating Oracle iStore with Oracle Marketing, for details.
Use Oracle Partner Management to provide a unified Partner dashboard in the Oracle iStore Customer UI. See the chapter, Integrating Oracle iStore with Oracle Partner Management, for details.
Use Oracle Quoting to create quotes that can be published to Oracle iStore sites, to provide contracts setup for Terms and Conditions, to capture carts as quotes when users request sales assistance, and to share quotes with other users. See the chapter, Integrating Oracle iStore with Oracle Quoting, for details.
Use Oracle Sales and Oracle TeleSales to import sales leads from Oracle iStore orders and expired shopping carts. For more information on the Lead Import functionality of Oracle iStore, see the chapter, Integrating Oracle iStore with Oracle Sales Applications.
Use the Order Management module, Oracle Shipping Execution (SE), to calculate shipping charges, and to set up shipping parameters, transportation calendars, pick slip rules, container-item relationships, suppliers (freight carriers), and document printing. The Oracle Shipping Execution module must be in place to enable post-order tracking and shipping detail views in Oracle iStore. See the chapter, Integrating Oracle iStore with Oracle Shipping Execution, for details.
Use Oracle Single Sign-On Server to provide single-authentication architecture. See the chapter, Integrating Oracle iStore with Oracle Single Sign-On, for more information.
Use Oracle Workflow to send HTML e-mail notifications and confirmations to customers and sales representatives. See the chapter, Integrating Oracle iStore with Oracle Workflow, for details.
Use Oracle Application Server Web Cache to serve the non-transactional Oracle iStore content. See the chapter, Integrating Oracle iStore with Oracle Application Server Web Cache, for details.