Need to pass period start date as parameter to ProjectLOVVO in OTL module

Question

Hi All,
I have a requirement of passing period start date as a parameter to ProjectLOVVO.
It will check against the project's base view PA_ONLINE_PROJECTS_V and allow to
display only those projects in the list where the project completion date and
resource assignment end date is greater than the period start date.
This VO is in Oracle Time and Labour Module. Navigation is SelfService Time> Create Timecard Screen.
The screen is based on AK Developer.
I have tried to followed the steps as per the document hxcconfiguiwp.pdf during the development work.
Steps are mentioned below. It is still not working.
Please go through the steps and if you have worked in this module please provide your valuable
suggestion as soon as possible.
Steps:
1. Modified the customizable view PA_ONLINE_PROJECTS_V to
keep the assignment end date in the select query.
2. Created Custom VO- XXProjectLOVVO using JDeveloper same as ProjectLOVVO
It's SQL Query is -
SELECT project_number projectnumber,
project_name projectname,
project_details projectdetails,
project_id projectid,
start_date,
completion_date,
carrying_out_organization_id
FROM pa_online_projects_v
WHERE TRUNC(completion_date) >= TRUNC(FND_DATE.CANONICAL_TO_DATE(:1))
AND TRUNC(assignment_end_date) >= TRUNC(FND_DATE.CANONICAL_TO_DATE(:2))
3. Placed the class files (XXProjectLOVVO.xml and XXProjectLOVVOImpl.class) in Custom Directory in server.
In location- apps_st/comn/java/classes/custom/oracle/apps/xxhxc/selfservice/timecard/server
4. Attached the Custom VO to standard AM- TimecardAM in location-oracle.apps.hxc.selfservice.timecard.server.TimecardAM
and in LovAM location-oracle.apps.hxc.selfservice.configui.server.LovAM
5. In AK Developer module created LOV Attributes 'XX_HXC_CUI_PROJECT_CO_ORG_ID', 'XX_HXC_CUI_PROJECT_END_DATE',
'XX_HXC_CUI_PROJECT_ID','XX_HXC_CUI_PROJECT_NAME',
'XX_HXC_CUI_PROJECT_NUMBER', 'XX_HXC_CUI_PROJECT_START_DATE'
and created a LOV region 'XX_HXC_CUI_PROJECT_LOV attached to Database Object 'ICX_PROMPTS' in the Object
and in Region items added all the above attributes.
Added LovAM location in place of AM and LovCO lication in place of CO.
6. Migrated the LOV with the below code
begin
hxc_lov_migration.migrate_lov_region
(p_region_code => 'XX_HXC_CUI_PROJECT_LOV'
,p_region_app_short_name => 'HXC'
,p_force => 'Y'
commit;
end;
7. Copied hxczzhxclayt0019.ldt LDT file from server. Renamed it to xhxczzhxclayt0019.ldt
modified the Layout section for ProjectLOV
BEGIN HXC_LAYOUT_COMPONENTS "Custom Projects Timecard Layout - Project"
OWNER = "CUSTOM"
COMPONENT_VALUE = "PROJECT"
REGION_CODE = "HXC_CUI_TIMECARD"
REGION_CODE_APP_SHORT_NAME = "HXC"
ATTRIBUTE_CODE = "HXC_TIMECARD_PROJECT"
ATTRIBUTE_CODE_APP_SHORT_NAME = "HXC"
SEQUENCE = "210"
COMPONENT_DEFINITION = "LOV"
RENDER_TYPE = "WEB"
PARENT_COMPONENT =
"Projects Timecard Layout - Day Scope Building blocks for worker timecard matrix"
LAST_UPDATE_DATE = "2010/11/10"
BEGIN HXC_LAYOUT_COMP_QUALIFIERS "Custom Projects Timecard Layout - Project"
OWNER = "CUSTOM"
QUALIFIER_ATTRIBUTE_CATEGORY = "LOV"
QUALIFIER_ATTRIBUTE1 = "XXProjectLOVVO"
QUALIFIER_ATTRIBUTE2 = "N"
QUALIFIER_ATTRIBUTE3 = "XX_HXC_CUI_PROJECT_LOV"
QUALIFIER_ATTRIBUTE4 = "809"
QUALIFIER_ATTRIBUTE5 = "12"
QUALIFIER_ATTRIBUTE6 =
"XxHxcCuiProjectNumber|PROJECT-DISPLAY|CRITERIA|N|XxHxcCuiProjectId|PROJECT|RESULT|N|XxHxcCuiProjectNumber|PROJECT-DISPLAY|RESULT|N"
QUALIFIER_ATTRIBUTE8 = "ProjectNumber"
QUALIFIER_ATTRIBUTE9 = "ProjectId#NUMBER"
QUALIFIER_ATTRIBUTE10 =
"custom.oracle.apps.xxhxc.selfservice.timecard.server.XXProjectLOVVO"
QUALIFIER_ATTRIBUTE11 = "TIMECARD_BIND_START_DATE|TIMECARD_BIND_START_DATE"
QUALIFIER_ATTRIBUTE17 = "OraTableCellText"
QUALIFIER_ATTRIBUTE20 = "N"
QUALIFIER_ATTRIBUTE21 = "Y"
QUALIFIER_ATTRIBUTE22 = "L"
QUALIFIER_ATTRIBUTE25 = "FLEX"
QUALIFIER_ATTRIBUTE26 = "PROJECTS"
QUALIFIER_ATTRIBUTE27 = "Attribute1"
QUALIFIER_ATTRIBUTE28 = "PROJECT"
LAST_UPDATE_DATE = "2010/11/10"
END HXC_LAYOUT_COMP_QUALIFIERS
END HXC_LAYOUT_COMPONENTS
8. Used FNDLOAD command to upload the ldt
FNDLOAD apps/apps@instance 0 Y UPLOAD /ad01/app/o2cdev/apps/apps_st/appl/hxc/12.0.0/patch/115/import/hxclaytlayoutsld.lct ./xhxczzhxclayt0019.ldt
9. Bounch Apache
10. Checked in below database table to check weather layout records are getting update or not and found records existing:
In table hxc_layout_COMPONENTS where region_code = 'HXC_CUI_TIMECARD' and component_value = 'PROJECT' and SEQUENCE = 210
and COMPONENT_NAME = 'Custom Projects Timecard Layout - Project'
In table hxc_layout_comp_qualifiers where layout_component_id is as in layout component table.
11. Checked that the XXProjectLOV is attached in the TimecardAM and LovAM. It is visible there but while quering for the project list its picking up all the projects irrelavant of start date parameter value .
As if its picking up all the records from seeded LOv- ProjectLOV not custom LOV.
Regards,
K Bosu

Answer 1

Hi
this steps is wrong
4. Attached the Custom VO to standard AM- TimecardAM in location-oracle.apps.hxc.selfservice.timecard.server.TimecardAM
and in LovAM location-oracle.apps.hxc.selfservice.configui.server.LovAMU cant add extended VO direct to standard AM .
VO extension requires .jpx import ,that u have to do ,rest will be take care by this import itself and no need to modify standard AM .
Please check the steps for VO extension in http://oracle.anilpassi.com/extend-vo-in-oa-framwork-2.html
thanks
Pratap