What is the significance of reference field in a dff

Tata Consultancy Services Ltd. A1 Technology Ltd. A3Logics India Ltd. Almighty Software Pvt Ltd. ABM Knowledgeware Ltd. Top Rated Companies: dr reddys laboratories ltd bank of america amazon india pvt ltd hp inc tata communications ltd ultratech cement ltd maruti suzuki india ltd tata motors ltd ericsson pvt ltd mahindra mahindra ltd cipla ltd accenture larsen and toubro ltd cognizant technology solutions bharti airtel ltd dell india itc ltd ibm india pvt ltd genpact india pvt ltd icici bank ltd oracle tata consultancy services ltd axis bank ltd infosys technologies ltd mphasis ltd wipro technologies ltd capgemini india pvt ltd hcl technologies ltd kotak mahindra bank.

Jobbuzz Feedback Contact us Jobbuzz for Employers. Follow us on Jobbuzz. Indiatimes Classified Network. Sign In. Don't have an account? Register now. Sign In using. Already a user? Sign in to JobBuzz. Follow us on Jobbuzz. Indiatimes Classified Network. Sign In. Don't have an account? Register now. Sign In using.

Already a user? Sign in to JobBuzz. Please enter a valid email id. Password mandatory! Forgot password?

Not you? Not using TJ? Create Account. Already a User? Old Fashioned? See: Reference Fields. If you have any context-sensitive segments for your flexfield, you should always check the Displayed check box if you do not specify either a default value or a reference field. Without the displayed context field, your flexfield must determine the context field value from the reference field or your default value. If you check the Displayed check box, a user can see and change the context field value that your flexfield derives from a reference field or obtains as a default value.

Tip: You should leave the Displayed check box unchecked only if the context field value derives from a reference field or a default value that you specify using this region, or you have only global segments.

If you do derive your context field value from a reference field, however, we recommend that you do not allow your user to see or change that value in the flexfield window. Note: In earlier versions of Oracle E-Business Suite, you allow users to see and modify the value in the context field by checking the "Override Allowed Display Context " check box.

Check this box if you want the context field value to be synchronized always with the reference field value for this descriptive flexfield. Use this block to define valid context field values that also serve as structure names for this descriptive flexfield.

You can set up a different descriptive flexfield segment structure for each value you define. A Global Data Elements value always appears in this block. You use Global Data Elements to set up global segments that you want to use in every segment structure.

These segments appear before any context field or context-sensitive segments in the flexfield window. For example, suppose you have a Client Type flexfield. You have two context-sensitive structures, Employee internal client , and Customer external client , for which you want to have different segments to capture different information.

However, you also want to capture certain information for both structures. You define global segments for the common information, using the Global Data Elements value. You also define context-sensitive segments for each of your two structures, Employee and Customer, to capture the two sets of different information. See: Planning Your Descriptive Flexfields. Enter a unique context field value also known as the flexfield structure name under the Code column.

Your flexfield uses this value, either derived from a reference field or entered by your user in an initial descriptive flexfield window, to determine which flexfield structure to display.

This value is written out to the structure column of the underlying table. Once you save your context field value, you cannot delete or change your context field value because it is referenced elsewhere in the system. You can disable a value, however. Tip: Choose and type your context field values carefully, since once you save them you cannot change or delete them later.

If you are using a reference field, the values you enter here must exactly match the values you expect your reference field to provide, including uppercase and lowercase letters. For example, your reference field may be a displayed field that provides the values "Item" and "Tax", so you would specify those. However, those would not be valid if you were using a corresponding hidden field as your reference field and that field provides the values "I" and "T".

If you are using a value set for the context field, any values you enter here must exactly match the values you expect your context field value set to provide, including uppercase and lowercase letters. All the values you enter in this field must exist in the value set, or they will not be valid context field values, even if you define context-sensitive segments for them. You only need to enter those values that require context-sensitive segments. If the value set is a table-validated value set, the values in this Code field correspond to the values in the ID column of the value set.

The context code will default in to this field. For a descriptive flexfield that is set up so that the context field is displayed, the context name would be entered in the displayed context field, and the context field value code will be stored in the hidden context field. The list of values on the context field will show the context name and description.

If you use a value set for the context field, the displayed value in the value set overrides the corresponding value name you type in this field for the same hidden ID value or context code. Enter a description for this descriptive flexfield context field value.

You can use this description to provide a better explanation of the content or purpose of this descriptive flexfield structure. You see this description along with the context name whenever you pick a descriptive flexfield context from inside the flexfield window. When you navigate to the next zone, this window automatically saves your pending changes.

Important: The width of your descriptive flexfield window depends on the length of the longest description you enter in this field, if this description is longer than the longest description size you choose for any of your segments in a given structure.

Choose the Segments button to open the Segments window, and define your flexfield segments. See: Defining Segments. Some descriptive flexfields in Oracle E-Business Suite are documented explicitly with specific setup suggestions, but most descriptive flexfields in Oracle E-Business Suite, which are meant to be set up on a site-by-site basis, are not explicitly documented.

In most cases, you can identify which descriptive flexfield appears on a particular form using the following procedure. If Examine is disabled or requires a password on your system, contact your system administrator for help.

The Examine Field and Variable Values window initially displays the hidden block and field names of the field your cursor was in when you opened Examine.

Note the block name displayed to help you select the correct flexfield in a later step. If there is more than one descriptive flexfield for your form, use the list on the Field field to select the one you want the list displays the hidden block names and field names for all descriptive flexfields on the form. If you do not see the descriptive flexfield you want, it may be because your form has special logic that prevents the flexfield from being read by Examine, such as logic that makes the flexfield appear only under certain conditions.

Make sure the descriptive flexfield is visible, that those conditions are met, and that your cursor is in the same block as the flexfield. Try using Examine again. The flexfield title that appears in the Value field is the title you should choose in the Descriptive Flexfield Segments form. See: Defining Descriptive Flexfield Structures. You should already know some basic flexfields terms and concepts: Flexfield Segment Structure Value Validation Validate Value set Now that you know terms and concepts that apply to both key and descriptive flexfields, you need to know additional terms that apply to descriptive flexfields only.

Descriptive flexfield segments Descriptive flexfields have two different types of segments, global and context-sensitive, that you can decide to use in a descriptive flexfield structure. Context-sensitive segments If you have context-sensitive segments, your descriptive flexfield needs context information a context value to determine which context-sensitive segments to show.

Using Value Sets With Context Fields Typically, you set up context field values by typing them into the Descriptive Flexfield Segments window individually, and you then set up context-sensitive segments for each context field value. Value sets used for context fields must obey certain restrictions or they will not be available to use in the Value Set field in the Context Field region of the Descriptive Flexfield Segments window: Format Type must be Character Char Numbers Only must not be checked alphabetic characters are allowed Uppercase Only must not be checked mixed case is allowed Right-justify and Zero-fill Numbers must not be checked Validation Type must be Independent or Table If the validation type is Independent: the value set maximum size must be less than or equal to 30 If the validation type is Table: the ID Column must be defined, it must be Char or Varchar2 type, and its size must be less than or equal to Example of conditional context field values without a separate table Suppose you already defined all of your context field values, and you do not need another table.

Synchronizing the Context Field Value with the Reference Field Value You can optionally set up your flexfield so that the context field value is always synchronized with the reference field value. The following table lists the possible behaviors: Context Field Synchronized? Context Field Displayed? Runtime Behavior No No The context value is derived from the reference field value the first time the descriptive flexfield record is touched.

Thereafter it is never synchronized with the reference field value. Hence, whatever context information defaults at the time the record is created is carried forward. Users will not be able to change the context subsequently because the context field is not displayed. Even if the reference field value changes, the context information will not be changed because it is not synchronized.

No Yes Context is derived from the reference field value the first time the descriptive flexfield record is touched. Thereafter it is never synchronized. Users are allowed to change the context at any time. Yes Yes The context value is always derived from the reference field value. The context field in the descriptive flexfield window remains non-updateable to the user, because users should not be allowed to break the synchronization by manually selecting a context value other than the derived one.

Yes No The context value is always derived from the reference field value. The context field is hidden from the user. Different Arrangements of Segments You have many choices for how you want your descriptive flexfield structures to look and behave. The different descriptive flexfield setup options are: Global Segments Context-sensitive segments Override Allowed Reference Field Default Context field Note that the option "Override Allowed" controls whether your user sees a context field in the flexfield pop-up window.

One structure The simplest way to define a flexfield is to have one structure that contains only global segments. In this example, you have the following settings: Global Segments - No Context-sensitive segments - Yes Override Allowed - No Reference Field - Yes Default Context field - OK This example has two context-sensitive structures, one with three context-sensitive segments and another with one context-sensitive segment.

Related Topics Descriptive Flexfield Concepts How Segments Use Underlying Columns Planning Your Descriptive Flexfield Planning Your Descriptive Flexfield When you are planning your flexfields, you should consider the following questions and their corresponding decisions: Do you want to capture information that is not otherwise captured by the window or page?

Do you want to require a value for each segment? Do you want to use Flexfield Value Security with your descriptive flexfield? Related Topics Planning Your Descriptive Flexfield Defining Descriptive Flexfield Structures Defining Segments Identifying Descriptive Flexfields in Oracle E-Business Suite Defining Descriptive Flexfields To define your descriptive flexfield, you define the segments that make up your descriptive flexfield structures, and the descriptive information and validation information for each segment in a structure.

Freeze Flexfield Definition The default value for this field is unchecked flexfield definition not frozen. Segment Separator Enter the character you want to use to separate your segments in a concatenated description field.

Context Field Region Enter information for your context field here. Prompt The context field automatically displays any existing context window prompt for this flexfield.

Value Set If you have context field values contained in an existing table, you can create a value set that includes those values, and enter the name of that value set here. Default Value Enter a default context field value for your flexfield to use to determine which descriptive flexfield structure to display.

Required Indicate whether a context field value is required. Reference Field Enter the name of the reference field from which your flexfield can automatically derive the context field value. Displayed If you have any context-sensitive segments for your flexfield, you should always check the Displayed check box if you do not specify either a default value or a reference field. Synchronize with Reference Field Check this box if you want the context field value to be synchronized always with the reference field value for this descriptive flexfield.

Code Enter a unique context field value also known as the flexfield structure name under the Code column. This value must be thirty 30 characters or fewer. Name Enter a name for this descriptive flexfield context value. Description Enter a description for this descriptive flexfield context field value.

Enabled You cannot enable new structures if your flexfield definition is frozen.