Setting Up Partner Profile Attributes

This chapter covers the following topics:

Overview of Partner Profile Attributes

Oracle Partner Management provides an extensible attribute framework to manually or automatically capture any kind of information about your partners. This information is presented in the performance and profile tab on the partner detail page. Partner profile attributes that track a partner's performance, such as Sales YTD and Opportunities Won, are displayed in the performance tab.

Performance profiles are numeric calculated values, based on partner transactions, which are refreshed at user-defined intervals. Non-performance related profiles such as partner certification, partner industry, and partner annual revenue are displayed in the profile tab. These profile values are either entered manually--directly or through a program enrollment questionnaire--or derived based on partner transactions.

Partner profiles are also accessible to the partner user from the partner dashboard. Both vendor and partner users can update the profile information if assigned update permission. For more information on attribute security, see Setting Up Attribute Security. The application maintains a history of the changes for profiles that are updated manually including changes made to partner contact profiles. In addition to partner profile attributes, the extensible attribute framework is also used to manually capture partner contact profiles. This information is presented in the Profile tab on the Partner Contact Detail page for the vendor user.

Partner Profile Attributes

An attribute is a specific piece of information about an individual partner. Examples of partner attributes include a partner's geographic coverage, the number of opportunities a partner currently has open, and the number of referrals a partner has submitted year to date (YTD).

Attribute information can be collected from a partner program enrollment request, entered by a vendor or partner user, or calculated based on partner data and transactions.

Attribute information is used to create a profile for a partner, and is available from tabs on a partner's Partner Details page and View Trends page. Collectively, partner profile information is used to track key performance indicators that appear on the channel manager dashboard.

Oracle Partner Management provides you with a thorough set of seeded partner attributes, which are described in detail in the section, Seeded Attributes. In the application, a channel administrator can view all the attributes from the Attributes Overview page. For a description of the information available on this page, refer to The Attributes Overview Page. A channel administrator can also create customized attributes, if needed, to meet her organization's needs. Refer to Setting up Custom Attributes for additional information.

Seeded Attributes

Oracle Partner Management provides numerous seeded partner attributes. The seeded attributes track a variety of facts about a partner. For an individual partner, the attributes provide a thorough, up-to-date partner profile. Collectively, partner attributes are used to build a 360-degree view of a channel's performance. The Channel Administrator can view details about seeded attributes, and can also define the order in which the attributes appear on the profile.

Seeded attributes can be informational or performance based. Informational attributes provide information about a partner that is unlikely to change frequently, such as a partner's industry. Performance attributes provide current information about a partner's activities, and are updated by concurrent programs. Most seeded attributes are performance attributes.

Performance attributes can be cumulative or noncumulative. Performance attributes allow a vendor to track a partner's performance over a period of time and are captured at a monthly level. These monthly values can be further aggregated to an annual value for some performance attributes. Cumulative performance attributes are additive, meaning the measurements taken at the monthly levels can be summed up to calculate the yearly figure. For example, the attribute Opportunities Won YTD tracks the total number of indirect opportunities a partner has won during the current fiscal year and is the sum of Opportunities Won for each month for that fiscal year.

Noncumulative attributes are point in time values, providing a snapshot for a specific partner performance profile attribute at the time the attribute was refreshed. These monthly level values cannot be summed up to calculate the yearly figure. For example, the attribute Open Opportunities Count lists the number of opportunities that are open currently for a partner or partners. You cannot sum up the Open Opportunities Count for each month to derive the annual Open Opportunities Count, because most likely an open opportunity in a prior month will have closed in the current month.

There are three types of performance attributes:

The data contained in the Key Metrics bin is populated by a query, which draws data from the pv_search_attr_trends table and other partner tables. The following table provides information about Oracle Partner Management seeded partner attributes.

Seeded Attributes
Attribute Description Category Display Style Enabled For
Additional Channel Offering Additional services provided by the partner (Implementation specific) General Multi-Select Profile Tab
Allow Partner to Edit Opportunities A vendor can control partner opportunity access on a partner-by-partner basis      
Capacity Rating Partner's capacity rating (Implementation specific) General Single-Select Profile Tab
Claims Paid Total claim settlement amount paid for soft funds and special pricing request based on settlement date Marketing Currency Trends Page
Claims Paid YTD Total claim amount paid for soft funds and special pricing request based on settlement date during the current fiscal year Marketing Currency Performance Tab
Country Countries that the partner has a presence in General Multi-Select Profile Tab
Customer Annual Revenue Annual revenue of the partner as stored in TCA table General Currency Profile Tab
Deals Accepted Total deal amount accepted based on deal creation date Sales Currency Trends Page
Deals Accepted Count Total number of deals accepted based on deal creation date Sales Count Trends Page
Deals Accepted YTD Total deal amount accepted based on deal creation date during the current fiscal year Sales Currency Performance Tab, Key Metrics Bin
Deals Accepted YTD Count Total number of deals accepted based on deal created during the current fiscal year Sales Count Performance Tab, Key Metrics Bin
Deals Close Rate Deals Closed Count/Deals Accepted Count Sales Percentage Performance Tab
Deals Closed Amount of total number of closed opportunities, based on the date the deal status changes to 'Closed. Opportunity Won' Sales Currency Trends Page
Deals Closed Count Total number of closed opportunities based on the date the deal status changes to 'Closed. Opportunity Won' Sales Count Trends Page
Deals Closed YTD Amount of total number of closed opportunities, where the deal status changes to 'Closed. Opportunity Won' during the current fiscal year Sales Currency Performance Tab
Deals Submitted Count Total number of deals that are not in draft status based on deal creation date Sales Count Trends Page
Deals Submitted YTD Count Total number of deals that are not in draft status based on deal created during the current fiscal year Sales Count Performance Tab
Functional Expertise Partner expertise with regards to vendor product or service offering General Multi-Select Profile Tab
Funds Paid Total settlement amount paid for fund requests based on the settlement date Marketing Currency Trends Page
Funds Paid YTD Total settlement amount paid for fund requests based on settlement date during the current fiscal year Marketing Currency Performance Tab, Key Metrics Bin
Funds Requested Total amount requested for fund requests based on the submitted date Marketing Currency Trends Page
Funds Requested YTD Total amount requested for fund requests based on the submitted date during the current fiscal year Marketing Currency Profile Tab, Key Metrics Bin
Geographic Coverage Partner's Geographic Coverage (Implementation specific) General Multi-Select Profile Tab
Inactive Partners Total number of active partners that have not placed an order (where partner is the 'sold-to') in the time span specified by the profile ' PV: Inactive Partners Time Window' General Count Key Metrics Bin
Indirect Sales Total amount based on the transaction date. This information is captured by Oracle Trade Management from the Point-of-Sale system Sales Currency Trends Page
Indirect Sales Prior year Total amount based on transaction date during last fiscal year. This information is captured by Oracle Trade Management from the Point-of-Sale system Sales Currency Performance Tab
Indirect Sales YTD Total amount based on transaction date during the current fiscal year. This information is captured by Oracle Trade Management from the Point-of-Sale System Sales Currency Performance Tab, Key Metrics Bin
Industry Partner's Industry (Implementation specific) General Multi-Select Profile Tab
Last Order Date Date of the last order where partner is the 'Sold to' party base on last ordered date Sales Date Profile Tab
New Partners Total number of partners created in the time span specified by the profile ' PV: New Partners Time Window' General Count Key Metrics Bin
Open Claims Total amount remaining for all open claims generated from referral, soft funds and special pricing Marketing Currency Performance Tab, Trends Page, Key Metrics Bin
Open Opportunities Total amount of open indirect opportunities that a partner is working on Sales Currency Performance Tab, Trends Page, Key Metrics Bin
Open Opportunities Count Total number of open indirect opportunities that a partner is working on Sales Count Performance Tab, Trends Page, Key Metrics Bin
Opportunities Won Total amount of indirect opportunities that a partner has won based on decision date Sales Currency Trends Page
Opportunities Won Prior year Total amount of indirect opportunities that a partner has won based on decision date during the last fiscal year Sales Currency Performance Tab
Opportunities Won YTD Total amount of indirect opportunities that a partner has won based on decision date during the current fiscal year Sales Currency Performance Tab
Opportunity Acceptance Rate Number of opportunities accepted by partner divided by the number of opportunities offered to partner Sales Percentage Performance Tab, Key Metrics Bin
Opportunity Close Rate Number of opportunities won by the partner divided by the number of opportunities accepted by the partner Sales Percentage Performance Tab, Key Metrics Bin
Partner Enrollment Date Partner enrollment date General Date Profile Tab
Partner Level Partner level (Implementation specific) General Single-Select Profile Tab
Partner Member Type Partner member type (Standard, Global, Subsidiary) General Single-Select Profile Tab
Partner Name Partner Name General String Profile Tab
Partner Type Partner type (End user, Original Equipment Manufacturer, Prospect, Distributor, Reseller). Users can define additional types General Single-Select Profile Tab
Partnership Activity Partnership Activity (Implementation specific) General Multi-Select Profile Tab
Product Categories Available in Special Pricing Product categories that a partner is authorized to submit special pricing requests for (Implementation specific) General Multi-Select Profile Tab
Products Bought Last Year List of products bought by the partner in the last twelve months. (from the current date) This is captured by taking union of products on all orders shipped last year where Partner is the 'Bill to' party Sales Multi-Select Profile Tab
Products Sold Last Year List of all products sold by the partner in the last twelve months. (from the current date) This metric is calculated by taking union on products on all line items maintained in the POS table against the given partner Sales Multi-Select Profile Tab
Referral Commission Paid Total commission amount paid based on the date the referral status changes to 'Closed. Fee Paid' Marketing Currency Trends Page
Referral Commissions Paid YTD Total commission amount paid based on the date the referral status changes to 'Closed. Fee Paid' during the current fiscal year Marketing Currency Performance Tab, Key Metrics Bin
Referrals Accepted Total referral amount accepted based on referral creation date Marketing Currency Trends Page
Referrals Submitted Count Total number of referrals that are not in draft status based on referral creation date Marketing Count Trends Page
Referrals Accepted YTD Total referral amount accepted based on referral creation date during the current fiscal year Marketing Currency Performance Tab, Key Metrics Bin
Referrals Accepted YTD count Total number of referrals accepted based on referral creation date during the current fiscal year Marketing Count Performance Tab, Key Metrics Bin
Referrals submitted YTD count Total number of referrals that are not in draft status based on referral creation date during the current fiscal year Marketing Count Performance Tab
Sales Total amount of all orders shipped where a partner is the sold-to party, based on the order date Sales Currency Trends Page
Sales Prior Year Total amount of all orders shipped where a partner is the sold-to party, based on order date during the prior fiscal year Sales Currency Performance Tab
Sales YTD Total amount of all orders shipped where a partner is the sold-to party based on order date during the current fiscal year Sales Currency Performance Tab, Key Metrics Bin
State States in which the partner has a presence General Multi-Select Profile Tab
Total Partners Total number of partners managed General Count Key Metrics Bin

The Attributes Overview Page

A vendor user with the Channel Administrator responsibility can access the Attributes Overview page. The Attributes Overview page displays all the attributes that can be associated with a partner.

The following table describes the information that appears on the Attributes - Overview page.

Attribute Information
Column Description
Profile Attribute Name The name of the attribute. Seeded attribute names can not be modified.
Attribute Type Indicates how the attribute's data is populated. Three attribute types are available: list of values, text box, and derived.

  • List of values. A value is selected from a range of values that the vendor sets up. Refer to Setting up an Internal List of Values for more information on lists of values and attributes.

  • Text box. Data is entered by a user.

  • Derived. Data is populated by an SQL query or database function.
Display Style For attributes with a type of text box, derived, or list of values, the display status indicates the information type of the attribute.
For attributes with a type of list of values, the display style is flexible, and can be set up according to a vendor's business requirements. Refer to Setting up Attribute Display Styles for additional information.
Category The functional category of the attribute. Refer to Setting up Attribute Categoriesfor additional information.
Attribute Values The View Values link appears in this column if the attribute has an internal List of Values associated with it. Click View Values to access the Attribute Details page, from which you can set up or modify an attribute's list of values.
Refresh Frequency The frequency with which the attribute is updated by the appropriate concurrent program. Refer to Setting up Refresh Frequency for additional information.
Other Attribute Information Enables you to assign one or more roles to an attribute
Active The attribute is enabled and is displayed in the respective profile pages.
Update Select this icon to navigate to the attribute edit page.
Remove Select to remove an attribute. You can remove only attributes for which no data has been collected. Additionally, seeded attributes cannot be removed; this icon is grayed out for them.

Lists of Values for Seeded Attributes

Many attributes are associated with a list of values. For many of the seeded attributes, and for some derived custom attributes, the list of values is populated from a Lookup or an external table. The list of values for other attributes can be set up by a channel administrator. If a list of values can be set up internally, a View Values link appears in the attribute's Attribute Values column. Refer to Setting up an Internal List of Values for more information.

The following table lists the seeded attributes that are associated with a list of values, and indicates the list of values source and additional information. The source can be the name of a Lookup, a SQL statement, or Internal if the list of values is created from within Oracle Partner Management.

Sources for Lists of Values for Seeded Attributes
Attribute Display Style List of Values Source Enabled For
Functional Expertise Multi-Select ENI_PROD_DEN_HRCHY_PARENTS_V WHERE PURCHASE_INTEREST = 'Y' AND (DISABLE_DATE IS NULL OR DISABLE_DATE > SYSDATE) Partner
Product Categories for Special Pricing Multi-Select ENI_PROD_DEN_HRCHY_PARENTS_V WHERE PURCHASE_INTEREST = 'Y' AND (DISABLE_DATE IS NULL OR DISABLE_DATE > SYSDATE) Partner
Partner Type Check Box INTERNAL Partner
Country Multi-Select FND_TERRITORIES_VL Partner, Opportunity
Industry Multi-Select LOOKUP (PRM_IND_CLASSIFICATION_TYPE) Partner, Opportunity
Partner Member Type Radio Button INTERNAL Partner
Geographic Coverage Multi-Select INTERNAL Partner, Opportunity
Additional Channel Offering Multi-Select INTERNAL Partner, Opportunity
Partnership Activity Multi-Select INTERNAL Partner, Opportunity
Campaign External List of Values AMS_P_SOURCE_CODES_V WHERE SC.STATUS IN ('ACTIVE', 'ONHOLD','COMPLETED') AND SC.SOURCE_TYPE IN ('EVEH','EVEO','CAMP','CSCH') Opportunity
Capacity Rating Drop Down INTERNAL Partner, Opportunity
Partner Level Drop Down INTERNAL Partner, Opportunity
State Multi-Select AR_LOCATION_VALUES WHERE LOCATION_SEGMENT_QUALIFIER = 'STATE' Partner, Opportunity
Customer External List of Values ASF_CUSTOMER_LOV_V WHERE PARTY_TYPE IN ('ORGANIZATION', 'PERSON') Opportunity
Opportunity Status Drop Down AS_STATUSES_VL WHERE ENABLED_FLAG = 'Y' AND OPP_FLAG = 'Y Opportunity
Product Category Multi-Select ENI_PROD_DEN_HRCHY_PARENTS_V WHERE PURCHASE_INTEREST = 'Y' AND (DISABLE_DATE IS NULL OR DISABLE_DATE > SYSDATE) Opportunity
Sales Channel Drop Down ASO_I_SALES_CHANNELS_V WHERE ENABLED_FLAG = 'Y' Opportunity
Sales Stage Drop Down AS_SALES_STAGES_ALL_VL WHERE ENABLED_FLAG = 'Y' AND SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE) Opportunity
Offer External List of Values AMS_P_SOURCE_CODES_V Opportunity
Win Probability Drop Down AS_FORECAST_PROB_ALL_VL WHERE ENABLED_FLAG = 'Y'AND ((SYSDATE BETWEEN START_DATE_ACTIVE AND END_DATE_ACTIVE) OR(SYSDATE > START_DATE_ACTIVE AND END_DATE_ACTIVE IS NULL)) Opportunity
Sales Methodology Drop Down AS_SALES_METHODOLOGY_VL WHERE SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE) Opportunity
Customer/Account Type Drop Down LOOKUPS (CUSTOMER_ACCOUNT_TYPE) Opportunity
Routing Status Drop Down LOOKUPS (PV_ROUTING_STAGE) Opportunity
Customer Category Drop Down AR_LOOKUPS WHERE LOOKUP_TYPE = 'CUSTOMER_CATEGORY' AND ENABLED_FLAG = 'Y' Opportunity
Products Bought Last Year Multi-Select MTL_SYSTEM_ITEMS_B WHERE ORGANIZATION_ID = FND_PROFILE.VALUE('ORG_ID') Partner
Products Sold Last Year Multi-Select MTL_SYSTEM_ITEMS_B WHERE ORGANIZATION_ID = FND_PROFILE.VALUE('ORG_ID') Partner

Working with Attributes

A channel administrator may need to perform the following tasks, either during implementation or as ongoing administrative tasks:

Setting up Attribute Categories

Attributes can be organized into different functional categories: General, Marketing, PRM, Resource, or Sales. The categories are used to group attributes on the Profile and Performance tabs on the Partner Details page.

A vendor user can set up additional categories either during or after implementation. Additional attribute categories are added through Oracle Forms, by adding new lookup values to the lookup type Attribute Categories (PV_ATTRIBUTE_CATEGORY_TYPE).

Setting up Attribute Display Styles

An attribute's Display Style indicates the type of control that will be used to provide information about the attribute. An attribute's Display Style is determined by its Attribute Type. Most of the seeded attributes with an Attribute Type of List of Values have flexible Display Styles, which can be set up by the channel administrator according to business requirements.

Depending on the drop-down list associated with the attribute, the channel manager can select one of two Display Style controls:

When a channel administrator creates a custom attribute, she indicates both the attribute type and display style. For more information, see Setting up Custom Attributes.

Setting up an Internal List of Values

When the View Values link is available for an attribute, a channel administrator can set up an internal list of values for the attribute. Click the View Values link to access the Attributes - Overview page and set up an attribute's internal list of values.

Notes

Setting Up Attribute Security

Partner attributes enable the channel manager to search for partners and track partner performance. These can be seeded or custom attributes that the channel administrator creates. To ensure the confidentiality and security of partner attributes, set the PV: Enable Profile Attribute Security profile option to Yes at the site level. To control whether vendor or partner users can view or update partner attributes, assign the appropriate permissions to user roles and roles to attributes. If you set the profile option to No, all roles can view and update attributes irrespective of the permissions assigned to the roles.

The permissions that you can assign to roles are PV_PARTNER_UPDATE_PROFILE_ATTRIBUTE and PV_PARTNER_VIEW_PROFILE_ATTRIBUTE. User roles can be existing or newly created. These roles include channel managers, channel representatives, and primary and secondary partner users.

You assign roles to attributes in the Attribute Details page. If you select to assign ALL ROLES to a partner attribute, both vendor and partner users can view and update the attribute based on the permission assigned to their role. Otherwise only the role assigned to the attribute can view or update the attribute based on the permission assigned to the role.

Setting Up Refresh Frequency

Attributes that track partner performance and trends need to be refreshed periodically. You set up an attribute's refresh frequency from the Attribute Details - Properties page, which is accessed by clicking the Refresh Frequency link for an attribute. The refresh frequency is subsequently used by concurrent programs to update an attribute's information.

How frequently a specific attribute should be refreshed depends on business requirements. You can specify that an attribute be refreshed hourly, daily, weekly, or monthly:

When setting up a refresh frequency, you should also take into consideration whether or not an attribute's value is derived from, and thus dependent upon, another attribute. For information on attribute refresh dependencies, refer to Understanding Performance Attribute Refresh Dependencies.

Attributes for which you have not assigned a refresh frequency are refreshed whenever the concurrent programs run.

Understanding Performance Attribute Refresh Dependencies

Many of the partner performance and partner group performance attributes derive their values from other attributes. Specifically, many of the partner performance attribute values are derived from partner trend measures, while many of the partner group performance attribute values are derived from partner performance attributes.

When an attribute is dependent upon another attribute for its value, the other attribute must be refreshed before the dependent attribute can be updated successfully. You must understand attribute dependencies to properly set up refresh values. The following table maps the dependencies between the three types of performance attributes.

Performance Attribute Refresh Dependencies
Partner Group Measure Depends on Partner Measure Depends on Partner Trend Measure
Open Opportunities Count Open Opportunities Count Open Opportunities Count
Open Opportunities Open Opportunities Open Opportunities
Sales YTD Sales YTD Sales
Indirect Sales YTD Indirect Sales YTD Indirect Sales
Opportunity Close Rate Opportunity Close Rate --
Opportunity Acceptance Rate Opportunity Acceptance Rate --
Referral Commissions Paid YTD Referral Commissions Paid YTD Referral Commission Paid
Referrals Accepted YTD Referrals Accepted YTD Referrals Accepted
Referrals Accepted YTD Count Referrals Accepted YTD Count --
Deals Accepted YTD Count Deals Accepted YTD Count Deals Accepted Count
Deals Accepted YTD Deals Accepted YTD Deals Accepted
Funds Requested YTD Funds Requested YTD Funds Requested
Funds Paid YTD Funds Paid YTD Funds Paid
Open Claims Open Claims Open Claims
-- Sales Prior Year Sales
-- Indirect Sales Prior Year Indirect Sales
-- Opportunities Won YTD Opportunities Won
-- Opportunities Won Prior Year Opportunities Won
-- Referrals Submitted YTD Count Referrals Submitted Count
-- Deals Close Rate Deals Closed Count divided by Deals Accepted Count
-- Deals Closed YTD Deals Closed
-- Deals Submitted YTD Count Deals Submitted Count
-- Claims Paid YTD Claims Paid
Total Partners -- --
New Partners -- --
Inactive Partners -- --

Refreshing Attribute Values with Concurrent Programs

The refresh frequency value is used by one of two concurrent programs to determine whether or not an attribute needs to be updated.

The following table provides the parameters of the PV: Refresh Partner Trend Values concurrent program.

PV: Refresh Partner Trend Values Parameters
Parameter Description
Start from Beginning of Month Identifies the starting month to refresh (only applies to measures that are cumulative). Non-cumulative measures are always calculated for the current month only.
To Ending of Month Identifies the ending month to refresh (only applies to measures that are cumulative). Non-cumulative measures are always calculated for the current month only.
New Partners Only If Yes, then only process for new partners. New partners are defined as partners created after the last refresh run of this concurrent program (stored in the profile 'PV: Partner Trend Last Refresh').
Ignore Refresh Interval If Yes, process all attributes even though the time interval from the last refresh has not exceeded the refresh interval set for some attributes.

For currency measures, the PV: Refresh Partner Trend Values concurrent program converts all currency to the currency stored in the profile PV: Common Currency for Rules Engines. If this profile is not set, it defaults to USD.

The following table provides the parameters of the PV: Refresh Attribute Text Table concurrent program.

PV: Refresh Attribute Text Table Parameters
Parameter Description
New Partners Only Only process for new partners. New partners are defined as partners created after the last refresh run of this concurrent program (stored in the profile PV: Refresh Search Attributes Last Update Date).

For currency measures, this concurrent program converts all currency to the currency stored in the profile PV: Common Currency for Rules Engines. The default value is USD.

Reordering Attributes

Reordering of attributes can be done only from the Channel Administrator responsibility. The Attribute overview page is the starting point for the attributes reordering process. Reordering is done at a category level; therefore, a Channel Administrator must select a specific category prior to initiating the reordering process.

Migrating Partner Type Values

In previous releases, you could assign multiple partner types to a single partner. In the R12 release, a partner can be assigned one partner type only. If you are upgrading from an earlier Oracle Partner Management release you need to perform some administrative functions to successfully migrate your partner type data:

Populate the PV_PARTNER_TYPE_RANKING lookup table with a numerical ranking for each existing partner type. The table is seeded with some partner types and ranking data; and vendors can add to and modify the seeded values. The PV: Partner Type Migration concurrent request uses this lookup table to assign a single type to each partner by evaluating all of the partner’s existing types and selecting the top-ranked type (the type with the lowest value).

For example, if a partner is currently assigned both Reseller and OEM partner types, and the value assigned to Reseller is lower than that assigned to OEM, then the partner’s new type will be Reseller. Vendors must provide a ranking for each partner type except for the VAD type. The VAD is always considered the top-ranked partner type, regardless of the ranking specified by the vendor. See Partner Profile Attribute lookups for more information.

After establishing the partner type rankings, run the PV: Partner Type Migration concurrent program to assign the new rankings to existing partners. The program can be run in Evaluation or Execution mode. See Concurrent Programs for Partner Profile Attributes for more information. The concurrent program generates a log file that provides information about the migration, including the original partner types and the new partner type for each partner.

Setting Up Custom Attributes

A channel administrator can create custom attributes to track additional information about partners. Customized attributes can be used to gather information about a partner or to derive information from other sources through SQL statements and database functions.

Navigation

Log on with the channel administrator responsibility, navigate to the Attributes Overview page, and click the Create button that appears on the Attributes - Overview page to access the Create Attribute page.

Notes

The following table lists all the attribute types and display styles available for custom attributes. The table also provides additional information for those attributes and display styles that require additional information during set up.

Attribute Types and Display Styles
Attribute Type Display Style Additional Information for Attribute
List of Values Check Box No
Multi Select Enter the number of lines to be included in the list.
Percentage By default, the percentage values must add up to 100%. To change the percentage total, modify the profile value PV: Attribute Percentage Total.
Radio Button No
Drop Down No
Text Box Currency Decimal points: Number of decimal points used for rounding.
Character Width: number of characters allowed in the text box.
Value Type: Used to evaluate attribute during opportunity matching. Specify Minimum or Maximum.
Date Value Type: Used to evaluate attribute during opportunity matching. Specify Minimum or Maximum.
Numeric Decimal points: Number of decimal points used to round amounts.
Value Type: Used to evaluate attribute during opportunity matching. Specify Minimum or Maximum.
Text Number of lines: The number of lines to be allowed in the text box.
Character Width: The number of characters allowed in the text box.
Derived Currency No
Date No
Numeric Value Type: Used to evaluate attribute during opportunity matching. Specify Minimum or Maximum.
Text No
List of Values No
Percentage Value Type: Used to evaluate attribute during opportunity matching. Specify Minimum or Maximum.

Creating a Derived Attribute

Creating a derived attribute involves providing code that is used to populate attribute values. A derived partner profile attribute can be populated by a PL/SQL stored procedure or package, or by a SQL statement. A user-defined SQL statement is used to populate the list of values that is associated with an attribute with List Of Values value type.

Coding for derived attributes is done in the Derived Attribute Properties section of the Attribute Detail page. This section appears when you click Create after providing the attribute's initial details.

Notes

Example: Populating a Derived Attribute with a Stored Procedure

Derived attributes support all the return types that are currently supported by Oracle Applications: currency, date, null_check, number, and string.

Currently, the following procedure template is supported. The procedure expects an IN parameter of NUMBER type and an OUT parameter of JTF_VARCHAR2_TABLE_4000 type:

PROCEDURE <procedure-name>
(
        p_partner_id NUMBER,
        x_output OUT JTF_VARCHAR2_TABLE_4000
)
IS
<declarations>
BEGIN
        x_output := JTF_VARCHAR2_TABLE_4000();
        <logic to derive the output values and store them in x_output table>
END;

The following is an example of a procedure that would be used to create an attribute that calculates a partner's actual revenue:

PROCEDURE Partner_Revenue(   p_partner_id NUMBER,
        x_assigned_count OUT JTF_VARCHAR2_TABLE_4000    )
IS
                        CURSOR lc_count IS
                                        SELECT orgp.curr_fy_potential_revenue  annual_revenue
                                        FROM apps.pv_partner_profiles PV, apps.hz_organization_profiles orgp
                                        WHERE orgp.curr_fy_potential_revenue IS NOT NULL
                                                        AND orgp.party_id = pv.partner_party_id
                                                        AND pv.partner_id = p_partner_id ;
                        indx NUMBER := 1;
BEGIN
                        x_assigned_count := JTF_VARCHAR2_TABLE_4000();
                        FOR lc_cursor IN lc_count LOOP
                                        x_assigned_count.EXTEND;
                                        x_assigned_count(indx) := lc_cursor.annual_revenue;
                                        indx := indx + 1;
END LOOP;
End;

Example: Populating a Derived Attribute with a SQL Statement

The application provides a the following sample SQL statement that can be modified to create a custom SQL statement for a list of values:

select pac.attr_code code, 
pac.description meaning,
pac.description description from
        pv_attribute_codes_v1 pac where
pac.attribute_id = ? and
pac.enabled_flag = 'Y'

In the SQL statement, attribute_id can refer to a table column or an actual attribute id.

For a derived attribute with a List Of Values value type, a list of values is provided through a user-defined SQL statement. The following example provides a SQL statement for a derived list of values attribute where:

select lkp.lookup_code code,
lkp.meaning meaning,
lkp.description description
from fnd_lookups lkp
where lkp.lookup_type = 'FND_EXAMPLE_LOOKUP'.
and xxxx= ?