Configuration

Configuration

One must follow some set of steps, in order to create a component / object in application. Those steps are known as the Configuration steps. In this section, we will discuss about the Configuration steps required for creating System Administration Components.

Creating a Function

  • Responsibility: System Administrator
  • Navigation: Application -> Function

(Figure 2.1 – Defining Functions)

Creating a Menu

  • Responsibility: System Administrator
  • Navigation: Application -> Menu

(Figure 2.2 – Defining Menus)

Creating a Request Group

A request group, as explained earlier, is a group of requests combined together. We attach the group to the responsibilities. Once attached a user can execute only those requests that are part of the request group attached to the responsibility in which the user has logged in. See Figure 2.3 – Defining Request Sets.

  • Responsibility: System Administrator
  • Navigation: Security -> Responsibility -> Request

(Figure 2.3 – Defining Request Groups)

Creating a Responsibility

Now it’s time for a new responsibility. See Figure 2.4 – Defining Responsibilities.

  • Responsibility: System Administrator
  • Navigation: Security -> Responsibility -> Define

(Figure 2.4 – Defining Responsibilities)

Creating a User

To create a user, we need to login to Oracle applications, and we must have the System Administrator Responsibility to do so. We should contact the system administrators / Installation analysts to get one user created first, so that we can log in and create other users.

  • Responsibility: System Administrator
  • Navigation: Security -> User -> Define

(Figure 2.5 – Defining Users)

Monitoring a User

There will be instances in which we will need to monitor a specific set of users, and see the current activities. To do so, one can use the monitor user functionality given to the System administrator. See Figure 2.6 – Monitoring Users.

  • Responsibility: System Administrator
  • Navigation: Security -> User -> Monitor

(Figure 2.6 – Monitoring Users)

Steps:

  • Query for the user, and it will list the current usage of the application of the user.
  • The Responsibility and form section tells us about the application and the forms being used.
  • The Time tells the length of the time, the user had been in that form / responsibility
  • The Oracle Process textbox tells us the Process id, of the Oracle process being executed by the user.

There will be instances in which we will need to monitor a specific set of users, and see the current activities. To do so, one can use the monitor user functionality given to the System administrator. See Figure 1.17 – Monitoring Users.

back to top

Administrating Profile Options

As discussed earlier, Profile options are the preferences that the system uses to make decisions. So these options direct the way our application behaves. Oracle E-Biz lists a set of Profile options that we need to define for each module to work in a certain way.

There are six different levels at which we can attach Profile Options.

    1. Site
    2. Application
    3. Responsibility
    4. Server
    5. Organization
    6. User

The hierarchy follows the same order. Like the Responsibility level overrides the option value given in the site level, and the Organization level overrides the option value at the Responsibility level. The user level, being the lowest overrides them all.

(Figure 2.7 – Profile Options)

Let’s see how to find and update a profile option. See Figure 1.8 – Finding Profile Options.

    • Responsibility: System Administrator
    • Navigation: Profile -> System

(Figure 2.8 – Finding Profile Options)

Steps:

  • Check the level at which we want to see the Option value.
  • Unless the level is Site, enter the name of the Object. Like if application is checked, enter the name of the application.
  • If we wish to see the values of Options with blank values in the particular level, check the “Profile with No values” flag.
  • Select the name of the profile, and press find.
  • Once the option value is open, we can go and update the option values if needed.
  • We can also set few profile options in Functional Administrator responsibility (Functional Administrator -> Core Services -> Profiles).

Creating Request Sets

A request set is a set of concurrent requests pooled together to run one after another. Let’s discuss about the steps involved in creating a request set.

  • Responsibility: System Administrator
  • Navigation: Concurrent -> Set

(Figure 2.9 – Defining Request Sets)

Steps:

Concurrent Requests

The concurrent requests are the requests that can run in the system without impacting the ongoing transactions. To elaborate, if a system is live, then a lot of users might be using it at one point of time, and in that period if we wish to run a report or run a process, then we can do it with Concurrent requests without impacting the performance of the system. Again, we can submit the request and keep on working on the regular application tasks. The request will automatically get completed, and we could check the results anytime later.

We can either submit a concurrent request or a set of requests combined together, known as the request sets. Let’s see how.

Submitting a New Request

A request set is a set of concurrent requests pooled together to run one after another. Let’s discuss about the steps involved in creating a request set.

  • Navigation: View (menu) -> Request (menu)

(Figure 2.10 – Submitting New Requests)

Steps:

  • It opens up the Find Request screen. See Figure 2.10 – Submitting New Requests.
  • Enter Submit a request to create a new Request
  • The system asks, if we wish to submit a single request or a request set. Choose single request
    • It opens up the submit request screen

(Figure 2.11 – Submit Requests)

  • From the List of Values choose the name of the request, and press tab. See Figure 2.11 – Submit Requests.
  • It should open up all the mandatory and optional Parameters that are needed for the request to run.
  • The language of the output can be changed by clicking on the language settings.
  • The request can be scheduled for a later point in time. To do so, go to the Schedule button, and select the schedule; else choose as soon as possible
  • If we wish to print or email or fax the output, put the required information in the Delivery options button
  • Press Submit. Once submitted, the system assigns a REQUEST_ID for the request and the Requests window opens.

(Figure 2.12 – View Request Status)

  • The requests window shows all request submitted by us / our group based on the settings. See Figure 2.12 – View Request Status.
  • There are four different phases of a request
    • Pending: The request is either waiting to be picked up based on priority / waiting for another request to be processed/ scheduled for later.
    • Running: The request is running.
    • Completed: The Request is complete.
    • Inactive: The Request is not prioritized yet; waiting for the Concurrent manager
  • Based on the phases, there are different statuses that a request can have:
  • For Child requests, the parent of the request shows the request that in turn created this child request.
  • The Hold Request Button pauses the processing of the request and changes the Phase to Inactive – On Hold.
  • Cancel request, cancels the reques
    • View Details button shows the submitted parameters with all the preferences on output and language as read only.
    • Diagnostics button opens up a new window detailing the status of the request.
    • View output button opens up a new window with the Output in it.
    • View Log shows the log file generated by the Process
    • Only the Parent requests have the log and the output; that to only after the request is completed
    • While browsing through the log and output, we can either use the page numbers to navigate or simply go to Tools menu -> Copy File to copy the entire output/ log to an Internet Explorer or a Text file.

back to top

Finding a Request

Once the request is submitted, the request status and the output can be checked anytime. Let’s see how to find a request. See Figure 2.13 – Find Requests.

Navigation: View (menu) -> Request (menu)

(Figure 2.13 – Find Requests)

  • Once the Find request window is open, we have the following Options.
    • Search all our completed requests by using ‘My Completed Requests’
    • Search all our running requests by using ‘My Requests in Progress’
    • Search all our request irrespective of any criteria by using ‘All my Requests’
    • Search requests by
      • Request Id
      • Concurrent Program name
      • Submitted / completed date
      • Current status or phase
      • Request submitted by
  • Enter the number of days we want to look for. It queries back till that many number of days and shows the requests.
  • Press Find to find the requests based on the criteria added.

Submitting a Request Set

(Figure 2.14 – Submitting Request Sets)

  • Once we click on ‘Submit New Request’, we can choose Request Set this time, rather selecting the Single request.
    • This opens up a new screen for request sets. See Figure 2.14 – Submitting Request Sets.
    • Enter the name of the request set and press tab
    • Then it will list the Programs listed under the request set.
    • Start entering the Parameters for the program.
    • If we wish to print or fax or mail the output, update the Delivery Options.
    • Update the schedule in needed.
    • Press submit
    • Once submitted the find request window opens with the submitted requests in there.