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.PO_INTERFACE_ERRORS_SV1 dependencies on PO_INTERFACE_ERRORS

Line 1: PACKAGE BODY PO_INTERFACE_ERRORS_SV1 AS

1: PACKAGE BODY PO_INTERFACE_ERRORS_SV1 AS
2: /* $Header: POXPIIEB.pls 115.17 2004/03/05 23:30:53 mbhargav ship $ */
3:
4: -- Read the profile option that enables/disables the debug log
5: g_po_pdoi_write_to_file VARCHAR2(1) := NVL(FND_PROFILE.VALUE('PO_PDOI_WRITE_TO_FILE'),'N');

Line 11: -- insert_po_interface_errors(). It is part of the refactoring done in the

7: --
8: -- Private function to this file
9: -- This function is a bare wrapper to the insert statement. It would be called
10: -- from the public procedures handle_interface_errors_msg() and
11: -- insert_po_interface_errors(). It is part of the refactoring done in the
12: -- PDOI-Grants Integration Project.
13: PROCEDURE insert_po_interface_errors_msg(
14: X_interface_type IN VARCHAR2,
15: X_Interface_Header_ID IN NUMBER,

Line 13: PROCEDURE insert_po_interface_errors_msg(

9: -- This function is a bare wrapper to the insert statement. It would be called
10: -- from the public procedures handle_interface_errors_msg() and
11: -- insert_po_interface_errors(). It is part of the refactoring done in the
12: -- PDOI-Grants Integration Project.
13: PROCEDURE insert_po_interface_errors_msg(
14: X_interface_type IN VARCHAR2,
15: X_Interface_Header_ID IN NUMBER,
16: X_Interface_Line_Id IN NUMBER,
17: X_Interface_Dist_Id IN NUMBER,

Line 26: -- it was present in the public function insert_po_interface_errors(). That

22: X_batch_id IN NUMBER)
23: IS
24:
25: -- Moved the AUTONOMOUS_TRANSACTION inside this new procedure. Prior to this
26: -- it was present in the public function insert_po_interface_errors(). That
27: -- function, in turn, now calls this procedure.
28:
29: -- Bug 2705777. Making this an autonomous transaction to avoid rollback issues
30: -- with the main transaction's savepoints.

Line 37: insert into po_interface_errors(Interface_Type,

33: X_progress varchar2(30) := null;
34: BEGIN
35: X_progress := '010';
36:
37: insert into po_interface_errors(Interface_Type,
38: Interface_Transaction_Id,
39: column_name,
40: table_name,
41: error_message,

Line 59: po_interface_errors_s.nextval,

55: Program_Update_date,
56: Batch_Id)
57: VALUES
58: (X_interface_type,
59: po_interface_errors_s.nextval,
60: X_column_name,
61: X_table_name,
62: X_Error_Message_text,
63: X_Error_Message_name,

Line 84: po_message_s.sql_error('insert_po_interface_errors_msg', X_progress,

80: commit;
81:
82: EXCEPTION
83: WHEN OTHERS THEN
84: po_message_s.sql_error('insert_po_interface_errors_msg', X_progress,
85: sqlcode);
86: RAISE;
87: END insert_po_interface_errors_msg;
88: --

Line 87: END insert_po_interface_errors_msg;

83: WHEN OTHERS THEN
84: po_message_s.sql_error('insert_po_interface_errors_msg', X_progress,
85: sqlcode);
86: RAISE;
87: END insert_po_interface_errors_msg;
88: --
89:
90: /*==================================================================*/
91: PROCEDURE handle_interface_errors(X_interface_type IN VARCHAR2,

Line 137: X_compl_code := po_interface_errors_sv1.insert_po_interface_errors(

133: -- call function po_interface_error_insert to insert a new error record
134: -- in an autonomous transaction. Therefore, all error messages will be
135: -- committed to the db without interfering with the main transaction's
136: -- savepoints
137: X_compl_code := po_interface_errors_sv1.insert_po_interface_errors(
138: X_interface_type,
139: X_Error_type, --
140: X_Batch_id,
141: X_Interface_Header_ID,

Line 169: FUNCTION NAME: insert_po_interface_errors()

165:
166: /* ========================================================================
167:
168:
169: FUNCTION NAME: insert_po_interface_errors()
170:
171: =========================================================================*/
172:
173: FUNCTION insert_po_interface_errors(X_interface_type IN VARCHAR2,

Line 173: FUNCTION insert_po_interface_errors(X_interface_type IN VARCHAR2,

169: FUNCTION NAME: insert_po_interface_errors()
170:
171: =========================================================================*/
172:
173: FUNCTION insert_po_interface_errors(X_interface_type IN VARCHAR2,
174: X_Error_type IN VARCHAR2,
175: X_Batch_id IN NUMBER,
176: X_Interface_Header_ID IN NUMBER,
177: X_Interface_Line_Id IN NUMBER,

Line 262: insert_po_interface_errors_msg(X_interface_type,

258:
259: --
260: -- Refactored this code to call this private function. This private function
261: -- is also called from the new public procedure handle_interface_errors_msg()
262: insert_po_interface_errors_msg(X_interface_type,
263: X_interface_header_id,
264: X_interface_line_id,
265: X_Interface_Dist_Id,
266: X_Error_Message,

Line 277: po_message_s.sql_error('insert_po_interface_errors', X_progress, sqlcode);

273: return('0');
274:
275: EXCEPTION
276: WHEN OTHERS THEN
277: po_message_s.sql_error('insert_po_interface_errors', X_progress, sqlcode);
278: ROLLBACK;
279: raise;
280: END insert_po_interface_errors;
281:

Line 280: END insert_po_interface_errors;

276: WHEN OTHERS THEN
277: po_message_s.sql_error('insert_po_interface_errors', X_progress, sqlcode);
278: ROLLBACK;
279: raise;
280: END insert_po_interface_errors;
281:
282: -- Bug 2705777. Removed procedures rollback_changes and rollback_line_changes
283:
284: --

Line 308: -- call function insert_po_interface_errors_msg to insert a new error record

304: X_header_processable_flag := 'N';
305: END IF;
306:
307: X_progress := '010';
308: -- call function insert_po_interface_errors_msg to insert a new error record
309: insert_po_interface_errors_msg(X_interface_type,
310: X_Interface_Header_ID,
311: X_Interface_Line_Id ,
312: X_Interface_Dist_Id,

Line 309: insert_po_interface_errors_msg(X_interface_type,

305: END IF;
306:
307: X_progress := '010';
308: -- call function insert_po_interface_errors_msg to insert a new error record
309: insert_po_interface_errors_msg(X_interface_type,
310: X_Interface_Header_ID,
311: X_Interface_Line_Id ,
312: X_Interface_Dist_Id,
313: X_Error_Message_text,

Line 325: END PO_INTERFACE_ERRORS_SV1;

321: RAISE;
322: END handle_interface_errors_msg;
323: --
324:
325: END PO_INTERFACE_ERRORS_SV1;