DBA Data[Home] [Help]

APPS.POS_ACK_PO dependencies on FND_API

Line 27: l_last_update_date IN DATE DEFAULT fnd_api.G_NULL_DATE,

23: l_po_accept_reject IN VARCHAR2,
24: l_po_acc_type_code IN VARCHAR2,
25: l_po_ack_comments IN VARCHAR2 ,
26: l_user_id IN VARCHAR2,
27: l_last_update_date IN DATE DEFAULT fnd_api.G_NULL_DATE,
28: x_error OUT NOCOPY VARCHAR2)
29: IS
30: l_acceptance_id NUMBER;
31: l_revision_num NUMBER := 0;

Line 192: IF (l_last_update_date <> fnd_api.G_NULL_DATE) THEN

188:
189: /*Bug 6772960 - Start
190: Locking the Notification id to allow only one user to update when more than
191: one supplier user tries to acknowledge the PO.*/
192: IF (l_last_update_date <> fnd_api.G_NULL_DATE) THEN
193: BEGIN
194: OPEN NID_CSR(l_nid);
195: FETCH NID_CSR INTO nidRec;
196: if (NID_CSR%NOTFOUND) then

Line 298: IF (l_last_update_date <> fnd_api.G_NULL_DATE) THEN

294: If there is any mismatch in the above dates that means the PO data whatever supplier user
295: seeing currently is not the latest.
296: */
297: -- Lock the PO Header Row for update of Last Update Date
298: IF (l_last_update_date <> fnd_api.G_NULL_DATE) THEN
299: if (l_po_release_id is not null ) then
300: BEGIN
301: OPEN REL_CSR(l_po_release_id);
302: FETCH REL_CSR INTO relRec;