This chapter covers the following topics:
Mandatory implementation steps are required for Oracle Proposals to function properly. Oracle recommends that you implement Oracle Proposals in the order listed.
The steps needed for implementing Oracle Proposals are listed in the order in which they should be carried out.
The following table describes the order and process of implementing Oracle Proposals.
| Step | Description | Performed Where | Performed By |
|---|---|---|---|
| 1 | Apply PRP Patch. | Environment | System Administrator |
| 2 | Check dependencies. | Environment | System Administrator |
| 3 | Create users, or identify existing users and verify their responsibility. Assign administrators the Proposals Main Menu. Assign sales representative users the Proposal Homepage Function. | Forms | System Administrator |
| 4 | Assign appropriate menus to any new responsibility. | Forms | System Administrator |
| 5 | Verify administrators and sales representative users are resources in Resource Manager. | Forms | System Administrator |
| 6 | Set up profile options. | Forms | System Administrator |
There are two main types of Proposals users- administrators and users.
Users can also be set up using the Oracle System Administrator Console.
The system administrator assigns the FND menus for Oracle Proposals users.
Before initiating Oracle Forms settings, verify that Oracle Applications is up and running. Because some setup steps require running concurrent programs, you must ensure that the concurrent managers are running. Consult your Oracle Applications system administrator for additional information.
Oracle E-Business Suite Setup Guide
Oracle Trading Community Architecture Administration Guide
Oracle Trading Community Architecture User Guide
Oracle E-Business Suite Concepts
Administrators have access to both the Administration and User sections of Oracle Proposals. Log in to Self Service applications and choose the Proposals Administrator responsibility. Access the administration tasks from the Administration menu and the user tasks from the Proposals link.
From the Administration link, you can access, create, delete, and generate administrative data including:
Templates
Components
Dynamic Fields
Template Categories
From the Proposals link, administrators can:
Create Proposals
View Proposals
Delete Proposals
Modify Proposals
Generate Proposals
Email Proposals
Search for Proposals
Administrators, like regular users, can only view and update those proposals for which they are on the sales team. There is no administrative access to all user's proposals.
Oracle Proposals users have access to the Proposals page to perform basic user functions. User must be set up as a Resource in Resource Manager. They will not have access to administrative data. They can:
Create Proposals
View Proposals
Delete Proposals
Modify Proposals
Generate Proposals
Send Proposals by E-mail
Search for Proposals
To access Oracle Proposals, a user must be set up as a FND User and as a Resource in Resource Manager. When a user logs into Oracle Proposals, a check is made against the FND table. Oracle Proposals checks to see if the FND User is a Resource first. If the user is set up as a Resource in Resource Manager, then the user's information such as name, title, phone, fax, e-mail id and address is picked from there. Care must be taken to ensure that if the user is a resource, all user information is stored correctly in Resource Manager. If the user information is not available in either FND or Resource Manager, the user's information is blank.
Note: The FND User name must be assigned to the user name field in Resource Manager.
If you want all users to have access to Oracle Proposals, they must be set up as valid resources in Oracle Resource Manager.
You can create a Resource either by entering the user information into Resource Manager, or by importing an employee from Oracle Human Resources into Resource Manager.
To synchronize any changes that have been made to employee information in Human Resources with Resource Manager, you must run the Synchronize Employee concurrent program from CRM administrator responsibility.
If you do not create a resource properly for the user, the user receives an error message when accessing proposals:
You do not have access to view or create proposals. Please contact your administrator to set up your user profile.
For information on creating a resource, see the Oracle Trading Community Architecture User Guide.
In Self-Service mode, there are two seeded responsibilities that can be assigned to the user giving the user access to Oracle Proposals:
Oracle Proposals Administrator
Oracle Proposals User
The system administrator can use an alternative method of assigning menus and functions to the Oracle Proposals user after the FND user has been created and a responsibility has been assigned:
Proposal Main Menu (PRP_MAIN_MENU)
Proposal Homepage Function (PRP_PR_PROPOSAL_HOME)
See the Oracle E-Business Suite Security Guide for details.
There are two profile options that must be set for e-mail capability in Oracle Proposals:
PRP: SMTP Server Name
PRP: SMTP Server Port
Oracle Proposals uses the e-mail address stored in Resource Manager for the contact. Therefore, the Synchronize Employee Concurrent Manager needs to be run any time there is an update to e-mail information in Human Resources or FND.
Note: If the Synchronize Employee Concurrent Manager is not run properly, the sales representative's e-mail address used to send the proposal by e-mail to the customer will not be correct.
Users should be given access to the e-mail SMTP server from the middle tier. Otherwise, users can receive an error when e-mailing proposals.
Oracle Proposals Profile Options
Before users can create proposals, a user who is identified as the proposals administrator needs to set up the following:
Template Categories
Templates
Components
Dynamic Fields
See the Proposals User Guide for details on template administration.
There are three flows in which proposals can be created - Business-to-Business (B2B), Business-to-Consumer (B2C), and a combination of both. Out of the box, the B2B flow is enabled. Depending on your organization requirements, you could also enable the B2C flow by doing the following:
In the Create Proposal and Update Proposal pages, hide the Contact Name field and the Select button using OA Personalization. In a B2C flow, there are no contacts.
In the Proposal Views Page, hide the Contact column, the Contact Name field and the Select button in the detail area.
Set the profile HZ: Default Party Type to Person.
Refer the Oracle Sales Implementation Guide for more details on this profile.
Verify that you can perform the following tasks after you have finished the implementation steps:
Creating users and assigning the appropriate menu or function.
Verifying that the FND User name is populated and that the user is in Resource Manager as a Resource.
Setting up the Oracle Proposals profile options.
Creating and administering template categories, components, and templates.
You must also be able to complete all of the following tasks successfully, or Oracle Proposals has not been implemented properly.
Create a proposal.
View a proposal.
Generate a proposal document.
Delete a proposal.
Send a proposal document by e-mail.
If you are able to perform these functions successfully, the implementation has been successful. See the Oracle Proposals User Guide for details on working with Proposals.