[Home] [Help]
PACKAGE BODY: APPS.CSP_CMERGE
Source
1 PACKAGE BODY CSP_CMERGE as
2 /* $Header: cscm100b.pls 115.1 99/09/13 16:55:11 porting ship $ */
3
4 /* Call all the blocks to update all the table for Service merge.
5 Below is a diagram of the calling sequence.
6
7 CSP_CMERGE.MERGE ( all tables for CS )
8 |
9 |---CSP_CMERGE_BB1.MERGE ( table cs_access_control_templates )
10 | |
11 | CS_MERGE_SYS_INSTALL_SITE_ID
12 | CS_MERGE_SYS_SHIP_USE_ID
13 | CS_MERGE_CP_INSTALL_SITE_ID
14 | CS_MERGE_CP_SHIP_SITE_ID
15 | CS_MERGE_CUSTOMER_ID
16 | CS_CHECK_MERGE_DATA
17 |
18 |---CSP_CMERGE_BB2.MERGE ( table cs_customer_products )
19 | |
20 | CS_MERGE_BILL_TO_SITE_ID
21 | CS_MERGE_INSTALL_SITE_ID
22 | CS_MERGE_SHIP_TO_SITE_ID
23 | CS_MERGE_ORDER_BILL_TO_SITE_ID
24 | CS_MERGE_ORDER_SHIP_TO_SITE_ID
25 | CS_MERGE_CUSTOMER_ID
26 |
27 |---CSP_CMERGE_BB3.MERGE ( table cs_systems )
28 | |
29 | CS_MERGE_BILL_TO_SITE_ID
30 | CS_MERGE_INSTALL_SITE_ID
31 | CS_MERGE_SHIP_TO_SITE_ID
32 | CS_MERGE_CUSTOMER_ID
33 | CS_CHECK_MERGE_DATA
34 |
35 |---CSP_CMERGE_BB4.MERGE ( table cs_templates_interface )
36 | |
37 | CS_MERGE_SYS_INSTALL_SITE_ID
38 | CS_MERGE_SYS_SHIP_TO_SITE_ID
39 | CS_MERGE_CP_INSTALL_SITE_ID
40 | CS_MERGE_CP_SHIP_TO_SITE_ID
41
42 | CS_MERGE_CUSTOMER_ID
43 | CS_CHECK_MERGE_DATA
44 |
45 |---CSP_CMERGE_BB5.MERGE ( table cs_mass_notification_txns_temp )
46 | |
47 | CS_MERGE_CUSTOMER_ID
48 |
49 |---CSP_CMERGE_BB6.MERGE ( table cs_mass_service_txns_temp )
50 |
51 | CS_MERGE_CUSTOMER_ID
52 |
53 |---CSP_CMERGE_BB7.MERGE (table cs_repairs)
54 | |
55 | RMA_CUSTOMER_ID
56 |
57 |---CSP_CMERGE_BB8.MERGE (table cs_incidents)
58 | |
59 | CUSTOMER_ID
60 | SHIP_TO_SITE_USE_ID
61 | BILL_TO_SITE_USE_ID
62 | INSTALL_TO_SITE_USE_ID
63
64
65
66 */
67
68 PROCEDURE MERGE ( req_id IN NUMBER,
69 set_number IN NUMBER,
70 process_mode IN VARCHAR2 ) IS
71
72 /* used to store a free form text to be written to the log file */
73
74 message_text VARCHAR2(255);
75
76 BEGIN
77
78 /* CS is not functional in base 11i and to avoid any problems in other
79 products RETURN is added as first statement in merge procedure. We
80 came across a bug#970262. This is because in earlier versions merge
81 updates record in CS_SYSTEM table now this table is a view on
82 CS_SYSTEM_B and CS_SYSTEM_TL. This endup in failing customer merge
83 in one of the AR's customer merge program. To avoid such kind of
84 problems before CS release return is added.
85 */
86
87 RETURN;
88
89
90 /* call the package that will merge cs_access_control_templates */
91
92 arp_message.set_line('CP_CMERGE.MERGE()+');
93
94 message_text := '******** -- STARTING THE MERGE PROCESS FOR CUSTOMER SERVICE -- ********';
95 arp_message.put_line(message_text);
96
97 CSP_CMERGE_BB1.MERGE ( req_id,
98 set_number,
99 process_mode );
100
104
101 CSP_CMERGE_BB2.MERGE ( req_id,
102 set_number,
103 process_mode );
105 CSP_CMERGE_BB3.MERGE ( req_id,
106 set_number,
107 process_mode );
108
109 CSP_CMERGE_BB4.MERGE ( req_id,
110 set_number,
111 process_mode );
112
113 CSP_CMERGE_BB5.MERGE ( req_id,
114 set_number,
115 process_mode );
116
117 CSP_CMERGE_BB6.MERGE ( req_id,
118 set_number,
119 process_mode );
120
121 CSP_CMERGE_BB7.MERGE ( req_id,
122 set_number,
123 process_mode );
124
125 CSP_CMERGE_BB8.MERGE ( req_id,
126 set_number,
127 process_mode );
128
129 message_text := '******** -- MERGE PROCESS FOR CUSTOMER SERVICE HAS COMPLETED -- ********';
130 arp_message.put_line(message_text);
131
132 arp_message.set_line('CP_CMERGE.MERGE()-');
133
134 END MERGE;
135
136
137 END CSP_CMERGE;