APPS.WF_ROUTE dependencies on WF_LOOKUPS

Line 152: from WF_LOOKUPS WL

148: meaning varchar2(80);
149: begin
150: select WL.MEANING
151: into meaning
152: from WF_LOOKUPS WL
153: where WL.LOOKUP_TYPE = GetLookupMeaning.ltype
154: and WL.LOOKUP_CODE = GetLookupMeaning.lcode;
155:
156: return(meaning);

Line 333: from WF_LOOKUPS

329: seq in varchar2)
330: as
331: cursor lookup_codes(p_lookup_type varchar2) is
332: select MEANING, LOOKUP_CODE
333: from WF_LOOKUPS
334: where LOOKUP_TYPE = p_lookup_type
335: order by MEANING;
336:
337: template varchar2(4000);

Line 647: from WF_LOOKUPS WL

643: -- Decode lookup meaning to code
644: begin
645: select WL.LOOKUP_CODE
646: into tvalue
647: from WF_LOOKUPS WL
648: where Wl.LOOKUP_TYPE = SetAttribute.attr_fmt
649: and MEANING = SetAttribute.attr_value;
650: exception
651: when no_data_found then

Line 898: WF_LOOKUPS WL

894: WRR.RULE_COMMENT,
895: WIT.DISPLAY_NAME TYPE_DISPLAY,
896: WM.SUBJECT
897: from WF_ROUTING_RULES WRR, WF_ITEM_TYPES_VL WIT, WF_MESSAGES_VL WM,
898: WF_LOOKUPS WL
899: where WRR.RULE_ID = nruleid
900: and WRR.MESSAGE_TYPE = WIT.NAME (+)
901: and WRR.MESSAGE_TYPE = WM.TYPE (+)
902: and WRR.MESSAGE_NAME = WM.NAME (+)

Line 1592: WF_LOOKUPS WL

1588: WM.DISPLAY_NAME MSG_DISPLAY,
1589: WM.SUBJECT,
1590: WL.MEANING ACTION_DISPLAY
1591: from WF_ROUTING_RULES WRR, WF_ITEM_TYPES_VL WIT, WF_MESSAGES_VL WM,
1592: WF_LOOKUPS WL
1593: where WRR.ROLE = username
1594: and WRR.MESSAGE_TYPE = WIT.NAME (+)
1595: and WRR.MESSAGE_TYPE = WM.TYPE (+)
1596: and WRR.MESSAGE_NAME = WM.NAME (+)

Line 1793: from WF_LOOKUPS WL,

1789: and NAME = 'RESULT';
1790: */
1791: select WL.MEANING
1792: into att_tvalue
1793: from WF_LOOKUPS WL,
1794: WF_MESSAGE_ATTRIBUTES_VL WMA,
1795: WF_ROUTING_RULES WRR,
1796: WF_ROUTING_RULE_ATTRIBUTES WRA
1797: where WRA.RULE_ID = rule.rule_id