Oracle时间卡配置指南

需积分: 10 109 浏览量更新于2024-08-02 收藏 535KB PDF 举报

"Oracle时间卡配置" Oracle Timecard Configuration主要涉及Oracle Time and Labor模块，这是一个用于管理企业员工工时和劳动的解决方案。此文档详细介绍了在构建自定义时间卡布局时，设计者可以使用的配置选项。Oracle Time and Labor允许通过修改AOL加载器文件并将其加载到数据库中来定制时间卡布局。 Oracle Time and Labor（OTL）是一个关键组件，它提供了全面的工时管理和劳动力跟踪功能。用户界面的配置是至关重要的，因为它直接影响到员工提交和管理者审批工时报告的体验。通过自定义时间卡布局，企业可以根据自身需求调整显示的信息、格式以及工作流程。文档的贡献者包括应用程序开发者、开发经理、功能分析师等，他们在文档中详细解释了如何使用OTL的配置工具。例如，Mark Stewart、Andrew Rundell、Joel Dupont、John Finnegan和Kris Van Der Pleog等人的贡献，确保了文档的准确性和实用性。文档的变更记录显示，随着时间的推移，文档进行了多次更新和改进。例如，2005年2月1日由Andrew Rundell将文档转换为PDF、WIKI和LaTeX格式，增加了可用性和可访问性；2007年8月6日，Amritha Nuthi对文档进行了更新，以反映包选择列表的正确功能；最后在2008年3月25日，Amritha Nuthi再次修改文档，仅展示交付的预设布局，并可能涉及到其他改进。在实际配置过程中，时间卡布局设计师可以定制的选项可能包括： 1. 布局结构：确定时间卡上各个部分的排列顺序，如日期、工作代码、小时数等。 2. 显示字段：选择哪些数据字段显示在时间卡上，如项目编号、任务描述、工作类型等。 3. 数据格式：设置日期、时间、数字等的显示格式。 4. 功能性选择：如启用或禁用某些特定功能，如自动计算、审批流等。 5. 审批规则：定义不同级别的审批流程，根据角色或部门设置不同的审批路径。 6. 语言和区域设置：支持多语言环境，适应全球化企业的需要。 7. 自定义逻辑：可能包括计算逻辑，例如根据工作小时数自动调整加班状态。 Oracle Timecard Configuration提供了强大的灵活性，允许企业根据其业务需求定制时间卡的各个方面，以优化工时管理和劳动力成本的控制。这不仅提高了员工提交工时的效率，也便于管理层进行有效的监控和决策。

1.4.5 Enterprise Asset Management

The enterprise asset management layouts delivered with the product are listed in table 5.

Layout Name Layout Code Layout Type Filename

EAM Conﬁrmation Layout EAM-CONFIRMATION CONFIRMATION eamhxclayt.ldt

EAM Review Layout EAM-REVIEW REVIEW eamhxclayre.ldt

EAM Timecard Layout EAM-TIMECARD TIMECARD eamhxclayco.ldt

Table 5: Enterprise Asset Management Layouts

1.4.6 Purchasing

The purchasing layouts delivered with the product are listed in table 6.

Layout Name Layout Code Layout Type Filename

Purchasing Timecard Layout PURCHASING-TIMECARD TIMECARD pozzhxclayt0054.ldt

Purchasing Review Time card Layout PURCHASING-REVIEW-TIMECARD REVIEW pozzhxclayt0055.ldt

Purchasing Conﬁrmation Timecard Layout PURCHASING-CONF-TIMECARD CONFIRMATION pozzhxclayt0056.ldt

Purchasing Notiﬁcation Timecard Layout PURCHASING-NOTIF-TIMECARD NOTIFICATION pozzhxclayt0057.ldt

Table 6: Purchasing Layouts

1.4.7 Projects-Purchasing

The projects-purchasing layouts delivered with the product are listed in table 7. Each of the layout names is prefaced with Projects-

Purchasing.

Layout Name Layout Code Layout Type Filename

Timecard Layout PROJECTS-PURCHASING-TIMECARD TIMECARD pazzhxclayt0039.ldt

Review Timecard Layout PROJECTS-PURCHASING-REVIEW REVIEW pazzhxclayt0040.ldt

Conﬁrmation Timecard Layout PROJECTS-PURCHASING-CONFIRM CONFIRMATION pazzhxclayt0041.ldt

Audit Entry Layout PA-PO-AUDIT AUDIT pazzhxclayt0042.ldt

CLA Review Layout PROJECTS-PURCHASING-CLA-REVIEW REVIEW pazzhxclayt0043.ldt

CLA Conﬁrmation PA-PO-CLA-CONFIRM CONFIRMATION pazzhxclayt0044.ldt

Table 7: Projects-Purchasing Layouts

2 Timecard Conﬁguration Basics

The fastest mechanism of conﬁguring a time card is to modify the existing set of layouts that are closest to the required functionality.

This white paper describes this process in detail, and illustrates with examples of common modiﬁcations. The document covers

the majority of customizations, which are to the timecard header — the comments ﬁeld, period list control and template control

widgets — and timecard matrix — the time attributes and time entry ﬁelds. In summary, the minimal number of steps to conﬁgure

a timecard layout are:

1. Use one of the seeded timecard layouts as a basis, or create a new timecard layout.

2. You must rename the timecard layout.

3. You conﬁgure the components of the timecard.

4. Upload the timecard layout to the database using FNDLOAD (see section 2.3).

NOTE: Do not use Web Application Dicti onary or the OA Conﬁguration Framework to conﬁgure the layouts.

However, there are items on the OTL timecard pages such as the product branding and buttons which are outside the scop e of the

conﬁgurable user interface. Thus use the personalization framework to modify to those user interface components, e.g. to change the

branding, or the labels on the buttons.

2.1 The Layout File

As previously mentioned, the timecard layout containing a set of user interface component, and associated qualifer descriptions, is

held in a simple text ﬁle. Use FNDLOAD, the generic AOL loader utility, to upload the ﬁle data into the OTL Conﬁgurable

User Interface database tables. Read the AOL documentation, within the Oracle Applications release 11i documentation, for more

information on FNDLOAD. In common with all FNDLOAD compatible ﬁles, OTL delivers a conﬁguration ﬁle, which deﬁnes the

structure of the layout ﬁles. This conﬁguration ﬁle deﬁnes the entities, and entity attributes that are present within the ﬁle, which

are in the form of name value pairs unless part of the developer key for the attribute. For example, the HXC LAYOUT entity has

two keys, the layout name, and the application short name that owns the layout (at the moment this is only OTL) and then a

number of attributes, such as the display layout name and the layout type. In OTL, each of the entities deﬁnied in the conﬁguration

ﬁle maps to an OTL table, e.g. the HXC LAYOUTS entity maps to the HXC LAYOUTS table. Each of the entity keys, or entity

attributes in the loader ﬁle maps directly or via a key to columns in those entities. E.g. DISPLAY LAYOUT NAME maps to the

database column, DISPLAY LAYOUT NAME, while PARENT COMPONENT maps to the column PARENT COMPONENT ID,

as the parent component speciﬁes a key attribute of an entity. The conﬁguration ﬁle is:

$APPL TOP/hxc/11.5/patch/115/import/hxclaytlayoutsld.lct

and must be used in conjunction with FNDLOAD when uploading the layout.

2.2 Using an Existing Layout as a Basis for Customization

When creating a custom layout the easiest approach is to select one the delivered layouts, based on which is closest to your require-

ments, and then use it as a starting point for your custom layout. To avoid overwriting the delivered OTL layouts you must give

your new timecard layouts new names. Even if you do not plan to use the delivered layouts this change should still be made to avoid

your custom layout being overwritten when OTL patches are applied to your environment. In order to rename the layout, you need

to change the layout name and description in the loader ﬁle. You do this in the section at the top of the data ﬁle.

For example:

BEGIN HXC LAYOUTS "EXCEPTION-TIMECARD" "HXC"

OWNER = "CUSTOM"

DISPLAY LAYOUT NAME = "Exception Layout - Timecard Entry Page"

LAYOUT TYPE = "TIMECARD"

Could be changed to:

BEGIN HXC LAYOUTS "MODIFIED-EXCEPTION-TIMECARD" "HXC"

OWNER = "CUSTOM"

DISPLAY LAYOUT NAME = "Modified Layout - Timecard Entry Page"

LAYOUT TYPE = "TIMECARD"

These changes must be made for any layout you are modifying, and it is also a good idea to change the ﬁlename of the loader ﬁle

to avoid confusion with the OTL delivered ﬁles.

2.3 Uploading Timecard Layouts

To upload the new layouts (for each of the layouts in the set you are using, or have customized) to the database execute the following

command from the command line:

FNDLOAD username/password@dbname 0 Y UPLOAD $HXC TOP/patch/115/import/hxclaytlayoutsld.lct ./layout.ldt

This command assumes the path environment variables are set correctly, so that the FNDLOAD executable lies on the path, and

the conﬁgured layout is in the current directory and in a ﬁle called layout.ldt.

Once the modiﬁed layout is successfully uploaded, it will be available in the OTL application Preferences form and you can give

it to a user, or groups of users as required.

2.4 Labels and Messages

There are two concepts used to store any text that is displayed on an OTL timecard screen - prompts and messages. In general, for

small amounts of text, use a prompt, otherwise use a message, which can be considerably more descriptive. For example, the tip at

the top of the timecard page is a me ss age, while the Project label in the timecard matrix is a prompt. All component prompts and

other items such as titles, button labels, etc. are deﬁned as prompts.

2.4.1 Labels

All labels in the OTL conﬁgurable UI are translatable and customizable via the AK Developer responsibility in Oracle Applications.

New labels can also be created in AK and used within the conﬁgurable UI for customized timecards. AK data for our purpose, is

deﬁned as a region containing one or more region items. For OTL, the region is just a ’container’ for all of the prompts - to see an

example of this you can review the region ’HXC CUI TIMECARD’ which contains most of the prompts for the timecard entry page

— see section 4. Each region item is based on an attribute, which are reusable, but for the purposes of OTL you will usually have

a one-to-one mapping between region items and attributes. When c reating region items there are many possible settings, but OTL

will only use a subset of these ﬁelds when querying labels - the ones used, and that should be set (other than mandatory ﬁelds such

as attribute name, application, length and sequence) are:

• Attribute Long Label (the text for the prompt)

• CSS Label Class Name (the CSS style name to be used for the prompt - this is optional and will b e defaulted if not speciﬁed)

When creating your own custom prompts you should take note of the attribute code (for the attribute referenced by your region

item), along with the region code and application you have created the region items under - this information will be needed to utilize

these labels within your conﬁgured timecard layout.

2.4.2 Messages

Messages in OTL use the standard Applications Object Library message functionality to provide a translatable and customizable

solution for longer sections of text. When creating messages you should note the message name you have speciﬁed, along with the

application name you have used.

剩余93页未读，继续阅读

hzzhai

粉丝: 0
资源: 1

Oracle时间卡配置指南

PyPI 官网下载 | Timecard-App-2.0.3.tar.gz

ECONZ Timecard-开源

中国石油大学(北京)克拉玛依校区在广东2021-2024各专业最低录取分数及位次表.pdf

浙江越秀外国语学院在广东2021-2024各专业最低录取分数及位次表.pdf

网站模板源代码（组件划分规范，二改省力）

华中科技大学 Java课程设计实验.zip

4G语音质差参数优化调整建议.xlsx

仲恺农业工程学院在广东2021-2024各专业最低录取分数及位次表.pdf

《Java语言程序设计（基础篇）》课后编程练习题.zip

电影订票后台系统（系分课程设计）.zip

最新资源