APPS.PO_ACTION_HISTORY_SV dependencies on PO_ACTION_HISTORY

Line 1: PACKAGE BODY PO_ACTION_HISTORY_SV AS

1: PACKAGE BODY PO_ACTION_HISTORY_SV AS
2: -- $Header: POXACTHB.pls 120.0.12020000.3 2013/02/10 18:36:21 vegajula ship $
3:
4: G_PKG_NAME CONSTANT varchar2(30) := 'PO_ACTION_HISTORY_SV';
5:

Line 4: G_PKG_NAME CONSTANT varchar2(30) := 'PO_ACTION_HISTORY_SV';

1: PACKAGE BODY PO_ACTION_HISTORY_SV AS
2: -- $Header: POXACTHB.pls 120.0.12020000.3 2013/02/10 18:36:21 vegajula ship $
3:
4: G_PKG_NAME CONSTANT varchar2(30) := 'PO_ACTION_HISTORY_SV';
5:
6: g_log_head CONSTANT VARCHAR2(50) := 'po.plsql.'|| G_PKG_NAME || '.' ;
7:
8: -- Read the profile option that enables/disables the debug log

Line 32: -- PO_ACTION_HISTORY

28: --Name: update_action_history
29: --Pre-reqs:
30: -- None.
31: --Modifies:
32: -- PO_ACTION_HISTORY
33: --Locks:
34: -- None.
35: --Function:
36: -- Updates the action history entry for documents that currently have

Line 47: -- PO_ACTION_HISTORY.object_type_code

43: -- PO_RELEASES_ALL.po_release_id
44: -- PO_REQUISITION_HEADERS_ALL.requisition_header_id
45: --p_doc_type_tbl
46: -- Document type corresponding to the IDs.
47: -- PO_ACTION_HISTORY.object_type_code
48: --p_action_code
49: -- The action with which to fill in the NULL entry.
50: -- PO_ACTION_HISTORY.action_code
51: --p_employee_id

Line 50: -- PO_ACTION_HISTORY.action_code

46: -- Document type corresponding to the IDs.
47: -- PO_ACTION_HISTORY.object_type_code
48: --p_action_code
49: -- The action with which to fill in the NULL entry.
50: -- PO_ACTION_HISTORY.action_code
51: --p_employee_id
52: -- The HR employee_id with which to record the action.
53: -- This id should correspond to PER_ALL_PEOPLE_F.person_id.
54: -- If NULL is passed, the employee_id will be retrieved

Line 115: UPDATE PO_ACTION_HISTORY POAH

111:
112: -- We've got all the data we need, so update the table.
113:
114: FORALL i IN 1 .. p_doc_id_tbl.COUNT
115: UPDATE PO_ACTION_HISTORY POAH
116: SET
117: POAH.last_update_date = SYSDATE
118: , POAH.last_updated_by = l_user_id
119: , POAH.action_code = p_action_code

Line 157: -- PO_ACTION_HISTORY

153: --Name: insert_action_history
154: --Pre-reqs:
155: -- None.
156: --Modifies:
157: -- PO_ACTION_HISTORY
158: --Locks:
159: -- None.
160: --Function:
161: -- Creates the specified action history entries.

Line 171: -- PO_ACTION_HISTORY.object_type_code

167: -- PO_RELEASES_ALL.po_release_id
168: -- PO_REQUISITION_HEADERS_ALL.requisition_header_id
169: --p_doc_type_tbl
170: -- Document type corresponding to the IDs.
171: -- PO_ACTION_HISTORY.object_type_code
172: --p_doc_subtype_tbl
173: -- Document subtype.
174: -- PO_HEADERS_ALL.type_lookup_code
175: -- PO_RELEASES_ALL.release_type

Line 184: -- PO_ACTION_HISTORY.action_code

180: -- PO_RELEASES_ALL.revision_num
181: -- These are NULL for Reqs.
182: --p_action_code_tbl
183: -- The actions to record.
184: -- PO_ACTION_HISTORY.action_code
185: -- The ordering of these actions are important for the
186: -- sequence_num of the action history entry.
187: -- SUBMIT should come before the other action.
188: --p_employee_id

Line 270: INSERT INTO PO_ACTION_HISTORY

266: -- The NVL, MAX are arranged to return a row with 0 as the sequence_num
267: -- when no entries exist for the doc.
268:
269: FORALL i IN 1 .. p_doc_id_tbl.COUNT
270: INSERT INTO PO_ACTION_HISTORY
271: ( object_id
272: , object_type_code
273: , object_sub_type_code
274: , sequence_num

Line 302: PO_ACTION_HISTORY POAH

298: , p_doc_revision_num_tbl(i)
299: , l_login_id
300: , SYSDATE
301: FROM
302: PO_ACTION_HISTORY POAH
303: WHERE POAH.object_id = p_doc_id_tbl(i)
304: AND POAH.object_type_code = p_doc_type_tbl(i)
305: ;
306:

Line 441: END PO_ACTION_HISTORY_SV;

437:
438:
439:
440:
441: END PO_ACTION_HISTORY_SV;