iStore White Paper: How to set up iStore for a new Operating Unit and Item Master in a Multi Org

environment
Abstract This paper provides an overview and steps of setting up a Specialty Store tied to a new Operating Unit. And it also contains the basic setup steps necessary to setup a new Operating Unit.

II. ASSUMPTIONS
1. Oracle Applications has been installed, setup and working for at least one Operating Unit. 2. IBE patchset O has been applied. 3. We are going to make use of an existing Legal Entity and Set of Books.

Scope
I. Setup an Operating Unit II. Setup a Specialty Store Please note that this paper does not replace your Multiple Organizations in Oracle Applications Guide or iStore and iMarketing implementation Guide. This paper is intended to give you a quick overview of the setting up an Operating Unit and a Specialty store.

Setup for the New Operating Unit

1. Define an Operating Unit. This can be performed from the HR Manger Responsibility by choosing Work Structures -> Organization -> Description form. Click on New and enter all the mandatory fields in the form 2. Run Replicate Seed Data Concurrent Program for the new Operating Unit from the System Administrator Responsibility. Navigation is Requests -> Run -> Single Request. Form is as shown below :

References
For detailed information on Multiple Organizations Architecture or iStore, please read the following references. Multiple Organizations in Oracle Applications Release 11i. Oracle Receivables User Guide Oracle Inventory User s Guide Oracle Order Management User s Guide Oracle Pricing User s Guide Oracle iStore and Oracle iMarketing Implementation Guide. Oracle iStore Concepts and Procedures

I. OVERVIEW OF MULTI ORG

The Oracle Applications organization models define organizations and the relationships among them in arbitrarily complex enterprises. This organization model serves as the cornerstone for all of the Oracle Application products. It dictates how transactions flow through different organizations and how those organizations interact with each other. Generally, a complex enterprise has several organization structures, such as Internal, Accounting, and Human Resources. You are able to define different structures to configure Oracle Applications according to your business needs. One of the available classifications for an Organization is the Operating Unit. Multiple Operating Units are defined when Companies want to track their Procurement and Sales information separately for different organizational units.

3. Create new Responsibilities using the Security -> Responsibility -> Define form. Required responsibilities for the new Operating Unit are System Administrator, Receivables, Order Management, Quoting, iStore Administrator and IBE_CUSTOMER.

4. Tie the responsibilities to the new Operating Unit by setting the profile MO: Operating Unit at the Responsibility level for the newly created Responsibilities from step 3. Navigation is Profile -> System. Values should appear as shown in fig below.

e.g.: For the new responsibility IBE_CUSTOMER_SPAIN, created in step 3, the new operating unit is displayed.

5. Define System Options in the new Receivables Responsibility. Navigation is Setup -> System -> System Options and click on each of the tabs Accounting, Tax, Tax Defaults and Rules, Trans and Customers, Miscellaneous. Enter all the mandatory fields (all the flexfields), for e.g. in Accounting (fig shown below) enter values for Realized Gains Account and Tax Account. You can derive these values from the LOVs.

8. Choose the new Item Master Organization and define Items in the Items -> Master Items form and enable these items in the Inventory Organization setup in step 6. 9. Assign the items to Price Lists from the Order Management Responsibility using Pricing -> Price Lists -> Price List Setup form as shown below :

10. Also define Transaction types for Order and Line from Setup -> Transaction Types -> Define form. 6. Define two Inventory Organizations tied to the new Operating Unit from Setup -> Organizations -> Organizations form. Make one of them its own master In the Inventory options form. This will be the master of the second inventory organization. 7. Define Shipping Methods in Inventory. Navigation is Setup -> Organizations -> Shipping Methods and form is a shown below : 11. Optionally create a Document Sequence from Setup -> Documents -> Define form and assign it to the Document Type in Setup -> Documents -> Assign form. 12. Define Freight Carriers and Carrier Ship Methods for the Organization (Operating Unit) you created navigating through Setup -> Shipping -> Freight Carriers, Cost Types -> Freight Carriers form. One of the forms is as shown below :

Setup for the Specialty Store

1. Create a new responsibility by cloning the seeded iStore Administrator responsibility. 2. Pick MO: Operating Unit as the operating unit we have created for this responsibility. 3. Create a new user via the Security -> User -> Define form and assign this new Admin responsibility along with the seeded iStore Administrator responsibility. Setup his/her JTF_PROFILE_DEFAULT_RESPONSIBILITY to point to the new responsibility. 4. Set the profile IBE: Item Validation Organization to point to the new Item Master at the user level for the user created in setp 3 and bounce apache. 5. Login as the new iStore Administrator and create a new section and add items from the new Inventory Organization to this Section. 6. Create a Specialty Store. Make the section defined in step 1 the Root Section of the store. Pick the new IBE_CUSTOMER responsibility as the Supported Responsibility. 7. Register a new End User or Business User either from iStore or from jtflogin.jsp 8. If a Business User was created in Step 3, then approve the Business User. 9. Query up the user in the System Administrator responsibility and end date the IBE_CUSTOMER responsibility and assign the new IBE_CUSTOMER responsibility to the user. Navigation is Security -> User -> Define. 10. For this User enter the responsibility id of the newly created IBE_CUSTOMER responsibility in the profile JTF_PROFILE_DEFAULT RESPONSIBILITY. The responsibility id can be found by using Help -> Debug -> Examine option after querying up the Responsibility in Security -> Responsibility -> Define form. Note: You may have to wait a day before testing the new user since we cannot end date a responsibility the same day it was assigned.

13. Pick the new Operating Unit in the Setup -> Parameters form and fill the Item Validation Organization. Only the items belonging to this Organization will be visible in the Merchant UI in iStore for adding to Sections. 14. Define ASO% profile options at the new IBE_CUSTOMER responsibility level from the new System Administrator Responsibility as per the iStore implementation guide. ASO: Default Order Type profile option will point to the Document Type setup in step 10 as shown in the form below :

Troubleshooting
In Netscape Click on Warn before accepting cookies and check whether the correct Operating Unit id is displayed when logging in as the User tied to the new IBE_CUSTOMER Responsibility. The value is stored in the cookie zo. If it does not show the correct value then revisit the steps and make sure everything is setup and verify that the correct patches mentioned in the ASSUMPTIONS section have been applied.

Conclusions and Observation

It is our hope that this paper has helped you understand how to setup a Specialty Store tied to a new Operating Unit and a new Item Master. The Product Search functionality is found to be working for the new section without any additional setup.

About the Author

Arun Ramanathan is a Senior Technical Analyst for the ECommerce support team.