APPS.FTE_TRACKING_WRAPPER dependencies on FTE_TRACKING_STATUS_S

Line 129: MESSAGE_TYPE, FTE_TRACKING_STATUS_S.nextval,

125: ACTIVITY_ID
126: )
127: select
128: l_transaction_id_s, l_delivery_leg_id,l_delivery_id,
129: MESSAGE_TYPE, FTE_TRACKING_STATUS_S.nextval,
130: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN,
131: CARRIER_NAME, GENERATION_DATE , STATUS , TRACKING_ID, TRACKING_ID_TYPE,
132: BILL_OF_LADING , CARRIER_SERVICE_LEVEL, CONTAINER_ID , CONTAINER_SEAL ,
133: ARRIVAL_DATE, RECEIVED_DATE , DELIVERY_SCHEDULED_DATE , DEPARTURE_DATE,

Line 155: select fte_tracking_status_s.nextval into l_content_details_id from dual;

151: END ;
152: -- Insert into details table
153: BEGIN
154:
155: select fte_tracking_status_s.nextval into l_content_details_id from dual;
156: insert into fte_shipment_status_details(
157: SHIPMENT_STATUS_DETAIL_ID,
158: DELIVERY_LEG_ID,
159: TRANSACTION_ID,

Line 198: select fte_tracking_status_s.nextval into l_content_pod_id from dual;

194: NULL; --No records in FTE_SHIPMENT_STATUS_DETAILS
195: END ;
196: -- Insert into delivery proof table
197: BEGIN
198: select fte_tracking_status_s.nextval into l_content_pod_id from dual;
199: insert into fte_delivery_proof(
200: ID,
201: TRANSACTION_ID,
202: RECEIVED_DATE,

Line 271: select fte_tracking_status_s.nextval into l_address_to_id from dual;

267:
268: --Inserting into fte_message partner as per FTEFSSI XGM to content
269: BEGIN
270:
271: select fte_tracking_status_s.nextval into l_address_to_id from dual;
272: INSERT INTO
273: FTE_MESSAGE_PARTNER (
274: ID,
275: NAME1 ,

Line 387: fte_tracking_status_s.nextval,

383: LAST_UPDATE_LOGIN,
384: TRANSACTION_ID
385: )
386: SELECT
387: fte_tracking_status_s.nextval,
388: l_address_to_id,
389: NAME1 ,
390: NAME2 ,
391: NAME3 ,

Line 469: fte_tracking_status_s.nextval,

465: LOCATION_TO_TABLE
466: )
467: SELECT
468: DECODE(location_to_table,'FTE_DELIVERY_PROOF',l_content_pod_id,l_content_details_id),
469: fte_tracking_status_s.nextval,
470: DESCRIPTION ,
471: GEOCOORDINATES ,
472: GEOCOORDINATES_TYPE ,
473: LOCATION_ID ,

Line 559: fte_tracking_status_s.nextval,

555: AND transaction_id = p_transaction_id ) and
556: transaction_id = l_transaction_id_s
557: )
558: ),
559: fte_tracking_status_s.nextval,
560: l_transaction_id_s ,
561: ADDRESS_TO_TABLE ,
562: ADDR_LINE1 ,
563: ADDR_LINE2 ,

Line 631: fte_tracking_status_s.nextval,

627: TRANSACTION_ID
628: )
629: SELECT
630: l_content_details_id,
631: fte_tracking_status_s.nextval,
632: EXCEPTION_DATE ,
633: DESCRIPTION ,
634: REASON_CODE ,
635: CREATED_BY ,

Line 646: select fte_tracking_status_s.currval into l_content_exceptions_id from dual;

642: l_transaction_id_s
643: FROM FTE_SHIPMENT_STATUS_EXCEPTIONS
644: WHERE TRANSACTION_ID = P_TRANSACTION_ID ;
645:
646: select fte_tracking_status_s.currval into l_content_exceptions_id from dual;
647: EXCEPTION
648: WHEN OTHERS THEN
649: null;
650: END ;

Line 685: fte_tracking_status_s.nextval ,

681: LAST_UPDATE_LOGIN ,
682: TRANSACTION_ID
683: )
684: SELECT
685: fte_tracking_status_s.nextval ,
686: DECODE(ATTACH_TO_TABLE,'FTE_MESSAGE_PARTNER',l_address_to_id,
687: 'FTE_SHIPMENT_STATUS_DETAILS',l_content_details_id,
688: 'FTE_SHIPMENT_STATUS_EXCEPTIONS',l_content_exceptions_id,
689: l_content_pod_id),