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_EFT_CP_BO

Line 540: p_eft_obj IN HZ_EFT_CP_BO,

536:
537: PROCEDURE create_eft_bo(
538: p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
539: p_validate_bo_flag IN VARCHAR2 := fnd_api.g_true,
540: p_eft_obj IN HZ_EFT_CP_BO,
541: p_created_by_module IN VARCHAR2,
542: x_return_status OUT NOCOPY VARCHAR2,
543: x_msg_count OUT NOCOPY NUMBER,
544: x_msg_data OUT NOCOPY VARCHAR2,

Line 557: * specifically for the API. The object type is HZ_EFT_CP_BO for the EFT business object. In addition to the object's

553:
554: /*#
555: * Create EFT Business Object (create_eft_bo)
556: * Creates a EFT business object. You pass object data to the procedure, packaged within an object type defined
557: * specifically for the API. The object type is HZ_EFT_CP_BO for the EFT business object. In addition to the object's
558: * business object attributes, the object type also includes lower-level embedded child entities or objects that can
559: * be simultaneously created.
560: *
561: * @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 583: p_eft_obj IN HZ_EFT_CP_BO,

579: * @rep:doccd 120hztig.pdf Create EFT Business Object, Oracle Trading Community Architecture Technical Implementation Guide
580: */
581: PROCEDURE create_eft_bo(
582: p_validate_bo_flag IN VARCHAR2 := fnd_api.g_true,
583: p_eft_obj IN HZ_EFT_CP_BO,
584: p_created_by_module IN VARCHAR2,
585: p_obj_source IN VARCHAR2 := null,
586: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
587: x_return_status OUT NOCOPY VARCHAR2,

Line 589: x_return_obj OUT NOCOPY HZ_EFT_CP_BO,

585: p_obj_source IN VARCHAR2 := null,
586: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
587: x_return_status OUT NOCOPY VARCHAR2,
588: x_messages OUT NOCOPY HZ_MESSAGE_OBJ_TBL,
589: x_return_obj OUT NOCOPY HZ_EFT_CP_BO,
590: x_eft_id OUT NOCOPY NUMBER,
591: x_eft_os OUT NOCOPY VARCHAR2,
592: x_eft_osr OUT NOCOPY VARCHAR2,
593: px_parent_id IN OUT NOCOPY NUMBER,

Line 1116: p_eft_obj IN HZ_EFT_CP_BO,

1112: -- 14-DEC-2004 Arnold Ng Created.
1113:
1114: PROCEDURE update_eft_bo(
1115: p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
1116: p_eft_obj IN HZ_EFT_CP_BO,
1117: p_created_by_module IN VARCHAR2,
1118: x_return_status OUT NOCOPY VARCHAR2,
1119: x_msg_count OUT NOCOPY NUMBER,
1120: x_msg_data OUT NOCOPY VARCHAR2,

Line 1129: * defined specifically for the API. The object type is HZ_EFT_CP_BO for the EFT business object. In addition to the

1125:
1126: /*#
1127: * Update EFT Business Object (update_eft_bo)
1128: * Updates a EFT business object. You pass any modified object data to the procedure, packaged within an object type
1129: * defined specifically for the API. The object type is HZ_EFT_CP_BO for the EFT business object. In addition to the
1130: * object's business object attributes, the object type also includes embedded child business entities or objects that
1131: * can be simultaneously created or updated.
1132: *
1133: * @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 1149: p_eft_obj IN HZ_EFT_CP_BO,

1145: * @rep:displayname Update EFT Business Object
1146: * @rep:doccd 120hztig.pdf Update EFT Business Object, Oracle Trading Community Architecture Technical Implementation Guide
1147: */
1148: PROCEDURE update_eft_bo(
1149: p_eft_obj IN HZ_EFT_CP_BO,
1150: p_created_by_module IN VARCHAR2,
1151: p_obj_source IN VARCHAR2 := null,
1152: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
1153: x_return_status OUT NOCOPY VARCHAR2,

Line 1155: x_return_obj OUT NOCOPY HZ_EFT_CP_BO,

1151: p_obj_source IN VARCHAR2 := null,
1152: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
1153: x_return_status OUT NOCOPY VARCHAR2,
1154: x_messages OUT NOCOPY HZ_MESSAGE_OBJ_TBL,
1155: x_return_obj OUT NOCOPY HZ_EFT_CP_BO,
1156: x_eft_id OUT NOCOPY NUMBER,
1157: x_eft_os OUT NOCOPY VARCHAR2,
1158: x_eft_osr OUT NOCOPY VARCHAR2
1159: );

Line 1780: p_eft_obj IN HZ_EFT_CP_BO,

1776:
1777: PROCEDURE save_eft_bo(
1778: p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
1779: p_validate_bo_flag IN VARCHAR2 := fnd_api.g_true,
1780: p_eft_obj IN HZ_EFT_CP_BO,
1781: p_created_by_module IN VARCHAR2,
1782: x_return_status OUT NOCOPY VARCHAR2,
1783: x_msg_count OUT NOCOPY NUMBER,
1784: x_msg_data OUT NOCOPY VARCHAR2,

Line 1798: * identification information, and creates or updates the object. The object type is HZ_EFT_CP_BO for the EFT business

1794: /*#
1795: * Save EFT Business Object (save_eft_bo)
1796: * Saves a EFT business object. You pass new or modified object data to the procedure, packaged within an object type
1797: * defined specifically for the API. The API then determines if the object exists in TCA, based upon the provided
1798: * identification information, and creates or updates the object. The object type is HZ_EFT_CP_BO for the EFT business
1799: * object. For either case, the object type that you provide will be processed as if the respective API procedure is
1800: * being called (create_eft_bo or update_eft_bo). Please see those procedures for more details. In addition to the
1801: * object's business object attributes, the object type also includes embedded child business entities or objects that
1802: * can be simultaneously created or updated.

Line 1826: p_eft_obj IN HZ_EFT_CP_BO,

1822: * @rep:doccd 120hztig.pdf Save EFT Business Object, Oracle Trading Community Architecture Technical Implementation Guide
1823: */
1824: PROCEDURE save_eft_bo(
1825: p_validate_bo_flag IN VARCHAR2 := fnd_api.g_true,
1826: p_eft_obj IN HZ_EFT_CP_BO,
1827: p_created_by_module IN VARCHAR2,
1828: p_obj_source IN VARCHAR2 := null,
1829: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
1830: x_return_status OUT NOCOPY VARCHAR2,

Line 1832: x_return_obj OUT NOCOPY HZ_EFT_CP_BO,

1828: p_obj_source IN VARCHAR2 := null,
1829: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
1830: x_return_status OUT NOCOPY VARCHAR2,
1831: x_messages OUT NOCOPY HZ_MESSAGE_OBJ_TBL,
1832: x_return_obj OUT NOCOPY HZ_EFT_CP_BO,
1833: x_eft_id OUT NOCOPY NUMBER,
1834: x_eft_os OUT NOCOPY VARCHAR2,
1835: x_eft_osr OUT NOCOPY VARCHAR2,
1836: px_parent_id IN OUT NOCOPY NUMBER,

Line 2344: x_eft_obj OUT NOCOPY HZ_EFT_CP_BO,

2340: p_init_msg_list IN VARCHAR2 := FND_API.G_FALSE,
2341: p_eft_id IN NUMBER,
2342: p_eft_os IN VARCHAR2,
2343: p_eft_osr IN VARCHAR2,
2344: x_eft_obj OUT NOCOPY HZ_EFT_CP_BO,
2345: x_return_status OUT NOCOPY VARCHAR2,
2346: x_msg_count OUT NOCOPY NUMBER,
2347: x_msg_data OUT NOCOPY VARCHAR2
2348: );

Line 2369: x_eft_obj OUT NOCOPY HZ_EFT_CP_BO,

2365: PROCEDURE get_eft_bo (
2366: p_eft_id IN NUMBER,
2367: p_eft_os IN VARCHAR2,
2368: p_eft_osr IN VARCHAR2,
2369: x_eft_obj OUT NOCOPY HZ_EFT_CP_BO,
2370: x_return_status OUT NOCOPY VARCHAR2,
2371: x_messages OUT NOCOPY HZ_MESSAGE_OBJ_TBL
2372: );
2373:

Line 2454: p_eft_obj IN HZ_EFT_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,
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,

Line 2482: p_eft_obj IN HZ_EFT_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,
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,

Line 2508: p_eft_obj IN HZ_EFT_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,
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,