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_EXTRACT_PERSON_CUST_BO_PVT dependencies on HZ_PERSON_CUST_BO

Line 68: x_person_cust_obj OUT NOCOPY HZ_PERSON_CUST_BO,

64: PROCEDURE get_person_cust_bo(
65: p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
66: p_person_id IN NUMBER,
67: p_action_type IN VARCHAR2 := NULL,
68: x_person_cust_obj OUT NOCOPY HZ_PERSON_CUST_BO,
69: x_return_status OUT NOCOPY VARCHAR2,
70: x_msg_count OUT NOCOPY NUMBER,
71: x_msg_data OUT NOCOPY VARCHAR2
72: );

Line 136: x_person_cust_objs OUT NOCOPY HZ_PERSON_CUST_BO_TBL,

132:
133: PROCEDURE get_person_custs_created(
134: p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
135: p_event_id IN NUMBER,
136: x_person_cust_objs OUT NOCOPY HZ_PERSON_CUST_BO_TBL,
137: x_return_status OUT NOCOPY VARCHAR2,
138: x_msg_count OUT NOCOPY NUMBER,
139: x_msg_data OUT NOCOPY VARCHAR2
140: );

Line 150: --the procedure returns database objects of the type HZ_PERSON_CUST_BO for all of

146: -- PROCEDURE get_person_custs_updated
147: --
148: -- DESCRIPTION
149: --The caller provides an identifier for the Person Customers update business event and
150: --the procedure returns database objects of the type HZ_PERSON_CUST_BO for all of
151: --the Person Customer business objects from the business event.
152:
153: --
154: -- EXTERNAL PROCEDURES/FUNCTIONS ACCESSED

Line 184: objects of the type HZ_PERSON_CUST_BO for all of the Person Customer business objects from the business event.

180: The Get Person Customers Updated procedure is a service to retrieve all of the Person Customer business objects whose
181: updates have been captured by the logical business event. Each Person Customers Updated business event signifies that
182: one or more Person Customer business objects have been updated.
183: The caller provides an identifier for the Person Customers Update business event and the procedure returns database
184: objects of the type HZ_PERSON_CUST_BO for all of the Person Customer business objects from the business event.
185: Gathering all of the returned database objects from those API calls, the procedure packages them in a table structure
186: and returns them to the caller.
187: */
188:

Line 192: x_person_cust_objs OUT NOCOPY HZ_PERSON_CUST_BO_TBL,

188:
189: PROCEDURE get_person_custs_updated(
190: p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
191: p_event_id IN NUMBER,
192: x_person_cust_objs OUT NOCOPY HZ_PERSON_CUST_BO_TBL,
193: x_return_status OUT NOCOPY VARCHAR2,
194: x_msg_count OUT NOCOPY NUMBER,
195: x_msg_data OUT NOCOPY VARCHAR2
196: );

Line 204: --the procedure returns one database object of the type HZ_PERSON_CUST_BO

200: -- PROCEDURE get_person_cust_updated
201: --
202: -- DESCRIPTION
203: --The caller provides an identifier for the Person customer update business event and person id
204: --the procedure returns one database object of the type HZ_PERSON_CUST_BO
205: --
206: -- EXTERNAL PROCEDURES/FUNCTIONS ACCESSED
207: --
208: -- ARGUMENTS

Line 234: x_person_cust_obj OUT NOCOPY HZ_PERSON_CUST_BO,

230: PROCEDURE get_person_cust_updated(
231: p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
232: p_event_id IN NUMBER,
233: p_person_cust_id IN NUMBER,
234: x_person_cust_obj OUT NOCOPY HZ_PERSON_CUST_BO,
235: x_return_status OUT NOCOPY VARCHAR2,
236: x_msg_count OUT NOCOPY NUMBER,
237: x_msg_data OUT NOCOPY VARCHAR2
238: );