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.HZ_LOCATION_SERVICES_PUB dependencies on WF_EVENT_T

Line 140: -- 2) Raise wf event to enerate xml document base on the rows retrieved.

136: -----------------------------------------------------------------------
137: -- It will do the following
138: -- 1) Accept parameters from conc program and retrieve rows from
139: -- HZ_LOCATIONS which meet the parameters passed in
140: -- 2) Raise wf event to enerate xml document base on the rows retrieved.
141: -- It may split up all rows into different batch due to the maximum batch
142: -- size defined for each adapter.
143: ------------------------------------------------------------------------
144: PROCEDURE address_validation (

Line 512: -- 2) Raise wf event to enerate xml document base on the rows retrieved.

508: -----------------------------------------------------------------------
509: -- It will do the following
510: -- 1) Accept parameters from conc program and retrieve rows from
511: -- HZ_LOCATIONS which meet the parameters passed in
512: -- 2) Raise wf event to enerate xml document base on the rows retrieved.
513: -- It may split up all rows into different batch due to the maximum batch
514: -- size defined for each adapter.
515: ------------------------------------------------------------------------
516: PROCEDURE address_validation_worker (

Line 620: -- As outdoc_rule raise wf event to parse xml, this function

616:
617: -----------------------------------------------------------------------
618: -- Called from function rule outdoc_rule
619: -----------------------------------------------------------------------
620: -- As outdoc_rule raise wf event to parse xml, this function
621: -- rule which is defined for a wf event will be called. The wf event
622: -- is called oracle.apps.ar.hz.locservice.parsexml
623: -- This function rule will do the following
624: -- 1) Get the parsed xml doc

Line 1961: p_event IN OUT NOCOPY wf_event_t )

1957: END get_adapter_link;
1958:
1959: FUNCTION indoc_rule (
1960: p_subscription_guid IN RAW,
1961: p_event IN OUT NOCOPY wf_event_t )
1962: RETURN VARCHAR2 IS
1963: l_event_data CLOB := NULL;
1964: l_ecx_map_code VARCHAR2(30);
1965: l_adapter_id NUMBER;

Line 2029: -- As address_validation raise wf event to generate xml, this function

2025:
2026: -----------------------------------------------------------------------
2027: -- Called from address_validation
2028: -----------------------------------------------------------------------
2029: -- As address_validation raise wf event to generate xml, this function
2030: -- rule which is defined for a wf event will be called. The wf event
2031: -- is called oracle.apps.ar.hz.locservice.generatexml
2032: -- This function rule will do the following
2033: -- 1) Get the generated xml doc

Line 2035: -- 3) Get returned validated xml doc, raise another wf event to parse

2031: -- is called oracle.apps.ar.hz.locservice.generatexml
2032: -- This function rule will do the following
2033: -- 1) Get the generated xml doc
2034: -- 2) Pass the xml doc to submit_addrval_doc
2035: -- 3) Get returned validated xml doc, raise another wf event to parse
2036: -- the validated addresses.
2037: ------------------------------------------------------------------------
2038: FUNCTION outdoc_rule (
2039: p_subscription_guid IN RAW,

Line 2040: p_event IN OUT NOCOPY wf_event_t )

2036: -- the validated addresses.
2037: ------------------------------------------------------------------------
2038: FUNCTION outdoc_rule (
2039: p_subscription_guid IN RAW,
2040: p_event IN OUT NOCOPY wf_event_t )
2041: RETURN VARCHAR2 IS
2042: l_event_data CLOB := NULL;
2043: l_event_nclob_data NCLOB := NULL;
2044: l_adapter_id NUMBER;