APPS.WMS_DEVICE_INTEGRATION_PVT dependencies on WMS_BUS_EVENT_DEVICES

Line 682: wms_bus_event_devices wbed,

678:
679: begin
680: seLECT DEVICE_ID INTO dev_ID FROM
681: ( SELECT wbed.DEVICE_ID FROM
682: wms_bus_event_devices wbed,
683: wms_devices_b wd
684: WHERE
685: wd.device_id = wbed.device_id
686: AND WBED.organization_id = WD.organization_id

Line 746: wms_bus_event_devices wbed,

742:
743: BEGIN
744: SELECT DEVICE_ID INTO dev_ID FROM
745: ( SELECT wbed.DEVICE_ID FROM
746: wms_bus_event_devices wbed,
747: wms_devices_b wd
748: WHERE
749: wd.device_id = wbed.device_id
750: AND WBED.organization_id = WD.organization_id

Line 1578: FROM wms_bus_event_devices

1574:
1575: BEGIN
1576: SELECT 1 INTO l_setup_row_cnt FROM DUAL WHERE exists
1577: (SELECT 1
1578: FROM wms_bus_event_devices
1579: WHERE business_event_id = p_bus_event);
1580:
1581: EXCEPTION
1582: WHEN NO_DATA_FOUND THEN

Line 2096: will not have any logic to resolve the API from the table wms_bus_event_devices

2092: /*
2093: This will be the overloaded device_request API which will be called
2094: from an OPM UI. The difference in this API is that, the caller will
2095: know the device_id to which the the request must be sent and the API
2096: will not have any logic to resolve the API from the table wms_bus_event_devices
2097:
2098: Inserting into WDR is kept transparent to the OPM team who will call this
2099: through a wrapper API in a group package
2100:

Line 2168: FROM wms_bus_event_devices

2164:
2165: BEGIN
2166: SELECT 1 INTO l_setup_row_cnt FROM DUAL WHERE exists
2167: (SELECT 1
2168: FROM wms_bus_event_devices
2169: WHERE business_event_id = p_bus_event);
2170:
2171: EXCEPTION
2172: WHEN NO_DATA_FOUND THEN

Line 2808: FROM wms_bus_event_devices

2804:
2805: BEGIN
2806: SELECT 1 INTO l_setup_row_cnt FROM DUAL WHERE exists
2807: (SELECT 1
2808: FROM wms_bus_event_devices
2809: WHERE business_event_id = p_bus_event_id
2810: AND organization_id = p_org_id
2811: and business_event_id < 50);
2812: