Skip Headers

Oracle iStore Implementation and Administration Guide
Release 12.1
Part Number E13575-06
Go to Table of Contents
Contents
Go to previous page
Previous
Go to next page
Next

Seeded User Data

This appendix covers the following topics:

Overview of Seeded User Data Appendix

This appendix lists the seeded Oracle Forms, Oracle CRM Applications, and Oracle iStore Site Administration and Customer Application users and responsibilities necessary to implement Oracle iStore.

Understanding Oracle Applications Responsibilities

User names and responsibilities are set up in Oracle Applications to secure access to the data and functionality within the applications. The key element in Oracle Applications security is the definition of a responsibility. A responsibility defines:

The system administrator defines application users and assigns one or more responsibilities to each user. In the Oracle iStore context, the system administrator may be you or another person.

See Oracle Applications System Administrator's Guide and Oracle Applications User's Guide for more information on how to set up user names and responsibilities.

All Oracle Applications products are installed with predefined responsibilities known as seeded responsibilities. Consult the implementation or reference guide for your Oracle Applications product for the names of those predefined responsibilities.

Oracle Forms Responsibilities for Oracle iStore Setup

Access Oracle Forms by navigating to:

http://<host>:<port>/

and selecting Apps Logon Links > VIS Logon through the Forms cartridge. Log in with the appropriate user name and responsibility to perform the specified tasks.

The following table summarizes the responsibilities necessary to perform setup and administrative tasks for Oracle iStore in Oracle Forms.

Oracle Forms Responsibilities
Responsibility Tasks
AK Developer Define regions in Apps to troubleshoot Postsales errors.
Application Developer Enable or disable B2B or B2C user registration.
Modify specialty site text messages.
Set up descriptive flexfields to appear on item detail pages.
Set up comment flexfields to appear on the checkout page.
Apps for the Web Manager Define regions in Apps to troubleshoot Postsales errors.
General Ledger Super User Set the daily currency conversion rate and create calendars in Oracle General Ledger for iStore Reports.
Inventory responsibility Inventory setups.
iStore Concurrent Programs Responsibility Schedule or run iStore concurrent programs
Order Management Super User Set up Oracle Order Management.
Receivables Manager Set up Oracle Receivables.
System Administrator Set profile options. Set up Oracle iStore administrator and guest user accounts. Check the status of concurrent program requests. Set up credit card payments in Oracle iStore.

Oracle E-Business Suite Responsibilities for Oracle iStore Setup

Access the Oracle CRM Login Servlet login page at:

http://host:port/oa_servlets/oracle.apps.jtf.base.session.CRMLogin

Log in with the appropriate user name and responsibility to perform the specified tasks.

The following table summarizes the user names and responsibilities necessary to perform setup and administrative tasks for Oracle iStore in Oracle CRM Applications.

Oracle E-Business Suite HTML Applications Users and Responsibilities
User Responsibility Tasks
<Site Manager User Account> iStore Administrator
IBE_ADMINSTRATOR
Logging in with this responsibility launches the Oracle iStore Site Administration UI.
All tasks within the Site Administration UI.
SYSADMIN Foundation (HTML) Administration
Logging in with this responsibility launches the Oracle CRM System Administrator Console.
Set up Oracle CRM System Administrator Console
Set up default roles and responsibilities for customer users.

Oracle iStore Customer UI Responsibilities

At least one customer responsibility is assigned to each customer name when the name is approved during user registration. You can use the seeded IBE_CUSTOMER responsibility and create other customer responsibilities too.

In a multiple operating unit environment, you need to create a customer responsibility for each operating unit if you want a customer to access only items from the Inventory Organization specific to each operating unit.

In the Site Administration UI, you can specify a list of the customer responsibilities that are supported by a given site. You can select these from all existing iStore responsibilities. You can also specify, for a given site, whether Oracle iStore checks the customer's responsibilities and grants access only if the customer has an assigned responsibility that is supported by the site.

If multiple responsibilities are supported by a site, a customer who logs in to the site must choose one responsibility for that session. The responsibility uniquely identifies the operating unit against which any orders placed during the session will be booked. The responsibility is assigned only for the current session.

If you set up a site to check the customer's responsibility, the customer can choose only from the responsibilities that have been assigned to him or her during registration. If the site is not set up to check the customer's responsibility, then the customer can choose any supported responsibility in any site that does not check the customer's assigned responsibilities.

The following table summarizes the responsibilities seeded by Oracle iStore for Web site customers to use in the Customer UI, located at:

http://<host>:<port>/OA_HTML/ibeCZzdMinisites.jsp

Oracle iStore Customer UI Users and Responsibilities
User Responsibility Tasks
<Guest User Account> IBE_CUSTOMER The guest user name is assigned to every customer who browses the site without registering. You must assign the IBE_CUSTOMER responsibility or another customer responsibility as a default for guest users.
<Customer User Account> IBE_CUSTOMER Select IBE_CUSTOMER or another customer responsibility to be assigned by default to every registered customer.

Oracle iStore Customer UI Roles and Permissions

This section lists the permissions that a shipped within each seeded user role.

Business User Role Seeded Permissions

The following are the permissions seeded and supported in the B2B user role, iStore Business User Role (IBE_BUSINESS_USER_ROLE). Note that several unsupported permissions may appear in this role out-of-the-box; the unsupported permissions are listed later in this chapter.

Note: The B2B role for previous releases, IBE_DEFAULT_ROLE, is also seeded in Oracle iStore, for backward compatibility.

Primary User Role Seeded Permissions

The following are the permissions seeded in the iStore Primary User Role (IBE_PRIMARY_USER_ROLE). Note that several unsupported permissions may appear in this role out-of-the-box; the unsupported permissions are listed later in this chapter.

Oracle iStore B2B User Permissions

This section describes the seeded role permissions that are supported for use in Oracle iStore.

Note: Some permissions enable certain UI objects to appear in the Customer UI, for the users with those permissions. For example, a user with IBE_CHANGE_BILLTO_CONTACT permission will see a Change button in the shipping and billing information pages. Similarly, a customer with IBE_CANCEL_ORDER permission will see a Cancel button next to orders that are cancellable in the Order Tracker pages. For users without these permissions, these UI objects do not appear.

Important: Roles (and thus permissions) do not apply to B2C users. When they register, they automatically receive their default Customer UI permissions, which are the same as the B2B permissions with a few exceptions in cart permissions. See the chapter, "Implementing Carts and Orders", for more information.

Oracle iStore-Specific Permissions

Following are the supported iStore-Specific B2B user permissions. Descriptions of each permission can be found later in this chapter.

Common Permissions

Following are the supported common B2B user permissions. Common permissions are those shared by Oracle iStore and other integrating applications. Descriptions of each permission can be found later in this chapter.

Oracle Common Application Components Permissions

See the section, "JTF_PRIMARY_USER_SUMMARY", later in this chapter.

Oracle iStore B2B User Permissions Descriptions

Following are the descriptions of the B2B user permissions:

IBE_ASK_SALES_ASSISTANCE

Allows a user to request sales assistance in the checkout phase, and to disagree with terms and conditions. If a user does not have this permission, he will not see the Need Salesrep Assistance button in the Order Review page, nor will he see the I disagree - Need Assistance button in the Review Terms and Conditions page.

IBE_ASSIGN_SITES

Controls the ability by primary users to assign sites to other users in the Sites > Assign Access pages (within the Contact Management menu).

IBE_BILLTO_ANY_ACCOUNT

Allows a customer to search on and retrieve all existing customers rather than only those with an existing billing relationship with the sold-to customer. Note that "all existing customers" is restricted to customers that have a valid party relationship of type 'CUSTOMER_OF' with the sold-to customer, as well as any customer that has a billing account relationship with the sold-to customer.

IBE_CANCEL_ORDER

Allows users to cancel their own orders that are in Booked or Entered state in Oracle Order Management. Enables the display of the Cancel Order button.

Note: If you wish to enable Cancel Order for B2B users who were created before Oracle Applications Release 11.5.8, you must manually add the IBE_CANCEL_ORDER permission to the user roles.

IBE_CANCEL_ORGANIZATION_ORDER

Allows users to view and cancel orders for their current session operating unit and other operating units within their organization.

IBE_CHANGE_BILLTO_CONTACT

Allows a user to change the bill-to contact name from the default (if any) bill-to contact name. This permission works in tandem with IBE_CHANGE_BILLTO_CUSTOMER.

IBE_CHANGE_BILLTO_CUSTOMER

Allows a user to change the bill-to customer from the default bill-to customer.

Note: If you explicitly grant this permission to a user, you should also grant the IBE_CHANGE_BILLTO_CONTACT permission to the user.

IBE_CHANGE_END_CUSTOMER

Allows a user to change the end customer.

IBE_CHANGE_END_CUST_CONTACT

Allows a user to change the end customer contact.

IBE_CHANGE_SHIPTO_CONTACT

Allows a user to change the ship-to contact name from the default (if any) ship-to contact. This permission works in tandem with IBE_CHANGE_SHIPTO_CUSTOMER.

IBE_CHANGE_SHIPTO_CUSTOMER

Allows a user to change the ship-to customer from the default ship-to customer.

Note: If you explicitly grant this permission to a user, you should also grant the IBE_CHANGE_SHIPTO_CONTACT permission to the user.

IBE_CHECKOUT

Allows a user to see and use the Checkout button in shopping cart.

IBE_CREATE_BILLTO_CONTACT

Allows the user to create a new contact name for the bill-to customer who will have a bill-to relationship with the bill-to customer.

IBE_CREATE_BILLTO_CONTACT_ADDRESS

Allows the user to create a new address associated with the bill-to contact which will have a bill-to relationship with the bill-to contact.

IBE_CREATE_BILLTO_CUSTOMER

Allows a user to create a new customer with a billing relationship to the sold-to customer.

IBE_CREATE_BILLTO_CUSTOMER_ADDRESS

Allows the user to create a new address associated with the bill-to customer which will have a bill-to relationship with the bill-to customer.

IBE_CREATE_END_CUSTOMER_CONTACT

Allows a user to create the end customer contact.

IBE_CREATE_END_CUSTOMER_CONTACT_ADDRESS

Allows a user to create the end customer contact's address.

IBE_CREATE_END_CUSTOMER

Allows a user to create the end customer.

IBE_CREATE_END_CUSTOMER_ADDRESS

Allows a user to create the end customer address.

IBE_CREATE_ORDER

Allows a user to submit a quote or cart as an order by pressing the Place Order button. If a user has this permission, ensure that he has the IBE_CHECKOUT permission as well, since without IBE_CHECKOUT the user will not see a Checkout button to enter the checkout phase.

IBE_CREATE_RETURN

Allows users to view and create returns from orders placed by themselves. Enables the Create Return button in the Returns summary page.

IBE_CREATE_SHIPTO_CONTACT

Allows the user to create a new contact name for the ship-to customer who will have a ship-to relationship with the ship-to customer.

IBE_CREATE_SHIPTO_CONTACT_ADDRESS

Allows the user to create a new address associated with the ship-to contact which will have a ship-to relationship with the ship-to contact.

IBE_CREATE_SHIPTO_CUSTOMER

Allows a user to create a new customer with a shipping relationship to the sold-to customer.

IBE_CREATE_SHIPTO_CUSTOMER_ADDRESS

Allows the user to create a new address associated with the ship-to customer which will have a ship-to relationship with the ship-to customer.

IBE_IGNORE_THRESHOLD

Exempts a user from any Payment Threshold restrictions that are in place.

IBE_SHIPTO_ANY_ACCOUNT

Allows a user to search on and retrieve all existing customers rather than only those with an existing shipping relationship with the sold-to customer. Note that "all existing customers" is restricted to customers that have a valid party relationship of type 'CUSTOMER_OF' with the sold-to customer, as well as any customer that has a shipping account relationship with the sold-to customer.

IBE_USE_ATTACHMENT

Allows the user to attach files in the shopping cart. If using this permission, ensure that the profile option, IBE: Attachment Document Category, is set to MISC at the iStore application level.

IBE_USE_PRICING_AGREEMENT

Allows the user to use pricing agreements. B2B users also must have IBE_VIEW_NET_PRICE permission to see pricing agreements data.

Note: The profile option, IBE: Use Line Agreements, specifies whether B2B users with the IBE_USE_PRICING_AGREEMENT permission can select pricing agreements at item level, in addition to the cart-level agreement selection enabled by the permission.

IBE_USE_PAYMENT_BOOK

Allows the user to include the payment book feature for retaining credit card preferences and specifying a default credit card when placing orders. This permission controls the availability of the payment book and specifying a default credit card when navigating through the ordering process. If this permission is not included for existing roles, then the link to the payment book will not be available. If using this permission, ensure that the profile option, “IBE: Retain Credit Card Preferences”, is set to Yes at the iStore site level.

IBE_VIEW_CUST_WITHOUT_ACCOUNT

Allows a user to search on and retrieve existing customers without an account.

IBE_VIEW_INVOICE

Allows a user to view invoices related to the entire organization, through Order Tracker. Oracle iStore checks this permission only if the profile option, IBE: Use Auth Permissions in Order Tracker, is set to Yes.

IBE_VIEW_NET_PRICE

Allows a user to see all prices (i.e. list prices, discount prices and net prices), instead of just list prices in the shopping cart and Order Tracker pages. This permission does not affect the user's ability to view prices in the catalog. This permission also controls the pricing agreement, promotion code, and commitment functionalities in Oracle iStore. Users without this permission cannot see amounts in the Order Tracker Invoices and Payments pages. In addition, different behavior occurs for TSO and non-TSO items, as described below.

Following is the specific behavior in the shopping cart.

Following is the specific behavior in Order Tracker (including Returns):

For users without this permission, it is recommended that they also not have the following permissions: IBE_CHECKOUT, IBE_CREATE_ORDER, IBE_CREATE_RETURN, or IBE_VIEW_ORDER.

IBE_VIEW_BILL_TO_ORDER and IBE_VIEW_ORDER

IBE_VIEW_BILL_TO_ORDER allows B2B users to see the orders for other customers where they are the bill-to, while IBE_VIEW_ORDER allows them to see orders where they are the sold-to.

IBE_VIEW_BILL_TO_ORDER example: If Customer 1 has placed an order for which Customer 1 is the sold-to, but Customer 2 is the bill-to, then when a user is logged in on behalf of Customer 2, he/she can view the order.

With both permissions, IBE_VIEW_ORDER and IBE_VIEW_BILL_TO_ORDER, B2B users can view their orders or organization orders, with the following differences:

Note that B2B users can always view orders they have placed, with or without these permissions. These permissions simply capture additional orders in the view that otherwise would not be viewable.

Additional Guidelines

The following information can aid your understanding of these permissions.

IBE_VIEW_PAYMENT

Allows a user to view payments related to the entire organization, through Order Tracker. Oracle iStore checks this permission only if the profile option, IBE: Use Auth Permissions in Order Tracker, is set to Yes.

IBE_VIEW_RETURN_ORDER

Allows a user to view all returns placed within his organization in the Order Tracker pages. Only checked if the profile option, IBE: Use Auth Permissions in Order Tracker, is set to Yes.

IBE_INT_ADMINISTRATORS

Gives users permission to view primary users of the organization in the Company Profile screens.

IBE_INT_ASSIGN_ACCOUNTS

Gives users permission to assign accounts in the User Management screens.

IBE_INT_ASSIGN_ROLES

Gives users permission to assign roles in the User Management screens.

IBE_INT_MANAGE_CONTACT

Gives users permission to create new and update existing organization contacts and users in the User Management screens.

IBE_INT_MANAGE_CONTACT_INFO

Gives users permission to update, create, and delete corporate addresses, e-mail addresses, phone numbers, and telex numbers in the Company Profile screens.

IBE_INT_ORG_ADDRESS_BOOK

Gives users permission to view company address book in the Company Profile screens.

IBE_INT_ORG_DETAILS

Gives users permission to view organization details in the Company Profile screens.

IBE_INT_ORG_EMAIL_ADDRESSES

Gives users permission to view e-mail addresses of the company in the Company Profile screens.

IBE_INT_ORG_PHONE_NUMBERS

Gives users permission to view phone numbers of the company functionality in the Company Profile screens.

IBE_INT_ORG_TELEX_NUMBERS

Gives users permission to view telex numbers of the company in the Company Profile screens.

IBE_INT_PENDING_APPROVAL

Gives users permission to approve users of the organization in the Pending Approval screens.

IBE_INT_PRIMARY_USER

Gives users permission to identify a user as primary user in the Administration screens.

IBE_INT_ROLE_MANAGEMENT

Gives users permission to create and update roles in the Role Management screens.

IBE_INT_UPDATE_ORG_DETAILS

Gives users permission to update organization details in the Company Profile screens.

IBE_INT_USER_MANAGEMENT

Gives users permission to access User Management screens.

JTF_PRIMARY_USER_SUMMARY

Oracle CRM Common Application Components permission which allows a primary user to approve pending registration requests.

iStore Permissions Not Supported

The following permissions are not currently supported. Although they may appear in some seeded user roles, they are non-functional.

Site Management User Type Definitions

This section contains information on the seeded site management user type definitions for Oracle iStore, Oracle iSupport, and Oracle Partner Management which are supported in the Oracle iStore Customer UI.

Note the following:

Individual Users

This section contains information about default data for the individual (B2C) user registration, including the seeded user type and the Oracle iStore and Oracle iSupport enrollments seeded within this user type.

Individual User Type

User Type for Online Access to Existing Account

iStore Enrollment for B2C Users

iSupport Enrollment for B2C Users

Non-Administrative B2B Users

This section contains information about default data for the non-administrative business (B2B) user registration, including the seeded user type and the Oracle iStore and Oracle iSupport enrollments seeded within this user type.

Regular Business User Type

User Type for Online Access to Existing Account

iStore Enrollment for Regular B2B Users

iSupport Enrollment for Regular B2B Users

Primary B2B Users

This section contains information about default data for the Primary (administrative) business (B2B) user registration, including the seeded user type and the Oracle iStore and Oracle iSupport enrollments seeded within this user type.

Primary B2B User Type

iStore Enrollment for B2B Primary Users

iSupport Enrollment for B2B Primary Users

Partner Non-Administrative Users

This section contains information about default data for the Oracle Partner Management non-administrative business (B2B) user registration, including the seeded user type and the Oracle iStore and Oracle Partner Management enrollments seeded within this user type.

Regular B2B Partner User Type

iStore Enrollment for Regular B2B Partner Users

Partner Enrollment for Regular B2B Partner Users

Partner Primary Users

This section contains information about default data for the Oracle Partner Management Primary (administrative) business (B2B) user registration, including the seeded user type and the Oracle iStore and Oracle Partner Management enrollments seeded within this user type.

Partner Primary User Type

iStore Enrollment for Partner Primary Users

Partner Enrollment for Partner Primary Users

Important: For the most current information on seeded user data for Oracle Partner Management and Oracle iSupport, see the product documentation for these applications.

Site Management User Registration Templates

This section contains data for the user registration templates used for site management. For user management Display Templates, see the section, "User Management Display Templates", in the "Seeded Display Data" appendix.

iStore Individual User Registration Template

Following are details about the iStore Individual User Registration Template:

iStore Regular B2B User Registration Template

Following are details about the iStore Regular B2B User Registration Template:

iStore Primary B2B User Registration Template

Following are details about the Primary B2B User Registration Template:

Partner Regular B2B User Registration Template

Following are details about the Partner Regular B2B User Registration Template:

Partner Primary B2B User Registration Template

Following are details about the Partner Primary B2B User Registration Template:

Online Access to Existing Account B2B User Registration Template

Following are details about the Online Access to Existing Account B2B User Registration Template:

Online Access to Existing Account Individual User Registration Template

Following are details about the Online Access to Existing Account Individual User Registration Template:

Site Management Profile Pages Permissions

This section contains information about site management user permissions involved in controlling the profile pages in the Customer UI.

For information about the script which automatically updates existing roles with new permissions, see the section, "Permission Migration Script", later in this chapter

Profile Pages Permissions Overview

Functionality within the Administration (user management) and Profile screens can be controlled through permissions within the roles awarded to B2B users. Each role is associated to a set of permissions. For B2C users, permissions are not used; thus, B2C users always see the same set of screens.

When integrating with other applications, different menus for each application can be configured for Profile and Administration functionality. To enable the menus, each menu is associated in Oracle Forms to the corresponding application responsibility. Each menu function is associated to a specific permission. For more information on integrating with Oracle iSupport and Oracle Partner Management, see the chapters, "Integrating Oracle iStore with Oracle iSupport" and "Integrating Oracle iStore with Oracle Partner Management". In a common implementation, the menus are the same in each application.

In an integrated environment, access to common screens is controlled by permissions that are shared across the different primary and non-primary users' roles. Screens that are application-specific are associated to permissions that should be assigned only to the appropriate roles.

Following are the codes used within the permissions:

Oracle iStore B2C users typically are associated to the IBE_CUSTOMER responsibility, which is tied to a generic menu associated to user pages within the Profile menu. Further permissions within the B2B roles allow access to specific application functions, such as Company Profile and user administration functionality. Typically, only users with the iStore Business User role can access the Company Profile screens. And, by default, only users with iStore Primary User role can access the Administration screens.

Additional access to functionality in the Profile pages can be provided for users of Oracle iSupport and Oracle Partner Management, by assigning the permissions that correspond to the functionality desired. See the sections, "Roles and Permissions Combinations for Oracle iSupport" and "Roles and Permissions Combinations for Oracle Partner Management", in this chapter, for recommended setups.

By default, any user registering using Register as individual, Register your company, and Register as a user of an existing company user types will receive the same level of Profile page permissions in Oracle iStore.

Permissions for User Pages

Following are the user Profile page permissions for Oracle iSupport and Oracle Partner Relationship Management. No specific permissions are needed for Oracle iStore users to access these pages.

Oracle iSupport Permissions:

Oracle Partner Management Permissions:

Permissions for Company Pages

Following are the permissions for company Profile pages. The code INT is included in common permissions. See the section, "Oracle iStore B2B User Permissions Descriptions", in this chapter, for descriptions of the common permissions.

Common Permissions:

Oracle Partner Management Permissions:

Permissions for Administration Pages

Following are the permissions for administration pages. The code INT is included in common permissions. See the section, "Oracle iStore B2B User Permissions Descriptions", in this chapter, for descriptions of the common permissions.

Common Permissions:

Oracle iStore Permissions:

Oracle Partner Management Permissions:

Roles and Permissions Combinations for Oracle iStore

Following are the typical page/permission assignments for Oracle iStore users in the Profile pages.

Individual Users (B2C)

Oracle iStore does not require roles and permissions for B2C users. B2C users will always be able to access the following pages:

User Pages

Business Users (B2B)

Within the default iStore Business User role, all B2C user pages permissions exist, plus additional ones for viewing company information. See the section, "Permissions for Company Pages", in this chapter.

Company Pages

Primary Users

For the default Primary User role, all B2B regular user and company pages permissions exist, plus additional ones for user administration pages.

Administration Pages

Roles and Permissions Combinations for Oracle iSupport

In an integrated environment, Oracle iSupport users should be assigned appropriate permissions to get access to the following functions, if business requirements comply:

IBU_REGULAR_USER

For the B2C users, all existing Oracle iSupport permissions can be assigned, plus other to access the following information:

IBU_BUSINESS_USER

For regular B2B users, all B2C permissions can be assigned, plus new ones to access the following information:

User Pages -- see the section, "Permissions for User Pages", in this chapter

Company Pages -- see the section, "Permissions for Company Pages", in this chapter

IBU_PRIMARY_USER

For the integration, assign all existing Oracle iSupport regular business user permissions, plus new ones to access the user administration pages:

Administration Pages -- see the section, "Permissions for Administration Pages", in this chapter

Roles and Permissions Combinations for Oracle Partner Management

For integration with Oracle Partner Relationship Management, the partner roles should be assigned appropriate permissions to get access to the following functions:

PV_BUSINESS_USER

Assign all existing Partner permissions, plus the new ones to access the following information:

User Pages -- see the section, "Permissions for User Pages", in this chapter

Company Pages -- see the section, "Permissions for Company Pages", in this chapter

PV_PRIMARY_USER

Assign all regular Partner user permissions for user and company pages, plus new ones to access the user administration pages:

Administration Pages -- see the section, "Permissions for Administration Pages", in this chapter

Permission Migration Script

In Release 11.5.10, Oracle iStore seeds several new permissions designed to accommodate the integration of other applications, such as Oracle iSupport and Oracle Partner Management, into the site management functionality. These permissions contain the code, INT. Additionally, several Oracle iStore-specific user permissions have been added, and several have been obsoleted.

The iStore Permission Migration script maps new Release 11.5.10 permissions to all existing roles. The SQL script runs automatically when the Release 11.5.10 patch is applied. This supplies all existing users (pre-Release 11.5.10) with the necessary permissions to access their intended functionality in the Customer UI. The seeding is done for all roles which contain at least one of the Oracle iStore (IBE) permissions, including custom roles.

The following table shows the permission migration information.

Release 11.5.10 Permission Mapping to Pre-Release Permissions
Component Permission Description Pre-R11510 Permission New Permissions
Sales Assistance Permission to request sales assistance and to reject terms and conditions None IBE_ASK_SALES_ASSISTANCE
Checkout Permission to checkout None IBE_CHECKOUT
Pricing Permission to view discount prices None IBE_VIEW_NET_PRICE
User Management Permission to create User Management screens IBE_USER_ADMIN IBE_INT_USER_MANAGEMENT
User Management Permission to create/update new contact and user IBE_USER_ADMIN IBE_INT_MANAGE_CONTACT
User Management Permission to view contact details IBE_USER_ADMIN BE_INT_CONTACT_DETAILS (unsupported)
User Management Permission to assign roles IBE_USER_ADMIN IBE_INT_ASSIGN_ROLES
User Management Permission to assign accounts IBE_USER_ADMIN IBE_INT_ASSIGN_ACCOUNTS
User Management Permission to assign sites IBE_USER_ADMIN IBE_ASSIGN_SITES
Pending Approval Permission to approve user registration IBE_USER_ADMIN IBE_INT_PENDING_APPROVAL
Primary User Permission to approve user registration IBE_USER_ADMIN JTF_PRIMARY_USER_SUMMARY
Primary User Permission to identify users as primary user IBE_USER_ADMIN IBE_INT_PRIMARY_USER
Role Management Permission to create and update roles IBE_ROLE_ADMIN IBE_INT_ROLE_MANAGEMENT
Company Profile Permission to view organization detail All roles which have IBE permissions IBE_INT_ORG_DETAILS
Company Profile Permission to view organization primary users All roles which have IBE permissions IBE_INT_ADMINISTRATORS
Company Profile Permission to view address book All roles which have IBE permissions IBE_INT_ORG_ADDRESS_BOOK
Company Profile Permission to view email addresses screen All roles which have IBE permissions IBE_INT_ ORG_EMAIL_ADDRESSES
Company Profile Permission to view phone numbers screens All roles which have IBE permissions IBE_INT_ ORG_PHONE_NUMBERS
Company Profile Permission to view Telex numbers screens All roles which have IBE permissions IBE_INT_ ORG_TELEX_NUMBERS
Company Profile Permission to update organization details IBE_USER_ADMIN IBE_INT_UPDATE_ORG_DETAILS
Company Profile Permission to update, create, delete corporate addresses, email and phone numbers IBE_USER_ADMIN IBE_INT_MANAGE_CONTACT_INFO