Istore Case Study: R12 Training Exercises
Istore Case Study: R12 Training Exercises
Istore Case Study: R12 Training Exercises
Document Control
Date Author Version Change Reference
09-14-2009 Robert Carini 1.0 New Document for R12, 1st Draft.
09-28-2009 Robert Carini 2.0 Added Appendix C & D for instructor notes, and replaced
reference to the iStore default Cascading Style Sheet
from “jtfucss.css” to “ibeCStyleSheet.css”.
System References
iStore
Advanced Pricing
Content Manager
Inventory
Order Management
Quoting
Distribution
Implementing iStore for R12
iStore Implementer
iStore Administrator
Ownership
The Job Title [[email protected]?Subject=EDUxxxxx] is responsible for ensuring
that this document is necessary and that it reflects actual practice.
Oracle iStore consists of two distinct, but integrated user interfaces: The Site
Administration Application and the Customer Application. The iStore Site
Administration Application interface allows administrators to create and maintain
multiple storefront sites, catalogs, and related business rules. The iStore Customer
Application interface is a full, web-based shopping application which is presented to the
customers coming in over the web channel to purchase products from the storefront site.
The iStore Site Administration Application allows you to design and set up a store in few
minutes, creating a multimedia repository, sections, products, and pricing information.
Multiple store fronts enable you to configure the iStore Customer UI user interface’s look
and feel according to your business needs.
The iStore Site Administration Application also offers advanced features such as multiple
stores related to the same catalog for global implementations; B2B and B2C selling
models; the ability to build relationships between products; the ability to customize the
iStore Customer UI look and feel using personalized templates; and advanced business
functions that provide seamless integrations with other Oracle applications such as
Advanced Pricing, Advanced Supply Chain, Configurator, Content Manager, iSupport,
Sales and Marketing, Payments, Procurement, Quoting, and Sales Contracts.
The focus of this case study is on the iStore Site Administration Application, which will
be referred to as the Administrator UI. This case study will provide you with the basic
steps in order to set up a store, and will also cover a few advanced topics once the store
has been created.
Once the store has been established, then you will be able to come in as an end user
consumer through the iStore Customer Application, which will be referred to as the
Customer UI, and browse the store sites, select products from the product catalog, place
them in your shopping cart, perform the checkout process, and submit your purchase to
Order Management.
Option 1
Build your store based on an Antique Store theme. In this scenario, the images have been
provided as well as some information added in the tables to help you with your task.
Please refer to Appendix A, Antique Store Tables.
Option 2
Build your store based on your own custom theme. You will be creating your own
products and providing images for your store. If you want to choose this option, you can
skip all of the tables in Appendix A that contain data and use the blank worksheet tables
to enter your stores specific information. Please refer to Appendix A, Custom Theme
Store Tables.
Do not allow
changing of store
Walk-ins allowed
Check Availability
Check for
Supported
Responsibilities
Change the default
layout of the bins
for your store
Change the default
layout of the bins
for your store
4. Load Product Images for Your Specialty Store into Content Manager.
6. Map Products to Media Objects and their Images using the Administrator UI.
Additional Customizations
13. Change the text in bins using Oracle Application Object Library (AOL).
Appendix
B. Glossary
Note: Navigational sections can contain products or sub-sections, but not both. Featured
sections contain products only and cannot have subsections. You can create groups of
featured products at any level in the hierarchy by creating a subsection of type Featured
in a Navigational section and then adding products to that Featured section.
3. On the Navigator window, select Inventory -> Items -> Master Items.
• Inventory Item
9. Select the Order Management TAB from the LOV drop down menu.
• Customer Ordered
11. Select the Web Option TAB from the LOV drop down menu on the right.
12. Make sure the value of “Published” is chosen in the List of Values (LOV) for
the Web Status drop down menu:
• Back Orderable
19. For each additional item you want to add, click on the “New” icon.
20. Repeat steps 5 through 19 for each item you want to add.
Use the data recorded in Appendix A for the Product and Images Table 1 for this step.
If you are using multiple pricelists and/or currencies, be sure to add all items to each of
the appropriate price lists.
4. Place your cursor in any of the Product Context fields and click once.
5. Click on the “New” icon.
8. In the Product Value field, query on your first item you want to put on the
price list, this will be the same entry you put in the Item field on the Master
Items form.
11. In the Value field you can enter the Price you are selling the item for on this
pricelist.
12. Click on the “Save” icon after you have entered the item.
13. Repeat steps 5 - 12 for each item you need to add to the price list.
Additional Note: Once you create your first Price List you can use Copy
Price List and Adjust Price List.
If you have chosen to build the Antique Store, your images will need to be uploaded into
the content manager repository. The process for defining images for the products you
want to have displayed and sold through iStore has three main steps:
• Upload your content (image files, HTML files, text, etc.) into Oracle
Content Manager either one at a time or through a bulk load process.
• Define a Media Object and associate the content you have uploaded to that
Media Object. A Media Object acts as a bridge between the image you
upload and the product it is assigned to.
4. On the Create Item page, specify the Content Type of “Image” and enter the
image name and optional description. Next, click on the “Continue” button.
5. The second portion of the Create Item page allows you to specify the file you
want to upload. Click on the “Browse” button and point to the file you need to
upload.
6. Finally, click on the “Submit for Approval” button. The image is then uploaded,
and you can click on the “Preview” button to view its contents.
7. Performing image uploads on a one by one basis can be time consuming when
you have many image files, so the bulk load option is available to make this
process more expedient.
4. Note: The Bulk Upload feature will only look for ZIP files, so you must create the
ZIP file with the images you want to upload prior.
5. On the Bulk Upload page, click on the “Browse” button and point to the ZIP file
on your local system that you want to upload.
6. The second portion of the Bulk Upload page allows you to review and make
changes to the file information being uploaded. You will see all of the files
contained in the ZIP file, and have the ability to change several options, such as
the Content Type, Name of the file, and how to handle conflicts if the image
already exists in the Content Manager repository.
7. Finally, click on the “Submit” button. The images are then uploaded through a
batch job (concurrent process) and will be ready for you to use.
8. A confirmation dialog will be displayed indicating that the bulk load concurrent
process has been invoked. When it has completed, you will see the multiple files
that were uploaded. You can then click on the “Return to Summary page” link
and preview the uploaded files.
9. Now that you have uploaded your images, the next step is to map them to media
objects.
In order to create media objects, one per product image, perform the following steps:
4. Click on the “Create Media Object” button. You will be placed in the Create
Media Object page.
5. For this example, we will be creating a large image media object and assigning it
the large image for the VisionPAd device. When we reference the large image
8. You can enter optional Keywords to make it easier to search for your multimedia
objects.
10. For the Class LOV, choose “Products” from the drop down list, since we are
defining media objects for products associated to your images.
12. When the screen repaints, select the “Add Content” button.
13. You will now be placed on the Add Content page. Find the product
image you want to associate to the media object by entering the Content
Item Name and clicking on the “Search” icon. This will be the name of
the image you uploaded earlier.
14. In the Search and Select Content Item window, find the image you added earlier.
Use the Content Name LOV to search by.
15. You can further refine your search to just look for images by selecting the “View”
LOV and selecting the “Go” button.
16. Click on the “Select” radio button to choose the product image to assign to the
media object.
19. Repeat Steps 3 through 18 until all media objects have been created.
For this step, use the data you recorded in the Items and Images Table 1 and Section
Images Table 2 found in Appendix A.
In order to create associations between products and media objects, perform the
following steps:
4. Find the product you want to associate to the media object by using the product
“Search” field and clicking on the “Go” button.
8. In the Search and Select window for the Media Object, find the Media Object you
defined earlier for the product’s small image. Use the Name LOV.
9. You can further refine your search if needed by selecting the “View” LOV and
selecting “Product”. This will show you just the Media Objects associated to
Products.
10. Click on the “Select” radio button for the Media Object you want to associate to
the product and click on the “Select” button.
Figure 21 Search for the Media Object associated with the Small Image
12. Clicking on the Show Details link below the Product Small Image field will
display the product image associated to that media object. This now completes
the relationship between the product being sold, the media object it is associated
to, and the uploaded image in Content Manager related to that media object.
13. Repeat steps 2 through 11 until you have mapped all images to all the products in
your store via media objects.
7. Once back on the Catalog Hierarchy page, select the Hierarchy link from the
Catalog TAB, Sections Sub-TAB.
8. Ensure the “Select” radio button for the section you created is selected.
9. Click on the “Sections” icon in the Sections column for the section you
just created.
11. After you create the hierarchy, you can change some of the sections from
Navigational to Featured.
12. Continue to build out your hierarchy until it appears similar to the screenshot
below. Be sure to drill down into the Hierarchy Applet and highlight the
appropriate section you want to create subsections under. If you make a mistake
you can use the “Duplicate” button to complete your Specialty Store hierarchy.
13. You are now ready to start adding your items (Products) into your catalog by
placing them into the sections in your hierarchy that you have just created.
1. Login into the HTML Applications as the iStore Administrator. Use the account
ibe_admin / welcome. http://host.domain:port/OA_HTML/AppsLocalLogin.jsp
3. Select the “Create a Site” from the drop down action menu in the Results section.
4. Click on the “Go” button, and you will be placed on the Create Site page.
8. Select Default Walk-in Price List (Corporate) Note: This is only to get your store
started. You may change the price lists later.
10. Select the remainder of the Store flags according to the business rules you want to
include.
12. Your screen will repaint and should appear similar to the following screen:
13. Select the Language link and add any additional languages.
14. Select the Pricing link and change Price Lists if needed. Set the orderable limit
and specify a Payment Threshold amount. Click on the “Apply” button when
finished.
16. Select the Shipping link and specify the Shipping Methods to use in your store.
Click on the “Apply” button when finished.
17. Select the Responsibility link and add the Support Responsibilities based on your
Business Requirements. Click on the “Apply” button when finished.
• Make sure to change the Display Name. The name you choose here will be the
name visible in ibeCCtdMinisites.jsp page.
18. Select the Access link and add Access Restrictions based on your Business
Requirements. Click on the “Apply” button when finished.
Note: Your store site should now be displayed in the list of Specialty Sites.
Note: Related is the only relationship type that works out of the box. The others will
require some code. This relationship can be seen on the Item Details page.
4. Select the value “Create Mapping Rule” from the Rule Type LOV.
7. Select a Product to Product relationship from the pull down action menu
12. The relationship should now appear on the Relationship Details page.
13. You should see the From Product and To Product mapping rule in the Rule
section as a Product to Product relationship.
Figure 37 The Current Store Logo and the New Store Logo
We will first start by uploading the new logo image to the content manager repository.
1. Login into the HTML Applications as the iStore Administrator. Use the
account ibe_admin / welcome.
http://host.domain:port/OA_HTML/AppsLocalLogin.jsp
5. Select “Image” from the Content Type LOV drop down menu.
7. Enter the Content Description for your new store logo image.
9. Click on the “Browse” button next to the Image Attachment field to select the
new logo image source file from your local system to upload.
12. When your screen repaints, a confirmation dialog will be displayed indicating
that the “New Store Logo has been submitted for Approval”. When it has
been uploaded, you will see the logo image file that was uploaded.
Figure 40 New Logo Image Content Uploaded and Ready for Use
Next, we will need to map the new logo image to your store in ALL languages.
3. In the Search field, enter “Store Main” and click on the “Go” button.
6. Enter the Content Item Name that you gave your new store logo when you
uploaded the image file.
8. Click on the “Select” radio button next to the new logo image.
11. Depending on your installation, you may need to “bounce” the web server in
order for the store logo changes to take effect since the store logo is held in
cache memory and needs to be refreshed by stopping and starting the web
server.
12. Here is what the store looks like before the logo change:
3. Open the style sheet in Notepad or WordPad and make your changes.
5. Place your file into the shared directory the instructor created.
6. Let the instructor know your style sheet is ready for upload. It will be loaded in
the $OA_HTML directory.
9. In the Search field, search for the STORE_, and click on the “Go” button.
10. Click on the “Update” icon for the Store Style Sheet.
12. In the Source File Name field enter the name of your CSS file. The name of the
file should not contain any spaces and should have an extension of “.css”.
16. Back on the Template Manager page, click on the “View Mappings” button.
17. You should see your CSS file mapped to your store. Click on the “Return to
Template Detail” link.
18. Depending on your installation, you may need to “bounce” the web server in
order for the style sheet changes to take effect.
20. The following screen shot shows the style of the storefront before the changes
were applied to the cascading style sheet file:
21. After the changes were made to the cascading style sheet file and placed in the
OA_HTML virtual directory, then the web server is “bounced”. Upon re-starting
the application web server, the storefront for the site that you have changed will
have a new appearance.
Oracle iStore ships with hundreds of Customer UI text messages. Text messages for
Oracle iStore are stored in the Oracle Application Object Library (AOL) schema.
You can use Oracle Application Developer to change the messages that appear in your
store. Inform the instructor if you are planning on changing some of the AOL Text
Messages. You must notify your instructor before changing the text, as conflicts can
occur when two or more students are changing AOL message text simultaneously.
Any text message can be changed that the customer sees in the customer user interface.
Some examples are:
IBE _PRMT_CALL_ME_BACK Have us call you back message in the Welcome Bin
IBE_PRMT_PHONE_COL Phone:
1. Login into the HTML Applications as the ERP Administrator using username /
password (ebusiness / welcome)
http://host.domain:port/OA_HTML/AppsLocalLogin.jsp
4. If you know the name of the Message, query for it in the Name field.
5. If you know what the current message is you can query for it in the Current
Message Text field.
6. If you don’t know the name of the message, click on the “Flash Light” icon to
find the message you want to change.
8. Change the message from “Have us call you back” to “We can contract you by
phone if you like.”
9. Once the message you wish to change is displayed, replace the message showing
in the Current Message Text field with your new message.
Figure 52 The Original Text and the New Text in the Welcome Bin
• Shipping Instructions
1. Login into the HTML Applications as the ERP Administrator using username /
password (ebusiness / welcome)
http://host.domain:port/OA_HTML/AppsLocalLogin.jsp
11. The following is a list of the profiles to change and their profile option name in
the system:
4. If you encounter any errors, missing images, etc, please go back and resolve those
issues and continue with testing your store.
5. As a final test, add items to your cart and checkout obtaining an Order Number
from Order Management.
If the Specialty Store you are building will be based on the Antique Store, use the table
above to create the section level multimedia components for your store. The files listed in
the Source File column already exist in the file system; therefore, you will not need to
upload them. You will simply be creating the Name and Programmatic Name for them.
To accomplish navigate to the Multimedia tab of the iStore Administrator UI.
Allow un-registered users to browse the store: gives guest users the ability to browse
the site without having to go through the registration process. By selecting this flag when
creating a site, the administrator will allow guest user access.
ATP Enabled: allows end users to check for product availability. By selecting the
“Allow customers to check item availability” flag when creating a site, the administrator
will allow the user to see if the product being purchased is available in inventory.
Check User Responsibility: control user responsibility before accessing the store.
Content Components: are used for products and sections, and can be looked at as
attributes that accept media; for example, a product content component allows the
administrator to assign media to a product’s large image, small image, HTML text, etc.
There are several out-of-the-box content components that are shipped with iStore, and the
administrator has the ability to define their own custom content components.
Display Styles: determine the manner in which a product appears on the storefront. For
instance, the iStore Administrator may want to display clearance items. The layout of
these items depends on the template created for each style. After the templates are
created, and filed on the server side, the administrator will associated the template to a
logical name created for the display style.
Enable Reporting: when creating a site, the purpose of this flag is to enable site metrics
to be visible in Oracle Web Analytics reports. This flag only displays if integration with
Oracle Web Analytics has occurred.
Enable Traffic Filter: when creating a site, the purpose of this flag is to allow visits
from IP addresses entered as traffic filters in Oracle Web Analytics.
Multimedia: objects that consist of files such as graphics, images, and text that are used
to present content on a Web page. The Multimedia page lists the existing multimedia
objects along with their programmatic access name, keywords, descriptions, and the
default source files mapped to all specialty stores and languages.
Multimedia Components: define the types of multimedia objects available for display
on a Web page, such as an image of a certain size or a short text description. They are
called by the store Web page templates to determine which multimedia appears on a
given store page. You can assign default and specific multimedia object at the product,
section and store levels.
Relationships: are used for merchandising, for example, to offer a substitute product for
a product that is out of stock. Relationship types are used to create specific relationship
rules that associate products, categories and sections.
Restrict customer access by responsibility: when creating a site, selecting this flag will
impose that the site will check the customer’s responsibility.
Root Section: the section folder specifically created for this store. You can associate a
specialty store to a portion of the overall hierarchy or to the whole hierarchy itself by
setting up its root node to point to a section.
Section Hierarchy: the hierarchy determines the organization of the specialty stores and
their sections and products in the Administrator UI. It also determines the organization
and presentation of each store’s sections and products in the Customer UI and, therefore,
the browsing experience of the customer and what products are featured at different
levels in the stores. When users come to a specialty store, they see the hierarchy starting
from the root node of the store.
Section Hierarchy Code: represents the unique section identifier. It specifies a Section
Code to use as a name for the section in customized template.
Section Hierarchy Name: the name of the section being displayed in the Customer UI
for a given section. It is mandatory but not unique, since in a multi-language installation
you can translate it according to the session language.
Section Hierarchy Type: can be featured or navigational. This is a featured section that
appears on the home page of its parent section. A navigational section appears as link in
the browsing map of its parent section.
Templates: control the appearance of the store through the use of JavaServer Pages.
iStore comes packaged with a complete set of JSP templates needed to run the store. If
you want to expand the functionality of the store Web pages or customize the pre-
packaged templates, then you need to identify the flow of the application and the JSP
templates need to implement the flow.
Walk-in customer enabled: allows non-registered users to browse the store and create a
shopping cart. Users will have to register before they can perform the check out process
and place an order.
3. Set the Home Folder and Current Folder to the directory where you will be
storing the images. Click on the “Folder Properties” button.
4. You will receive a list of all users that can access content and their permissions.
If user IBE_ADMIN is not on this list, click on the “Add Another Row” button.
5. Select the Type = “User” and enter IBE_ADMIN in the Name field. Then click
on the “Search” icon and select IBE_ADMIN.
6. Assign all permissions by selecting the checkboxes for the various permissions to
IBE_ADMIN.
2. Click on the FVWM link under Linux Session Servers. This will open up a framework
session.
3. Left mouse click and select Shells, XTERM, and log in to your UNIX home.
4. Login to the environment where the source ibeCStyleSheet.css exists. Example: ssh -l
app1600 rws60184rems.us.oracle.com
5. Change the directory so that you can access the ibeCStyleSheet.css file. Example: cd
$OA_HTML
7. List the ibeCStyleSheet.css file to make certain that it is in the current directory.
Example: ls ibeCStyleSheet.css
8. Open up a second XTERM session by performing a left mouse click. You will be placed
in your home directory.
9. Create a folder where you will make changes to the copy of the ibeCStyleSheet.css file
and change the permissions and user mask of the folder. Example: mkdir temp chmod 777
temp cd temp
10. Make a copy of the ibeCStyleSheet.css file by placing it into your home directory folder
that you just created in session one. Example: cp ibeCStyleSheet.css /home/<yourlogin>/temp
12. Instead of using the UNIX editors, it is much easier to map the UNIX folder as a network
folder and access it from your PC to make your changes. This requires that you map the
UNIX environment as a network drive from your PC. To do this, you need to find out
the location of your UNIX environment. Open up a third UNIX session and issue the
following command: df lgrep <yourlogin>. This will tell you the location of your UNIX
environment. Example: ap142nap:/vol/home6/<yourlogin>
14. Select the letter of the Drive you want to map to and enter the Folder information (this is
the location of your UNIX environment). Example: ap142nap:/vol/home6/<yourlogin>
15. You can now access the copy of the ibeCStyleSheet.css file and directly edit it.
16. When you are through making the changes to the copy of the ibeCStyleSheet.css file,
move it back from your UNIX directory to the OA_HTML directory. Example: cp
/home/<yourlogin>/temp/Bobs_Store_Style_Sheet.css .