How You Can Derive and Validate Descriptive Flexfield Values Using Purchasing Document Header Attributes

You can use purchasing document header attributes such as procurement business unit when configuring descriptive flexfields. You can use the attributes to define value sets to limit the list of possible values.

With default values and value sets, you can reduce the data entry time for purchase orders and purchase agreements.

Your Procurement administrator can define value sets with logic to derive values based on purchasing document parameters. For details on how to define flexfields and value sets, refer to the Flexfield section of the Configuring and Extending Applications guide.

This table shows the purchasing document attributes that are enabled as flexfield parameters and the syntax for the value set logic. These parameters are available in the Purchasing Document Headers, Lines, Schedules, and Distributions flexfields.

Parameter

Syntax

Requisition BU ID

:{PARAMETER.RequisitioningBUId}

Procurement BU ID

:{PARAMETER.ProcurementBUId}

Document Type

:{PARAMETER.DocumentType}

Sold-to Legal Entity ID

:{PARAMETER.SoldtoLegalEntityId}

Document Style ID

:{PARAMETER.DocumentStyleId}

Here is an example of how to use purchasing document header attributes.

In this example, we will see how to default the descriptive flexfield context segment to the document type and show different context sensitive segments depending on the document type. In this example, when creating a purchase order, the document type will be STANDARD and the page will only show the Context Sensitive Segments for that context.

  1. Create a value set for the document type, and define these values:

    • From clause: po_lookup_codes types

    • Value Column Name: types.LOOKUP_CODE

    • Where clause: types.LOOKUP_TYPE = 'DOCUMENT_SUBTYPE' and types.LOOKUP_CODE = :{PARAMETER.DocumentType}

  2. Set the value set of the Context Segment to the value set you defined.

  3. Create a context for each document type (STANDARD, BLANKET, and CONTRACT) and define Context Sensitive Segments for each context.

  4. Save your changes and deploy the flexfield.