1 PACKAGE XNB_UTIL_PVT AUTHID CURRENT_USER AS
2 /* $Header: XNBVUTYS.pls 120.3 2006/06/25 13:38:24 pselvam noship $ */
3
4 -- Name
5 -- update_cln
6 -- Purpose
7 -- Private procedure that raises the CLN event to update collaboration.
8 -- Arguments
9 -- p_doc_status - Document Status for this update
10 -- p_app_ref_id - Application Reference ID for the collaboration
11 -- p_orig_ref - Originator Reference ID
12 -- p_intl_ctrl_no - Internal Control Number
13 -- p_msg_data - Message data.
14 -- Returns
15 -- None
16 -- Notes
17 -- None
18 PROCEDURE update_cln (
19 p_doc_status IN VARCHAR2,
20 p_app_ref_id IN VARCHAR2,
21 p_orig_ref IN VARCHAR2,
22 p_intl_ctrl_no IN NUMBER,
23 p_msg_data IN VARCHAR2
24 );
25
26 -- Name
27 -- check_collaboration_doc_status
28 -- Purpose
29 -- Private procedure to check the status of a document publish in collaboration history
30 -- of Supply Chain Trading Connector (CLN).
31 -- Arguments
32 -- p_doc_no - Document Number for the collaboration
33 -- p_int_txn_type - XML Gateway Internal Transaction Type
34 -- p_int_txn_sub_type - XML Gateway Internal Transaction Subtype
35 -- Returns
36 -- Collaboration Status.
37 -- 1 - EVERY billing Application has sent ATLEAST ONE Confirm BOD with status SUCCESS for the doc.
38 -- 2 - Atleast one of the hub users is yet to confirm success of a publish of the doc
39 -- OR There is no collaboration for the given document number
40 -- -1 - If there was an error during the check.
41 -- Notes
42 -- This procedure will be called by the TCA Account and Sales Order Publish processes
43 -- and will be later replaced by the procedure 'check_doc_collaboration_status'.
44 -- Note that the names of these procedures are very similiar.
45 FUNCTION check_collaboration_doc_status (
46 p_doc_no NUMBER,
47 p_collab_type VARCHAR2
48 ) RETURN NUMBER;
49
50 -- Name
51 -- check_doc_collaboration_status
52 -- Purpose
53 -- Private procedure to check the status of a document publish in collaboration history
54 -- of Supply Chain Trading Connector (CLN).
55 -- Arguments
56 -- p_doc_no - Document Number for the collaboration
57 -- p_int_txn_type - XML Gateway Internal Transaction Type
58 -- p_int_txn_sub_type - XML Gateway Internal Transaction Subtype
59 -- Returns
60 -- Collaboration Status.
61 -- 1 - EVERY billing Application has sent ATLEAST ONE Confirm BOD with status SUCCESS for the doc.
62 -- 2 - Atleast one of the hub users is yet to confirm success of a publish of the doc
63 -- OR There is no collaboration for the given document number
64 -- -1 - If there was an error during the check.
65 -- Notes
66 -- This procedure will be called by the Inventory Item Update and IB Ownership Change
67 -- flows to check the collaboration document status.
68 -- This will eventually replace the procedure 'check_doc_collaboration_status'
69 FUNCTION check_doc_collaboration_status (
70 p_doc_no NUMBER,
71 p_collab_type VARCHAR2
72 ) RETURN NUMBER;
73
74 -- Name
75 -- check_doc_collaboration_status
76 -- Purpose
77 -- Private procedure to check the status of a document publish in collaboration history
78 -- of Supply Chain Trading Connector (CLN).
79 -- Arguments
80 -- p_doc_no - Document Number for the collaboration
81 -- p_int_txn_type - XML Gateway Internal Transaction Type
82 -- p_int_txn_sub_type - XML Gateway Internal Transaction Subtype
83 -- p_tp_loc_code - Billing Application identification code. Source Trading Partner Location Code
84 -- Returns
85 -- Collaboration Status.
86 -- 0 - The given billing application is yet to confirm the document with SUCCESS
87 -- 1 - The given billing application has already confirmed the document with SUCCESS
88 -- -1 - There was an error during the check
89 -- Notes
90 -- None
91 FUNCTION check_cln_billapp_doc_status (
92 p_doc_no NUMBER,
93 p_collab_type VARCHAR2,
94 p_tp_loc_code VARCHAR2
95 ) RETURN NUMBER;
96
97
98 ------------------------------------------------------------------------------------
99 /* Program to return the Flag for the qualifier */
100 /* Account Update Functionality */
101
102 PROCEDURE return_qualifier
103 (
104 p_event_name IN VARCHAR2,
105 p_event_param IN VARCHAR2,
106 p_transaction_id IN VARCHAR2,
107 x_qualifier OUT NOCOPY VARCHAR2
108 );
109
110
111 ------------------------------------------------------------------------------------
112 /* Program to return the ship_to_contact details of an OrderLine */
113 /* R12 : Enhanced Salesorder Functionality */
114
115 /* ST Bug Fix: 5165987 : Ship To Contact Point Issue
116 PROCEDURE return_ship_to_contact
117 (
118 p_ship_to_contact_id IN NUMBER,
119 x_person_identifier OUT NOCOPY VARCHAR2,
120 x_person_title OUT NOCOPY VARCHAR2,
121 x_person_pre_name_adjunct OUT NOCOPY VARCHAR2,
122 x_person_first_name OUT NOCOPY VARCHAR2,
123 x_person_middle_name OUT NOCOPY VARCHAR2,
124 x_person_last_name OUT NOCOPY VARCHAR2,
125 x_person_name_suffix OUT NOCOPY VARCHAR2,
126 x_salutation OUT NOCOPY VARCHAR2,
127 x_email_address OUT NOCOPY VARCHAR2,
128 x_phone_line_type OUT NOCOPY VARCHAR2,
129 x_phone_country_code OUT NOCOPY VARCHAR2,
130 x_phone_area_code OUT NOCOPY VARCHAR2,
131 x_phone_number OUT NOCOPY VARCHAR2
132
133 );
134 */
135 ------------------------------------------------------------------------------------
136 /* Program to return Address details from site_use_id */
137 /* R12 : Enhanced Salesorder Functionality */
138
139
140 PROCEDURE return_address_from_usageid
141 (
142 p_site_use_id IN NUMBER,
143 x_address_line OUT NOCOPY VARCHAR2,
144 x_country OUT NOCOPY VARCHAR2,
145 x_state OUT NOCOPY VARCHAR2,
146 x_county OUT NOCOPY VARCHAR2,
147 x_city OUT NOCOPY VARCHAR2,
148 x_postal_code OUT NOCOPY VARCHAR2
149
150 );
151
152
153 END xnb_util_pvt;
[Home] [Help]