Restrict number of rows to be pulled from PeopleSoft's PS_LEDGER table while importing data in FDMEE

Question

Hi,
We need to know if FDMEE 11.1.2.3.520 product supports restricting number of rows to be pulled from PeopleSoft's PS_LEDGER table.
All the records fetched from PS_LEDGER is getting loaded into TDATASEG table.
Currently, it is trying to pull all the records based on the given "period", "version" and "year" combination. We are looking to restrict rows based on specific account/entity/program/subprogram combination.
If this is can be done, will it be an out-of-the-box functionality or does it require any customization/import scripts/api.
Admin guide does say we can use Jython to filter rows using import scripts. However, it seems to be limited to file not a table as a source.
I have attached a document with the screenshots so that the issue is better understood !
Thanks,
Hari

Answer 1

1)
When you set a column to hidden in a classic report using the method I described, it creates hidden form elements for that column.
<tt><input type="hidden" name="f01" value="" id="f01_0002"></tt>
You should inspect the source to figure out the name value.
Since this belongs to the wwv_flow form, we can therefore get this data with: wwv_flow.f01
Alternatively, you could have used the apex_item API to achieve the same result, which probably gives a bit better control.
http://docs.oracle.com/cd/E37097_01/doc/doc.42/e35127/apex_item.htm#CHDBFHGA
select apex_item.hidden(1, col) || col col
from table
Set that column to a standard report column so it doesn't escape the html.
You can also reference the data in these fields using PL/SQL using the apex_application API:
http://docs.oracle.com/cd/E37097_01/doc/doc.42/e35127/apex_app.htm#CHDGJBAB
2)
As above, setting the column to hidden creates hidden elements on the page. It is simply f01 because that is the only hidden field I would have on my page. With four reports on the page, you would need to be careful not to do the same on the other reports, as you would get inaccurate data. For each report, setting columns to hidden always starts with f01. In that, you would be best to use the apex_item API.
I actually initially ran into this issue when i had a tabular form on the same page as a report with hidden fields, which was causing conflicts in the page processes.
Hope it helps.