The basic purpose of 'EXTRA WHERE CLAUSE' is to store a part of

"Where Clause" coming from last query executed when the integrator
is attached to and launched from PUI instead of WebADI Create
Document page Flow. The "Where Statement" is split into two parts -
one part is stored in "hr:where" parameter and the other one in
"hr:extra" parameter which is nothing but "Extra Where Clause".
These parameters are later merged to give complete "WHERE Clause".

However , the same "hr:extra" parameter or "Extra Where Clause" has

been modified to provide flexibility to the end user to add additional
where statement to the download query when spreadsheet is launched
from "WebADI Create Document Page Flow". This feature can only be
used with "Where" clause i.e. if user has created at least one where
condition. In case user wants to add flexible condition i.e. "EXTRA
WHERE CLAUSE" only and no fixed column restraint , he should use
"Create Standalone Query" integrator to create a dummy "where
statement" like 'where 1=1' in "SQL Where Clause" keeping all the
parameter related columns (Parameter Name , prompt and type)
empty . When integrator is launched from a form, this "extra where
clause" is ignored.

Patch 6756987 has been created to do the following:

1. No need to start extra where clause with a blank space. It would be

taken care of by the code itself.

2. This "EXTRA WHERE CLAUSE" would be a part of the download

query and won't be ignored anymore while downloading data onto
spreadsheet.

NOTE: This feature has to be manually activated by making

modification in BNE tables i.e. by setting Default Visible Flag to 'Y' in
BNE_PARAM_DEFNS_B for param_defn_code =
'HR_STANDARD_EXTRA' . By default , it would be set to 'N'.
ERRORED EXTRA WHERE CLAUSE

WORKING EXTRA WHERE CLAUSE

NOTE the BLANK SPACE before and