Tips & Tricks for Customizing iStore pages

Tips to develop JSPs:

1. Two types of block comments – JSP and HTML.

1.1. JSP Comments - "<%"-- these comments will not show in source code of HTML page --%>

1.2. HTML comments - 2. In iStore, pages you want to modify for template purposes almost always end in I.

2.1. IStore Naming Convention: ibeCZzdError.jsp

2.2. Ibe is the prefix indicating it’s an iStore page. (I think this may tie to being a customer facing page as well but I can’t confirm it)

2.4. The zd indicates it’s a display page. If it had tp it would indicate a processing page.

2.5. In display template pages, the JSPs are paired, with a processing page (e.g. ibeCZtpSpecialPage.jsp) and a display page (e.g. ibeCZzdSpecialPageI.jsp). The pairs are normally named the same with a differentiation on the zd and the appended I. The processing page will also reference the display page programatically through its Programattic Access Name, stored within oracle iStore. (you can find the programmatic display name via the processing JSP - find DisplayManager.getTemplate and you’ll see the programmatic accessname in all caps)

3. Directories where JSPs are held - $OA_HTML

4. Flags to set in zone.properties to speed development of JSP –

4.1. Autoreload.classes = true

4.2. Autoreload. file=true

4.3. developer_mode=true

Tricks to develop pages:

1) Always see if a profile option can do the trick. Lots of the iStore bins can be turned on and off via templates or profile options. Read Appendix A and D in the IBE Administrator guide prior to making changes to the JSP.

2) When modifying JSPs, set all border=0 to border=1 in the JSP. This will allow you to see the layout while you make changes.

3) Errors such as Catch without Try or If statement errors normally point to a missing closing bracket or semicolon.

Creating Templates in iStore Administrator:

Templates in iStore consists of two types of JSPs:

1) A processing page – e.g. ibeCCtpLfStMsL.jsp

2) A display page (also known as the INCLUDE) – e.g. ibeCCtdLfStMsLI.jsp

When creating a new template, you must create BOTH pages.

I. Processing Page:

This page calls the display programatically. There is a specific change to be made in the processing page, found under DisplayManager.getTemplate(SOME_NAME).

SOME_NAME must be changed to the programmatic access name of the display page. (This name is selected by you, but when entering the display page in the Display Manager, it must correspond to the name you have entered in the processing page)

Additioonally, when creating a new template type for the processing page, you must choose the type of template it is –

· Section Contains Products Only

· Section contains Navigational Subsections only

· Section contains Featured Subsection

There’s a few others that are available, but the top two will be the most commonly used. As you gain sophistication in iStore and web sales in general, you may determine a need for featured sections, which can also be created here.

II. Display Page

This page displays the items or sections as you determine.

When adding this page into the template manager, ensure that:

· Its template type is “Others”

· Its Programattic Access Name corresponds to the name chosen in the Processing Page.

iStore Public APIs

Oracle iStore supports only the following public APIs,

1) StoreMinisite - Miisite Info API
2) StoreProfile - Store Profiles setups
3) DisplayManager - Template Mappings and Other Mappings
4) Catalog - iStore Catalog - Section, display template etc.
8) ShoppingCart - Quote, Shopping cart
9) AK Objects reltd APIs - Postsales data
10) IbeAtpPvt - ATP - Availability

Oracle iStore return Orders

Here's an article which gives a good idea on how return orders work in iStore.

http://oraclescm.smartapps.nl/index.php?op=ViewArticle&articleId=8&blogId=1

Thanks to Johan Louwers

Implementing iStore in MultiOrg environment

How to setup Stores in a Multi Org Environment

By default, the design for iStore is geared towards single operating unit installations:

- One Store Admin responsibility (IBE_ADMIN),

- One Customer responsibility (IBE_CUSTOMER)

- One Guest User responsibility (IBE_GUEST)

- One Operating Unit

- One Item Validation Organization (usually Master, but any Inventory Org will suffice)

To perform a Multi-Operating Unit iStore setup correctly, we need to create separate responsibilities for each of the Operating Units. In effect, the design discards the default responsibilities

Assume that Operating Unit 1 (OU1) has under it Inventory Orgs IO1, IO2, IO3

Similarly, Operating Unit 2 (OU2) has under it Inventory Orgs IO3, IO4, IO5

The correct setup would be

For Operating Unit 1: (OU1)

Define an OU1_iStore Administrator responsibility, copied from iStore Administrator

Define a OU1_IBE_CUSTOMER, copied from IBE_CUSTOMER

Define a OU1_IBE_GUEST, copied from IBE_GUEST

In the profile options,

IBE: Item Validation Organization needs now to be setup at the responsibility level for

OU1_iStore Administrator

OU1_IBE_CUSTOMER

OU1_IBE_GUEST

The value can be any of the Inventory Organizations (IOs) belonging to the Operating Unit (IO1, IO2, IO3)

Similarly, the Profile Option MO: Operating Unit needs to be OU1 for each of the above responsibilities

The correct setup would be

For Operating Unit 2: (OU2)

Define an OU2_iStore Administrator responsibility, copied from iStore Administrator

Define a OU2_IBE_CUSTOMER, copied from IBE_CUSTOMER

Define a OU2_IBE_GUEST, copied from IBE_GUEST

In the profile options,

IBE: Item Validation Organization needs now to be setup at the responsibility level for

OU2_iStore Administrator

OU2_IBE_CUSTOMER

OU2_IBE_GUEST

The value can be any of the Inventory Organizations (IOs) belonging to the Operating Unit (IO4, IO5, IO6)

Similarly, the Profile Option MO: Operating Unit needs to be OU2 for each of the above responsibilities

These responsibilities need to be created under the CRM HTML Administrator responsibility. NOTE: The sysadmin username needs to be used

Furthermore, Registration templates need to be created for each Operating Unit. These can be copied from the existing registration templates.

iStore Module dependency

iStore - General Concepts

• Specialty stores:
– Multiple sites within a single instance
– Sites could be categorized by access, language, product group, customer etc
• Product catalog:
– Customizable Layouts
– Customizable Product Search
– Supports product relationships (substitute items etc )
• Oracle Configurator:
– Fully integrated as in Order Management
• Oracle Advanced Pricing:
– Fully integrated as in Order Management
– Supports promotion codes with Limits
• ATP check:
– Integrated as in Order Management
– Supports product relationships (substitute items, related items etc )
• B2B functionality:
– Comprehensive User Registration
– Approval step, consolidated check out, Share Cart…
• Customer’s Shopping List:
– Customer can use their own shopping list
• Attachments:
– Attachments applied are copied up to OM Order
• Direct item Entry:
– Customer can enter items without searching
• Promotion Codes / Agreements
– Use promotion codes / Agreements to use in QP.
• E-mail notifications:
– Orders placed, Cancelled orders, Forgotten passwords, User Registrations, …
• Product Search:
– By Item Code, Description, Long Description, Category and item relationships
(synonyms, substitute items,…)
• Order Cancellation Ability;
– Till order is Pick Released;
• Order Tracker functionality:
– Delivery status, carrier consignment status
• Payments Tracker functionality
• Invoice Tracker functionality

Oracle iStore Demo

Please refer to the following links for a demo on the new Oracle iStore Rel 12 product.

Part 1
http://oracleyou.com/blg_view.php?blog_id=163

Part 2
http://oracleyou.com/blg_view.php?blog_id=164

Part 3
http://oracleyou.com/blg_view.php?blog_id=165&org_id=59

Oracle iStore Introduction

Oracle iStore is an eCommerce application which comes as a part of a comprehensive ERP suite - Oracle Applications. Oracle iStore enables clients to create, manage, and customize powerful and scalable eCommerce sites.

Oracle iStore is very well integrated with Oracle Applications's sales and CRM modules prociding centralized data management and a secure and personalized environment.

Oracle iStore supports Business-to-Business(B2B) and Business-to-Consumer(B2C) business models. Oracle iStore uses the similar architecture to Oracle Order Management and utilizes most features of Oracle Advanced pricing hence benefiting the users with low cost centrallized sales system.

Oracle iStore is also fully integrated with Oracle iPayment which enables credit card processing and transactions easier.