OTL Mobile App PDF

Oracle Time and Labor
Configuring Timecards App

Implementation and Usage notes for Administrators
An Oracle Whitepaper
Oracle Mobile Timecards for Oracle E-Business Suite™: White Paper 2
Contributors:
Ashok Rajagopal
Praveen Kumar
Anima Prasad
Change History:
Version Date Comments

1.0 08-Jun-2014 Initial Version
1.1 27-Feb-2014 Modified setup steps for
MAF2.0
Acronyms Used:
Usage Meaning
OTL Oracle Time and Labor
Timecards App Oracle Mobile Timecards for Oracle E-Business
Suite™
SSWA Self Service Web Applications
LOV List of Values
OTLR Oracle Time and Labor Rules Engine
EBS Oracle Time and Labor Development

Contents
SSWA time entry VS Smartphone Time entry .................................................................................... 4
Smartphone Time entry...................................................................................................................... 4
Time entry using Smartphone App ................................................................................................. 8
Time Entry Implementation ........................................................................................................... 8
Non SSWA time entry and Timecards App ..................................................................................... 9
Using Timecards App ........................................................................................................................ 10
Administrators .............................................................................................................................. 10
Mobile Framework Configuration: ............................................................................................... 10
OTL Setup/Configuration: ............................................................................................................. 11
Users ............................................................................................................................................. 12
Configuring Timecards App .............................................................................................................. 13
Layout Components – Limitations and Restrictions ......................................................................... 15
Features in SSWA not available in Timecards App ........................................................................... 17
Features not supported in Timecards App ....................................................................................... 18
Features with limitations .................................................................................................................. 19
Seeded Layouts ready for use in Timecards App.............................................................................. 20
Using a custom Responsibility with Timecards App ......................................................................... 20
Using a Custom Menu with Timecards App ..................................................................................... 20
Using a configured layout with Timecards App ................................................................................ 21
Creating Value Sets for View Objects ............................................................................................... 21
Creating Value Sets for Hidden Attributes ....................................................................................... 26
Dependent LOVs ............................................................................................................................... 34
Method 1: Using Layout LDT files. ................................................................................................ 34
Method 2: ..................................................................................................................................... 36
Running OTL: Upgrade Layouts for Mobile Time Entry .................................................................... 45
Trouble Shooting .............................................................................................................................. 48
Mobile Foundation: ...................................................................................................................... 48
Timecards: .................................................................................................................................... 49

SSWA time entry VS Smartphone Time entry

SSWA time entry layouts follow a matrix layout where the whole timecard can be seen an edited in
the same page. Sample screenshot provided below.
Time entry in the Smartphone App however has to make use of limited space on screen with maximum
usability. Consequently the time entry mode in Timecards App is designed to make use of a day level
time entry with means to navigate to next and previous days within the timecard period. While
editing/viewing/creating a timecard above requires user to go to Recent Timecards-> Create/update in
SSWA, the same action happens the following way in Timecards App.
Smartphone Time entry

Here is a quick overview of the Time entry process in the Timecards app.
Pic 1: You can use the same login Pic 2: You can use the same Pic 3: Just like the way a
credentials that you use to login responsibility that you use to responsibility and functions are
to use the SSWA Timecard to enter/update the SSWA displayed in SSWA, Timecards
login to the Timecards app. Timecards in the Timecards app. app has a Springboard with all
the time entry related features

Pic 4: Similar to the Recent Pic 5: Time entry page displays Pic 6: Time entry page displays
Timecards page on SSWA, Time the same number of Timecard the same number of Timecard
Entry page on Timecards app Attributes as per the SSWA Attributes as per the SSWA
lists all details for the selected Timecard entry layout. Timecard entry layout.
date.
Sample of Seeded Payroll Sample of Seeded Projects
Selecting a date and tapping on Timecard layout on Timecards Timecard layout on Timecards
the Create button displays the app. app.
Time Entry page
PS: The week starts on Sunday

by default, it can be changed to
match you SSWA Timecard
period start date by using
Settings-> Start Week on

Pic 7: Tapping on Submit Time Pic 8: Just like Clicking on Details Pic 9: Just like the way, Time
on the Springboard displays the icon on the SSWA Recent entry rule error messages are
list of all Timecards which need Timecards page, Tapping on the displayed when Timecard is
to be submitted for further Timecard period on Submit Time submitted in SSWA, Timecards
processing. page on Timecards app displays mobile app also displays the
Timecards in Error status are the day wise summary of all errors messages as part of
displayed with a Error Icon Time entries and the status of Timecards submission process.
the Timecards in the header
region. You also have the option to edit
You can Submit the Timecard by the time entires from Time
tapping on the Submit button on Details page.
top right corner.

Pic 10: Tapping on View Time on Pic 11: Similar to the concept of Pic 12: Clicking on the Action
the Springboard displays the list Templates in SSWA Timecard, button on the Footer displays
of all timecard for the current there is an option of Quick Entry the other options to quickly
month which have been which defaults either the Last enter the time.
submitted and the latest status Saved Entry or the your You can enable the Default Quick
of that timecard. Favourite time entry for today Time by using Settings page.

Time entry using Smartphone App

Time entry from Timecards App, as a result of the innate mobility is different from SSWA applications in
the following ways.
• Time entry/edit/delete follows a one-detail per entry mode. It means that each detail needs to
be entered and a save issued.
• Due to limited availability of space, the maximum number of layout attributes allowed in
Timecards App is set to Seven.
• A timecard gets automatically created for each detail Saved as mentioned above. This timecard
has a NEW status Draft.
• A timecard saved in Draft status in the device is not visible in SSWA applications. However, this
timecard period is not available for Create/Edit/Approve or Retrieve to recipient applications.
This is to ensure data integrity.
• A timecard Saved (status: Working), Submitted (status: Submitted), Approved (status:
Approved), or Rejected (status: Rejected), acted upon in the Device with an edit would be
automatically converted to Draft Status. However, this status change and the changes to
timecard data are not visible in SSWA until the following action is done.
• Timecard(s) saved in Draft status need to be submitted by the user from the Device to complete
timecard creation/edit activity.
Time Entry Implementation
With the multiple flavors of time entry available in OTL with flexible options, the primary objective
of the design of the Timecards App time entry mode is to ensure that basic functionality of time entry
and configurations are made available to the smartphone devices with best performance and easiest
configuration options. Timecards App time entry follows the Self Service timecard layout concepts as
the foundation to build on. The following salient features may be noted.
OTL Self Service time entry uses the concept of Self Service Timecard Layouts which are packaged in
LDT files. Each of the LDT files defines an array of layout components, the definition of which is
available for further configuration. Self Service Timecard Layouts use View Objects for various Layout
Attributes to search for, select and display Timecard attributes. To aid ease of configuration, upgrade
and optimum performance, Timecards App uses Value Sets in place of View Objects for Layout
Attributes to search for, select and display Timecard Attributes. Consequently all self service layouts
require an upgrade path to enable them for Time entry using Timecards App. This is detailed in the later
sections.
The following table shows the basic differences between SSWA based time entry and Timecards App
based time entry

Table 1
SSWA Timecards App
Follows matrix layout where timecards are created/edited Follows a detail layout where time entries are created/edited
as a whole detail by detail
Requires one Save per timecard after editing one or more Requires one Save(to Draft status) per time entry.
details
Layout attributes are primarily based on View Objects Layout Attributes are primarily based on Value Sets
Allows extensive configuration by multiple permutations of Configuration limited to Layout attributes definition and order.
LDT file definitions
No Draft status Saved time entries move into Draft Status timecards
Periods available for edit dependent upon Self Service Maximum 3 months periods available for edit. Self Service
status that allows Edits status that allows Edits may be used to further limit time entries.
Does not allow edit of timecards in Error Status Allows edit of timecards in Error status.
LOV components are allowed to have multiple columns for LOV components are allowed to have a Single column to select
additional information with no additional columns shown. However, a concatenated
list of columns may be configured.
No restriction on number of layout attributes available on Number of layout attributes allowed is limited to 7
Self Service layout
Non SSWA time entry and Timecards App

OTL also provides other time entry modes like Timekeeper and Timestore Deposit API. While these
are meant to work hand in hand with SSWA, there are shops which use OTL exclusively with
Timekeepers and Timestore APIs. Such implementations however do not fall in the primary usage of
Smartphone where an employee is supposed to key in time for themselves. However in cases where TK
or API based time entry complements SSWA based time entry, Timecards App functionality has a value.
If your OTL implementation does not use a SSWA time entry, and no Self Service layouts (Seeded or
custom) are used for time entry, it is not possible to use Timecards App. Timecards App requires a valid
Self Service layout attached to the employee’s preferences used as the foundation for time entry.
The following points about usage of Timecards App may be noted for implementations using
Timekeeper and/or Timestore Deposit API for time entry.
• Timecards App requires a Self Service layout attached to the employee for functioning.
• It may be possible for Administrators to attach Self service layouts to employees in preferences,
though SSWA is not used by employees. Timecards App may be usable in this case, but with
respect to the following point.
• In cases where Self Service layout and TK layout are not equivalent to each other, Timecards
App time entry bases itself on Self Service layout. Eg. If Self Service layout uses seeded Payroll
layout (with Hours type and Cost centre), while timekeeper uses a layout with Hours Type, Cost
Centre and Activity Type, Timecards App follows the attributes from Self Service layout.
• In direct consequence to the above factor, a layout attribute configured in Timekeeper only
would not be available for use in Timecards App.

Using Timecards App
Administrators
Administrators need to perform the following steps to make Timecards App available for users.
1. Mobile Framework Configuration

2. OTL Setup/Configuration
Mobile Framework Configuration:

For Timecards App to access the EBS server, the mobile configuration service needs to be enabled using
the following steps given below.
The following MOS note can be accessed to get more details on the Mobile Framework Configuration
steps: Oracle E-Business Suite Mobile Apps Administrator's Guide for Release 12.1 and Release 12.2 (Doc
ID 1642431.1)
• On an instance where mobile framework patches are installed, Login as SYSADMIN user and
navigate to Mobile Framework responsibility.
• Enter Time and Labor Engine in the Parent Application Field and search.

• Change the Status to Enabled, and click on the “Save and Generate Files” button.
• To confirm if the configuration service has been successfully enabled, try this url
http(s):<<your_host>>:<<port>>/OA_HTML/config/com.oracle.ebs.hr.hxc.Timecards/connection
s.xml
• This URL should display the connections.xml file. If the configuration service is not enabled
properly then a corresponding error is thrown.
OTL Setup/Configuration:
• The initial version of Timecards App has limited support; Adjust OTL preferences to turn off
features which are not required for mobile use.
• Set Self Service Timecard Layouts to one that is already supported (see Table 3) or follow steps
mentioned in this document to upgrade the Layouts used.
• Add Role “Mobile Time Entry” to the responsibility used by the users. 1 Refer Using a custom
Responsibility with Timecards App for more details.
• Add Menu “Mobile Time Entry” as a submenu to the menu used for Time entry. 2
1
This step may be skipped for seeded OTL self service responsibilities. This is a mandatory step for all custom
Responsibilities used to enter Time in SSWA.
2
This step may be skipped for seeded OTL Menus. This is a mandatory step for all custom menus.

Users
To use Timecards App, users may need the following information.
• Username/Password to log into Oracle E-Business Suite instance.
• Oracle E-Business Suite Server URL in the following format :
ht t p( s) : / / <host name>: <por t >/ OA_HTML/ conf i g
To start using Timecards App, a user must need to follow the steps below.
• Download and install the App from authorized location.
• In the one-time configuration screen, key in username, password and the configuration service
URL.
• After above configuration completes key in username and password in the Login page to
authenticate the session.
• In the Responsibilities page, choose the appropriate responsibility to use Timecards App.

Configuring Timecards App

Seeded Projects Layout shown below.
ProjectLOVVO ExpenditureType2LOVVO
TaskLOVVO
The above screenshot shows Seeded Projects Layout. There are 3 layout attributes in the layout,
Project, Task and Type. Each of these attributes are based on a View Object, shown in the picture. The
respective View Objects are used to display the List of valid Values to select by the user and to translate
already selected values.
The same timecard, for the same user looks like below in Timecards App.
ProjectLOVVO_VS
TaskLOVVO_VS
ExpenditureType2LOVVO_VS

Each layout attribute in the Timecards App is based on a Value set for displaying List of Valid Values, and
Translation of already stored attributes. These value sets are built based on the existing View Objects
and are available out of the box for seeded layouts listed below.
The following pages describe how a Self Service timecard layout is upgraded for usage in Timecards App.
For some seeded layouts this is already taken care of out of the box, while for some this may be covered
in future releases. Refer Table 3 for the list of Self Service Layouts upgraded out of the box.
For all configured layouts, the detailed steps may be executed to enabled time entry using Timecards
App.

Layout Components – Limitations and Restrictions
List of Values
The following LOVs are supported
• Seeded LOVs for the layouts listed in Table 3.
• Configured LOVs based on CustomXVOs, in turn based on HXC_CUI_CUSTOMX_V, listed in
section LOV Custom Objects in Timecard Config UI WP. These layouts require running of OTL:
Upgrade layouts for Mobile time entry. Refer to page 45.
• Any custom LOV object that works on a Self Service timecard layout, that is not dependent on a
Hidden Field.
• Any custom LOV object that works on a Self Service timecard layout, that stores not more than 3
hidden attributes.
• Any custom LOV object that works on a Self Service timecard Layout which has not more than a
single component with Hidden attributes.
• Any custom LOV object that works on a Self Service timecard layout that uses the bind variables
limited to this list.
“ RESOURCE_I DENTI FI ER_I D, TI MECARD_BI ND_START_DATE, TI MECARD_BI ND
_END_DATE, ALI ASI D”
For all Layouts other than the Seeded Layouts listed in Table 3, running OTL: Upgrade Timecard Layouts
program is mandatory.
Choice Lists
The following Choice lists are supported.
• Seeded choice lists belonging to the layouts mentioned in Table 3.
• Any custom choice list based on CustomXVO, in turn based on HXC_CUI_CUSTOMX_V views.
• Any custom choice list that works on a Self Service Timecard Layout with not more than 3
hidden attributes, and a single component storing the hidden attributes.
• Any custom choice list that works on a Self Service timecard layout that uses the bind variables
limited to this list.
“ RESOURCE_I DENTI FI ER_I D, TI MECARD_BI ND_START_DATE, TI MECARD_BI ND_EN
D_DATE, ALI ASI D”
For all Layouts other than the Seeded Layouts listed in Table 3, running OTL: Upgrade Timecard Layouts
program is mandatory.
Package Choice Lists

The following package choice lists are supported.
• Seeded package choice lists belonging to layouts mentioned in Table 3.
• Any ONE custom package choice list per layout, using parameters limited to the following.
RESOURCE_I DENTI FI ER_I D, TI MECARD_BI ND_START_DATE, TI MECARD_BI ND_
END_DATE
Text fields
Layouts holding Text Fields for Timecard Attributes are not allowed to be used in Timecards App
currently.

Descriptive Flexfields
Any descriptive flexfield based layout attribute is not supported in Timecards App. This is planned for a
future release.

Features in SSWA not available in Timecards App

Following features in SSWA based time entry are not available in Timecards App. These are planned for
a future release.
Override/Default Approver
Facility to enter Override approver is not available in Timecards App. However, the timecards created in
devices may be edited in SSWA to key in Override approvers.
Timecard Level Comments

Timecards App does not allow users to key in timecard level comments. This is planned for a future
release.
Detail Level Comments

Though not available in Seeded layouts, Self Service layouts can be configured to enable detail level
comments for each time entry. This functionality is also available in Timekeeper. Timecards App
however does not support a provision to enter detail level comments.
Additional Details
Self Service Layouts functionality of entering Additional details for Projects timecards, configured on PA
Expenditure Item DFF is not available currently in Timecards App.
Absences/PTO Accrual region

Self Service functionality of displaying Absences/PTO in the timecard header is not available in
Timecards App.
Timecard Header level Message

Since there is no provision in Timecards App to display any message in the timecard header,
configuration option of timecard level message header is not available as well. This is planned for a
future release.
Regular/Overtime Totals – Time category based Totals

The Hours totals on Confirmation page are not available for viewing in Timecards App. However,
timecards created by the device may be opened in SSWA to view totals.

Features not supported in Timecards App

The following features of OTL are not supported in Timecards App. If your implementation uses either
of these functionalities, you may have to wait for a future release to use Timecards App.
Change and Late Audit

CLA functionality is not supported in Timecards App. This also means that employees using Timecards
App should have no Audit Layout or Audit Time Entry rules attached to preferences along with Self
service timecard flow set to standard.
OTL Absences Integration

OTL Absences Integration is not supported for Timecards App. An employee for whom Absences is
configured as part of OTL preferences is not allowed to use Timecards App.
Quarterly/Half yearly/Yearly Time periods

Employees who use quarterly, half yearly or yearly time card or approval periods are not allowed to use
Timecards App. Support to this feature is planned for a future release.
Templates Functionality
Facility to create and use Templates is not supported in Timecards App. This is planned for a future
release

Features with limitations

Following features of Oracle Time and Labor, though supported for Timecards App do have certain
limitations of use.
OTLR Engine
Timecards App allows time entry and edit for OTLR users. However, time explosion is not available for
users to see on Timecards App. For viewing explosion of time, the respective timecards have to be
submitted from smartphone devices and must be opened thru Recent Timecards page in SSWA.
Time Entry Rules

Timecards App allows Time entry rule functionality for all cases except rules to be enforced during
Timecard Save. Save action from devices move the timecards to status Draft which does not enforce
Time entry rules. However, all time entry rules enabled to fire during submission and delete work as
intended.
Supported Application sets

The following matrix shows application sets and their usability with Timecards App.
Table 2
Application Set Layout Used Usage Note
Payroll Listed in Table 3 No Upgrade Required
Payroll and Human Resources Listed in Table 3 No Upgrade Required
Payroll Configured Layout Upgrade Required
Projects Listed in Table 3 No Upgrade Required
Projects Configured Layout Upgrade Required
Projects and Payroll Listed in Table 3 No Upgrade Required
Projects and Payroll Configured Layout Upgrade Required
Any application set mentioned above with Usage mentioned as Upgrade Required requires
Administrators to run OTL: Upgrade Timecard Layouts for Mobile Time Entry for each layout used. This
also means that such layouts may work only within the limitations mentioned in various sections in this
document. Any application set for which layouts do not follow the standards listed in this document
may not work seamlessly even after running OTL: Upgrade Timecard Layouts for Mobile Time entry.
Any application set which is not mentioned in the above Table, which may be a permutation of the
available time recipients for OTL, is not certified to work with Timecards App.

Seeded Layouts ready for use in Timecards App

The following table lists the seeded layouts ready for use out of the box in this release.
Table 3
LAYOUT_NAME DISPLAY_LAYOUT_NAME
PAYROLL-TIMECARD Payroll Timecard Layout
PROJECTS-TIMECARD Projects Timecard Layout
EXCEPTION-TIMECARD Exception Layout - Timecard Entry Page
PROJECTS-ALTERNATE-TIMECARD Projects and Payroll Timecard Layout
EXCPTO-TIMECARD Exception Layout with ACC BAL - Timecard Entry Page
US-EXCEPTION-TIMECARD US Exception Layout - Timecard Entry Page
US-PROJECTS-ALTERNATE-TIMECARD US Projects and Payroll Timecard Layout
PROJECTS-DETAILS-TIMECARD Projects Timecard Layout - With Project & Task details concatenated
PROJECTS-DET-ALT-TIMECARD Projects and Payroll Timecard Layout - With Project & Task details concatenated
US-PROJPAY-DET-TIMECARD US Projects and Payroll Timecard Layout - With Project & Task details concatenated
Using a custom Responsibility with Timecards App

Timecards App is configured to use seeded OTL Self service responsibilities. However, if you use one of
your own responsibilities, you must perform the below steps.
1. Login as Sysadmin -> User Management.
2. Go to Roles & Role Inheritance.
3. Query your responsibility and add role Mobile Time Entry to the responsibility.
A sample screenshot shown below.
Using a Custom Menu with Timecards App

Timecards App requires Menu Mobile Time Entry to function. For responsibilities that do not use
seeded OTL menu Time and Expenses Self Service Menu, add Mobile Time Entry as a submenu to your
custom menu.

Using a configured layout with Timecards App
Upgrading Self Service timecard Layouts involves the following steps.

1. Analyze the layout to list the View Objects used for Layout attributes.
2. Create Value sets for each View Object.
3. Run OTL: Upgrade Layouts for Mobile Time Entry.
If these steps are not performed for the Self Service timecard Layout attached to the employee, logging
in to Timecards App throws the following error.
“Invalid Setup: XXX Timecard Layout”
where XXX Timecard Layout is the name of the Self Service timecard layout attached to the
employee.
This error may be thrown in other cases where no Self Service timecard layout is attached to the
employee explicitly by the Administrator (the default layout may be picked up by the application in this
case) and the default Self Service timecard Layout is not upgraded for Timecards App.
Creating Value Sets for View Objects

1. Locate the name of the View Object
The name of the view object used for any layout attribute is available in the LDT file for the layout,
as qualifier_attribute1 . Examples of Layout attributes Project (from seeded Projects Layout) and
Cost Center (from Seeded payroll layout) provided below. Name of the VO shown in Red.
BEGI N HXC_LAYOUT_COMPONENTS " Payr ol l Ti mecar d Layout - Cost Cent er "

OWNER = " ORACLE12. 2. 0"
COMPONENT_VALUE = " COSTCENTER"
REGI ON_CODE = " HXC_CUI _TI MECARD"
REGI ON_CODE_APP_SHORT_NAME = " HXC"
ATTRI BUTE_CODE = " HXC_TI MECARD_COST_CENTER"
ATTRI BUTE_CODE_APP_SHORT_NAME = " HXC"
SEQUENCE = " 190"
COMPONENT_DEFI NI TI ON = " CHOI CE_LI ST"
RENDER_TYPE = " WEB"
PARENT_COMPONENT =
" Payr ol l Ti mecar d Layout - Day Scope Bui l di ng bl ocks f or wor ker t i mecar d mat r i x"
LAST_UPDATE_DATE = " 2004/ 05/ 24"
BEGI N HXC_LAYOUT_COMP_QUALI FI ERS " Payr ol l Ti mecar d Layout - Cost Cent er "
QUALI FI ER_ATTRI BUTE_CATEGORY = " CHOI CE_LI ST"
QUALI FI ER_ATTRI BUTE1 = " Cost Cent er 2VO"
QUALI FI ER_ATTRI BUTE4 = " N"
QUALI FI ER_ATTRI BUTE8 = " Di spl ayVal ue"
QUALI FI ER_ATTRI BUTE9 = " Val ue#NUMBER"
QUALI FI ER_ATTRI BUTE10 =
" or acl e. apps. hx c. sel f s er vi ce. t i mecar d. ser ver . Cost Cent er 2VO"
QUALI FI ER_ATTRI BUTE11 = " TI MECARD_BI ND_END_DATE| TI MECARD_BI ND_END_DATE"
QUALI FI ER_ATTRI BUTE17 = " Or aTabl eCel l Text "
QUALI FI ER_ATTRI BUTE21 = " Y"
QUALI FI ER_ATTRI BUTE22 = " L"
QUALI FI ER_ATTRI BUTE25 = " FLEX"
QUALI FI ER_ATTRI BUTE26 = " Dummy Cost Cont ext "
QUALI FI ER_ATTRI BUTE27 = " At t r i but e1"
END HXC_LAYOUT_COMP_QUALI FI ERS
END HXC_LAYOUT_COMPONENTS
BEGI N HXC_LAYOUT_COMPONENTS " Pr oj ect s Ti mec ar d Lay out - Pr oj ect "
COMPONENT_VALUE = " PROJ ECT"
ATTRI BUTE_CODE = " HXC_TI MECARD_PROJECT"

SEQUENCE = " 210"

COMPONENT_DEFI NI TI ON = " LOV"
PARENT_COMPONENT =
" Pr oj ect s Ti mecar d Layout - Day Scope Bui l di ng bl ocks f or wor ker t i mecar d mat r i x"
BEGI N HXC_LAYOUT_COMP_QUALI FI ERS " Pr oj ect s Ti mec ar d Layout - Pr oj ect "

QUALI FI ER_ATTRI BUTE_CATEGORY = " LOV"
QUALI FI ER_ATTRI BUTE1 = " Pr oj ect LOVVO"
QUALI FI ER_ATTRI BUTE3 = " HXC_CUI _PROJECT_LOV"
QUALI FI ER_ATTRI BUTE4 = " 809"
" HxcCui Pr oj ect Number | PROJECT- DI SPLAY| CRI TERI A| N|
HxcCui Pr oj ect I d| PROJECT| RESULT| N|
HxcCui Pr oj ect Number | PROJECT- DI SPLAY| RESULT| N"
QUALI FI ER_ATTRI BUTE8 = " Pr oj ect Number "
QUALI FI ER_ATTRI BUTE9 = " Pr oj ect I d#NUMBER"
" or acl e. apps. hx c. sel f s er vi ce. t i mecar d. ser ver . Pr oj ect LOVVO"
QUALI FI ER_ATTRI BUTE26 = " PROJECTS"
QUALI FI ER_ATTRI BUTE28 = " PROJECT"
Alternatively you can run the below query to figure out the View objects attached to each of your layout
attributes.
s el ec t Component _name,
VO_NAME,
Layout _at t r i but e,
Bi nd_par amet er s
f r om hx c_mob_l ay out _comps _v
wher e l ayout _i d = : l ay out _i d
Snapshot below shows the query results for seeded Projects Layout, returning the values for 3
attributes, Project, Task and Expenditure Type.
2. Analyze the query for in your VO

A View Object usually has a query of the following structure
SELECT i dc ol umn,
di spl ay _c ol umn,
addi t i onal _c ol umns
FROM XXX_TABLE
WHERE f i l t er _condi t i ons

The View Object usually selects multiple columns, one of which would be the Id or the Value to be
stored in HXC_TIME_ATTRIBUTES table. There would be one display column, which would be the
user readable value or name of the attribute. There may be additional columns shown as additional
information in the LOV popup pages. The key items we are looking for in this case are the Id or the
Value to be stored, and the display value. For ease of reference in this and following sections, let’s
call these as Id Column and Display Column.
To easily figure out the Id and Display columns for your View Object, you may look at
qualifier_attribute9 and qualifier_attribute8 in your layout attribute definition. These are shown in
Blue below.
BEGI N HXC_LAYOUT_COMP_QUALI FI ERS " Payr ol l Ti mecar d Layout - Cost Cent er "
QUALI FI ER_ATTRI BUTE_CATEGORY = " CHOI CE_LI ST"
QUALI FI ER_ATTRI BUTE1 = " Cost Cent er 2VO"
QUALI FI ER_ATTRI BUTE8 = " Di s pl ay Val ue "
QUALI FI ER_ATTRI BUTE9 = " Val ue #NUMBER"
" or acl e. apps. hxc. sel f ser vi ce. t i mecar d. ser ver . Cost Cent er 2VO"
QUALI FI ER_ATTRI BUTE11 = " TI MECARD_BI ND_END_DATE| TI MECARD_BI ND_END_DATE"
QUALI FI ER_ATTRI BUTE26 = " Dummy Cost Cont ext "
BEGI N HXC_LAYOUT_COMP_QUALI FI ERS " Pr oj ect s Ti mecar d Layout - Pr oj ect "
QUALI FI ER_ATTRI BUTE8 = " Pr oj ec t Number "
QUALI FI ER_ATTRI BUTE9 = " Pr oj ec t I d #NUMBER"
" or acl e. apps. hxc. sel f ser vi ce. t i mecar d. ser ver . Pr oj ect LOVVO"
For ProjectLOVVO above, used for Project, VO query from ProjectLOVVO.xml is

s el ec t pr oj ec t _number pr oj ec t number ,
pr oj ec t _name pr oj ec t name,
pr oj ec t _det ai l s pr oj ec t det ai l s ,
pr oj ec t _i d pr oj ect i d,
st ar t _dat e,
compl et i on_dat e,
car r y i ng_out _or gani z at i on_i d
f r om pa_onl i ne_pr oj ec t s _v
From the LDT file definition, the Id column is ProjectId, which in the above query is a Column Alias
for project_id.
The display column is ProjectNumber, which in the above query is a column Alias for
project_number.
3. Once we have figured out the required values for Id column and Display column, we may proceed to
creation of Value Sets.
Steps below shows creation of Value set for View Object ProjectLOVVO.xml for the seeded projects
layout.
From Application Developer -> Application -> Validation -> Sets 34
3
The Value set created should always be of Validation Type Table. Value sets of other validation types are not
supported in this release.
4
The Value set example shown here follows a naming convention of VO_NAME_VS. This is followed to make
the Value sets created Well Defined while upgrading the layouts using OTL: Upgrade layouts for Mobile
Time Entry. Administrators may follow any naming convention.

Following section explains the values to use for fields in the Validation Information page and
the rationale in arriving at the right values.
Table Name: The table in the FROM clause of the SELECT query in the View object is used
here. If there are multiple tables, a comma separated list may be used here, shown in examples
below. If there are multiple tables, using Table aliases may be required. You must ensure that
the Value set is tested successfully. For cases where there are more table names than what can
be put in this field, a View may be created out of the View Object’s query and used here. An
example of this case is ExpTypeElementLOVVO_VS, delivered for the Seeded Projects Layout.
Value: This field represents the Display column from the View Object’s query. It must be
noted here that only one column is allowed to be a display column, and hence multiple
additional columns are never displayed in Timecard App’s LOV searches. However, a
concatenated list of columns is allowed to be used in this field. The example above shows
“project_number” as the Display column. It may be modified to “project_number||’-
‘||project_name” to show Project Name along with Project Number.
Meaning: This field must be left blank.
Id: This field represents the Id column of the layout attribute. The example above shows
“project_id” column. No concatenated values are allowed in this field. It must be noted that
the column mentioned in this field is the value that actually gets stored in
HXC_TIME_ATTRIBUTES and must be able to uniquely identify a value selected. In most cases,
the column used here should be the primary key.
Where/Order By: Any filter conditions used in the View Objects’ query may be inserted
here. Since our example above does not have any filter conditions in the View Objects,
Expenditure Type LOV’s Value set is provided below as an example. Any bind variable or any
other condition must be used here.

Note the WHERE/Order By field that uses bind variables :TIMECARD_BIND_START_DATE and
:TIMECARD_BIND_END_DATE amongst other conditions.
Additional Columns: This field is to be used to add Hidden Attributes to the Value sets. For
more explanation of how to use this field, refer to the following section.
Creating Value Sets for Hidden Attributes
Definition of Hidden Attributes

Definition of Hidden attributes can be found in the LDT file used to create the configured layouts.
Hidden Attributes, conceptually are attributes which are not selected explicitly by the user nor are they
displayed on the timecard. A sample hidden field definition is provided below. Example used is seeded
Projects layout with System Linkage Function as hidden field.
BEGI N HXC_LAYOUT_COMPONENTS
" Pr oj ect s Ti mecar d Layout - Syst em Li nkage Funct i on"
COMPONENT_VALUE = " SYSTEMLI NKAGEFUNCTI ON"
SEQUENCE = " 200"
COMPONENT_DEFI NI TI ON = " HI DDEN_FI ELD"
PARENT_COMPONENT =
BEGI N HXC_LAYOUT_COMP_QUALI FI ERS

" Pr oj ect s Ti mecar d Layout - Syst em Li nkage Funct i on"
QUALI FI ER_ATTRI BUTE_CATEGORY = " HI DDEN_FI ELD"
QUALI FI ER_ATTRI BUTE18 = " EXCLUDE"
QUALI FI ER_ATTRI BUTE19 = " | CSV| "


QUALI FI ER_ATTRI BUTE23 = " FORM"
QUALI FI ER_ATTRI BUTE28 = " SYSLI NKFUNC"
Qualifier_attribute28 is the key here, for populating hidden field. The value provided in
qualifier_attribute28 here would be attached to another layout attribute, which will be picked up by the
layout when time is entered. For the above sample hidden field, the value in qualifier_attribute28 is
“SYSLINKFUNC”. This value is picked up from another layout component, Expenditure type. Layout
Component qualifiers would be as shown below.
BEGI N HXC_LAYOUT_COMPONENTS " Pr oj ect s Ti mecar d Layout - Expendi t ur e Type"
COMPONENT_VALUE = " EXPENDI TURETYPE"
ATTRI BUTE_CODE = " HXC_TI MECARD_EXPTYPE"
SEQUENCE = " 230"
PARENT_COMPONENT =

" Pr oj ect s Ti mecar d Layout - Expendi t ur e Type"
QUALI FI ER_ATTRI BUTE1 = " Expendi t ur eType2LOVVO"
QUALI FI ER_ATTRI BUTE3 = " HXC_CUI _EXPTYPE2_LOV"
" HxcCui Expt ypeDi spCol umn| EXPTYPE-
DI SPLAY| CRI TERI A| N| HxcCui Expt ypeExpType| EXPTYPE| RESULT| N|
HxcCui Expt ypeDi spCol umn| EXPTYPE-
DI SPLAY| RESULT| N| HxcCui Expt ypeSysLi nkFunc| SYSLI NKFUNC| RESULT| N"
QUALI FI ER_ATTRI BUTE7 = " SYSLI NKFUNC| Syst emLi nkageFunct i on "
QUALI FI ER_ATTRI BUTE8 = " Di spl ayCol umn"
QUALI FI ER_ATTRI BUTE9 = " Expendi t ur eType"
" or acl e. apps. hxc. sel f ser vi ce. t i mecar d. ser ver . Expendi t ur eType2LOVVO"
" TI MECARD_BI ND_END_DATE| TI MECARD_BI ND_END_DATE| TI MECARD_BI ND_START_DATE|
TI MECARD_BI ND_END_DATE| TI MECARD_BI ND_END_DATE| TI MECARD_BI ND_START_DATE"
QUALI FI ER_ATTRI BUTE28 = " EXPTYPE"
Qualifier_attribute28 of Hidden field is linked with qualifier_attribute7 of the component that

picks up the value for the hidden field ( in this case, SystemLinkageFunction).

Another method to get the value to be used for Hidden field in the value set to be created is to
run the query as provided below*.
select *
from hxc_mob_hidden_field_details_v
where layout_id = :1;
The above query returns a column called “column_name”. Value in this column is the key in
specifying the hidden attributes in the value set to be prepared.
If there are multiple hidden fields, the above query would return more than one rows.
All of the 3 hidden attributes should have corresponding columns in the Value set to be defined.
Steps
Analyze the query in the VO used for hidden attribute.
The VO used for another layout attribute should return the value to be used for the hidden attribute(s)
too. The format of the query in the VO typically would be like this.
SELECT i dcol umn,

di spl ay col umn,
addi t i onal _i nf o,
mor e_addi t i onal _i nf o,
hi dden_at t r i but e1,
hi dden_at t r i but e2,
hi dden_at t r i but e3
FROM VO_TABLE
WHERE f i l t er _c ondi t i ons
The value set would be created for the VO with the following specifications in the additional information
page.
Tabl e Appl i cat i on: Ti me and Labor Engi ne

Tabl e Name: VO_TABLE
Val ue: di spl ay col umn
I D: i dcol umn
WHERE/ Or der By: f i l t er _c ondi t i ons

In addition to these values, the Additional Columns field should be populated with columns for hidden
attributes, with value returned by column_name from query above as aliases.
Addi t i onal Col umns: hi dden_at t r i but e1 c ol umn_name1, hi dden_at t r i but e2

col umn_name2, hi dden_at t r i but e3 c ol umn_name3
Example
Let’s take a scenario example of an LOV with 3 hidden attributes.
Analyze the definition of the attribute

Hidden Attributes’ definition as per LDT file
" OTL Demo Except i on Ti mecar d Layout - Locat i on LOV St at e"
COMPONENT_VALUE = " STATE"
SEQUENCE = " 220"
PARENT_COMPONENT =
" OTL Demo Except i on Ti mecar d Layout - Day Scope Bui l di ng bl ocks f or wor ker t i mecar d
mat r i x"
" OTL Demo Except i on Ti mecar d Layout - Locat i on LOV St at e"
OWNER = " ANONYMOUS"
QUALI FI ER_ATTRI BUTE26 = " Dummy El ement Cont ext "
QUALI FI ER_ATTRI BUTE28 = " STATE"
" OTL Demo Except i on Ti mecar d Layout - Locat i on LOV Count y"
COMPONENT_VALUE = " COUNTY"
SEQUENCE = " 230"
PARENT_COMPONENT =
mat r i x"
" OTL Demo Except i on Ti mecar d Layout - Locat i on LOV Count y"
QUALI FI ER_ATTRI BUTE28 = " COUNTY"

" OTL Demo Except i on Ti mecar d Layout - Locat i on LOV Ci t y"

COMPONENT_VALUE = " CI TY"
SEQUENCE = " 240"
PARENT_COMPONENT =
mat r i x"
" OTL Demo Except i on Ti mecar d Layout - Locat i on LOV Ci t y"
QUALI FI ER_ATTRI BUTE28 = " CI TY"
LOV that picks out the hidden attributes defined like below.
" OTL Demo Except i on Ti mecar d Layout - Locat i on LOV"
COMPONENT_VALUE = " LOC"
ATTRI BUTE_CODE = " HXC_CUI _LOCATI ON_LABEL"
SEQUENCE = " 250"
PARENT_COMPONENT =
" OTL Demo Except i on Ti mecar d Layout - Day Scope Bui l di ng
bl ocks f or wor ker t i mecar d mat r i x"
" OTL Demo Except i on Ti mecar d Layout - Locat i on LOV"
QUALI FI ER_ATTRI BUTE1 = " Ci t yLi st VO"
QUALI FI ER_ATTRI BUTE3 = " HXC_CUI _LOCATI ON_LOV"
" Locat i onI d| LOCDI SPLAY| CRI TERI A| N|
Zi p| LOC| RESULT| N| Locat i onI d|
LOC- DI SPLAY| RESULT| N|
Count y| COUNTY| RESULT| N|
Ci t y| CI TY| RESULT| N|
St at e| STATE| RESULT| N"
QUALI FI ER_ATTRI BUTE7 = " STATE| St at e| COUNTY| Count y| CI TY| Ci t y"
QUALI FI ER_ATTRI BUTE8 = " Locat i oni d"
QUALI FI ER_ATTRI BUTE9 = " Zi p#STRI NG"
" or acl e. apps. hxc. sel f ser vi ce. conf i gui . us. ser ver . Ci t yLi st VO"
" St at e| STATE| Y#
Count y| COUNTY| Y#
Ci t y| CI TY| Y"
" upper ( St at e) = upper ( : : St at e) #
upper ( Count y) = upper ( : : Count y) #
upper ( Ci t y) = upper ( : : Ci t y) "


QUALI FI ER_ATTRI BUTE28 = " LOC"
As we see above, the LOV uses a VO named CityListVO. Query from the VO is as follows
sel ect pcy. CI TY_NAME| | ' , ' | |
pst . STATE_NAME| | ' , ' | |
pct . COUNTY_NAME| | ' count y, ' | |
pzc. ZI P_START Locat i onI d,
pst . STATE_ABBREV St at eI d,
pst . STATE_NAME St at e,
pct . COUNTY_NAME Count y,
pcy. CI TY_NAME Ci t y,
pzc. ZI P_START Zi p,
pzc. ZI P_END Zi pEnd
f r om
pay_us_st at es pst ,
pay_us_count i es pct ,
pay_us_ci t y_names pcy,
PAY_US_ZI P_CODES pzc
wher e
( pst . st at e_code < 52 or pst . st at e_code = 72)
and pcy. STATE_CODE = pst . STATE_CODE
and pcy. COUNTY_CODE = pct . COUNTY_CODE
and pct . STATE_CODE = pst . STATE_CODE
and pcy. CI TY_CODE = pzc. CI TY_CODE
and pcy. STATE_CODE = pzc. STATE_CODE
and pcy. COUNTY_CODE = pzc. COUNTY_CODE
or der
by pcy. CI TY_NAME,
pst . STATE_NAME,
pct . COUNTY_NAME,
pzc. ZI P_START
Let’s run the query to get Hidden Field details.
We have 3 hidden_attributes coming out from the above LOV component. For this case, let’s see the
steps to create the value set.
Following are the specifications from the VO and Layout comp qualifiers.
Display Column:
pc y . CI TY_NAME| | ' , ' | | ps t . STATE_NAME| | ' , ' | | pct . COUNTY_NAME| | ' count y, ' | | pzc. ZI P_START
Loc at i onI d
(As per qualifier_attribute8, which says LocationId. LocationId is an alias for the above
concatenated column list in the VO query. This is the text shown to the user in a Saved timecard)

Id Column:
pzc. ZI P_START Zi p ( As per VO quer y )
Zip#String ( from qualifier_attribute9; meaning column name from query is Zip, which in this case is
a Column Alias for pzc.zip_start and format is String)
Create Value set for Hidden Attributes
1. Create value set with validation type Table
2. Open Edit Information and key in values

Note the following

• Table Name field has all the tables in the VO query.
• Value field has the column corresponding to Display Column of the LOV component.
• Id field has the column corresponding to Id Column of the LOV component.
• Where/Order By field has the complete WHERE clause of the VO query
Now we have created the value set for the layout attribute Location LOV. Now let’s add the
columns for hidden attributes. These need to be added to Additional Columns.
There are 3 hidden columns with these column names: State, County, City.
These columns correspond to the following columns as per the VO query:
pst . STATE_NAME
pc t . COUNTY_NAME
pc y . CI TY_NAME
Additional column to be created as a combination of VO select columns and column aliases as

recognized by the layout
ps t . s t at e_name St at e, pc t . count y _name Count y , pc y . c i t y _name Ci t y
3. Add information to the Value set definition as below.

Value set is now ready to use.
Dependent LOVs
By definition, a dependent LOV is based on one or more previously selected Layout attributes. Such
LOVs need special steps for use in Mobile.
To know if your layout has a dependent attribute and to gather details about the dependent LOVs
follow either of these methods.
Method 1: Using Layout LDT files.

Key values to look for in the Layout LDT file, against the Layout component definition is
Qualifier_attribute14 and qualifier_attribute15. Shown below is a sample from Seeded Projects Layout.
BEGI N HXC_LAYOUT_COMPONENTS " Pr oj ect s Ti mecar d Layout - Pr oj ect "
COMPONENT_VALUE = " PROJECT"
SEQUENCE = " 210"
PARENT_COMPONENT =
BEGI N HXC_LAYOUT_COMP_QUALI FI ERS " Pr oj ect s Ti mecar d Layout - Pr oj ect "



QUALI FI ER_ATTRI BUTE8 = " Pr oj ect Number "
QUALI FI ER_ATTRI BUTE9 = " Pr oj ect I d#NUMBER"
" or acl e. apps. hxc. sel f ser vi ce. t i mecar d. ser ver . Pr oj ect LOVVO"
BEGI N HXC_LAYOUT_COMPONENTS " Pr oj ect s Ti mecar d Layout - Task"
COMPONENT_VALUE = " TASK"
ATTRI BUTE_CODE = " HXC_TI MECARD_TASK"
SEQUENCE = " 220"
PARENT_COMPONENT =
BEGI N HXC_LAYOUT_COMP_PROMPTS " HxcCui TaskPr oj ect I d" " AK_PROMPT"
REGI ON_APP_SHORT_NAME = " HXC"
ATTRI BUTE_APP_SHORT_NAME = " HXC"
END HXC_LAYOUT_COMP_PROMPTS
BEGI N HXC_LAYOUT_COMP_QUALI FI ERS " Pr oj ect s Ti mecar d Layout - Task"

QUALI FI ER_ATTRI BUTE1 = " TaskLOVVO"
QUALI FI ER_ATTRI BUTE3 = " HXC_CUI _TASK_LOV"
" HxcCui TaskNumber | TASK- DI SPLAY| CRI TERI A| N|
HxcCui TaskPr oj ect I d| PROJECT| PASSI VE_CRI TERI A| Y|
HxcCui TaskI d| TASK| RESULT| N| HxcCui TaskNumber | TASK- DI SPLAY| RESULT| N"
QUALI FI ER_ATTRI BUTE8 = " TaskNumber "
QUALI FI ER_ATTRI BUTE9 = " TaskI d#NUMBER"
" or acl e. apps. hxc. sel f ser vi ce. t i mecar d. ser ver . TaskLOVVO"
" HxcCui TaskPr oj ect I d| PROJECT| Y#HxcCui TaskPr oj ect Number | PROJECT- DI SPLAY| Y"
" pr oj ect _i d = : : HxcCui TaskPr oj ect I d#upper ( pr oj ect _number ) =
upper ( : : HxcCui TaskPr oj ect Number ) "
QUALI FI ER_ATTRI BUTE28 = " TASK"

The above excerpt from Projects layout LDT, shows the definition of Project and Task components’
definition. In the Task component definition, qualifier_attribute14 and qualifier_attribute15 shows the
details about the dependent component(shown in Red). Qualifier_attribute15 refers the WHERE clause
to be attached to the query to bind the value from previous attribute where as qualifier_attribute14
mentions which layout attribute it has to refer to. PROJECT, shown in Green above points to the Project
component’s qualifier_attribute28 in the previous definition (also shown in Green).
Using this method, it is now clear that the LOV for Task is dependent on Project LOV’s selected value.
Task LOV is the second layout attribute displayed on the Self Service layout and it is dependent on the
project, which is the first attribute.
To implement this feature in mobile application, the Value set created should have an additional
WHERE clause referring to the previous attribute. Qualifier_attribute15 has the WHERE clause to be
used.
So, we proceed on to define the WHERE clause as
“project_id = :attribute1”
Below screenshot shows the value set created for Task LOV.
Method 2:
This method uses a query to point out dependent attributes in a given layout.
sel ect deps. component _name dependent _component _name,
deps. l ayout _at t r i but e dependent _at t r i but e_num,
comps. component _name sour ce_component _name,
comps. l ayout _at t r i but e sour ce_at t r i but e_num,
REGEXP_REPLACE(
REGEXP_SUBSTR(
l cq2. qual i f i er _at t r i but e15, ' [ ^ #] +' , 1,
RANK( ) OVER ( par t i t i on by deps. l ayout _component _i d

or der by comps. l ayout _at t r i but e

)
) , ' ( : : ) . * ' , ' : ' | | l ower ( comps. l ayout _at t r i but e)
) WHERE_CLAUSE
f r om hxc_mob_l ayout _comps_v comps,
hxc_l ayout _comp_qual i f i er s l cq,
hxc_l ayout _comp_qual i f i er s l cq2,
( sel ect l ayout _i d,
l ayout _component _i d,
component _name,
par ent _component _i d,
l ayout _at t r i but e,
VO_name,
RTRI M( LTRI M( f i el d, ' | ' ) , ' | ' ) f i el d
f r om hxc_mob_l ayout _comps_v
unpi vot ( f i el d f or dep_col umn i n
( dependent _1,
dependent _2,
dependent _3,
dependent _4)
)
) deps
WHERE comps. par ent _component _i d = deps. par ent _component _i d
AND l cq. l ayout _component _i d = comps. l ayout _component _i d
AND l cq. qual i f i er _at t r i but e28 = deps. f i el d
AND deps. l ayout _i d = : LAYOUT
AND l cq2. l ayout _component _i d = deps. l ayout _component _i d
Use layout_id as the bind variable. Let’s see the query outputs for a few layouts.
Projects Layout
First and second columns give the detail of the layout attribute which is dependent on a previous
one. Third and fourth columns give details of the layout component which the former component is
dependent on. And WHERE Clause to be added to the Value set to be created is provided as the last
column. The above query result means that the Task component is dependent on Project component
and WHERE clause to be added is “project_id = :attribute1”

Purchasing Layout
The following example demonstrates creation of Dependent LOV components dependent on more than
one attributes. For this example, we are considering seeded Purchasing Layout. 5
Above query result shows two distinct components, Purchase Order Line and Price Type as
dependent attributes. They are dependent on one and two previous attributes respectively.
Purchase order line is dependent on Purchase Order Number and WHERE clause to be added is
“POHeaderid = :attribute1”.
Price Type is dependent on Purchase Order Number and Purchase Order Line( Two rows returned in
the query). Two conditions have to be added in the WHERE clause: “POHeaderId = :attribute1” and
“POLineId = :attribute2”. They may be joined as “POHeaderId = :attribute1 AND POLineId = :attribute2”.
It may be noted here that the WHERE clause derived by the query above uses column aliases.
Creation of the value set may require aliases to be replaced by actual column names. Eg.
PO_HEADER_ID instead of POHeaderId.
Example
Sample Value Set creation with more than one dependent attributes
Layout: Seeded Purchasing Layout 6
Component: Price Type
Excerpt from LDT file showing definition of Purchase Order Number, Line and Price Type.
5
Purchasing layout is used only as a sample layout for this case. This does not confirm all features of the
layout is allowed to be used in Timecards App.
6
Purchasing Layouts are not certified to work with Timecards App. Example shown here is for illustrative
purpose.

" Pur chasi ng Ti mecar d Layout - Pur chase Or der Number "
COMPONENT_VALUE = " PONUMBER"
REGI ON_CODE = " PO_CUI _TI MECARD"
REGI ON_CODE_APP_SHORT_NAME = " PO"
ATTRI BUTE_CODE = " PO_TI MECARD_PO_NUMBER"
ATTRI BUTE_CODE_APP_SHORT_NAME = " PO"
SEQUENCE = " 220"
PARENT_COMPONENT =
" Pur chasi ng Ti mecar d Layout - Day Scope Bui l di ng bl ocks f or wor ker t i mecar d mat r i x"
" Pur chasi ng Ti mecar d Layout - Pur chase Or der Number "
QUALI FI ER_ATTRI BUTE1 = " Pur chaseOr der Number LOVVO"
QUALI FI ER_ATTRI BUTE3 = " PO_CUI _PO_NUMBER_LOV"
" POCui PONumber | PO_NUMBER-
DI SPLAY| CRI TERI A| N| POCui POHeader I d| PO_NUMBER| RESULT| N| POCui PONumber | PO_NUMBER- DI SPLAY| RESULT| N"
QUALI FI ER_ATTRI BUTE8 = " PONumber "
QUALI FI ER_ATTRI BUTE9 = " POHeader I d#NUMBER"
" or acl e. apps. po. sel f ser vi ce. t i mecar d. ser ver . Pur chaseOr der Number LOVVO"
" TI MECARD_BI ND_START_DATE| TI MECARD_BI ND_END_DATE| RESOURCE_I DENTI FI ER_I D|
TI MECARD_BI ND_START_DATE| TI MECARD_BI ND_END_DATE| TI MECARD_I D| TI MECARD_OVN"
QUALI FI ER_ATTRI BUTE26 = " PURCHASI NG"
QUALI FI ER_ATTRI BUTE28 = " PO_NUMBER"
" Pur chasi ng Ti mecar d Layout - Pur chase Or der Li ne"
COMPONENT_VALUE = " POLI NE"
ATTRI BUTE_CODE = " PO_TI MECARD_PO_LI NE"
SEQUENCE = " 230"
PARENT_COMPONENT =
" Pur chasi ng Ti mecar d Layout - Pur chase Or der Li ne"
QUALI FI ER_ATTRI BUTE1 = " Pur chaseOr der Li neLOVVO"
QUALI FI ER_ATTRI BUTE3 = " PO_CUI _PO_LI NE_LOV"
" POCui POLi ne| PO_LI NE-
DI SPLAY| CRI TERI A| N| POLi neCui POHeader I d| PO_NUMBER| PASSI VE_CRI TERI A| N|
POCui POLi neI d| PO_LI NE| RESULT| N| POCui POLi ne|
PO_LI NE- DI SPLAY| RESULT| N"
QUALI FI ER_ATTRI BUTE8 = " POLi ne"
QUALI FI ER_ATTRI BUTE9 = " POLi neI d#NUMBER"
" or acl e. apps. po. sel f ser vi ce. t i mecar d. ser ver . Pur chaseOr der Li neLOVVO"
" TI MECARD_BI ND_START_DATE| TI MECARD_BI ND_END_DATE| RESOURCE_I DENTI FI ER_I D|
TI MECARD_BI ND_START_DATE| TI MECARD_BI ND_END_DATE| TI MECARD_I D| TI MECARD_OVN"

QUALI FI ER_ATTRI BUTE14 = " POLi neCui POHeader I d| PO_NUMBER| Y"

QUALI FI ER_ATTRI BUTE15 = " POHeader I d = : : POLi neCui POHeader I d"
QUALI FI ER_ATTRI BUTE28 = " PO_LI NE"
" Pur chasi ng Ti mecar d Layout - Pr i ce Type"
COMPONENT_VALUE = " PRI CETYPE"
ATTRI BUTE_CODE = " PO_TI MECARD_PRI CE_TYPE"
SEQUENCE = " 240"
PARENT_COMPONENT =
BEGI N HXC_LAYOUT_COMP_QUALI FI ERS " Pur chasi ng Ti mecar d Layout - Pr i ce Type"

QUALI FI ER_ATTRI BUTE1 = " Pur chaseOr der Pr i ceTypeLOVVO"
QUALI FI ER_ATTRI BUTE3 = " PO_CUI _PRI CE_TYPE_LOV"
" POCui Pr i ceTypeDsp| PRI CE_TYPE
- DI SPLAY| CRI TERI A| N| POCui POHeader I d| PO_NUMBER| PASSI VE_CRI TERI A| N|
POCui POLi neI d| PO_LI NE| PASSI VE_CRI TERI A| N|
POCui Pr i ceType| PRI CE_TYPE| RESULT| N|
POCui Pr i ceTypeDsp| PRI CE_TYPE- DI SPLAY| RESULT| N"
QUALI FI ER_ATTRI BUTE8 = " POPr i ceTypeDi spl ay"
QUALI FI ER_ATTRI BUTE9 = " POPr i ceType"
" or acl e. apps. po. sel f ser vi ce. t i mecar d. ser ver . Pur chaseOr der Pr i ceTypeLOVVO"
QUALI FI ER_ATTRI BUTE11 = " TI MECARD_I D| TI MECARD_OVN"
" POCui POHeader I d| PO_NUMBER| Y#POCui POLi neI d| PO_LI NE| Y"
" POHeader I d = : : POCui POHeader I d#POLi neI d = : : POCui POLi neI d"
QUALI FI ER_ATTRI BUTE28 = " PRI CE_TYPE"
Qualifier_attribute1 mentions PurchaseOrderPriceTypeLOVVO as the VO attached to this layout

attribute.
Query used in the VO is as follows.
SELECT poh. segment 1 PONumber
, poh. po_header _i d POHeader I d
, TO_CHAR ( pol . l i ne_num) POLi ne
, pol . po_l i ne_i d POLi neI d
, f l v. l ookup_code POPr i ceType
, f l v. meani ng POPr i ceTypeDi spl ay
FROM po_header s_al l poh
, po_l i nes_al l pol
, f nd_l ookups f l v
, ( SELECT ent i t y_i d

, pr i ce_t ype
, mul t i pl i er
FROM po_pr i ce_di f f er ent i al s
WHERE ent i t y_t ype = ' PO LI NE'
AND enabl ed_f l ag = ' Y'
UNI ON ALL
SELECT po_l i ne_i d
, ' STANDARD'
, 1. 0
FROM po_l i nes_al l
) popd
WHERE pol . po_header _i d = poh. po_header _i d
AND f l v. l ookup_t ype = ' PRI CE DI FFERENTI ALS'
AND f l v. l ookup_code = popd. pr i ce_t ype
AND popd. ent i t y_i d = pol . po_l i ne_i d
UNI ON
, hxc_t i me_bui l di ng_bl ocks day
, hxc_t i me_bui l di ng_bl ocks det ai l
, hxc_t i me_at t r i but es ht a
, hxc_t i me_at t r i but e_usages ht au
WHERE poh. po_header _i d = TO_NUMBER ( ht a. at t r i but e8)
AND pol . po_l i ne_i d = TO_NUMBER ( ht a. at t r i but e2)
AND f l v. l ookup_code = ht a. at t r i but e3
AND day. par ent _bui l di ng_bl ock_i d = : 1
AND day. par ent _bui l di ng_bl ock_ovn = : 2
AND det ai l . par ent _bui l di ng_bl ock_i d = day. t i me_bui l di ng_bl ock_i d
AND det ai l . par ent _bui l di ng_bl ock_ovn = day. obj ect _ver si on_number
AND ht au. t i me_bui l di ng_bl ock_i d = det ai l . t i me_bui l di ng_bl ock_i d
AND ht au. t i me_bui l di ng_bl ock_ovn = det ai l . obj ect _ver si on_number
AND ht au. t i me_at t r i but e_i d = ht a. t i me_at t r i but e_i d
AND ht a. at t r i but e_cat egor y = ' PURCHASI NG'
For ease of explanation, let’s consider only the first part of the UNION for now. Query is
, ( SELECT ent i t y_i d
, pr i ce_t ype
, mul t i pl i er
FROM po_pr i ce_di f f er ent i al s
WHERE ent i t y_t ype = ' PO LI NE'
AND enabl ed_f l ag = ' Y'
UNI ON ALL
SELECT po_l i ne_i d
, ' STANDARD'
, 1. 0
FROM po_l i nes_al l
) popd
WHERE pol . po_header _i d = poh. po_header _i d
AND f l v. l ookup_code = popd. pr i ce_t ype
AND popd. ent i t y_i d = pol . po_l i ne_i d
Let us first create a View out of the query so that it is easier to define the value set. This is not a
mandatory step.

From Application Developer responsibility, Value Sets
In Edit Information page,

As per qualifier_attribute8 and qualifier_attribute9 created Value(Display Column) and Id (Id column).
Qualifier_attribute14 and qualifier_attribute15 shows the below text

" POCui POHeader I d| PO_NUMBER| Y#POCui POLi neI d| PO_LI NE| Y"
" POHeader I d = : : POCui POHeader I d#POLi neI d = : : POCui POLi neI d"
Two layout attributes need reference in this value set, PO Number and PO line, first and second
attribute respectively.
WHERE clause to be build like
“POHeaderId = :attribute1 AND POLineId = :attribute2”


Running OTL: Upgrade Layouts for Mobile Time Entry
Include the concurrent program in your request group.
Invoke the program from the Administrator responsibility
Choose No if the request is being run for the first time for the layout to be upgraded. If you are doing a
rerun or a correction, choose Yes.

Select the layout you want to upgrade
Program automatically populates the layout attributes attached to the layout.
Against each layout attribute, select the appropriate value set.

Verify that the request completes successfully and look for the following message in the log
file.

Trouble Shooting
Mobile Foundation:
Issue #1
When entering user credentials and server URL in the configuration screen, no error message is
shown. However, the configuration screen is presented again.
Probable Cause
User credentials are wrong and/or configuration server URL is wrong.
Resolution
User should verify that they enter their valid E-Business Suite username and password. The
configuration server URL should be valid in the format of http(s)://<hostname>:<port>/OA_HTML/config
Issue #2
When entering valid user credentials and valid server URL in the configuration screen, no error
message is shown. However, the configuration screen is presented again.
Probable Cause
Application bundle id in the configuration service request sent to the E-Business Suite server
from the mobile app does not match with server setup.
Resolution
System administrator should verify that the application bundle id in the Mobile Application
Manager matches the mobile app implementation guide.
Issue #3
Configuration server URL is not accessible when tested from a web browser. An HTTP 404 error
appears.
Probable Cause
HTTP server configuration for configuration service is missing.
Resolution
Verify that AutoConfig was run after applying the appropriate ATG consolidated patch for your
Oracle E-Business Suite release.
Issue #4
Configuration server URL is not accessible when tested from a web browser. An HTTP 404 error
appears.
Probable Cause
HTTP server configuration for configuration service is missing.

Resolution
Verify that AutoConfig was run after applying the appropriate ATG consolidated patch for your
Oracle E-Business Suite release.
Issue #5
Login server URL is not accessible when users attempt to login to app.
Probable Cause
Issues with pre-requisite patch.
Resolution
The login service on the E-Business Suite server is automatically setup after patch application.
Login service is of format
http(s)://<hostname>:<port>/OA_HTML/config
Issues during patch application could result in login service in accessible. Contact Oracle
Support.
Timecards:
Issue #1
You do not have access to use this mobile application. Please contact your System
Administrator.
Probable Cause
“Mobile Time Entry” Role has not been added to the responsibility (or) “Mobile Time Entry”
Menu is missing.
Resolution
Add the “Mobile Time Entry” role to the responsibility and “Mobile Time Entry” menu as a
submenu to the associated responsibility.
Please refer to the white paper available in MOS Doc ID 1671889.1 for more details.
Issue #2
Invalid Setup: <<LAYOUT_NAME>> is not upgraded.
Probable Cause
Employee has a timecard layout preference which is not upgraded for mobile time entry.
Resolution
Check the layout attached to self service timecard layout preference. If not upgraded, please
execute the concurrent program “OTL: Upgrade Layouts for Mobile Time Entry”.
If layout attached to preference is upgraded, check if the employee has already entered
timecards with a layout that is not upgraded.

Issue #3
Invalid Setup: Absence Integration is enabled
Probable Cause
OTL Absence Integration is enabled for this user via OTL Preferences.
Resolution
The V1 version of mobile Timecard app does support OTL Absence Integration. Please disable
the Integration to use mobile timecard app.
Issue #4
Invalid Setup: Audit Layout has been set.
Probable Cause
User has OTL preference set up with an Audit Layout.
Resolution
Change and Late Audit feature is not supported in V1 version.
Remove the value in Audit Layout, (6th segment) in SS timecard layout preference.
Issue #5
Invalid Setup: Audit Preferences has been enabled.
Probable Cause
SS timecard flow is set to Audit
Resolution
Set SS timecard flow to Standard. Audit flow is linked to CLA feature which is not enabled for
mobile timecards.
Issue #6
Invalid Setup: Audit Time Entry Rule has been set.
Probable Cause
Time Store Audit Requirements is set to a valid Time entry rule.
Resolution
Set Time Store Audit Requirements to NULL. Audit Time Entry Rule is linked to CLA feature
which is not enabled for mobile timecards.

Issue #7
You must use <<RESP>> responsibility for this action.
Probable Cause
This issue occurs when multiple responsibilities are enabled for mobile timecards. Timecard
created with one responsibility cannot be modified using another responsibility.
Resolution
User must use the corresponding responsibility to modify the timecard. Navigate to Settings ->
Responsibility and select the correct responsibility.
Issue #8
You must enter <<FIELDS>>.
Eg: You must enter Hours Type.
Probable Cause
Timecard has one or more mandatory fields and user has not entered all the required fields.
Resolution
User must key in all the required fields. <<FIELDS>> in the error message are the mandatory
fields.
Issue #9
Submit Failed. Timecard cannot be found.
Save Failed. Timecard cannot be found.
Delete Failed. Timecard cannot be found.
Probable Cause
The administrator or user has deleted the specific timecard in Timestore, there is a discrepancy
in the data between the device and Timestore.
Resolution
Delete the timecard, logout and log in to continue working.
Issue #10
Timecard period does not match your setup. You must delete this timecard.
Probable Cause
User's SS timecard period was changed after a timecard was pending in Draft status in the
device.
Resolution
Delete the timecard in Draft status, logout and log in to continue working.

Issue #11
You cannot create this Time Entry.
Probable Cause
SS status allowing edit preference does not allow user to create this timecard.
Resolution
Adjust Future Number of days and Past number of days preference values.

OTL Mobile App PDF

Uploaded by

Copyright:

Available Formats

OTL Mobile App PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OTL Mobile App PDF

Uploaded by

Copyright:

Available Formats

Oracle Time and Labor

Configuring Timecards App

Version Date Comments

EBS Oracle Time and Labor Development

EBS Oracle Time and Labor Development

SSWA time entry VS Smartphone Time entry

Smartphone Time entry

EBS Oracle Time and Labor Development

PS: The week starts on Sunday

EBS Oracle Time and Labor Development

EBS Oracle Time and Labor Development

EBS Oracle Time and Labor Development

Time entry using Smartphone App

Time Entry Implementation

EBS Oracle Time and Labor Development

Non SSWA time entry and Timecards App

EBS Oracle Time and Labor Development

Using Timecards App

1. Mobile Framework Configuration

Mobile Framework Configuration:

EBS Oracle Time and Labor Development

EBS Oracle Time and Labor Development

EBS Oracle Time and Labor Development

Configuring Timecards App

EBS Oracle Time and Labor Development

EBS Oracle Time and Labor Development

Layout Components – Limitations and Restrictions

Package Choice Lists

EBS Oracle Time and Labor Development

EBS Oracle Time and Labor Development

Features in SSWA not available in Timecards App

Timecard Level Comments

Detail Level Comments

Absences/PTO Accrual region

Timecard Header level Message

Regular/Overtime Totals – Time category based Totals

EBS Oracle Time and Labor Development

Features not supported in Timecards App

Change and Late Audit

OTL Absences Integration

Quarterly/Half yearly/Yearly Time periods

EBS Oracle Time and Labor Development

Features with limitations

Time Entry Rules

Supported Application sets

EBS Oracle Time and Labor Development

Seeded Layouts ready for use in Timecards App

Using a custom Responsibility with Timecards App

Using a Custom Menu with Timecards App

EBS Oracle Time and Labor Development

Using a configured layout with Timecards App

Upgrading Self Service timecard Layouts involves the following steps.

Creating Value Sets for View Objects

BEGI N HXC_LAYOUT_COMPONENTS " Payr ol l Ti mecar d Layout - Cost Cent er "

EBS Oracle Time and Labor Development

SEQUENCE = " 210"

BEGI N HXC_LAYOUT_COMP_QUALI FI ERS " Pr oj ect s Ti mec ar d Layout - Pr oj ect "

2. Analyze the query for in your VO

EBS Oracle Time and Labor Development