An Oracle White Paper

July 2017

Configuring Descriptive Flexfield

Segments With Requisition Parameters
Oracle Procurement Cloud Releases 12 and 13
 Configuring Descriptive Flexfield Segments with Requisition Parameters

Introduction ....................................................................................... 3
DFF segment with LOV values based on requisitioning BU and source
agreement ......................................................................................... 4
DFF segment with LOV values based on requisition line type ........... 5
DFF segment with LOV values based on the requester ..................... 5
Project expenditure type LOV values based on purchasing category 6
 Configuring Descriptive Flexfield Segments with Requisition Parameters

Introduction
Businesses often need to capture additional information along with requisitions. You can use descriptive flexfields
to extend the requisition header, line, and distribution to meet your business needs. Flexfields help you create and
configure attributes to save additional data with your requisition.

A segment is a field within a descriptive flexfield (DFF) that represents an information attribute that can be
displayed on Self Service Procurement pages. You can allow users to enter values into segments while using the
application. In addition, you can configure segments with a value set that ensures your self-service users only see
and select valid values for a descriptive flexfield segment within the context of a requisition.

In Release 12, the requisition line descriptive flexfield supports parameters that provide run-time requisition line
values for descriptive flexfield validation. Procurement administrators can now define value sets with logic to
derive values based on requisition parameters. For details on how to define flexfields and value sets, please refer to
our Define Applications Core Configuration in the Oracle Procurement Cloud Implementing Procurement:
http://docs.oracle.com/applications/farel12/procurementop_gs/OAPRO/OAPRO1063547.htm#OAPRO10635
37

The following table shows requisition line attributes enabled as flexfield parameters, and the syntax to be used in
the value set logic. Note that the parameters below can be used only with the Requisition Line DFF.

Parameter Syntax
Requisitioning BU ID :{PARAMETER.RequisitioningBUId}
Source Agreement ID :{PARAMETER.SourceAgreementId}
Requester ID :{PARAMETER.RequesterId}
Category ID :{PARAMETER.CategoryId}
Supplier ID :{PARAMETER.SupplierId}
Urgent :{PARAMETER.Urgent}
Line Type ID :{PARAMETER.LineTypeId}

Examples explaining how to use the above parameters follow.

 Configuring Descriptive Flexfield Segments with Requisition Parameters

DFF segment with LOV values based on requisitioning BU and source

agreement
Scenario: a supplier DFF segment should show a list of values based on the requisitioning BU and source
agreement provided in the requisition line.
Using the SLA mapping sets UI, you can define the list of values for the supplier DFF segment based on the
requisitioning BU and source agreement combination. You can access the mapping sets UI through the FSM task
Manage Mapping Sets. Make sure that the context for this task is Purchasing:

Go to the Manage Descriptive Flexfields task to define your DFF segments. Search for DFFs under the Self
Service Procurement Common Components module and select the Requisition Lines DFF.

Create the supplier global segment with data type number. For the value set, define the following:

a. From clause: poz_suppliers_v supplier, xla_mapping_set_values mapping, po_headers_all po,

fun_all_business_units_v bu
b. Value Column Name: supplier.vendor_name
c. ID Column Name: supplier.vendor_id
d. Where clause:
mapping.mapping_set_code = 'ORA'
AND mapping.input_value_constant1 = bu.bu_name
AND bu.bu_id = :{PARAMETER.RequisitioningBUId}
AND mapping.input_value_constant4 = po.segment1
AND (po.po_header_id = :{PARAMETER.SourceAgreementId})
AND mapping.input_value_constant2 = supplier.vendor_id
e. Order by clause: supplier.vendor_name
f. Save your changes and deploy the flexfield
 Configuring Descriptive Flexfield Segments with Requisition Parameters

Note that constant1/constant2/constant4 match the order of the columns in the mapping set table in the previous
screenshot. You can also check the mapping set table xla_mapping_set_values to make sure you have the constant
pointing to the right table column.

In this example, for requisition lines that have agreement number 1002381, and requisitioning BU as Vision
Operations, the supplier DFF segment should show only the values: Office Depot, and Office Max. For
requisition lines with agreement 1000587 and requisitioning BU as Vision Operations, the supplier DFF segment
should show only the value: Office Supplies

When you select multiple lines for mass edit, and the lines do not have the same combination of agreement and
requisitioning BU, the supplier DFF segment LOV will be null.

DFF segment with LOV values based on requisition line type

Scenario: a service type DFF segment should show values when the requisition line type is fixed price service.
Similar to the previous example, use the mapping sets UI to define the list of values for the service type DFF
segment based on the requisition line type. For example, you can map the fixed price service line type to
Advertising, and Accounting service types.

For the Requisition Line DFF, create the service type global segment with data type varchar. For the value set,
define the following:

a. From clause: xla_mapping_set_values mapping, po_line_types_TL polines

b. Value Column Name: SUBSTR(mapping.input_value_constant2, 1, 150)
c. Where clause:
mapping.mapping_set_code = 'LTP'
and mapping.input_value_constant1=polines.LINE_TYPE and
polines.line_type_id=:{PARAMETER.LineTypeId}
d. Save your changes and deploy the flexfield

In this example, when the requisition line type is ‘fixed price service’, the service type DFF segment will have the
values ‘Advertising’, and ‘Accounting’; otherwise, it will be null.

DFF segment with LOV values based on the requester

Scenario: a department DFF segment should show the requester’s department from his primary employment
assignment.
For the Requisition Line DFF, create the department global segment with data type character. For the value set
define the following:

a. From Clause: HR_ALL_ORGANIZATION_UNITS_X org,

PER_ALL_ASSIGNMENTS_M assignments
b. Value Column Name: SUBSTR(org.NAME, 1, 150)
 Configuring Descriptive Flexfield Segments with Requisition Parameters

c. Where Clause: assignments.PERSON_ID=:{PARAMETER.RequesterId} AND

org.ORGANIZATION_ID=assignments.ORGANIZATION_ID and
assignments.PRIMARY_FLAG='Y'
d. Save your changes and deploy the flexfield.

Project expenditure type LOV values based on purchasing category

Scenario: Project expenditure type LOV values should be filtered based on the requisition purchasing category. If
the LOV contains only one record, then that value should be defaulted.
Using the SLA mapping sets UI, you can define the mapping between the purchasing category and the expenditure
type. You can access the mapping sets UI through the FSM Manage Mapping Sets task. Make sure that the context
for this task is Purchasing. For example:
- Select “Segment” as the mapping set output type.

- Add two input sources:

o Item Category

o Expenditure Type (from Project Costing sources)

- Select “Account” for the “Chart of Accounts” segment value.

- Select the Item Category input value from the list of values and the corresponding Expenditure Type
value from list of values. You can define many-to-many combinations of purchasing category and
expenditure type.

- You must provide output values as shown in the screen below for the account segment, even though
it’s not fundamentally needed for this usage of the mapping set.

- Create new value set

 Configuring Descriptive Flexfield Segments with Requisition Parameters

ValueSet Where Clause: system_linkage_function = 'VI' and trunc(sysdate) between

nvl(expnd_typ_start_date_active, trunc(sysdate)) and nvl(expnd_typ_end_date_Active,
trunc(sysdate)) and trunc(sysdate) between nvl(sys_link_start_date_active, trunc(sysdate)) and
nvl(sys_link_end_date_Active, trunc(sysdate)) and project_unit_id = (select
PROJECT_UNIT_ID from PJF_PROJECTS_ALL_B_V pr where pr.project_id =
:{SEGMENT.PROJECT_ID}) and expenditure_type_id in (select input_value_constant2 from
XLA_MAPPING_SET_VALUES where mapping_set_code = 'PO_G4S_EXP_MAPPING1'
and application_id = 201 and input_value_constant1
=to_char(:{PARAMETER.PurchaseCategory}))

- Map the newly created valueset to Project Cost Collection Widget Description FlexFields -> POR:
Requisition context -> EXPENDITURE_TYPE_ID segment.
o Search for task “Manage Project Standard Cost Collection Flexfield”.

o Edit the flexfield.

o Go to Manage Contexts.
 Configuring Descriptive Flexfield Segments with Requisition Parameters

o Search for Display Name: POR: Requisition, and edit it.

o Select the “EXPENDITURE_TYPE_ID” record and edit it.

o Select the newly created value set from the drop down.
 Configuring Descriptive Flexfield Segments with Requisition Parameters

o Click Save and Close, and deploy the flexfield.

Uploading Attachments to Requisitions Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

Oracle Procurement Cloud

This document is provided for information purposes only, and the contents hereof are subject to change without notice. This
Releases 12 and 13
document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in
July 2017
law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any
Author: Mara Prieto
liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This
document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our
Oracle Corporation
prior written permission.
World Headquarters
500 Oracle Parkway
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Redwood Shores, CA 94065
U.S.A.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
Worldwide Inquiries: are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
Phone: +1.650.506.7000 trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0113
Fax: +1.650.506.7200

oracle.com