APPS.FEM_DIMENSION_UTIL_PKG dependencies on FEM_OBJECT_CATALOG_B

Line 528: stores that value into FEM_OBJECT_CATALOG_B.local_vs_combo_id.

524:
525: For example - you create a Mapping Rule - the UI should call this
526: function to identify the Global Combo for that mapping rule based upon
527: the ledger under which it was created. It then
528: stores that value into FEM_OBJECT_CATALOG_B.local_vs_combo_id.
529:
530: When you go to open that rule under a different ledger, the UI compares
531: the Global Combo that returns for the new Ledger with the global combo
532: stored in FEM_OBJECT_CATALOG_B.local_vs_combo_id for the rule being

Line 532: stored in FEM_OBJECT_CATALOG_B.local_vs_combo_id for the rule being

528: stores that value into FEM_OBJECT_CATALOG_B.local_vs_combo_id.
529:
530: When you go to open that rule under a different ledger, the UI compares
531: the Global Combo that returns for the new Ledger with the global combo
532: stored in FEM_OBJECT_CATALOG_B.local_vs_combo_id for the rule being
533: opened.
534:
535: There are 2 signatures for this function - one is OA framework
536: compatible while the other is not.

Line 989: FROM fem_object_catalog_b

985:
986: BEGIN
987: SELECT local_vs_combo_id
988: INTO v_rule_vs_id
989: FROM fem_object_catalog_b
990: WHERE object_id = p_object_id;
991: EXCEPTION
992: WHEN no_data_found THEN
993: RETURN 'N';