OTL Timecard -- Hours Type LOV issue

I am facing some problem with the timecard. Scenerio is there is one employee who is eligible for all premium type elements.
Now the employee data is updated.Now employee is eligible for restricted premium types.
Lets say there is a timecard from 26th july,2010 to 2nd aug,2010. Employee data is updated on 28th jul,2010.
Now in timecard for that employee i am able to see duplicate values in Hours type field.
eg. Lets say employee till 27th jul,2010 is able to view premium entries like
1. Overtime Weekend
2. Overtime Weekday
3. Day Shift allowance etc.
and from 28th jul,2010 as the employee data is changed he will only see the Day Shift allowance in timecard.
But employee while entering is able to see Day shift allowance twice along with Overtime Weekend and Overtime Weekday for time card 26th july,2010 to 2nd aug,2010.
What would be the solution for that?

I would say its the correct functionality. Even though, all the premium elements are getting displayed, they won't pass the validation on either on time entry or during transfer process. What's the otl patching level?
If you are still concerned, raise an SR.
--Shiv                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

Similar Messages

  • OTL Timecard Restrict Expendituretype LOV

    Hi,
    I'm really stuck with following issue.
    My client has the requirement to restrict the Expendituretype LOV based on selected project.
    I know this is possible and read all documentation about it but I can't get it working.
    It should be possible because the TaskLOV is also restricted based on selected project.
    Can anyone please help ? Search on
    This is what I did:
    1. I extended ExpTypeElementLOVVO in such a way that project_id is included in the query.
    2. I created a custom layout file as follows. Relevant part is below.
    I made changes to ATTRIBUTE6,14 and 15. As I don't entirely grasp the syntax of these attributes I probably made some mistakes there. By the way, I did bounce Apache and OC4J.
    BEGIN HXC_LAYOUT_COMPONENTS "Projects Alternate Timecard Layout - Expenditure Type"
    OWNER = "ORACLE"
    COMPONENT_VALUE = "EXPENDITURETYPE"
    REGION_CODE = "HXC_CUI_TIMECARD"
    REGION_CODE_APP_SHORT_NAME = "HXC"
    ATTRIBUTE_CODE = "HXC_TIMECARD_EXPTYPE"
    ATTRIBUTE_CODE_APP_SHORT_NAME = "HXC"
    NAME_VALUE_STRING = "EXPENDITURE_ELEMENTS"
    SEQUENCE = "220"
    COMPONENT_DEFINITION = "LOV"
    RENDER_TYPE = "WEB"
    PARENT_COMPONENT = "Projects Alternate Timecard Layout - Day Scope Building blocks for worker timecard matrix"
    LAST_UPDATE_DATE = "2004/05/24"
    BEGIN HXC_LAYOUT_COMP_QUALIFIERS "Projects Alternate Timecard Layout - Expenditure Type"
    OWNER = "ORACLE"
    QUALIFIER_ATTRIBUTE_CATEGORY = "LOV"
    QUALIFIER_ATTRIBUTE1 = "ExpTypeElementLOVVO"
    QUALIFIER_ATTRIBUTE2 = "N"
    QUALIFIER_ATTRIBUTE3 = "HXC_CUI_LOV_EXPTYPE_ELEMENT"
    QUALIFIER_ATTRIBUTE4 = "809"
    QUALIFIER_ATTRIBUTE5 = "5"
    QUALIFIER_ATTRIBUTE6 = "HxcCuiAliasValue|ALIAS-DISPLAY|CRITERIA|N|HxcCuiExpProjectId|PROJECT|PASSIVE_CRITERIA|Y|HxcCuiAliasId|DUMMY|PASSIVE_CRITERIA|N|HxcCuiAliasId|ALIAS|RESULT|N|HxcCuiAliasValue|ALIAS-DISPLAY|RESULT|N"
    QUALIFIER_ATTRIBUTE8 = "AliasValueName"
    QUALIFIER_ATTRIBUTE9 = "AliasValueId#NUMBER"
    QUALIFIER_ATTRIBUTE10 = "oracle.apps.hxc.selfservice.timecard.server.ExpTypeElementLOVVO"
    QUALIFIER_ATTRIBUTE14 = "HxcCuiExpProjectId|PROJECT|Y"
    QUALIFIER_ATTRIBUTE15 = "project_id = ::HxcCuiExpProjectId"
    QUALIFIER_ATTRIBUTE17 = "OraTableCellText"
    QUALIFIER_ATTRIBUTE20 = "N"
    QUALIFIER_ATTRIBUTE21 = "Y"
    QUALIFIER_ATTRIBUTE22 = "L"
    QUALIFIER_ATTRIBUTE24 = "ELEMENTS_EXPENDITURE_SLF"
    QUALIFIER_ATTRIBUTE25 = "FLEX"
    QUALIFIER_ATTRIBUTE26 = "OTL_ALIAS_1"
    QUALIFIER_ATTRIBUTE27 = "Attribute1"
    QUALIFIER_ATTRIBUTE28 = "ALIAS"
    LAST_UPDATE_DATE = "2004/05/24"
    END HXC_LAYOUT_COMP_QUALIFIERS
    END HXC_LAYOUT_COMPONENTS
    Please help me out.
    Jan
    Edited by: Jan Blok on Apr 29, 2011 1:56 PM
    Edited by: Jan Blok on Apr 29, 2011 1:58 PM

    I would say its the correct functionality. Even though, all the premium elements are getting displayed, they won't pass the validation on either on time entry or during transfer process. What's the otl patching level?
    If you are still concerned, raise an SR.
    --Shiv                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • OTL Timecard issue

    Hi,
    We have to show 2 timecards to users. For Org A they want to show Projects Timecard and for Org B they want to show a timecard without any Project / Task / Expenditure (Only monday to friday days). So I created 2 preferences with 2 different layouts.
    Only issue is for the Org B we chosen 'Oracle Internal Layout - Timecard Entry Page' as this layout has only 1 field as Hour Type.
    Question is how is populate values in it (LOV) and can this field be hidden with some default value.
    I am new to OTL so Thanks in advance.
    Jay

    The list of values for Hours types comes from the "Alternate Name" definition. Define an Alternate Name and include all the elements that you want to display and link this Alternate Name in the preferences. Make sure that element links are properly established, although the element is available in alternate name but if the element link does not exist, then it wont appear in the Hours Type.
    Regarding hiding of Hours type, I don't think thats gonna work. OTL is a combination of building blocks (i.e. Hours information) and attributes (i.e. Hours type/project/task etc..), so you have to have both information in the timecard.

  • OTL Timecard LOV Sort Order

    Hello,
    We have an LOV field on our OTL timecard called Rate Up. It is a custom timecard created by someone who is long gone. We would like it sorted in a particular order. We identified a database view that is likely the source of the data, but adding an ORDER BY in the view did not work.
    This is probably really simple when one knows how. How can we put a sort order on this LOV?
    Thank you,

    Both of these suggestions are really close. I thank Avinash and Giuseppe for their advice.
    I found a validation set named XXEP_OTL_RATEUP_CODE_TK, but it is already sorted. We use this validation set on the Oracle Forms style OTL Timekeeper screens, but not on the web self service screens, where our sort problem exists.
    I enabled diagnostics without any useful information, but a trace gave me the following sql statement which uses hxc_cui_custom4_v. I added an order by into the view, cleared cache, logged off and on, tried a different PC with a different user, but no luck sorting. So where is this select specified, so I can add an order by?
    Thank you,
    PARSING IN CURSOR #192 len=1188 dep=0 uid=435 oct=3 lid=435 tim=3702128553905 hv=3217417118 ad='b8abd5f8'
    select distinct display_value displayvalue, value
    from hxc_cui_custom4_v a,
    (select trunc(FND_DATE.CANONICAL_TO_DATE(:1)) "TC_DATE" from dual) b
    where person_id = :2
    and b.TC_DATE between emp_per_start_date and emp_per_end_date
    and b.TC_DATE between emp_asg_start_date and emp_asg_end_date
    and b.TC_DATE between emp_pgr_start_date and emp_pgr_end_date
    and b.TC_DATE between emp_sps_start_date and emp_sps_end_date
    and b.TC_DATE between emp_gd_start_date and emp_gd_end_date
    and b.TC_DATE between emp_pgd_start_date and emp_pgd_end_date
    and b.TC_DATE between emp_pgs_start_date and emp_pgs_end_date
    and b.TC_DATE between emp_pspp_start_date and emp_pspp_end_date
    and b.TC_DATE between all_pgr_start_date and all_pgr_end_date
    and b.TC_DATE between all_sps_start_date and all_sps_end_date
    and b.TC_DATE between all_gd_start_date and all_gd_end_date
    and b.TC_DATE between all_pgd_start_date and all_pgd_end_date
    and b.TC_DATE between un_pur_start_date and un_pur_end_date
    and b.TC_DATE between un_purv_start_date and un_purv_end_date
    and b.TC_DATE between un_puci_start_date and un_puci_end_date
    and b.TC_DATE between un_puci2_start_date and un_puci2_end_date
    END OF STMT
    EXEC #192:c=0,e=521,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=1,tim=3702128553897
    FETCH #192:c=1430000,e=1552659,p=0,cr=25048,cu=0,mis=0,r=10,dep=0,og=1,tim=3702130106837
    FETCH #192:c=0,e=52,p=0,cr=0,cu=0,mis=0,r=10,dep=0,og=1,tim=3702130109204
    FETCH #192:c=0,e=21,p=0,cr=0,cu=0,mis=0,r=10,dep=0,og=1,tim=3702130109625
    FETCH #192:c=0,e=14,p=0,cr=0,cu=0,mis=0,r=10,dep=0,og=1,tim=3702130109853
    FETCH #192:c=0,e=42,p=0,cr=0,cu=0,mis=0,r=10,dep=0,og=1,tim=3702130111605
    FETCH #192:c=0,e=22,p=0,cr=0,cu=0,mis=0,r=10,dep=0,og=1,tim=3702130112010
    FETCH #192:c=0,e=19,p=0,cr=0,cu=0,mis=0,r=10,dep=0,og=1,tim=3702130112207
    FETCH #192:c=0,e=194,p=0,cr=0,cu=0,mis=0,r=7,dep=0,og=1,tim=3702130112570

  • Creating fields as LOV (using alternate names) on OTL timecards

    Hi,
    I would really appreciate if someone can help me understand the process of being able to add fields on OTL timecard as LOV fields using alternate names. These are COST segments which I need to add on OTL timecard. The part which is most confusing to me is modifying the .ldt to get these fields working.
    Appreciate if anyone can point me to related documents.
    Thanks,
    Maddy
    --

    Hi Maddy
    Ramsys has pointed you towards a very useful document, the timecard configuration guide. But, the guide is very complicated and it shows you what to do, but doesn't really explain 'why' you have to do it.
    I run training courses on OTL, and this is a complex area to understand. It is possible to display almost anything on the timecard if you put your mind to it! Your example fo the cost centre is quite straightforward. Youi can create a value set to display the cost codes you want. A suitable one might already exist. You then need to have a view object (VO) to use this on the timecard. OTL provides 10 dummy VOs which you can use. The guide explains how to do this. The VO links your value set to the timecard. This step accounts for displaying the data on the timecard.
    You also need to have somewhere to store the values selected by the user. To do this you need to define a contect in the OTL_INFORMATION_TYPES DFF to store the data. You will also need to have a mapping component to link the data on the screen to the OTL_INFORMATION_TYPES context. Usually, you can use an existing mapping component.
    Good luck!
    Regards
    Tim

  • OTL -Time Sheet Hour Type field detail required.

    Hi all,
    I'm working on a Report which gets time sheet data for an employee. My time sheet structure has project, Task,Type and Hour type. I have got all the column data as required for my report but i'm not able to find out where the hours type info (as mentioned above) is stored.
    I do know that the LOV for the Hour Type column is from hxc_alias_values table. But i want to know the table /column where hour type info is stored when a person enters the time sheet.i.e., For an employee entered time sheet - project-task-type-hour type and number of hrs against it.
    We tried a lot of options but were unable to find out. Any help on this will be very helpful.
    Thanks,
    Suresh

    The value will be available in HXC_TIME_ATTRIBUTES with Attribute_Category = ELEMENT - <Element Type Id>. This cane be retrieved by joining HXC_TIME_BUILDING_BLOCKS > HXC_TIME_ATTRIBUTE_USAGES > HXC_TIME_ATTRIBUTE_USAGES.

  • OTL - Hours Type Hard Coding

    Hello,
    While creating a Time card in OTL, we want to restrict a particular operating unit of ours to have only "Regular" Hours Type. In general, the Alias for Hours Type has both the "Regular" and "Overtime" . This being through the OAF am not sure, how this could be achieved.
    TIA..

    Hi,
    You can go through OA Framework Developer's Guide,Chapter 9 - Extending OA Framework Applications to get a start.
    Thanks.

  • OTL timekeeper entry - retrieve Hours type

    Hi guys,
    In the Timekeeper(OTL) entry form (where you enter time for multiple workers) there is a 'Hours Type' field .
    I need to retrieve the 'hours type' field value(As displayed in timekeeper entry screen) for a particular person(say person_id=2222) and for a particular period(june 9,2008-june 15,2008)..
    can anyone tell me the query or any pointers will be highly appreciated
    Thanks

    The Hours Type field needs to be configured as an Alternate Name Definition. This will associate a list of values for hours types to the corresponding elements.
    Then you have to associate the hours type alternate name definition as a timekeeper layout item in the Preferences window.

  • Hours Type in OTL

    Hi,
    I am trying to fill in a self service time card for a employee. I see two fields on the time card as Hours Type and Cost Center. Problem is the list of values for both these are empty so i cant choose any value for them. If i submit without putting hours type then i get a error on submission. Please can someone help me as i am new to OTL
    Thanks

    Have you tried looking at the seeded formulas as a starting point?
    Oracle Time & Labor
    Implementation and User Guide
    Release 11i
    Part No. B15865-01
    January 2005
    Write Formulas for Time Entry and Approval Rules; Page 6-10
    Seeded Formula for Period Maximum: HXC_PERIOD_MAXIMUM
    Approval Assignment Status Test: HXC_APPROVAL_ASG_STATUS
    Approval Maximum Test: HXC_APPROVAL_MAXIMUM
    Assignment Standard Hours vs Time Category: HXC_ASSG_STD_HRS_Comparison
    PTO Accrual Balance vs Absence: HXC_PTO_ACCRUAL_Comparison
    Period Hours vs Time Category: HXC_TIME_CATEGORY_Comparison
    Override Approver WF Person Mechanism: HXC_OVERRIDE_APPROVER_WF_PERSON
    You can copy and configure all these formulas, or write your own formulas, according
    to the following rules.
    Formula Inputs and Outputs
    Formulas executed from time entry rules (for validation or approval) must be
    of the following form:
    INPUTS ARE resource_id (number)
    submission_date (text)
    <other inputs>
    /* Formula Processing */
    RETURN <formula result>, <message 1..5>
    Regards,
    Greg

  • OTL Hours Type not exploding..

    Hi,
    Can anyone suggest why one of my hours type not exploding. I have two different elements setup in two different earning policies.
    Element One is defined in the first earning policy's explosion rule which when tested exploded fine. Element two is also defined in Policy One earning group but it isnt exploding within it!!
    Element Two is then defined in the second earning policy explosion rule but it isnt exploding at all. This earning policy and elements are pretty much setup identical to each other so I'm confused as to why the first one is working and not the second one.
    Any suggestion?
    Regards
    TL

    It drills down to how you've setup the earnings policies.
    There are some examples in the Note below -
    Oracle Time and Labor (OTL) OTLR California Overtime Policy Setup and Examples [ID 1451080.1]
    Try to compare yours with the above to see if all is fine.
    Cheers,
    Vignesh

  • Where clause for TaskLOVVO on OTL Timecard

    Hi,
    Following is the customization on our OTL timecard layout(Projects and Payroll Layout):
    ->Extended TaskLOVVO and based on a value selected in TaskLOV, i am defaulting Hours type.
    The dynamic where clause for the TaskLOVO is taken care of by the below QUALIFIER_ATTRIBUTES(Same as seeded layout)
    QUALIFIER_ATTRIBUTE14 = "HxcCuiTaskProjectId|PROJECT|Y#HxcCuiTaskProjectNumber|PROJECT-DISPLAY|Y"
    QUALIFIER_ATTRIBUTE15 = "project_id = ::HxcCuiTaskProjectId#upper(project_number) = upper(::HxcCuiTaskProjectNumber)"
    But in some scenarios the dynamic layout is not getting appended to TaskLOVO and the query behind the TaskLOV is pulling too many records.
    This issue is happening on Fridays when around 15000 employees submit the timecards, as Friday is our deadline for Timecard submission.
    I have tried different scenarios to replicate this issue in test intances but I am not able to replicate it.
    Please suggest what could be the issue and why is the whereclause is not getting appended in some scenarios.
    Thank you

    Hi,
    Thank you for your reply.
    The whoole LDT file is more than 30000 characters, which is not allowed in the post, so I have included only the lines which have customization.
    FYI: This is a Projects and Payroll layout.
    Following is my LDT file:
    # $Header: hxczzhxclayt0093.ldt 120.0 2008/02/08 09:26:10 bbayragi noship $
    # dbdrv: exec fnd bin FNDLOAD bin &phase=dat+10 checkfile:~PROD:~PATH:~FILE &ui_apps 0 Y UPLOAD @HXC:patch/115/import/hxclaytlayoutsld.lct @~PROD:~PATH/~FILE
    LANGUAGE = "US"
    LDRCONFIG = "hxclaytlayoutsld.lct 120.0"
    #Source Database seed121
    #RELEASE_NAME 12.1.0
    # -- Begin Entity Definitions --
    BEGIN HXC_LAYOUT_COMPONENTS
    "Projects Details Alternate Timecard Layout - Project"
    OWNER = "ORACLE12.1.0"
    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 = "200"
    COMPONENT_DEFINITION = "LOV"
    RENDER_TYPE = "WEB"
    PARENT_COMPONENT = "Projects Details Alternate Timecard Layout - Day Scope Building blocks for worker timecard matrix"
    LAST_UPDATE_DATE = "2004/05/24"
    BEGIN HXC_LAYOUT_COMP_QUALIFIERS
    "Projects Details Alternate Timecard Layout - Project"
    OWNER = "ORACLE12.1.0"
    QUALIFIER_ATTRIBUTE_CATEGORY = "LOV"
    QUALIFIER_ATTRIBUTE1 = "ProjectLOVVO"
    QUALIFIER_ATTRIBUTE2 = "N"
    QUALIFIER_ATTRIBUTE3 = "HXC_CUI_PROJECT_DETAILS_LOV"
    QUALIFIER_ATTRIBUTE4 = "809"
    QUALIFIER_ATTRIBUTE5 = "25"
    QUALIFIER_ATTRIBUTE6 = "HxcCuiProjectDetails|PROJECT-DISPLAY|CRITERIA|N|HxcCuiProjectId|PROJECT|RESULT|N|HxcCuiProjectDetails|PROJECT-DISPLAY|RESULT|N|HxcCuiProjectCoOrgId|LOCATION1|RESULT|N|HxcCuiProjectName|CNAME|RESULT|N"
    QUALIFIER_ATTRIBUTE8 = "ProjectDetails"
    QUALIFIER_ATTRIBUTE9 = "ProjectId#NUMBER"
    QUALIFIER_ATTRIBUTE10 = "oracle.apps.hxc.selfservice.timecard.server.ProjectLOVVO"
    QUALIFIER_ATTRIBUTE11 = "RESOURCE_IDENTIFIER_ID"
    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 = "2004/05/24"
    END HXC_LAYOUT_COMP_QUALIFIERS
    END HXC_LAYOUT_COMPONENTS
    BEGIN HXC_LAYOUT_COMPONENTS
    "Projects Details Alternate Timecard Layout - Task"
    OWNER = "ORACLE12.1.0"
    COMPONENT_VALUE = "TASK"
    REGION_CODE = "HXC_CUI_TIMECARD"
    REGION_CODE_APP_SHORT_NAME = "HXC"
    ATTRIBUTE_CODE = "HXC_TIMECARD_TASK"
    ATTRIBUTE_CODE_APP_SHORT_NAME = "HXC"
    SEQUENCE = "210"
    COMPONENT_DEFINITION = "LOV"
    RENDER_TYPE = "WEB"
    PARENT_COMPONENT = "Projects Details Alternate Timecard Layout - Day Scope Building blocks for worker timecard matrix"
    LAST_UPDATE_DATE = "2004/05/24"
    BEGIN HXC_LAYOUT_COMP_PROMPTS "HxcCuiTaskProjectId" "AK_PROMPT"
    OWNER = "ORACLE12.1.0"
    REGION_CODE = "HXC_CUI_TIMECARD"
    REGION_APP_SHORT_NAME = "HXC"
    ATTRIBUTE_CODE = "HXC_TIMECARD_PROJECT"
    ATTRIBUTE_APP_SHORT_NAME = "HXC"
    LAST_UPDATE_DATE = "2004/05/24"
    END HXC_LAYOUT_COMP_PROMPTS
    BEGIN HXC_LAYOUT_COMP_QUALIFIERS
    "Projects Details Alternate Timecard Layout - Task"
    OWNER = "ORACLE12.1.0"
    QUALIFIER_ATTRIBUTE_CATEGORY = "LOV"
    QUALIFIER_ATTRIBUTE1 = "TaskLOVVO"
    QUALIFIER_ATTRIBUTE2 = "N"
    QUALIFIER_ATTRIBUTE3 = "HXC_CUI_TASK_DETAILS_LOV"
    QUALIFIER_ATTRIBUTE4 = "809"
    QUALIFIER_ATTRIBUTE5 = "10"
    QUALIFIER_ATTRIBUTE6 = "HxcCuiTaskDetails|TASK-DISPLAY|CRITERIA|N|HxcCuiTaskProjectId|PROJECT|PASSIVE_CRITERIA|Y|HxcCuiTaskId|TASK|RESULT|N|HxcCuiTaskDetails|TASK-DISPLAY|RESULT|N|HxcCuiTaskBillableFlag|EXPTYPE|RESULT|N"
    QUALIFIER_ATTRIBUTE8 = "TaskDetails"
    QUALIFIER_ATTRIBUTE9 = "TaskId#NUMBER"
    QUALIFIER_ATTRIBUTE10 = "oracle.apps.hxc.selfservice.timecard.server.TaskLOVVO"
    QUALIFIER_ATTRIBUTE11 = "RESOURCE_IDENTIFIER_ID|TIMECARD_BIND_END_DATE"
    QUALIFIER_ATTRIBUTE14 = "HxcCuiTaskProjectId|PROJECT|Y#HxcCuiTaskProjectNumber|PROJECT-DISPLAY|Y"
    QUALIFIER_ATTRIBUTE15 = "project_id = ::HxcCuiTaskProjectId#upper(project_number) = upper(::HxcCuiTaskProjectNumber)"
    QUALIFIER_ATTRIBUTE17 = "OraTableCellText"
    QUALIFIER_ATTRIBUTE20 = "N"
    QUALIFIER_ATTRIBUTE21 = "Y"
    QUALIFIER_ATTRIBUTE22 = "L"
    QUALIFIER_ATTRIBUTE25 = "FLEX"
    QUALIFIER_ATTRIBUTE26 = "PROJECTS"
    QUALIFIER_ATTRIBUTE27 = "Attribute2"
    QUALIFIER_ATTRIBUTE28 = "TASK"
    LAST_UPDATE_DATE = "2004/05/24"
    END HXC_LAYOUT_COMP_QUALIFIERS
    END HXC_LAYOUT_COMPONENTS
    BEGIN HXC_LAYOUT_COMPONENTS
    "Projects Details Alternate Timecard Layout - Location"
    OWNER = "CUSTOM"
    COMPONENT_VALUE = "LOCATION"
    REGION_CODE = "HXC_CUI_TIMECARD"
    REGION_CODE_APP_SHORT_NAME = "HXC"
    ATTRIBUTE_CODE = "HXC_CUI_LOCATION_LABEL"
    ATTRIBUTE_CODE_APP_SHORT_NAME = "HXC"
    SEQUENCE = "215"
    COMPONENT_DEFINITION = "CHOICE_LIST"
    RENDER_TYPE = "WEB"
    PARENT_COMPONENT = "Projects Details Alternate Timecard Layout - Day Scope Building blocks for worker timecard matrix"
    LAST_UPDATE_DATE = "2004/05/24"
    BEGIN HXC_LAYOUT_COMP_QUALIFIERS "Projects Details Alternate Timecard Layout - Location"
    OWNER = "CUSTOM"
    QUALIFIER_ATTRIBUTE_CATEGORY = "CHOICE_LIST"
    QUALIFIER_ATTRIBUTE1 = "Custom2VO"
    QUALIFIER_ATTRIBUTE4 = "N"
    # QUALIFIER_ATTRIBUTE5 = "10"
    # QUALIFIER_ATTRIBUTE8 = "DisplayValue"
    # QUALIFIER_ATTRIBUTE9 = "Value#NUMBER"
    QUALIFIER_ATTRIBUTE10 = "oracle.apps.hxc.selfservice.timecard.server.Custom2VO"
    QUALIFIER_ATTRIBUTE17 = "OraTableCellText"
    QUALIFIER_ATTRIBUTE20 = "N"
    QUALIFIER_ATTRIBUTE21 = "Y"
    QUALIFIER_ATTRIBUTE22 = "L"
    QUALIFIER_ATTRIBUTE25 = "FLEX"
    QUALIFIER_ATTRIBUTE26 = "Dummy Element Context"
    QUALIFIER_ATTRIBUTE27 = "Attribute15"
    QUALIFIER_ATTRIBUTE28 = "LOCATION1"
    LAST_UPDATE_DATE = "2004/05/24"
    END HXC_LAYOUT_COMP_QUALIFIERS
    END HXC_LAYOUT_COMPONENTS
    BEGIN HXC_LAYOUT_COMPONENTS "Projects Details Alternate Timecard Layout - Expenditure Type"
    OWNER = "ORACLE"
    COMPONENT_VALUE = "EXPENDITURETYPE"
    REGION_CODE = "HXC_CUI_TIMECARD"
    REGION_CODE_APP_SHORT_NAME = "HXC"
    ATTRIBUTE_CODE = "HXC_TIMECARD_EXPTYPE"
    ATTRIBUTE_CODE_APP_SHORT_NAME = "HXC"
    SEQUENCE = "225"
    COMPONENT_DEFINITION = "PACKAGE_CHOICE_LIST"
    RENDER_TYPE = "WEB"
    PARENT_COMPONENT = "Projects Details Alternate Timecard Layout - Day Scope Building blocks for worker timecard matrix"
    LAST_UPDATE_DATE = "2004/05/23"
    BEGIN HXC_LAYOUT_COMP_QUALIFIERS "Projects Details Alternate Timecard Layout - Expenditure Type"
    OWNER = "ORACLE"
    QUALIFIER_ATTRIBUTE_CATEGORY = "PACKAGE_CHOICE_LIST"
    QUALIFIER_ATTRIBUTE1 = "BOLINF.XXHXC_TYPE_CHOICE.EXPTTYPE"
    QUALIFIER_ATTRIBUTE2 = "@RESOURCE_IDENTIFIER_ID|@TIMECARD_BIND_END_DATE"
    QUALIFIER_ATTRIBUTE4 = "N"
    QUALIFIER_ATTRIBUTE8 = "aliasname"
    QUALIFIER_ATTRIBUTE9 = "value#NUMBER"
    QUALIFIER_ATTRIBUTE20 = "N"
    QUALIFIER_ATTRIBUTE21 = "Y"
    QUALIFIER_ATTRIBUTE22 = "R"
    QUALIFIER_ATTRIBUTE24 = "ET_EXPENDITURE_TYPE"
    QUALIFIER_ATTRIBUTE25 = "FLEX"
    QUALIFIER_ATTRIBUTE26 = "OTL_ALIAS_1"
    QUALIFIER_ATTRIBUTE27 = "Attribute1"
    QUALIFIER_ATTRIBUTE28 = "EXPTYPE"
    LAST_UPDATE_DATE = "2004/05/24"
    END HXC_LAYOUT_COMP_QUALIFIERS
    END HXC_LAYOUT_COMPONENTS
    BEGIN HXC_LAYOUT_COMPONENTS "Projects Details Alternate Timecard Layout - Customer name"
    OWNER = "ORACLE"
    REGION_CODE = "HXC_CUI_TIMECARD"
    REGION_CODE_APP_SHORT_NAME = "HXC"
    ATTRIBUTE_CODE = "XXTW_HXC_TIMECARD_CUST_NAME"
    ATTRIBUTE_CODE_APP_SHORT_NAME = "HXC"
    SEQUENCE = "205"
    COMPONENT_DEFINITION = "TEXT_FIELD"
    RENDER_TYPE = "WEB"
    PARENT_COMPONENT = "Projects Details Alternate Timecard Layout - Day Scope Building blocks for worker timecard matrix"
    LAST_UPDATE_DATE = "2004/05/24"
    BEGIN HXC_LAYOUT_COMP_QUALIFIERS "Projects Details Alternate Timecard Layout - Customer name"
    OWNER = "ORACLE"
    QUALIFIER_ATTRIBUTE_CATEGORY = "TEXT_FIELD"
    QUALIFIER_ATTRIBUTE1 = "N"
    QUALIFIER_ATTRIBUTE2 = "Y"
    QUALIFIER_ATTRIBUTE3 = "20"
    QUALIFIER_ATTRIBUTE4 = "1"
    QUALIFIER_ATTRIBUTE5 = "20"
    QUALIFIER_ATTRIBUTE7 = "OraTableCellText"
    QUALIFIER_ATTRIBUTE17 = "NONE"
    QUALIFIER_ATTRIBUTE20 = "Y"
    QUALIFIER_ATTRIBUTE21 = "Y"
    QUALIFIER_ATTRIBUTE22 = "L"
    QUALIFIER_ATTRIBUTE25 = "FLEX"
    QUALIFIER_ATTRIBUTE26 = "PROJECTS"
    QUALIFIER_ATTRIBUTE27 = "Attribute9"
    QUALIFIER_ATTRIBUTE28 = "CNAME"
    QUALIFIER_ATTRIBUTE30 = "Y"
    LAST_UPDATE_DATE = "2004/05/24"
    END HXC_LAYOUT_COMP_QUALIFIERS
    END HXC_LAYOUT_COMPONENTS
    And the query in TASKLOVVO:
    SELECT task.task_number tasknumber, task.task_name, task_details taskdetails, task.task_id taskid, bolinf.GETALIASID(proj.project_type,proj.project_id,task.task_id, :1, :2) billable_flag, task.project_id, task.start_date, task.completion_date, task.chargeable_flag, proj.project_number , proj.project_details from pa_online_tasks_v task ,pa_online_projects_v proj where proj.project_id = task.project_id
    In the above query GETALIASID is a custom function that returns a value.
    Thank you
    Edited by: Santo on Mar 18, 2013 2:12 PM

  • OTL Timecard Customization !!!

    Hi All,
    I'm trying Customization to OTL Timecard i.e add two extra columns Project Name and Task Name.
    I got this ldt file (hxczzhxclayt0019.ldt) to customize. I did my changes to add these fields. I was successful in seeing these columns.
    But the problem is I don’t know if the LOV is actually working or not. When I click on the Torch or LOV icon, it does open and I’m able to select the project name. But when I’m done with selection of the project name it does not reflect on the Project Name column of the Table Matrix, it instead shows the Project Id in the Project Column of the Table Matrix. And how will I make the Project Id and Project Name dependent.
    Note:1) ProjectLOVVO was already there with project name. so i dint customize it.
    2) And i have no idea how QUALIFIER_ATTRIBUTE6 field works.
    3) Could any body please explain me or direct me where i can get the definitions of the fields QUALIFIER_ATTRIBUTE (1 to 30)
    Here is the code changes I have made in the ldt file.
    ##########Text Field for Project Name############
    BEGIN HXC_LAYOUT_COMPONENTS "Projects Timecard Layout - Project Name"
    OWNER = "ORACLE"
    COMPONENT_VALUE = "PN"
    REGION_CODE = "HXC_CUI_TIMECARD"
    REGION_CODE_APP_SHORT_NAME = "HXC"
    ATTRIBUTE_CODE = "HXC_CUI_PROJECT_NAME"
    ATTRIBUTE_CODE_APP_SHORT_NAME = "HXC"
    SEQUENCE = "215"
    COMPONENT_DEFINITION = "LOV"
    RENDER_TYPE = "WEB"
    PARENT_COMPONENT =
    "Projects Timecard Layout - Day Scope Building blocks for worker timecard matrix"
    LAST_UPDATE_DATE = "2009/05/20"
    BEGIN HXC_LAYOUT_COMP_QUALIFIERS "Projects Timecard Layout - Project Name"
    OWNER = "ORACLE"
    QUALIFIER_ATTRIBUTE_CATEGORY = "LOV"
    QUALIFIER_ATTRIBUTE1 = "ProjectLOVVO"
    QUALIFIER_ATTRIBUTE2 = "N"
    QUALIFIER_ATTRIBUTE3 = "HXC_CUI_PROJECT_LOV"
    QUALIFIER_ATTRIBUTE4 = "809"
    QUALIFIER_ATTRIBUTE5 = "12"
    QUALIFIER_ATTRIBUTE6 =
    "HxcCuiProjectNumber|PROJECT-DISPLAY|CRITERIA|N|HxcCuiProjectId|PROJECT|RESULT|N|HxcCuiProjectNumber|PROJECT-DISPLAY|RESULT|N|HxcCuiProjectName|PN|RESULT|N"
    QUALIFIER_ATTRIBUTE8 = "ProjectName"
    QUALIFIER_ATTRIBUTE9 = "ProjectId#NUMBER"
    QUALIFIER_ATTRIBUTE10 =
    "oracle.apps.hxc.selfservice.timecard.server.ProjectLOVVO"
    QUALIFIER_ATTRIBUTE17 = "OraTableCellText"
    QUALIFIER_ATTRIBUTE20 = "N"
    QUALIFIER_ATTRIBUTE21 = "Y"
    QUALIFIER_ATTRIBUTE22 = "L"
    QUALIFIER_ATTRIBUTE25 = "FLEX"
    QUALIFIER_ATTRIBUTE26 = "PROJECTS"
    QUALIFIER_ATTRIBUTE27 = "Attribute8"
    QUALIFIER_ATTRIBUTE28 = "PN"
    LAST_UPDATE_DATE = "2009/05/20"
    END HXC_LAYOUT_COMP_QUALIFIERS
    END HXC_LAYOUT_COMPONENTS
    Please suggest me a solutions, this is an urgent issue i need to resolve !!!
    Thanks and in advance.

    Client Does not want it to be a earning element and do not want to catch Punch in and Punch out times for Unpaid breaks.
    User should enter only minutes and that should be deducted from Regular Hours before explosion.

  • In R12.2.3 Task type LOV is blank

    Hi,
    We are implementing R12.2.3 Service modules for our client.
    But after defining the task types using the Service Responsibility, the same are available under Task manager window.
    But none of the task type neither the seeded one are available under the task type LOV in create service request form.
    Nor we can see any task type available under mapping objects window which opens after clicking on Map Types button in Task Type definition form.
    Is there anything we missing any profile option or some key setup.
    Please let me know if anyone has seen this issue before.
    Best Regards,
    Shyam

    Hi Shyam,
    Please open the Task Types form ( JTFTKTTY.fmb) and click on the 'Map Types' button.
    Query for Source Object = 'Service Request'.
    a) Do you see Task Types already mapped?
    b) If you add a row: there are no Task Types in the LOV at all? Do you see any errors at the bottom of the form (i.e. FRM-41826)?
    Thanks,
    M.

  • Package Choicelist OTL timecard

    Has anyone implemented package choicelist in OTL timecard?...I wanted to ask you if you encountered a problem wherein you dont see any values in the list when you open a timecard after implementing package choiclist:
    Here is what my layout file looks like :
    BEGIN HXC_LAYOUT_COMP_QUALIFIERS
    "Projects Alternate Timecard Layout - Expenditure Type"
    OWNER = "ORACLE"
    QUALIFIER_ATTRIBUTE_CATEGORY = "PACKAGE_CHOICE_LIST"
    QUALIFIER_ATTRIBUTE1 = "XXX_EXP_CHOICELIST_PKG.EXP_CHOICELIST_FUNC"
    QUALIFIER_ATTRIBUTE2 = "@RESOURCE_IDENTIFIER_ID"
    QUALIFIER_ATTRIBUTE4 = "N"
    QUALIFIER_ATTRIBUTE20 = "N"
    QUALIFIER_ATTRIBUTE21 = "Y"
    QUALIFIER_ATTRIBUTE22 = "L"
    QUALIFIER_ATTRIBUTE24 = "ELEMENT_EXPENDITURE_SLF"
    QUALIFIER_ATTRIBUTE25 = "FLEX"
    QUALIFIER_ATTRIBUTE26 = "OTL_ALIAS_1"
    QUALIFIER_ATTRIBUTE27 = "Attribute1"
    QUALIFIER_ATTRIBUTE28 = "ALIAS"
    LAST_UPDATE_DATE = "2006/09/18"
    END HXC_LAYOUT_COMP_QUALIFIERS
    and here is the package and function :
    CREATE OR REPLACE PACKAGE BODY XXX_EXP_CHOICELIST_PKG AS
    FUNCTION EXP_CHOICELIST_FUNC(P_RESOURCE_IDENTIFIER_ID VARCHAR2)
    RETURN VARCHAR2
    IS
    l_alias_value_name VARCHAR2(100);
    l_resource_id NUMBER(20);
    BEGIN
    -- convert parameters
    l_resource_id := TO_NUMBER(p_resource_identifier_id);
    --code to retrieve the contents of the list using the parameters passed...
    BEGIN
    SELECT DISTINCT
    alias_value_name
    INTO l_alias_value_name
    FROM hxc_alias_values
    WHERE alias_definition_id = hxc_preference_evaluation.resource_preferences
    (l_resource_id, 'TC_W_TCRD_ALIASES|1|',sysdate)
    ORDER BY alias_value_name ;
    EXCEPTION
    WHEN OTHERS THEN
    RETURN (0);
    END;
    RETURN l_alias_value_name;
    END;
    END XXX_EXP_CHOICELIST_PKG;
    I tried even hardcoding l_resource_id and cant see any data?
    Thanks in advance
    [email protected]

    I see that you still have the same layout name used i.e. "Projects Alternate Timecard Layout". Try uploading your modified layout with a different name and attach that to the user. Bounce apache once and test.

  • OTL Timecard

    Hi,
    I need to add a display only field on the OTL Timecard. It should show the 'display_value' column from Custom2VO. The values I see in the ldt file for referencing Custom2VO are choice_list and lov - are there other options?
    Thanks!

    Add following line in component qualifier region of the ldt
    QUALIFIER_ATTRIBUTE30 = "Y"
    This attribute says read only flag Yes

Maybe you are looking for