1 PACKAGE PON_TCA_MERGE_PVT AUTHID CURRENT_USER as
2 /* $Header: PONTCMGS.pls 120.3 2005/11/28 09:42:17 sapandey noship $ */
3
4 G_BUYER CONSTANT VARCHAR2(20) := 'BUYER';
5 G_SELLER CONSTANT VARCHAR2(20) := 'SELLER';
6 G_INCOMPATIBLE CONSTANT VARCHAR2(20) := 'INCOMPATIBLE';
7 G_IRRELEVANT CONSTANT VARCHAR2(20) := 'IRRELEVANT';
8
9
10 /*PROCEDURE PARTY_MERGE(p_Entity_name IN VARCHAR2,
11 p_from_id IN NUMBER,
12 p_to_id IN OUT NOCOPY NUMBER ,
13 p_From_FK_id IN NUMBER,
14 p_To_FK_id IN NUMBER,
15 p_Parent_Entity_name IN VARCHAR2,
16 p_batch_id IN NUMBER,
17 p_Batch_Party_id IN NUMBER,
18 p_return_status IN OUT NOCOPY VARCHAR2 );*/
19
20 -- Start of comments
21 -- API name : VETO_ENTERPRISE_PARTY_MERGE
22 --
23 -- Type : Group
24 --
25 -- Pre-reqs : Negotiation with the given trading_partner_id
26 -- (p_From_FK_id) must exists in the database
27 --
28 -- Function : This procedure will be attached to the Trading Partner Id
29 -- merge for Sourcing Buyer entities thus it will simply veto the
30 -- accidental merge without checking any thing.
31 --
32 -- So, DO NOT attach this procedure to any other Party Merge
33 -- scenario apart from the Enterprise Buyer Party merge case
34 -- for which it is designed
35 --
36 -- Parameters:
37 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
38 -- TCA Merge Dictionary that is going to merge
39 --
40 -- IN : p_from_id NUMBER Required, the value of PK of the record
41 -- which is going to be merged
42 --
43 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
44 -- to which the p_from_id party is going to be merged
45 --
46 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
47 -- Party Site, etc.) when merge is executed
48 --
49 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
50 -- Party Site, etc.) when merge is executed
51 --
52 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
53 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
54 --
55 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
56 -- Party Merge is executed
57 --
58 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
59 -- for which the Party Merge is executed
60 --
61 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
62 -- was successful or not; It can have the following values -
63 --
64 -- FND_API.G_RET_STS_SUCCESS (Success)
65 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
66 -- failed due to Unexpected error)
67 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
68 -- vetod the Party Merge)
69 --
70 -- Version : Current version 1.0
71 -- Previous version 1.0
72 -- Initial version 1.0
73 --
74 -- End of comments
75 PROCEDURE VETO_ENTERPRISE_PARTY_MERGE (
76 p_Entity_name IN VARCHAR2,
77 p_from_id IN NUMBER,
78 x_to_id IN OUT NOCOPY NUMBER ,
79 p_From_FK_id IN NUMBER,
80 p_To_FK_id IN NUMBER,
81 p_Parent_Entity_name IN VARCHAR2,
82 p_batch_id IN NUMBER,
83 p_Batch_Party_id IN NUMBER,
84 x_return_status IN OUT NOCOPY VARCHAR2 );
85
86
87 -- Start of comments
88 -- API name : NEG_TPC_MERGE
89 --
90 -- Type : Group
91 --
92 -- Pre-reqs : Negotiation with the given trading_partner_contact_id
93 -- (p_From_FK_id) must exists in the database
94 --
95 -- Function : This procedure will be attached to the TRADING_PARTNER_CONTACT_ID
96 -- merge for Sourcing PON_AUCTION_HEADERS_ALL entity.
97 --
98 -- It will veto Party Merge if -
99 -- p_From_FK_id and p_To_FK_id both are not Buyer user party
100 --
101 -- This will merge the all the PON_AUCTION_HEADERS_ALL records
102 -- having TRADING_PARTNER_CONTACT_ID equals to p_From_FK_id
103 -- to party id having value (p_To_FK_id)
104 --
105 -- Parameters:
106 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
107 -- TCA Merge Dictionary that is going to merge
108 --
109 -- IN : p_from_id NUMBER Required, the value of PK of the record
110 -- which is going to be merged
111 --
112 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
113 -- to which the p_from_id party is going to be merged
114 --
115 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
116 -- Party Site, etc.) when merge is executed
117 --
118 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
119 -- Party Site, etc.) when merge is executed
120 --
121 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
122 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
123 --
124 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
125 -- Party Merge is executed
126 --
127 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
128 -- for which the Party Merge is executed
129 --
130 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
131 -- was successful or not; It can have the following values -
132 --
133 -- FND_API.G_RET_STS_SUCCESS (Success)
134 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
135 -- failed due to Unexpected error)
136 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
137 -- vetod the Party Merge)
138 --
139 -- Version : Current version 1.0
140 -- Previous version 1.0
141 -- Initial version 1.0
142 --
143 -- End of comments
144 PROCEDURE NEG_TPC_MERGE (
145 p_Entity_name IN VARCHAR2,
146 p_from_id IN NUMBER,
147 x_to_id IN OUT NOCOPY NUMBER ,
148 p_From_FK_id IN NUMBER,
149 p_To_FK_id IN NUMBER,
150 p_Parent_Entity_name IN VARCHAR2,
151 p_batch_id IN NUMBER,
152 p_Batch_Party_id IN NUMBER,
153 x_return_status IN OUT NOCOPY VARCHAR2 );
154
155 -- Start of comments
156 -- API name : NEG_DRFT_LCK_MERGE
157 --
158 -- Type : Group
159 --
160 -- Pre-reqs : Negotiation with the given draft_locked_by_contact_id
161 -- (p_From_FK_id) must exists in the database
162 --
163 -- Function : This procedure will be attached to the DRAFT_LOCKED_BY_CONTACT_ID
164 -- merge for Sourcing PON_AUCTION_HEADERS_ALL entity.
165 --
166 -- It will veto Party Merge if -
167 -- p_From_FK_id and p_To_FK_id both are not Buyer user party
168 --
169 -- This will merge the all the PON_AUCTION_HEADERS_ALL records
170 -- having DRAFT_LOCKED_BY_CONTACT_ID equals to p_From_FK_id
171 -- to party id having value (p_To_FK_id)
172 --
173 -- Parameters:
174 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
175 -- TCA Merge Dictionary that is going to merge
176 --
177 -- IN : p_from_id NUMBER Required, the value of PK of the record
178 -- which is going to be merged
179 --
180 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
181 -- to which the p_from_id party is going to be merged
182 --
183 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
184 -- Party Site, etc.) when merge is executed
185 --
186 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
187 -- Party Site, etc.) when merge is executed
188 --
189 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
190 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
191 --
192 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
193 -- Party Merge is executed
194 --
195 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
196 -- for which the Party Merge is executed
197 --
198 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
199 -- was successful or not; It can have the following values -
200 --
201 -- FND_API.G_RET_STS_SUCCESS (Success)
202 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
203 -- failed due to Unexpected error)
204 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
205 -- vetod the Party Merge)
206 --
207 -- Version : Current version 1.0
208 -- Previous version 1.0
209 -- Initial version 1.0
210 --
211 -- End of comments
212 PROCEDURE NEG_DRFT_LCK_MERGE (
213 p_Entity_name IN VARCHAR2,
214 p_from_id IN NUMBER,
215 x_to_id IN OUT NOCOPY NUMBER ,
216 p_From_FK_id IN NUMBER,
217 p_To_FK_id IN NUMBER,
218 p_Parent_Entity_name IN VARCHAR2,
219 p_batch_id IN NUMBER,
220 p_Batch_Party_id IN NUMBER,
221 x_return_status IN OUT NOCOPY VARCHAR2 );
222
223 -- Start of comments
224 -- API name : NEG_DRFT_UNLCK_MERGE
225 --
226 -- Type : Group
227 --
228 -- Pre-reqs : Negotiation with the given draft_unlocked_by_contact_id
229 -- (p_From_FK_id) must exists in the database
230 --
231 -- Function : This procedure will be attached to the DRAFT_UNLOCKED_BY_CONTACT_ID
232 -- merge for Sourcing PON_AUCTION_HEADERS_ALL entity.
233 --
234 -- It will veto Party Merge if -
235 -- p_From_FK_id and p_To_FK_id both are not Buyer user party
236 --
237 -- This will merge the all the PON_AUCTION_HEADERS_ALL records
238 -- having DRAFT_UNLOCKED_BY_CONTACT_ID equals to p_From_FK_id
239 -- to party id having value (p_To_FK_id)
240 --
241 -- Parameters:
242 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
243 -- TCA Merge Dictionary that is going to merge
244 --
245 -- IN : p_from_id NUMBER Required, the value of PK of the record
246 -- which is going to be merged
247 --
248 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
249 -- to which the p_from_id party is going to be merged
250 --
251 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
252 -- Party Site, etc.) when merge is executed
253 --
254 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
255 -- Party Site, etc.) when merge is executed
256 --
257 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
258 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
259 --
260 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
261 -- Party Merge is executed
262 --
263 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
264 -- for which the Party Merge is executed
265 --
266 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
267 -- was successful or not; It can have the following values -
268 --
269 -- FND_API.G_RET_STS_SUCCESS (Success)
270 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
271 -- failed due to Unexpected error)
272 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
273 -- vetod the Party Merge)
274 --
275 -- Version : Current version 1.0
276 -- Previous version 1.0
277 -- Initial version 1.0
278 --
279 -- End of comments
280 PROCEDURE NEG_DRFT_UNLCK_MERGE (
281 p_Entity_name IN VARCHAR2,
282 p_from_id IN NUMBER,
283 x_to_id IN OUT NOCOPY NUMBER ,
284 p_From_FK_id IN NUMBER,
285 p_To_FK_id IN NUMBER,
286 p_Parent_Entity_name IN VARCHAR2,
287 p_batch_id IN NUMBER,
288 p_Batch_Party_id IN NUMBER,
289 x_return_status IN OUT NOCOPY VARCHAR2 );
290
291 -- Start of comments
292 -- API name : NEG_SCORE_LCK_MERGE
293 --
294 -- Type : Group
295 --
296 -- Pre-reqs : Negotiation with the given scoring_lock_tp_contact_id
297 -- (p_From_FK_id) must exists in the database
298 --
299 -- Function : This procedure will be attached to the SCORING_LOCK_TP_CONTACT_ID
300 -- merge for Sourcing PON_AUCTION_HEADERS_ALL entity.
301 --
302 -- It will veto Party Merge if -
303 -- p_From_FK_id and p_To_FK_id both are not Buyer user party
304 --
305 -- This will merge the all the PON_AUCTION_HEADERS_ALL records
306 -- having SCORING_LOCK_TP_CONTACT_ID equals to p_From_FK_id
307 -- to party id having value (p_To_FK_id)
308 --
309 -- Parameters:
310 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
314 -- which is going to be merged
311 -- TCA Merge Dictionary that is going to merge
312 --
313 -- IN : p_from_id NUMBER Required, the value of PK of the record
315 --
316 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
317 -- to which the p_from_id party is going to be merged
318 --
319 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
320 -- Party Site, etc.) when merge is executed
321 --
322 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
323 -- Party Site, etc.) when merge is executed
324 --
325 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
326 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
327 --
328 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
329 -- Party Merge is executed
330 --
331 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
332 -- for which the Party Merge is executed
333 --
334 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
335 -- was successful or not; It can have the following values -
336 --
337 -- FND_API.G_RET_STS_SUCCESS (Success)
338 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
339 -- failed due to Unexpected error)
340 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
341 -- vetod the Party Merge)
342 --
343 -- Version : Current version 1.0
344 -- Previous version 1.0
345 -- Initial version 1.0
346 --
347 -- End of comments
348 PROCEDURE NEG_SCORE_LCK_MERGE (
349 p_Entity_name IN VARCHAR2,
350 p_from_id IN NUMBER,
351 x_to_id IN OUT NOCOPY NUMBER ,
352 p_From_FK_id IN NUMBER,
353 p_To_FK_id IN NUMBER,
354 p_Parent_Entity_name IN VARCHAR2,
355 p_batch_id IN NUMBER,
356 p_Batch_Party_id IN NUMBER,
357 x_return_status IN OUT NOCOPY VARCHAR2 );
358
359
360 -- Start of comments
361 -- API name : NEG_EVENT_MERGE
362 --
363 -- Type : Group
364 --
365 -- Pre-reqs : Negotiation Event with the given trading_partner_contact_id
366 -- (p_From_FK_id) must exists in the database
367 --
368 -- Function : This procedure will be attached to the TRADING_PARTNER_CONTACT_ID
369 -- merge for Sourcing PON_AUCTION_EVENTS entity.
370 --
371 -- It will veto Party Merge if -
372 -- p_From_FK_id and p_To_FK_id both are not Buyer user party
373 --
374 -- This will merge the all the PON_AUCTION_EVENTS records
375 -- having TRADING_PARTNER_CONTACT_ID equals to p_From_FK_id
376 -- to party id having value (p_To_FK_id)
377 --
378 -- Parameters:
379 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
380 -- TCA Merge Dictionary that is going to merge
381 --
382 -- IN : p_from_id NUMBER Required, the value of PK of the record
383 -- which is going to be merged
384 --
385 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
386 -- to which the p_from_id party is going to be merged
387 --
388 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
389 -- Party Site, etc.) when merge is executed
390 --
391 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
392 -- Party Site, etc.) when merge is executed
393 --
394 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
395 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
396 --
397 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
398 -- Party Merge is executed
399 --
400 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
401 -- for which the Party Merge is executed
402 --
403 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
404 -- was successful or not; It can have the following values -
405 --
406 -- FND_API.G_RET_STS_SUCCESS (Success)
407 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
411 --
408 -- failed due to Unexpected error)
409 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
410 -- vetod the Party Merge)
412 -- Version : Current version 1.0
413 -- Previous version 1.0
414 -- Initial version 1.0
415 --
416 -- End of comments
417 PROCEDURE NEG_EVENT_MERGE (
418 p_Entity_name IN VARCHAR2,
419 p_from_id IN NUMBER,
420 x_to_id IN OUT NOCOPY NUMBER ,
421 p_From_FK_id IN NUMBER,
422 p_To_FK_id IN NUMBER,
423 p_Parent_Entity_name IN VARCHAR2,
424 p_batch_id IN NUMBER,
425 p_Batch_Party_id IN NUMBER,
426 x_return_status IN OUT NOCOPY VARCHAR2 );
427
428 -- Start of comments
429 -- API name : BIDDER_LST_MERGE
430 --
431 -- Type : Group
432 --
433 -- Pre-reqs : Bidders List with the given trading_partner_contact_id
434 -- (p_From_FK_id) must exists in the database
435 --
436 -- Function : This procedure will be attached to the TRADING_PARTNER_CONTACT_ID
437 -- merge for Sourcing PON_BIDDERS_LISTS entity.
438 --
439 -- It will veto Party Merge if -
440 -- p_From_FK_id and p_To_FK_id both are not Buyer user party
441 --
442 -- This will merge the all the PON_BIDDERS_LISTS records
443 -- having TRADING_PARTNER_CONTACT_ID equals to p_From_FK_id
444 -- to party id having value (p_To_FK_id)
445 --
446 -- Parameters:
447 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
448 -- TCA Merge Dictionary that is going to merge
449 --
450 -- IN : p_from_id NUMBER Required, the value of PK of the record
451 -- which is going to be merged
452 --
453 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
454 -- to which the p_from_id party is going to be merged
455 --
456 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
457 -- Party Site, etc.) when merge is executed
458 --
459 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
460 -- Party Site, etc.) when merge is executed
461 --
462 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
463 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
464 --
465 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
466 -- Party Merge is executed
467 --
468 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
469 -- for which the Party Merge is executed
470 --
471 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
472 -- was successful or not; It can have the following values -
473 --
474 -- FND_API.G_RET_STS_SUCCESS (Success)
475 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
476 -- failed due to Unexpected error)
477 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
478 -- vetod the Party Merge)
479 --
480 -- Version : Current version 1.0
481 -- Previous version 1.0
482 -- Initial version 1.0
483 --
484 -- End of comments
485 PROCEDURE BIDDER_LST_MERGE (
486 p_Entity_name IN VARCHAR2,
487 p_from_id IN NUMBER,
488 x_to_id IN OUT NOCOPY NUMBER ,
489 p_From_FK_id IN NUMBER,
490 p_To_FK_id IN NUMBER,
491 p_Parent_Entity_name IN VARCHAR2,
492 p_batch_id IN NUMBER,
493 p_Batch_Party_id IN NUMBER,
494 x_return_status IN OUT NOCOPY VARCHAR2 );
495
496 -- Start of comments
497 -- API name : NEG_ATTR_LST_MERGE
498 --
499 -- Type : Group
500 --
501 -- Pre-reqs : Attributes List with the given trading_partner_contact_id
502 -- (p_From_FK_id) must exists in the database
503 --
504 -- Function : This procedure will be attached to the TRADING_PARTNER_CONTACT_ID
505 -- merge for Sourcing PON_ATTRIBUTE_LISTS entity.
506 --
507 -- It will veto Party Merge if -
508 -- p_From_FK_id and p_To_FK_id both are not Buyer user party
509 --
510 -- This will merge the all the PON_ATTRIBUTE_LISTS records
511 -- having TRADING_PARTNER_CONTACT_ID equals to p_From_FK_id
512 -- to party id having value (p_To_FK_id)
513 --
517 --
514 -- Parameters:
515 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
516 -- TCA Merge Dictionary that is going to merge
518 -- IN : p_from_id NUMBER Required, the value of PK of the record
519 -- which is going to be merged
520 --
521 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
522 -- to which the p_from_id party is going to be merged
523 --
524 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
525 -- Party Site, etc.) when merge is executed
526 --
527 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
528 -- Party Site, etc.) when merge is executed
529 --
530 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
531 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
532 --
533 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
534 -- Party Merge is executed
535 --
536 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
537 -- for which the Party Merge is executed
538 --
539 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
540 -- was successful or not; It can have the following values -
541 --
542 -- FND_API.G_RET_STS_SUCCESS (Success)
543 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
544 -- failed due to Unexpected error)
545 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
546 -- vetod the Party Merge)
547 --
548 -- Version : Current version 1.0
549 -- Previous version 1.0
550 -- Initial version 1.0
551 --
552 -- End of comments
553 PROCEDURE NEG_ATTR_LST_MERGE (
554 p_Entity_name IN VARCHAR2,
555 p_from_id IN NUMBER,
556 x_to_id IN OUT NOCOPY NUMBER ,
557 p_From_FK_id IN NUMBER,
558 p_To_FK_id IN NUMBER,
559 p_Parent_Entity_name IN VARCHAR2,
560 p_batch_id IN NUMBER,
561 p_Batch_Party_id IN NUMBER,
562 x_return_status IN OUT NOCOPY VARCHAR2 );
563
564 -- Start of comments
565 -- API name : RES_SURROG_MERGE
566 --
567 -- Type : Group
568 --
569 -- Pre-reqs : Responses with the given surrog_bid_created_contact_id
570 -- (p_From_FK_id) must exists in the database
571 --
572 -- Function : This procedure will be attached to the SURROG_BID_CREATED_CONTACT_ID
573 -- merge for Sourcing PON_BID_HEADERS entity.
574 --
575 -- It will veto Party Merge if -
576 -- p_From_FK_id and p_To_FK_id both are not Buyer user party
577 --
578 -- This will merge the all the PON_BID_HEADERS records
579 -- having SURROG_BID_CREATED_CONTACT_ID equals to p_From_FK_id
580 -- to party id having value (p_To_FK_id)
581 --
582 -- Parameters:
583 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
584 -- TCA Merge Dictionary that is going to merge
585 --
586 -- IN : p_from_id NUMBER Required, the value of PK of the record
587 -- which is going to be merged
588 --
589 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
590 -- to which the p_from_id party is going to be merged
591 --
592 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
593 -- Party Site, etc.) when merge is executed
594 --
595 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
596 -- Party Site, etc.) when merge is executed
597 --
598 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
599 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
600 --
601 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
602 -- Party Merge is executed
603 --
604 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
605 -- for which the Party Merge is executed
606 --
607 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
608 -- was successful or not; It can have the following values -
609 --
610 -- FND_API.G_RET_STS_SUCCESS (Success)
614 -- vetod the Party Merge)
611 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
612 -- failed due to Unexpected error)
613 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
615 --
616 -- Version : Current version 1.0
617 -- Previous version 1.0
618 -- Initial version 1.0
619 --
620 -- End of comments
621 PROCEDURE RES_SURROG_MERGE (
622 p_Entity_name IN VARCHAR2,
623 p_from_id IN NUMBER,
624 x_to_id IN OUT NOCOPY NUMBER ,
625 p_From_FK_id IN NUMBER,
626 p_To_FK_id IN NUMBER,
627 p_Parent_Entity_name IN VARCHAR2,
628 p_batch_id IN NUMBER,
629 p_Batch_Party_id IN NUMBER,
630 x_return_status IN OUT NOCOPY VARCHAR2 );
631
632 -- Start of comments
633 -- API name : RES_SCORE_MERGE
634 --
635 -- Type : Group
636 --
637 -- Pre-reqs : Responses with the given score_override_tp_contact_id
638 -- (p_From_FK_id) must exists in the database
639 --
640 -- Function : This procedure will be attached to the SCORE_OVERRIDE_TP_CONTACT_ID
641 -- merge for Sourcing PON_BID_HEADERS entity.
642 --
643 -- It will veto Party Merge if -
644 -- p_From_FK_id and p_To_FK_id both are not Buyer user party
645 --
646 -- This will merge the all the PON_BID_HEADERS records
647 -- having SCORE_OVERRIDE_TP_CONTACT_ID equals to p_From_FK_id
648 -- to party id having value (p_To_FK_id)
649 --
650 -- Parameters:
651 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
652 -- TCA Merge Dictionary that is going to merge
653 --
654 -- IN : p_from_id NUMBER Required, the value of PK of the record
655 -- which is going to be merged
656 --
657 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
658 -- to which the p_from_id party is going to be merged
659 --
660 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
661 -- Party Site, etc.) when merge is executed
662 --
663 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
664 -- Party Site, etc.) when merge is executed
665 --
666 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
667 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
668 --
669 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
670 -- Party Merge is executed
671 --
672 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
673 -- for which the Party Merge is executed
674 --
675 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
676 -- was successful or not; It can have the following values -
677 --
678 -- FND_API.G_RET_STS_SUCCESS (Success)
679 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
680 -- failed due to Unexpected error)
681 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
682 -- vetod the Party Merge)
683 --
684 -- Version : Current version 1.0
685 -- Previous version 1.0
686 -- Initial version 1.0
687 --
688 -- End of comments
689 PROCEDURE RES_SCORE_MERGE (
690 p_Entity_name IN VARCHAR2,
691 p_from_id IN NUMBER,
692 x_to_id IN OUT NOCOPY NUMBER ,
693 p_From_FK_id IN NUMBER,
694 p_To_FK_id IN NUMBER,
695 p_Parent_Entity_name IN VARCHAR2,
696 p_batch_id IN NUMBER,
697 p_Batch_Party_id IN NUMBER,
698 x_return_status IN OUT NOCOPY VARCHAR2 );
699
700 -- Start of comments
701 -- API name : RES_SHRT_LIST_MERGE
702 --
703 -- Type : Group
704 --
705 -- Pre-reqs : Responses with the given shortlist_tpc_id
706 -- (p_From_FK_id) must exists in the database
707 --
708 -- Function : This procedure will be attached to the SHORTLIST_TPC_ID
709 -- merge for Sourcing PON_BID_HEADERS entity.
710 --
711 -- It will veto Party Merge if -
712 -- p_From_FK_id and p_To_FK_id both are not Buyer user party
713 --
714 -- This will merge the all the PON_BID_HEADERS records
715 -- having SHORTLIST_TPC_ID equals to p_From_FK_id
719 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
716 -- to party id having value (p_To_FK_id)
717 --
718 -- Parameters:
720 -- TCA Merge Dictionary that is going to merge
721 --
722 -- IN : p_from_id NUMBER Required, the value of PK of the record
723 -- which is going to be merged
724 --
725 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
726 -- to which the p_from_id party is going to be merged
727 --
728 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
729 -- Party Site, etc.) when merge is executed
730 --
731 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
732 -- Party Site, etc.) when merge is executed
733 --
734 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
735 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
736 --
737 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
738 -- Party Merge is executed
739 --
740 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
741 -- for which the Party Merge is executed
742 --
743 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
744 -- was successful or not; It can have the following values -
745 --
746 -- FND_API.G_RET_STS_SUCCESS (Success)
747 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
748 -- failed due to Unexpected error)
749 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
750 -- vetod the Party Merge)
751 --
752 -- Version : Current version 1.0
753 -- Previous version 1.0
754 -- Initial version 1.0
755 --
756 -- End of comments
757 PROCEDURE RES_SHRT_LIST_MERGE (
758 p_Entity_name IN VARCHAR2,
759 p_from_id IN NUMBER,
760 x_to_id IN OUT NOCOPY NUMBER ,
761 p_From_FK_id IN NUMBER,
762 p_To_FK_id IN NUMBER,
763 p_Parent_Entity_name IN VARCHAR2,
764 p_batch_id IN NUMBER,
765 p_Batch_Party_id IN NUMBER,
766 x_return_status IN OUT NOCOPY VARCHAR2 );
767
768 -- Start of comments
769 -- API name : NEG_CONTRCT_MERGE
770 --
771 -- Type : Group
772 --
773 -- Pre-reqs : Negotitions with the given authoring_party_contact_id
774 -- (p_From_FK_id) must exists in the database
775 --
776 -- Function : This procedure will be attached to the AUTHORING_PARTY_CONTACT_ID
777 -- merge for Sourcing PON_CONTRACTS entity.
778 --
779 -- It will veto Party Merge if -
780 -- p_From_FK_id and p_To_FK_id both are not Buyer user party
781 --
782 -- This will merge the all the PON_CONTRACTS records
783 -- having AUTHORING_PARTY_CONTACT_ID equals to p_From_FK_id
784 -- to party id having value (p_To_FK_id)
785 --
786 -- Parameters:
787 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
788 -- TCA Merge Dictionary that is going to merge
789 --
790 -- IN : p_from_id NUMBER Required, the value of PK of the record
791 -- which is going to be merged
792 --
793 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
794 -- to which the p_from_id party is going to be merged
795 --
796 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
797 -- Party Site, etc.) when merge is executed
798 --
799 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
800 -- Party Site, etc.) when merge is executed
801 --
802 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
803 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
804 --
805 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
806 -- Party Merge is executed
807 --
808 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
809 -- for which the Party Merge is executed
810 --
811 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
812 -- was successful or not; It can have the following values -
813 --
817 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
814 -- FND_API.G_RET_STS_SUCCESS (Success)
815 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
816 -- failed due to Unexpected error)
818 -- vetod the Party Merge)
819 --
820 -- Version : Current version 1.0
821 -- Previous version 1.0
822 -- Initial version 1.0
823 --
824 -- End of comments
825 PROCEDURE NEG_CONTRCT_MERGE (
826 p_Entity_name IN VARCHAR2,
827 p_from_id IN NUMBER,
828 x_to_id IN OUT NOCOPY NUMBER ,
829 p_From_FK_id IN NUMBER,
830 p_To_FK_id IN NUMBER,
831 p_Parent_Entity_name IN VARCHAR2,
832 p_batch_id IN NUMBER,
833 p_Batch_Party_id IN NUMBER,
834 x_return_status IN OUT NOCOPY VARCHAR2 );
835
836 -- Start of comments
837 -- API name : NEG_DISC_THR_MERGE
838 --
839 -- Type : Group
840 --
841 -- Pre-reqs : Discussion Messages with the given owner_party_id
842 -- (p_From_FK_id) must exists in the database
843 --
844 -- Function : This procedure will be attached to the OWNER_PARTY_ID
845 -- merge for Sourcing PON_THREADS entity.
846 --
847 -- It will veto Party Merge if -
848 -- p_From_FK_id and p_To_FK_id both are not Buyer user party
849 -- OR
850 -- p_From_FK_id and p_To_FK_id both are not Seller user party
851 --
852 -- This will merge the all the PON_THREADS records
853 -- having OWNER_PARTY_ID equals to p_From_FK_id
854 -- to party id having value (p_To_FK_id)
855 --
856 -- Parameters:
857 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
858 -- TCA Merge Dictionary that is going to merge
859 --
860 -- IN : p_from_id NUMBER Required, the value of PK of the record
861 -- which is going to be merged
862 --
863 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
864 -- to which the p_from_id party is going to be merged
865 --
866 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
867 -- Party Site, etc.) when merge is executed
868 --
869 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
870 -- Party Site, etc.) when merge is executed
871 --
872 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
873 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
874 --
875 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
876 -- Party Merge is executed
877 --
878 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
879 -- for which the Party Merge is executed
880 --
881 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
882 -- was successful or not; It can have the following values -
883 --
884 -- FND_API.G_RET_STS_SUCCESS (Success)
885 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
886 -- failed due to Unexpected error)
887 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
888 -- vetod the Party Merge)
889 --
890 -- Version : Current version 1.0
891 -- Previous version 1.0
892 -- Initial version 1.0
893 --
894 -- End of comments
895 PROCEDURE NEG_DISC_THR_MERGE (
896 p_Entity_name IN VARCHAR2,
897 p_from_id IN NUMBER,
898 x_to_id IN OUT NOCOPY NUMBER ,
899 p_From_FK_id IN NUMBER,
900 p_To_FK_id IN NUMBER,
901 p_Parent_Entity_name IN VARCHAR2,
902 p_batch_id IN NUMBER,
903 p_Batch_Party_id IN NUMBER,
904 x_return_status IN OUT NOCOPY VARCHAR2 );
905
906
907 -- Start of comments
908 -- API name : NEG_DISC_THR_ENTRY_MERGE
909 --
910 -- Type : Group
911 --
912 -- Pre-reqs : Discussion Message Entries with the given from_id
913 -- (p_From_FK_id) must exists in the database
914 --
915 -- Function : This procedure will be attached to the FROM_ID
916 -- merge for Sourcing PON_THREAD_ENTRIES entity.
917 --
918 -- It will veto Party Merge if -
919 -- p_From_FK_id and p_To_FK_id both are not Buyer user party
923 -- This will merge the all the PON_THREAD_ENTRIES records
920 -- OR
921 -- p_From_FK_id and p_To_FK_id both are not Seller user party
922 --
924 -- having FROM_ID equals to p_From_FK_id
925 -- to party id having value (p_To_FK_id)
926 --
927 -- Parameters:
928 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
929 -- TCA Merge Dictionary that is going to merge
930 --
931 -- IN : p_from_id NUMBER Required, the value of PK of the record
932 -- which is going to be merged
933 --
934 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
935 -- to which the p_from_id party is going to be merged
936 --
937 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
938 -- Party Site, etc.) when merge is executed
939 --
940 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
941 -- Party Site, etc.) when merge is executed
942 --
943 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
944 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
945 --
946 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
947 -- Party Merge is executed
948 --
949 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
950 -- for which the Party Merge is executed
951 --
952 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
953 -- was successful or not; It can have the following values -
954 --
955 -- FND_API.G_RET_STS_SUCCESS (Success)
956 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
957 -- failed due to Unexpected error)
958 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
959 -- vetod the Party Merge)
960 --
961 -- Version : Current version 1.0
962 -- Previous version 1.0
963 -- Initial version 1.0
964 --
965 -- End of comments
966 PROCEDURE NEG_DISC_THR_ENTRY_MERGE (
967 p_Entity_name IN VARCHAR2,
968 p_from_id IN NUMBER,
969 x_to_id IN OUT NOCOPY NUMBER ,
970 p_From_FK_id IN NUMBER,
971 p_To_FK_id IN NUMBER,
972 p_Parent_Entity_name IN VARCHAR2,
973 p_batch_id IN NUMBER,
974 p_Batch_Party_id IN NUMBER,
975 x_return_status IN OUT NOCOPY VARCHAR2 );
976
977 -- Start of comments
978 -- API name : NEG_COMP_MERGE
979 --
980 -- Type : Group
981 --
982 -- Pre-reqs : Trading Partner ID entries with the given from_company_id
983 -- (p_From_FK_id) must exists in the database
984 --
985 -- Function : This procedure will be attached to the TRADING_PARTNER_ID (p_From_FK_id)
986 -- merge for different Sourcing entities (like PON_THREAD_ENTRIES etc.).
987 --
988 -- It will veto Party Merge if -
989 -- p_From_FK_id or p_To_FK_id is/are Buyer company party
990 -- OR
991 -- p_From_FK_id is Seller but p_To_FK_id is not Buyer or Seller party
992 -- OR
993 -- p_To_FK_id is Seller but p_From_FK_id is not Buyer or Seller party
994 --
995 -- This will check the merge possibility for the entities
996 -- having TRADING_PARTNER_ID equals to p_From_FK_id
997 -- to TRADING_PARTNER_ID having value (p_To_FK_id). This will raise veto
998 -- if the merge is not possible.
999 --
1000 -- Parameters:
1001 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
1002 -- TCA Merge Dictionary that is going to merge
1003 --
1004 -- IN : p_from_id NUMBER Required, the value of PK of the record
1005 -- which is going to be merged
1006 --
1007 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
1008 -- to which the p_from_id party is going to be merged
1009 --
1010 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
1011 -- Party Site, etc.) when merge is executed
1012 --
1013 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
1014 -- Party Site, etc.) when merge is executed
1015 --
1016 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
1020 -- Party Merge is executed
1017 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
1018 --
1019 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
1021 --
1022 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
1023 -- for which the Party Merge is executed
1024 --
1025 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
1026 -- was successful or not; It can have the following values -
1027 --
1028 -- FND_API.G_RET_STS_SUCCESS (Success)
1029 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
1030 -- failed due to Unexpected error)
1031 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
1032 -- vetod the Party Merge)
1033 --
1034 -- Version : Current version 1.0
1035 -- Previous version 1.0
1036 -- Initial version 1.0
1037 --
1038 -- End of comments
1039 PROCEDURE NEG_COMP_MERGE (
1040 p_Entity_name IN VARCHAR2,
1041 p_from_id IN NUMBER,
1042 x_to_id IN OUT NOCOPY NUMBER ,
1043 p_From_FK_id IN NUMBER,
1044 p_To_FK_id IN NUMBER,
1045 p_Parent_Entity_name IN VARCHAR2,
1046 p_batch_id IN NUMBER,
1047 p_Batch_Party_id IN NUMBER,
1048 x_return_status IN OUT NOCOPY VARCHAR2 );
1049
1050
1051
1052 -- Start of comments
1053 -- API name : NEG_DISC_TE_RCP_MERGE
1054 --
1055 -- Type : Group
1056 --
1057 -- Pre-reqs : Discussion Message Thread Entries with the given to_id
1058 -- (p_From_FK_id) must exists in the database
1059 --
1060 -- Function : This procedure will be attached to the TO_ID
1061 -- merge for Sourcing PON_TE_RECIPIENTS entity.
1062 --
1063 -- It will veto Party Merge if -
1064 -- p_From_FK_id and p_To_FK_id both are not Buyer user party
1065 -- OR
1066 -- p_From_FK_id and p_To_FK_id both are not Seller user party
1067 --
1068 -- This will merge the all the PON_TE_RECIPIENTS records
1069 -- having TO_ID equals to p_From_FK_id
1070 -- to party id having value (p_To_FK_id)
1071 --
1072 -- Parameters:
1073 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
1074 -- TCA Merge Dictionary that is going to merge
1075 --
1076 -- IN : p_from_id NUMBER Required, the value of PK of the record
1077 -- which is going to be merged
1078 --
1079 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
1080 -- to which the p_from_id party is going to be merged
1081 --
1082 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
1083 -- Party Site, etc.) when merge is executed
1084 --
1085 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
1086 -- Party Site, etc.) when merge is executed
1087 --
1088 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
1089 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
1090 --
1091 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
1092 -- Party Merge is executed
1093 --
1094 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
1095 -- for which the Party Merge is executed
1096 --
1097 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
1098 -- was successful or not; It can have the following values -
1099 --
1100 -- FND_API.G_RET_STS_SUCCESS (Success)
1101 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
1102 -- failed due to Unexpected error)
1103 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
1104 -- vetod the Party Merge)
1105 --
1106 -- Version : Current version 1.0
1107 -- Previous version 1.0
1108 -- Initial version 1.0
1109 --
1110 -- End of comments
1111 PROCEDURE NEG_DISC_TE_RCP_MERGE (
1112 p_Entity_name IN VARCHAR2,
1113 p_from_id IN NUMBER,
1114 x_to_id IN OUT NOCOPY NUMBER ,
1115 p_From_FK_id IN NUMBER,
1116 p_To_FK_id IN NUMBER,
1117 p_Parent_Entity_name IN VARCHAR2,
1121
1118 p_batch_id IN NUMBER,
1119 p_Batch_Party_id IN NUMBER,
1120 x_return_status IN OUT NOCOPY VARCHAR2 );
1122 -- Start of comments
1123 -- API name : RES_SURR_ACK_MERGE
1124 --
1125 -- Type : Group
1126 --
1127 -- Pre-reqs : Responses with the given surrog_bid_ack_contact_id
1128 -- (p_From_FK_id) must exists in the database
1129 --
1130 -- Function : This procedure will be attached to the SURROG_BID_ACK_CONTACT_ID
1131 -- merge for Sourcing PON_ACKNOWLEDGEMENTS entity.
1132 --
1133 -- It will veto Party Merge if -
1134 -- p_From_FK_id and p_To_FK_id both are not Buyer user party
1135 --
1136 -- This will merge the all the PON_ACKNOWLEDGEMENTS records
1137 -- having SURROG_BID_ACK_CONTACT_ID equals to p_From_FK_id
1138 -- to party id having value (p_To_FK_id)
1139 --
1140 -- Parameters:
1141 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
1142 -- TCA Merge Dictionary that is going to merge
1143 --
1144 -- IN : p_from_id NUMBER Required, the value of PK of the record
1145 -- which is going to be merged
1146 --
1147 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
1148 -- to which the p_from_id party is going to be merged
1149 --
1150 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
1151 -- Party Site, etc.) when merge is executed
1152 --
1153 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
1154 -- Party Site, etc.) when merge is executed
1155 --
1156 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
1157 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
1158 --
1159 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
1160 -- Party Merge is executed
1161 --
1162 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
1163 -- for which the Party Merge is executed
1164 --
1165 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
1166 -- was successful or not; It can have the following values -
1167 --
1168 -- FND_API.G_RET_STS_SUCCESS (Success)
1169 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
1170 -- failed due to Unexpected error)
1171 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
1172 -- vetod the Party Merge)
1173 --
1174 -- Version : Current version 1.0
1175 -- Previous version 1.0
1176 -- Initial version 1.0
1177 --
1178 -- End of comments
1179 PROCEDURE RES_SURR_ACK_MERGE (
1180 p_Entity_name IN VARCHAR2,
1181 p_from_id IN NUMBER,
1182 x_to_id IN OUT NOCOPY NUMBER ,
1183 p_From_FK_id IN NUMBER,
1184 p_To_FK_id IN NUMBER,
1185 p_Parent_Entity_name IN VARCHAR2,
1186 p_batch_id IN NUMBER,
1187 p_Batch_Party_id IN NUMBER,
1188 x_return_status IN OUT NOCOPY VARCHAR2 );
1189
1190
1191 -- Start of comments
1192 -- API name : NEG_SUPP_ACC_MERGE
1193 --
1194 -- Type : Group
1195 --
1196 -- Pre-reqs : Supplier Access Lock entries with the given buyer_tp_contact_id
1197 -- (p_From_FK_id) must exists in the database
1198 --
1199 -- Function : This procedure will be attached to the BUYER_TP_CONTACT_ID
1200 -- merge for Sourcing PON_SUPPLIER_ACCESS entity.
1201 --
1202 -- It will veto Party Merge if -
1203 -- p_From_FK_id and p_To_FK_id both are not Buyer user party
1204 --
1205 -- This will merge the all the PON_SUPPLIER_ACCESS records
1206 -- having BUYER_TP_CONTACT_ID equals to p_From_FK_id
1207 -- to party id having value (p_To_FK_id)
1208 --
1209 -- Parameters:
1210 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
1211 -- TCA Merge Dictionary that is going to merge
1212 --
1213 -- IN : p_from_id NUMBER Required, the value of PK of the record
1214 -- which is going to be merged
1215 --
1216 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
1217 -- to which the p_from_id party is going to be merged
1218 --
1219 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
1220 -- Party Site, etc.) when merge is executed
1221 --
1225 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
1222 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
1223 -- Party Site, etc.) when merge is executed
1224 --
1226 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
1227 --
1228 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
1229 -- Party Merge is executed
1230 --
1231 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
1232 -- for which the Party Merge is executed
1233 --
1234 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
1235 -- was successful or not; It can have the following values -
1236 --
1237 -- FND_API.G_RET_STS_SUCCESS (Success)
1238 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
1239 -- failed due to Unexpected error)
1240 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
1241 -- vetod the Party Merge)
1242 --
1243 -- Version : Current version 1.0
1244 -- Previous version 1.0
1245 -- Initial version 1.0
1246 --
1247 -- End of comments
1248 PROCEDURE NEG_SUPP_ACC_MERGE (
1249 p_Entity_name IN VARCHAR2,
1250 p_from_id IN NUMBER,
1251 x_to_id IN OUT NOCOPY NUMBER ,
1252 p_From_FK_id IN NUMBER,
1253 p_To_FK_id IN NUMBER,
1254 p_Parent_Entity_name IN VARCHAR2,
1255 p_batch_id IN NUMBER,
1256 p_Batch_Party_id IN NUMBER,
1257 x_return_status IN OUT NOCOPY VARCHAR2 );
1258
1259
1260 -- Start of comments
1261 -- API name : BID_PARTY_TPC_MERGE
1262 --
1263 -- Type : Group
1264 --
1265 -- Pre-reqs : Invitation List entries with the given trading_partner_contact_id
1266 -- (p_From_FK_id) must exists in the database
1267 --
1268 -- Function : This procedure will be attached to the TRADING_PARTNER_CONTACT_ID
1269 -- merge for Sourcing PON_BIDDING_PARTIES entity.
1270 --
1271 -- It will veto Party Merge if -
1272 -- p_From_FK_id and p_To_FK_id both are not Seller user party
1273 --
1274 -- This will merge the all the PON_BIDDING_PARTIES records
1275 -- having TRADING_PARTNER_CONTACT_ID equals to p_From_FK_id
1276 -- to party id having value (p_To_FK_id)
1277 --
1278 -- Parameters:
1279 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
1280 -- TCA Merge Dictionary that is going to merge
1281 --
1282 -- IN : p_from_id NUMBER Required, the value of PK of the record
1283 -- which is going to be merged
1284 --
1285 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
1286 -- to which the p_from_id party is going to be merged
1287 --
1288 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
1289 -- Party Site, etc.) when merge is executed
1290 --
1291 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
1292 -- Party Site, etc.) when merge is executed
1293 --
1294 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
1295 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
1296 --
1297 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
1298 -- Party Merge is executed
1299 --
1300 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
1301 -- for which the Party Merge is executed
1302 --
1303 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
1304 -- was successful or not; It can have the following values -
1305 --
1306 -- FND_API.G_RET_STS_SUCCESS (Success)
1307 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
1308 -- failed due to Unexpected error)
1309 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
1310 -- vetod the Party Merge)
1311 --
1312 -- Version : Current version 1.0
1313 -- Previous version 1.0
1314 -- Initial version 1.0
1315 --
1316 -- End of comments
1317 PROCEDURE BID_PARTY_TPC_MERGE (
1318 p_Entity_name IN VARCHAR2,
1319 p_from_id IN NUMBER,
1320 x_to_id IN OUT NOCOPY NUMBER ,
1324 p_batch_id IN NUMBER,
1321 p_From_FK_id IN NUMBER,
1322 p_To_FK_id IN NUMBER,
1323 p_Parent_Entity_name IN VARCHAR2,
1325 p_Batch_Party_id IN NUMBER,
1326 x_return_status IN OUT NOCOPY VARCHAR2 );
1327
1328 -- Start of comments
1329 -- API name : BID_PARTY_ACK_TPC_MERGE
1330 --
1331 -- Type : Group
1332 --
1333 -- Pre-reqs : Invitation List entries with the given ack_partner_contact_id
1334 -- (p_From_FK_id) must exists in the database
1335 --
1336 -- Function : This procedure will be attached to the ACK_PARTNER_CONTACT_ID
1337 -- merge for Sourcing PON_BIDDING_PARTIES entity.
1338 --
1339 -- It will veto Party Merge if -
1340 -- p_From_FK_id and p_To_FK_id both are not Seller user party
1341 --
1342 -- This will merge the all the PON_BIDDING_PARTIES records
1343 -- having ACK_PARTNER_CONTACT_ID equals to p_From_FK_id
1344 -- to party id having value (p_To_FK_id)
1345 --
1346 -- Parameters:
1347 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
1348 -- TCA Merge Dictionary that is going to merge
1349 --
1350 -- IN : p_from_id NUMBER Required, the value of PK of the record
1351 -- which is going to be merged
1352 --
1353 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
1354 -- to which the p_from_id party is going to be merged
1355 --
1356 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
1357 -- Party Site, etc.) when merge is executed
1358 --
1359 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
1360 -- Party Site, etc.) when merge is executed
1361 --
1362 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
1363 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
1364 --
1365 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
1366 -- Party Merge is executed
1367 --
1368 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
1369 -- for which the Party Merge is executed
1370 --
1371 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
1372 -- was successful or not; It can have the following values -
1373 --
1374 -- FND_API.G_RET_STS_SUCCESS (Success)
1375 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
1376 -- failed due to Unexpected error)
1377 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
1378 -- vetod the Party Merge)
1379 --
1380 -- Version : Current version 1.0
1381 -- Previous version 1.0
1382 -- Initial version 1.0
1383 --
1384 -- End of comments
1385 PROCEDURE BID_PARTY_ACK_TPC_MERGE (
1386 p_Entity_name IN VARCHAR2,
1387 p_from_id IN NUMBER,
1388 x_to_id IN OUT NOCOPY NUMBER ,
1389 p_From_FK_id IN NUMBER,
1390 p_To_FK_id IN NUMBER,
1391 p_Parent_Entity_name IN VARCHAR2,
1392 p_batch_id IN NUMBER,
1393 p_Batch_Party_id IN NUMBER,
1394 x_return_status IN OUT NOCOPY VARCHAR2 );
1395
1396 -- Start of comments
1397 -- API name : RES_UNLCK_TPC_MERGE
1398 --
1399 -- Type : Group
1400 --
1401 -- Pre-reqs : Responses with the given draft_unlocked_by_contact_id
1402 -- (p_From_FK_id) must exists in the database
1403 --
1404 -- Function : This procedure will be attached to the DRAFT_UNLOCKED_BY_CONTACT_ID
1405 -- merge for Sourcing PON_BID_HEADERS entity.
1406 --
1407 -- It will veto Party Merge if -
1408 -- p_From_FK_id and p_To_FK_id both are not Seller user party
1409 --
1410 -- This will merge the all the PON_BID_HEADERS records
1411 -- having DRAFT_UNLOCKED_BY_CONTACT_ID equals to p_From_FK_id
1412 -- to party id having value (p_To_FK_id)
1413 --
1414 -- Parameters:
1415 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
1416 -- TCA Merge Dictionary that is going to merge
1417 --
1418 -- IN : p_from_id NUMBER Required, the value of PK of the record
1419 -- which is going to be merged
1420 --
1421 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
1422 -- to which the p_from_id party is going to be merged
1423 --
1427 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
1424 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
1425 -- Party Site, etc.) when merge is executed
1426 --
1428 -- Party Site, etc.) when merge is executed
1429 --
1430 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
1431 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
1432 --
1433 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
1434 -- Party Merge is executed
1435 --
1436 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
1437 -- for which the Party Merge is executed
1438 --
1439 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
1440 -- was successful or not; It can have the following values -
1441 --
1442 -- FND_API.G_RET_STS_SUCCESS (Success)
1443 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
1444 -- failed due to Unexpected error)
1445 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
1446 -- vetod the Party Merge)
1447 --
1448 -- Version : Current version 1.0
1449 -- Previous version 1.0
1450 -- Initial version 1.0
1451 --
1452 -- End of comments
1453 PROCEDURE RES_UNLCK_TPC_MERGE (
1454 p_Entity_name IN VARCHAR2,
1455 p_from_id IN NUMBER,
1456 x_to_id IN OUT NOCOPY NUMBER ,
1457 p_From_FK_id IN NUMBER,
1458 p_To_FK_id IN NUMBER,
1459 p_Parent_Entity_name IN VARCHAR2,
1460 p_batch_id IN NUMBER,
1461 p_Batch_Party_id IN NUMBER,
1462 x_return_status IN OUT NOCOPY VARCHAR2 );
1463
1464 -- Start of comments
1465 -- API name : RES_LCK_TPC_MERGE
1466 --
1467 -- Type : Group
1468 --
1469 -- Pre-reqs : Responses with the given draft_locked_by_contact_id
1470 -- (p_From_FK_id) must exists in the database
1471 --
1472 -- Function : This procedure will be attached to the DRAFT_LOCKED_BY_CONTACT_ID
1473 -- merge for Sourcing PON_BID_HEADERS entity.
1474 --
1475 -- It will veto Party Merge if -
1476 -- p_From_FK_id and p_To_FK_id both are not Seller user party
1477 --
1478 -- This will merge the all the PON_BID_HEADERS records
1479 -- having DRAFT_LOCKED_BY_CONTACT_ID equals to p_From_FK_id
1480 -- to party id having value (p_To_FK_id)
1481 --
1482 -- Parameters:
1483 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
1484 -- TCA Merge Dictionary that is going to merge
1485 --
1486 -- IN : p_from_id NUMBER Required, the value of PK of the record
1487 -- which is going to be merged
1488 --
1489 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
1490 -- to which the p_from_id party is going to be merged
1491 --
1492 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
1493 -- Party Site, etc.) when merge is executed
1494 --
1495 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
1496 -- Party Site, etc.) when merge is executed
1497 --
1498 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
1499 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
1500 --
1501 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
1502 -- Party Merge is executed
1503 --
1504 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
1505 -- for which the Party Merge is executed
1506 --
1507 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
1508 -- was successful or not; It can have the following values -
1509 --
1510 -- FND_API.G_RET_STS_SUCCESS (Success)
1511 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
1512 -- failed due to Unexpected error)
1513 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
1514 -- vetod the Party Merge)
1515 --
1516 -- Version : Current version 1.0
1517 -- Previous version 1.0
1518 -- Initial version 1.0
1519 --
1520 -- End of comments
1524 x_to_id IN OUT NOCOPY NUMBER ,
1521 PROCEDURE RES_LCK_TPC_MERGE (
1522 p_Entity_name IN VARCHAR2,
1523 p_from_id IN NUMBER,
1525 p_From_FK_id IN NUMBER,
1526 p_To_FK_id IN NUMBER,
1527 p_Parent_Entity_name IN VARCHAR2,
1528 p_batch_id IN NUMBER,
1529 p_Batch_Party_id IN NUMBER,
1530 x_return_status IN OUT NOCOPY VARCHAR2 );
1531
1532 -- Start of comments
1533 -- API name : RES_TPC_MERGE
1534 --
1535 -- Type : Group
1536 --
1537 -- Pre-reqs : Responses with the given trading_partner_contact_id
1538 -- (p_From_FK_id) must exists in the database
1539 --
1540 -- Function : This procedure will be attached to the TRADING_PARTNER_CONTACT_ID
1541 -- merge for Sourcing PON_BID_HEADERS entity.
1542 --
1543 -- It will veto Party Merge if -
1544 -- p_From_FK_id and p_To_FK_id both are not Seller user party
1545 --
1546 -- This will merge the all the PON_BID_HEADERS records
1547 -- having TRADING_PARTNER_CONTACT_ID equals to p_From_FK_id
1548 -- to party id having value (p_To_FK_id)
1549 --
1550 -- Parameters:
1551 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
1552 -- TCA Merge Dictionary that is going to merge
1553 --
1554 -- IN : p_from_id NUMBER Required, the value of PK of the record
1555 -- which is going to be merged
1556 --
1557 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
1558 -- to which the p_from_id party is going to be merged
1559 --
1560 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
1561 -- Party Site, etc.) when merge is executed
1562 --
1563 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
1564 -- Party Site, etc.) when merge is executed
1565 --
1566 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
1567 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
1568 --
1569 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
1570 -- Party Merge is executed
1571 --
1572 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
1573 -- for which the Party Merge is executed
1574 --
1575 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
1576 -- was successful or not; It can have the following values -
1577 --
1578 -- FND_API.G_RET_STS_SUCCESS (Success)
1579 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
1580 -- failed due to Unexpected error)
1581 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
1582 -- vetod the Party Merge)
1583 --
1584 -- Version : Current version 1.0
1585 -- Previous version 1.0
1586 -- Initial version 1.0
1587 --
1588 -- End of comments
1589 PROCEDURE RES_TPC_MERGE (
1590 p_Entity_name IN VARCHAR2,
1591 p_from_id IN NUMBER,
1592 x_to_id IN OUT NOCOPY NUMBER ,
1593 p_From_FK_id IN NUMBER,
1594 p_To_FK_id IN NUMBER,
1595 p_Parent_Entity_name IN VARCHAR2,
1596 p_batch_id IN NUMBER,
1597 p_Batch_Party_id IN NUMBER,
1598 x_return_status IN OUT NOCOPY VARCHAR2 );
1599
1600 -- Start of comments
1601 -- API name : OPTMZ_TPC_MERGE
1602 --
1603 -- Type : Group
1604 --
1605 -- Pre-reqs : Optimization Scenario with the given trading_partner_contact_id
1606 -- (p_From_FK_id) must exists in the database
1607 --
1608 -- Function : This procedure will be attached to the TRADING_PARTNER_CONTACT_ID
1609 -- merge for Sourcing PON_OPTIMIZE_CONSTRAINTS entity.
1610 --
1611 -- It will veto Party Merge if -
1612 -- p_From_FK_id and p_To_FK_id both are not Seller user party
1613 --
1614 -- This will merge the all the PON_OPTIMIZE_CONSTRAINTS records
1615 -- having TRADING_PARTNER_CONTACT_ID equals to p_From_FK_id
1616 -- to party id having value (p_To_FK_id)
1617 --
1618 -- Parameters:
1619 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
1620 -- TCA Merge Dictionary that is going to merge
1621 --
1622 -- IN : p_from_id NUMBER Required, the value of PK of the record
1623 -- which is going to be merged
1624 --
1625 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
1629 -- Party Site, etc.) when merge is executed
1626 -- to which the p_from_id party is going to be merged
1627 --
1628 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
1630 --
1631 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
1632 -- Party Site, etc.) when merge is executed
1633 --
1634 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
1635 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
1636 --
1637 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
1638 -- Party Merge is executed
1639 --
1640 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
1641 -- for which the Party Merge is executed
1642 --
1643 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
1644 -- was successful or not; It can have the following values -
1645 --
1646 -- FND_API.G_RET_STS_SUCCESS (Success)
1647 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
1648 -- failed due to Unexpected error)
1649 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
1650 -- vetod the Party Merge)
1651 --
1652 -- Version : Current version 1.0
1653 -- Previous version 1.0
1654 -- Initial version 1.0
1655 --
1656 -- End of comments
1657 PROCEDURE OPTMZ_TPC_MERGE (
1658 p_Entity_name IN VARCHAR2,
1659 p_from_id IN NUMBER,
1660 x_to_id IN OUT NOCOPY NUMBER ,
1661 p_From_FK_id IN NUMBER,
1662 p_To_FK_id IN NUMBER,
1663 p_Parent_Entity_name IN VARCHAR2,
1664 p_batch_id IN NUMBER,
1665 p_Batch_Party_id IN NUMBER,
1666 x_return_status IN OUT NOCOPY VARCHAR2 );
1667
1668 -- Start of comments
1669 -- API name : RES_ACK_MERGE
1670 --
1671 -- Type : Group
1672 --
1673 -- Pre-reqs : Invitation Response with the given trading_partner_contact_id
1674 -- (p_From_FK_id) must exists in the database
1675 --
1676 -- Function : This procedure will be attached to the TRADING_PARTNER_CONTACT_ID
1677 -- merge for Sourcing PON_ACKNOWLEDGEMENTS entity.
1678 --
1679 -- It will veto Party Merge if -
1680 -- p_From_FK_id and p_To_FK_id both are not Seller user party
1681 --
1682 -- This will merge the all the PON_ACKNOWLEDGEMENTS records
1683 -- having TRADING_PARTNER_CONTACT_ID equals to p_From_FK_id
1684 -- to party id having value (p_To_FK_id)
1685 --
1686 -- Parameters:
1687 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
1688 -- TCA Merge Dictionary that is going to merge
1689 --
1690 -- IN : p_from_id NUMBER Required, the value of PK of the record
1691 -- which is going to be merged
1692 --
1693 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
1694 -- to which the p_from_id party is going to be merged
1695 --
1696 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
1697 -- Party Site, etc.) when merge is executed
1698 --
1699 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
1700 -- Party Site, etc.) when merge is executed
1701 --
1702 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
1703 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
1704 --
1705 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
1706 -- Party Merge is executed
1707 --
1708 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
1709 -- for which the Party Merge is executed
1710 --
1711 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
1712 -- was successful or not; It can have the following values -
1713 --
1714 -- FND_API.G_RET_STS_SUCCESS (Success)
1715 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
1716 -- failed due to Unexpected error)
1717 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
1718 -- vetod the Party Merge)
1719 --
1720 -- Version : Current version 1.0
1724 -- End of comments
1721 -- Previous version 1.0
1722 -- Initial version 1.0
1723 --
1725 PROCEDURE RES_ACK_MERGE (
1726 p_Entity_name IN VARCHAR2,
1727 p_from_id IN NUMBER,
1728 x_to_id IN OUT NOCOPY NUMBER ,
1729 p_From_FK_id IN NUMBER,
1730 p_To_FK_id IN NUMBER,
1731 p_Parent_Entity_name IN VARCHAR2,
1732 p_batch_id IN NUMBER,
1733 p_Batch_Party_id IN NUMBER,
1734 x_return_status IN OUT NOCOPY VARCHAR2 );
1735
1736
1737 -- Start of comments
1738 -- API name : AUC_SUMM_TPC_MERGE
1739 --
1740 -- Type : Group
1741 --
1742 -- Pre-reqs : Award Summary records with the given trading_partner_contact_id
1743 -- (p_From_FK_id) must exists in the database
1744 --
1745 -- Function : This procedure will be attached to the TRADING_PARTNER_CONTACT_ID
1746 -- merge for Sourcing PON_AUCTION_SUMMARY entity.
1747 --
1748 -- It will veto Party Merge if -
1749 -- p_From_FK_id and p_To_FK_id both are not Seller user party
1750 --
1751 -- This will merge the all the PON_AUCTION_SUMMARY records
1752 -- having TRADING_PARTNER_CONTACT_ID equals to p_From_FK_id
1753 -- to party id having value (p_To_FK_id)
1754 --
1755 -- Parameters:
1756 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
1757 -- TCA Merge Dictionary that is going to merge
1758 --
1759 -- IN : p_from_id NUMBER Required, the value of PK of the record
1760 -- which is going to be merged
1761 --
1762 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
1763 -- to which the p_from_id party is going to be merged
1764 --
1765 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
1766 -- Party Site, etc.) when merge is executed
1767 --
1768 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
1769 -- Party Site, etc.) when merge is executed
1770 --
1771 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
1772 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
1773 --
1774 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
1775 -- Party Merge is executed
1776 --
1777 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
1778 -- for which the Party Merge is executed
1779 --
1780 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
1781 -- was successful or not; It can have the following values -
1782 --
1783 -- FND_API.G_RET_STS_SUCCESS (Success)
1784 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
1785 -- failed due to Unexpected error)
1786 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
1787 -- vetod the Party Merge)
1788 --
1789 -- Version : Current version 1.0
1790 -- Previous version 1.0
1791 -- Initial version 1.0
1792 --
1793 -- End of comments
1794 PROCEDURE AUC_SUMM_TPC_MERGE (
1795 p_Entity_name IN VARCHAR2,
1796 p_from_id IN NUMBER,
1797 x_to_id IN OUT NOCOPY NUMBER ,
1798 p_From_FK_id IN NUMBER,
1799 p_To_FK_id IN NUMBER,
1800 p_Parent_Entity_name IN VARCHAR2,
1801 p_batch_id IN NUMBER,
1802 p_Batch_Party_id IN NUMBER,
1803 x_return_status IN OUT NOCOPY VARCHAR2 );
1804
1805 -- Start of comments
1806 -- API name : SUP_ACT_MERGE
1807 --
1808 -- Type : Group
1809 --
1810 -- Pre-reqs : Supplier Activity records with the given trading_partner_contact_id
1811 -- (p_From_FK_id) must exists in the database
1812 --
1813 -- Function : This procedure will be attached to the TRADING_PARTNER_CONTACT_ID
1814 -- merge for Sourcing PON_SUPPLIER_ACTIVITIES entity.
1815 --
1816 -- It will veto Party Merge if -
1817 -- p_From_FK_id and p_To_FK_id both are not Seller user party
1818 --
1819 -- This will merge the all the PON_SUPPLIER_ACTIVITIES records
1820 -- having TRADING_PARTNER_CONTACT_ID equals to p_From_FK_id
1821 -- to party id having value (p_To_FK_id)
1822 --
1823 -- Parameters:
1824 -- IN : p_Entity_name VARCHAR2 Required, the Entity name from
1825 -- TCA Merge Dictionary that is going to merge
1826 --
1827 -- IN : p_from_id NUMBER Required, the value of PK of the record
1828 -- which is going to be merged
1829 --
1830 -- IN OUT : x_to_id NUMBER Required, the value of PK of the record
1831 -- to which the p_from_id party is going to be merged
1832 --
1833 -- IN : p_From_FK_id NUMBER Required, value of the from ID (e.g. Party,
1834 -- Party Site, etc.) when merge is executed
1835 --
1836 -- IN : p_To_FK_id NUMBER Required, Value of the to ID (e.g. Party,
1837 -- Party Site, etc.) when merge is executed
1838 --
1839 -- IN : p_Entity_name VARCHAR2 Required, Name of parent HZ
1840 -- table (e.g. HZ_PARTIES, HZ_PARTY_SITES)
1841 --
1842 -- IN : p_batch_id NUMBER Required, ID of the batch in which the
1843 -- Party Merge is executed
1844 --
1845 -- IN : p_Batch_Party_id NUMBER Required, ID of the batch and Party record
1846 -- for which the Party Merge is executed
1847 --
1848 -- IN OUT : x_return_status VARCHAR2, flag to indicate if the Party Merge procedure
1849 -- was successful or not; It can have the following values -
1850 --
1851 -- FND_API.G_RET_STS_SUCCESS (Success)
1852 -- FND_API.G_RET_STS_UNEXP_ERROR (Not vetoed but
1853 -- failed due to Unexpected error)
1854 -- FND_API.G_RET_STS_ERROR (Failed as the procedure
1855 -- vetod the Party Merge)
1856 --
1857 -- Version : Current version 1.0
1858 -- Previous version 1.0
1859 -- Initial version 1.0
1860 --
1861 -- End of comments
1862 PROCEDURE SUP_ACT_MERGE (
1863 p_Entity_name IN VARCHAR2,
1864 p_from_id IN NUMBER,
1865 x_to_id IN OUT NOCOPY NUMBER ,
1866 p_From_FK_id IN NUMBER,
1867 p_To_FK_id IN NUMBER,
1871 x_return_status IN OUT NOCOPY VARCHAR2 );
1868 p_Parent_Entity_name IN VARCHAR2,
1869 p_batch_id IN NUMBER,
1870 p_Batch_Party_id IN NUMBER,
1872
1873
1874
1875
1876 END PON_TCA_MERGE_PVT;
[Home] [Help]