You are on page 1of 102

Flex Fields

Priya Holkar||20-Sep-2011

Introduction and Concepts Setup and Usage Benefits of using Flex Fields. Some Technical Aspects.

Contents
 Requirements and Solution.
 Overview of Flex Field.
 Types of Flex Fields  Basic Flex Fields Concepts.

 Key Flex Fields in Detail.  Descriptive Flex Fields in Detail.  Validations, Value Sets and Structures*.  Using Advanced Validation Capabilities*.

Overview of Flex Fields
 Fields which provide capability to capture Validated,

Structured and Well-Defined set of Data.
 Fields which can customize an Application to suit

Specific business needs Precisely.

Types of Flex Fields
 The Key Flex Fields (KFF). • Capture Key Data which is Integrated with Internal Processing of Applications.  The Descriptive Flex Fields (DFF). • Capture Additional Information and Provide Expansion Space In Data Capture Process.

KFF and DFF

Basic Flex Fields Concepts  Segments  Value  Validations  Value Sets  Structure .

A Segment is represented in the database as a single table column. .A segment is a single sub–field within a Flex Field.

.Values are the data Entered into the Segments of a Flex Field.

.Validations are the Tests in which Data appear before entering into the Segments.

Value Sets are the Sets of Predefined Values for a Specific Segment Validation. .

.Valid Combination of Various Segments in a Flex Field Creates a Structure of Flex Field.

Working with Flex Fields  Flex Fields Segments  Structure of Flex Fields  Segment Prompts and Value Descriptions  Values  Various Value Sets .

Structure .

Prompts and Value Description. .

Validation With Value Sets .

Some Application KFF Examples Detail Discussion Related to KFF FF Qualifiers and Optional KFF Features .

Some Application KFF Examples .

Detail Discussion Related to KFF  KFF as Intelligent Keys  The Dual Purpose of KFF  Implementation of KFF • KFF Structures • KFF Code Combinations • Storing Code Combinations and CC Tables • Flex Field Qualifiers  Segment Qualifiers  Technical Aspects .

Other KFF Options  Dynamic Insertion of New Values  Cross Validation of Segment Value Combinations  Security on Values Accessible  Aliases to Speed Entry of Frequently Used Value Combinations. .

KFF as Intelligent Keys .

.  Key Flex Fields Can Be Used As Intelligent Keys as It Capture Meaningful Information In Segments.  Each Part Contains Meaningful Information.KFF as Intelligent Keys  Intelligent Keys are Multipart Key Values.

.  Provide Users with Ability to Customize Structure and Appearance.The Dual Purpose of KFF  Collect Key Information About the System Required for Application’s Internal Processing.

.  One KFF can have Multiple Structures Depending upon the Specific Needs.KFF Structure…  Combination With Logical Sequence of Various Segments of KFF Provides KFF Structure.  Different Business Entities Have Different Structures.

KFF Structure .

.  For Example Oracle General Ledger Determines which Accounting FF Structure to Use From the Profile Option* Set of Books. Application Generally Determines The Correct Structure With Which to Work.KFF Structure  With Multiple Structures For a KFF.

The KFF Qualifiers  Allow User to Customize the Flex Fields As per the Requirement AND  Allow Application to Find the Information it Needs for Processing. .

Types of Qualifiers…  Flex Field Qualifier .To Identify a Value in Segment .To Identify a Segment in Flex Field  Segment Qualifier .

Types of Qualifiers .

 They work as a WHERE Clause in SQL Statement.  Play Vital Role at the Time of Internal Processing to Filter out Records. Posting or Summary.Segment Qualifiers  Identify Value Stored in the Segment of Flex Field for a Predefined Operations Like Budgeting. .

Segment Qualifiers .

Dynamic Insertion Cross-Validations Security Aliases .

.The Accounting Flex Field.

KFF Code Combination .

.Storing Code Combinations…  Each KFF Stores its Code Combination In a Database Table Called a Code Combination Table. Example: GL_CODE_COMBINATIONS  In Code Combination Table There is One Column For Every Flex Field Segment.

 The Information of CC Table is Stored in apps. .Storing Code Combinations…  Each Row In the Combination Table is Identified by a Unique ID called Combination ID Which is Stored in a Unique ID Column. there is one Structure ID Column.fnd_id_flexes Table.  For KFF having Multiple Structure.

application_table_name apps.fnd_id_flexs application_id.Storing Code Combinations…  Names of All CC tables can be queried through: - SELECT FROM ORDER BY id_flex_name . .

Storing Code Combinations .

A Code Combination Table .

Storing Code Combinations .

 The Values can be Entered in KFF only through Regular Window of KFF. New Values can be entered into KFF from Other Forms too.  Using Dynamic Insertion Option (As allowed). .Dynamic Insertion…  KFF are Used at various Forms in Applications.

Dynamic Insertion .

The Security Rules  Cross Validation – Check for Valid Combinations for Multi-Segment KFF to Control Data Integrity. .  Value Security Rule – Check For Valid Data Entry for Independent Segment as Per the Value Security Rule.

Cross Validation Rules .

Value Security Rules .

 Allow users to enter data faster and more easily with shorthand aliases.  An alias is a label for a particular combination of key Flex Field segment values.Short Aliases.. .

Short Aliases .

Implementation of KFF…  Identify the target Flex Field.  Define the Key Flex Field Structure. .  Plan the Flex Field Structure Behavior and Appearance. The Information Required by Oracle Application  Plan if Any Qualifier required.

Define Cross Validation Rules When Appropriate.Implementation of KFF     Define Any Value Set Required and Their Values.* Define Security Rules When Appropriate. Define Shorthand Aliases When Appropriate .

 Primary Key Column: • APPLICATION_ID .KFF – Technical Aspects  fnd_application • This table stores information about all of the applications registered with Oracle Application Object Library.

and a description.  Primary Key Column:  APPLICATION_ID  TABLE_ID .KFF – Technical Aspects  fnd_tables  This table stores information about the registered tables in your applications. Each row includes the actual table name (TABLE_NAME) a more descriptive title (USER_TABLE_NAME).

KFF – Technical Aspects  fnd_id_flexs • This table stores registration information about key Flex Fields.  Primary Key Column: • APPLICATION_ID • ID_FLEX_CODE .

KFF – Technical Aspects  fnd_segment_attribute_types • This table stores information about Flex Field qualifiers for key Flex Fields.  Primary Key Columns: • APPLICATION_ID • ID_FLEX_CODE • SEGMENT_ATTRIBUTE_TYPE .

KFF – Technical Aspects  fnd_flex_validation_qualifiers • This table stores information about Flex Field qualifiers and segment qualifiers.  Primary Key Columns: • • • • • FLEX_VALUE_SET_ID ID_FLEX_APPLICATION_ID ID_FLEX_CODE SEGMENT_ATTRIBUTE_TYPE VALUE_ATTRIBUTE_TYPE .

KFF – Technical Aspects  fnd_flex_value_sets • This table stores information about the value sets used by both key and descriptive Flex Fields.  Primary Key Column: • FLEX_VALUE_SET_ID .

 Primary Key Column: • APPLICATION_ID • ID_FLEX_CODE • ID_FLEX_NUM • APPLICATION_COLUMN_NAME • SEGMENT_ATTRIBUTE_TYPE .KFF – Technical Aspects  fnd_segment_attribute_values • This table stores the values of Flex Field qualifiers for particular segments of particular key Flex Field structures.

KFF – Technical Aspects  fnd_segment_attribute_types • This table stores information about Flex Field qualifiers for key Flex Fields.  Primary Key Column: • APPLICATION_ID • ID_FLEX_CODE • SEGMENT_ATTRIBUTE_TYPE .

KFF – Technical Aspects  fnd_id_flex • This table stores registration information about key Flex Fields.  Primary Key Columns: • APPLICATION_ID • ID_FLEX_CODE .

 Primary Key Columns: • APPLICATION_ID • ID_FLEX_CODE • ID_FLEX_NUM .KFF – Technical Aspects  fnd_id_flex_structures • This table stores structure information about key Flex Fields.

as well as the correspondences between application table columns and the key Flex Field segments the columns are used for.  Primary Key Columns: • APPLICATION_ID • ID_FLEX_CODE .KFF – Technical Aspects  fnd_id_flex_segments • This table stores setup information about key Flex Field segments.

KFF – Technical Aspects • ID_FLEX_NUM • APPLICATION_COLUMN_NAME .

KFF – Technical Aspects  fnd_shorthand_flex_aliases • This table stores alias information for shorthand Flex Field entry.  Primary Key Columns: • APPLICATION_ID • ID_FLEX_CODE • ID_FLEX_NUM • ALIAS_NAME .

 Primary Key Columns: • APPLICATION_ID • ID_FLEX_CODE • ID_FLEX_NUM .KFF – Technical Aspects  fnd_flex_validation_rule_stats • This table stores statistics on the number of key Flex Field cross–validation rules and rule lines for a given key Flex Field structure.

KFF – Technical Aspects  fnd_flex_validation_rules • This table stores information about key Flex Field cross– validation rules.  Primary Key Columns: • APPLICATION_ID • ID_FLEX_CODE • ID_FLEX_NUM • FLEX_VALIDATION_RULE_NAME .

 Primary Key Column: • RULE_LINE_ID .KFF – Technical Aspects  fnd_flex_validation_rule_lines • This table stores cross–validation rule elements for key Flex Field cross–validation rules.

KFF – Technical Aspects  fnd_flex_exclude_rule_lines • This table stores cross–validation rule elements broken out into individual columns for key Flex Field exclude rule lines.  Primary Key Column: • RULE_LINE_ID .

KFF – Technical Aspects  fnd_flex_include_rule_lines • This table stores cross–validation rule elements broken out into individual columns for key Flex Field include rule lines.  Primary Key Column: • RULE_LINE_ID .

KFF – Technical Aspects  fnd_compiled_id_flex_structs • This table stores compiled information about key Flex Field structures.  Primary Key Columns: • APPLICATION_ID • ID_FLEX_CODE • ID_FLEX_NUM • SEQUENCE .

KFF – Technical Aspects  fnd_compiled_id_flexs • This table stores compiled information about key Flex Fields.  Primary Key Column: • APPLICATION_ID • ID_FLEX_CODE • COMPILER_VERSION_NUM • SEQUENCE .

Typical DFF Information Examples DFF Components Implementation and Technical Aspects of DFF .

Which System Anyway Doesn’t Capture.  DFF Expand the Capability to Capture Data.The Descriptive Flex Fields  Descriptive Flex Fields (DFF) are used to Capture Additional Information. .  DFF are Optional Fields and Appear on Form as a Single-Space Field In Square Brackets [ ] without a Prompt.

The DFF on a Form .

Typical DFF Info. Examples  Payment Information  Credit Information  Distribution System Information .

Use Following Steps to determine the name of DFF on Form: Click On The Field. 2.The DFF Implementation…   1. Select Help->Diagnostics->Examine This Opens a Window Showing the Information of the Field. 3. . DFF are Not Labeled.

Note Down the name of the Block where DFF Appears. 6. 5.The DFF Implementation… 4. Click the Block List of Values Button to Display a List of available Blocks for this Form-> select $DESCRIPTIVE_FLEXFIELD$. . Click the Field List of values Button to Display a list of Descriptive Flex Fields for this Form.

Each Entry is Prefixed by the Name of The Block in Which the DFF Appears-> Find the Entries for the Block. . whose name is Found in Step-4 Select the DFF to be Implemented.The DFF Implementation… 7. 8. The User Name of DFF appears in the Value List.

The DFF Implementation  Determine the Available Resource With Following Steps:  Navigate through: Application-> Flex Field>Descriptive-> Segments  Use the list of Values for the Column Field in the Segment Summary Window to Determine How Many Segments can be Planned to Use. .

Components of DFF…  Global Segments –  Display Information Common to all Contexts  Context Sensitive Segments –  Display Information Appropriate to a Particular Contexts .

A Domain or an Area.Group of Relevant Information. .

Identifying the Information Grouping the Information Determine Different Contexts .

Identifying the Information  Store Number  Check Number  Credit Card Number  Expiration Date  Down Payment .

Grouping the Information:
 By Usage: • Finance
• Store Number Down Payment

• Check
• Store Number Check Number

• Credit Card
• Store Number CC Number Expiration Date

Isolate Common Information
 Information Used by All Tasks  Store Number  Information Vary by Tasks • Down Payment • Check Number • CC Number • Expiration Date

Determine Different Contexts
 Down Payment -> Finance
 Check Number -> Check  CC Number, Expiration Date -> Credit Card

A Segment that Contains Information which Global or Common to All Context. .

Segment For Global Information  Information Used by All Tasks  Store Number  Information Vary by Tasks • Down Payment • Check Number • CC Number • Expiration Date .

Global Segments .

Segment Which Contain Information That Very as per the Context . .

Context Sensitive Segments .

Distinguishing Between Context .

Components of DFF  Reference Fields  Fields on the Application Window whose Value is Used to Determine the Context  Context Field  A Field in the DFF Structure whose Value is Used to Determine the Particular Context .

DFF – Technical Aspects  Already Discussed Tables Along with KFF – Technical Discussion: • fnd_application • fnd_tables • fnd_flex_value_sets .

 Primary Key Columns: • APPLICATION_ID • DESCRIPTIVE_FLEXFIELD_NAME .DFF – Technical Aspects  fnd_descriptive_flexs • This table stores setup information about descriptive Flex Fields.

 Primary Key Columns: • APPLICATION_ID • DESCRIPTIVE_FLEXFIELD_NAME • COMPILER_VERSION_NUM • SEQUENCE .DFF – Technical Aspects  fnd_compiled_descriptive_flexs • This table stores compiled information about descriptive Flex Fields.

 Primary Key Columns: • • • • APPLICATION_ID DESCRIPTIVE_FLEXFIELD_NAME DESCRIPTIVE_FLEX_CONTEXT_CODE APPLICATION_COLUMN_NAME .DFF – Technical Aspects  fnd_descr_flex_column_usages • This table stores the correspondences between application table columns and the descriptive Flex Field segments.

DFF – Technical Aspects  fnd_descr_flex_contexts • This table stores context field values (also known as structure names) for descriptive Flex Fields.  Primary Key Columns: • APPLICATION_ID • DESCRIPTIVE_FLEXFIELD_NAME • DESCRIPTIVE_FLEX_CONTEXT_CODE .

 Primary Key Columns: • APPLICATION_ID • DESCRIPTIVE_FLEXFIELD_NAME • DEFAULT_CONTEXT_FIELD_NAME .DFF – Technical Aspects  fnd_default_context_fields • This table stores the names of form fields that users can use as reference fields for descriptive Flex Fields.

Advance Validation Capabilities  Using Table Validated Value Sets  Using Profile Option Values for Validation  Using Table Value from a Prior Field on a Form  Using Value From a Prior Value Set .

What is the Significance of Data Validations? . What is the Distinction between Flex Fields and Application Features? 2.1.

 http://www. • Oracle Applications Developer Guide.com  Oracle Application Documentation • Flex Fields User’s Guide • Applications Object’s Library (AOL) Technical Reference Manual.metalink. .oracle.References.

com .For any detailed discussion please email your queries to akhileshr@kpitcummins.

2704 Mail : .com .akhileshr@kpitcummins.Akhilesh Rajoria Ext : .

 @ n°nf¾½ n¾ XZV!_WYWZ`!S``^Ta`W!` \W_ Ð _`STW_`[^W_ZX[^S`[ZST[a` W  WV]aSXW^_ X[^W  W  WV_ ^S^  W [aZ Ð   .

!  Ð ! !.

 Ð   ! !  .

 @ n°nf¾½ n¾ XZV!V!XW Ð _`STW_`[^W_^WY_`^S`[ZZX[^S`[ZST[a`W  W  WV_ ^S^  W [aZ_ Ð   .

!  Ð ! !.

 .

 @ n°nf¾½ n¾ XZV!V!XW !_`^aU`a^W_ Ð _`STW_`[^W__`^aU`a^WZX[^S`[ZST[a`W  W  WV_ ^S^  W [aZ_ Ð   .

!  Ð ! !.

 Ð ! !  .

 @ n°nf¾½ n¾ XZV!V!XW !_WYWZ`_ Ð _`STW_`[^W__W`a\ZX[^S`[ZST[a`W  W  WV _WYWZ`_S_cWS_`WU[^^W_\[ZVWZUW_TW`cWWZ S\\US`[Z`STWU[aZ_SZV`WW  W  WV _WYWZ`_`WU[aZ_S^Wa_WVX[^ ^S^  W [aZ_ Ð   .

!  Ð ! !.

 .

 @ n°nf¾½ n¾ ! !  Ð   .

!.

 !   Ð .

 @ n°nf¾½ n¾ XZV!_[^`SZV!XW !SS_W_ Ð _`STW_`[^W_SS_ZX[^S`[ZX[^_[^`SZV W  WVWZ`^  ^S^  W [aZ_ Ð   .

!  Ð ! !.

 Ð ! !  Ð  !   .

 @ n°nf¾½ n¾ XZV!XW !bSVS`[Z!^aW!_`S`_ Ð _`STW_`[^W__`S`_`U_[Z`WZaTW^[XW  W  WVU^[__ÊbSVS`[Z^aW_SZV^aWZW_X[^SYbWZW  W  WV_`^aU`a^W ^S^  W [aZ_ Ð   .

!  Ð ! !.

 Ð ! !  .

 @ n°nf¾½ n¾ XZV!XW !bSVS`[Z!^aW_ Ð _`STW_`[^W_ZX[^S`[ZST[a`W  W  WVU^[__Ê bSVS`[Z^aW_ ^S^  W [aZ_ Ð   .

!  Ð ! !.

 Ð ! !  Ð !  .

! !   .

 @ n°nf¾½ n¾ XZV!XW !bSVS`[Z!^aW!ZW_ Ð _`STW_`[^W_U^[__ÊbSVS`[Z^aWWWWZ`_X[^W  W  WVU^[__ÊbSVS`[Z^aW_ ^S^  W [aZ Ð  ! !  .

 @ n°nf¾½ n¾ XZV!XW !W UaVW!^aW!ZW_ Ð _`STW_`[^W_U^[__ÊbSVS`[Z^aWWWWZ`_T^[WZ [a`Z`[ZVbVaSU[aZ_X[^W  W  WVW UaVW ^aWZW_ ^S^  W [aZ Ð  ! !  .

 @ n°nf¾½ n¾ XZV!XW !ZUaVW!^aW!ZW_ Ð _`STW_`[^W_U^[__ÊbSVS`[Z^aWWWWZ`_T^[WZ [a`Z`[ZVbVaSU[aZ_X[^W  W  WVZUaVW ^aWZW_ ^S^  W [aZ Ð  ! !  .

 @ n°nf¾½ n¾ XZV!U[\WV!V!XW !_`^aU`_ Ð _`STW_`[^W_U[\WVZX[^S`[ZST[a`W  W  WV_`^aU`a^W_ ^S^  W [aZ_ Ð   .

!  Ð ! !.

 Ð ! !  Ð   .

 @ n°nf¾½ n¾ XZV!U[\WV!V!XW _ Ð _`STW_`[^W_U[\WVZX[^S`[ZST[a`W  W  WV_ ^S^  W [aZ Ð   .

!  Ð ! !.

 Ð .

! .

!  Ð   .

 \US  ZX[^S`[Z S\W_  [\[ZWZ`_ \WWZ`S`[ZSZVWUZUS_\WU`_[X  .

@  ¾n½    ¾ W_U^\`bW W  WV_ S^Wa_WV`[S\`a^W VV`[ZS ZX[^S`[ZU _`WZ cS  [W_Z`S\`a^W  S^W.

\`[ZS WV_SZV\\WS^[Z [^S_S ZYW\SUW WV Z]aS^W^SUW`_ÓÔc`[a`S ^[\`   \SZV`WS\ST` `[S\`a^WS`S .

@ °f¯ .

@½nf°€ f¯½ ¾ S WZ` ZX[^S`[Z ^WV` ZX[^S`[Z _`^Ta`[Z _`W ZX[^S`[Z .

@ ¯½ ¯ °f°  S^W [` STWWV _W [[cZY`W\_`[VW`W^ZW`WZSW[X  [Z [^ # # # U.

ZW WV WWU` W\SYZ[_`U_ SZW _.

\WZ_SZV[c[cZY`W ZX[^S`[Z[X `W WV .

@ ¯½ ¯ °f°  [`W[cZ`WZSW[X`W[UcW^W  \\WS^_  U`W[U _`[XSaW_a``[Z`[_\S S _` [XSbSSTW[U_X[^`_ [^_WWU` "  !   "  U`W WV _`[XbSaW_a``[Z`[_\S S_`[X W_U^\`bW W  WV_X[^`_ [^ .

@ ¯½ ¯ °f°   SUZ`^ _ ^WX WVT `W SW[XW[UZ U`W \\WS^_ ZV`WZ`^W_X[^`W [Uc[_WZSW_ [aZVZ`W\ WWU``W `[TW \WWZ`WVW_W^ SW[X  S\\WS^_Z`WSaW _` .

@ ¯½ ¯ °f° W`W^ZW`WbSSTWW_[a^UW` [[cZY `W\_ SbYS`W`^[aY\\US`[Z W  WV W_U^\`bWWYWZ`_ _W`W_`[XSaW_X[^`W[aZ WVZ`W WYWZ`aS^ ZV[c`[W`W^ZW [c SZ  WYWZ`_USZTW SZZWV`[_W .

.

¯½° °¾€ [TSWYWZ`_Ê _\S  ZX[^S`[Z[[Z`[S[Z`W `_ [Z`W `WZ_`bWWYWZ`_Ê _\S  ZX[^S`[Z\\^[\^S`W`[S S^`UaS^ [Z`W `_ .

^[a\[XWWbSZ` ZX[^S`[Z [SZ[^SZ^WS .

VWZ`X ZY`W ZX[^S`[Z ^[a\ZY`W ZX[^S`[Z W`W^ZWXXW^WZ`[Z`W `_ .

 °€°– °€¯f° `[^W aTW^ WU aTW^ ^WV`S^V aTW^  \^S`[ZS`W [cZ S WZ` .

½°– °€¯f°  _SYW Ð ZSZUW Ð `[^W aTW^ [cZ S WZ` Ð WU Ð `[^W aTW^ WU aTW^ Ð ^WV`S^V Ð `[^W aTW^  aTW^  \^S`[ZS`W .

¾f .

¯¯°°€¯f° ZX[^S`[Z_WVT S__ `[^W aTW^ ZX[^S`[ZS^ T S__ Ð [cZ S WZ` Ð WU aTW^ Ð  aTW^ Ð  \^S`[ZS`W .

  ¯° €€  °.

° ¾ [cZ S WZ` ZSZUW WU aTW^WU  aTW^ \^S`[ZS`W^WV`S^V .

WYWZ``S`[Z`SZ_ ZX[^S`[ZcU [TS[^ [[Z`[[Z`W ` .

 –¯ ° f°€¯f° ZX[^S`[Z_WVT S__ `[^W aTW^ ZX[^S`[ZS^ T S__ Ð [cZ S WZ` Ð WU aTW^ Ð  aTW^ Ð  \^S`[ZS`W .

 f –¯ °¾ .

WYWZ`U[Z`SZ ZX[^S`[ZS`W^ S_\W^ `W[Z`W ` .

.

°  °¾  –¯ °¾ .

¾°–¾°–  °.

°  .

.

¯½° °¾€ WXW^WZUW WV_ WV_[Z`W\\US`[ZZV[cc[_WSaW__WV `[W`W^ZW`W[Z`W ` [Z`W ` WV  WVZ`W `^aU`a^Wc[_WSaW__WV`[ W`W^ZW`W S^`UaS^[Z`W ` .

 @ n°nf¾½ n¾ ^WSV _Ua__WVSTW_[ZYc` Ê WUZUS _Ua__[Z Ð XZV!S\\US`[Z Ð XZV!`STW_ Ð XZV!XW !bSaW!_W`_ .

 @ n°nf¾½ n¾ XZV!VW_U^\`bW!XW _ Ð _`STW_`[^W__W`a\ZX[^S`[ZST[a`VW_U^\`bW W  WV_ ^S^  W [aZ_ Ð   .

!  Ð   !   !   .

 @ n°nf¾½ n¾ XZV!U[\WV!VW_U^\`bW!XW _ Ð _`STW_`[^W_U[\WVZX[^S`[ZST[a`VW_U^\`bW W  WV_ ^S^  W [aZ_ Ð Ð Ð Ð   .

!    !   !   .

! .

!    .

 @ n°nf¾½ n¾ XZV!VW_U^!XW !U[aZ!a_SYW_ Ð _`STW_`[^W_`WU[^^W_\[ZVWZUW_TW`cWWZ S\\US`[Z`STWU[aZ_SZV`WVW_U^\`bW W  WV _WYWZ`_ ^S^  W [aZ_ Ð Ð Ð Ð   .

!    !   !     ! !.

!.

   .

!.

 !   .

 @ n°nf¾½ n¾ XZV!VW_U^!XW !U[Z`W `_ Ð _`STW_`[^W_U[Z`W `XWVbSaW_S_[Z[cZS_ _`^aU`a^WZSW_X[^VW_U^\`bW W  WV_ ^S^  W [aZ_ Ð   .

!  Ð   !   !   Ð   ! !.

!.

 .

 @ n°nf¾½ n¾ XZV!VWXSa`!U[Z`W `!XWV_ Ð _`STW_`[^W_`WZSW_[XX[^XWV_`S`a_W^_USZ a_WS_^WXW^WZUWXWV_X[^VW_U^\`bW W  WV_ ^S^  W [aZ_ Ð   .

!  Ð   !   !   Ð   !.

!  !   .

 f°n If f°.

f½f  ¾ _ZYSTWSVS`WVSaWW`_ _ZY ^[XW.

\`[ZSaW_X[^SVS`[Z _ZYSTWSaWX^[S ^[^ WV[ZS [^ _ZYSaW ^[S ^[^SaWW` .

# S`_`W_`ZU`[ZTW`cWWZ W  WV_SZV \\US`[Z WS`a^W_ # S`_`WYZXUSZUW[XS`SSVS`[Z_ .

 €  °n ¾ ``\ÈÈcccW`SZ[^SUWU[ .

^SUW\\US`[Z[UaWZ`S`[Z Ð W  WV__W^_ aVW Ð \\US`[Z_.

TWU`_ T^S^ .

WUZUS WXW^WZUW SZaS Ð .

^SUW\\US`[Z_WbW[\W^ aVW .

[^SZ VW`SWVV_Ua__[Z\WS_WWS [a^]aW^W_`[ SW_^!\`UaZ_U[ .

W_S[^S  `  # # S  SW_^!\`UaZ_U[ .