DBA Data[Home] [Help]

PACKAGE: APPS.WIP_RESERVATIONS_GRP

Source


1 PACKAGE wip_reservations_grp  AS
2 /* $Header: wipsogps.pls 120.1 2005/09/28 04:26 mraman noship $ */
3 
4 /***************************************************************************
5 |         PROCEDURE get_available_supply_demand()
6 |***************************************************************************
7 |
8 | The purpose of this API is to get the final availability of the
9 | document line for which the reservation is being created/ modified.
10 | This procedure will be called by the inventory APIs to get the expected
11 | availability at the document level.
12 |
13 | Various Parameters enlisted
14 |
15 |  x_return_status  -	Returns the status to the calling API
16 |
17 |  x_msg_count 	    -   Returns the message count in the stack
18 |
19 |  x_msg_data	    -   Returns the messages from the stack
20 |
21 |  x_available_quantity	 Returns the final available quantity on the
22 |                        document line for which the reservation is
23 			 being made
24 |
25 | x_source_uom_code	  Returns the UOM of the source document
26 |
27 | x_source_primary_uom_code	Returns the primary UOM of the
28 				source document
29 |
30 | p_organization_id   -	Organization id of the document to be
31 			validated
32 |
33 | p_item_id	      - Inventory item id of the document to be validated
34 |
35 | p_revision	      - Revision of the item
36 |
37 | p_lot_number	      - Lot number of the item
38 |
39 | p_subinventory_code  - Subinventory code
40 |
41 | p_locator_id	       - Locator id of the subinventory if the
42 |                        subinventory is locator controlled
43 |
44 | p_supply_demand_code	     - The action determines whether the
45 				calling API
46 |                              is querying for a supply or demand
47 |
48 | p_supply_demand_type_id   - This holds the demand type for which
49 			      the availability is to be checked
50 | p_supply_demand_header_id - This holds the header information of
51 |			      the demand document for which the
52 			      availability is to be checked
53 | p_supply_demand_line_id   - This holds the line information of
54 			      the demand document for which the
55 			      availability is to be checked
56 | p_supply_demand_line_detail	- This holds the line information of
57                                   the demand document for which
58 				  the availability is to be checked
59 | p_lpn_id	      -    This is the lpn for the supply document
60 			   for which the availability is going to
61 			   be computed
62 | P_project_id	      -	   This holds the project id for the
63 			   demand document
64 | P_task_id	      -    This holds the task id for the
65 |			   demand document
66 | p_api_version_number -   Api version number
67 |
68 | p_init_msg_lst      -  	To initialize message list or not
69 |
70 | p_return_txn        -    To differentiate between return transaction and
71 |                          Other transactions
72 |
73 |
74 ***************************************************************************/
75 
76 PROCEDURE get_available_supply_demand (
77  p_api_version_number     		IN     	NUMBER default 1.0
78 , p_init_msg_lst             		IN      VARCHAR2
79 ,x_return_status            		OUT    	NOCOPY VARCHAR2
80 , x_msg_count                		OUT    	NOCOPY NUMBER
81 , x_msg_data                 		OUT    	NOCOPY VARCHAR2
82 , x_available_quantity			OUT      NOCOPY NUMBER
83 , x_source_primary_uom_code	        OUT      NOCOPY VARCHAR2
84 , x_source_uom_code			OUT      NOCOPY VARCHAR2
85 , p_organization_id			IN 	NUMBER default null
86 , p_item_id				IN 	NUMBER default null
87 , p_revision				IN 	VARCHAR2 default null
88 , p_lot_number			        IN	VARCHAR2 default null
89 , p_subinventory_code		        IN	VARCHAR2 default null
90 , p_locator_id			        IN 	NUMBER default null
91 , p_supply_demand_code		        IN	NUMBER
92 , p_supply_demand_type_id		IN	NUMBER
93 , p_supply_demand_header_id		IN	NUMBER
94 , p_supply_demand_line_id		IN	NUMBER
95 , p_supply_demand_line_detail		IN	NUMBER default FND_API.G_MISS_NUM
96 , p_lpn_id				IN	NUMBER default FND_API.G_MISS_NUM
97 , p_project_id			        IN	NUMBER default null
98 , p_task_id				IN	NUMBER default null
99 , p_return_txn                          IN      NUMBER default  0
100 ) ;
101 
102 /***************************************************************************
103 |         PROCEDURE validate_supply_demand ()
104 |***************************************************************************
105 |
106 | The purpose of this API is to validate whether a supply or a demand line
107 | for which the reservation is being created/ modified is a valid document line.
108 | This API will return a 'Y' or 'N', and the process will continue if the
109 | returned value is 'Y'.
110 |
111 | x_return_status     - Returns the status to the calling API
112 |
113 | x_msg_count         -	Returns the message count in the stack
114 |
115 | x_msg_data	      - Returns the messages from the stack
116 |
117 | x_valid_status      -	Returns whether the supply or demand
118 |			document is valid or not
119 | p_organization_id	Organization id of the document to be validated
120 |
121 | P_item_id		- Inventory item id of the document to be
122 			  validated
123 | p_supply_demand_code	- The action determines whether the calling
124 |			  API is querying for a supply or demand
125 | p_supply_demand_type_id   - This holds the demand type for which
126 			      the availability is to be checked
127 | p_supply_demand_header_id - This holds the header information of the
128 			      demand document for which the availability
129 			      is to be checked
130 | p_supply_demand_line_id   - This holds the line information of the demand
131 			      document for which the availability is to
132 			      be checked
133 | p_supply_demand_line_detail - This holds the line information of the demand
134 			      document for which the availability is to
135 			      be checked
136 | p_demand_ship_date	     - This is will be filled in for reservations
137                                that are crossdocked. For non-crossdocked
138 			       reservations, this will be the need-by-date
139 			       of the demand
140 | p_expected_receipt_date    - This is will be filled in for reservations
141 			      that are crossdocked.
142 			      For non-crossdocked reservations, this will be null.
143 | p_api_version_number	    - Api version number
144 |
145 | p_init_msg_lst            - To initialize message list or not
146 |
147 ***************************************************************************/
148 
149 PROCEDURE validate_supply_demand (
150 x_return_status            		OUT    	NOCOPY VARCHAR2
151 , x_msg_count                		OUT    	NOCOPY NUMBER
152 , x_msg_data                 		OUT    	NOCOPY VARCHAR2
153 , x_valid_status			OUT      NOCOPY VARCHAR2
154 , p_organization_id			IN	NUMBER
155 , p_item_id				IN	NUMBER
156 , p_supply_demand_code			IN	NUMBER
157 , p_supply_demand_type_id		IN	NUMBER
158 , p_supply_demand_header_id		IN	NUMBER
159 , p_supply_demand_line_id		IN	NUMBER
160 , p_supply_demand_line_detail		IN	NUMBER default FND_API.G_MISS_NUM
161 , p_demand_ship_date			IN	DATE
162 , p_expected_receipt_date		IN	DATE
163 , p_api_version_number     		IN     	NUMBER default 1.0
164 ,p_init_msg_lst		        IN VARCHAR2
165 ) ;
166 
167 END wip_reservations_grp ;
168