Using date in prompt you have got an option of using calendar with button current date. In this case I do not see sense using LOV for date. If I were an user I would not like to search for date in a huge list of all dates.
My suggestion is to use prompts for month and year and put in LOV labels: Current Month , Current Year
I assume that year column in DB is changing that is why we would need LOV with Year values from DB and label ‘Current Year’. There are always 12 months (unless 13th is used on some purpose) so we can used fixed LOV.
First create object for Years and edit LOV SQL, put something like this
select table_name.year from table_name
union
select 'Current Year' from dual
check ‘Do not generate SQL…’
now create object condition:
(
lpad(UNIVERSE.MONTH,2,'0') = @Prompt('Month Equal to:','A',{'01','02','03','04','05','06','07','08','09','10','11','12','Current Month'},Mono,Constrained,,{'Current Month'},User:0)
or
(
'Current Month' = @Prompt('Month Equal to:','A',{'01','02','03','04','05','06','07','08','09','10','11','12','Current Month'},Mono,Constrained,,{'Current Month'},User:0)
and
lpad(UNIVERSE.MONTH,2,'0')=to_char(sysdate,'mm')
)
)
and
(
to_char(Table.YEAR)= @Prompt('Year Equal to:','A','Class\Year_wCY',Mono,Constrained,,{'Current Year'},User:1)
or
(
'Current Year'= @Prompt('Year Equal to:','A','Class\Year_wCY',Mono,Constrained,,{'Current Year'},User:1)
and
Table.YEAR=to_number(to_char(sysdate,'yyyy'))
)
)
remember to hide Year object in universe, we do not want users to use it in query
When you parse there is error but in report is working fine 
Marfi
(BOB member since 2006-12-18)