1 PACKAGE IBY_PAYMENT_MANAGER_PKG AUTHID CURRENT_USER AS
2 /* $Header: ibypayms.pls 120.0 2010/09/03 16:02:16 svinjamu noship $ */
3
4 /*New parameters for : 10022548 */
5 TYPE snapshot_count_type IS RECORD (
6 l_need_action NUMBER,
7 l_processing NUMBER,
8 l_terminated NUMBER,
9 l_errors NUMBER,
10 l_completed NUMBER
11 );
12 /*End of New parameters for : 10022548 */
13 TYPE snapshot_count_t IS TABLE OF snapshot_count_type ;
14
15
16 /*-----------------------------------------------------------------------------------------
17 | FUNCTION - get_psr_snapshot_count PIPELINED.
18 |
19 | DESCRIPTION - This function is designed for the Payables Payment Manager
20 | Home Page . The function returns the total count of Payment
21 | Process Requests with a particular Status or a combination
22 | of Payment Process Request Statuses that map to a particular
23 | snapshot code
24 |
25 | SNAPSHOT CODE STATUS
26 | ------------- ------------------------------------------------
27 | NEED_ACTION_BY_ME AP:
28 | 'REVIEW', 'MISSING RATES'
29 | IBY:
30 | 'INFORMATION_REQUIRED'
31 | 'PENDING_REVIEW_DOC_VAL_ERRORS',
32 | 'PENDING_REVIEW_PMT_VAL_ERRORS',
33 | 'PENDING_REVIEW'
34 |
35 | PROCESSING AP:
36 | 'UNSTARTED', 'SELECTING', 'CANCELING',
37 | 'CALCULATING', 'SELECTED'
38 | IBY:
39 | 'INSERTED', 'SUBMITTED',
40 | 'ASSIGNMENT_COMPLETE','DOCUMENTS_VALIDATED',
41 | 'RETRY_DOCUMENT_VALIDATION',
42 | 'RETRY_PAYMENT_CREATION'
43 |
44 | USER_TERMINATED AP:
45 | 'CANCELED' , 'CANCELLED NO PAYMENTS'
46 | IBY:
47 | 'TERMINATED'
48 |
49 | PROGRAM_ERRORS IBY:
50 | 'PENDING_REVIEW_DOC_VAL_ERRORS'
51 | 'PENDING_REVIEW_PMT_VAL_ERRORS'
52 |
53 | COMPLETED IBY:
54 | 'PAYMENTS_CREATED'
55 |
56 | TOTAL COUNT(*) IN AP
57 |
58 |===========================================================================================
59 |Understanding PIPELINED FUNCTION:
60 |-----------------------------------
61 |PIPELINED functions are piece of code that can be used for querying SQL.
62 |Basically, when you would like a PLSQL routine to be the source
63 |of data -- instead of a table -- you would use a pipelined function.
64 |PIPELINED functions will operate like a table.
65 |Using PL/SQL table functions can significantly lower the over-head of
66 |doing such transformations. PL/SQL table functions accept and return
67 |multiple rows, delivering them as they are ready rather than all at once,
68 |and can be made to execute as parallel operations.
69 |
70 -----------------------------------------------------------------------------------------
71 */
72 FUNCTION get_psr_snapshot_pipe RETURN snapshot_count_t PIPELINED;
73
74 --Function check_user_access(p_pay_instruction_id IN Number) RETURN VARCHAR2;
75
76 FUNCTION check_org_access( p_payment_service_request_id IN NUMBER)
77 RETURN VARCHAR2;
78
79 END IBY_PAYMENT_MANAGER_PKG;
[Home] [Help]