Oracle is regularly imbedding UDA into a growing list of application modules.

And that list now includes

Order Management in R12.2. Since our original post, weve been able to bring up our Oracle R12.2 Vision
instances and take it for a test drive. Heres how it looks:

UDA Functionality with Order Management

In order for UDA to be functional with Order Management, Oracle must embed it in the specific
record and form.
Because of this, Oracle has embedded UDA into the sales order header, lines and related forms in Order
Management. This includes the quote headers and lines forms but does not include the Oracle Quoting
modules quote records.
Oracle also extended the seeded workflow of the Order Interface to support importing of UDA information
to related sales order headers and lines forms.

Setup
Setup was surprisingly fast. After a little navigating around and getting familiar with the form layout, I was
able to quickly complete the simple steps and it worked! There were no glitches or undocumented
features.

Outside of setting up the value sets and related values (these are the same value sets used everywhere
else), everything can be done from the one UDA form available in the seeded workflow of the Order
Management Super User responsibility.
Heres a condensed version of the steps required:
1. Create Value Sets
This works the same as with old school forms. If your UDI attributes are validated, you must create/define
value sets to reference them. All the standard value set types are supported (e.g. independent, table,
etc.).
2. Create the Attribute Group, Add Attributes
Note: This step takes 90% of the all the setup work and is somewhat like configuring a
descriptive flexfield.
Attributes are simply segments of the information you are going to collect, such a data type, length,
validation type etc.
The attribute group is, wait for it a grouping of attributes. An indefinite amount of them can be defined.
You can capture data from an attribute group on one order and data from a second attribute groupor a
combination of both groupson another order.
Attribute groups can be single-row or multi-row. With multi-row ones, you can capture more than one set
of attributes per sales order record and also choose a constraint based upon a defined single attribute or
a group.
For a motherboard item, you can create a multi-row attribute group called Operating Systems with the
OS name, version, and service pack attributes; then, associate multiple UDA records to the sales order
line. For its item, motherboard specification is an attribute group with a single value.
3. Associate Attribute Group to the Predefined Classification: ADMIN_DEFINED
This takes a couple of clicks per attribute group. Its pretty straightforward, as theres not an option in
Order Management to create additional classifications.
4. Create UDA Pages
UDA pages are one-to-one with attribute groups. This step also takes just a couple of clicks per attribute
group.
5. Create Database View

This step is optional. In a few clicks per attribute group, you can automatically create a database view
thats specific to the attribute group (i.e. for queries, reporting etc.).

Check back this Thursday for the second part of this blog post segment. If you have not done so
already, follow us below on Twitter, Facebook or LinkedIn to keep posted on the latest articles from
Oracle is Easy.

Getting UDA Information onto the Sales Order Record

There are two basic options here: the first one is to enter the data directly in the sales order entry forms;
and the second is to interface the information onto the sales order record.
Posted on January 8, 2015 by Scott Lehmkuhl
Option 1: Entering on the Sales Orders Forms
Unlike descriptive flexfields, the UDA attribute information cannot be entered directly from the formsbased screens. Instead, you must click the Actions button on the Sales Order Header or
Lines form and select the User Defined Attributes option. This brings up a separate OA
Framework (HTML) form labeled Order Header of Line Extension.
The first attribute group/form in sequence is displayed and other attribute groups/forms can be selected
for entry from a dropdown list. If the attribute group is multi-row, just click the Add Another Row
icon to make an additional record.
Note: Its fairly easy to navigate around and enter information, but its not nearly as
convenient and quick as tabbing through descriptive flexfield information.
Unfortunately, there does not appear to be another option to drill to this entry screen. There
is not a folder option to create the link as a button on the sales order line. Nor is there an
option to drill to the UDA form by right-clicking with the mouse. To even get to the UDA
entry screen, you must first click the Actions button and select the appropriate option.
With option two, all the information is written to additional related tables and not on the base Sales Order
Header and Line tables. They
are OE_ORDER_HEADERS_ALL_EXT_B andOE_ORDER_LINES_ALL_EXT_B and are only
populated if UDA data is captured.
Option 2: Entering through Order Import via Supported Interface Tables:
This test drive did not include actually importing the UDA information, but there are very simply additional
related header and line interface tables
OE_HEADERS_EXT_IFACE_ALL andOE_LINES_EXT_IFACE_ALLto interface the UDA information.

Viewing the UDA Information on Sales Order Records

The UDA information that is captured on the Sales Order Headers and Line form can only be viewed in
the same place on the form where its entered. You must click on the Actions button on theSales
Order Header or Lines form and select the User Defined Attributes option. From there, select the
appropriate attribute groups if more than one group is to be defined.
Its not quite as convenient as having the information as a field on the folder directly on the sales order
record However, if the attribute group is multi-row, you can see all the records together.