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_LOCATION_BO_PUB dependencies on HZ_LOCATION_OBJ

Line 52: p_location_obj IN HZ_LOCATION_OBJ,

48:
49: PROCEDURE create_location_bo(
50: p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
51: p_validate_bo_flag IN VARCHAR2 := fnd_api.g_true,
52: p_location_obj IN HZ_LOCATION_OBJ,
53: p_created_by_module IN VARCHAR2,
54: x_return_status OUT NOCOPY VARCHAR2,
55: x_msg_count OUT NOCOPY NUMBER,
56: x_msg_data OUT NOCOPY VARCHAR2,

Line 65: * specifically for the API. The object type is HZ_LOCATION_OBJ for the Location business object. In addition to the

61:
62: /*#
63: * Create Location Business Object (create_location_bo)
64: * Creates a Location business object. You pass object data to the procedure, packaged within an object type defined
65: * specifically for the API. The object type is HZ_LOCATION_OBJ for the Location business object. In addition to the
66: * object's business object attributes, the object type also includes lower-level embedded child entities or objects
67: * that can be simultaneously created.
68: *
69: * @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 87: p_location_obj IN HZ_LOCATION_OBJ,

83: * @rep:doccd 120hztig.pdf Create Location Business Object, Oracle Trading Community Architecture Technical Implementation Guide
84: */
85: PROCEDURE create_location_bo(
86: p_validate_bo_flag IN VARCHAR2 := fnd_api.g_true,
87: p_location_obj IN HZ_LOCATION_OBJ,
88: p_created_by_module IN VARCHAR2,
89: p_obj_source IN VARCHAR2 := null,
90: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
91: x_return_status OUT NOCOPY VARCHAR2,

Line 93: x_return_obj OUT NOCOPY HZ_LOCATION_OBJ,

89: p_obj_source IN VARCHAR2 := null,
90: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
91: x_return_status OUT NOCOPY VARCHAR2,
92: x_messages OUT NOCOPY HZ_MESSAGE_OBJ_TBL,
93: x_return_obj OUT NOCOPY HZ_LOCATION_OBJ,
94: x_location_id OUT NOCOPY NUMBER,
95: x_location_os OUT NOCOPY VARCHAR2,
96: x_location_osr OUT NOCOPY VARCHAR2
97: );

Line 132: p_location_obj IN HZ_LOCATION_OBJ,

128: --
129:
130: PROCEDURE update_location_bo(
131: p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
132: p_location_obj IN HZ_LOCATION_OBJ,
133: p_created_by_module IN VARCHAR2,
134: x_return_status OUT NOCOPY VARCHAR2,
135: x_msg_count OUT NOCOPY NUMBER,
136: x_msg_data OUT NOCOPY VARCHAR2,

Line 145: * defined specifically for the API. The object type is HZ_LOCATION_OBJ for the Location business object. In addition to

141:
142: /*#
143: * Update Location Business Object (update_location_bo)
144: * Updates a Location business object. You pass any modified object data to the procedure, packaged within an object type
145: * defined specifically for the API. The object type is HZ_LOCATION_OBJ for the Location business object. In addition to
146: * the object's business object attributes, the object type also includes embedded child business entities or objects that
147: * can be simultaneously created or updated.
148: *
149: * @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 165: p_location_obj IN HZ_LOCATION_OBJ,

161: * @rep:displayname Update Location Business Object
162: * @rep:doccd 120hztig.pdf Update Location Business Object, Oracle Trading Community Architecture Technical Implementation Guide
163: */
164: PROCEDURE update_location_bo(
165: p_location_obj IN HZ_LOCATION_OBJ,
166: p_created_by_module IN VARCHAR2,
167: p_obj_source IN VARCHAR2 := null,
168: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
169: x_return_status OUT NOCOPY VARCHAR2,

Line 171: x_return_obj OUT NOCOPY HZ_LOCATION_OBJ,

167: p_obj_source IN VARCHAR2 := null,
168: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
169: x_return_status OUT NOCOPY VARCHAR2,
170: x_messages OUT NOCOPY HZ_MESSAGE_OBJ_TBL,
171: x_return_obj OUT NOCOPY HZ_LOCATION_OBJ,
172: x_location_id OUT NOCOPY NUMBER,
173: x_location_os OUT NOCOPY VARCHAR2,
174: x_location_osr OUT NOCOPY VARCHAR2
175: );

Line 211: p_location_obj IN HZ_LOCATION_OBJ,

207:
208: PROCEDURE save_location_bo(
209: p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
210: p_validate_bo_flag IN VARCHAR2 := fnd_api.g_true,
211: p_location_obj IN HZ_LOCATION_OBJ,
212: p_created_by_module IN VARCHAR2,
213: x_return_status OUT NOCOPY VARCHAR2,
214: x_msg_count OUT NOCOPY NUMBER,
215: x_msg_data OUT NOCOPY VARCHAR2,

Line 225: * identification information, and creates or updates the object. The object type is HZ_LOCATION_OBJ for the Location

221: /*#
222: * Save Location Business Object (save_location_bo)
223: * Saves a Location business object. You pass new or modified object data to the procedure, packaged within an object type
224: * defined specifically for the API. The API then determines if the object exists in TCA, based upon the provided
225: * identification information, and creates or updates the object. The object type is HZ_LOCATION_OBJ for the Location
226: * business object. For either case, the object type that you provide will be processed as if the respective API procedure
227: * is being called (create_location_bo or update_location_bo). Please see those procedures for more details. In addition to
228: * the object's business object attributes, the object type also includes embedded child business entities or objects that
229: * can be simultaneously created or updated.

Line 249: p_location_obj IN HZ_LOCATION_OBJ,

245: * @rep:doccd 120hztig.pdf Save Location Business Object, Oracle Trading Community Architecture Technical Implementation Guide
246: */
247: PROCEDURE save_location_bo(
248: p_validate_bo_flag IN VARCHAR2 := fnd_api.g_true,
249: p_location_obj IN HZ_LOCATION_OBJ,
250: p_created_by_module IN VARCHAR2,
251: p_obj_source IN VARCHAR2 := null,
252: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
253: x_return_status OUT NOCOPY VARCHAR2,

Line 255: x_return_obj OUT NOCOPY HZ_LOCATION_OBJ,

251: p_obj_source IN VARCHAR2 := null,
252: p_return_obj_flag IN VARCHAR2 := fnd_api.g_true,
253: x_return_status OUT NOCOPY VARCHAR2,
254: x_messages OUT NOCOPY HZ_MESSAGE_OBJ_TBL,
255: x_return_obj OUT NOCOPY HZ_LOCATION_OBJ,
256: x_location_id OUT NOCOPY NUMBER,
257: x_location_os OUT NOCOPY VARCHAR2,
258: x_location_osr OUT NOCOPY VARCHAR2
259: );

Line 317: x_location_obj OUT NOCOPY HZ_LOCATION_OBJ,

313: p_init_msg_list IN VARCHAR2 := FND_API.G_FALSE,
314: p_location_id IN NUMBER,
315: p_location_os IN VARCHAR2,
316: p_location_osr IN VARCHAR2,
317: x_location_obj OUT NOCOPY HZ_LOCATION_OBJ,
318: x_return_status OUT NOCOPY VARCHAR2,
319: x_msg_count OUT NOCOPY NUMBER,
320: x_msg_data OUT NOCOPY VARCHAR2
321: );

Line 342: x_location_obj OUT NOCOPY HZ_LOCATION_OBJ,

338: PROCEDURE get_location_bo (
339: p_location_id IN NUMBER,
340: p_location_os IN VARCHAR2,
341: p_location_osr IN VARCHAR2,
342: x_location_obj OUT NOCOPY HZ_LOCATION_OBJ,
343: x_return_status OUT NOCOPY VARCHAR2,
344: x_messages OUT NOCOPY HZ_MESSAGE_OBJ_TBL
345: );
346:

Line 371: p_location_obj IN HZ_LOCATION_OBJ,

367: -- 02-NOV-2005 Arnold Ng Created.
368: --
369:
370: PROCEDURE assign_location_rec(
371: p_location_obj IN HZ_LOCATION_OBJ,
372: p_loc_os IN VARCHAR2,
373: p_loc_osr IN VARCHAR2,
374: p_create_or_update IN VARCHAR2 := 'C',
375: px_location_rec IN OUT NOCOPY HZ_LOCATION_V2PUB.LOCATION_REC_TYPE