R12.2.4 ++++aaaaaaaaaaa
R12.2.4 ++++aaaaaaaaaaa
R12.2.4 ++++aaaaaaaaaaa
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.