Extensible Flexfields (EFF) in Oracle Fusion Cloud

Extensible Flexfields (EFF) is just a extension of Dynamic Flexfields (DFF). In other words, Extensible Flexfields (EFF) expand the scale and scope of Dynamic Flexfields (DFF) by adding enhanced features.

Technically, Extensible Flexfields (EFF) decouple the flexfield segment as a single column in transaction database tables to segment values and context and stores them in a child tables. This will provide the implementers/consultants the customizable expandible space to configure an unlimited number of both segments and contexts.

From configuration perspective, Extensible Flexfields (EFF) use context in the same way as Dynamic Flexfields (DFF)  but adding an intermediate layer to support extension. This intermediate layer is Category that will support the context and all the contexts can be organized into a structure and can be displayed based on the usage.

Now let’s take a look into the system to apply the idea discussed above.

Navigate to Setup and Maintenance area and search for Extensible Flexfields1

We will go and create some EFF at sales order header level. Click on “Manage Order Extensible Flexfields” and search for Header Information

2

Go to Actions > Edit to go inside

3

On this landing page, you will see the Category – Additional Header Information and all the contexts associated with category. Now click on the Pages tab under Category Details to view the pages displayed and hierarchy on the Sales Order UI.

4

If you scroll down the above page, then you will find that under Associated context details the context specific segments that is displayed under each page are associated to the page

5

Now let create one context and context specific segment and create separate page to display under sales order additional information UI.

Click on Manage Contexts to create context

6

7

Go to Actions > Create to create a new context

8

Enter the Context display name and select the behavior. DO NOT CHANGE Code and API name, it should be system populated.

Now associate Context to Category under Context Usage

9

Click Save and Go to Actions > Create under Context Sensitive Segment to create Segments

10

I am not detailing on each and every value on segment assuming you are aware of how to create segment. But listing out the important fields:

  • Enter Segment Name. DO NOT CHANGE  Code and API name, it should be system populated.
  • Select Data Type and Table Column
  • Select Value Set
  • Select Display Type

Click on Save and Close

11

The segment is added to the context. Click on Save and Close to complete the context and context specific segment creation.

12

Click again on Save and Close to go back to the EFF Main page

Now, till this step it is same as DFF. But to display this segment (EFF) on the sales order additional information UI, we need to perform below steps:

  • Associate the Context to Category

Highlight the “Additional Header Information” Category and click on Actions > Create under Associated Context to associate the context

13

Search for your context and click on OK and then Apply to associate the context to Category

14

  • Create Page under Category under which the Context specific Segment is available

Highlight the “Additional Header Information” Category click on Pages under Category: Details

15

Go to Actions  >Create to create page that represent context specific segment

18

 

Enter the Page name same as segment name and DO NOT CHANGE the Code as it is system populated. Always Select Usage as “Additional Header Information”. Click OK

19

  • Associate the Context to the Page

Go to Actions > Create under Associated Context Details for Page

20

Search for your context and click on OK and then Apply to associate the page with context.

21

Click on Save and Close to complete the EFF creation.

22

Click on Deploy Flexfield to deploy the EFF for sales order

23

Click OK to complete EFF deployment

Now go to sales order creation UI to view the EFF just created

24

 

 

 

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *