D96139GC10 Appendix A

A
Unauthorized reproduction or distribution prohibited Copyright 2016, Oracle and/or its affiliates
Appendix A: Common
Application Topics
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens Copyright 2016, Oracle and/or its affiliates. All rights reserved.
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no
Objectives
After completing this lesson, you should be able to:

Manage Oracle Social Network Objects.
Define Flexfields.
Define Lookups.
Define Profile Options.
Define Attachments.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no
Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 2

Manage Oracle Social Network Objects
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
d d y l i ce Copyright 2016, Oracle and/or its affiliates. All rights reserved.
R e able
r th sfer
aOracle
To manage
h a t r a nSocial Network objects, use the Manage Oracle Social Network Objects
B
task in the n - and Maintenance work area.
Setup
n o
Enabling Business Objects for Integration
You can determine whether information about a business object, such as benefit plans
or sales accounts, appears in social network.
If you enable an object for sharing, users can collaborate on the object through social
networking. You can choose whether all instances of an object are shared, or only at the
user's discretion. You can also choose which attributes are shared, such as names and
details, and who made the last update.
To open the Manage Oracle Social Network Objects page, start on the Setup and
Maintenance Overview page and search for the Manage Oracle Social Network Objects
task.

Enablement Options
The following enablement options are available for enabling social

network objects on the Manage Oracle Social Network Objects
page:
Manual
Automatic
No
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r s f er
ath(Recommended)
a
Manual:
h with t r a n Lets users decide whether to share each instance of the
Bobject - the social network. When shared, all updates to the enabled attributes of the
non appear on the social network. If the instance is deleted, that information is also
instance
shared.
Note: Click Enable All to enable all objects for all applications. Enable All automatically
applies the Manual option, which means that the user can choose whether to share an
object instance.
Automatic: Notifications about all instances of the object appears on the social network,
including:
- Every newly created instance
- All subsequent updates to the enabled attributes
- Deletion of any instances
No: (Default value) No notifications about the object appears on the social network.
Note: When you click Disable Object, the enabled setting of the selected business
object is automatically changed to No.

Enablement Options
After you enable an object, you must enable one or more

attributes of the object.
Only the enabled attributes are shared.

The Status column in the Business Objects table indicates
which enabled business objects have or do not have enabled
attributes.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r athobjects s f er
h a
For business
t r a n with no enabled attributes, only the following information appears on the
B n-
social network:
n o
Internal bookkeeping information when you create or update an instance of the object.
News that an instance is deleted.

Update Translations
Use Update Translations on the Manage Oracle Social Network

Objects page for subsequent updates to labels and attributes.
s a
a
)h
For example, if a new language pack is installed in Oracle m
co uide
e
Applications Cloud, click Update Translationshtop sendGthe
r@network.
e n t
updated labels and their translations to social a
k u m Stud
d d y- this
t h re use
a r a e to
e dd ble l
t h R ra
a r
Use Update n s fe at the:
aTranslations
Bh n-trObjects
Business
a
table level to send translations for a selected business object to social
no
network. This button is enabled only when you select a row for a business object with
the enablement option as Manual or Automatic.
Manage Oracle Social Network Objects page level to send translations for all business
objects with the enablement option as Manual or Automatic to social network.
Note: When you save the enablement of a business object, Update Translations sends the
translations. You dont need to click Update Translations after saving the enablement.
When you click Update Translations, you:
Send translations for all business objects with enablement as Manual or Automatic to
social network.
Synchronize the newly translated text from Oracle Applications Cloud so that it can be
used within social network. This means that you can:
- Install and enable a new language.
- Take a language patch at any time.
Send attribute labels and business object names to social network for use in its user
interface.

Update Translations
Note
In social network, the attribute or business object labels
appear in the language of your locale. If you change the

locale, then these labels appear in the updated language.
The data appears in the language in which it was originally
sent to social network.
If you have previously sent an instance of the business object
to social network, then the instance data is not updated even a
when you click Update Translations. a s
)h
c om ide
h pe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Practice A-1: Managing Oracle Social Network Objects
Demonstration
This demonstration covers the following topic: Enabling Oracle
Social Network objects on the Manage Oracle Social Network
Objects page.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Oracle Social Network Reference Resources
Related Resources:
Oracle Fusion Applications Common Implementation Guide
https://osn-fusioncrm.oracle.com/osn/web/help/index.html?locale=en
https://cloud.oracle.com/mycloud/f?p=service:socialnetwork_faq:0
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Define Flexfields
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Manage Flexfields
To manage flexfields, use the Define Flexfields tasks in the Setup

and Maintenance work area.
A flexfield:
Provides a means to customize application features without
programming.
Extends a business object with additional data fields to
capture enterprise information.
Consists of segments representing different data or values. s a
a
)h
Stores data in database table columns, one for each m segment.
e
Appears to end users as attributes of information.
co uide
hp G
a r@ dent
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Types of Flexfields: Descriptive
Flexfield Type Description Examples

Descriptive Optional customizable Components of a student's

expansion space in the contact information.
user interface for Tracking asset specifics, such as
additional information. the number of floors, square
footage, and date of insurance
renewals.
Extensible Similar to descriptive A list of countries where an electronic
flexfields, but with item is compatible based on country-
advanced capacities a
specific standards such as power line
s
such as categories. a
frequency and item attributes such as
)h
signal resolution. m
Key Mandatory key for Unique item p e co uide
numbers.
identifying business Account @ h nt G
numbers.
entities using an Am
r
a tukey
composite dethat collates
enterprise-defined u Sprice, and shipping time.
-k location,
d y h i s
code.
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Flexfield Concepts
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r ath can s f er
A single
h a flexfield
t r a n capture multiple attributes, which you can display in the user interface as
B
fields. The n - shows several fields added to an order page by defining a part number key
figure
noand additionally a descriptive flexfield for capturing part type and sales
flexfield,
representative information.

Flexfield Segments
Represent attributes of entities (business objects)

Can appear:
Based on a structure or context.

Globally wherever the flexfield is implemented.
Can be made available to an application as groups of
attributes called contexts.
Can be assigned a value set that determines which values are
valid for the segment. sa ha
)
c om ide
h pe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
e
nsf that are defined to include a flexfield, some can accommodate
ara traobjects
Of thehbusiness
B nflexfields
descriptive - and others accommodate extensible flexfields or key flexfields, at the
noof application development.
discretion
Flexfield attributes are available across the deployment, such as in Web Services, Oracle
Business Intelligence, desktop integration with Application Development Framework, and
Oracle Fusion Search. Any UI page presenting the business object includes the flexfield
attributes that extend the business object. Oracle Business Intelligence reports include
flexfield attributes.

Flexfield Structure
A flexfield structure is:

Only relevant to key flexfields.
A specific configuration of key flexfield segments.

Composed of one or more instances each of which:
Contains the same number and order of segments.
Differ in the allowable values or value sets attached to the
segments.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Flexfield Context
A flexfield context is:

Relevant only to descriptive and extensible flexfields.
A grouping of attributes that makes segments available to an

application.
A set of context-sensitive segments that stores a particular
type of related information.
Note:
Descriptive flexfield segments can be context-sensitive.
s a
Extensible flexfield segments must be context-sensitive.
) h a
A way of reusing the same database columnpfor ideor
ca similar om
h e G u
r@ ent
different segment based on different needs.
a tud
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Flexfield Category
Relevant only in extensible flexfields.

A grouping of contexts.
A hierarchy of categories.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Flexfield Usage
Is set when application development registers the flexfield.

Specifies the application and table the flexfield is associated
with.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Accessing Flexfields for Configuration
To configure a flexfield, access it in one of the following ways:

Using the Highlight Flexfields command.
Accessing flexfield management tasks and searching for

flexfields.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Using the Highlight Flexfields Command
In highlight mode, you can use the:

Information icon to access details about the flexfield.
Configure the Flexfield icon to add segments and configure

them with advanced options on segments.
Add Global Segment icon to add global segments with
common options for descriptive flexfields.
Add New Context icon to add context values for descriptive
flexfields. s a
)h a
Add Context-Sensitive Segment icon to add context-sensitive
m
segments with common options for the selected o idevalue
ccontext
h e
p t Gu
of the descriptive flexfield. r@ en
m a tud
u
-k his S
d y
d se t
r e
a r ath e to u
e dd ble l
t h R ra
Use thea r
Highlight s fe command in the Administration menu of the Setup and
a nFlexfields
Bh n-work
Maintenance tra area to identify the location of flexfields on the run-time page.
no

Accessing Flexfield Management Tasks and Searching
for Flexfields
Use the flexfield management tasks in the Setup and
Maintenance work area. From the task list, search for Define
Flexfields on All Tasks tab.

Tip: Use the Business Object parameter to search Application
Key Flexfields, Application Descriptive Flexfields, and Application
Extensible Flexfields to find all tasks related to flexfields.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
Note har
ath nsfer
B ntasks
To access - trafor configuring flexfields and value sets, you must be provisioned with roles
no you to access the Define Flexfields task list or tasks for managing product-specific
that entitle
flexfields. Contact your security administrator for details. For information about product-
specific flexfield tasks, such as Manage Purchasing Descriptive Flexfields, consult the
product-specific documentation in Oracle Fusion Applications Help.

Accessing Flexfield Management Tasks and Searching
for Flexfields
To manage any flexfield across all Oracle Fusion Applications
products, search for the Define Flexfields task list and access the
following tasks:
Manage Descriptive Flexfields
Manage Extensible Flexfields
Manage Key Flexfields
After searching for and selecting the required flexfields, you can
use the Configure Flexfield icon to view and configure the s a
flexfields. )h a
c om ide
h pe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Value Sets
A set of values assigned to a flexfield segment or other entity

outside of flexfields.
The basis of validation for a value entered into a flexfield

segment by an end user.
Defined before you configure the key flexfield, because you
assign value sets to each segment when you configure the
key flexfield.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
Note:h aracantrcreate
You a n value sets when you create or edit descriptive and extensible flexfield
B
segments. n - you use the Add Global Segment and Add Context-Sensitive Segment icons
When
no Flexfields mode, value sets are created automatically when a segment is created.
in Highlight

Value Sets
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r
The figure
fe set being used for a descriptive flexfield segment.
ashows na svalue
Bh n-tra
no

Value Set Validation
Validation Types Description

Format only End users enter data rather than selecting values
from a list.
Independent The list of values consists of valid values you
specify.
Dependent A valid value in a list of values derives from the
independent value of another segment.
Subset The list of values is a subset of the values in an
existing independent value set.
s a
Table h a
The values derive from a column in an application
)
m
table, which can optionally be limited by a WHERE
o
clause.
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Value Set Usage
Specifies the segment where the value set is assigned.

Indicates which flexfields use a shared value set.
You can use value sets additionally for supplying values to

regular user interface fields, such as in Oracle Fusion Contracts.
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
ara tranhas
If yourhapplication more than one language installed, or you may install one or more
B -
additional languages for your application in the future, select Translatable. If you select
non you do not need to provide translated values now, but you cannot change this
Translatable,
option if you decide to provide them later.

Descriptive Flexfields
A descriptive flexfield:
Is often optional.
Provides a way to add custom attributes to entities and define

validation and display properties for custom attributes.
Is enabled for most business entities.
Consists of segments that are made available to end users as
individual fields in the application user interface.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Descriptive Flexfields: Segments
Correspond to custom attributes of entities.

Are generally standalone and need not be related or treated
together with other segments as a combination.

Are of the following types:
Global segment, which is always available.
Context segment, which determines the context-sensitive
segments that are displayed.
Context-sensitive segment, which is displayed depending ona
the value of the context segment. has
)
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Descriptive Flexfields: Context Segment
Need not be assigned a value set.

If assigned a value set, you can use only table-validated or
independent value sets.

Note
The data type must be character.
The maximum length of the values being stored must not be
larger than the column length of the context.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Descriptive Flexfields
The number of segments available for configuring is determined

by the number of columns reserved by application development to
store segment values. During implementation, determine which

attributes to add using the:
Available columns
Context values
Combination of attributes in each context
a
The same column can be used for attributes in different contexts,
s
such as Height in Context1 and Color in Context2. )h a
c om ide
h pe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
For eacha r a and
global n s fe
context-sensitive segment, you configure the values allowed for the
B h
segment and t r a
-how the values that are entered by end users should be validated, including
non validation among the segments.
interdependent

Adding Flexfield Segments on Application Pages
For adding segments and configuring them with advanced options

on segments (such as change a segments sequence number, or
configure a descriptive flexfield segments business intelligence

label), use the Configure Flexfield icon.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

To configure segments with common options, use the following

icons on an application page where descriptive flexfields are
highlighted:
Add Global Segment: To add global segments for descriptive
flexfields. Global segments are always relevant, irrespective of
context values.
Add New Context: To add context values for descriptive
flexfields. a
Add Context-Sensitive Segment: To add context-sensitive a s
m )h
e co uide
segments for the selected context value of the descriptive
flexfield. hp t G
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a
The rcontext s fe immediately precedes the Add New Context icon.
a nsegment
Bh n-trathat you add using the Add New Context icon appear in the drop-down list of
Theovalues
n context segment after you refresh the page.
the
You must select a context value from the context drop-down list, and then use the Add
Context-Sensitive Segment icon to add a segment specific to that context value.
You must sign out and sign in to the application again to view the changes you make
using the following icons:
- Configure Flexfield
- Add Global Segment
- Add Context-Sensitive Segment

When you use the Add Global Segment and Add Context-
Sensitive Segment icons:
You must accept the automatically set:

Segment code
Name and description
Table column
Sequence number
You must accept the automatically created value set. s a
h a
You can enter valid values, including: m) c o ide
Valid values descriptions
pe t Gu
h
The default value a r@ den
Formatting constraints for the value - k umset, S tu as minimum and
such
maximum values e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a
Dependingr s fe type, the value set created by the Add Global Segment and Add
aon thendisplay
Bh n-tra Segment icons is one of the following value sets:
Context-Sensitive
An noindependent value set
A format-only value set

The following table shows which type of value set is created

depending on the display component you select:
Display Component Type of Value Set
Check box Independent

Drop-down List
List of Values
Radio Button Group
Pop up List of Values
s a
h
) a
o m
Text Box
Text Area
Format Only
p e c uide
Date and Time @ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Extensible Flexfields
Extensible flexfields are like descriptive flexfields, with some

additional features.
With extensible flexfields, you can:

Have multiple groups of custom attributes attached to a single
entity. Each group of custom attributes is a context. In
addition, different entity rows can have different groups of
attributes (or contexts) based on the value of the category.
This is in contrast to descriptive flexfields for which the a
attributes vary based on the context. a s
m )h
co uideas
Add as many context-sensitive segments to theflexfield
e
you need. You are not limited by the number
@ hpof segments
n t G
r
ma tude
predefined and registered for the flexfield.
ku is S
d y -
r e d e th
r a th to us
( b ha nse
R e able
a r ath nsfer
Bh n-tra
no

Configure a one-to-many relationship between the entity and

its extended attribute rows.
Configure attributes in contexts, which serve as groups of

attributes. Attributes in a context appear together in the user
interface.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Extensible Flexfields Context
Can be defined as single-row, meaning a one-to-one

relationship between the entity and its extended attribute
rows.
Can be defined as multirow, meaning a one-to-many
relationship between the entity row and its extended attribute
rows.
Can be set to store translatable free-form text values.
Is reusable throughout extensible flexfield categories. a
h a s
m )
o
c uide
p e
h nt G
r @
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

An extensible flexfield category enables you to:

Use the category value (that each entity row has) to determine
which attribute groups (contexts) apply to the row.

Assign different combinations of contexts to different categories
to capture different information about different entity rows.
An extensible flexfield page:
Combines contexts into a group that is presented together in
the application user interface.
a
Corresponds to one extensible flexfield category, with ahas
separate section of the page for each associated o m)
context.
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
Note har
a nsfe
B n-tra flexfields, you can define categories in a hierarchy. When you use
For someoextensible
n categories, the entity displays attributes from contexts that are:
hierarchical
Directly associated with the category
Defined in parent categories of the category

Extensible Flexfield Example
You can specify whether end users can enter one set of data or
multiple sets of data for a context.
For example, if you have a job positions entity that stores

information about different positions in your organization, you can
configure additional contexts that store a list of requirements for
that position.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

To start with, the job positions entity includes fields for the
following attributes:
Position ID
Position code
Description
Department
Location
Hiring status s a
h
) a
Whether the job is permanent or temporary o m
p e c uide
Whether the job is full-time or part-time h tG
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

You then can extend the list of job positions to capture the
following classes of attributes:
Educational requirements, such as degrees

Certifications and licenses required for the position
Travel required for this position
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r th sfer
athis
h a
Implement
t rby
a nsetting up context values corresponding to each group of custom attributes.
B
Setting up n - values means specifying segments for each context, such as various
context
degreesnoin an educational requirements context and various credentials in a certification and
license requirements context. You set up a job position category that contains the three
contexts for the three classes of attributes you want to capture, and set up a page for that
category.

s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
ara create
Whenhusers
t r a na job in the job positions category, they see the additional attributes.
B
When users -define job position requirements, they select the education level, credentials, and
non by the position.
travel required

Key Flexfields
A key flexfield:
Provides a means of capturing a key, such as a part number,
a job code, or an account code that represents an entity in

your application.
Consists of one or more segments, where each segment can
have a meaning.
Is not optional and must be configured to ensure that your
applications operate correctly. a
a s
) h and
Is provided by applications development and is configured
m
o ide
ec
maintained with the Manage Key Flexfields task.
h p t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Key Flexfields
Have one corresponding combinations table containing the

complete codes or combinations of segment values that make
up the codes.
Can be used in different ways on different pages:
Combination maintenance page, where users maintain
individual combinations directly.
Foreign key page, where users manipulate rows containing
code combination IDs (CCID).
Partial usage page, where users may be presented withhonlya sa
m )
parts of the configuration based on a products transaction
o
c uide
table. pe
h nt G
r @
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Key Flexfield Structure
Defines the following segment options:

What segments to include
Number of segments
Segment sequence
Segment labels where applicable, for example, natural account
and primary balancing in general ledger
Value sets
Sets the maximum number of segments allowed in your keya
flexfield combinations table. h a s
m )
Allows one or more alternate structure instances o ide
cthatucan
p e
h nt G
have different value sets. @
r
a segmentde values when
Includes a delimiter to visually separate
u m S t u
the key flexfield is displayed dindy
-k hisinterface.
the user
t
t h re use
a r a e to
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Key Flexfield Instances
All key flexfield structure instances:

Contain the same:
Set of segments
Arrangement of segments
Properties at the segment and structure levels
May differ in whether dynamic combination creation is
allowed, which means a new valid combination is inserted into
a combinations table from a page other than the combinationa
a s
maintenance page. )h
c om ide
h pe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Key Flexfields
Key flexfield segment instances in a key flexfield structure

instance may differ in the following aspects:
Value set
Default type and default value
Tree code defining a hierarchical relationship to other
segment values of a key flexfield registered with a tree
structure
Whether the segment is any of the following: s a
h
) a
Required m
Displayed
o
c uide
p e
h nt G
Enabled for business intelligence a r @ e
um Sintua dkey flexfield
Optional or required as a query-kcriterion
combination search e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Key Flexfields
The predefined key flexfields are:

Account Alias Flexfield
Accounting Flexfield
Asset Key Flexfield
Budgeting Flexfield
Category Flexfield
Cost Allocation Flexfield
s a
Item Categories h
) a
Location Flexfield o m
p e c uide
Locator Flexfield @ h nt G
r
a tude
People Group Flexfield u m
d y -k his S
Valuation Unit Flexfield red et
r a th to us
( b ha nse
R e able
a r ath nsfer
Bh n-tra
no

Tips for Managing Key Flexfields
When you configure a key flexfield, define metadata about the

key flexfield, such as how many segments are in a structure,
how many structures the flexfield uses, and what value sets
each segment uses.
For example, you can use one group of value sets for the US
and another for France.
You must add segments in the order that your key requires.
After they are deployed, the order cant be changed.
s a
If you change the configuration of a key flexfield, such as athe
)h
delimiter, the change affects the previously stored m
key
co uide
e
flexfields with that structure.
@ hp nt G
Enable segments to indicate that they r in use
aare de and appear
k u m S t u
at run time.
e dy- his
d se t
r
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Tips for Managing Key Flexfields
Dont change the number, order, and maximum length of

segments after you have acquired flexfield data.
To protect the integrity of your data, disable a segment if you

have already used it to enter data.
You can dynamically create account code combinations when
entering data by enabling dynamic insertion on the Key
Flexfield Instance page.
At any time, enable or disable allowing dynamic combinationa
creation. h a s
m )
o
c uide
Define cross-validation rules to ensure that theedynamic
combination creation process doesnt create
p
h incorrect
t G account
r @
a tude n
combinations. um
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Flexfield Implementation Flow
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a
Managing rflexfields
fer registering, planning, configuring, and deploying flexfields.
ath nsinvolves
Bh n-developers
Applications tra develop and register flexfields. Administrators and implementors
noflexfields and optionally customize their appearance in the user interface.
configure

Flexfield Implementation Flow
There are two types of deployment:

A sandbox-enabled flexfield for testing flexfield behavior in a
sandbox MDS repository that is accessible only to the

administrator who activates and accesses it, not to users
generally.
A mainline-enabled flexfield for applying the flexfield definition
to the mainline MDS repository where it is available to end
users. a
a
After deploying the flexfield to the mainline, you can customize
s
m )h
the page where the flexfield segments appear. co de
pe t Gui
h
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Flexfield Reference Resources
Related Resources:
Oracle Fusion Applications Implementing Common Features
Oracle Applications Cloud Extending the Applications

Oracle Fusion Applications Developer's Guide
To view flexfields in the Oracle Enterprise Repository, see
https://fusionappsoer.oracle.com/oer/.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Define Lookups
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Sample Lookup Type
Lookup Type Lookup Code Meaning Tag Enabled

TICKET_CLASS ANY Any class Any

depending
upon
availability
BUSINESS Business Business

class
s a
FIRST First class First a
) h
m
o ide
Economyec
ECONOMY Economy
h p t Gu
class
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
Per the a r a shown
settings n s fein the table, users would see the following values in the list on the
Bh nUI-ttoradetermine the ticket class:
application
Any no
Business
Economy

Lookup Components
Lookup Type: A static list of values that users use to make

entries in the application.
Lookup Code: An internal application code for each lookup

that is not visible to users.
Meaning: The actual UI term that appears in the lookup list of
values.
Tag: A label associated with the lookup.
Enabled: A status that determines the availability of the s a
meaning within the selection list for the lookup type. ) h
a
c om ide
h pe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r
Lookup
a Type:
n s fe is the name of the field that appears on the setup UI and not on the
This
h -traUI where you make the selection.
Bapplication
non The actual UI term associated with the lookup code. It is the item that appears
Meaning:
in the list on the application UI against the specific field name, and can be selected by
users to indicate their choice.
Tag: Certain product offerings use lookup tags for functionality that is specific to that
product. Refer to the product offering specific documentation for more information. If no
such use of tag is documented, the tag is ignored.
Enabled: If you do not enable it, the value does not appear in the selection list at run
time.

Lookup Categories
Standard Lookups: Consist of lookup codes and their

meanings.
Common Lookups:
Available for internal system administrative use.
Used by more than one application.
Set-Enabled Lookups: Contain lookup codes that are part of a
reference data.
Use sets to enable various values in the lookup for different a
sets of users. h a s
m )
Select an attribute at run time to determine which o ide
c set-enabled
h p e u
lookup is visible to the users. tG
r@ den
a
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
Ana r a nofsfaeSet-Enabled Lookup: The attribute east-coast or west-coast in the
example
h -tdeterminant
Blocation ra determines whether it is the east-coast or the west-coast location,
no n
depending on the selected lookup.
Lookup codes and their meanings are valid within a specified date range. If a date range
is not specified, the lookup codes and meanings have indefinite validity from the time
they are created.

Manage Lookups
Define the three types of lookups in:

Standard view
Common view
Set-enabled view
Lookups are:
Enabled
Associated with a module
Striped by application taxonomy to provide a criterion for s a
ha
narrowing a search or limiting the number of lookups accessed
)
c om ide
by a product-specific task such as Manage Purchasing
Lookups hpe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
You can a r a new
create n s fe types and also add new lookup codes and meanings to the
lookup
Bh lookup
existing n - a depending on the access permissions granted to you. But for the
trtypes,
o lookup values to appear as values in the lists, they need to be enabled.
lookupsnand
To enable a lookup type, you need to enable at least one of its lookup codes and that
code must be in a valid date range.
By default, most lookup types are enabled at the time of deployment. You can disable
the ones that you do not require.
Note: Applications development can define lookups in an application view to restrict the UI
pages where they appear.
Navigate to:
Setup and Maintenance > All Tasks > Search > Enter Define Lookups in the
Name field > Search > Expand > Manage Standard Lookups
Name field > Search > Expand > Manage Common Lookups
Name field > Search > Expand > Manage Set Enabled Lookups

Customize Lookups
Based on the defined customization levels.

Restricted to the extent to which customization is allowed.
The following levels of customization are defined:

User: Create or modify all parameters of a lookup type.
Extensible:
Modify only certain aspects of the lookup type such as the dates.
Add new lookup codes.
Cannot delete the lookup type. a
System: h a s
m )
o
c uide
Cannot add or delete any aspect of the lookup type.

Modify only its meaning. p e

h nt G

r @
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Define Profile Options
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Define Profile Options
In this section, you will learn key concepts about:

Profile Options
Profile Option Categories

Profile Option Levels and Values
Profile Options for Common Setup
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Profile Options
Profile options are global configuration settings that users can

modify to change the way an application works.
For example, settings such as user preferences and application

configuration parameters can be modified per the users
requirements.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a
You can r
use
fe to modify:
a profilensoptions
Bh n-trand
Theolook
a
behavior of the application's user interface

n
User preferences such as settings used for social networking
The business logic of the application
Log settings and processing options that determine how and where information is stored
A profile option consists of:
Name
Application and module
Values
Categories and Hierarchy level
You can modify any of these constituents of the existing profile options, but system
administrators must have enabled the profile option for modification.
The use of profile options is guided by the functional requirements. To determine which profile
options to use in the implementation project, refer to the product offering-specific
documentation.

Profile Option Categories
Profile options are grouped into categories depending on the

functional area in which the profile options are used.
Profile option categories facilitate searching and defining data

security.
A profile option can be grouped into more than one category.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r athin Oracle
s f er
h a
For example,
t r a n Fusion Receivables, the Transactions profile option category groups
B n- that are related to Receivables transactions processing, such as:
the profile options
n o
Require Adjustment Reason
Invoices with Unconfirmed Receipts
Use Invoice Accounting for Credit Memos

Profile Option Levels
In an application, the display and availability of profile options

depends on the hierarchy level at which it is enabled.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r athlevels
s f er
a
h -tran
The hierarchy are:
B
n n accessibility to all users of the application across the deployment site. In a
Siteolevel: The lowest level of hierarchy (unless superseded by any other level) that
provides
multitenant environment, Site is scoped per tenant.
Product level: The next level in the hierarchy that applies to the selected product family
(product offering within Oracle Fusion, such as Financials) and its specific users. For the
same user, the profile option at this level supersedes any site level profile option setting.
User level: The highest level in the hierarchy that applies to the specific user or user
role. Also, it supersedes any product or site level setting that was defined for that user.
Note: Profile options defined at higher levels override the profile options at the lower level.
Profile values determine application behavior at a specific selected level. Contexts, such as
user session or accessed product, determine which profile option value is associated with the
profile option name.
The following example of the AFLOG_LEVEL profile option shows how the profile values
determine application logging at various levels.

Profile Option Values
Profile values determine application behavior at a specific

selected level. Contexts, such as user session or accessed
product, determine which profile option value is associated with

the profile option name.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r athof the s f er
h a
This example
t r a n AFLOG_LEVEL profile option shows how the profile values determine
B -
applicationnlogging at various levels:
Siten o
- Profile option value: Severe
- Effect: Log activities at the site level indicating failures within the environment
- Result: Only administrators are notified
Product/Product Family (CRM/SCM)
- Profile option value: Warning
- Effect: Log activities that are specific to the product family
- Result: Administrators and product-specific implementation consultants are
notified
User (Bob)
- Profile option value: Info
- Effect: Log activities pertaining to user actions such as invalid user name or
password, or account locked out
- Result: Administrators, implementation consultants, and users are notified

Profile Options for Common Setup
You can set up a common profile option, such as logging, which

applies to the entire applications suite.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r th sfer
alogging
h a
By default,
t r a nis set to SEVERE at the Site level. To diagnose or troubleshoot any
B
problem, set -logging to FINEST at the User level for a particular user so that you can examine
ondetail.
the logsnin
As a result, actions of that particular user are captured in the finest level possible. The benefit
of this setting is that it does not affect other users and does not impact logging or performance
at the Site level.
Another example could be the use of the profile option FND_SERVER_TIMEZONE to record
the time zone of the database instance. The selected profile value and the hierarchy level at
which the profile option is set determines the time stamp on all the transactions performed on
that server. Usually, such profile options are applied only at the site level because of their
universal impact.
You can find these profile options under the Manage Profile Options task on the Setup and
Maintenance Overview page.

Quiz
Q
For a profile option, if you set the hierarchy level for both
site and user, the site level hierarchy takes precedence
over the user level hierarchy.

a. True
b. False
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
Answer:abr a nsfe
Bh n-tra
no

Define Attachments
This section describes the tasks in the Define Attachments task

list:
Manage Attachment Entities

Manage Attachment Categories
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
Navigatea r ath nsfer
to:
Bh nand
Setup - traMaintenance > All Tasks > Search > Enter Define Attachments in the Name
no> Search > Expand > Manage Attachment Entities
field
Setup and Maintenance > All Tasks > Search > Enter Define Attachments in the Name
field > Search > Expand > Manage Attachment Categories

Define Attachments
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Key Concepts
Attachments are:
Pieces of supplementary information that users can associate
with specific business objects. For example, users might

attach receipts to expense reports.
URLs, desktop files, or text.
Stored in a content server.
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
ara tranare
Whenhattachments stored in the Oracle Enterprise Content Management document
B
repository, n - can select folders or files from the repository as attachments.
users
n o
Attachment entities
Identify the business object that attachments can be attached to.
Are typically named after the primary table or view used to store information about the
business object.
Attachment categories
Classify attachments. For example, when users add an attachment to an expense
report, they can select a category to indicate whether the attachment is a receipt, travel
itinerary, and so on.
Can optionally be used to restrict access. For example, users with a specific role are not
given access to one of the expense report attachment categories, so they cannot select
it when adding attachments to their reports. They also cannot see any attachments
assigned to the category.
Are assigned to attachment entities so that each category is tied to the relevant
business objects.
Note: Each attachment entity must have at least one assigned category. Otherwise, users
cannot add attachments for the corresponding business object.

Key Concepts
The UIs across Oracle Fusion Applications facilitate adding

attachments, where applicable.
Depending upon the roles and access levels, you may view,
add, update, or delete attachments.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
ara trisanot
Wherehaccess n granted, users cannot view any attachment. For example, if a user does
B
for the n on- report.
not have access
expense
to a specific expense report, then the same user cannot access attachments

Manage Attachment Entities
Attachment entity is a database entity a table or a view.

An attachment entity represents business objects with which
the actual attachments can be associated.

You can either use the predefined entities or create new ones.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
Ana r
attachment
fer name should match the name of the table or view that represents
ath nsentity
h business
Bthe - tra object to attach to. The name is also used in the repository folder that is
no n
automatically created to store attachments for the entity.
The attachment entity display name should be something that users know to represent
the business object.

Attachment UIs for users to add or manage attachments are fully

functional and do not require setup.
Predefined attachment categories are already assigned to

attachment entities.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
For your a r
changes
fer in attachment UIs for users, the users must sign out and sign in
ath ntosappear
Bhto clear
again n - ra cache for categories. If your new categories are still not displayed, then the
tthe
o
specificnattachment UI likely has predefined restrictions on categories in place. Check with
your administrator or help desk.
Note: The Manage Attachment Entities task can also be used to assign categories to entities.
You do not need to use this page unless you are performing additional or technical
configuration.
If an entity has only one category, then:
All attachments added for the corresponding business object are automatically assigned
to that category.
The Category attribute is hidden in the UIs where users add or view attachments for the
business object.

Create new attachment categories as needed and assign to

relevant attachment entities.
Remove the association of categories with specific entities.
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r th sfer
acreating
Example a
h -tran new attachment categories
of
B
create n
on wants to identify attachments that fulfill a specific fiscal requirement. You can
Your company
a new category and assign it to all attachment entities representing business objects
that are relevant to the requirement.
Example of removing the association of categories
A predefined category is not relevant to any of your users for certain business objects, so you
remove its association with those objects.

Attachment Category Security
You or a technical administrator can implement data security on

attachment categories to determine:
Which categories users can access when adding attachments.

What actions they can perform on attachments assigned to
those categories.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
ara trancategory
For anhattachment or set of categories, assign one or more of the privileges to roles.
B - the Oracle Fusion Applications Developer's Guide.
For details,nsee
n o
After the security rules are in place, you or your technical administrator can use the Security
Enabled check box on the Manage Attachment Entities page to enable this security for
specific attachment entities.
Note: If security is enabled for an attachment entity before any data security rules are in place
for a particular category, then that category will not be visible to anyone until rules are in place
or security is disabled.
In some cases, data security for categories is predefined. For example, predefined
attachment categories are available for suppliers and receivers. Both types of users can go to
the same page with an attachment UI, but see only the categories that they can access based
on security.

Attachment Category Security
Each action is captured by predefined privileges:

Read: Read Application Attachment
(FND_READ_APPLICATION_ATTACHMENT_DATA)
Update: Update Application Attachment
(FND_UPDATE_APPLICATION_ATTACHMENT_DATA)
Delete: Delete Application Attachment
(FND_DELETE_APPLICATION_ATTACHMENT_DATA)
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r
For example, n s fe Report attachment entity currently has three attachment
a the Expense
Bh n-tra
categories:
no
Receipts
Missing Receipts Declaration
Travel Itinerary

Example
You need to track the mileage of cars that belong to your

company.
Your users record miles traveled in a log book, scan the

relevant page, and attach the image file as part of their
expense reports.
The clerks handling the corporate fleet vehicles need to see
these attachments, but should not view the other types of
attachments for expense reports. The managers of users a
submitting the expense reports can view all categories.has
m )
o
c uide
p e
h nt G
r @
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Solution
To implement this security:

Use the Manage Attachments Category page to create a
Mileage attachment category and associate it with the

Expense Report attachment entity.
Define data security so that the role for the clerk can see only
the Mileage category, while the role for the manager can see
all categories.
Select the Enable Security check box on the Manage a
Attachment Entities page for the Expense Report entity. a s
)h
c om ide
h pe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Quiz
Q
Attachment categories are assigned to specific attachment
entities:
a. So that the categories are available for the relevant business

objects.
b. Because these are the entities with the Enable Security check
box selected.
c. Only on the Manage Attachment Categories page.
d. All of the above. sa ha
)
c om ide
h pe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
Answer:aar a nsfe
Bh nnot-trassign
a
no
You would categories to security-enabled entities. Security is optional.
You can also assign categories to entities using the Manage Attachment Entities page.

Quiz
Q
Attachments can be created without an assigned
attachment category.
a. True
b. False
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r ath sfer
Answer: a
h b -tran
B
on must have an assigned category. Even if the attachment entity has only one
All attachments
n
associated category, attachments are automatically assigned to that category and the user
does not see a field to select a category.

Summary
In this lesson, you should have learned how to:

Manage Oracle Social Network Objects.
Define Flexfields.
Define Lookups.
Define Profile Options.
Define Attachments.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

D96139GC10 Appendix A

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

D96139GC10 Appendix A

Uploaded by

Copyright:

Available Formats

A

After completing this lesson, you should be able to:

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 2

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 3

The following enablement options are available for enabling social

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 4

After you enable an object, you must enable one or more

Only the enabled attributes are shared.

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 5

Use Update Translations on the Manage Oracle Social Network

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 6

appear in the language of your locale. If you change the

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 7

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 8

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 9

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 10

To manage flexfields, use the Define Flexfields tasks in the Setup

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 11

Flexfield Type Description Examples

Descriptive Optional customizable Components of a student's

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 12

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 13

Represent attributes of entities (business objects)

Based on a structure or context.

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 14

A flexfield structure is:

A specific configuration of key flexfield segments.

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 15

A flexfield context is:

A grouping of attributes that makes segments available to an

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 16

Relevant only in extensible flexfields.

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 17

Is set when application development registers the flexfield.

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 18

To configure a flexfield, access it in one of the following ways:

Accessing flexfield management tasks and searching for

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 19

In highlight mode, you can use the:

Configure the Flexfield icon to add segments and configure

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 20

Flexfields on All Tasks tab.

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 21

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 22

A set of values assigned to a flexfield segment or other entity

The basis of validation for a value entered into a flexfield

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 23

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 24

Validation Types Description

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 25

Specifies the segment where the value set is assigned.

You can use value sets additionally for supplying values to

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 26

Provides a way to add custom attributes to entities and define

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 27

Correspond to custom attributes of entities.

together with other segments as a combination.

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 28

Need not be assigned a value set.

independent value sets.

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 29

The number of segments available for configuring is determined

store segment values. During implementation, determine which

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 30