Scribd
Upload
44 views16 pages

OTL Self-Service Timecard Setup Guide

This whitepaper outlines a setup for Oracle Time and Labor (OTL) to enable self-service timecard entries for multiple assignments, including custom views and layout modifications. It addresses current limitations in OTL's functionality regarding multiple assignments and provides detailed steps for configuring the system. The document is intended for HR and IT professionals involved in implementing and managing OTL functionalities.

Uploaded by

Parag Bhasin
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
44 views16 pages

OTL Self-Service Timecard Setup Guide

This whitepaper outlines a setup for Oracle Time and Labor (OTL) to enable self-service timecard entries for multiple assignments, including custom views and layout modifications. It addresses current limitations in OTL's functionality regarding multiple assignments and provides detailed steps for configuring the system. The document is intended for HR and IT professionals involved in implementing and managing OTL functionalities.

Uploaded by

Parag Bhasin
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

ORACLE TIME AND LABOR

WHITEPAPER -
A SAMPLE SETUP TO:
ENABLE OTL SELF SERVICE
TIMECARD ENTRIES TO
MULTIPLE-ASSIGNMENT

Global HRMS Development

Creation Date: 29 - Mar - 2006


Last Updated: 10 - Apr - 2006
Version: DRAFT 1.0

Copyright (C) 2000 Oracle Corporation


All Rights Reserved
Copyright information

Oracle Time and Labor, Releases 11i and 12


Copyright 2000 Oracle Corporation
All rights reserved.

Creation Date: 29-Mar-06


Last Updated: 10-Apr-06

This software was not developed for use in any nuclear, aviation, mass transit, medical, or other
inherently dangerous applications. It is the customer's responsibility to take all appropriate
measures to ensure the safe use of such applications if the programs are used for such
purposes.
This software/documentation contains proprietary information of Oracle Corporation; it is
provided under a license agreement containing restrictions on use and disclosure and is also
protected by copyright law. Reverse engineering of the software is prohibited.
If this software/documentation is delivered to a U.S. Government Agency of the Department of
Defense, then it is delivered with Restricted Rights and the following legend is applicable:
Restricted Rights Legend Use, duplication, or disclosure by the
Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-
7013, Rights in Technical Data and Computer Software (October 1988).
Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.
If this software/documentation is delivered to a U.S. Government Agency is not for use within the
Department of Defense, then it is delivered with “Restricted Rights", as defined in FAR 52.227-
14, Rights in Data - General, including Alternate III (June 1987).
The information in this document is subject to change without notice. If you find any problems in
the documentation, please report them to us in writing. Oracle Corporation does not warrant that
this document is error
free. No part of this document may be reproduced or transmitted in any form or by any means
electronic or mechanical, for any purpose without the express written permission of Oracle
Corporation.
Oracle is a registered trademark and ConText, Enabling the Information Age, Oracle7, Oracle8,
Oracle8i, Oracle Access, Oracle Application Object Library, Oracle Financials, Oracle
Discoverer, Oracle Web Customers, Oracle Web Employees, Oracle Workflow, Oracle Work in
Process, PL/SQL, Pro*C, SmartClient, SQL*, SQL*Forms, SQL*Loader, SQL*Menu, SQL*Net,
SQL*Plus, and SQL*Report are trademarks or registered trademarks of Oracle Corporation.
All other products or company names are used for identification purposes only, and may be
trademarks of their respective owners.

2
Contents

Copyright information ..........................................................................................................................................2


Contents................................................................................................................................................................3
Introduction ..........................................................................................................................................................4
Audience...............................................................................................................................................................4
Prerequisite knowledge.........................................................................................................................................5
Problem statement ................................................................................................................................................5
Limitations when using Multiple Assignments in OTL .......................................................................................5
Sample OTL Setups for Assignment entries on the Timecard .............................................................................7
Step 1 – Create and enable the new Descriptive Flexfield Context / Segment as an OTL Mapping
Component....................................................................................................................................................7
Step 2 - Define the custom views used in the new layout ............................................................................8
Examples of Custom Views used in Sample layouts................................................................................8
Step 3 - Define the AK Attributes / Regions to display Column Headers on the New Layouts...................9
Step 4 - Define the New Layouts..................................................................................................................9
Examples of New Defined layout sections – New Name section and ‘Job’ sections Custom Views used
in sample layouts. ...................................................................................................................................10
NOTE - The following sections displayed are only a part of the entire layout (ldt) files, and display the
‘Job’ component. ....................................................................................................................................10
Timecard Layout.........................................................................................................................................10
Review Layout............................................................................................................................................11
Confirmation Layout ..................................................................................................................................11
Notification Layout.....................................................................................................................................12
Step 5 –Examples in the Application..........................................................................................................13
Timecard Entry – Jobs displayed are those associated with User’s Assignments. .....................................13
Review Page ...............................................................................................................................................13
Confirmation Layout ..................................................................................................................................15
What Approver sees in the ‘Mass Approval’ Page.....................................................................................15
What Approver sees in the ‘Workflow Notification’ Page ........................................................................16
BEE Entries after transfer from OTL to BEE.............................................................................................16

3
Introduction
This whitepaper provides an example of how to setup the OTL application to
allow assignment number entries on a self-service timecard. The examples
include custom views and self service layout files, to enable a worker to
enter assignment information on a timecard and transfer that time from OTL
to Batch Element Entry (BEE).

This document describes current OTL functionality using multiple


assignments on a resource. The OTL application intends to enhance
multiple assignment functionality at some future date to address the
limitations which have been outlined in this document.

This document covers:

1) Examples of modified OTL Self-Service Timecard, Review, Confirmation


and Notification layouts based on the delivered ‘Exception Layouts’

2) Examples of a Custom1VO and Custom2VO views used in the modified


timecard layouts. The custom views allow the worker and approver to
select the Job Description associated with their multiple assignment
values. The views are created as hxc_cui_custom1_v and
hxc_cui_custom2_v.

3) Examples of additional OTL Information Type Descriptive Flexfield


entries to store the Assignment ID

4) Examples of adding to the OTL Mapping Components and adding to the


delivered ‘BEE Retrieval Mapping’

5) Identifying the limitations in current OTL functionality as it relates to


HRMS Multiple Assignments

Audience
This document is intended for the following audience;

• Functional Consultants, HR and Payroll Professionals Note 1

• Technical Consultants, System Administrators and IT Professionals Note 2

Note 1: For defining OTL Users requiring timecards with Assignment entry fields,
and assigning OTL Preferences to those users.

Note 2: For defining the new OTL Layouts, loading them to the Oracle Instance,
Enabling custom views, and defining an additional OTL Information Type
Descriptive Flexfield’s Context and Segment.

4
Prerequisite knowledge
Knowledge to assign multiple assignments to one person is a pre-requisite.
The examples in this document use multiple assignments with different Job
Descriptions.

Problem statement
Organizations that use multiple assignments with their workers, want
workers’ time entries to reflect time worked against the various assignments.
The organization wants to enable a timecard that can capture the different
assignment information, displaying a meaningful assignment identifier for the
worker to select.

OTL provides the means to configure a timecard that allows a worker to


enter a meaningful value on the timecard that identifies one assignment
versus another, and transfer the time to Batch Element Entries (BEE).

This white paper provides an example of how the user can enter a value
associated with the worker’s different assignments (in this paper the value
displayed is the worker’s ‘Job’ associated with each defined assignment),
store the Assignment ID for the different entries, and then transfer the values
to BEE (and not to OTLR or Projects). The ‘Job’ example may be changed
to any meaningful value on the assignment, as long as the views created
reflect a unique assignment value.

NOTE - The entry and transfer of multiple assignment entries from OTL to
BEE has limitations and may not meet all organizations’ requirements.

Limitations when using Multiple Assignments in OTL

Current OTL Multiple Assignment functionality is limited within the following


parameters:

1. Assignment entries stored in the HXC schema, and transferred


directly from OTL to BEE.

2. Assignment entries will not transfer from OTL to OTLR (HXT


schema). Therefore, OTLR users may not enter multiple
assignments and expect the entries to transfer to OTLR than to
BEE.

3. Multiple Assignment entries will not affect the transfer of data to


Projects. Projects entries will transfer using the Primary
Assignment.

4. Choice Lists displayed on the Timecard along with Multiple


Assignment entry fields, will only consider the worker’s primary
assignment in defining Payroll Validation and HRMS ‘Link’ eligibility
(for example, if the worker is eligible to use elements on an
assignment other than their primary assignment, then the Payroll

5
validation will fail, since validation only considers primary
assignment)

Note – To enable restricted element lists dependent on the assignment


selected, or Payroll validation based on the assignment entries requires
the use of dependent list of values (LOV’s) and, or customized
validation routines, neither of which are described in this document.

5. OTL Preference evaluation is based on the worker’s primary


assignment, and not other defined assignments.

6. Timecard Validation is based on the Worker’s primary assignment,


no matter what value is selected for the assignment entry on the
timecard.

6
Sample OTL Setups for Assignment entries on the Timecard
OTL’s current functionality allows for the capture of various entries on the
self service timecard. OTL delivers functionality to add Mapping
Components and add the new Mapping Components to the BEE Retrieval
Mapping.

Step 1 – Create and enable the new Descriptive Flexfield Context / Segment as an OTL Mapping
Component

Define a New OTL Information Type Descriptive Flexfield Context /


Segment:

• Navigate to System Administration > Application > Flexfield >


Descriptive > Segments

• Query on Title = OTL Information Types

• Create a New Context / Segment value of:

o Context Code – ASSIGNMENT

o Segment - Assignment ID ( Attribute 1)

o Save, Freeze, and Re-compile the Flexfield

• Navigate to OTL Application Developer (responsibility used to


administer OTL – that includes the ‘Deposit / Retrieval Processes’
sub-menu > Processes and Reports)

• Run the ‘Generate Flexfield and Mapping Information’ Process

o Parameters – Delete Definitions = No

o Effective Date = ‘current date’

7
• Navigate to OTL Application Developer (responsibility used to
administer OTL – that includes the ‘Deposit / Retrieval Processes’
sub-menu > Deposit / Retrieval Process > Define Mapping
Components)

• Add the new Mapping Component

o Name = P_ASSIGNMENT_ID

o Field Name = P_ASSIGNMENT_ID

o Type = ASSIGNMENT

o Category (completed based on Type)

o Segment = Assignment ID

o Save

• Navigate to OTL Application Developer (responsibility used to


administer OTL – that includes the ‘Deposit / Retrieval Processes’
sub-menu > Deposit / Retrieval Process > Define Mapping)

• Query Name = ‘BEE Retrieval Process Mapping’

• Add Component Name = P_ASSIGNMENT_ID

• Save

Step 2 - Define the custom views used in the new layout

• Create 2 views (using custom view numbers not previously defined,


e.g., hxc_cui_custom1_v for Custom1VO and hxc_cui_custom2_v
for Custom2VO if not previously defined and used in other layouts)

• The hxc_cui_custom1_v is used on the timecard, and limits the list


of Jobs that may be selected to those associated with the User’s
assignment(s).

• The hxc_cui_custom2_v is used on the Review, Confirmation and


Notification pages, so that the Approver will see the Job
(assignment) selection, and to not limit the displayed value based on
the User (who in the approval’s case is the Approver).

Examples of Custom Views used in Sample layouts

8
create or replace view hxc_cui_custom1_v as
select [Link] display_value, paaf.assignment_id value
from per_all_assignments_f paaf,
fnd_user fu,
per_jobs pj
where paaf.person_id = fu.EMPLOYEE_ID
and paaf.job_id = pj.job_id
and fu.user_id = fnd_profile.value ('USER_ID')

Note – The sample for hxc_cui_custom1_v is written to limit the list of displayed Job’s
based on the Workers’ assignments.

create or replace view hxc_cui_custom2_v


(display_value, value)
as
(select [Link],
paaf.assignment_id
from per_all_assignments_f paaf,
per_jobs_tl pjt
where paaf.job_id = pjt.job_id )

Note – The sample for hxc_cui_custom2_v is written to display the jobs associated with
assignments that were entered on the timecard. The view is not limited based on the
user viewing the timecard (the Approver). This view is used on the view only pages e.g.,
Review, Confirmation and Notification pages. The timecard assignment id entries bind
to the review pages view, displaying the correct Job value.

Step 3 - Define the AK Attributes / Regions to display Column Headers on the New Layouts

Create the new ‘AK’ Common Module Attributes associated to either a new
Region or on an existing OTL Region. Attributes are defined based on the
OTL Configuration Whitepaper (Metalink note - 304340.1)

NOTE – you should use a new Region to ensure your company defined
Attribute / Regions are not affected by future Oracle patches.

Step 4 - Define the New Layouts

The various layout example sections listed below were added to a copy of
the delivered ‘Exception Layouts’ layout set. The sample code has specific
entries highlighted to emphasize the specific lines / entry.

The examples of layout code were added to copies of the delivered


‘Exception Layout’, renaming the layout, and adding the example sections
before the ‘Cost Segment’ code section.

Create 4 layouts using the OTL Configuration Whitepaper as your guide.

9
• Timecard layout – Sample Uses Custom1VO to restrict the list of
available Assignment values based on the worker associated to the
User Login.

• Review Layout – Sample uses Custom2VO to not restrict the


assignments displayed, so that the Approver will see the assignment
entries selected (not limited based on User Login)

• Confirmation Layout - Sample uses Custom2VO to not restrict the


assignments displayed, so that the Approver will see the assignment
entries selected (not limited based on User Login)

• Notification - Sample uses Custom2VO to not restrict the


assignments displayed, so that the Approver will see the assignment
entries selected (not limited based on User Login)

• Others – if used by your organization

Examples of New Defined layout sections – New Name section and ‘Job’ sections
Custom Views used in sample layouts.

NOTE - The following sections displayed are only a part of the entire layout (ldt) files,
and display the ‘Job’ component.

Timecard Layout
LDRCONFIG = "[Link] 115.7"
.
.

BEGIN HXC_LAYOUTS "MA-EXCEPTION-TIMECARD" "HXC"


OWNER = "ORACLE"
DISPLAY_LAYOUT_NAME = "MA-Exception Layout - Timecard Entry Page"
LAYOUT_TYPE = "TIMECARD"
TOP_LEVEL_REGION_CODE = "HXCCONFIGTESTCUI"
LAST_UPDATE_DATE = "2004/05/23"
.
.
.
BEGIN HXC_LAYOUT_COMPONENTS "MA-Exception Timecard Layout - Job"
OWNER = "ORACLE"
COMPONENT_VALUE = "JOB"
REGION_CODE = "HXC_CUI_TIMECARD"
REGION_CODE_APP_SHORT_NAME = "HXC"
ATTRIBUTE_CODE = "HXC_TIMECARD_M_ASG"
ATTRIBUTE_CODE_APP_SHORT_NAME = "HXC"
SEQUENCE = "205"
COMPONENT_DEFINITION = "CHOICE_LIST"
RENDER_TYPE = "WEB"
PARENT_COMPONENT =
"MA-Exception Timecard Layout - Day Scope Building blocks for worker timecard matrix"
LAST_UPDATE_DATE = "2004/05/23"

BEGIN HXC_LAYOUT_COMP_QUALIFIERS "MA-Exception Timecard Layout - Job"


OWNER = "ORACLE"
QUALIFIER_ATTRIBUTE_CATEGORY = "CHOICE_LIST"
QUALIFIER_ATTRIBUTE1 = "Custom1VO"
QUALIFIER_ATTRIBUTE4 = "N"
QUALIFIER_ATTRIBUTE8 = "DisplayValue"
QUALIFIER_ATTRIBUTE9 = "Value"
QUALIFIER_ATTRIBUTE10 =
"[Link].Custom1VO"
# QUALIFIER_ATTRIBUTE11 = "TIMECARD_BIND_END_DATE|TIMECARD_BIND_END_DATE"
# Qualifier Attribute 11 is commented out because the custom choice list does not use a bind variable
10
QUALIFIER_ATTRIBUTE17 = "OraTableCellText"
QUALIFIER_ATTRIBUTE20 = "N"
QUALIFIER_ATTRIBUTE21 = "Y"
QUALIFIER_ATTRIBUTE22 = "L"
QUALIFIER_ATTRIBUTE25 = "FLEX"
QUALIFIER_ATTRIBUTE26 = "ASSIGNMENT"
QUALIFIER_ATTRIBUTE27 = "Attribute1"
LAST_UPDATE_DATE = "2004/05/23"
END HXC_LAYOUT_COMP_QUALIFIERS

END HXC_LAYOUT_COMPONENTS

Review Layout

LDRCONFIG = "[Link] 115.3"

BEGIN HXC_LAYOUTS "MA-EXCEPTION-REVIEW" "HXC"


OWNER = "ORACLE"
DISPLAY_LAYOUT_NAME = "MA-Exception Layout - Timecard Review Page"
LAYOUT_TYPE = "REVIEW"
TOP_LEVEL_REGION_CODE = "HXCCONFIGTESTCUI"
LAST_UPDATE_DATE = "2004/05/24"

BEGIN HXC_LAYOUT_COMPONENTS "MA-Exception Review Layout - Job"


OWNER = "ORACLE"
COMPONENT_VALUE = "JOB"
REGION_CODE = "HXC_CUI_TIMECARD"
REGION_CODE_APP_SHORT_NAME = "HXC"
ATTRIBUTE_CODE = "HXC_TIMECARD_M_ASG"
ATTRIBUTE_CODE_APP_SHORT_NAME = "HXC"
SEQUENCE = "168"
COMPONENT_DEFINITION = "CHOICE_LIST"
RENDER_TYPE = "WEB"
PARENT_COMPONENT =
"MA-Exception Review Layout - Day building blocks - matrix layout"
LAST_UPDATE_DATE = "2004/05/24"

BEGIN HXC_LAYOUT_COMP_QUALIFIERS "MA-Exception Review Layout - Job"


OWNER = "ORACLE"
QUALIFIER_ATTRIBUTE_CATEGORY = "CHOICE_LIST"
QUALIFIER_ATTRIBUTE1 = "Custom2VO"
QUALIFIER_ATTRIBUTE8 = "DisplayValue"
QUALIFIER_ATTRIBUTE9 = "Value#NUMBER"
QUALIFIER_ATTRIBUTE10 =
"[Link].Custom2VO"

QUALIFIER_ATTRIBUTE17 = "OraTableCellText"
QUALIFIER_ATTRIBUTE20 = "N"
QUALIFIER_ATTRIBUTE21 = "Y"
QUALIFIER_ATTRIBUTE22 = "L"
QUALIFIER_ATTRIBUTE25 = "FLEX"
QUALIFIER_ATTRIBUTE26 = "ASSIGNMENT"
QUALIFIER_ATTRIBUTE27 = "Attribute1"
QUALIFIER_ATTRIBUTE30 = "Y"
LAST_UPDATE_DATE = "2004/05/24"
END HXC_LAYOUT_COMP_QUALIFIERS

END HXC_LAYOUT_COMPONENTS

Confirmation Layout

LDRCONFIG = "[Link] 115.7"

11
BEGIN HXC_LAYOUTS "MA-EXCEPTION-CONFIRMATION" "HXC"
OWNER = "ORACLE"
DISPLAY_LAYOUT_NAME = "MA-Excptn Layout - Timecard Confirmation Page"
LAYOUT_TYPE = "CONFIRMATION"
TOP_LEVEL_REGION_CODE = "HXCCONFIGTESTCUI"

BEGIN HXC_LAYOUT_COMPONENTS "MA-Excptn Confirmation Layout - Job"


OWNER = "ORACLE"
COMPONENT_VALUE = "JOB"
REGION_CODE = "HXC_CUI_TIMECARD"
REGION_CODE_APP_SHORT_NAME = "HXC"
ATTRIBUTE_CODE = "HXC_TIMECARD_M_ASG"
ATTRIBUTE_CODE_APP_SHORT_NAME = "HXC"
SEQUENCE = "218"
COMPONENT_DEFINITION = "CHOICE_LIST"
RENDER_TYPE = "WEB"
PARENT_COMPONENT =
"MA-Excptn Confirmation Layout - Day Scope Building blocks for worker timecard matrix"
LAST_UPDATE_DATE = "2004/05/23"

BEGIN HXC_LAYOUT_COMP_QUALIFIERS
"MA-Excptn Confirmation Layout - Job"
OWNER = "ORACLE"
QUALIFIER_ATTRIBUTE_CATEGORY = "CHOICE_LIST"
QUALIFIER_ATTRIBUTE1 = "Custom2VO"
QUALIFIER_ATTRIBUTE8 = "DisplayValue"
QUALIFIER_ATTRIBUTE9 = "Value#NUMBER"
QUALIFIER_ATTRIBUTE10 =
"[Link].Custom2VO"

QUALIFIER_ATTRIBUTE17 = "OraTableCellText"
QUALIFIER_ATTRIBUTE20 = "N"
QUALIFIER_ATTRIBUTE21 = "Y"
QUALIFIER_ATTRIBUTE22 = "L"
QUALIFIER_ATTRIBUTE25 = "FLEX"
QUALIFIER_ATTRIBUTE26 = "ASSIGNMENT"
QUALIFIER_ATTRIBUTE27 = "Attribute1"
QUALIFIER_ATTRIBUTE30 = "Y"
LAST_UPDATE_DATE = "2004/05/23"
END HXC_LAYOUT_COMP_QUALIFIERS

END HXC_LAYOUT_COMPONENTS

Notification Layout

LDRCONFIG = "[Link] 115.7"

BEGIN HXC_LAYOUTS "MA-EXCEPTION-NOTIFICATION" "HXC"


OWNER = "ORACLE"
DISPLAY_LAYOUT_NAME = "MA-Excptn Layout - Timecard Notification Page"
LAYOUT_TYPE = "NOTIFICATION"
TOP_LEVEL_REGION_CODE = "HXCCONFIGTESTCUI"
LAST_UPDATE_DATE = "2004/05/24"

BEGIN HXC_LAYOUT_COMPONENTS "MA-Excptn Notification Layout - Job"


OWNER = "ORACLE"
COMPONENT_VALUE = "JOB"
REGION_CODE = "HXC_CUI_TIMECARD"
REGION_CODE_APP_SHORT_NAME = "HXC"
ATTRIBUTE_CODE = "HXC_TIMECARD_M_ASG"
ATTRIBUTE_CODE_APP_SHORT_NAME = "HXC"
SEQUENCE = "168"
12
COMPONENT_DEFINITION = "CHOICE_LIST"
RENDER_TYPE = "WEB"
PARENT_COMPONENT =
"MA-Excptn Notification Layout - Day building blocks - matrix layout"
LAST_UPDATE_DATE = "2004/05/24"

BEGIN HXC_LAYOUT_COMP_QUALIFIERS
"MA-Excptn Notification Layout - Job"
OWNER = "ORACLE"
QUALIFIER_ATTRIBUTE_CATEGORY = "CHOICE_LIST"
QUALIFIER_ATTRIBUTE1 = "Custom2VO"
QUALIFIER_ATTRIBUTE8 = "DisplayValue"
QUALIFIER_ATTRIBUTE9 = "Value#NUMBER"
QUALIFIER_ATTRIBUTE10 =
"[Link].Custom2VO"

QUALIFIER_ATTRIBUTE17 = "OraTableCellText"
QUALIFIER_ATTRIBUTE20 = "N"
QUALIFIER_ATTRIBUTE21 = "Y"
QUALIFIER_ATTRIBUTE22 = "L"
QUALIFIER_ATTRIBUTE25 = "FLEX"
QUALIFIER_ATTRIBUTE26 = "ASSIGNMENT"
QUALIFIER_ATTRIBUTE27 = "Attribute1"
QUALIFIER_ATTRIBUTE30 = "Y"
LAST_UPDATE_DATE = "2004/05/24"
END HXC_LAYOUT_COMP_QUALIFIERS

END HXC_LAYOUT_COMPONENTS

Step 5 –Examples in the Application

Timecard Entry – Jobs displayed are those associated with User’s Assignments.

Review Page

13
14
Confirmation Layout

What Approver sees in the ‘Mass Approval’ Page

15
What Approver sees in the ‘Workflow Notification’ Page

BEE Entries after transfer from OTL to BEE

Note – The Values entered on May 15 and May 16 (values 5.15 and 5.16) had either no Job value
entered, or used the job associated with the (-1) assignment. When no Job (assignment override) is
entered, the default assignment is applied.

16

Common questions

Powered by AI

Custom views in OTL, such as Custom1VO and Custom2VO, enhance timecard functionality by allowing workers and approvers to select job descriptions associated with multiple assignment values. Custom1VO limits the job list to those linked with the user's assignments for timecard entries, ensuring relevant data capture. Custom2VO, used for review, confirmation, and notification pages, displays jobs for all assignments, promoting a comprehensive view of submitted entries for approvers. This setup allows flexibility in displaying relevant job information, streamlining the review and approval processes .

The use of choice lists on timecards that rely on primary assignments impacts payroll validation and HRMS functionality since they restrict the validation to primary assignment-related data. This means that if an employee is eligible for other elements beyond their primary assignment, those elements would fail validation. Consequently, organizations may face challenges in accurately capturing all necessary payroll data and managing comprehensive HR functions without additional customization. This constraint necessitates using custom views or validation routines to achieve desired validation and reporting outcomes effectively, potentially complicating system management .

The design of timecard layouts utilizing Custom1VO and Custom2VO views supports multi-assignment functionality by allowing specific and flexible job entry and approval processes. Custom1VO enables restriction of job selection on timecards to only those relevant to the user's assignments, promoting accuracy in time reporting. Custom2VO offers a comprehensive review and confirmation process by allowing approvers to see all job assignments selected, regardless of user assignment limits, facilitating a complete oversight of submitted data before approval. These custom views enhance the system's ability to manage multiple assignments, crucial for organizations with diverse employee roles and ensuring accurate data transfer to BEE .

Current OTL multiple assignment functionality is limited because assignment entries stored in the HXC schema are transferred directly from OTL to BEE but not to OTLR, meaning users cannot expect multiple assignment entries to move from OTL to OTLR or beyond to BEE. Additionally, data transfer to Projects is limited to the primary assignment, and choice lists on timecards are also restricted to primary assignment for payroll validation, impacting users attempting to utilize multiple assignments for elaborate payroll and HRMS functionalities .

Using descriptive flexfields as OTL mapping components involves creating a new context or segment that aids in capturing multiple assignment entries on timecards. This setup is crucial for reflecting meaningful assignment identifiers for workers, which affects how data is transferred to BEE. Descriptive flexfields serve as the basis for new mapping components and require precise configuration, such as defining context codes and recompiling flexfields. Proper implementation ensures accurate timecard and BEE data reflection, which is essential for accurate payroll and project accounting .

Organizations need to consider several limitations when implementing OTL multiple assignments, including the restriction that choice lists and payroll validation rely solely on the primary assignment. This affects eligibility for certain elements if an employee's non-primary assignment is needed. Also, OTL does not support transferring multiple assignment data to OTLR, leading to potential issues if those systems need to interact. Moreover, the transfer of data to Projects is only based on the primary assignment, which may not always align with the organization’s operational needs .

The configuration process of new descriptive flexfields as OTL Mapping Components is intricately aligned with capturing assignment entries on a timecard by defining new flexfields that record specific assignment identifiers. This involves creating a new context/segment and mapping it to timecard components such as Assignment ID, which ensures that multiple assignment data is captured correctly and reflects the correct assignments in BEE. The process requires strategic planning and precise execution to ensure the configuration accurately meets the organization's data entry and reporting needs .

The use of multiple assignments in OTL allows for capturing time entries that reflect time worked against various assignments, which can then be transferred to BEE. However, it introduces limitations such as the inability to transfer entries to OTLR (OTL entries are transferred directly to BEE) and affecting the transfer of data to Projects where only the primary assignment is considered. This impacts BEE as the entries must be specifically tailored to support these limitations, often requiring additional configuration like specific list of values for payroll validation which only considers primary assignment .

AK attributes and regions play a significant role in customizing new layouts in OTL by providing additional modular elements that can be tailored to specific business requirements. These attributes enable the creation of new, distinct layout regions that enhance system flexibility, as they can be adjusted independently of future Oracle patches. By carefully defining and associating AK attributes with new regions, organizations can ensure that custom business logic and user requirements are embedded in the timecard and approval processes, thereby creating a more controlled and adaptable OTL environment .

Organizations can benefit from modifying the delivered 'Exception Layouts' in OTL by tailoring these layouts to incorporate specific assignment values and job descriptions that address their unique business requirements. By customizing these layouts, organizations can enhance data entry accuracy and reporting capabilities on timecards, leading to more efficient payroll and HR management. This adaptability allows for the inclusion of useful features such as new AK attributes or custom decision-related fields, optimizing the user's experience and streamlining workflows in accordance with organizational protocols .

You might also like