This appendix covers the following topics:
Before making Oracle Forms settings, ensure that all Oracle Applications server processes are up and running. In particular, if you stopped concurrent managers before applying Oracle Applications patchsets, restart them now by changing to $COMMON_TOP/admin/scripts, and executing adcmctl.sh<APPS username?Apps password>start.
Use the following procedure to set a profile option.
None.
Log in to Oracle Forms as a System Administrator and navigate to Functions > Profile > System.
In the Find System Profile Values window, check the level(s) at which you want to set the profile option. The available levels are listed below:
Site: Indicates that profiles are set at the site level. This site level setting affects the entire database.
Application: If you select this level, choose the application from the Application LOV for which you want to set the profile option.
Responsibility: If you select this level, choose the responsibility from the Responsibility LOV for which you want to set the profile option.
User: If you select this level, choose the user from the User LOV for whom you want to set the profile option.
In the Profile field, enter the profile name, such as PV: Item Validation Organization, or a wildcard search criterion such as PV%.
Click Find.
The System Profile Values form opens with the results of your search.
Verify or set the profile option(s) at the levels that you selected.
To implement the Channel Manager dashboard, set the profiles listed in the following table.
Profile Name | Required | Level | Setting | Description |
---|---|---|---|---|
PV: New Partners Time Window | Yes | Site Application Responsibility User |
Numeric value. Seeded Value = 30 |
Used in the Key Metrics bin in the New Partners statistics. The bin shows the number of partners registered in the system in the last N days, where N is the seeded value. |
PV: Inactive Partners Time Window | Yes | Site Application Responsibility User |
Numeric Value. Seeded Value = 90 |
Used in the Key Metrics bin in the Inactive Partners statistics. The bin displays the number of partners in the system that have not placed orders in the last N days, where N is the seeded value. |
PV: Territory Assignment Online | Yes | Site Application Responsibility User |
Yes/No Seeded Value = Yes |
If the value is Yes, the channel team assignment occurs automatically when a partner is created or updated. If the value is No, the channel team is assigned when the concurrent program PV: Channel Team Assignment for Partner in TOTAL/INCREMENTAL Mode is run. Note: If you are importing a large number of partners from an external system, it is recommended that you set the option to No. |
PV: Batch size for territory assignment processing | Yes | Site Application Responsibility User |
Numeric value Seeded Value = 1000 |
Calculates the number of child processes that are created when the PV: Channel Team Assignment for Partner concurrent program is run in TOTAL/INCREMENTAL mode. |
To implement deal registration, set the profiles listed in the following table.
Profile | Required | Level | Setting | Description |
---|---|---|---|---|
PV: Default Indirect Channel Type | Yes | Application Responsibility |
Name of an indirect sales channel | This profile option specifies the indirect sales channel to which all opportunities generated from deal registrations will be assigned. |
ASN: Opportunity Access Privilege | Site Application Responsibility User |
Full Sales team |
This profile determines which opportunities a user can access. If set to Sales Team, a user can only access opportunities where the user is on the sales team or at least one of the user’s subordinates is on the sales team. Sales Team is the default. If set to Full, a user can access all the opportunities. | |
PV: Default Deal Registration Approver | Site Application User |
A user | Specifies a user as the default deal registration request approver if the Oracle Approvals Management approval rule does not return an approver. Alternatively, an organization can use this profile option to specify an approver instead of setting up approval rules in Oracle Approvals Management. |
|
PV: Default DQM Approver | - | A user | Specifies a user as the default Data Quality Management approver if Oracle Approvals Management does not return an approver. Alternatively, an organization can use this profile option to specify an approver instead of setting up approval rules in Oracle Approvals Management. |
|
PV: Assign Approvers to lead or opportunity | Site Application Responsibility |
Yes No |
When set to Yes, the deal registration approvers are automatically added to the sales team if the deal registration generates an opportunity or lead. When a lead is created, the owner of the lead is set to the first approver for the deal registration. If the PV: Assign Channel Manager to sales transactions profile option is also set to Yes, the owner of the lead is set to one of the channel managers for the deal. |
|
PV: Assign Channel Manager to sales transactions | Site Application Responsibility |
Yes No |
When set to Yes, the channel manager assigned to the partner that submitted the request is added to the sales team if the deal registration generates an opportunity or lead. When a lead is created, the channel manager also becomes the owner of the lead. If multiple channel managers are assigned to the partner, the owner is selected randomly. |
|
PV: DQM Contact Match Rules | Site Application Responsibility |
DQM rule name | This profile stores the Data Quality Management rule that is used to perform contact matching for the customer. | |
PV: DQM Customer Match Rules | Site Application Responsibility |
DQM rule name | Stores the Data Quality Management rule that is used to perform customer matching. | |
PV: Contact Relationship Codes | Site Application Responsibility |
Contact Of | Used to determine the relationship of the contact with the customer. | |
PV: Enable Single Column Layout in Additional Details | Site Application Responsibility User |
Yes/No | When this profile is set to 'Yes' the attributes on the additional detail section on the Referral/Deal Registration Create Screen are rendered in a Single Column. By default the format is double column. | |
PV: iStore Login URL | Site | <hostname>:<port> | Partner Login URL link sent with workflow notification for partner users. | |
PV:Self Service URL with Workflow Notification | Site | <hostname>:<port> | Vendor Self Service Applications URL sent with a workflow notification for vendor users. | |
HZ: Generate Party Number | Site Application Responsibility User |
Yes No |
If this profile is set to Yes, as part of the customer de-duplication process for deals, a new customer and its corresponding party number are created in the system if no match is identified. | |
HZ: Generate Party Site Number | Site Application Responsibility User |
Yes No |
If this profile is set to Yes, as part of the customer de-duplication process for deals, a new customer and its corresponding party site number are created in the system if no match is identified. |
To implement enrollments, set the profiles listed in the following table.
Option | Required | Level | Setting | Description |
---|---|---|---|---|
PV: Program Enrollment Request Reminder Notification Duration | Yes | Site Application |
Default=15 | If the enrollment request approver does not act upon an enrollment request in the number of days specified by this profile, the request is forwarded to the default approver. |
PV: Default Enrollment Request Approver | Yes | Site Application |
A user | Specifies a user as the default enrollment request approver if the Oracle Approvals Management approval rule does not return an approver. Alternatively, an organization can use this profile option to specify an approver instead of setting up approval rules in Oracle Approvals Management. |
PV: Allow Approval Without Contract | Yes | Site | Yes No |
Determines whether or not a partner program enrollment request can be approved before a signed contract is received from the partner. Yes: Approval without signed contract is allowed. No: A signed contract must be received before a request can be approved. |
PV: Default Salesperson used for Orders | Yes | Responsibility or Site level depending on what orgs partner users belong to (sales reps are org striped) | A valid Sales rep. At run time, sales rep retrieved from this profile option needs to be a valid sales rep for the 'MO: operating Unit' of user's logged in responsibility | Oracle Order Management requires that a sales person be identified for each order. This profile option allows you to specify a CRM resource as the sales person for each enrollment request order. A sales quota will be associated with the person specified; enter a fictional resource if a sales quota should not be associated with orders generated from partner program enrollments. |
PV: Order Cancel Reason | Yes | Site | Reason codes form the Oracle Order Management CANCEL_CODE Lookup | Provides an order cancellation reason for a partner program enrollment request. This reason will be used when an enrollment request is cancelled because:
|
PV: Order Transaction Type | Yes | Responsitiliby or Site | Any transaction type that is applicable for non-shippable items and that can provide invoicing capability. | As Order Management transaction types are org striped, this profile option needs to be set at either responsibility or site level depending on what orgs partner users belong to. At run time, transaction type retrieved from this profile option needs to be a valid transaction type for the 'MO: operating Unit' of user's logged in responsibility. |
PV: Max number of credit card authorization | Optional | Site | Default = 3 Numeric value |
Specifies the number of times that a credit card authorization can fail. If the number specified has been exceeded, the enrollment request ends, and the user is returned to the Partner Dashboard. The registration is saved, including the contract information. In addition, billing information is saved by Oracle Order Management. |
IBE: iStore Secure URL | Optional | Site | This profile option needs to be set to secure server and port that should be used in payment pages | If this profile is set, payment pages use this secure (https) server and port. Otherwise, the regular port in payment page is used. Example of this profile option value: https://qapache.us.oracle.com:2000/OA_HTML/ |
IBE: iStore Non Secure URL | Optional | Site | This profile option needs to be set to non secure server and port that should be used after processing payment | If the profile is set, the server and profile mentioned is used to switch to a nonsecure url once payment has been processed. Otherwise, the same port that is used in payment pages are used. Example of this profile option value: http://qapache.us.oracle.com:1111 /OA_HTML/ |
Sequential Numbering | Yes | Site Application Responsibility |
Always Used | Specifies that orders created in Order Management are numbered sequentially. |
MO: Operating Unit | Yes | Responsibility | Default operating unit | Specifies the operating unit against which users place orders. The user can view and purchase items that are in the Inventory Organization associated with this operating unit only. Set to the default operating unit at the customer responsibility level. |
To implement partner funds, set the profiles listed in the following table.
Profile Option | Required | Level | Setting | Description |
---|---|---|---|---|
OZF_SF_GRACE_DAYS | Optional | Site Responsibility |
Numeric value Default = 0 |
Specifies a grace period for a partner fund. The system uses the number of days specified in this profile to determine for how long after the fund approval date a fund request remains active. Once the grace period has passed, the status of the fund request changes to Closed, and claim can no longer be submitted against the fund request. Note: By default, this profile is set to zero, which specifies up a grace period of one day. You must change this profile to provide for a realistic grace period. |
OZF_SF_DEFAULT_BENEFIT | Optional | Site Responsibility |
List of fund request benefits | Used to set up default benefit for fund requests. For deployments that do not use partner programs, this profile can be used to set up a partner fund benefit. |
OZF_SF_DEFAULT_APPROVER | Optional | Site Responsibility |
A user | Specifies a user as the default fund request approver if the Oracle Approvals Management approval rule does not return an approver. Alternatively, an organization can use this profile option to specify an approver instead of setting up approval rules in Oracle Approvals Management. |
To implement opportunities, set the profiles listed in the following table.
Option | Required | Level | Setting | Description |
---|---|---|---|---|
PV: Partner Matching Type | Optional | Site | Default is Stop at first rule at site level | Possible Values: Exhaust all rules - The partner matching engine evaluates each rule (that matches the conditions specified in the Opportunity Selection section of each rule), by order of precedence, until it finds a partner. If there was a preferred partner specified on the opportunity, the evaluation stops at the first rule regardless of whether the first rule evaluated returned any partner. Stop at first rule - The partner matching engine, after finding a rule that matches the conditions specified in the Opportunity Selection of that rule, uses only that rule in finding partners. |
PV: Enable Full Access on Opportunity to Partner | Optional | Site | Yes | This profile is used to determine whether partner contacts are added to the opportunity sales team with full access or read-only access during opportunity routing. If set to Yes, the partner, after accepting the opportunity can update the opportunity details. If set to No, the partner user has read-only access to the opportunity. In addition, the partner can create notes and add attachments. |
PV: Filter Partner Search by Identifying Address | Optional | Site Application Responsibility |
Yes No |
If the profile is set to Yes, the partner Simple Search, Advanced Search, and Generate Partner List return partner identifying addresses only, and the results pages display partner identifying addresses only. If the profile is set to No, all partner address are returned by the searches, and the pages display all partner addresses. |
PV: Active Notification Flag | Optional | User | Yes No |
User can enable or disable notifications when the partners accepts an opportunity. If set to Yes, the partner contact receives a notification when the routing status changes from Offered to Active. |
PV: Bypass CM Approval for Campaign Routing | Yes | Site | Yes No |
Determine whether channel manager approval is required for partners matched by a campaign. This profile option is used along with PV: Enable Automatic Routing by Campaign. The default value is No. |
PV: Common Currency for Rules Engines | Yes | Site | Any available currency | Base currency used for currency comparison in partner matching. If the currency specified for the rule is not the same as the base currency, it is converted to the base currency and then the comparison is performed. This profile is also used by the concurrent program PV Refresh Attribute Text Table. The default is USD. |
PV: Default Batch Assignment User | Optional | Site | A User | This user is added to the sales team of an opportunity which failed to complete the full automated background Lead to Opportunity to Routing process. |
PV: Default CM TimeOut | Optional | Site | Numeric value | Default channel manager timeout in hours if not specified at the country level. Sets the time period available to channel managers to review and approve partner matching and selection. If the channel manager does not respond in the given time, the default response is Match Approved. |
PV: Default Partner TimeOut | Optional | Site | Numeric value | Default partner timeout in hours if not specified at the country level. Sets the time period available to Partner Contacts to accept the offered opportunity. If no response, the default response is Offer Declined. |
PV: Default Routing Type | Yes | Site | Default = Single Multiple-Serial Multiple-Parallel Joint |
Default assignment type used by the background partner routing. Partners default assignment type. |
PV: Default Unassigned Opportunity TimeOut | Optional | Site | Numeric value | Sets the time period an unassigned opportunity may have the Unassigned routing status. At the expiration of the time period, a concurrent manager program, PV Unassigned Opportunity Process After Timeout, performs automatic matching and routing. |
PV: Default Vendor User (Channel Manager) | Optional | Site Application Responsibility |
- | Default channel manager used if none found for partner. |
PV: Default for Bypass Channel Manager approval checkbox | Optional | - | - | Determines the display of the Bypass channel manager approval flag on the opportunity assignment page. Possible Values: Bypass CM - Allow update Bypass CM - No Update Allowed Do not Bypass CM - Allow Update Do not Bypass CM - No update Allowed |
PV: Display Submit Routing Button | Optional | Site Application Responsibility User |
Yes/No | Enable and disable ability for user to submit or withdraw assignment routing. When set to Yes, a Submit Routing button is displayed on the opportunity assignment page. This profile is not available to partner users. The default is No. |
PV: Enable Automatic Routing by Campaign | Optional | Responsibility | Yes/No | Enables automatic routing based on campaigns. When the campaign field is completed, the system adds associated partners to the sales team, opportunity routing list and starts the routing process. The default is No. |
PV: Enable Partial Matching of Attributes | Optional | All | No | Enables the partner matching engine to return partners even if an exact match is not found for manual matching. The algorithm used is: if no partners are returned for the search conditions specified, the lowest ranked condition is dropped and the engine performs the search again. This process continues until at least one partner is found or all the search conditions are exhausted. |
PV: Enable Workflow to send e-mails | Yes | Site | Yes/No | Enable or disable notifications in indirect opportunity management. |
PV: Enforce Address Filters in Partner LOV | Yes | Site | Yes/No | If set to Yes, the partner LOV allows a search based on partner name and address. |
PV: Java Class to Restrict ORG Access Privilege | Optional | Site | Java Class Filename | Customizable Java Class is available to restrict partners from accessing customer details from the opportunity pages by clicking the customer link. |
PV: Locator Default Distance Unit | Yes | Site Application Responsibility User |
Distance Unit | Default distance unit for manual search. Also used for automatic matching if rule selected did not specify distance unit. This is also used by the reseller locator. The default value is Mile. |
PV: Locator Proxy Port | Yes | Site | - | Proxy server port. The default value is 80. |
PV: Locator Proxy Server | Yes | Site | - | Proxy server address. The default value is www.proxy.us.oracle.com. |
PV: Locator Server Timeout | Yes | Site Application Responsibility User |
Time in milliseconds | Timeout for the eLocation Request used in reseller locator. The default value is 20000 milliseconds. |
PV: Matched Notification Flag | Optional | User | Yes No |
User can enable or disable the notification when an opportunity is matched. If set to Yes, the user receives an e-mail notification when an opportunity is matched with a partner. The default is Yes. |
PV: Matching Rule Selected by Engine | Yes | User | Yes/No | If set to Yes, the matching rule is selected by the Rules Engine in automatic matching. If set to No, a user is able to select the rule to use for opportunity matching. The default value is No. See Profile PV: Rule for Automatic Matching. |
PV: Max Number of Matched Partners | Yes | Site | - | Maximum number of partners returned during partner matching (manual and automatic). If the value is not specified, the number of partners returned is 10. |
PV: Offered Notification Flag | Optional | User | Yes/No | If set to Yes, the user receives an e-mail notification when an opportunity routing status changes to Offered. |
PV: Require Opportunity Contact for Manual Routing | Optional | Resp | Yes/No | Do not allow, or allow assignment routing if there are no opportunity contacts. When set to Yes, a contact name for the opportunity is required for manual and batch routing to start. If set to No, a contact name is not required. The default is No. |
PV: Restrict Sales Team Partner Contact LOV | Optional | Site | Yes No |
For customer external sales team, if 'Yes', restrict the display of contacts to those partners that the sales team member can access. |
PV: Rule for Automatic Matching | Yes | Site | Yes No |
If the profile, PV: Matching Rules Selected by Engine is set to No, this profile is used to determine which rule to use for automatic matching. |
PV: Trace for Auto Matching | Optional | Site Application Responsibility User |
Yes No |
If set to Yes, automatic partner assignment process trace is displayed in the UI for debugging. The default value is No. |
PV: Unassigned Notification Flag | Optional | User | Yes No |
If set to Yes, user receives a notification for a new opportunity with routing status 'Unassigned'. The default is Yes. |
PV: Withdrawn Notification Flag | Optional | User | Yes No |
If set to Yes, the user receives an e-mail notification when an opportunity routing status changes from Offered to Withdrawn. The default is Yes. |
Applications Server-Side Proxy Host and Domain | Optional | Site | - | This is used by the TCA concurrent program, Spatial Information for Locations Batch Update. |
HZ: Spatial Provider URL | Yes | Site Application Responsibility User |
A URL | A URL for Spatial Information on Location (Default at site level is http://elocation.oracle.com/elocation/lbs). This is used by the TCA concurrent program, Spatial Information for Locations Batch Update. |
HZ: Web Server Proxy Host Name | Optional | Site Application Responsibility User |
Web Server Proxy Name | This is used by the TCA concurrent program, Spatial Information for Locations Batch Update. |
HZ: Web Server Proxy Port | Optional | Site Application Responsibility User |
Web Server Proxy Port | This is used by the TCA concurrent program, Spatial Information for Locations Batch Update. |
OS: Auto Convert Lead to Opportunity | Yes | Site | Yes/No | If Yes, the system converts indirect leads to opportunities and performs automated rule-based partner assignment. |
PV: Locator Server URL | Yes | Site | http://elocation.oracle.com/servlets/lbs | PV Locator URL used to get the eLocation service |
PV: Skip eLocation for Partner Matching Service | Optional | Site Application Responsibility User |
Yes No |
If 'Yes', system skips eLocation server and perform geo-proximity analysis based on radial distances only. If value is not set, the system defaults to No. |
PV: Unassigned Opportunity Timeout (Days) | Yes | Site | 10 | Number of days an indirect Opportunity has stayed unassigned. Used by concurrent program PV - Unassigned Opportunity process after timeout. |
PV: Abandon Notification flag | Optional | User | Default = Yes No |
User can enable or disable notification when opportunity is abandoned. |
PV: Recycled notification flag | Yes | User | Default = Yes No |
User can enable or disable notification when the opportunity is recycled. |
PV: iStore Login URL | Yes | Site | http://Machine Name:Port No/OA_HTML/ibeCAcdLogin.jsp?ref=ibeCZzdMinisites.jsp?grp=PARTNER | Defines a URL for an iStore. The URL is embedded in workflow notifications that are received by partner users. |
PV:Self Service URL with Workflow Notifications | Yes | Site | http://Machine Name:Port No/OA_HTML/ibeCAcdLogin.jsp?ref=ibeCZzdMinisites.jsp?grp=PARTNER | Defines the URL for self-service log in that is embedded in the program approval request notifications that are received by a vendor user. |
ASN: Opportunity Access Privilege | Yes | Site Application Responsibility User |
Full Sales Team |
Determines which opportunities a user can access. If set to Sales Team, a user can only access opportunities where the user is on the sales team or at least one of the user's subordinates is on the sales team. Sales Team is the default. If set to Full, a user can access all opportunities. |
To implement the Partner Dashboard, set the profiles listed in the following table.
Option | Required | Level | Settings | Description |
---|---|---|---|---|
ASO: Default Quote Status | Yes | Application | STORE DRAFT DRAFT |
Set to STORE DRAFT if iStore is used as the partner ordering tool. If quoting is used as the partner quoting / ordering tool, set to DRAFT. |
PV: Default Vendor Organization | Yes | This can be set up at the application or site level if there is only one internal vendor organization that should be used to create partner of relationship. This should be set up for the default responsibility that is derived from partner geography when a new partner is registered. |
- | Used during the self-service registration and Customer to Partner conversion to identify which internal organization should be used for creating partner-of relationship between partner and vendor internal organization. |
FUNCTION_SECURITY_REGION | Yes | Responsibility | PV_PARTNER_FUNC_SEC_REGION | Needs to be set up for each partner user responsibility that will be assigned to users who will need to access Oracle Partner Management transactional pages. |
PV: Filter Partner Search by Identifying Address | Yes No |
If the profile is set to Yes, the partner Simple Search, Advanced Search, and Generate Partner List return partner identifying addresses only, and the results pages display partner identifying addresses only. If the profile is set to No, all partner address are returned by the searches, and the pages display all partner addresses. |
||
IBE: Enable Shopping Cart Global Icon | Optional | Responsibility | Yes No |
Enables or disables the Shopping Cart global icon. Set this option to No for partner site responsibility. |
IBE: Enable Order Tracker Global con | Optional | Responsibility | No | Enables or disables the Order Tracker global icon for partner sites. This needs to be disabled for the partner dashboard at the responsibility level. |
IBE: Enable Quick Search | Optional | Responsibility | No | Enables or disables the Quick Search for partner sites. This needs to be disabled for the partner dashboard at the responsibility level. |
IBE: Use Web Placements | Yes | - | - | Needs to be set to View eMerchandising Postings in the marketing postings bin. The Marketing postings bin requires additional implementation steps to see the eMerchandising postings in the partner site. For more information, see Oracle iStore Implementation Guide. |
IBE: Quick Links Menu | Yes | Responsibility | - | This is a mandatory profile if the Quick Links bin needs to be displayed when logging in with a particular responsibility. Needs to be set up to the correct FND menu from which quick links are rendered. This needs to be setup at responsibility level for partner site responsibility. Partner Super User responsibility should have this profile option set up as a Partner User Sub Menu. |
IBE_USE_ORDER_TRACKER | Optional | Site Application Responsibility User |
- | The order tracker icon is displayed by default in the global icons section of any site. The icon can be disabled using this profile. This profile has the site level value seeded as Yes. Customers can turn off this profile at the application level if Oracle Partner Management and Oracle iStore are not implemented together in one site. If Oracle iStore and Oracle Partner Management are both implemented, this profile should be set to No at the partner responsibility level. |
To implement the partner locator, set the profiles listed in the following table.
Profile Name | Required | Level | Setting | Description |
---|---|---|---|---|
PV: Locator Default Distance Unit | Yes | Site | Default = Mile | Default distance unit used to search for a partner. |
PV: Locator Proxy Port | Yes | Site Application Responsibility User |
number | Proxy Server port number |
PV: Locator Proxy Server | Yes | Site Application Responsibility User |
address | Proxy Server address |
PV: Locator Server URL | Yes | Site Application Responsibility User |
http://elocation.orcle.com/servlets/lbs | PV Locator URL used to get the eLocation service |
PV: Locator Skip eLocation Server | Yes | Site Application Responsibility User |
Default = No | If set to Yes, system sill skip the eLocation server and perform geo-proximity analysis based on radial distances |
PV: Locator Distance | Yes | Site Application Responsibility User |
Default = 10 | The Reseller Locator will search for partners within this distance. |
PV: Locator Maximum No. Of Partners | Yes | Site Application Responsibility User |
number | The maximum number of partners returned with the Partner Locator is searching for partners. If not specified, the default is 20. |
PV: Locator Partners Per Page | Yes | Site Application Responsibility User |
number | Number of partners that can be displayed per page in the Partner Locator. If not specified, the default is 10. |
Applications Server-Side Proxy Host and Domain | Yes | Site | host and domain | Used by the TCA concurrent program Spatial Information for Locations Batch Update. |
HZ: Spatial Provider URL | Yes | Site Application Responsibility User |
a URL | A URL for Spatial Information on Location (Default at site level is http://elocation.oracle.com/elocation/lbs). This is used by the TCA concurrent program, Spatial Information for Locations Batch Update |
HZ: Web Server Proxy Host Name | Yes | Site Application Responsibility User |
a web server proxy name | Used by the TCA concurrent program Spatial Information for Locations Batch Update. |
HZ: Web Server Proxy Port | Yes | Site Application Responsibility User |
a web server proxy port | Used by the TCA concurrent program Spatial Information for Locations Batch Update. |
To implement partner profile attributes, set the profiles listed in the following table.
Profile Name | Required | Level | Setting | Description |
---|---|---|---|---|
OS: Forecast Calendar | Optional | Site | - | This profile sets the accounting calendar that is used to determine the start and end dates for the company's fiscal year. |
OS: Default Period Type for Currency Conversion | Optional | Site | - | Default Period Type for Currency Conversion |
PV: Common Currency for Rules Engines | Optional | Site Application Responsibility User |
- | Used by the concurrent program PV: Refresh Partner Trend Values and PV Refresh Attribute Text Table to convert and store all currency attributes in this currency. This enables currency comparison to be performed accurately. |
PV: Enable Profile Attribute Security | Required | Site | No | Used to control if users can only view or view and update partner attributes |
PV: Partner Trend Last Refresh | - | - | - | Can not be updated. Used by Refresh Partner trend concurrent program to determine the last incremental refresh time. |
PV: Refresh Search Attributes Last Update Date | - | - | - | Not updatable by the users. Used by Refresh Partner trend concurrent program to determine the last incremental refresh time. |
PV: Vad/Partner Full Access To Profile Screens | Site Application Responsibility User |
Default = N | This profile determines whether a partner or distributor can update their company profile and their own profile information from the partner dashboard. | |
PV: Attribute Percentage Total | Site Application Responsibility User |
Default = 100 | Used by attributes with a display style of Percentage to determine the percentage that its values should add up to. For example, if 80 is specified, the values for the attribute must add up to 80 percent. |
To implement partner programs, set the profiles listed in the following table.
Option | Required | Level | Setting | Description |
---|---|---|---|---|
PV: Default Program for New Partner | Optional | Site | Program name | When this profile option is set, every time a new partner is created in the system, the partner gets automatically enrolled into this program after registration. |
AMS : Item Validation Master Organization | Yes | Site | A valid master inventory organization | Creates a partner program as an item in Oracle Inventory under the specified master organization. |
PV:Self Service URL with Workflow Notification | Yes | Site | http://servername:port/OA_HTML/US/ICXINDEX.htm | Defines the URL for the self-service log that is embedded in the program approval request notifications that are received by a vendor user. |
PV: Is External Responsibility | Optional | Responsibility | Yes No |
When set to Yes for a responsibility, the responsibility can be mapped to a partner program. When a partner user joins the program, he is assigned the responsibility specified. When set to No, the responsibility is not available for partner users. |
PV: iStore Login URL | Yes | Site | http://Machine Name:Port No/OA_HTML/ibeCAcdLogin.jsp?ref=ibeCZzdMinisites.jsp?grp=PARTNER | Defines a URL for an iStore. The URL is embedded in workflow notifications that are received by partner users. |
PV: Allow Approval without Contract | Yes | Site | Yes No |
Specifies whether or not a partner program enrollment request can be approved before a signed contract is received from the partner Yes: An enrollment request can be approved without a signed contract No: A signed contract must be received before an enrollment can be approved. |
PV: Contract Terms Layout Template for Preview | Site | Layout Template for Formatting Terms and Conditions in Partner Management when previewing a template or an accepted contract. | ||
IBC: Use Access Control | Optional | Site | Yes Null No |
Determines whether a security check is required when a vendor user accesses Oracle Content Manager to set up a Program Overview. No or Null: Disables the security check. Yes: Enables the security check. When Yes is specified, addition security set up is required within Oracle Content Manager. |
QP: Source System Code | Yes | Application | Default = Oracle Special Pricing Oracle Application Name |
Specifies the Oracle application that will be the source of the price lists used by Partner Programs. |
Self Service Accessibility Feature | Yes | Site | Screen Reader Optimized NONE Standard Accessibility |
A rich text editor can be used to create a Program Overview. The editor offers the ability to add images and formatting to an Overview, which can cause accessibility challenges for some users. This profile option allows you to enable or disable the rich text editor, and to select an editor that provides greater accessibility for users. Three settings are available for the editor: NONE: Enables the rich text editor, and makes the accessibility-specific features unavailable Screen Reader Optimized: Content is optimized for reading on a computer screen Standard Accessibility: Accessibility compliant mode |
PV: Concatenated Inventory Flex Segments for Program | Yes | Site Application Responsibility |
Free flow text | This value is used to populate the key flexfield segment values while creating the program as an inventory item internally. The value should be in the format: Segment1.Segment2.Segment3.Segment4 etc. (Etc.is just to denote as many segments as implemented). Here Segment1, 2,3… should be the values of the key flexfield segments that are used for inventory item creation from program. The delimiter should be the one that inventory uses to define the segments. One of the segment values should have the code PV_PRGM_FLEX_CODE. This code is replaced with first five characters of program name concatenated with program_id while creating the inventory item. So, for example, the value could be US.SOFTWARE.EBUS.PV_PGRM_FLEX_CODE where US, SOFTWARE are key flexfield segment Values and '.' is delimiter. |
QP: Multi-Currency Usage | Yes | Application | Yes No |
Determines whether or not an application can use multiple-currency price lists. Make sure that other Oracle applications that use price lists and that you are integrating with have the same setting for this profile options. By default, no setting is provided for the profile. |
JTF_PROFILE_DEFAULT_RESPONSIBILITY | Yes | Site | Same as vendor responsibilities | For any vendor responsibilities which have access to the Oracle Partner Management lists of values, set the profile value to the same responsibilities. Make sure the profile value in user level is set to null. |
PV: Default UOM Code | Yes | Site | Unit of measure used by enterprise | You must set the unit of measure for the master inventory to ensure that the unit of measure matches up with your inventory application. |
OZF: Global Flag for Pricing Related Objects | Yes | Site or Application | Mandatory |
To implement referral management, set the profiles listed in the following table.
Option | Required | Level | Setting | Description |
---|---|---|---|---|
PV: Default Indirect Channel Type | Yes | Application Responsibility |
Name of an indirect sales channel. | This profile option specifies the indirect sales channel to which all opportunities that are generated for a specific partner from referral will be assigned. Opportunities that generated from referrals but are not created for a specific partner are assigned a sales channel using the OS: Default Sales Channel profile option. |
ASN: Lead Access Privilege | Site Application Responsibility User |
Full Sales Team |
This profile determines which leads a user can access. If set to Sales Team, a user can only access leads where the user is on the sales team or at least one of the user’s subordinates is on the sales team. Sales Team is the default. If set to Full, a user can access all the leads. | |
ASN: Opportunity Access Privilege | Site Responsibility User |
Full | This profile drives the behavior of opportunity access. This profile is defined within the Sales Application but Oracle Partner Management uses it to drive access to referrals. If this profile is set to Full, users can view all the referrals that have been approved and converted into opportunities or linked to opportunities that the users can access. If this profile is set to another value, users can only view referrals linked to opportunities for which they are on the sales team. | |
PV: Default Referral Approver | Site | A user | Specifies a user as the default referral request approver if Oracle Approvals Management does not return an approver. Alternatively, an organization can use this profile option to specify an approver instead of setting up approval rules in Oracle Approvals Management. |
|
PV: Assign Approvers to lead or opportunity | Site Application Responsibility |
Yes No |
When set to Yes, the referral approvers are automatically added to the sales team if the referral generates an opportunity or lead. When a lead is created, the owner of the lead is set to the first approver for the referral. If the PV: Assign Channel Manager to sales transactions profile option is also set to Yes, the owner of the lead is set to one of the channel managers for the referral. The owner is selected randomly. |
|
PV: Assign Channel Manager to sales transactions | Site Application Responsibility |
Yes No |
When set to Yes, the channel manager assigned to the partner that submitted the referral is added to the sales team if the referral generates an opportunity or lead. When a lead is created, the channel manager also becomes the owner of the lead. If multiple channel managers are assigned to the partner, the owner is selected randomly. |
|
PV: Copy Lead Owner or Sales team members on approval notifications | Site Application Responsibility |
- | If this profile is set to 'Yes', notifications are sent to lead owners if a lead is generated from a referral, or to sales team members if an opportunity is generated from a referral. Note: The referral benefit must be configured to send notification to those user types. |
|
PV: DQM Contact Match Rules | Site Application Responsibility |
DQM rule name | This profile stores the Data Quality Management rule that is used to perform contact matching for the customer. | |
PV: DQM Customer Match Rules | Site Application Responsibility |
DQM rule name | This profile stores the Data Quality Management rule that is used to perform customer matching. | |
OZF: Validate market and product eligibility between object and budget | Site Responsibility |
Yes No |
Enables budget validation when a referral offer is created. This profile should be set at the responsibility level for the Channel Administrator responsibility and it should be set to Validate customer and products by each budget. | |
QP: Source System Code | Site Application User |
- | This should be set at the application level for Oracle Partner Management. It should be set to the same value that the Oracle Marketing application is set to. | |
AMS: Allow Recalculation of Committed Budget | Site Application Responsibility User |
Yes No |
If this profile is set to Yes, when the budget exceeds the limit while making the accrual, the accrual is allowed to exceed the budget's committed amount, enabling the offer to ask for more funds later. | |
OZF: Allow committed budget to exceed total amount | - | Yes No |
If set to Yes, the referral benefit can be activated even though the requested budget amount exceeds the total budget amount. If set to No, the referral benefit will fail validation if the requested budget amount exceeds the total budget amount. |
|
PV: Contact Relationship Codes | Site Application Responsibility |
Contact Of | When a new customer contact is created, this profile is used to determine the relationship of the contact with the customer. | |
PV: iStore Login URL | Site | <hostname>:<port> | Partner login URL link sent with workflow notification for the partner users. | |
PV:Self Service URL with Workflow Notification | Site | <hostname>:<port> | Vendor Self Service Applications URL sent with a workflow notification for vendor users. | |
PV: Default DQM Approver | SIte Application Responsibility |
A user | Specifies a user as the default Data Quality Management approver if Oracle Approvals Management does not return an approver. Alternatively, an organization can use this profile option to specify an approver instead of setting up approval rules in Oracle Approvals Management. |
|
HZ: Generate Party Number | Site Application Responsibility User |
Yes No |
If set to Yes, as part of the customer deduplication process for referrals, a new customer and its corresponding party number are created in the system if no match is identified. | |
HZ: Generate Party Site Number | Site Application Responsibility User |
Yes No |
If set to Yes, as part of the customer deduplication process for referrals, a new customer and its corresponding party site number are created in the system if no match is identified. | |
PV: Enable Single Column Layout in Additional Details | No | Site Application Responsibility User |
Y N |
When set to Y (yes), renders the Additional Detail section of the Referral Creation/Detail page in a single column rather than in the standard double-column format. If no value is set, the double-column display is used. |
To implement special pricing, set the profiles listed in the following table.
Profile Option | Required | Level | Setting | Description |
---|---|---|---|---|
OZF_SP_ENABLE_PROD_SECURITY | Optional | Site Responsibility |
Yes/No | Value in the profile controls if all products should be displayed or only products belonging to categories assigned to a partner in the Special Pricing Product Categories field in the partner's profile. The user selects at the product category level. The partner can see all products under that category and subcategories. |
OZF_SP_GRACE_DAYS | Optional | Site Responsibility |
Numeric value | Specifies a grace period for a special pricing request. The system uses the number of days specified in this profile to determine how long (in days) after the request end date a special pricing request remains active. Once the grace period has passed, the status of the request changes to Closed, and claims can no longer be submitted against the request. Note: By default, this profile is set to zero, which specifies up a grace period of one day. You must change this profile to provide for a realistic grace period. |
OZF_SP_DEFAULT_APPROVER | Optional | Site Responsibility |
A user | Specifies a user as the default special pricing request approver if Oracle Approvals Management does not return an approver. Alternatively, an organization can use this profile option to specify an approver instead of setting up approval rules in Oracle Approvals Management. |
OZF_SP_DEFAULT_BUDGET | Optional | Site Responsibility |
One or more active, fixed budgets | Depending on an organization's business needs, a single special pricing budget can fund all special pricing requests, or multiple special pricing budgets can be set up. This profile is used to determine whether or not multiple budgets will be used and identifies the budget(s). Multiple budgets: Each budget is specified at the Responsibility level, where the responsibility is a business unit or geographic entity. The name of a budget (set up in Oracle Trade Management) is specified for each responsibility. Single budget: Specify the name of the budget (set up in Oracle Trade Management) at the Site level. |
OZF_SP_PARTY_DQM_RULE | Optional | Site Responsibility |
List of DQM rules for party match | Used to find the master party record for the reseller and end customer names, when submitting a special pricing request. |