iStore- Steps to create a Basic Store

Posted by Apurva at 1:30 AM Read our previous post

Steps to Create a Basic Store

Note: All of the following steps are performed in the Store Administration UI as the iStore Administrator.

Step 1: Enter basic store information

This step involves entering:

•          Store Name --- This should be your company’s internal name by which the store is known; this name will not appear to customers.

•          Store Code --- Store code functionality is reserved for future use. Currently, any value you enter here would be used for your company’s own internal purposes.

•          Description --- This should be an internal description; this description will not appear to customers.

•          Start Date --- Using the calendar icon, select the date when the specialty stores of this store should first be active and available to customers in the Customer UI. This will default to system date. The start date of a specialty store can also be controlled by setting the supported responsibility (specialty store) start date.

•          End Date --- Optionally, use the calendar icon to select the date the specialty stores of this store should no longer be active and available to customers in the Customer UI. To remove a store from operation, end-date it. The end date of a specialty store can also be controlled by setting the supported responsibility end date.

•          Default Language --- This textbox will display the current default language for the store. To select a different default language: Select the flashlight icon to launch the Select: Languages page, where you can select from a list of installed languages. Except for the default language known as the base language, languages must first be installed and then set up in Oracle Applications before they appear in the Store Administration UI.

•          Default Currency --- Select a default currency for the store. This is a mandatory field. The default currency can be changed using the store Pricing page. Select the flashlight icon to launch the Search and Select: Currencies page, where you can select from a list of implemented currencies. Currencies are set up during implementation of Oracle General Ledger. Until they are set up, currencies will not appear in the Store Administration UI.

•          Default Walk-in Price List --- Select a default price list for walk-in (guest) users of the store. This is a mandatory field. The price list assignment can be changed using the store Pricing page. Use the flashlight icon to launch the Search and Select: Price Lists page, where you can select from a list of implemented price lists within your organization.

•          Catalog Root Section --- In this step, you select the parent node (or browsing section) under which this store resides. This is a mandatory field. Use the flashlight icon to launch the Search and Select: Sections page, where you can select a parent section for the store. The default parent section also can be changed using the Update Store: Details page.

This step also involves determining whether to enable the following features:

•          Allow un-registered users to browse the store --- Selecting this checkbox allows unregistered users (also called guest users and walk-in users) to navigate within this store’s specialty stores. Guest users cannot place orders, but can add items to the shopping cart. If you do not select this box, then guest users will not see the specialty stores within this store on the Specialty Store Page.

•          Allow customers to check item availability ---  Selecting this checkbox allows users to check Available to Promise (ATP) information for products. Do not select this unless you have set up either Regular or Global ATP.

•          Restrict customer access by responsibility --- Selecting this checkbox makes all specialty stores within this store check user responsibility when customers enter the specialty store. If you select this, then specialty stores within this store will only grant access to those users whose responsibilities are supported by the specialty store.

•          Enable Threshold for Payment Types --- Selecting this checkbox begins the enabling process for Payment Threshold feature in all specialty stores within this store. This feature allows you to set a monetary amount and then select which payment types can be used when users place orders below that amount. There are additional steps to set up this feature; it is covered fully later in this lesson.

Note: Upon creation, your store will be given a unique number, which you can view in the Store ID field in the Update Store: Details page. The Store ID is the same as the Minisite ID.

Step 2: Assign Languages

In this step, you select additional languages for the store. This is optional. To enable additional languages, you must first install and then set up the languages in Oracle Applications. In addition, your implementation must be multi-org enabled.

Step 3: Assign Currencies

In this step, you select currencies for the store. Currencies must be set up in Oracle General Ledger before they can be selected in the Store Administration UI.

Step 4: Assign Price Lists

In this step, you select price lists for the store.  Price lists must be set up in Oracle Order Management Basic Pricing module or Oracle Advanced Pricing before they can be selected in the Store Administration UI.

Step 5: Assign Payment Types

In this step, you select the payment types that the store will support. Payment types must first be set up in Oracle Applications before they can be selected in the Store Administration UI.

Step 6: Assign Shipping Methods

In this step, you assign the shipping methods supported by the store. Shipping methods must be set up before they will display in the Store Administration UI. Only the shipping methods supported by a store will display in the Customer UI.

Step 7: Assign Responsibility/Enter Name

You must assign at least one Oracle iStore customer responsibility to a store. Each iteration of a store plus a responsibility makes a specialty store. The display names you select in this phase of the store building process appear in the Customer UI as the specialty stores’ display names.

Oracle iStore ships with a default responsibility for the Customer UI. This responsibility is IBE_CUSTOMER. When you create a store, Oracle iStore automatically maps this responsibility to the store. If you wish, this responsibility assignment can be removed in the Responsibilities page.

Step 8: Build Catalog

After creating a store, you can begin building the store section hierarchy and assigning products to the catalog.