APPS.OE_SCH_FIRM_CONC dependencies on WF_ENGINE

Line 118: -- and notified status, call wf_engine to complete the activity.

114: BEGIN
115:
116: -- When user does not specifiy any parameters, we drive the scheduling
117: -- through workflow. Pick up all the lines which are schedule eligible
118: -- and notified status, call wf_engine to complete the activity.
119:
120: -- If value is passed through any of the parameters, then get the header
121: -- and line
122: -- records and call wf_engine.

Line 122: -- records and call wf_engine.

118: -- and notified status, call wf_engine to complete the activity.
119:
120: -- If value is passed through any of the parameters, then get the header
121: -- and line
122: -- records and call wf_engine.
123:
124: oe_debug_pub.add('Starting Progress Firm: ' , 1 ) ;
125:
126: IF OE_CODE_CONTROL.CODE_RELEASE_LEVEL > '110509' THEN

Line 171: wf_engine.CompleteActivityInternalName

167:
168: IF l_debug_level > 0 THEN
169: oe_debug_pub.add( 'COMPLETING ACTIVITY FOR : ' || K.ITEM_KEY ,1);
170: END IF;
171: wf_engine.CompleteActivityInternalName
172: ('OEOL',
173: k.item_key,
174: 'FIRM_ELIGIBLE',
175: 'COMPLETE');

Line 401: wf_engine.CompleteActivityInternalName

397: IF l_debug_level > 0 THEN
398: oe_debug_pub.add( 'COMPLETING ACTIVITY FOR : ' || v_line_id ,1);
399: END IF;
400:
401: wf_engine.CompleteActivityInternalName
402: ('OEOL',
403: to_char(v_line_id),
404: 'FIRM_ELIGIBLE',
405: 'COMPLETE');