br100aibe istore application setup

8/8/2019 BR100Aibe iStore Application Setup

1/21

AIM

BR.100AIBEISTORE APPLICATIONSETUP

Author:

Creation Date: July 19, 2000

Last Updated: July 19, 2000

Document Ref:

Version: DRAFT 1A

Approvals:


2/21

BR.100Aibe iStore Application Setup

Document Control

Attention: The CRM BR100 Application Setup Documents area work in process. As such, some of the content may not be inits final form. If you have comments or suggestions forimproving this template please send them [email protected].

Change Record

5

Date Author Version Change Reference

19-Jul-00 Draft 1a No Previous Document

Reviewers

Name Position

Distribution

CopyNo.

Name Location

1 Library Master Project Library

2 Project Manager3

Note To Holders:

If you receive an electronic copy of this document and print it out, pleasewrite your name on the equivalent of the cover page, for documentcontrol purposes.

If you receive a hard copy of this document, please write your name onthe front cover, for document control purposes.

File Ref: 49708432.doc (v. DRAFT 1A )

Create Hierarchy

Doc Ref: July 19, 2000


3/21

BR.100Aibe iStore Application Setup

Contents

Document Control.......................................................................................ii

Application Set Up Control Sheet - iStore...................................................1

Define System Profiles................................................................................2

Create Specialty Store................................................................................5

Create Store UI / Identify Templates...........................................................7

Create Content............................................................................................8

Define Multimedia Components..................................................................9

Define Display Types................................................................................10

Create Multimedia....................................................................................11

Create Templates.....................................................................................12

Create Hierarchy.......................................................................................13

Create Store Content / Build Product Relationships..................................15

Setup Configurator....................................................................................16

Run Concurrent Programs.........................................................................17

Open and Closed Issues for this Deliverable.............................................18

Open Issues.........................................................................................18Closed Issues.......................................................................................18

File Ref: 49708432.doc (v. DRAFT 1A )

Create Hierarchy

Doc Ref: July 19, 2000


4/21

Application Set Up Control Sheet - iStore

Environment Name: Machine: Type (definition, execution, orboth):

Workflow

SubWorkflow Name

Set Up Task Responsibility Due Date QA Responsibility QA Due Date SignatureApproval

Profile Options Setup Profile

Specialty Store Create Specialty store

Store UI Identify templates

Store UI Create content

Store UI Define Multimedia Components

Store UI Define display styles

Store UI Create multimedia

Store UI Create templates

Store content Create Store hierarchy

Store content Build Product Relationships

Shipping options List Shipping options

Payment options List Payment options

Configurator setup Setup Configurator

Concurrent Manager Run Concurrent Programs

File Ref: 49708432.doc (v. )

Create Hierarchy

Doc Ref:


5/21

Define System Profiles

Forms> Profiles>

Form

Name Process:

Business Area:

Date:

Control Number:

Priority(H, M, L):

Process Owner:

Description: Use this form to define System Profile options.

Attention: This is reached through Forms

Warning: IBE_ITEM_VALIDATION_ORG must be set. This is theinventory or used to create the product catalog

Warning: IBE_CATEGORY_SET_ID must be set. Required to setupthe display styles and multimedia components at category level

Profile Name Default Value User Value

IBE: One Click Consolidation Time Interval

IBE: One Click Error Behavior

IBE: Cache

IBE: Enable Preloading of Cache for Catalog

IBE: Category Set

IBE: Number of Days for New Item Definition

IBE: Default Display Context

IBE: Default Item Media

IBE: Default Section Media

File Ref: 49708432.doc (v. )

Create Hierarchy

Doc Ref:


6/21


IBE: Line Level Pricing Event for Shopping Cart

IBE: Pricing Event for Shopping Cart

IBE: Items Per Page for Display

IBE: Item Cache Size

IBE: Default Item Template

IBE: Item Validation Organization

IBE: Notification User Role

IBE: Authorize Payment Offline during normalCheckout

IBE: Capture Payment for Downloadable products

IBE: Finalize Order On Error in Authorize Payment

IBE: Pricing Event -- Before Shopping Cart

IBE: Request Type to get a Price

IBE: Retrieve Price When Displaying Items

IBE: Reserve Items On Every One Click

IBE: No of Results in Search

IBE: Days For Email

IBE: Add number of rows to direct entry cart

IBE: Shopping Cart Expiration Duration

IBE: Maximum Number of Saved Shopping Carts

IBE: Maximum Number of Shopping Lists

File Ref: 49708432.doc (v. )

Create Hierarchy

Doc Ref:


7/21


IBE: Shopping Cart Price based on Owner

IBE: Shopping Cart Price Frozen Duration

IBE: Search Lines Per Page

IBE: Sections Per Page for display

IBE: Section Cache Size

IBE: Default Section Template

IBE: Top Number of Items

File Ref: 49708432.doc (v. )

Create Hierarchy

Doc Ref:


8/21

Create Specialty Store

Setup> Specialty StoresForm

Name Process:

Business Area:

Date:

Control Number:

Priority(H, M, L):

Process Owner:

Description: Specialty Stores are analogous to store fronts and have a display catalog

Warning: Each Specialty Store must have a root node, which has not been created. As a workaround, leavethe root id blank, proceed to the step Choose root node and then return

abSpecialty Stores

Remove Specialty Store Name Description

CreateBasic Information

Specialty StoreName

Description Enabled forStore

Languages Default Language

File Ref: 49708432.doc (v. )

Create Hierarchy

Doc Ref:


9/21

Continue

Responsibilities TDB

ContinueStore Flags

ATP Enabled Walkin Customers enabled Root Section

File Ref: 49708432.doc (v. )

Create Hierarchy

Doc Ref:


10/21

Create Store UI / Identify Templates

Outside StoreForm

Name Process:

Business Area:

Date:

Control Number:

Priority(H, M, L):

Process Owner:

Description: This step involves identifying the JSP templates needed to run iStore. The out-of-the-box application comes packaged witha complete set of templates needed to run the store. If the customer wants to expand the functionality or wishes to customize the pre-packaged templates, the customer will need to identify the flow of the application and identify the JSP templates needed to implementthe flow.

Note: Leave this blank if you are running iStore out of the box

Area Template Sub-Template Navigation Description Location

File Ref: 49708432.doc (v. )

Create Hierarchy

Doc Ref:


11/21

Create Content

Outside StoreForm

Name Process:

Business Area:

Date:

Control Number:

Priority(H, M, L):

Process Owner:

Description: This step involves determining the products the merchant wants to sell on his web site and entering description for theproducts that will be sold on the web. It also involves creating images and other multimedia that will used in the templates.

Multimedia file Description Location

File Ref: 49708432.doc (v. )

Create Hierarchy

Doc Ref:


12/21

Define Multimedia Components

Setup > Multimedia SetupForm

Name Process:

Business Area:

Date:

Control Number:

Priority(H, M, L):

Process Owner:

Description: This step involves creating multimedia components that will needed to present the items and sections in the store. AMultimedia Component is used to determine the physical multimedia that will be used to present an item or section based on somecontext. An item or a section can use different physical multimedia by switching the multimedia component. Creation involves specifyingthe name and description for the component and specifying the default multimedia that will be used for it.

Note: Leave this blank if you are using the multimedia componentsbundled with webstore

abMultimedia Setup

Remove Name Programmatic accessname

Description < name notfinalized>

Default source file

Create

Name Programmatic Access Name Description < name not finalized>

Update

File Ref: 49708432.doc (v. )

Create Hierarchy

Doc Ref:


13/21

Define Display Types

Setup > Display StylesForm

Name Process:

Business Area:

Date:

Control Number:

Priority(H, M, L):

Process Owner:

Description: This step involves creating display styles that will needed to present the items in the store. A Display Style is used todetermine the template that will be used to present an item based on some context. An item can be displayed differently using differenttemplates by switching the display style based on some context. An item can be displayed differently using different templates byswitching the display style. Creation involves specifying the name and description of the display style and specifying the default templatethat will be used for it.

Note: This step is optional because the product ships with a set ofdisplay styles

abDisplay Styles


Description < name notfinalized>

Default sourcefile

Create

Name Programmatic accessname

Description < name not finalized>

Update

File Ref: 49708432.doc (v. )

Create Hierarchy

Doc Ref:


14/21

Create Multimedia

MultimediaForm

Name Process:

Business Area:

Date:

Control Number:

Priority(H, M, L):

Process Owner:

Description: This step involves adding new multimedia that will replace or add to the multimedia already available in the base product.It involves adding the name and description for these new multimedia and also specifying the different multimedia that will be used atrun-time based on language and the specialty store.

Note: This is an optional step because the out-of-the-box productcomes packaged with a set of multimedia.


Keywords Description Displays Default source file

Create


Description Default source file Keywords Displays

Update

File Ref: 49708432.doc (v. )

Create Hierarchy

Doc Ref:


15/21

Create Templates

TemplatesForm

Name Process:

Business Area:

Date:

Control Number:

Priority(H, M, L):

Process Owner:

Description: This step involves adding new templates that will replace or add to the templates already available in the base product. Itinvolves adding the name and description for these new templates and also specifying the different physical JSP templates that will beused at run-time based on language and the specialty store.

Note: This is an optional step because the out-of-the-box productcomes packaged with a set of templates.


Keywords Description Displays Default source file for all sites andlanguages

Create


Description Default source file Keywords Displays

Update

File Ref: 49708432.doc (v. )

Create Hierarchy

Doc Ref:


16/21

Create Hierarchy

HierarchyForm

Name Process:

Business Area:

Date:

Control Number:

Priority(H, M, L):

Process Owner:

Description: This step involves adding new sections and associating display styles and templates to them

Note: When clicking on Hierarchy for the first time, there will be noentries in the hierarchy tree

Warning: Specialty store table (JTF_MSITES_B) should be seededwith an entry with master_msite_flag set to Y.


Name Section Code Section type Short description Long Description Template Display Style

Update

Note: After creating a root node, go back to Setup > Specialty Store> Store flags and set the root node

UpdateAdd Sections

File Ref: 49708432.doc (v. )

Create Hierarchy

Doc Ref:


17/21

Remove Part Number Name Published flag Start date End date

Add Product

Warning: Make sure that FND_LOOKUPS for section type(JTF_SECTION_TYPE) is defined with 2 seeded lookup codes forNavigational and Featured. New lookups codes can be added basedon the merchants requirement.

Select products

Search Criteria A Search criteria B

Go

Select Name Part Number Category Status

Add

Done

File Ref: 49708432.doc (v. )

Create Hierarchy

Doc Ref:


18/21

Create Store Content / Build Product Relationships

RelationshipsForm

Name Process:

Business Area:

Date:

Control Number:

Priority(H, M, L):

Process Owner:

Description: This page shows all the seeded and user-defined relationships. For the seeded ones, you can enter item relationshipseither from Inventory form or from this iStores page. For user-defined ones, you must use iStores page, used to create a relationshipand its rules. A SQL rule selects inventory item id from MTL_SYSTEM_ITEMS table. You can specify any WHERE conditions and join withother tables. The mapping rules have from-to format and you can specify an item, a category, or a section in the from and to part.When you view the result of the relationship, you will not see the item relationships defined in Inventory.

Warning: All the bind variables should start with a colon.

Warning: A relationship can have either a SQL rule or multiplemapping rules, but not both of them.

Remove Part Number Name Published flag Start date End date


File Ref: 49708432.doc (v. )

Create Hierarchy

Doc Ref:


19/21

Setup Configurator

FormsForm

Name Process:

Business Area:

Date:

Control Number:

Priority(H, M, L):

Process Owner:

Description: This complete guide is located at http://www-apps.us.oracle.com/cz/prod_docs/released/czag_html/toc.htmA URL that will handle all interaction between the client and the server. For example, this could be http://apps-server-host/apps/cz/oracle.apps.cz.servlet.UiServlet The server and directory structure is installation information that the calling applicationmust read, but the oracle.apps.cz.servlet.UiServlet portion will always be the same. This URL should be read from the CZ_UIMGR_URLprofile variable.

File Ref: 49708432.doc (v. )

Create Hierarchy

Doc Ref:


20/21

Run Concurrent Programs

Concurrent ManagerForm

Name Process:

Business Area:

Date:

Control Number:

Priority(H, M, L):

Process Owner:

Description: Choose the iStore concurrent programs responsibility and run the associated concurrent programs

File Ref: 49708432.doc (v. )

Create Hierarchy

Doc Ref:


21/21

Open and Closed Issues for this Deliverable

Open Issues

ID Issue Resolution Responsibility Target Date Impact Date

Closed Issues

ID Issue Resolution Responsibility Target Date Impact Date

Doc Ref: