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.IBU_REQ_PKG dependencies on JTF_VARCHAR2_TABLE_100

Line 82: p_contact_type IN JTF_VARCHAR2_TABLE_100 := null,

78: p_last_updated_by IN NUMBER,
79: p_language IN VARCHAR2,
80: --UCONTACT
81: p_contact_party_id IN JTF_NUMBER_TABLE := null,
82: p_contact_type IN JTF_VARCHAR2_TABLE_100 := null,
83: p_contact_point_id IN JTF_NUMBER_TABLE := null,
84: p_contact_point_type IN JTF_VARCHAR2_TABLE_100 := null,
85: p_contact_primary IN JTF_VARCHAR2_TABLE_100 := null,
86: p_sr_contact_point_id IN JTF_NUMBER_TABLE := null,

Line 84: p_contact_point_type IN JTF_VARCHAR2_TABLE_100 := null,

80: --UCONTACT
81: p_contact_party_id IN JTF_NUMBER_TABLE := null,
82: p_contact_type IN JTF_VARCHAR2_TABLE_100 := null,
83: p_contact_point_id IN JTF_NUMBER_TABLE := null,
84: p_contact_point_type IN JTF_VARCHAR2_TABLE_100 := null,
85: p_contact_primary IN JTF_VARCHAR2_TABLE_100 := null,
86: p_sr_contact_point_id IN JTF_NUMBER_TABLE := null,
87: -- done
88: x_return_status OUT NOCOPY VARCHAR2,

Line 85: p_contact_primary IN JTF_VARCHAR2_TABLE_100 := null,

81: p_contact_party_id IN JTF_NUMBER_TABLE := null,
82: p_contact_type IN JTF_VARCHAR2_TABLE_100 := null,
83: p_contact_point_id IN JTF_NUMBER_TABLE := null,
84: p_contact_point_type IN JTF_VARCHAR2_TABLE_100 := null,
85: p_contact_primary IN JTF_VARCHAR2_TABLE_100 := null,
86: p_sr_contact_point_id IN JTF_NUMBER_TABLE := null,
87: -- done
88: x_return_status OUT NOCOPY VARCHAR2,
89: x_msg_count OUT NOCOPY NUMBER,

Line 120: p_note_status in jtf_varchar2_table_100,

116: p_urgency_id IN NUMBER,
117: p_summary IN VARCHAR2,
118: p_problem_description IN jtf_varchar2_table_32767,
119: p_problem_detail IN jtf_varchar2_table_32767,
120: p_note_status in jtf_varchar2_table_100,
121: p_contact_party_id in jtf_number_table,
122: p_contact_type in jtf_varchar2_table_100,
123: p_contact_point_id IN jtf_number_table,
124: p_contact_point_type in jtf_varchar2_table_100,

Line 122: p_contact_type in jtf_varchar2_table_100,

118: p_problem_description IN jtf_varchar2_table_32767,
119: p_problem_detail IN jtf_varchar2_table_32767,
120: p_note_status in jtf_varchar2_table_100,
121: p_contact_party_id in jtf_number_table,
122: p_contact_type in jtf_varchar2_table_100,
123: p_contact_point_id IN jtf_number_table,
124: p_contact_point_type in jtf_varchar2_table_100,
125: p_contact_primary in jtf_varchar2_table_100,
126:

Line 124: p_contact_point_type in jtf_varchar2_table_100,

120: p_note_status in jtf_varchar2_table_100,
121: p_contact_party_id in jtf_number_table,
122: p_contact_type in jtf_varchar2_table_100,
123: p_contact_point_id IN jtf_number_table,
124: p_contact_point_type in jtf_varchar2_table_100,
125: p_contact_primary in jtf_varchar2_table_100,
126:
127: p_status_id IN NUMBER,
128: p_severity_id IN NUMBER,

Line 125: p_contact_primary in jtf_varchar2_table_100,

121: p_contact_party_id in jtf_number_table,
122: p_contact_type in jtf_varchar2_table_100,
123: p_contact_point_id IN jtf_number_table,
124: p_contact_point_type in jtf_varchar2_table_100,
125: p_contact_primary in jtf_varchar2_table_100,
126:
127: p_status_id IN NUMBER,
128: p_severity_id IN NUMBER,
129: -- p_owner_id IN NUMBER,

Line 139: p_note_type IN jtf_varchar2_table_100,

135: p_helpdesk_no IN VARCHAR2,
136: p_party_id IN NUMBER,
137: p_solved IN VARCHAR2,
138: p_employee_id IN NUMBER,
139: p_note_type IN jtf_varchar2_table_100,
140: p_contract_id in varchar2,
141: p_project_num in varchar2,
142: p_short_code in varchar2,
143: p_os_version in varchar2,