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_SMS_CP_BO

Line 637: p_sms_obj IN HZ_SMS_CP_BO,

633:
634: PROCEDURE create_sms_bo(
635: p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
636: p_validate_bo_flag IN VARCHAR2 := fnd_api.g_true,
637: p_sms_obj IN HZ_SMS_CP_BO,
638: p_created_by_module IN VARCHAR2,
639: x_return_status OUT NOCOPY VARCHAR2,
640: x_msg_count OUT NOCOPY NUMBER,
641: x_msg_data OUT NOCOPY VARCHAR2,

Line 654: * specifically for the API. The object type is HZ_SMS_CP_BO for the SMS business object. In addition to the object's

650:
651: /*#
652: * Create SMS Business Object (create_sms_bo)
653: * Creates a SMS business object. You pass object data to the procedure, packaged within an object type defined
654: * specifically for the API. The object type is HZ_SMS_CP_BO for the SMS business object. In addition to the object's
655: * business object attributes, the object type also includes lower-level embedded child entities or objects that can
656: * be simultaneously created.
657: *
658: * @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 680: p_sms_obj IN HZ_SMS_CP_BO,

676: * @rep:doccd 120hztig.pdf Create SMS Business Object, Oracle Trading Community Architecture Technical Implementation Guide
677: */
678: PROCEDURE create_sms_bo(
679: p_validate_bo_flag IN VARCHAR2 := fnd_api.g_true,
680: p_sms_obj IN HZ_SMS_CP_BO,
681: p_created_by_module IN VARCHAR2,
682: p_obj_source IN VARCHAR2 := null,
683: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
684: x_return_status OUT NOCOPY VARCHAR2,

Line 686: x_return_obj OUT NOCOPY HZ_SMS_CP_BO,

682: p_obj_source IN VARCHAR2 := null,
683: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
684: x_return_status OUT NOCOPY VARCHAR2,
685: x_messages OUT NOCOPY HZ_MESSAGE_OBJ_TBL,
686: x_return_obj OUT NOCOPY HZ_SMS_CP_BO,
687: x_sms_id OUT NOCOPY NUMBER,
688: x_sms_os OUT NOCOPY VARCHAR2,
689: x_sms_osr OUT NOCOPY VARCHAR2,
690: px_parent_id IN OUT NOCOPY NUMBER,

Line 1196: p_sms_obj IN HZ_SMS_CP_BO,

1192: -- 14-DEC-2004 Arnold Ng Created.
1193:
1194: PROCEDURE update_sms_bo(
1195: p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
1196: p_sms_obj IN HZ_SMS_CP_BO,
1197: p_created_by_module IN VARCHAR2,
1198: x_return_status OUT NOCOPY VARCHAR2,
1199: x_msg_count OUT NOCOPY NUMBER,
1200: x_msg_data OUT NOCOPY VARCHAR2,

Line 1209: * defined specifically for the API. The object type is HZ_SMS_CP_BO for the SMS business object. In addition to the

1205:
1206: /*#
1207: * Update SMS Business Object (update_sms_bo)
1208: * Updates a SMS business object. You pass any modified object data to the procedure, packaged within an object type
1209: * defined specifically for the API. The object type is HZ_SMS_CP_BO for the SMS business object. In addition to the
1210: * object's business object attributes, the object type also includes embedded child business entities or objects that
1211: * can be simultaneously created or updated.
1212: *
1213: * @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 1229: p_sms_obj IN HZ_SMS_CP_BO,

1225: * @rep:displayname Update SMS Business Object
1226: * @rep:doccd 120hztig.pdf Update SMS Business Object, Oracle Trading Community Architecture Technical Implementation Guide
1227: */
1228: PROCEDURE update_sms_bo(
1229: p_sms_obj IN HZ_SMS_CP_BO,
1230: p_created_by_module IN VARCHAR2,
1231: p_obj_source IN VARCHAR2 := null,
1232: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
1233: x_return_status OUT NOCOPY VARCHAR2,

Line 1235: x_return_obj OUT NOCOPY HZ_SMS_CP_BO,

1231: p_obj_source IN VARCHAR2 := null,
1232: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
1233: x_return_status OUT NOCOPY VARCHAR2,
1234: x_messages OUT NOCOPY HZ_MESSAGE_OBJ_TBL,
1235: x_return_obj OUT NOCOPY HZ_SMS_CP_BO,
1236: x_sms_id OUT NOCOPY NUMBER,
1237: x_sms_os OUT NOCOPY VARCHAR2,
1238: x_sms_osr OUT NOCOPY VARCHAR2
1239: );

Line 1880: p_sms_obj IN HZ_SMS_CP_BO,

1876:
1877: PROCEDURE save_sms_bo(
1878: p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
1879: p_validate_bo_flag IN VARCHAR2 := fnd_api.g_true,
1880: p_sms_obj IN HZ_SMS_CP_BO,
1881: p_created_by_module IN VARCHAR2,
1882: x_return_status OUT NOCOPY VARCHAR2,
1883: x_msg_count OUT NOCOPY NUMBER,
1884: x_msg_data OUT NOCOPY VARCHAR2,

Line 1898: * identification information, and creates or updates the object. The object type is HZ_SMS_CP_BO for the SMS business

1894: /*#
1895: * Save SMS Business Object (save_sms_bo)
1896: * Saves a SMS business object. You pass new or modified object data to the procedure, packaged within an object type
1897: * defined specifically for the API. The API then determines if the object exists in TCA, based upon the provided
1898: * identification information, and creates or updates the object. The object type is HZ_SMS_CP_BO for the SMS business
1899: * object. For either case, the object type that you provide will be processed as if the respective API procedure is
1900: * being called (create_sms_bo or update_sms_bo). Please see those procedures for more details. In addition to the
1901: * object's business object attributes, the object type also includes embedded child business entities or objects that
1902: * can be simultaneously created or updated.

Line 1926: p_sms_obj IN HZ_SMS_CP_BO,

1922: * @rep:doccd 120hztig.pdf Save SMS Business Object, Oracle Trading Community Architecture Technical Implementation Guide
1923: */
1924: PROCEDURE save_sms_bo(
1925: p_validate_bo_flag IN VARCHAR2 := fnd_api.g_true,
1926: p_sms_obj IN HZ_SMS_CP_BO,
1927: p_created_by_module IN VARCHAR2,
1928: p_obj_source IN VARCHAR2 := null,
1929: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
1930: x_return_status OUT NOCOPY VARCHAR2,

Line 1932: x_return_obj OUT NOCOPY HZ_SMS_CP_BO,

1928: p_obj_source IN VARCHAR2 := null,
1929: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
1930: x_return_status OUT NOCOPY VARCHAR2,
1931: x_messages OUT NOCOPY HZ_MESSAGE_OBJ_TBL,
1932: x_return_obj OUT NOCOPY HZ_SMS_CP_BO,
1933: x_sms_id OUT NOCOPY NUMBER,
1934: x_sms_os OUT NOCOPY VARCHAR2,
1935: x_sms_osr OUT NOCOPY VARCHAR2,
1936: px_parent_id IN OUT NOCOPY NUMBER,

Line 2413: x_sms_obj OUT NOCOPY HZ_SMS_CP_BO,

2409: p_init_msg_list IN VARCHAR2 := FND_API.G_FALSE,
2410: p_sms_id IN NUMBER,
2411: p_sms_os IN VARCHAR2,
2412: p_sms_osr IN VARCHAR2,
2413: x_sms_obj OUT NOCOPY HZ_SMS_CP_BO,
2414: x_return_status OUT NOCOPY VARCHAR2,
2415: x_msg_count OUT NOCOPY NUMBER,
2416: x_msg_data OUT NOCOPY VARCHAR2
2417: );

Line 2438: x_sms_obj OUT NOCOPY HZ_SMS_CP_BO,

2434: PROCEDURE get_sms_bo (
2435: p_sms_id IN NUMBER,
2436: p_sms_os IN VARCHAR2,
2437: p_sms_osr IN VARCHAR2,
2438: x_sms_obj OUT NOCOPY HZ_SMS_CP_BO,
2439: x_return_status OUT NOCOPY VARCHAR2,
2440: x_messages OUT NOCOPY HZ_MESSAGE_OBJ_TBL
2441: );
2442:

Line 2455: p_sms_obj IN HZ_SMS_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,
2456: p_cp_pref_objs IN OUT NOCOPY HZ_CONTACT_PREF_OBJ_TBL,
2457: p_cp_type IN VARCHAR2,
2458: p_created_by_module IN VARCHAR2,
2459: p_obj_source IN VARCHAR2 := null,

Line 2483: p_sms_obj IN HZ_SMS_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,
2484: p_cp_pref_objs IN OUT NOCOPY HZ_CONTACT_PREF_OBJ_TBL,
2485: p_cp_type IN VARCHAR2,
2486: p_created_by_module IN VARCHAR2,
2487: p_obj_source IN VARCHAR2 := null,

Line 2509: p_sms_obj IN HZ_SMS_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,
2510: p_cp_pref_objs IN OUT NOCOPY HZ_CONTACT_PREF_OBJ_TBL,
2511: p_cp_type IN VARCHAR2,
2512: p_created_by_module IN VARCHAR2,
2513: p_obj_source IN VARCHAR2 := null,