eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.HZ_CUST_ACCT_CONTACT_BO_PUB dependencies on HZ_CUST_ACCT_CONTACT_BO

Line 1: PACKAGE HZ_CUST_ACCT_CONTACT_BO_PUB AS

1: PACKAGE HZ_CUST_ACCT_CONTACT_BO_PUB AS
2: /*$Header: ARHBCRBS.pls 120.7 2006/09/21 17:59:01 acng noship $ */
3: /*#
4: * Customer Account Contact Business Object API
5: * Public API that allows users to manage Customer Account Contact business objects in the Trading Community Architecture.

Line 57: p_cust_acct_contact_obj IN HZ_CUST_ACCT_CONTACT_BO,

53:
54: PROCEDURE create_cust_acct_contact_bo(
55: p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
56: p_validate_bo_flag IN VARCHAR2 := fnd_api.g_true,
57: p_cust_acct_contact_obj IN HZ_CUST_ACCT_CONTACT_BO,
58: p_created_by_module IN VARCHAR2,
59: x_return_status OUT NOCOPY VARCHAR2,
60: x_msg_count OUT NOCOPY NUMBER,
61: x_msg_data OUT NOCOPY VARCHAR2,

Line 74: * type defined specifically for the API. The object type is HZ_CUST_ACCT_CONTACT_BO for the Customer Account Contact

70:
71: /*#
72: * Create Customer Account Contact Business Object (create_cust_acct_contact_bo)
73: * Creates a Customer Account Contact business object. You pass object data to the procedure, packaged within an object
74: * type defined specifically for the API. The object type is HZ_CUST_ACCT_CONTACT_BO for the Customer Account Contact
75: * business object. In addition to the object's business object attributes, the object type also includes lower-level
76: * embedded child entities or objects that can be simultaneously created.
77: *
78: * @param p_return_obj_flag Indicates if the created object is to be returned to the caller as an output parameter. Default value: false

Line 100: p_cust_acct_contact_obj IN HZ_CUST_ACCT_CONTACT_BO,

96: * @rep:doccd 120hztig.pdf Create Customer Account Contact Business Object, Oracle Trading Community Architecture Technical Implementation Guide
97: */
98: PROCEDURE create_cust_acct_contact_bo(
99: p_validate_bo_flag IN VARCHAR2 := fnd_api.g_true,
100: p_cust_acct_contact_obj IN HZ_CUST_ACCT_CONTACT_BO,
101: p_created_by_module IN VARCHAR2,
102: p_obj_source IN VARCHAR2 := null,
103: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
104: x_return_status OUT NOCOPY VARCHAR2,

Line 106: x_return_obj OUT NOCOPY HZ_CUST_ACCT_CONTACT_BO,

102: p_obj_source IN VARCHAR2 := null,
103: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
104: x_return_status OUT NOCOPY VARCHAR2,
105: x_messages OUT NOCOPY HZ_MESSAGE_OBJ_TBL,
106: x_return_obj OUT NOCOPY HZ_CUST_ACCT_CONTACT_BO,
107: x_cust_acct_contact_id OUT NOCOPY NUMBER,
108: x_cust_acct_contact_os OUT NOCOPY VARCHAR2,
109: x_cust_acct_contact_osr OUT NOCOPY VARCHAR2,
110: px_parent_id IN OUT NOCOPY NUMBER,

Line 149: p_cust_acct_contact_obj IN HZ_CUST_ACCT_CONTACT_BO,

145: --
146:
147: PROCEDURE update_cust_acct_contact_bo(
148: p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
149: p_cust_acct_contact_obj IN HZ_CUST_ACCT_CONTACT_BO,
150: p_created_by_module IN VARCHAR2,
151: x_return_status OUT NOCOPY VARCHAR2,
152: x_msg_count OUT NOCOPY NUMBER,
153: x_msg_data OUT NOCOPY VARCHAR2,

Line 162: * an object type defined specifically for the API. The object type is HZ_CUST_ACCT_CONTACT_BO for the Customer Account

158:
159: /*#
160: * Update Customer Account Contact Business Object (update_cust_acct_contact_bo)
161: * Updates a Customer Account Contact business object. You pass any modified object data to the procedure, packaged within
162: * an object type defined specifically for the API. The object type is HZ_CUST_ACCT_CONTACT_BO for the Customer Account
163: * Contact business object. In addition to the object's business object attributes, the object type also includes embedded
164: * child business entities or objects that can be simultaneously created or updated.
165: *
166: * @param p_return_obj_flag Indicates if the updated object is to be returned to the caller as an output parameter. Default value: false

Line 182: p_cust_acct_contact_obj IN HZ_CUST_ACCT_CONTACT_BO,

178: * @rep:displayname Update Customer Account Contact Business Object
179: * @rep:doccd 120hztig.pdf Update Customer Account Contact Business Object, Oracle Trading Community Architecture Technical Implementation Guide
180: */
181: PROCEDURE update_cust_acct_contact_bo(
182: p_cust_acct_contact_obj IN HZ_CUST_ACCT_CONTACT_BO,
183: p_created_by_module IN VARCHAR2,
184: p_obj_source IN VARCHAR2 := null,
185: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
186: x_return_status OUT NOCOPY VARCHAR2,

Line 188: x_return_obj OUT NOCOPY HZ_CUST_ACCT_CONTACT_BO,

184: p_obj_source IN VARCHAR2 := null,
185: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
186: x_return_status OUT NOCOPY VARCHAR2,
187: x_messages OUT NOCOPY HZ_MESSAGE_OBJ_TBL,
188: x_return_obj OUT NOCOPY HZ_CUST_ACCT_CONTACT_BO,
189: x_cust_acct_contact_id OUT NOCOPY NUMBER,
190: x_cust_acct_contact_os OUT NOCOPY VARCHAR2,
191: x_cust_acct_contact_osr OUT NOCOPY VARCHAR2
192: );

Line 235: p_cust_acct_contact_obj IN HZ_CUST_ACCT_CONTACT_BO,

231:
232: PROCEDURE save_cust_acct_contact_bo(
233: p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
234: p_validate_bo_flag IN VARCHAR2 := fnd_api.g_true,
235: p_cust_acct_contact_obj IN HZ_CUST_ACCT_CONTACT_BO,
236: p_created_by_module IN VARCHAR2,
237: x_return_status OUT NOCOPY VARCHAR2,
238: x_msg_count OUT NOCOPY NUMBER,
239: x_msg_data OUT NOCOPY VARCHAR2,

Line 253: * provided identification information, and creates or updates the object. The object type is HZ_CUST_ACCT_CONTACT_BO for

249: /*#
250: * Save Customer Account Contact Business Object (save_cust_acct_contact_bo)
251: * Saves a Customer Account Contact business object. You pass new or modified object data to the procedure, packaged within
252: * an object type defined specifically for the API. The API then determines if the object exists in TCA, based upon the
253: * provided identification information, and creates or updates the object. The object type is HZ_CUST_ACCT_CONTACT_BO for
254: * the Customer Account Contact business object. For either case, the object type that you provide will be processed as if
255: * the respective API procedure is being called (create_cust_acct_contact_bo or update_cust_acct_contact_bo). Please see
256: * those procedures for more details. In addition to the object's business object attributes, the object type also includes
257: * embedded child business entities or objects that can be simultaneously created or updated.

Line 281: p_cust_acct_contact_obj IN HZ_CUST_ACCT_CONTACT_BO,

277: * @rep:doccd 120hztig.pdf Save Customer Account Contact Business Object, Oracle Trading Community Architecture Technical Implementation Guide
278: */
279: PROCEDURE save_cust_acct_contact_bo(
280: p_validate_bo_flag IN VARCHAR2 := fnd_api.g_true,
281: p_cust_acct_contact_obj IN HZ_CUST_ACCT_CONTACT_BO,
282: p_created_by_module IN VARCHAR2,
283: p_obj_source IN VARCHAR2 := null,
284: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
285: x_return_status OUT NOCOPY VARCHAR2,

Line 287: x_return_obj OUT NOCOPY HZ_CUST_ACCT_CONTACT_BO,

283: p_obj_source IN VARCHAR2 := null,
284: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
285: x_return_status OUT NOCOPY VARCHAR2,
286: x_messages OUT NOCOPY HZ_MESSAGE_OBJ_TBL,
287: x_return_obj OUT NOCOPY HZ_CUST_ACCT_CONTACT_BO,
288: x_cust_acct_contact_id OUT NOCOPY NUMBER,
289: x_cust_acct_contact_os OUT NOCOPY VARCHAR2,
290: x_cust_acct_contact_osr OUT NOCOPY VARCHAR2,
291: px_parent_id IN OUT NOCOPY NUMBER,

Line 358: x_cust_acct_contact_obj OUT NOCOPY HZ_CUST_ACCT_CONTACT_BO,

354: p_init_msg_list IN VARCHAR2:=FND_API.G_FALSE,
355: p_cust_acct_contact_id IN NUMBER,
356: p_cust_acct_contact_os IN VARCHAR2,
357: p_cust_acct_contact_osr IN VARCHAR2,
358: x_cust_acct_contact_obj OUT NOCOPY HZ_CUST_ACCT_CONTACT_BO,
359: x_return_status OUT NOCOPY VARCHAR2,
360: x_msg_count OUT NOCOPY NUMBER,
361: x_msg_data OUT NOCOPY VARCHAR2
362: );

Line 384: x_cust_acct_contact_obj OUT NOCOPY HZ_CUST_ACCT_CONTACT_BO,

380: PROCEDURE get_cust_acct_contact_bo (
381: p_cust_acct_contact_id IN NUMBER,
382: p_cust_acct_contact_os IN VARCHAR2,
383: p_cust_acct_contact_osr IN VARCHAR2,
384: x_cust_acct_contact_obj OUT NOCOPY HZ_CUST_ACCT_CONTACT_BO,
385: x_return_status OUT NOCOPY VARCHAR2,
386: x_messages OUT NOCOPY HZ_MESSAGE_OBJ_TBL
387: );
388:

Line 392: p_cust_acct_contact_obj IN OUT NOCOPY HZ_CUST_ACCT_CONTACT_BO,

388:
389: PROCEDURE do_create_cac_bo(
390: p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
391: p_validate_bo_flag IN VARCHAR2 := fnd_api.g_true,
392: p_cust_acct_contact_obj IN OUT NOCOPY HZ_CUST_ACCT_CONTACT_BO,
393: p_created_by_module IN VARCHAR2,
394: p_obj_source IN VARCHAR2 := null,
395: x_return_status OUT NOCOPY VARCHAR2,
396: x_msg_count OUT NOCOPY NUMBER,

Line 409: p_cust_acct_contact_obj IN OUT NOCOPY HZ_CUST_ACCT_CONTACT_BO,

405: );
406:
407: PROCEDURE do_update_cac_bo(
408: p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
409: p_cust_acct_contact_obj IN OUT NOCOPY HZ_CUST_ACCT_CONTACT_BO,
410: p_created_by_module IN VARCHAR2,
411: p_obj_source IN VARCHAR2 := null,
412: x_return_status OUT NOCOPY VARCHAR2,
413: x_msg_count OUT NOCOPY NUMBER,

Line 424: p_cust_acct_contact_obj IN OUT NOCOPY HZ_CUST_ACCT_CONTACT_BO,

420:
421: PROCEDURE do_save_cac_bo(
422: p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
423: p_validate_bo_flag IN VARCHAR2 := fnd_api.g_true,
424: p_cust_acct_contact_obj IN OUT NOCOPY HZ_CUST_ACCT_CONTACT_BO,
425: p_created_by_module IN VARCHAR2,
426: p_obj_source IN VARCHAR2 := null,
427: x_return_status OUT NOCOPY VARCHAR2,
428: x_msg_count OUT NOCOPY NUMBER,

Line 439: END HZ_CUST_ACCT_CONTACT_BO_PUB;

435: px_parent_osr IN OUT NOCOPY VARCHAR2,
436: px_parent_obj_type IN OUT NOCOPY VARCHAR2
437: );
438:
439: END HZ_CUST_ACCT_CONTACT_BO_PUB;