|Oracle iAssets User Guide|
Part Number E13435-03
This chapter covers the following topics:
This section covers the steps that you follow in setting up Oracle iAssets.
Before you set up Oracle iAssets, set up Oracle Applications responsibilities and users for the implementation. Oracle iAssets provides Oracle iAssets responsibilities.
The Setup Checklist presents the steps that you follow to set up Oracle iAssets. If you are setting up other Oracle applications at the same time, you can also refer to the Related Products setup steps and tables.
Related Product Setup Steps
You may need to perform the following steps to implement Oracle iAssets. These steps are discussed in detail in the Setting Up sections of their respective Oracle product user guides.
You need to set up underlying Oracle Applications technology, which includes the following steps:
Perform system-wide setup tasks such as configuring concurrent managers and printers
Manage data security, which includes setting up responsibilities to allow access to a specific set of business data and complete a specific set of transactions, and assigning individual users to one or more of these responsibilities.
Set up Oracle Workflow
Before implementing Oracle iAssets, you must implement Oracle Assets. See: Overview of Setting Up, Oracle Assets User Guide.
Before implementing Oracle iAssets, you must implement Oracle Human Resources. Refer to the Setting Up section in Implementing Oracle HRMS for help in completing Oracle Human Resources setup steps, and to the Setup Checklist for information on the specific Human Resources setup steps that need to be completed for Oracle iAssets.
Oracle Applications System Administrator's Guide
Oracle Workflow Guide
The following table lists Oracle iAssets setup steps including steps that you need to complete in other products. For each step, the table lists whether the step is optional or required. After you log on to Oracle Applications, complete these steps to implement Oracle iAssets:
|Oracle Assets Setup Steps|
|Step 1||Required||Set up Oracle Assets.|
See: Overview of Setting Up, Oracle Assets User Guide
Context: Perform this step once per installation.
|Oracle HRMS Setup Steps|
|Step 2||Conditionally Required||Defining a Job.|
This step is required if you choose the Management hierarchy-based approvals option on the Create Rule page and the Absolute Job Level rule in AME. The default Absolute Job Level rule is set to level 3. This means that Oracle iAssets starts the approval chain from the requester's supervisor to each subsequent job level up to level 3. For Management hierarchy-based approvals to work properly using the default Absolute Job Level rule, you must create a job with approval authority of 3 or above and assign the approver to this job. Alternatively, you can change the Absolute Job Level via AME to match the job level of the final approver. See: Defining a Job, Managing Your Workforce Using Oracle HRMS.
Context: Perform this step once for each job.
|Step 3||Required||Enter employees.|
This step is required to define employees and supervisors. See: Entering a New Person, Managing Your Workforce Using Oracle HRMS.
Context: Perform this step once for each Oracle iAssets user.
|Step 4||Conditionally Required||Create an organization. The organization must have an organization classification of Company Cost Center.|
This step is required if you have set up Oracle iAssets to require cost center-based approvals or apply cost center security on the Create Rule page. For cost center-based approvals to work properly, each cost center must have a manager defined. See: Creating an Organization, Using Oracle HRMS - The Fundamentals.
Context: Perform this step once per organization.
|Step 6||Optional||Set up custom approval rules in AME.|
See: Approval Rules (Implementing Oracle Approvals Management).
Context: Perform this step once per installation.
|Oracle iAssets Setup Steps|
|Step 5||Required||Set Up Rules.|
See: Defining Oracle iAssets Transfer Rules.
Context: Perform this step when ever you need to define rules.
|Step 6||Required||Set up profile options.|
See: Profile Options and Profile Option Categories Overview.
Context: Perform this step when ever you need to define rule names.
|Step 7||Required||Assign rule names to user responsibilities.|
See: Assigning Rule Names to User Responsibilities.
Context: Perform this step when ever you need to assign rule names to user responsibilities.
You define Oracle iAssets rules to control the features that end users will be able to access. Oracle iAssets rules determine the transactions a user can access, whether the user can create transfer requests or query assets only, the approvals that are needed for a transfer request, and the approval method. You can also define custom text that will appear on the first page of the transfer process.
Searching for Rules
Navigate to the Rules Search page to search for existing rules. You can also use this page to create new rules.
Log into the iAssets Setup Administrator responsibility.
Navigate to the Create Rule page.
Enter a unique rule name.
Enter a description of the rule.
Assign a corporate book to the rule. Users will have access only to assets in the assigned corporate book.
Determine whether users will be able to use self service transfer functionality.
The Enable Self-Service Transfer Functionality check box must be checked to enable users to create transfer requests.
If you do not check this check box, users will only be able to search and view assets.
Determine whether users will be able to enter a transfer effective date while requesting a transfer.
If you check the Allow user-enterable transaction date check box, users will be able to enter the current date or any date within the current fiscal year. A user can also enter a future date but the transfer will be posted only when the period in which this date falls is opened in the asset book.
If you do not check this check box, the transfer date is set to the date the transfer is approved.
Determine whether fixed asset manager (iAssets manager) approval is required before applying any self service transfers.
If you check the Require iAssets Manager approval before applying any self-service transfers check box, then Oracle iAssets will require approval from the fixed asset manager. The fixed asset manager can review the transfer lines from the iAssets Manager Responsibility and change the request status.
If you do not check the check box, after management approval, all transfer lines will be transferred to Oracle Assets with a status of Post.
Determine the approval type that will be required for each transfer request.
Both Releasing and Destination approvals required: If you choose this option, an Approver field appears for each asset selected for transfer on both the releasing and destination information pages. Both of these fields are required. This option is the default approval type.
No approvals required: If you choose this option, all transfer requests will be automatically approved.
Only Destination approvals required: If you choose this option, no Approver field will be displayed on the releasing information page. The Approver field will appear on the destination information page.
Only Releasing approvals required: If you choose this option, the Releasing Approver field is required. No Approver field will be displayed on the destination information page.
Determine the approval method that will be required for each transfer request.
Cost Center-based approvals: If you choose this option, the default approver will be the cost center manager.
Management hierarchy-based approvals: If you choose this option, the default approver will be based on the employee hierarchy relationship. The employee is the person for whom the transfer is requested. The approver defaults to the user who logs in. This option is the default approval method.
Choose the accounting segments that will be displayed throughout Oracle iAssets.
Check the Enforce Security by Cost Center check box to allow users to view and perform transactions only on assets in their cost center. If you do not check this check box, users will be able to view and perform transactions on assets in all cost centers.
Determine whether users will be restricted to search only their own requests. If you choose the Restrict users to only search for their saved requests check box, users will be able to search only their saved requests. If this check box is not checked, users will be able to query all requests on the system.
Determine whether you want to add any company-specific instructions that users need to follow before submitting a transfer. To add these instructions, you need to check the Enable custom text input check box, and enter the company-specific information in the Custom Text box. This text is visible in the content container on the Create Transfer Request: Request Details page.
Save your changes.
After defining rule names in the IA: iAssets Rule Name profile option, you must assign each rule name to a user responsibility. Every Oracle iAssets user responsibility and Oracle iAssets approver responsibility must be assigned a rule name. Otherwise, when users log into an Oracle iAssets responsibility, they will receive an error message and will be unable to proceed.
Copyright © 2004, 2010, Oracle and/or its affiliates. All rights reserved.