Friday, 14 February 2014

How to use Reference Field on DFF






Simple Steps For
Reference Field
On
DFF definition.



Author: Prashant Kumar
SCM Functional Consultant


 Q: How to add value in Reference Field LOV?
A: Add reference field in:
Application developer à Descriptive Flex Field à Register

Query Purchase Order Header DFF (PO Headers)


Click on “Reference Fields” button:



Add a new line with the new value as: OPERATING_UNIT (See: How to get the variable name for reference Field)



Q: How to configure reference field on DFF?
A: Navigate to DFF:


1)      Query for “PO Headers”
2)      Unfreeze.
3)      Check the LOV values of Reference field. (See: How to add value in Reference Field LOV)

You can find the “OPERATING_UNIT” value available in this list. This is the same value which we added, to reference field values, in previous section.
4)      Now select the value “OPERATING_UNIT” and save the record.
5)      Add the context value as name of Operating units. (See: How to determine the values for the context name)

6)      Define the segments.
a.       For this demo we have Defined 3 segments for OU1
b.      and 4 Segments for OU2



7)      Freeze and compile the DFF.
8)      We will discuss about “Synchronize with reference field” in other section.
Now verify the effect of reference field on DFF segments:
1)      Navigate to Purchase order form.

2)      Click on DFF.
3)      You will see the default value in CONTEXT field as OU1 and the 3 fields below this context value. There are several fields appearing above this context because those fields are defined in global context.
4)      Also you can change the value easily from the LOV of the context.

5)      See the changing segments when we select the other value from LOV. Now we can see the 4 segments. (This is similar to having multiple contexts and not using the reference field functionality on DFF).

6)      To see the effect of “Displayed” and “Synchronize with reference field” please see: How to work with “Synchronize with reference field” section.







Q: How to determine the values for the context name?
A: For our example, we have to navigate to Purchase Order form.
See the value in first field i.e. “Operating Unit”.

Similarly if we would have used the “TYPE_LOOKUP_CODE” in reference field then we would have referred the values of Type field of the above screen shot (Standard, Blanket etc.)
Note: Value being referred (value on the form) by Reference field should be same as the name of context. Only then this will display the segments of the matching context in DFF.
In other words if we would have used “TYPE_LOOKUP_CODE” then the context values (in DFF definition lines) would be
Standard purchase order, Blanket purchase Agreement etc.
In our case as we have selected the “OPERATING_UNIT” as reference field hence we used the context values as OU1 and OU2.





Q: How to get the variable name for reference Field?
A: As we have taken PO heads flex field in our example, we need to navigate to Purchase order form to determine the value of reference field.
1)      Open Purchase order header form.
2)      Navigate to Helpà DiagnosticàExamine.
3)      If you face the error “this function is not enabled for you” then please update the profile option “Utilities:DiagnosticsSet it to yes at site level, your problem will get resolved.





Q: How to work with “Synchronize with reference field”?
1)      Un-freeze the flex field.
2)      Select the “Synchronize with reference field” checkbox.



3)      Freeze the DFF, compile it and verify the effect on Purchase Order header DFF as below.

4)      Here Context value is non-editable. Here we can find the real usage of “Reference field” as value of the context is being defaulted in the DFF and context is non-editable as it gets synchronized with the value of reference field of the DFF definition.
5)      Here we can go one step ahead, if the context is non-editable then there is no use of displaying the context. For this oracle has given the functionality of “Displayed” check box on DFF definition.
6)      Uncheck the displayed checkbox:

7)      Freeze and compile the DFF. And see the effect on Purchase order header DFF.

8)      You will not find the context field anymore available on the DFF screen, but the segments are displayed according to the values of Reference field.






Note for “value set” field on DFF definition:

This has the same functionality as reference field.
To implement this we use the value set to display the values under context field (Say on DFF page of Purchase order header)
And for this the Context values should be the values being returned by value set.

For eg: if we use Yes/no Value set and the return value of this value set is Y and N then we have to create the context values with code as “Y” and another context with code as “N”. (Similar to the codes OU2 and OU1)

3 comments:

  1. This comment has been removed by the author.

    ReplyDelete
  2. The best explanation I have found about this topic..

    Thanks alot

    ReplyDelete
  3. Simply wish to say your article is as astonishing. The clarity in your post is simply great, and I could assume you are an expert on this subject. Same as your blog i found another one Oracle Fusion Procurement .Actually I was looking for the same information on internet for Oracle Fusion Procurement and came across your blog. I am impressed by the information that you have on this blog. Thanks a million and please keep up the gratifying work.

    ReplyDelete