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_CONTACT_POINT_BO_PUB dependencies on HZ_TELEX_CP_BO

Line 152: p_telex_obj IN HZ_TELEX_CP_BO,

148:
149: PROCEDURE create_telex_bo(
150: p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
151: p_validate_bo_flag IN VARCHAR2 := fnd_api.g_true,
152: p_telex_obj IN HZ_TELEX_CP_BO,
153: p_created_by_module IN VARCHAR2,
154: x_return_status OUT NOCOPY VARCHAR2,
155: x_msg_count OUT NOCOPY NUMBER,
156: x_msg_data OUT NOCOPY VARCHAR2,

Line 169: * specifically for the API. The object type is HZ_TELEX_CP_BO for the Telex business object. In addition to the

165:
166: /*#
167: * Create Telex Business Object (create_telex_bo)
168: * Creates a Telex business object. You pass object data to the procedure, packaged within an object type defined
169: * specifically for the API. The object type is HZ_TELEX_CP_BO for the Telex business object. In addition to the
170: * object's business object attributes, the object type also includes lower-level embedded child entities or objects
171: * that can be simultaneously created.
172: *
173: * @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 195: p_telex_obj IN HZ_TELEX_CP_BO,

191: * @rep:doccd 120hztig.pdf Create Telex Business Object, Oracle Trading Community Architecture Technical Implementation Guide
192: */
193: PROCEDURE create_telex_bo(
194: p_validate_bo_flag IN VARCHAR2 := fnd_api.g_true,
195: p_telex_obj IN HZ_TELEX_CP_BO,
196: p_created_by_module IN VARCHAR2,
197: p_obj_source IN VARCHAR2 := null,
198: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
199: x_return_status OUT NOCOPY VARCHAR2,

Line 201: x_return_obj OUT NOCOPY HZ_TELEX_CP_BO,

197: p_obj_source IN VARCHAR2 := null,
198: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
199: x_return_status OUT NOCOPY VARCHAR2,
200: x_messages OUT NOCOPY HZ_MESSAGE_OBJ_TBL,
201: x_return_obj OUT NOCOPY HZ_TELEX_CP_BO,
202: x_telex_id OUT NOCOPY NUMBER,
203: x_telex_os OUT NOCOPY VARCHAR2,
204: x_telex_osr OUT NOCOPY VARCHAR2,
205: px_parent_id IN OUT NOCOPY NUMBER,

Line 801: p_telex_obj IN HZ_TELEX_CP_BO,

797: -- 14-DEC-2004 Arnold Ng Created.
798:
799: PROCEDURE update_telex_bo(
800: p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
801: p_telex_obj IN HZ_TELEX_CP_BO,
802: p_created_by_module IN VARCHAR2,
803: x_return_status OUT NOCOPY VARCHAR2,
804: x_msg_count OUT NOCOPY NUMBER,
805: x_msg_data OUT NOCOPY VARCHAR2,

Line 814: * defined specifically for the API. The object type is HZ_TELEX_CP_BO for the Telex business object. In addition to

810:
811: /*#
812: * Update Telex Business Object (update_telex_bo)
813: * Updates a Telex business object. You pass any modified object data to the procedure, packaged within an object type
814: * defined specifically for the API. The object type is HZ_TELEX_CP_BO for the Telex business object. In addition to
815: * the object's business object attributes, the object type also includes embedded child business entities or objects
816: * that can be simultaneously created or updated.
817: *
818: * @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 834: p_telex_obj IN HZ_TELEX_CP_BO,

830: * @rep:displayname Update Telex Business Object
831: * @rep:doccd 120hztig.pdf Update Telex Business Object, Oracle Trading Community Architecture Technical Implementation Guide
832: */
833: PROCEDURE update_telex_bo(
834: p_telex_obj IN HZ_TELEX_CP_BO,
835: p_created_by_module IN VARCHAR2,
836: p_obj_source IN VARCHAR2 := null,
837: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
838: x_return_status OUT NOCOPY VARCHAR2,

Line 840: x_return_obj OUT NOCOPY HZ_TELEX_CP_BO,

836: p_obj_source IN VARCHAR2 := null,
837: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
838: x_return_status OUT NOCOPY VARCHAR2,
839: x_messages OUT NOCOPY HZ_MESSAGE_OBJ_TBL,
840: x_return_obj OUT NOCOPY HZ_TELEX_CP_BO,
841: x_telex_id OUT NOCOPY NUMBER,
842: x_telex_os OUT NOCOPY VARCHAR2,
843: x_telex_osr OUT NOCOPY VARCHAR2
844: );

Line 1380: p_telex_obj IN HZ_TELEX_CP_BO,

1376:
1377: PROCEDURE save_telex_bo(
1378: p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
1379: p_validate_bo_flag IN VARCHAR2 := fnd_api.g_true,
1380: p_telex_obj IN HZ_TELEX_CP_BO,
1381: p_created_by_module IN VARCHAR2,
1382: x_return_status OUT NOCOPY VARCHAR2,
1383: x_msg_count OUT NOCOPY NUMBER,
1384: x_msg_data OUT NOCOPY VARCHAR2,

Line 1398: * identification information, and creates or updates the object. The object type is HZ_TELEX_CP_BO for the Telex

1394: /*#
1395: * Save Telex Business Object (save_telex_bo)
1396: * Saves a Telex business object. You pass new or modified object data to the procedure, packaged within an object type
1397: * defined specifically for the API. The API then determines if the object exists in TCA, based upon the provided
1398: * identification information, and creates or updates the object. The object type is HZ_TELEX_CP_BO for the Telex
1399: * business object. For either case, the object type that you provide will be processed as if the respective API procedure
1400: * is being called (create_telex_bo or update_telex_bo). Please see those procedures for more details. In addition to
1401: * the object's business object attributes, the object type also includes embedded child business entities or objects
1402: * that can be simultaneously created or updated.

Line 1426: p_telex_obj IN HZ_TELEX_CP_BO,

1422: * @rep:doccd 120hztig.pdf Save Telex Business Object, Oracle Trading Community Architecture Technical Implementation Guide
1423: */
1424: PROCEDURE save_telex_bo(
1425: p_validate_bo_flag IN VARCHAR2 := fnd_api.g_true,
1426: p_telex_obj IN HZ_TELEX_CP_BO,
1427: p_created_by_module IN VARCHAR2,
1428: p_obj_source IN VARCHAR2 := null,
1429: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
1430: x_return_status OUT NOCOPY VARCHAR2,

Line 1432: x_return_obj OUT NOCOPY HZ_TELEX_CP_BO,

1428: p_obj_source IN VARCHAR2 := null,
1429: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
1430: x_return_status OUT NOCOPY VARCHAR2,
1431: x_messages OUT NOCOPY HZ_MESSAGE_OBJ_TBL,
1432: x_return_obj OUT NOCOPY HZ_TELEX_CP_BO,
1433: x_telex_id OUT NOCOPY NUMBER,
1434: x_telex_os OUT NOCOPY VARCHAR2,
1435: x_telex_osr OUT NOCOPY VARCHAR2,
1436: px_parent_id IN OUT NOCOPY NUMBER,

Line 2068: x_telex_obj OUT NOCOPY HZ_TELEX_CP_BO,

2064: p_init_msg_list IN VARCHAR2 := FND_API.G_FALSE,
2065: p_telex_id IN NUMBER,
2066: p_telex_os IN VARCHAR2,
2067: p_telex_osr IN VARCHAR2,
2068: x_telex_obj OUT NOCOPY HZ_TELEX_CP_BO,
2069: x_return_status OUT NOCOPY VARCHAR2,
2070: x_msg_count OUT NOCOPY NUMBER,
2071: x_msg_data OUT NOCOPY VARCHAR2
2072: );

Line 2093: x_telex_obj OUT NOCOPY HZ_TELEX_CP_BO,

2089: PROCEDURE get_telex_bo (
2090: p_telex_id IN NUMBER,
2091: p_telex_os IN VARCHAR2,
2092: p_telex_osr IN VARCHAR2,
2093: x_telex_obj OUT NOCOPY HZ_TELEX_CP_BO,
2094: x_return_status OUT NOCOPY VARCHAR2,
2095: x_messages OUT NOCOPY HZ_MESSAGE_OBJ_TBL
2096: );
2097:

Line 2451: p_telex_obj IN HZ_TELEX_CP_BO,

2447: p_cp_os IN VARCHAR2,
2448: p_cp_osr IN VARCHAR2,
2449: p_phone_obj IN HZ_PHONE_CP_BO,
2450: p_email_obj IN HZ_EMAIL_CP_BO,
2451: p_telex_obj IN HZ_TELEX_CP_BO,
2452: p_web_obj IN HZ_WEB_CP_BO,
2453: p_edi_obj IN HZ_EDI_CP_BO,
2454: p_eft_obj IN HZ_EFT_CP_BO,
2455: p_sms_obj IN HZ_SMS_CP_BO,

Line 2479: p_telex_obj IN HZ_TELEX_CP_BO,

2475: p_cp_os IN VARCHAR2,
2476: p_cp_osr IN VARCHAR2,
2477: p_phone_obj IN HZ_PHONE_CP_BO,
2478: p_email_obj IN HZ_EMAIL_CP_BO,
2479: p_telex_obj IN HZ_TELEX_CP_BO,
2480: p_web_obj IN HZ_WEB_CP_BO,
2481: p_edi_obj IN HZ_EDI_CP_BO,
2482: p_eft_obj IN HZ_EFT_CP_BO,
2483: p_sms_obj IN HZ_SMS_CP_BO,

Line 2505: p_telex_obj IN HZ_TELEX_CP_BO,

2501: p_cp_os IN VARCHAR2,
2502: p_cp_osr IN VARCHAR2,
2503: p_phone_obj IN HZ_PHONE_CP_BO,
2504: p_email_obj IN HZ_EMAIL_CP_BO,
2505: p_telex_obj IN HZ_TELEX_CP_BO,
2506: p_web_obj IN HZ_WEB_CP_BO,
2507: p_edi_obj IN HZ_EDI_CP_BO,
2508: p_eft_obj IN HZ_EFT_CP_BO,
2509: p_sms_obj IN HZ_SMS_CP_BO,