Document 1904073.

1 of 4

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

How To Create OU Specific Context DFF For Requisition Header Which Works In Core Requisition Form And
iProcurement. (Doc ID 1904073.1)
In this Document
Goal
Solution
References

APPLIES TO:
Oracle iProcurement - Version 12.1.3 and later
Information in this document applies to any platform.

GOAL
How to create OU specific Context DFF For Requisition Header which works in Core Requisition Form And iProcurement ?

SOLUTION
The solution provided here shows the workaround to setup the Context DFF which can be used both in iProcurement and Core Purchasing
Requisition Form. It caters for specific scenario where the Context is based on the OU in which the requisition is being created.
In past, to setup context DFF in Core Purchasing Requisition form the use of $PROFILES$ was evident where $PROFILES$.ORG_ID would
serve as reference field. However the same was not allowed in iProcurement. The iProcurement pages are based on framework which could
not directly interpret $PROFILES$ for reference column. Below steps show the workaround to such issue, which help to achieve this
functionality both in Core Purchasing Forms and iProcurement Framework Pages.
1. Make sure that below profiles are not set or set to null.
POR: Context value for Requisition header descriptive flexfield
POR: Context value for Requisition line descriptive flexfield
POR: Context value for Requisition distribution descriptive flexfield
2. Setup the Context DFF for Requisition Headers.
a) Navigate to System Administrator -> Application -> Flexfields -> Descriptive -> Segments
b) Query for Title : Requisition Headers
c) Unfreeze the DFF : uncheck the box for Freeze Flexfield Definition
d) Enter the value for Reference Field as :$PROFILES$.ORG_ID (technically we can put any value instead of ORG_ID , however we have
choosen it to be ORG_ID so that it works for Core Requisition Form as well. Also this value should match later when setting up Flex Map in
iProcurement in later steps) , check the box for Synchronize with Reference Field.

03-10-2016 11:51

Document 1904073.1

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

Now create the Context Segments. Please note here we need the OU id , ie: the id of OU that is setup with profile: MO: Operating Unit for
iProcurement and Core Purchasing responsibility.
Create a record in Context Field Values section.
a) Code = 204 , Name = Vision Operations - 204 , Description : Vision Operations - 204 . (FYI: The value 204 , refers to Vision Operations
OU on a Vision Instance)
b) Click on button 'Segments'
Enter Segments: Customer can enter segments as per their requirement, specific to the OU. Example given as below:
c) Number = 1 , Name = Segment_Org_204 , Window Prompt = Segment_Org_204 , Column = ATTRIBUTE1 , Value Set = 20 Characters.
d) Click on button 'Open' to further change the attributes of the segments ie: Required , default value etc.

Save the changes and freeze the DFF. Make sure to compile the DFF once it is freezed.

3. Personalization needed for iProcurement Framework Pages.

Navigate to iProcurement responsibility add a item to cart and checkout (This is to be done so that user can navigate to the page where
DFF need to be personalized). The page shown should be: Checkout: Requisition Information
( /oracle/apps/icx/por/req/webui/CheckoutSummaryPG ), where the Requisition Header DFF will be shown.
NOTE : Customer can also use resp : Functional Administrator, instead of above and do personalizations for Document Path : /oracle
/apps/icx/por/req/webui/CheckoutSummaryPG
Enable the DFF for Requisition Headers.
a) Click on the link : Personalize Stack Layout: (ReqHeaderRN)
b) Search for 'Flex: (ReqHeaderDFF)'
c) Now click on the personalize pencil icon for 'Flex: (ReqHeaderDFF)'
d) Set the 'Rendered' property to 'true' at the desired level (ie: Site, Organization, Responsibility)
e) Apply the changes
Create the Flex Map for Context Field.
f) Now click on the Create Item on the row 'Flex: (ReqHeaderDFF)' . Here you can define the Flex Map settings.
g) Enter the Flex Map Settings
Enter ID = BBBingo
( Can be any Unique Id)
Name = ORG_ID
( The value here should match to value entered in step 2(d) above example :$PROFILES$.ORG_ID )
Reference Value = ${oa.PoRequisitionHeadersVO.OrgId}
(This is the actual reference column based on which the Context DFF will be
shown)
Refer Context = true. (This has to be true, as the flex map needs to refer to the context)
h) Apply the changes.

2 of 4

03-10-2016 11:51

Document 1904073.1

3 of 4

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

4. Clear the Apache Cache.

Navigate to Functional Administrator Responsibility > Core Services > Caching Framework > Global Configuration > Click on Clear all Cache.
5. Context DFF seen in iProcurement based on OU used for responsibility.
Relogin into iProcurement and checkout and navigate to the page : Checkout: Requisition Information . The Context DFF should now be
displayed. This is shown only when the iProcurement responsibility is attached to the OU : Vision Operations , as per MO: Operationg Unit.

6. Context DFF Seen in Core Purchasing Form based on the OU selected.

Similarly, if user is creating requisition in Core Requisition Form and Operating Unit selected is Vision Operations , then they should see
similar DFF segments .

03-10-2016 11:51

Document 1904073.1

4 of 4

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

NOTE : There 2 important points to note here. The solution in above steps works because :
1. The ORG_ID column exists in the core purchasing forms. Hence the reference field is $PROFILES$.ORG_ID .
2. In iProcurement pages , the View Object has the same column . ie: PORequisitionHeadersVO.OrgId .
The reference field setup in Context DFF is mapped to Flex map, which in turns acts as reference for the DFF and redirects the display of
DFF context based on value of PORequisitionHeadersVO.OrgId .

REFERENCES
NOTE:332364.1 - How Are Descriptive Flex Fields Supported Against Context
NOTE:1576419.1 - Why Are iProcurement Users Not Able To Choose The Context Tor A Descriptive Flexfield (DFF) That Is Setup With
Multiple Context Values?
NOTE:728844.1 - Is There A Way To Select The Reference Field Set Up in The Purchasing Requisition Descriptive Flexfield (DFF) Definition?
NOTE:456339.1 - What Is the Option For Context Flexfield If $PROFILES$.ORG_ID Is Not Available In iProcurement
NOTE:1904073.1 - How To Create OU Specific Context DFF For Requisition Header Which Works In Core Requisition Form And
iProcurement.
Didn't find what you are looking for?

03-10-2016 11:51