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.IGS_TR_GEN_002 dependencies on IGS_TR_STEP

Line 78: existing IGS_GE_NOTE records and insert IGS_TR_STEP_NOTES

74:
75: Purpose:
76: 1. This program unit is used to insert the default tracking_steps for an item
77: based on the IGS_TR_TYPE and its associated tracking_type_steps, duplicate
78: existing IGS_GE_NOTE records and insert IGS_TR_STEP_NOTES
79:
80: Usage: (e.g. restricted, unrestricted, where to call from)
81: 1. Called from IGSTR007.FMB upon creation of a tracking item.
82:

Line 139: a IGS_TR_STEP record.

135: Date created:
136:
137: Purpose:
138: 1. This module will update fields of the action days of
139: a IGS_TR_STEP record.
140: Usage: (e.g. restricted, unrestricted, where to call from)
141: 1. Called from IGSTR007.FMB
142:
143: Known limitations/enhancements/remarks:

Line 167: Purpose: This procedure will synchronise the content of the table IGS_TR_STEP_GRP_LMT with the content

163: /***********************************************************************************************************
164:
165: Created By: pradhakr
166: Date Created By: 11-Feb-2002
167: Purpose: This procedure will synchronise the content of the table IGS_TR_STEP_GRP_LMT with the content
168: of IGS_TR_TYPE_STEP_V.
169: 1. If that step group being deleted in form IGSTR001 ( block tracking step) is the last one of its
170: kind for a particular tracking id, the step group id will be deleted from IGS_TR_TSTP_GRP_LMT
171: else Step Group Limit will be decremented by 1.

Line 192: Purpose: This procedure will synchronise the content of the table IGS_TR_STEP_GRP_LMT with the content

188: Created By: Arun Iyer
189:
190: Date Created By: 13-Feb-2002
191:
192: Purpose: This procedure will synchronise the content of the table IGS_TR_STEP_GRP_LMT with the content
193: of IGS_TR_STEP_V.
194: 1. If that step group being deleted in form IGSTR007 ( block tracking step) is the last one of its
195: kind for a particular tracking id, the step group id will be deleted from IGS_TR_STEP_GRP_LMT
196:

Line 193: of IGS_TR_STEP_V.

189:
190: Date Created By: 13-Feb-2002
191:
192: Purpose: This procedure will synchronise the content of the table IGS_TR_STEP_GRP_LMT with the content
193: of IGS_TR_STEP_V.
194: 1. If that step group being deleted in form IGSTR007 ( block tracking step) is the last one of its
195: kind for a particular tracking id, the step group id will be deleted from IGS_TR_STEP_GRP_LMT
196:
197: 2. Any new Step Group ID being created in the form IGSTR007 ( block tracking step) will also be created

Line 195: kind for a particular tracking id, the step group id will be deleted from IGS_TR_STEP_GRP_LMT

191:
192: Purpose: This procedure will synchronise the content of the table IGS_TR_STEP_GRP_LMT with the content
193: of IGS_TR_STEP_V.
194: 1. If that step group being deleted in form IGSTR007 ( block tracking step) is the last one of its
195: kind for a particular tracking id, the step group id will be deleted from IGS_TR_STEP_GRP_LMT
196:
197: 2. Any new Step Group ID being created in the form IGSTR007 ( block tracking step) will also be created
198: in the table IGS_TR_STEP_GRP_LMT and the Step Group Limit would be defaulted to 1.
199:

Line 198: in the table IGS_TR_STEP_GRP_LMT and the Step Group Limit would be defaulted to 1.

194: 1. If that step group being deleted in form IGSTR007 ( block tracking step) is the last one of its
195: kind for a particular tracking id, the step group id will be deleted from IGS_TR_STEP_GRP_LMT
196:
197: 2. Any new Step Group ID being created in the form IGSTR007 ( block tracking step) will also be created
198: in the table IGS_TR_STEP_GRP_LMT and the Step Group Limit would be defaulted to 1.
199:
200: 3. In case IGS_TR_STEP_GRP_LMT.STEP_GROUP_LIMIT is greater than the count of step_group_id's for tracking_id and step_group_id
201: combination in IGS_TR_STEP_V view then set it equal to the lower value (i.e count of step_group_id's in the IGS_TR_STEP_V).
202:

Line 200: 3. In case IGS_TR_STEP_GRP_LMT.STEP_GROUP_LIMIT is greater than the count of step_group_id's for tracking_id and step_group_id

196:
197: 2. Any new Step Group ID being created in the form IGSTR007 ( block tracking step) will also be created
198: in the table IGS_TR_STEP_GRP_LMT and the Step Group Limit would be defaulted to 1.
199:
200: 3. In case IGS_TR_STEP_GRP_LMT.STEP_GROUP_LIMIT is greater than the count of step_group_id's for tracking_id and step_group_id
201: combination in IGS_TR_STEP_V view then set it equal to the lower value (i.e count of step_group_id's in the IGS_TR_STEP_V).
202:
203:
204: Known limitations,enhancements,remarks:

Line 201: combination in IGS_TR_STEP_V view then set it equal to the lower value (i.e count of step_group_id's in the IGS_TR_STEP_V).

197: 2. Any new Step Group ID being created in the form IGSTR007 ( block tracking step) will also be created
198: in the table IGS_TR_STEP_GRP_LMT and the Step Group Limit would be defaulted to 1.
199:
200: 3. In case IGS_TR_STEP_GRP_LMT.STEP_GROUP_LIMIT is greater than the count of step_group_id's for tracking_id and step_group_id
201: combination in IGS_TR_STEP_V view then set it equal to the lower value (i.e count of step_group_id's in the IGS_TR_STEP_V).
202:
203:
204: Known limitations,enhancements,remarks:
205:

Line 211: PROCEDURE sync_trk_item_grplmt ( p_tracking_id IGS_TR_STEP_V.tracking_id %TYPE,

207:
208: Who When What
209: ************************************************************************************************************/
210:
211: PROCEDURE sync_trk_item_grplmt ( p_tracking_id IGS_TR_STEP_V.tracking_id %TYPE,
212: p_execute VARCHAR2 DEFAULT 'N'
213: ) ;
214:
215:

Line 238: FUNCTION validate_completion_status ( p_tracking_id IN IGS_TR_STEP_V.TRACKING_ID%TYPE,

234:
235: Who When What
236: ************************************************************************************************************/
237:
238: FUNCTION validate_completion_status ( p_tracking_id IN IGS_TR_STEP_V.TRACKING_ID%TYPE,
239: p_tracking_status IN IGS_TR_ITEM_V.TRACKING_STATUS%TYPE,
240: p_sequence_ind IN IGS_TR_ITEM_V.SEQUENCE_IND%TYPE,
241: p_message_name OUT NOCOPY VARCHAR2
242: ) RETURN BOOLEAN;

Line 258: p_tracking_id igs_tr_step.tracking_id%TYPE,

254: Who When What
255: pradhakr 14-Feb-2002 Added a parameter step_group_id in the function.
256: ************************************************************************************************************/
257: FUNCTION trkp_prev_step_cmplt (
258: p_tracking_id igs_tr_step.tracking_id%TYPE,
259: p_tracking_step_number igs_tr_step.tracking_step_number%TYPE,
260: p_step_group_id igs_tr_step.step_group_id%TYPE,
261: p_message_name OUT NOCOPY VARCHAR2
262: ) RETURN BOOLEAN ;

Line 259: p_tracking_step_number igs_tr_step.tracking_step_number%TYPE,

255: pradhakr 14-Feb-2002 Added a parameter step_group_id in the function.
256: ************************************************************************************************************/
257: FUNCTION trkp_prev_step_cmplt (
258: p_tracking_id igs_tr_step.tracking_id%TYPE,
259: p_tracking_step_number igs_tr_step.tracking_step_number%TYPE,
260: p_step_group_id igs_tr_step.step_group_id%TYPE,
261: p_message_name OUT NOCOPY VARCHAR2
262: ) RETURN BOOLEAN ;
263:

Line 260: p_step_group_id igs_tr_step.step_group_id%TYPE,

256: ************************************************************************************************************/
257: FUNCTION trkp_prev_step_cmplt (
258: p_tracking_id igs_tr_step.tracking_id%TYPE,
259: p_tracking_step_number igs_tr_step.tracking_step_number%TYPE,
260: p_step_group_id igs_tr_step.step_group_id%TYPE,
261: p_message_name OUT NOCOPY VARCHAR2
262: ) RETURN BOOLEAN ;
263:
264: