Thursday, October 9, 2014

FIC useful Links

Posted by at No comments:

Wednesday, October 8, 2014

FlexField--1

Administrators configure flexfield segments to capture data that represents the values of attributes. Flexfield segments represent attributes of entities (business objects). Most business objects are enabled for descriptive flexfields. Some business objects are enabled for extensible flexfields.
For example, an airline manufacturer might require very specific attributes for their orders that aren't provided by the out-of-the-box implementation of an order. Because a flexfield exists for the order business object, you can use it to create and configure the desired attribute.
The figure shows the layers of a flexfield: the business entity table and metadata in the database, business components that are Application Development Framework (ADF) objects or ADF business component (ADFbc) objects derived from the metadata and stored in the Metadata Services Repository (MDS), and the user interface where the input fields defined by the flexfield segments are rendered. The flexfield definition consists of all the metadata defined during configuration and stored in the database.
The figure follows flexfield development from adding capacity in the database to enable flexfield segments through applications development creating the flexfield and administrators configuring the flexfield so the definition is stored in the database and the business components are deployed to the Metadata Services repository, which makes the attributes representing the flexfields available in the user interface accessing those business components.
Application developers create a flexfield and register it so that it is available for configuration. Administrators and implementation consultants configure segments and other properties of the available flexfields. This information is stored as additional flexfield metadata in the database. Deploying the flexfield generates ADF business components based on the flexfield metadata in the database.
The following aspects are important in understanding how flexfields and Oracle Fusion Applications architecture work together:
  • Integration
  • Deployment
  • Import and Export
  • Runtime
  • Patching

Integration

The attributes that you add by configuring flexfields are available throughout the Oracle Fusion Middleware technology stack, allowing the flexfields to be used in user interface pages, incorporated into the service-oriented architecture (SOA) infrastructure, and, in the case of descriptive flexfields, integrated with Oracle Business Intelligence. You identify flexfield segments for integration by the segment's Application Programming Interface (API) name.
A flexfield affects the Web Services Description Language (WSDL) schemas exposed by ADF services and used by SOAcomposites. The Web services that expose base entity data also expose flexfield segment data.
Attributes incorporate into SOA infrastructure (BPEL, Rules) and integrate with business intelligence (Oracle Business Intelligence, Extended Spread Sheet Database (ESSbase)).
Flexfield configurations are preserved across Oracle Fusion Applications updates.

Deployment

The metadata for the flexfield is stored in the application database as soon as you save your configuration changes. Deploying the flexfield generates the ADF business components so that the runtime user interface reflects the latest definition of the flexfield in the metadata.

Importing and Exporting

You can export and import flexfields with a deployment status of Deployed or Deployed to Sandbox across instances of Oracle Fusion Applications using the Setup and Maintenance Overview page. Ensure a flexfield is eligible for migration (by verifying that it has successfully deployed) prior to attempting the migration.

Runtime

For a flexfield to reflect the latest flexfield definition at runtime it must be deployed. The user interface accesses a business object and the deployed flexfield definition indicates which business object attributes the flexfield captures values for. If you add display customizations for a flexfield using Oracle Composer, these are customizations on the page so that the same flexfield segments can appear differently on various different pages.
Values entered for segments are validated using value sets.

Patching

Flexfield configurations are preserved during patching and upgrading.
Posted by at No comments:

FlexFields

Incentive Compensation Base Transaction Descriptive Flexfield: Explained


Use Base Transaction incentive compensation descriptive flexfield global segments to store transaction attributes that do not exist by default in the CN_TP_TRANSACTIONS_ALL table.
The global segment data types VARCHAR2 and NUMBER have the following customizable attributes available for immediate use.
Data Type
Attributes
VARCHAR2 (240 CHAR)
ATTRIBUTE1 - ATTRIBUTE150
NUMBER
ATTRIBUTE_NUMBER1 -- ATTRIBUTE_NUMBER50
In the Setup and Maintenance work area:
  • Use the Manage Incentive Compensation Descriptive Flexfield task to configure one or more global segments, including associating any relevant value sets or lookups, and deploy the Base Transaction descriptive flexfield.
  • Use the Configure Tables and Columns task to enable the global segments for use in the calculation process.
  • Use the Manage Custom Rule Qualifiers task to enable the global segments for use in the crediting and classification processes.
======================
Why did my flexfield changes not appear in the runtime UI?
The ADF business components or artifacts of a flexfield, which are generated into an metadata services (MDS) repository when the flexfield is deployed, are cached within a user session. You must sign out and sign back in again to view flexfield definition changes reflected in the runtime application user interface page.
A flexfield's deployment status indicates whether the flexfield segments as currently defined in the metadata are available to end users. The flexfield segments seen by end users in the runtime correspond to the flexfield definition that was last deployed successfully.
=================




deployment status indicates how the flexfield metadata definition in the Oracle Fusion Applications database relates to the Application Development Framework (ADF) business components generated into a Metadata Services (MDS) repository.
The following aspects are important in understanding how flexfield deployment status is calculated:
  • Settings that affect flexfield deployment status
  • How deployment status is calculated

Settings That Affect Flexfield Deployment Status

If you have made a change to a flexfield and expect a changed deployment status, be sure you have saved your changes. No settings affect flexfield deployment status.

How Deployment Status Is Calculated

If the flexfield definition has been edited through the Define Flexfields activity task flows, the status is Edited. The latest flexfield metadata definition in the Oracle Fusion application diverges from the latest deployed flexfield definition. Any change, including if a value set used in a flexfield changes, changes the deployment status to Edited. If a flexfield has never been deployed, its status is Edited.


=================
Why did the extensible flexfield context not appear at runtime?
If a deployed extensible flexfield context doesn't appear in the user interface, verify that the context is associated with one of the category's pages defined for the extensible flexfield.
=================
Defining and driving segment values

To populate a flexfield segment with a default value when a row is created, specify a default type of constant or parameter and a default value.
To synchronize a segment's value with another field's value whenever it changes, specify the derivation value to be the flexfield parameter from which to derive the attribute's value. Whenever the parameter value changes, the attribute's value is changed to match. If you derive an attribute from a parameter, consider making the attribute read-only, as values entered by users are lost whenever the parameter value changes.
When defaulting or deriving a default value from a parameter, only those attributes designated by development as parameters are available to be chosen.
Different combinations of making the segments read only or editable in combination with the default or derivation value or both, have different effects.
Initial runtime behavior corresponds to the row for the attribute value being created in the entity table. If the default value is read only, it cannot subsequently be changed through the user interface. If the default value isn't read only, users can modify it. However, if the segment value is a derived value, a user-modified segment value is overwritten when the derivation value changes.
Default Type
Default value specified?
Derivation value specified?
Initial runtime behavior
Runtime behavior after parameter changes
None
No
Yes
No initial segment value
The changed parameter derivation value updates segment value
Constant
Yes
No
Default segment value
N/A
Constant
Yes
Yes
Default segment value
The changed parameter derivation value updates segment value
Parameter
Yes
No
The default segment value is the parameter's default value
N/A
Parameter
Yes
Yes, and same as default value
The default segment value is the parameter's default and derivation value
The changed parameter derivation value updates segment value
Parameter
Yes
Yes, and different from default value
The default segment value is the parameter's default value
The changed parameter default value doesn't update segment value. Only the changed derivation value updates the segment value.
====================


Posted by at No comments:

Participant Import

APPLIES TO:

Oracle Fusion Incentive Compensation Cloud Service - Version 11.1.7.0.0 and later
Information in this document applies to any platform.

GOAL

How to import specific users as participants into Incentive Compensation?
 

SOLUTION

You can use the filters to restrict which users will be imported as participants. You can use the following conditions to filter users to be imported as participants:

ROLE :
Text input, with wildcard support. If you provide a value, Oracle Data
Integrator matches it against the Oracle Fusion Resource Manager value
JTF_RS_ROLES_B.ROLE_CODE.
ROLE TYPE:
Text input, without wildcard support. If you provide a value, Oracle Data
Integrator matches it against the value JTF_RS_ROLES_B.ROLE_TYPE.
In order to filter by role you can run a query in BI answers like
select role_code, role_type_code
from jtf_rs_roles_b
order by role_code

The role_code can be found in manage users under Resource Information, there is a dropdown for resource role. In the dropdown you can see a number of resource roles and while you import participant you can use the associated role_code in your filter for participants. Say you assign a resource role of IC Salesrep (this is user defined), you need to find out the role_code for IC_Salesrep in jtf_roles_b in my case its IC_REP and if i wanted to import this user as a participant only i would filter by Resource Role=IC_REP.

PERSON NUMBER:
Text input, without wildcard support. If you provide a value, Oracle
Data Integrator matches it against the Oracle Fusion HCM value
PER_ALL_PEOPLE_F.PERSON_NUMBER

person number can be located by navigating to
Workforce Management > Person Management and query up the user.
 
Posted by at No comments:
Subscribe to: Posts (Atom)