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.INV_PICK_RELEASE_PVT dependencies on FND_API

Line 50: -- fnd_api.g_ret_sts_success;

46: --
47: -- Output Parameters
48: -- x_return_status
49: -- if the process succeeds, the value is
50: -- fnd_api.g_ret_sts_success;
51: -- if there is an expected error, the value is
52: -- fnd_api.g_ret_sts_error;
53: -- if there is an unexpected error, the value is
54: -- fnd_api.g_ret_sts_unexp_error;

Line 52: -- fnd_api.g_ret_sts_error;

48: -- x_return_status
49: -- if the process succeeds, the value is
50: -- fnd_api.g_ret_sts_success;
51: -- if there is an expected error, the value is
52: -- fnd_api.g_ret_sts_error;
53: -- if there is an unexpected error, the value is
54: -- fnd_api.g_ret_sts_unexp_error;
55: -- x_msg_count
56: -- if there is one or more errors, the number of error messages

Line 54: -- fnd_api.g_ret_sts_unexp_error;

50: -- fnd_api.g_ret_sts_success;
51: -- if there is an expected error, the value is
52: -- fnd_api.g_ret_sts_error;
53: -- if there is an unexpected error, the value is
54: -- fnd_api.g_ret_sts_unexp_error;
55: -- x_msg_count
56: -- if there is one or more errors, the number of error messages
57: -- in the buffer
58: -- x_msg_data

Line 60: -- (See fnd_api package for more details about the above output parameters)

56: -- if there is one or more errors, the number of error messages
57: -- in the buffer
58: -- x_msg_data
59: -- if there is one and only one error, the error message
60: -- (See fnd_api package for more details about the above output parameters)
61: --
62: -- Bug8757642. Added p_wave_simulation_mode with default vale 'N' for WavePlanning Project.
63: -- This project is available only in for R121 and mainline. To retain dual maintenance INV code changes are made in branchline, however it will not affect any existing flow.
64:

Line 68: ,p_init_msg_list IN VARCHAR2 DEFAULT fnd_api.g_false

64:
65: PROCEDURE Process_Line
66: (
67: p_api_version IN NUMBER
68: ,p_init_msg_list IN VARCHAR2 DEFAULT fnd_api.g_false
69: ,p_commit IN VARCHAR2 DEFAULT fnd_api.g_false
70: ,x_return_status OUT NOCOPY VARCHAR2
71: ,x_msg_count OUT NOCOPY NUMBER
72: ,x_msg_data OUT NOCOPY VARCHAR2

Line 69: ,p_commit IN VARCHAR2 DEFAULT fnd_api.g_false

65: PROCEDURE Process_Line
66: (
67: p_api_version IN NUMBER
68: ,p_init_msg_list IN VARCHAR2 DEFAULT fnd_api.g_false
69: ,p_commit IN VARCHAR2 DEFAULT fnd_api.g_false
70: ,x_return_status OUT NOCOPY VARCHAR2
71: ,x_msg_count OUT NOCOPY NUMBER
72: ,x_msg_data OUT NOCOPY VARCHAR2
73: ,p_mo_line_rec IN OUT NOCOPY INV_Move_Order_PUB.TROLIN_REC_TYPE

Line 75: ,p_allow_partial_pick IN VARCHAR2 DEFAULT fnd_api.g_true

71: ,x_msg_count OUT NOCOPY NUMBER
72: ,x_msg_data OUT NOCOPY VARCHAR2
73: ,p_mo_line_rec IN OUT NOCOPY INV_Move_Order_PUB.TROLIN_REC_TYPE
74: ,p_grouping_rule_id IN NUMBER
75: ,p_allow_partial_pick IN VARCHAR2 DEFAULT fnd_api.g_true
76: ,p_print_mode IN VARCHAR2
77: ,x_detail_rec_count OUT NOCOPY NUMBER
78: ,p_plan_tasks IN BOOLEAN DEFAULT FALSE
79: ,p_wave_simulation_mode IN VARCHAR2 DEFAULT 'N'

Line 116: -- fnd_api.g_ret_sts_success;

112: --
113: -- Output Parameters
114: -- x_return_status
115: -- if the process succeeds, the value is
116: -- fnd_api.g_ret_sts_success;
117: -- if there is an expected error, the value is
118: -- fnd_api.g_ret_sts_error;
119: -- if there is an unexpected error, the value is
120: -- fnd_api.g_ret_sts_unexp_error;

Line 118: -- fnd_api.g_ret_sts_error;

114: -- x_return_status
115: -- if the process succeeds, the value is
116: -- fnd_api.g_ret_sts_success;
117: -- if there is an expected error, the value is
118: -- fnd_api.g_ret_sts_error;
119: -- if there is an unexpected error, the value is
120: -- fnd_api.g_ret_sts_unexp_error;
121: -- x_msg_count
122: -- if there is one or more errors, the number of error messages

Line 120: -- fnd_api.g_ret_sts_unexp_error;

116: -- fnd_api.g_ret_sts_success;
117: -- if there is an expected error, the value is
118: -- fnd_api.g_ret_sts_error;
119: -- if there is an unexpected error, the value is
120: -- fnd_api.g_ret_sts_unexp_error;
121: -- x_msg_count
122: -- if there is one or more errors, the number of error messages
123: -- in the buffer
124: -- x_msg_data

Line 126: -- (See fnd_api package for more details about the above output parameters)

122: -- if there is one or more errors, the number of error messages
123: -- in the buffer
124: -- x_msg_data
125: -- if there is one and only one error, the error message
126: -- (See fnd_api package for more details about the above output parameters)
127: --
128:
129: PROCEDURE process_prj_dynamic_locator
130: (

Line 182: , p_allow_partial_pick IN VARCHAR2 DEFAULT fnd_api.g_true

178: , p_mo_line_rec IN inv_move_order_pub.trolin_rec_type
179: , p_mso_line_id IN NUMBER
180: , p_demand_source_type IN VARCHAR2
181: , p_demand_source_name IN VARCHAR2
182: , p_allow_partial_pick IN VARCHAR2 DEFAULT fnd_api.g_true
183: , x_demand_rsvs_ordered OUT NOCOPY inv_reservation_global.mtl_reservation_tbl_type
184: , x_rsv_qty_available OUT NOCOPY NUMBER
185: ,x_rsv_qty2_available OUT NOCOPY NUMBER --7377744
186: );