DBA Data[Home] [Help]

PACKAGE: APPS.PAY_FLOW_REQUESTS_PKG

Source


1 PACKAGE PAY_FLOW_REQUESTS_PKG AUTHID CURRENT_USER AS
2 /* $Header: pyprflow.pkh 120.1.12020000.1 2013/03/22 08:07:50 nvankadh noship $ */
3 /*
4  ******************************************************************
5  *                                                                *
6  *  Copyright (C) 1993 Oracle Corporation UK Ltd.,                *
7  *                   Chertsey, England.                           *
8  *                                                                *
9  *  All rights reserved.                                          *
10  *                                                                *
11  *  This material has been provided pursuant to an agreement      *
12  *  containing restrictions on its use.  The material is also     *
13  *  protected by copyright law.  No part of this material may     *
14  *  be copied or distributed, transmitted or transcribed, in      *
15  *  any form or by any means, electronic, mechanical, magnetic,   *
16  *  manual, or otherwise, or disclosed to third parties without   *
17  *  the express written permission of Oracle Corporation UK Ltd,  *
18  *  Oracle Park, Bittams Lane, Guildford Road, Chertsey, Surrey,  *
19  *  England.                                                      *
20  *                                                                *
21  ******************************************************************
22 
23  Name        : PAY_FLOW_REQUESTS_PKG
24  Description : Contains the procedures used by the process-flow data
25                model. This package is very generic and can be used for multiple
26 	       flow-process designs. Only the data model needs to
27 	       be changed for the new process flows. The procedures in this
28 	       pacakge are very generic and don't refer to any flow in
29 	       particular. Any future changes to the procedures should
30 	       also be done such that they apply to all the process flows
31 	       using them and should not be specific for any process flow.
32 
33  ======================================================================
34 
35 
36  Change List
37  ===========
38 
39  Version Date       Author    ER/CR No. Description of Change
40  -------+---------+----------+---------+-------------------------------
41  115.0   03/03/08  ckesanap   6820127   Created the file.
42  ----------------------------------------------------------------------
43 */
44 
45 /*--------------------------  RECORD types ---------------------------*/
46 
47 type REQUEST_DETAIL IS RECORD (
48               asg_action NUMBER(15,0),
49               request_id NUMBER(15,0) );
50 TYPE REQUEST_DETAIL_ARRAY IS TABLE OF REQUEST_DETAIL index by BINARY_INTEGER;
51 
52 
53 --
54 -- ----------------------------------------------------------------------------
55 -- |-----------------------< create_request >-------------------|
56 -- ----------------------------------------------------------------------------
57 --
58 -- Description:
59 -- This procedure creates a request in the data model - pay_process_requests table
60 -- to be picked up for processing
61 --
62 -- ----------------------------------------------------------------------------
63 procedure create_request( p_process_flow_id in number,
64                            p_no_of_params in number,
65                            p_asg_action in number,
66                            p_asg_set_var_id in number,
67                            p_param_details in out NOCOPY PARAM_DETAIL_ARRAY,
68                            p_process_request_id OUT NOCOPY number
69                            );
70 
71 -- ----------------------------------------------------------------------------
72 -- |------------------------------< invoke_request>----------------------------|
73 -- ----------------------------------------------------------------------------
74 --
75 -- Description:
76 -- This procedure invokes a flow for all the  requests in pay_process_requests.
77 --  The individual processes in the flow are invoked sequentially
78 --    THIS SHOULD BE A CONCURRENT REQUEST which can handle many assignments
79 --    in parallel.
80 --
81 -- ----------------------------------------------------------------------------
82 procedure invoke_request (errbuf  OUT NOCOPY  VARCHAR2,
83                           retcode OUT NOCOPY  NUMBER,
84                           p_request_id in number);
85 
86 -- ----------------------------------------------------------------------------
87 -- |-------------------------< update_process_status >------------------------|
88 -- ----------------------------------------------------------------------------
89 --
90 -- Description:
91 -- This function updates the PAY_PROCESS_REQUESTS table with the current status
92 -- and request_id of the concurrent request
93 --
94 -- ----------------------------------------------------------------------------
95 procedure update_process_status(p_process_request_id in number,
96                                 p_fnd_request_id  in number);
97 
98 -- ----------------------------------------------------------------------------
99 -- |-----------------------------< execute_request >---------------------------|
100 -- ----------------------------------------------------------------------------
101 --
102 -- Description:
103 -- This procedure invokes the request and then updates the status of the
104 --  request in PAY_PROCESS_REQUESTS
105 --
106 -- ----------------------------------------------------------------------------
107 procedure execute_request(p_request_id in number);
108 
109 -- ----------------------------------------------------------------------------
110 -- |-----------------------------< purge_requests >---------------------------|
111 -- ----------------------------------------------------------------------------
112 --
113 -- Description:
114 -- This procedure is called from the UI and purges the completed requests and
115 -- associated parameter values from the tables PAY_PROCESS_REQUESTS and
116 -- PAY_PARA_SET_VAR_VALUES.
117 --
118 -- ----------------------------------------------------------------------------
119 procedure purge_requests(p_fnd_request_id in number default null,
120                          p_message OUT NOCOPY varchar2);
121 
122 -- ----------------------------------------------------------------------------
123 -- |-----------------------------< cancel_request >---------------------------|
124 -- ----------------------------------------------------------------------------
125 --
126 -- Description:
127 -- This procedure is called from the UI and cancels the pending requests.
128 --
129 -- ----------------------------------------------------------------------------
130 procedure cancel_request(p_fnd_request_id in number,
131                          p_message out NOCOPY varchar2);
132 
133 -- ----------------------------------------------------------------------------
134 -- |-----------------------------< insert_child_request >---------------------|
135 -- ----------------------------------------------------------------------------
136 --
137 -- Description:
138 -- This procedure inserts the child requests in the pay_process_requests table.
139 -- This can be called from the wrapper packages of individual processes to
140 -- update the table before doing any other processing post request completion.
141 --
142 -- ----------------------------------------------------------------------------
143 procedure insert_child_request(p_assignment_action_id in number,
144                                p_fnd_request_id in number);
145 --
146 
147 END PAY_FLOW_REQUESTS_PKG;