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

AbstractThis paper provides an overview and steps ofsetting up a Specialty Store tied to a newOperating Unit. And it also contains the basicsetup steps necessary to setup a new OperatingUnit.

ScopeI. Setup an Operating UnitII. Setup a Specialty StorePlease note that this paper does not replace yourMultiple Organizations in Oracle ApplicationsGuide or iStore and iMarketing implementationGuide. This paper is intended to give you a quickoverview of the setting up an Operating Unit anda Specialty store.

ReferencesFor detailed information on MultipleOrganizations Architecture or iStore, please readthe following references.Multiple Organizations in Oracle ApplicationsRelease 11i.Oracle Receivables User GuideOracle Inventory User’s GuideOracle Order Management User’s GuideOracle Pricing User’s GuideOracle iStore and Oracle iMarketingImplementation Guide.Oracle iStore Concepts and Procedures

I. OVERVIEW OF MULTI ORGThe Oracle Applications organization modelsdefine organizations and the relationships amongthem in arbitrarily complex enterprises. Thisorganization model serves as the cornerstone forall of the Oracle Application products. It dictateshow transactions flow through differentorganizations and how those organizationsinteract with each other. Generally, a complexenterprise has several organization structures,such as Internal, Accounting, and HumanResources. You are able to define differentstructures to configure Oracle Applicationsaccording to your business needs. One of theavailable classifications for an Organizationis the Operating Unit. Multiple Operating Unitsare defined when Companies want to track theirProcurement and Sales information separatelyfor different organizational units.

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

Setup for the New Operating Unit1. Define an Operating Unit. This can beperformed from the HR Manger Responsibilityby choosing Work Structures -> Organization ->Description form. Click on New and enter all themandatory fields in the form

2. Run Replicate Seed Data Concurrent Programfor the new Operating Unit from the SystemAdministrator Responsibility. Navigation isRequests -> Run -> Single Request. Form is asshown below :

3. Create new Responsibilities using the Security-> Responsibility -> Define form. Requiredresponsibilities for the new Operating Unit areSystem Administrator, Receivables, OrderManagement, Quoting, iStore Administrator andIBE_CUSTOMER.

4. Tie the responsibilities to the new OperatingUnit by setting the profile MO: Operating Unit atthe Responsibility level for the newly createdResponsibilities from step 3.Navigation is Profile -> System. Values shouldappear as shown in fig below.

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

5. Define System Options in the newReceivables Responsibility. Navigation is Setup-> System -> System Options and click on eachof the tabs Accounting, Tax, Tax Defaults andRules, Trans and Customers, Miscellaneous.Enter all the mandatory fields (all the flexfields),for e.g. in Accounting (fig shown below) entervalues for Realized Gains Account and TaxAccount. You can derive these values from theLOVs.

6. Define two Inventory Organizations tied to thenew Operating Unit from Setup -> Organizations-> Organizations form. Make one of them itsown master In the Inventory options form. Thiswill be the master of the second inventoryorganization.

7. Define Shipping Methods in Inventory.Navigation is Setup -> Organizations ->Shipping Methods and form is a shown below :

8. Choose the new Item Master Organization anddefine Items in the Items -> Master Items formand enable these items in the InventoryOrganization setup in step 6.

9. Assign the items to Price Lists from the OrderManagement Responsibility using Pricing ->Price Lists -> Price List Setup form as shownbelow :

10. Also define Transaction types for Order andLine from Setup -> Transaction Types -> Defineform.

11. Optionally create a Document Sequence fromSetup -> Documents -> Define form and assign itto the Document Type in Setup -> Documents ->Assign form.

12. Define Freight Carriers and Carrier ShipMethods for the Organization (Operating Unit)you created navigating through Setup ->Shipping -> Freight Carriers, Cost Types ->Freight Carriers form. One of the forms is asshown below :

13. Pick the new Operating Unit in the Setup ->Parameters form and fill the Item ValidationOrganization. Only the items belonging to thisOrganization will be visible in the Merchant UIin iStore for adding to Sections.

14. Define ASO% profile options at the newIBE_CUSTOMER responsibility level from thenew System Administrator Responsibility as perthe iStore implementation guide. ASO: DefaultOrder Type profile option will point to theDocument Type setup in step 10 as shown inthe form below :

Setup for the Specialty Store1. Create a new responsibility by cloning theseeded iStore Administrator responsibility.

2. Pick MO: Operating Unit as the operating unitwe have created for this responsibility.

3. Create a new user via the Security -> User ->Define form and assign this new Adminresponsibility along with the seeded iStoreAdministrator responsibility. Setuphis/herJTF_PROFILE_DEFAULT_RESPONSIBILITYto point to the new responsibility.

4. Set the profile IBE: Item ValidationOrganization to point to the new Item Master atthe user level for the user created in setp 3 andbounce apache.

5. Login as the new iStore Administrator andcreate a new section and add items from the newInventory Organization to this Section.

6. Create a Specialty Store. Make the sectiondefined in step 1 the Root Section of the store.Pick the new IBE_CUSTOMER responsibility asthe Supported Responsibility.

7. Register a new End User or Business Usereither from iStore or from jtflogin.jsp

8. If a Business User was created in Step 3, thenapprove the Business User.

9. Query up the user in the System Administratorresponsibility and end date theIBE_CUSTOMER responsibility and assign thenew IBE_CUSTOMER responsibility to theuser. Navigation is Security -> User -> Define.

10. For this User enter the responsibility id of thenewly created IBE_CUSTOMER responsibilityin the profile JTF_PROFILE_DEFAULTRESPONSIBILITY. The responsibility id can befound by using Help -> Debug -> Examineoption after querying up the Responsibility inSecurity -> Responsibility -> Define form.Note: You may have to wait a day before testingthe new user since we cannot end date aresponsibility the same day it was assigned.

TroubleshootingIn Netscape Click on Warn before acceptingcookies and check whether the correct OperatingUnit id is displayed when logging in as the Usertied to the new IBE_CUSTOMERResponsibility. The value is stored in the cookiezo. If it does not show the correct value thenrevisit the steps and make sure everything issetup and verify that the correct patchesmentioned in the ASSUMPTIONS section havebeen applied.

Conclusions and ObservationIt is our hope that this paper has helped youunderstand how to setup a Specialty Store tied toa new Operating Unit and a new Item Master.The Product Search functionality is found to beworking for the new section without anyadditional setup.

About the AuthorArun Ramanathan is a Senior Technical Analystfor the ECommerce support team.