How To Make Descriptive Flex Field To Prompt Based On Document Type In Buyer Work Center And Core Purchasing
(Doc ID 1126873.1)
Last updated on JULY 02, 2018
Oracle Purchasing - Version: 12.0.0 to 12.1.3 - Release: 12 to 12.1 Information in this document applies to any platform.
The objective of this note is to demonstrate how to prompt different set of flexfields on the Purchase Order header, based on the document type. This prompting of flexfield will be done in Core Purchasing and in Buyer Work Center. However, there is a limitation in prompting the flexfields in Buyer Work Center based on the document type. The user has to manually choose the document type to prompt the correct set of flexfields.
If the flexfield setup has to be done only for the Buyer Work Center, <> can be used. Please use the section ' B.3 Context DFF using a reference field' of the document. However if you configure the flexfield definition according to that document, core purchasing will not work.
Hence this document has been developed to satisfy both core purchasing and buyer work center, although with a limitation. The limitation is mentioned in <>.
An enhancement request has been logged to overcome this limitation. <> - ER: CONTEXT OF PO HEADER DFF IS NOT SYNCHRONIZED IN 'BUYER WORK CENTER'
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.