Create a Site
1. Begin the site creation process by entering basic information for a site, such as name, description, and default parameters.
Note: To remove a site from operation, you must end-date it.
• Sections which contains at least one navigational subsection
• Sections which are leaf sections (contain only products, not subsections)
• Sections which only have featured subsections; Oracle iStore does not support this
• Unpublished or non-active sections, as this will cause incorrect rendering in the Customer UI
2.1 Assigning Price Lis
Price lists must be set up in the pricing application before they can be selected in the Site Administration UI. Since the iStore Administration Application is not operating unit (OU) aware, the list of available price lists displays all existing price lists. If a price list is set up as OU-specific, then be sure to associate this price list only to sites whose associated customer responsibilities are linked to the OU where the price list is enabled.
• The price lists selected in the Pricing page are used to fetch prices only when the pricing is site-based (i.e., IBE: Use Price list Associated with Specialty Site is Yes).
• For each supported currency, choose the price lists for Walk-in Customers (guest users), Individual Customers (B2C users), Business Customers (B2B users), and Partners (Oracle Partner Management end users).
• If multi-currency price lists are enabled, you can choose the same price list for a different currency.
• You cannot remove the default currency.
2.2
Assigning Payment TypesPayment types must first be set up in Oracle Applications before they can be selected in the Site Administration UI. Only the payment types supported by a site will display in the Customer UI.
Shipping methods must be set up in Oracle Forms’ Shipping menus before they will display in the Site Administration UI. Only the shipping methods supported by a site will display in the Customer UI.
You must assign at least one customer responsibility to a site. Each iteration of a site plus a responsibility makes a specialty site. The display names you select in this phase of the site building process appear in the Customer UI as the specialty sites’ display names.
A single Customer UI responsibility is seeded for the default customer user; it is IBE_CUSTOMER. This responsibility is associated to all available Oracle iStore user types by default during registration. When you create a site, IBE_CUSTOMER is
assigned to the site by default.
Oracle iStore also supports using Oracle iSupport and Oracle Partner Management responsibilities for Customer UI users. If you wish to assign other responsibilities to customers, you must change user types setup, defining new Oracle CRM User
Management enrollments associated to the user types and mapping the corresponding responsibilities to the appropriate sites.
Oracle iStore allows you to organize speciality sites into groups. The Site Selection Page page in the Customer UI will display the specialty sites within a site according to groups that you place them in. You also can assign a single speciality site to
multiple groups.
3.2 Organization Access
Access restrictions allow you to control a B2B user’s access to the Customer UI based on his organization. When you use access restrictions, you do one of the following:
- Restrict access to a site based on users’ organization(s) affiliation.
- Allow only users from a certain organization(s) to access a site.
- No restriction: Select this radio button to have no organization-related access restrictions on the site.
- Exclude the following organizations: Select this radio button to restrict access to the site by users associated with the organization(s) you specify.
- Include the following organizations: Select this radio button to allow access to the site only by users associated with the organization(s) you specify.
Comments
Post new comment