Descriptive Flexfields:: Step 1
Descriptive Flexfields:: Step 1
Descriptive FlexFields:
Descriptive flexfields provide customizable "expansion space" on your forms. You
can use descriptive flexfields to track additional information, important and unique
to your business that would not otherwise be captured by the form. Descriptive
flexfields can be context sensitive, where the information your application stores
depends on other values your users enter in other parts of the form.
A descriptive flexfield appears on a form as a single-character, unnamed field
enclosed in brackets. Just like in a key flexfield, a pop-up window appears when you
move your cursor into a customized descriptive flexfield. And like a key flexfield, the
pop-up window has as many fields as your organization needs.
Step 2:
Click the Edit icon by selecting line record:
For e.g. we select PO_HEADERS Flexfield Code
User can create Global Segment and Context Sensitive Segments:
Reference Document_V1
Now select the line and click on Edit Icon to view the details of record:
Click Enabled check box so that this additional field is become view able on
transaction pages.
Click BI Enabled check box so that this additional field is became available on BI.
2
Reference Document_V1
Step 3:
Creating and Value Set:
Value Sets act as validations for the values entered by users. When the users enter
the values in any of the fields (on any form), if there is a value set attached to this
field, the values entered by user are validated against the value set.
When you first define your flexfields, you choose how many segments you want to
use and what order you want them to appear. You also choose how you want to
validate each of your segments. The decisions you make affect how you define your
value sets and your values.
As we have already created a Value Set so click on View Value Set button.
Reference Document_V1
Step 4:
Deploying a Flexfield after creating and making any changes click the deploy button
verify the deployment status from front end.
Reference Document_V1
Step 5:
Execute the concurrent Import Oracle Fusion Data Extensions for Transactional
Business Intelligence from Schedule Processes so that field is visible on BI.
Schedule Process execution steps are mentioned below:
Next
Reference Document_V1
Reference Document_V1
Step 6:
Verify column in OTBI subject area.
Step 7:
Verify DFF at PO header at Purchase Order from application.
Reference Document_V1
Reference:
Video tutorial for context sensitive DFF.
https://www.youtube.com/watch?v=eNgtii7wMcA