11g Release 1 (11.1.3)
Part Number E20387-03
Contents
Previous
Next
|
Oracle® Fusion
Applications
Product Information Management Implementation Guide 11g Release 1 (11.1.3) Part Number E20387-03 |
Contents |
Previous |
Next |
This chapter contains the following:
Oracle Fusion Profile Management Components: How They Work Together
Define Talent Profile Settings
Profile management provides a framework for developing and managing talent profiles that meet your industry or organizational requirements. Profiles summarize the qualifications and skills of a person or a workforce structure such as a job or position. Profiles are valuable for tracking workers' skills, competencies, and accomplishments, and for various talent management activities, such as career planning, identifying training needs, performance management, and in the recruitment process for identifying job requirements and suitable applicants.
This topic discusses:
Profile search
Profile comparison
Best-fit analysis
You can search profiles for workers, jobs, and positions with certain criteria. For example, an HR (Human Resources) specialist in London who is looking to fill an applications developer position from within the company can search for profiles of all workers who are based in London and have experience with Java and PL/SQL.
Using the comparison feature, you can compare profiles to determine next career moves or training needs for workers, and identify suitable candidates for jobs. For example, if John is looking for his next career move, he can compare his profile to that of a job to determine whether his competency ratings match the targeted competency ratings in a job profile. For example, if his Teamwork rating is 3 and the Product Strategy Teamwork requirement is 4, he has a deficiency of -1. John and his manager can use this gap to drive development plans and for other talent management-related functions.
Use the best-fit analysis to determine the person profile that most closely matches a job profile, or the job profile that is the best match for a person profile. For example, if you are trying to fill a Developer vacancy, and the job profile requires a B.S. degree in Computer Science, level 4 expertise coding Java, and a Teamwork rating of at least 3, you can review an automatically-generated list of workers who most closely match this set of requirements. You can also use the best-fit analysis to find workers who are similar to a selected worker, or jobs that are similar to a selected job.
You can configure Oracle Fusion Profile Management to meet your business requirements using these components: the content library, profiles and profile types, content subscribers, educational establishments, instance qualifier sets, and rating models.
This figure illustrates how the components of Profile Management fit together.
The content library provides the foundation for profiles as it stores both content types and content items.
Profile types are templates that you use to create profiles. Profile types determine whether the profile is for a person or for a workforce structure such as a job or a position, and the content of the profile. You select content types from the content library to create content sections for the profile type.
You create person profiles for individual workers and model profiles for workforce structures, such as a jobs or positions. The information that you complete for the profile is determined by how the profile type has been set up. For example, a person profile might contain information about a person's education, language skills, competencies, and activities and interests. A job profile might contain information about the requirements for the job, such as competencies, language skills, degrees, or certifications.
Content subscribers are applications external to Oracle Fusion Profile Management that use content types.
You can define educational establishments for workers to use when they add education information, such as degrees, to their profile.
You assign instance qualifiers to content types. Instance qualifier sets uniquely identify multiple instances of a content item on a profile. For example, if multiple people update a performance rating for a competency on a worker's profile, instance qualifiers provide a unique identifier to each instance of the competency so that you can determine who provided each rating.
When you create content types in the content library, you can attach rating models to determine the scale for measuring performance and proficiency. You can also use rating models to measure the risk and impact of loss for workers, and to measure their potential.
Oracle Fusion Profile Management supports talent management business processes in these products:
Oracle Fusion Performance Management
Oracle Fusion Goal Management
Oracle Fusion Talent Review
Oracle Fusion Performance Management uses the rating models that you define in Profile Management to rate workers on their performance. When you define a performance document template, you can specify whether the ratings and comments from managers and workers are uploaded automatically to workers' profiles when the performance document is finalized. Instance qualifier sets distinguish the manager ratings from the workers' self ratings. Performance Management also uses competencies from the content library in performance documents.
You can set up a content type relationship between the Goals content type and other content types, such as the Competencies content type and the Memberships content type. Using these relationships, you can then set up target outcomes for goals. Target outcomes are the content items within the content type that is related to the Goals content type. For example, if you set up a relationship between the Goals content type and the Competencies content type, workers can add a target outcome of a specific competency to their goals. In this case, the specific competency is the content item within the Competencies content type. When workers complete the goal, their profiles are updated to include the competency.
Oracle Fusion Talent Review uses information from the Performance and Potential and Risk of Loss sections within a worker's profile to build the analytics that are part of the talent review process. These sections are defined as content types within the content library and included in the person profile type. When a talent review is complete, workers' profiles are updated automatically with the performance rating given during calibration discussions. Instance qualifier sets enable you to distinguish the talent review rating from ratings given by the worker's manager, a peer, or perhaps the worker's self-evaluation.
This topic identifies common lookups that are profile management-related and have user or extensible customization levels. Review these lookups, and update them as appropriate to suit enterprise requirements.
Profile management lookups are described in the following table.
|
Lookup Type |
Description |
Customization Level |
|---|---|---|
|
HRT_CONTENT_SUPP_CODE |
Codes to identify where the content type originated, such as from the customer or from a third party. HR specialists assign supplier codes when setting up new content types. |
Extensible |
|
HRT_COMPETENCY_EVAL_TYPE |
Types of competency ratings, such as self, supervisor, and peer. Evaluation types are used in instance qualifier sets to identify the role of the person who provided a competency rating for a worker. |
User |
|
HRT_DEGREE_LEVEL |
Required levels of education for a job or position profile, such as a Bachelor's Degree or Masters degree. |
User |
|
HRT_DURATION |
Time periods for when a worker would like to make a career move. Workers select a duration for their career move in the career preferences information on the career planning card. |
User |
|
HRT_EDUCATION_LEVEL |
Types of education that a degree provides, such as a Bachelor's degree or one year college. HR specialists use education levels when creating content items in the Degrees content type. |
User |
|
HRT_IMPORTANCE |
Values for the importance level of each content type. Importance values are used in the best-fit analysis calculation. |
User |
|
HRT_PAY_FREQUENCY |
Frequencies at which a worker is paid. Workers specify a preferred pay frequency when they edit their work requirements on the experience and qualifications card. |
User |
|
HRT_READINESS |
Time periods in which a worker will be ready for advancement to a specified job or position profile. Managers and human resource (HR) specialists use readiness levels when editing the talent ratings information on workers' career planning cards. |
User |
|
HRT_RISK_REASON |
Reasons for why a worker is at risk for leaving the company. Managers and HR specialists use risk reasons when editing the talent ratings information on workers' career planning cards. |
User |
|
HRT_SATISFACTION_METHOD |
Methods by which an item such as a competency is verified, such as assessment or demonstration. Managers and HR specialists use these values to identify the method that was used to evaluate the proficiency of a worker in a particular skill or quality. |
User |
|
HRT_TRAVEL_FREQUENCY |
Percentages of time a worker is expected to travel for a job or position, for example, 25 percent or 50 percent. Managers and HR specialists specify the required travel frequency on job and position profiles. Workers also specify a travel frequency when they edit their work requirements on the experience and qualifications car |
User |
|
HRT_VALIDITY_PERIOD |
Periods of time for which content items such as licenses and certifications are valid. Managers and human resource (HR) specialists select validity periods when setting up content items for the Licenses and Certifications content type. |
User |
|
HRT_WORK_DAYS |
Work days for a job or position, such as Monday through Friday. Managers and HR specialists specify the expected work days on job and position profiles. |
User |
|
HRT_WORK_HOURS |
Work hours for a job or position, such as 9:00 a.m. to 5:00 p.m. Managers and HR specialists specify the expected work hours on job and position profiles. |
User |
A value set is a set of valid values that you assign to a flexfield segment.
An end user enters a value into a flexfield segment while using the application. The flexfield validates the segment against the set of valid values that you configured as a value set and assigned to the segment.
For example, you can define a required format, such as a five digit number, or a list of valid values, such as green, red, and blue.
Flexfield segments are usually validated, and typically each segment in a given flexfield uses a different value set. You can assign a single value set to more than one segment, and you can share value sets among different flexfields.
Caution
Be sure changes to a shared value set are compatible with all flexfields segments using the value set.
Defining value sets involves making decisions about the following.
Validation
Security
Precision and scale
Usage and deployment
The following types of validation are available for value sets.
Format only, where end users enter data rather than selecting values from a list
Independent, a list of values consisting of valid values you specify
Dependent, a list of values where a valid value derives from the independent value of another segment
Subset, where the list of values is a subset of the values in an existing independent value set
Table, where the values derive from a column in an application table and the list of values is limited by a WHERE clause
A segment that uses a format only value set does not present a list of valid values to users.
You can build a tree structure from the values in an independent value set whose data type is character.
Note
Adding table validated value sets to the list of available value sets available for configuration is considered a custom task.
For more information, see the Oracle Fusion Applications Extensibility Guide.
Value set security only works in conjunction with usage within flexfield segments. If a value set is used standalone, meaning outside a flexfield, value set security is not applied, but Oracle Fusion data security is enforced.
You can specify that data security be applied to the values in flexfield segments that use a value set. Based on the roles provisioned to users, data security policies determine which values of the flexfield segment end users can view or modify.
Value set security applies at the value set level. If a value set is secured, every usage of it in any flexfield is secured. It is not possible to disable security for individual usages of the same value set.
Value set security applies to independent, dependent or table-validated value sets.
Value set security applies mainly when data is being created or updated, and to key flexfield combinations tables for query purposes. Value set security does not determine which descriptive flexfield data is shown upon querying.
Security conditions defined on value sets will always use table aliases. When filters are used, table aliases are always used by default. When predicates are defined for data security conditions, make sure that the predicates will also use table aliases.
For key flexfields, the attributes in the view object that correspond to the code combination ID (CCID), structure instance number (SIN) and data set number (DSN) cannot be transient. They must exist in the database table. For key flexfields, the SIN segment is the discriminator attribute, and the CCID segment is the common attribute.
For a value set with the data type Number, you can specify the precision (maximum number of digits user can enter) or scale (maximum number of digits following the decimal point).
The usage of a value set is the flexfields where that value set is used. The deployment status of flexfields in which the value set is used indicates the deployment status of the value set instance.
The figure shows a value set used by a segment in a key flexfield and the context segment of a descriptive flexfield.
For most value sets, when you enter values into a flexfield segment, you can enter only values that already exist in the value set assigned to that segment.
Global and context-sensitive segment require a value set. You can assign a value set to a descriptive flexfield context segment. If you specify only context values, not value sets for contexts, the set of valid values is equal to the set of context values.
Validation and usage of value sets determine where and how end users access valid values for attributes represented by flexfield segments.
Tip
As a flexfield guideline, define value sets before configuring the flexfield, because you assign value sets to each segment as you configure a flexfield.
When assigning a value set to a context segment, you can only use table-validated or independent value sets. The data type must be character and the maximum length of the values being stored must not be larger than column length of the context.
The format only validation type enables end users to enter any value, as long as it meets your specified formatting rules. That is, the value must not exceed the maximum length you define for your value set, and it must meet any format requirements for that value set.
For example, if the value set allows only numeric characters, your user could enter the value 456 (for a value set with maximum length of three or more), but could not enter the value ABC. A format only value set does not otherwise restrict the range of different values that users can enter. For numeric values, you can also specify if a numeric value should be zero filled or how may digits should follow the radix separator
You cannot specify a dependent value set for a given segment without having first defined an independent value set that you apply to another segment in the same flexfield. You use a dependent value set to limit the list of values for a given segment based on the value that the end user has chosen for a related independent segment. The available values in a dependent list and the meaning of a given value depend on which value was selected for the independently validated segment.
For example, you could define an independent value set of U.S. states with values such as CA, NY, and so on. Then you define a dependent value set of U.S. cities, with values such as San Francisco and Los Angeles that are valid for the independent value CA, and New York City and Albany that are valid for the independent value NY. In the UI, only the valid cities can be selected for a given state.
Because you define a subset value set from an existing independent value set, you must define the independent value set first. End users do not need to choose a value for another segment first to have access to the subset value set.
Typically, you use a table-validated set when the values you want to use are already maintained in an application table (for example, a table of vendor names). Table validation allows you to enable a segment to depend upon multiple prior segments in the same context or structure.
Table-validated value sets have unique values across the table, irrespective of bind variables. The WHERE clause fragment of the value set is considered if it does not have bind variables. If it has bind variables, the assumption is that the values are unique in the value set.
In the case of format, independent, or dependent value sets, you can specify a range to further limit which values are valid. You can specify a range of values that are valid within a value set. You can also specify a range validated pair of segments where one segment represents the low end of the range and another segment represents the high end of the range
For example, you might specify a range for a format-only value set with format type Number where the user can enter only values between 0 and 100. If you use a table value set, you cannot reference flexfield segments in the WHERE clause of the value set . For example, the WHERE clause cannot reference a segment or a value set.
In the case of independent and dependent values, you can specify that data security be applied to the values in segments that use a value set. Based on the roles provisioned to users, data security policies determine which values of the flexfield segment end users can view or modify.
When you enable security on a table-validated value sets, the security rule that is defined is absolute and not contingent upon the bind variables (if any) that may be used by the WHERE clause of the value set. For example, suppose a table-validated value set has a bind variable to further filter the value list to x, y and z from a list of x, y, z, xx, yy, zz. The data security rule or filter written against the value set should not assume anything about the bind variables; it must assume the whole list of values is available and write the rule, for example, to allow x, or to allow y and z. By default in data security all values are denied, and show only rows to which access has been provided.
There is no need to define or maintain values for a table-validated or subset value set, as the values are managed as part of the referenced table or independent value set, respectively.
If your application has more than one language installed, or there is any possibility that you might install one or more additional languages for your application in the future, select Translatable. This does not require you to provide translated values now, but you cannot change this option if you decide to provide them later.
For more information about defining value sets, see the Oracle Fusion Applications Extensibility Guide.
Use rating models to rate workers on their performance and level of proficiency in the skills and qualities that are set up on the person profile. You can also use rating models to specify target proficiency levels for items on a model profile, so that the model profile can be compared to workers' profiles.
To rate workers on their performance and proficiency, you attach rating models to the content types that are included in the person profile, and then workers can be rated on the items within the type. For example, you can rate workers on the Communication content item within the Competencies content type.
For model profiles, you can specify target proficiency levels for items on the profile, so that the model profile can be compared to workers' profiles. Using the ratings, managers can compare a model profile to workers' profiles to determine the best person suited to fill a position. Workers can compare their profile to model profiles to identify other positions within the organization that they are suited for, or to identify gaps in skills that they need to fill before applying for other positions.
Rating models that measure workers' potential and the impact and risk of loss are also available.
Rating models can include some or all of the following components, depending on the use for the model:
Rating levels
Review points
Rating categories
Distributions
Rating levels identify the qualitative values, such as 1, 2, 3, or 4, that you use to rate or score a worker's performance. Define numeric ratings for rating models that you use with performance documents that use the average calculation method.
Define review points for rating models that you use with performance documents that use the sum or band calculation method. The review points and point ranges that you define for the rating model are used to calculate ratings.
Rating categories enable you to group rating levels together for analysis tools used in the talent review process, such as the box chart that is used in the talent review process. You can group rating levels into categories such as low, medium, and high, and those categories then become the labels for the analytic. You should not change rating categories after setting them up, as the changes could affect the analytic.
Oracle Fusion Compensation Management and Oracle Fusion Performance Management both use rating model distributions to determine the targeted minimum and maximum percentage of workers that should be given each rating level. Compensation Management uses the distribution values that you set up directly on rating models. However, you can set up distributions at the performance template level for rating models that are used in Performance Management.
Content types are the skills, qualities, and qualifications that you want to track in talent profiles. The content library contains predefined content types such as competencies, languages, and degrees, but you can create new content types as needed. You can also create free-form content types.
Content types contain:
Properties
Relationships
Subscribers
Note
Free-form content types do not contain relationships and do not contain properties until you add them to a profile type.
For each content type, you define the properties that all content items of the content type can or must have. To define properties of the content type, you select fields to be displayed when setting up the content items and the attributes of those fields. The attributes that you specify for each field are: field label, default value, whether the field is required, and whether the field is hidden, display-only, or editable. If the field is attached to a predefined list of values, you also specify the source of the list.
Specify where one content type is a parent of another, or where one content type supports another. Content items of content types with relationships inherit the relationship. You cannot create two kinds of relationships between two types or create a relationship between a type and itself. For example, content type A cannot be both the parent and child of content type B. A content type cannot be related to itself.
Specify the subscriber codes of the applications or other Oracle Fusion products that use each content type. If you do not specify a subscriber code for the content type, you cannot view the content type in other applications. For example, if you add a new content type called Corporate Citizenship to the person profile type, you cannot view the content section for Corporate Citizenship in person profiles until you add the new content type to the HRMS content subscriber code.
Content relationships enable you to associate content items of related content types with each other. The following scenarios illustrate the use of content type relationships.
The Resource Manager component of Oracle Fusion Trading Community Model uses content type relationships to track the areas of expertise of workers. Using the predefined content type relationship where the Categories content type is a parent of Products, and Products is a parent of Components, resource managers can keep track of the categories, products, and components that are considered to be their areas of expertise for their resources.
Note
Because these content types and relationships are applicable only to the Resource Manager component of Oracle Fusion Trading Community Model, this product is the only predefined content subscriber to these content types.
To help your workers manage their goals, you want them to associate their goals with target outcomes, which are content types such as Competencies and Memberships. To accomplish this, you can set up a relationship on the Competencies content type where Competencies is supported by Goals. Workers can then set up goals that have a specific competency as a target outcome.
Content items are the individual skills, qualities, and qualifications within the content types in the content library. For example, within the Competencies content type, communication is a content item. You can create content items to meet your business needs.
This topic discusses:
Item properties
Related content items
Proficiency descriptions
Content items inherit the fields and field properties that you define for the content type to which the item belongs. For example, one of the fields defined for the Memberships content type is ITEM_DESCRIPTION field. The attributes of this field are set up so that the label is Description, the field is editable, and the field does not require an entry. When you set up a content item for the Memberships content type, you will see a field labeled Description, in which you can enter text to describe the agency, but the field will not be required.
If the content type for which you are creating an item has related content types, then you can enter the related content items for the item. For example, if you have a content type relationship where the Competencies content type is supported by the Goals content type, then on the content items for competencies, you can enter the related goals.
If the content item belongs to a content type that has a rating model defined for it, then you can either use the existing descriptions for the ratings within the model, or define descriptions for the ratings that are specific to the content item. When ratings are given for the content item, the descriptions defined for the item are used instead of those on the rating model.
This example demonstrates how to set up a new content type and content items to track the corporate citizenship activities of your workers so that you can rate them on their involvement in the organization. This example also demonstrates how to set up a rating model to be used with the content type and add the new content type to the person profile.
The following table summarizes key decisions for this scenario.
|
Decisions to Consider |
In This Example |
|---|---|
|
Can a predefined rating model be used to rate corporate citizenship? |
No. The predefined rating models do not have relevant rating descriptions. |
|
Should the content type be a free-form content type? |
No. Content items are needed, and the content should be stored in the content library. |
|
What field and properties should the content type contain? |
Add two fields to the content type:
The ITEM_TEXT1 field will have a label of Comments, and will be used to enter comments about the workers' corporate involvement. The RATING_MODEL_ID field will have a label of Company Contribution and will be used to attach the rating model for corporate citizenship to the content type. Both fields should require entry and should be editable. |
|
Does the content type need any content subscribers? |
Yes. In order to be visible on the person profile, the new content type must be added to the HRMS content subscriber code. |
|
What content items are needed to track the required information? |
|
|
When the content type is added to the person profile as a content section, what properties should the fields contain? |
Both the Comments field and the Company Contribution fields should display in the detail view of the content section, they should be required, and they should be included in search results. |
To track corporate citizenship for your workers, complete the following tasks:
Create a rating model.
Create a content type.
Create content items.
Add the content type to the person profile type.
|
Field |
Value |
|---|---|
|
Code |
Citizenship |
|
Rating Name |
Corporate Citizenship |
|
Description |
Rating model for corporate citizenship |
|
Rating Level |
Name |
|---|---|
|
1 |
Demonstrates limited or unused influence. |
|
2 |
Demonstrates clear evidence of influence. |
|
3 |
Provides a successful image of the company as socially responsible in limited environments. |
|
4 |
Actively called upon to use influence as a corporate representative in selected environments. |
|
5 |
Demonstrates high level of influence and is able to operate effectively in all environments. |
|
Field |
Value |
|---|---|
|
Code |
Citizenship |
|
Name |
Corporate Citizenship |
|
Description |
Ratings for corporate citizenship behaviors for workers. |
|
Field Name |
Field Label |
Required |
Display Option |
|---|---|---|---|
|
ITEM_TEXT_1 |
Comments |
Selected |
Editable |
|
RATING_MODEL_ID |
Company Contribution |
Selected |
Editable |
|
Field |
Value |
|---|---|
|
Content Type |
Corporate Citizenship |
|
Content Item |
Corporate Social Responsibility |
|
Column Name |
Display Flag |
Required |
Searchable |
|---|---|---|---|
|
ITEM_DESCRIPTION |
Detail |
Selected |
Selected |
|
RATING_LEVEL_ID1 |
Detail |
Selected |
Selected |
This example demonstrates how to set up a free-form content type, add it to the HRMS content subscriber code, and then add the content type to the person profile type.
Your company wants to track the previous employment information for workers, including employer name, dates of employment, and job description. However, you do not want to set up and maintain content items for each employer, and this information applies only to person profiles. You decide to use a free-form content type for this information. You can set up the free-form content type with minimal information, and then when you add it to the person profile as a content section, you can define properties for employer name, dates of employment, and job description. Workers can complete their employment information on their profile based on how you set up the content section. The following table summarizes key decisions for this scenario.
|
Decisions to Consider |
In This Example |
|---|---|
|
Should the content type be a free-form content type? |
Yes. Content items are not needed, and the content should not be stored in the content library. |
|
Does the content type need any content subscribers? |
Yes. In order to be visible on the person profile, the new content type must be added to the HRMS content subscriber code. |
|
When the content type is added to the person profile as a content section, what fields are needed? |
To capture the previous employer, a text field is needed. To capture employment dates, two date fields are needed. To capture job description, another text field is needed. Therefore, the following fields must be added:
|
|
What properties are needed for the ITEM_TEXT30_1 field? |
The field should not be required and the information should not be available as search criteria, so you need only set up these field properties as follows:
|
|
What properties are needed for the ITEM_DATE_1 field? |
The field should not be required and the information should not be available as search criteria, so you need only set up these field properties as follows:
|
|
What properties are needed for the ITEM_DATE_2 field? |
The field should not be required and the information should not be available as search criteria, so you need only set up these field properties as follows:
|
|
What properties are needed for the ITEM_TEXT240_1 field? |
The field should not be required and the information should not be available as search criteria, so you need only set up these field properties as follows:
|
|
What role access should be granted for the content section? |
Employees, managers, and HR specialists should all have access to update the section. |
To set up a free-form content type to track previous employment information for workers, you must:
Set up a free-form content type
Add the free-form content type to the person profile type
|
Field |
Value |
|---|---|
|
Code |
PREVEMP |
|
Name |
Previous Employment |
|
Description |
Track previous employment information for workers. |
|
Column Name |
Label |
Display |
|---|---|---|
|
ITEM_TEXT30_1 |
Previous Employer |
Detail |
|
ITEM_DATE_1 |
From Date |
Detail |
|
ITEM_DATE_2 |
To Date |
Detail |
|
ITEM_TEXT240_1 |
Job Description |
Detail |
A label for a grouping of rating levels. Rating categories are used in talent management processes such as performance management and talent reviews to group ratings for analysis tools such as the performance and potential box chart.
You can edit any content type relationships that you define. However, the relationships that are predefined cannot be changed.
Set up the relationship on the content type that you want to relate to goals using the relationship type: Is supported by. For example, if you want to define a relationship between the Goals content type and the Competencies content type, set up the relationship on the Competencies content type, instead of the Goals content type.
Free-form content types enable you to capture information in a profile that you do not need to store in the content library. For example, you can set up a free-form content type to store information about the previous employment information for your workers.
A free-form content type contains only a code, name, and a description, and does not have any properties defined for it until you add it to a profile type. Free-form content types do not include any content items.
A content item's relationship type is derived from its content type, and you cannot change it. You can only change relationships at the content type level. You cannot change predefined relationships.
Profile types include person profile types and model profile types. The person profile type is the template that you use to create profiles of your workers. The person profile contains the skills, qualities, and qualifications that you want to track for your workers. The person profile type is predefined, and you can have only one. Model profile types are templates for workforce structures such as jobs and positions. Model profiles identify the targeted and required skills and qualifications for a job or position, and also identify work requirements, such as work schedule and travel frequency. You can set up multiple model profile types.
To define profile types, you first specify whether the profile type is a person or model profile. For model profiles, you also specify the workforce structures for which the model profile can be used. For example, if you specify that the model profile can be used for jobs and positions, then you can use the profile type to create both job and position profiles. To define the structure of the profile type, you add one or more content sections using content types from the content library and free-form content types. Define the following for each content section:
Instance qualifier sets
Section properties
Role access
If you have defined instance qualifier sets for the content type, you select the instance qualifier set to use for the sections.
The properties determine the fields and how they are displayed when you create profiles based on the type. For example, properties determine the label for the field, whether the field is required, and whether the field should be included in profile searches. For sections with content types from the content library, you can use the field properties as they have been defined in the content library, or add, remove, or change the properties to suit the content section. You define all of the properties for free-form content types.
You can specify the user roles, such as Employee or Manager, that can view the content section, and which user roles have access to update the section.
An instance qualifier set is a group of codes that you use to uniquely identify different occurrences of the same profile item within the Competency content type. Instance qualifiers typically identify the role of the person who edited a competency. For example, if a worker, the worker's peer, and the worker's manager all enter a rating for a competency on the worker's profile, instance qualifier sets uniquely identify each instance, or, the rating given by each different role. Uniquely identifying different instances of competencies enables you to specify which instance is used when you view or compare profiles.
Each instance qualifier contains a code and a description, which indicate the role or the application that updated the competency. For example, P is the code that is used when an employee's peer rates the employee and T is used for the rating that results from the talent review meeting. You can use the predefined codes and descriptions, or you can create your own.
In addition to the code and description, each instance qualifier has the following properties:
Priority
Employer and manager views
Search ability
Default instance qualifier for employer and manager
Priority determines the order in which different instances of a competency are displayed, and also determines which instance to use when searching and comparing profiles. The lowest number indicates the highest priority.
Employer and manager views determine which instances are visible to employees and to managers.
You can specify whether items that have been assigned the instance qualifier code should be included in profile searches. For example, you might not want the ratings for competencies given by peers to display when other workers are searching person profiles.
You can specify the default instance qualifier to use when managers and employees update a competency. Each time an employee or manager updates a competency, the record is assigned the instance qualifier code that is identified as the employee or manager default code.
Content subsections are for content types that have a parent content type. You add subsections to the content section for the parent content type.
Content sections are for content types that do not have a parent content type.
|
 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
