How to fetch UDA using SQL?
SELECT oeh.order_number,
ohx.c_ext_attr1
FROM apps.oe_order_headers_all oeh,
ont.OE_ORDER_HEADERS_ALL_EXT_B ohx
WHERE order_number IN ('57088463','57088466')
AND oeh.header_id = ohx.header_id
How to fetch UDA using SQL based on attribute Group?
Cons of UDA
1.Navigation to enter/update UDA is time consuming and results in more data entry time for users.
2.Validations based on the attribute entered is cumbersome, to do any validations, we need to change the underlying OAF page and it is too costly.
SELECT oeh.order_number,
ohx.c_ext_attr1
FROM apps.oe_order_headers_all oeh,
ont.OE_ORDER_HEADERS_ALL_EXT_B ohx
WHERE order_number IN ('57088463','57088466')
AND oeh.header_id = ohx.header_id
How to fetch UDA using SQL based on attribute Group?
SELECT oeh.order_number,
ohx.c_ext_attr1
FROM apps.oe_order_headers_all
oeh,
ont.OE_ORDER_HEADERS_ALL_EXT_B ohx,
apps.EGO_FND_DSC_FLX_CTX_EXT egex
WHERE --order_number IN ('57088463','57088466')
--AND
oeh.header_id = ohx.header_id
AND
egex.descriptive_flex_context_code='PNET_ORDER'
AND egex.attr_group_id =ohx.attr_group_id
Pros of UDA
1.Best feature which provides place holder for custom attributes and avoids too many custom attribute forms.
2.Custom Value set can be attached to the UDA.
3.Attribute is updateable even if the line status is in closed status, this is not the case in DFF.
2.Custom Value set can be attached to the UDA.
3.Attribute is updateable even if the line status is in closed status, this is not the case in DFF.
Cons of UDA
1.Navigation to enter/update UDA is time consuming and results in more data entry time for users.
2.Validations based on the attribute entered is cumbersome, to do any validations, we need to change the underlying OAF page and it is too costly.
No comments:
Post a Comment