List Price vs Item Cost vs Unit Selling Price - Oracle

List Price vs Item Cost vs Unit Selling Price - Oracle

List Price - OM Sales Order Screen	List price is the price of the item which gets defaulted from the price list
Selling Price	Unit selling price is the price which gets reflected once the discount which is mentioned in the modifier, gets applied. So, (List price-discounts applied ) = unit selling price.
Item Cost	the total expenditure to manufacture and package the product
Profit	List Price - Item Cost
List Price - Item Master - Purchasing	The value that Oracle Purchasing uses as the default price on a purchase order, requisition, RFQ, or quotation.

Oracle Order Management - UDA - User Defined Attributes - R12.2 Feature

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?

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.

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.

Oracle OM Order Type which has enabled Credit Check - Query

SELECT ottl.name,
  otta.end_date_active,
  otta.entry_credit_check_rule_id
FROM apps.oe_transaction_types_all otta,
  apps.oe_transaction_types_tl ottl
WHERE transaction_type_code     ='ORDER'
AND entry_credit_check_rule_id IS NOT NULL
AND (end_date_active           IS NULL
OR end_date_active              > sysdate)
AND otta.transaction_type_id    = ottl.transaction_type_id
ORDER BY ottl.name ASC