Realms Setup In iProcurement

Realms restrict the user access to iProcurement categories in any of two level

1. Responsibility level

2. User level

Define Realms:

Responsibility: Purchasing SuperUser

Navigation: Setup > E-catalog Admin > Realms

Enter Realms on the form as shown below

The iProcurement categories are attached to the Realm as components. We have a choice of attaching Item Sources or Categories asComponent Type. The Component Type LOV is given below

1.Responsibility level:

Now the realms are all setup. We shall now assign the realm to the responsibility and/or user. First let us assign the realm to a responsibility. Open the responsibility form.

Responsibility: System Administrator

Navigation: Security > Responsibility > Define

Query for the responsibility named, i-Procurement , We shall set the realm for the responsibility.

Click on Securring Attributes tab.
Enter the Securring Attribute name, ICX_POR_REALM_ID.
Click on Values button.
The Attribute Values window opens. Now click on the Values LOV and search for the realm you have created earlier, i.e. Special Event – Sales.

Note that the realm id is shown on the form. This ID was generated on the Realm definition form before. Save the form to set the realm for this responsibility

2.User Level:

Realm can be set on the user level as well. Open the Users form.

Responsibility: System Administrator

Navigation: Security > User > Define

Query for user SYSADMIN

Click on Securring Attributes tab.

Enter a new securing attribute, ICX_POR_REALM_ID.

Enter the realm value 247 (the realm id of the realm we have created earlier)

Save the form. Now the realm is set on the user level as well.

Now if you login to any iProcurement responsibility using this user you will be restricted to the iProcurement categories under the realm,Special Event – Sales, even though you might not be using the previously defined responsibility iProcurement. If you go to this responsibility you will again be restricted to the realm, Special Event – Sales, even though you may be logged into Oracle with a different user.