eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.WF_ENGINE_BULK dependencies on WF_ENGINE

Line 1: package WF_ENGINE_BULK as

1: package WF_ENGINE_BULK as
2: /* $Header: wfengblks.pls 120.7 2006/10/04 21:38:40 dlam noship $ */
3: /*#
4: * Provides APIs that can be called by an application program
5: * to launch multiple work items at once in bulk and to set

Line 13: * @rep:category BUSINESS_ENTITY WF_ENGINE

9: * @rep:product OWF
10: * @rep:displayname Workflow Engine Bulk Processing
11: * @rep:lifecycle active
12: * @rep:compatibility S
13: * @rep:category BUSINESS_ENTITY WF_ENGINE
14: * @rep:ihelp FND/@wfebulk See the related online help
15: */
16: --
17: -- Constant values

Line 40: g_FailedItems WF_ENGINE_BULK.ItemKeyTabType;

36: -- commit for every n iterations
37: commit_frequency number := 500;
38:
39: -- Table of Failed Items
40: g_FailedItems WF_ENGINE_BULK.ItemKeyTabType;
41:
42: -- Table of Successful Items
43: g_SuccessItems WF_ENGINE_BULK.ItemKeyTabType;
44: --

Line 43: g_SuccessItems WF_ENGINE_BULK.ItemKeyTabType;

39: -- Table of Failed Items
40: g_FailedItems WF_ENGINE_BULK.ItemKeyTabType;
41:
42: -- Table of Successful Items
43: g_SuccessItems WF_ENGINE_BULK.ItemKeyTabType;
44: --
45: -- Table of failed attributes
46: g_FailedAttributes wf_engine.nametabtyp;
47:

Line 46: g_FailedAttributes wf_engine.nametabtyp;

42: -- Table of Successful Items
43: g_SuccessItems WF_ENGINE_BULK.ItemKeyTabType;
44: --
45: -- Table of failed attributes
46: g_FailedAttributes wf_engine.nametabtyp;
47:
48:
49: --
50: -- CreateProcess (PUBLIC)

Line 90: itemkeys in wf_engine_bulk.itemkeytabtype,

86: * @rep:compatibility S
87: * @rep:ihelp FND/@a_cpbulk See the related online help
88: */
89: procedure CreateProcess(itemtype in varchar2,
90: itemkeys in wf_engine_bulk.itemkeytabtype,
91: process in varchar2,
92: user_keys in wf_engine_bulk.userkeytabtype,
93: owner_roles in wf_engine_bulk.ownerroletabtype,
94: parent_itemtype in varchar2 default null,

Line 92: user_keys in wf_engine_bulk.userkeytabtype,

88: */
89: procedure CreateProcess(itemtype in varchar2,
90: itemkeys in wf_engine_bulk.itemkeytabtype,
91: process in varchar2,
92: user_keys in wf_engine_bulk.userkeytabtype,
93: owner_roles in wf_engine_bulk.ownerroletabtype,
94: parent_itemtype in varchar2 default null,
95: parent_itemkey in varchar2 default null,
96: parent_context in varchar2 default null,

Line 93: owner_roles in wf_engine_bulk.ownerroletabtype,

89: procedure CreateProcess(itemtype in varchar2,
90: itemkeys in wf_engine_bulk.itemkeytabtype,
91: process in varchar2,
92: user_keys in wf_engine_bulk.userkeytabtype,
93: owner_roles in wf_engine_bulk.ownerroletabtype,
94: parent_itemtype in varchar2 default null,
95: parent_itemkey in varchar2 default null,
96: parent_context in varchar2 default null,
97: masterdetail in boolean default null);

Line 115: * call either WF_ENGINE.CreateProcess() or

111: * once, identified by the specified item type and array of
112: * workflow item keys. The Workflow Engine locates the activity
113: * marked as a Start activity in the process definition and then
114: * defers that activity for each of the new work items. You must
115: * call either WF_ENGINE.CreateProcess() or
116: * WF_ENGINE_BULK.CreateProcess() to define the item type and item
117: * keys before calling WF_ENGINE_BULK.StartProcess(). You cannot use
118: * this API to start forced synchronous processes.
119: * @param itemtype Item Type

Line 116: * WF_ENGINE_BULK.CreateProcess() to define the item type and item

112: * workflow item keys. The Workflow Engine locates the activity
113: * marked as a Start activity in the process definition and then
114: * defers that activity for each of the new work items. You must
115: * call either WF_ENGINE.CreateProcess() or
116: * WF_ENGINE_BULK.CreateProcess() to define the item type and item
117: * keys before calling WF_ENGINE_BULK.StartProcess(). You cannot use
118: * this API to start forced synchronous processes.
119: * @param itemtype Item Type
120: * @param itemkeys Array of Item Keys

Line 117: * keys before calling WF_ENGINE_BULK.StartProcess(). You cannot use

113: * marked as a Start activity in the process definition and then
114: * defers that activity for each of the new work items. You must
115: * call either WF_ENGINE.CreateProcess() or
116: * WF_ENGINE_BULK.CreateProcess() to define the item type and item
117: * keys before calling WF_ENGINE_BULK.StartProcess(). You cannot use
118: * this API to start forced synchronous processes.
119: * @param itemtype Item Type
120: * @param itemkeys Array of Item Keys
121: * @rep:scope public

Line 128: itemkeys in wf_engine_bulk.itemkeytabtype);

124: * @rep:compatibility S
125: * @rep:ihelp FND/@a_spbulk See the related online help
126: */
127: procedure StartProcess(itemtype in varchar2,
128: itemkeys in wf_engine_bulk.itemkeytabtype);
129:
130:
131: -- FastForward (PUBLIC)
132: --

Line 158: * Engine first calls WF_ENGINE_BULK.CreateProcess() to create the

154: * The activity at which execution begins must be marked as a Start
155: * activity. However, it can have incoming transitions. The activity
156: * must be a direct child of the process in which execution of the
157: * work item begins. It cannot be part of a subprocess. The Workflow
158: * Engine first calls WF_ENGINE_BULK.CreateProcess() to create the
159: * new work items and then sets the Start activity for each work
160: * item to the specified status, either 'DEFERRED' or 'NOTIFIED'.
161: * You cannot use WF_ENGINE_BULK.FastForward() to start forced
162: * synchronous processes.

Line 161: * You cannot use WF_ENGINE_BULK.FastForward() to start forced

157: * work item begins. It cannot be part of a subprocess. The Workflow
158: * Engine first calls WF_ENGINE_BULK.CreateProcess() to create the
159: * new work items and then sets the Start activity for each work
160: * item to the specified status, either 'DEFERRED' or 'NOTIFIED'.
161: * You cannot use WF_ENGINE_BULK.FastForward() to start forced
162: * synchronous processes.
163: * @param itemtype Item Type
164: * @param itemkeys Array of Item Keys
165: * @param process Process Name

Line 179: itemkeys in wf_engine_bulk.itemkeytabtype,

175: * @rep:compatibility S
176: * @rep:ihelp FND/@a_ffbulk See the related online help
177: */
178: procedure FastForward(itemtype in varchar2,
179: itemkeys in wf_engine_bulk.itemkeytabtype,
180: process in varchar2,
181: activity in varchar2,
182: activityStatus in varchar2 default null,
183: parent_itemtype in varchar2 default null,

Line 218: itemkeys in Wf_Engine_Bulk.ItemKeyTabType,

214: * @rep:ihelp FND/@a_siatbulk See the related online help
215: */
216: procedure SetItemAttrText(
217: itemtype in varchar2,
218: itemkeys in Wf_Engine_Bulk.ItemKeyTabType,
219: anames in Wf_Engine.NameTabTyp,
220: avalues in Wf_Engine.TextTabTyp);
221:
222: -- SetItemAttrNumber (PUBLIC)

Line 219: anames in Wf_Engine.NameTabTyp,

215: */
216: procedure SetItemAttrText(
217: itemtype in varchar2,
218: itemkeys in Wf_Engine_Bulk.ItemKeyTabType,
219: anames in Wf_Engine.NameTabTyp,
220: avalues in Wf_Engine.TextTabTyp);
221:
222: -- SetItemAttrNumber (PUBLIC)
223: -- Set the values of an array of number item attribute.

Line 220: avalues in Wf_Engine.TextTabTyp);

216: procedure SetItemAttrText(
217: itemtype in varchar2,
218: itemkeys in Wf_Engine_Bulk.ItemKeyTabType,
219: anames in Wf_Engine.NameTabTyp,
220: avalues in Wf_Engine.TextTabTyp);
221:
222: -- SetItemAttrNumber (PUBLIC)
223: -- Set the values of an array of number item attribute.
224: -- Unlike SetItemAttrText(), it stores the values directly.

Line 252: itemkeys in Wf_Engine_Bulk.ItemKeyTabType,

248: * @rep:ihelp FND/@a_sianbulk See the related online help
249: */
250: procedure SetItemAttrNumber(
251: itemtype in varchar2,
252: itemkeys in Wf_Engine_Bulk.ItemKeyTabType,
253: anames in Wf_Engine.NameTabTyp,
254: avalues in Wf_Engine.NumTabTyp);
255:
256: -- SetItemAttrDate (PUBLIC)

Line 253: anames in Wf_Engine.NameTabTyp,

249: */
250: procedure SetItemAttrNumber(
251: itemtype in varchar2,
252: itemkeys in Wf_Engine_Bulk.ItemKeyTabType,
253: anames in Wf_Engine.NameTabTyp,
254: avalues in Wf_Engine.NumTabTyp);
255:
256: -- SetItemAttrDate (PUBLIC)
257: -- Set the values of an array of date item attribute.

Line 254: avalues in Wf_Engine.NumTabTyp);

250: procedure SetItemAttrNumber(
251: itemtype in varchar2,
252: itemkeys in Wf_Engine_Bulk.ItemKeyTabType,
253: anames in Wf_Engine.NameTabTyp,
254: avalues in Wf_Engine.NumTabTyp);
255:
256: -- SetItemAttrDate (PUBLIC)
257: -- Set the values of an array of date item attribute.
258: -- Unlike SetItemAttrText(), it stores the values directly.

Line 285: itemkeys in Wf_Engine_Bulk.ItemKeyTabType,

281: * @rep:ihelp FND/@a_siadbulk See the related online help
282: */
283: procedure SetItemAttrDate(
284: itemtype in varchar2,
285: itemkeys in Wf_Engine_Bulk.ItemKeyTabType,
286: anames in Wf_Engine.NameTabTyp,
287: avalues in Wf_Engine.DateTabTyp);
288:
289: end WF_ENGINE_BULK;

Line 286: anames in Wf_Engine.NameTabTyp,

282: */
283: procedure SetItemAttrDate(
284: itemtype in varchar2,
285: itemkeys in Wf_Engine_Bulk.ItemKeyTabType,
286: anames in Wf_Engine.NameTabTyp,
287: avalues in Wf_Engine.DateTabTyp);
288:
289: end WF_ENGINE_BULK;

Line 287: avalues in Wf_Engine.DateTabTyp);

283: procedure SetItemAttrDate(
284: itemtype in varchar2,
285: itemkeys in Wf_Engine_Bulk.ItemKeyTabType,
286: anames in Wf_Engine.NameTabTyp,
287: avalues in Wf_Engine.DateTabTyp);
288:
289: end WF_ENGINE_BULK;

Line 289: end WF_ENGINE_BULK;

285: itemkeys in Wf_Engine_Bulk.ItemKeyTabType,
286: anames in Wf_Engine.NameTabTyp,
287: avalues in Wf_Engine.DateTabTyp);
288:
289: end WF_ENGINE_BULK;