Flexfield Setup Whitepaper

Extensible Flexfield Setup
An Oracle White Paper

November 2014
Oracle Fusion Product Hub
Extensible Flexfield Set Up
Page 1 of 31
Disclaimer
The following is intended to outline our general product direction. It is intended for information
purposes only, and may not be incorporated into any contract. It is not a commitment to deliver
any material, code, or functionality, and should not be relied upon in making purchasing
decisions. The development, release, and timing of any features or functionality described for
Oracles products remains at the sole discretion of Oracle.
Page 2 of 31
Executive Overview ......................................................................... 4

Introduction ..................................................................................... 4
Terms and Definitions ..................................................................... 5
Solution Overview ........................................................................... 6
Extensible Flexfield Attribute Groups and Attributes ................... 7
Attribute Group ............................................................................ 7
Usage ......................................................................................... 10
Create Privilege in Oracle Authorization Policy Manager (APM) ......... 11
Attribute ..................................................................................... 11
Value Sets ............................................................................................ 13
Item Class Association ............................................................. 17
Pages.......................................................................................... 18
Flexfield Deployment................................................................. 19
Extensible Flexfield Data Security............................................ 20
Frequently Asked Questions ........................................................ 25
Resources ...................................................................................... 30
Page 3 of 31
Executive Overview
Extensible flexfields allows users to configure their items to add custom attributes that are not seeded. These attributes
can be added based on your business needs and they can be displayed as a single row or multi-row attributes. For more
information on extensible flexfield see Oracle Fusion Applications Developer's Guide 11g Release 9 (11.1.9) Part
Number E10308-09.
Introduction
This whitepaper explains the set up process required for extensible flexfields in Product Information Management
(PIM). This document explains the pre-setup steps as well as post setup steps required for exposing extensible flexfields
and also address the Frequently Asked Questions (FAQs).
Page 4 of 31
Terms and Definitions
TERM DEFINITION
EFF An extensible flexfield is similar to a descriptive flexfield in that

it provides an additional customization of the pages that
implementors, such as Oracle Fusion Applications customers,
can use to configure additional attributes (segments) without
additional programming.
Attribute Group A logical group of attributes that is displayed in its own sub
region of the user interface (UI) page at runtime.
Attribute The specific characteristics of an item.
APM Authorization Policy Manager. Application where the duty roles

and privileges are managed.
Privilege A special right granted to a person or a group of people.
Deploy Deployment generates or refreshes the Application

Development Framework (ADF) business component objects in
MDS that render the flexfield in a user interface. The
deployment process adds the custom attributes to the Web
Services Description Language (WSDL) schemas that are
exposed by Oracle ADF services and that are used by SOA
composites.
FSM Functional Setup Manager
Context An extensible flexfield context is a data grouping mechanism

that implementors can use to arrange segments into meaningful
groups. An attribute group is referred to as a context.
API Application programming interface. A published interface to

accomplish a business or scientific function. An API defines a
contract to its users by guaranteeing a published interface but
hides its implementation details.
Segments Attributes. With extensible flexfields, every segment is a member

of a context (attribute group). That is, every segment is a
context-sensitive segment.
Value Set A predefined, named group of values that can be used to

validate the content of a flexfield segment.
UCM Oracle Universal Content Management
MDS Metadata Services Repository

Table 1: Terms and Definitions
Page 5 of 31
Solution Overview
The diagram below, Overview Extensible Flexfield Setup Process, provides an overview of all the tasks
involved in the set up of the extensible flexfield (EFF) of an item class. Each setup task is accessed through
the Functional Setup Manager (FSM) and must be completed to gain access to the extensible flexfield
attribute.
The attribute groups and attributes in product information management are built on the extensible flexfield
infrastructure and some of the terms for the EFF components have been re-labeled to make it easier for
you to understand.
The extensible flexfields include the following key artifacts:

Attribute Groups (Contexts)
Usages (Context usage)
Attributes (Context-sensitive segments)
Pages (Logical pages)
Item Classes (Categories, categories hierarchy)
Figure 1: Overview of Extensible Flexfield Setup Process
Page 6 of 31
The Taxonomy of Extensible Flexfield Artifacts diagram provides an overview of how and where the
different artifacts are positioned. This will enable you to understand why certain setup is required and
where used.
Figure 2: Taxonomy of the Extensible Flexfield Artifacts
Extensible Flexfield Attribute Groups and Attributes

To create an attribute group and attributes, you must use Manage Item Attribute Groups and Attributes
task which is accessed through Setup and Maintenance.
Setup and Maintenance >> All Tasks >> Manage Item Attribute Groups and Attributes
Figure 3: Access to task
Attribute Group
An attribute group is a logical grouping of attributes. It is also referred to as Context in Oracle Fusion
Applications. Each attribute group/context is associated with one or more item classes. An attribute group
can be configured as a single row, or multi-row which means that the attributes can be displayed as a name-
value pair in a form format or in a table format.
To create an attribute group, you must enter a display name and an internal name. An API name is
generated by the system. You are required to select the behavior of the attribute groups that determines
whether the attributes within the attribute group is displayed as a single row or multiple row.
Page 7 of 31
Once saved, you cannot edit the behavior of the attribute group. You will have to discard it and begin the
creation of new attribute group with the correct behavior type.
In the example below the attribute group is Technical Specifications and within the group, multiple
attributes are defined along with the context usage.
Figure 4: Edit Attribute Group (Context)
Display Properties
The following table summarizes display properties for attribute group definition.
ATTRIBUTE DESCRIPTION
Flexfield Name Item Extended Attributes.

Flexfield Code EGO_ITEM_EFF. This is system generated.
The Application Programming Interface (API) name is a name
for the attribute that isn't exposed to end users. It is system
API Name generated and is used to identify the attribute in various
integration points including web services, rules, and business
intelligence.
Enabled Whether the attribute group can be used.
If an attribute group is marked as translatable, all attribute values
are stored in the translation extension table. If an attribute group
is not marked as translatable all attribute values are stored in the
base extension table. This means that a translatable attribute
Translatable
group cannot contain attributes of non-translatable data types,
such as numbers or dates. By enabling translation, the language
for the session can be changed and data can be entered in the
sessions language through the same UI.
Behavior Single Row/Multiple Row.
An attribute used to create style and SKU items. Ex: A shirt for
Variant Attribute men comes in three colors, white, blue, and yellow. The value
set will be created for shirt color with three values, one for each
Page 8 of 31
of the shirt colors.

The group-level instruction help text to display for the group.
Instruction help text is used to provide directions on using the
Instruction help text
attribute group. If instruction help text is specified, it is
displayed in the attribute group header title.
Table 2: Display Properties for Attribute Group
The run time display of a single row or multi-row behavior is shown below:
Figure 5: Example of Single Row Attribute Group
Figure 6: Example of a Muli-Row Attribute Group
If an item has an attribute group defined as variant, it is displayed in the overview tab of the item.
Figure 7: Example of Variant Attributes
Page 9 of 31
Usage
You must configure the usage prior to creating attributes within the attribute group. The create button for
the attribute is enabled only after saving the usage configuration. The setup of context usage will determine
at which data level the attribute group is associated.
Figure 8: Context Usage
The different data levels are at Item, Item Revision, and Item Supplier of the item and they are displayed in
the Specifications tab of the items page.
As a part of context usage configuration, you can set variant attribute groups as blank, defaulted, or
inherited across child item classes by using the Style to SKU column setting. Attributes groups can be
defaulted or inherited from master organization to child organization by using the Master to Child
Organization column setting.
Privileges can be associated to the attribute group based on the data level set up. These privileges are
created in the Oracle Authorization Policy Manager (APM).
Display Properties
The following table summarizes display properties for context usage.

ATTRIBUTE DESCRIPTION
Determines the attribute group display at runtime. It can be at

Name
Item, Item Revision, or Item Supplier level.
Determines the configuration of non-variant attributes values
Style to SKU
for a SKU item. It can be None, Defaulted or Inherited.
Even if the parent item/style item has a value associated with it,
None
the same attribute for the child/SKU will be blank.
The attribute value will be inherited from the parent item/style
Inherited
item and these values are read-only.
The attribute value will be defaulted from the parent item/style
Defaulted
item but these values are editable.
Master to Child Determines the configuration of attributes values from master
Organization organization to child organizations
View privilege created in APM associated to extensible flexfield
View Privileges
attribute group at a specific data level.
Edit privilege created in APM associated to extensible flexfield
Edit Privileges
attribute group at a specific data level.
Table 2: Display Properties for Context Usage
Page 10 of 31
Create Privilege in Oracle Authorization Policy Manager (APM)

The creation of privilege in the Oracle Authorization Policy Manager (APM) is discussed in Using Data
Security Features of Oracle Fusion Product Data Hub whitepaper.
Attribute
Each attribute group contains one or more attributes. In the context of a flexfield, an attribute is also
referred to as Context-Sensitive Segment or just Segment. An attribute is always defined within an
attribute group.
In PIM, an EFF attribute is created by accessing the Manage Item Attribute Groups and Attributes task.
Once an attribute group is created, an attribute is created from within the Edit Attribute Group page. This
is accomplished by selecting the Create icon in the Attributes table toolbar or selecting Create from
Actions menu.
Any attribute created will automatically be assigned the next available sequence number and the sequence
number is editable. The sequence number will determine the sequence in which the attribute will appear
within the attribute group.
In the example below, an attribute, Memory, is created within the attribute group, Technical
Specifications. Properties of the attributes are defined that determines the data type, value set it is
associated to, display properties, etc.
Figure 9: Edit Attribute (Segments)
Display Properties
The following table summarizes display properties for an attribute.

ATTRIBUTE DEFINITION
Enabled Whether the attribute can be used.

The data type determines the type of information the variable
Data Type
holds. It can be a Character, Number, Date, and Date and Time
Based on the data type selected, the table column is system
Table Column
generated.
Page 11 of 31
The indexed property requires end users to enter a value before

conducting a search on the attribute represented by the indexed
Indexed
segment. A database administrator must create an index on the
segment column representing the indexed attribute.
A value set is a group of valid values that you assign to a
Value Set flexfield segment to control the values that are stored for
business object attributes.
If the attribute is part of a range specification, whether the
attribute is the low value or the high value. For example, if
Range Type
adding minimum height and maximum height attributes, then
the minimum height attribute has a range type of low.
Required Whether the end user is required to provide a value.
The initial default value for an attribute when the row is created.
You can specify a constant value or, for descriptive flexfields,
Initial Default Type
you can specify a flexfield parameter, which provides a derived
value.
The string to be used for the attributes label in the user
Prompt
interface.
Display type The type of field in which to display the attribute.
Display size The character width of the field.
The height of the field as measured in visible number of lines
Display height
when the display type is a text area.
Whether the field should display as read-only, not editable text.
This is used when the value for the attribute is populated based
Read only
on a rule or its coming from a different system and you don't
want the users to change it.
The field-level description help text to display for the field. Use
description help text to display a field-level description that
expands on or clarifies the prompt provided for the field.
Description help text If description help text is specified, a Help icon button is
displayed next to the field in the run time application. The
description help text is displayed when the user hovers over the
Help icon button.
The field-level instruction help text to display for the field.
Use instruction help text to provide directions on using the field.
Instruction help text If instruction help text is specified, it is displayed in an in-field
help note window that appears when users give focus to or
hover over the field.
When enabled, the attribute is available for use in Oracle
Business Intelligence (BI). This is available only in release 10.
BI Enabled
See Enabling Extensible Flexfield Segments for Business
Intelligence: Points to Consider
Checked and unchecked If the display type is check box, the actual values to save. For
values example, Y and N or 0 and 1. The checked/unchecked values
Page 12 of 31
must match the Value Set values else the data is not stored
accurately.
The order the attribute appears in relation to the other
Sequence
configured attributes.
Displays a value set value with its description when the display
Show value description
type is a droplist or a list of values.
Table 3: Display Properties for Attributes
Value Sets
A value set is used in data validation in the Oracle Fusion Applications. Each value set is associated to one
or more attributes in the same attribute group or a different attribute group. A value set can be predefined
by accessing Manage Value Set task in Setup and Maintenance. However, for the PIM extensible flexfields,
you can easily create a value set directly from the item attribute group page by clicking on Create Value Sets
button.
The following types of validation are available for value sets:
Format only - end users enters 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 is derived from the independent value of another
attribute
Subset - a list of values is a subset of the values in an existing independent value set
Table - the values are derived from a column in an application table and the list of values is limited
by a WHERE clause
The most commonly used validation types are, independent and format only.
In the example below, a value set, sm_memory_va is created as an independent validation type.
Figure 10: Edit Value Set
Page 13 of 31
Within the value set sm_memory_vs, multiple values are created. In the example below multiple memory
sizes are created as values.
Figure 11: Manage Values
Each value is created one at a time by clicking on the Create icon in the Manage Values page or by
selecting Create from the Actions menu.
Figure 12: Edit Value
Once you create the values, you must save and close the page then, click Done to navigate back to the page
for value set.
In the example below for format only value set, the maximum value for camera megapixel must not exceed
the maximum value of 50.0 or fall below 4.9.
The precision defined below defines the maximum number of digits allowed and scale defines the
maximum number of digits following the decimal point that can be entered.
Figure 13: Example of Format Only Value Set
Page 14 of 31
Import Value Set
Value sets can be imported if it is file-based. These files must be in the specified format as shown in the
screenshots below. Multiple value sets along with their values can be uploaded through one import process.
Figure 14: Independent Value Set Values Data File
Figure 15: Dependent Value Set Values Data File
To import the values, you must follow the following steps:

1. Create the value sets
2. Create a file in the specified format
Figure 16: Create File in Specified Format for Independent Validation Type
Page 15 of 31
3. Go to the Navigator and select File Import and Export. The Actions menu in the Search Results
region has an Upload action that will allow you to load the file to UCM. Select the file you created
and select Account = scm/item/import. The Account is seeded and determines the location of
the file in UCM where it is uploaded.
Figure 17: Select File Import and Export in the Navigator Figure 18: Upload File to UCM
Figure 19: File is Uploaded to UCM
4. Once it is uploaded to the UCM, go back to the Navigator and select Setup and Maintenance
5. Search for the task Manage Value Sets and select Import from the Actions menu located in the
Search Results region
6. Enter the file name and Account = scm/item/import. Note that the file name is case sensitive
and this should match the one you uploaded
Figure 20: Import the Value Sets
7. Click Upload
Page 16 of 31
Item Class Association

After one or more extensible flexfield attribute groups are created, the attribute group must be associated
to an item class or they are deemed as orphans. Follow the navigation path to associate an attribute group
to an item class:
Setup and Maintenance >> All Tasks >> Manage Item Classes >> Pages and Attribute Groups Tab
In order to add an attribute group to a page, you must add the attribute group to the attribute groups tab in
the item class. When the attribute group has been added to the attribute groups tab, you MUST save prior
to associating the attribute group to a page.
In the example below, the attribute group, Technical Specifications is added to the Attribute Groups tab.
Figure 21: Add EFF Attribute Group to Item Class
The logical diagram of EFF at run time shows the arrangement of EFF artifacts in the context of an item.
Figure 22: Logical Diagram of EFF at Run Time
Page 17 of 31
Pages
Attribute groups are grouped together in what is called the pages. A page is also referred to as Logical
Page in Oracle Fusion Application. Each page consists of one or more attribute groups along with their
attributes. There is no limit to how many attribute groups can be added to a page. There is also no limit on
how many pages that can be created per item class. The sequence of the pages is determined by the
sequence number when creating a page.
In the example below, a page called Technical Specifications is created for the item class, Smartphones.
Figure 23: Create Page
In the example below, after a page, Technical Specifications is created, the attribute group, Technical
Specifications is added.
Figure 24: Add Page to Item Class
At run time, the page is displayed in the left hand pane in the specifications tab and the attribute groups
along with its attributes are displayed in the right hand pane of the selected page.
Page 18 of 31
Usage
Attribute Group and Attribute
Page
Figure 25: Run Time Page Display
Flexfield Deployment
Once the attribute groups and the pages are associated to an item class, the flexfield must be deployed.
Without deploying the flexfields, you cannot view the pages or attribute groups at run time. To deploy the
flexfield, follow the following navigation path:
Setup and Maintenance >> All Tasks >> Manage Extensible Flexfield >> Search and Select the Flexfield
>> Deploy Flexfield
The easiest way to search for the PIM extensible flexfield is to enter the flexfield code as EGO.
Figure 26: Extensible Flexfield Deployment
In the Oracle Fusion Application, there are three methods to deploy flexfield and they are:
1. Deploy Flexfield an online incremental/delta deployment. The process begins immediately and
you can monitor the deployment process. When you use this action, only the extensible flexfield
set up that has changed will be deployed. This is what is meant by incremental deployment.
The progress window show when deployment is completed. The icon for the deployment status is
changed based on the result of the deployment.
You MUST log out and log back in to view the EFF configuration on the item.
2. Deploy Offline an offline, background process of incremental/delta deployment. When this

action is selected, you can continue working on the session without having to wait for deployment
to complete.
Page 19 of 31
You must choose this action if the flexfield changes impact 30 or more item classes. For more
information see Oracle Fusion Applications Extensibility Guide 11g Release 6 (11.1.6)
3. Refresh & deploy offline a complete (forced) deployment of all available extensible flexfield.
The completion time for this type of deployment is dependent on the number of flexfields you
have set up. Hence, this option should be utilized only if the first two options result in errors.
The icons in the offline status column and the deployment status column indicate the progress
and result of the deployment.
Extensible Flexfield Data Security

Extensible flexfield data security is discussed in detail in Using Data Security Features of Oracle Fusion
Product Data Hub white paper
Import Attribute Groups, Attributes and Value Sets

A file-based import can be used to import attribute groups, attributes and value sets. The data files for
attribute groups, attributes and value sets must be in the specified formats as shown in the tables below.
Multiple attribute groups along with their attributes and value sets can be uploaded through one import
process.
Attribute Group Data File Columns

COLUMN NAME MANDATORY? DATA TYPE SIZE DESCRIPTION
APPLICATIONID YES LONG LONG FOR PRODUCT HUB: 10010
EFFCODE YES STRING 40 FOR EFFS IN PRODUCT HUB: EGO_ITEM_EFF
CONTEXTCODE YES STRING 80 CODE OF THE EFF ATTRIBUTE GROUP
NAME YES STRING 80 NAME OF THE EFF ATTRIBUTE GROUP
MULTIROWFLAG YES STRING 1 FLAG TO INDICATE A MULTIROW
ATTRIBUTE GROUP. VALUES: Y OR N
ENABLEDFLAG YES STRING 1 FLAG TO INDICATE AN ENABLED
ATTRIBUTE GROUP. VALUES: Y OR N
DESCRIPTION NO STRING 240 DESCRIPTION OF THE EFF ATTRIBUTE

GROUP
FLEXFIELDUSAGECODE YES STRING 30 CONTEXT USAGE OF THE ATTRIBUTE
GROUP.
FOR ITEM USAGE: EGO_ITEM_DL
FOR ITEM REVISION USAGE:
EGO_ITEM_REVISION_DL
FOR ITEM SUPPLIER USAGE:
EGO_ITEM_SUPPLIER_DL
VIEWPRIVILEGENAME NO STRING 400 NAME OF THE VIEW PRIVILEGE CREATED
IN APM ASSOCIATED TO EXTENSIBLE
FLEXFIELD ATTRIBUTE GROUP AT A
SPECIFIC DATA LEVEL.
EDITPRIVILEGENAME NO STRING 400 NAME OF THE EDIT PRIVILEGE CREATED
Page 20 of 31
IN APM ASSOCIATED TO EXTENSIBLE
FLEXFIELD ATTRIBUTE GROUP AT A
SPECIFIC DATA LEVEL.
CEXTATTRIBUTE1 NO STRING 150 CONTEXT USAGE SPECIFYING STYLE TO
SKU BEHAVIOR.
CEXTATTRIBUTE2 NO STRING 150 CONTEXT USAGE SPECIFYING MASTER TO
CHILD BEHAVIOR.
CEXTATTRIBUTE3 NO STRING 150 NOT IN USE FOR PRODUCT HUB.
Table 4: Attribute Group Data File
** IMPORT OF TRANSLATABLE ATTRIBUTE GROUPS IS NOT SUPPORTED.
Attribute Data File Columns

APPLICATIONID YES LONG LONG FOR PRODUCT HUB: 10010
EFFCODE YES STRING 40 FOR EFFS IN PRODUCT HUB: EGO_ITEM_EFF
CONTEXTCODE YES STRING 80 CODE OF THE EFF ATTRIBUTE GROUP
SEGMENTCODE YES STRING 30 CODE OF THE EFF ATTRIBUTE
NAME YES STRING 60 NAME OF THE EFF ATTRIBUTE
COLUMNNAME YES STRING 30 TABLE COLUMN FOR THE EFF ATTRIBUTE
VALUESETCODE YES STRING 60 CODE OF THE VALUE SET OF THE EFF
ATTRIBUTE
DISPLAYTYPE YES STRING 30 DISPLAY TYPE OF THE EFF ATTRIBUTE
PROMPT YES STRING 80 PROMPT OF THE EFF ATTRIBUTE
SHORTPROMPT YES STRING 80 SHORT PROMPT OF THE EFF ATTRIBUTE
ENABLEDFLAG YES STRING 1 FLAG TO INDICATE AN ENABLED EFF
ATTRIBUTE. VALUES: Y OR N
REQUIREDFLAG YES STRING 1 FLAG TO INDICATE A REQUIRED EFF
READONLYFLAG YES STRING 1 FLAG TO INDICATE A READ-ONLY EFF
DESCRIPTION NO STRING 240 DESCRIPTION OF THE EFF ATTRIBUTE
UOMCLASS NO STRING 10 UOM CLASS FOR NUMERIC EFF ATTRIBUTES
Table 5: Attribute Data File
Value Set Data File Columns

VALUESETCODE YES STRING 60 VALUE SET CODE USED TO IDENTIFY THE VALUE SET
MODULETYPE YES STRING 60 MODULE TYPE. THIS VALUE USED TO GET MODULE ID
FROM VIEW FND_APPL_TAXONOMY_VL
Page 21 of 31
MODULEKEY YES STRING 60 MODULE KEY. THIS VALUE USED TO GET MODULE ID
FROM VIEW FND_APPL_TAXONOMY_VL
VALIDATIONTYPE YES STRING 30 THE VALIDATION TYPE OF THE VALUE SET.
CURRENTLY THIS FEATURE SUPPORTS INDEPENDENT
(INDEP) VALUE SET CREATION.
VALUEDATATYPE YES STRING 30 VALUE DATA TYPE OF THE VALUE SET.
VALUESUBTYPE YES STRING 30 VALUE SUBTYPE OF THE VALUE SET.
MAXIMUMLENGTH YES INTEGER INT MAXIMUM LENGTH FOR VALUE SUBTYPES OF THE
VALUE SET.
DESCRIPTION NO STRING 240 DESCRIPTION OF THE VALUE SET.
Table 6: Value Set Data File
To import the attribute groups, attributes and value sets, you must follow the following steps:
1. Create the data files for attribute groups, attributes and value sets in the specified format:
Figure 27: Create File for Attribute Groups
Figure 28: Create File for Attributes
Figure 29: Create File for Value Sets
2. Go to the Navigator and select File Import and Export. The Actions menu in the Search Results
region has an Upload action that will allow you to load the file to UCM. Select the files you
created and select Account = scm/item/import. The Account is seeded and determines the
location of the file in UCM where it is uploaded.
Page 22 of 31
Figure 30: Select File Import and Export in the Navigator Figure 31: Upload Files to UCM
Figure 32: Files are Uploaded to UCM
3. Once the files are uploaded to the UCM, go back to the Navigator and select Setup and
Maintenance
4. Search and open the task, Manage Extensible Flexfields. On the Manage Extensible Flexfields
page, select Import from the Actions menu located in the Search Results region
5. Select Account = scm/item/import and enter ValueSet = <value set data file name>, Context =
<attribute group data file name> and Segment = <attribute data file name>. Note that you can
leave any of the fields blank if you dont want to import attribute group, attribute or value set.
Page 23 of 31
Figure 33: Import the Attribute Groups, Attributes and Value Sets
6. Click Upload
Page 24 of 31
Frequently Asked Questions

1. Why did the extensible flexfield context not appear at run time?
If a deployed extensible flexfield context doesn't appear in the user interface, verify that the
attribute group is associated with one of the item class pages defined for the extensible
flexfield.
Verify that the flexfield is in the deployed status. This can be accomplished by checking the
deployments status column.
You must log out and log back in after every deployment.
2. Why did the change made to the value set not appear at run time?
When you change an existing value set, the deployment status for all affected flexfields changes to
Edited. You must redeploy all flexfields that use that value set to make the flexfields reflect the
changes.
3. Why was the change made to the privilege not applied?

If you change a privilege for a usage after you deploy the flexfield, you must redeploy the flexfield for
the change to take place.
4. How do I debug EFF deployment failures?

Download MDS artifacts for EGO_ITEM_EFF from Manage Extensible Flexfields UI:
1. Now you can download the EFF artifacts from the Applcore's Manage Extensible Flexfields UI
2. This will only download the EGO_ITEM_EFF ones and so the download is faster and the zip
archive is much smaller.
3. Screenshots for information on how to access/download it.
Page 25 of 31
5. Where is the MDS file download to, Desktop or Server? And, does it prompt me to
save the file?
The MDS files are downloaded to the desktop and yes, you are prompted to save the file.
6. EFF was deployed but why dont I see it on the Item?

You must log out then log back in to view the EFF configuration.
7. Why can I not edit the attribute group from a single row to a multiple row type?
Once you click on save, you cannot change the selection. You must create a new attribute group.
8. Manage Values button is deactivated. How can I activate the button?

You must save to activate the Manage Values button.
9. Can attribute groups be deleted or end-dated?

No. An attribute group once created cannot be deleted or end-dated. It can however, be disabled by
un-checking the Enabled check box.
10. What happens to the data that is already entered for the attribute group that is
now disabled? Will it still show on item specifications? If yes, will you be able to
edit the attributes?
Once the EFFs are regenerated/deployed, the data will not be displayed in the Item Specifications and
you will not be able to edit the attributes any longer. However, the data is not deleted and will remains
in the tables.
Page 26 of 31
11. Attribute group was added to attribute groups tab in the item class but I cannot
find the group to add it to the page.
After the attribute group is added to the attribute groups tab, you must save.
12. Can a value set be created where it is dependent on the value entered for another
attribute?
Yes, you can use the cross context bind variables to create a where clause for a table-based value set.
In the example below, the values for the SEGMENT attribute is filtered based on the item class
entered for CONTEXT attribute.
13. Can EFFs be used in item rules framework?

Yes. EFFs can be used in item rules.
14. How can one find all attribute groups defined?

You can query the attribute groups using Manage Item Attribute Group and Attributes UI.
15. Can EFFs be mass updated? If yes, how?

Yes, you can mass update EFF attributes using the user interface or though a spreadsheet. To update
the EFF attributes through the UI, you must:
1. Add the EFFs as a column to the search results table of the Manage Items Page
2. Select the items for which you want the attributes updated
3. Click on the Actions Menu > Manage Item Mass Changes > Edit Item Attributes
4. Edit the appropriate attributes
Page 27 of 31
5. Apply the changes

6. Click on Next and Submit the item batch.
To edit the attributes in a spreadsheet:

1. Click on the Actions Menu > Manage Item Mass Changes > Edit Item Attributes in a
Spreadsheet
2. Select the import format
3. Open the downloaded spreadsheet

4. Edit the appropriate attributes
5. Upload the spreadsheet
16. Can EFFs be imported?

Yes, you can use the item batch to import EFF values. Import of spreadsheet to the interface tables
can import EFFs.
17. List the PIM tables where EFF values are stored.
EGP_ITEM_CLASSES_B - Stores item class definitions.
EGO_ITEM_EFF_B/TL - Stores attribute values.
18. List the middleware table that stores the EFF metadata.
FND_DF_CONTEXTS_B/TL - Stores attribute group definitions for DFFs and EFFs.
Page 28 of 31
FND_DF_SEGMENTS_B/TL - Stores attribute definitions for EFFs and DFFs.

FND_VS_VALUE_SETS - Stores flexfield value set definitions.
FND_VS_VALUES_B/TL - Stores value set values.
FND_EF_CATEGORIES_B - Stores item class definitions.
FND_EF_CONTEXT_USAGES Stores data level/business entity, item/item revision/item
supplier etc usage definitions.
19. Does EFF support rich text format (RTF)? If yes, what is the display configuration
for the attributes?
Yes, RTF is supported in the EFFs. To use a rich text data type, you will need a column size greater
than 500 to a maximum of 4000 character size.
In R10, only translatable attributes are supported because the column size for a translatable attribute is
1000 characters, whereas non-translatable attributes in R10 has only 150 character size.
It is recommended that you use the type, format only for the value set.
Page 29 of 31
Resources
Oracle Fusion Applications Developer's Guide 11g Release 9 (11.1.9)
Oracle Fusion Applications Help
o Flexfields and Oracle Fusion Application Architecture: How They Work Together
o Value Sets: Explained
o Defining Value Sets: Critical Choices
o Flexfields and Value Sets: How They Work Together
o Flexfield Deployment: Explained
o Upload Value Set Values Process
o Uploading Value Set Values: Explained
Oracle Applications Cloud Extending the Applications for Functional
Administrators
o Flexfields for Custom Attributes
Oracle Fusion Applications Extensibility Guide 11g Release 6 (11.1.6)
o Creating Custom Value Sets
Page 30 of 31
Fusion Product Hub Publication Process Copyright 2012, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and the contents hereof
November 2014 are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether
Author: Ringo Shakya expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically
disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This
document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written
Oracle Corporation
permission.
World Headquarters
500 Oracle Parkway
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Redwood Shores, CA 94065
U.S.A.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or
Worldwide Inquiries: registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered
Phone: +1.650.50--6.7000 trademarks of Advanced Micro Devices. UNIX is a registered trademark licensed through X/Open Company, Ltd. 0112
Fax: +1.650.506.7200
oracle.com

Flexfield Setup Whitepaper

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Flexfield Setup Whitepaper

Caricato da

Copyright:

Formati disponibili

Extensible Flexfield Setup

An Oracle White Paper

Oracle Fusion Product Hub

Extensible Flexfield Set Up

Executive Overview ......................................................................... 4

Terms and Definitions

EFF An extensible flexfield is similar to a descriptive flexfield in that

Attribute The specific characteristics of an item.

APM Authorization Policy Manager. Application where the duty roles

Privilege A special right granted to a person or a group of people.

Deploy Deployment generates or refreshes the Application

FSM Functional Setup Manager

Context An extensible flexfield context is a data grouping mechanism

API Application programming interface. A published interface to

Segments Attributes. With extensible flexfields, every segment is a member

Value Set A predefined, named group of values that can be used to

MDS Metadata Services Repository

The extensible flexfields include the following key artifacts:

Figure 1: Overview of Extensible Flexfield Setup Process

Figure 2: Taxonomy of the Extensible Flexfield Artifacts

Extensible Flexfield Attribute Groups and Attributes

Figure 3: Access to task

Figure 4: Edit Attribute Group (Context)

Flexfield Name Item Extended Attributes.

of the shirt colors.

Figure 5: Example of Single Row Attribute Group

Figure 6: Example of a Muli-Row Attribute Group

Figure 7: Example of Variant Attributes

Figure 8: Context Usage

The following table summarizes display properties for context usage.

Determines the attribute group display at runtime. It can be at

Create Privilege in Oracle Authorization Policy Manager (APM)

Figure 9: Edit Attribute (Segments)

The following table summarizes display properties for an attribute.

Enabled Whether the attribute can be used.

The indexed property requires end users to enter a value before

The following types of validation are available for value sets:

Figure 10: Edit Value Set

Figure 11: Manage Values

Figure 12: Edit Value

Figure 13: Example of Format Only Value Set

Import Value Set

Figure 14: Independent Value Set Values Data File

Figure 15: Dependent Value Set Values Data File

To import the values, you must follow the following steps:

Figure 19: File is Uploaded to UCM

Figure 20: Import the Value Sets

Item Class Association

Figure 21: Add EFF Attribute Group to Item Class

Figure 22: Logical Diagram of EFF at Run Time

Figure 23: Create Page

Figure 24: Add Page to Item Class

Figure 25: Run Time Page Display

Figure 26: Extensible Flexfield Deployment

2. Deploy Offline an offline, background process of incremental/delta deployment. When this

Extensible Flexfield Data Security

Import Attribute Groups, Attributes and Value Sets

Attribute Group Data File Columns

APPLICATIONID YES LONG LONG FOR PRODUCT HUB: 10010

EFFCODE YES STRING 40 FOR EFFS IN PRODUCT HUB: EGO_ITEM_EFF

CONTEXTCODE YES STRING 80 CODE OF THE EFF ATTRIBUTE GROUP

NAME YES STRING 80 NAME OF THE EFF ATTRIBUTE GROUP

MULTIROWFLAG YES STRING 1 FLAG TO INDICATE A MULTIROW

ATTRIBUTE GROUP. VALUES: Y OR N