FlexFields

Incentive Compensation Base Transaction Descriptive Flexfield: Explained

Help topic

|

06/18/2014

|

Generic

Edit

Bookmark

Tags

Print

E-Mail

Discuss (0 topics)

Add Rating

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. ====================