Oracle Human Resources Consulting

OTL Timecard Customization

2010-05-12T05:25:00.000-07:00

For customizing the OTL timecard:
1) Choose the seeded Oracle timecard layout closest to your requirements. The file is on the server path: $HXC_TOP/patch/115/import/hxclaytlayoutsld.ldt
2) Copy the file and rename it (so that the original file is kept intact).
3) Change the following regin in the file and save it:
     BEGIN HXC_LAYOUTS "XXAHM-PAYROLL-TIMECARD" "HXC"
     OWNER = "AHMAD"
     DISPLAY_LAYOUT_NAME = "AHMAD Payroll Timecard Layout"
     LAYOUT_TYPE = "TIMECARD"
     TOP_LEVEL_REGION_CODE = "HXCCONFIGTESTCUI"
     LAST_UPDATE_DATE = "2010/05/12"
4) Comment any fields you do not want to appear in the Timecard by prefixing the lines with #. for example:
      #BEGIN HXC_LAYOUT_COMPONENTS "Payroll Timecard Layout - Start Time Label"
# OWNER = "ORACLE"
# REGION_CODE = "HXC_CUI_TIMECARD"
# REGION_CODE_APP_SHORT_NAME = "HXC"
# ATTRIBUTE_CODE = "HXC_TIMECARD_STARTTIME"
# ATTRIBUTE_CODE_APP_SHORT_NAME = "HXC"
# SEQUENCE = "210"
# COMPONENT_DEFINITION = "DISPLAY_LABEL"
# RENDER_TYPE = "WEB"
# PARENT_COMPONENT = "Payroll Timecard Layout - Table Layout Component"
# LAST_UPDATE_DATE = "2004/05/24"
#
#
# BEGIN HXC_LAYOUT_COMP_QUALIFIERS
# "Payroll Timecard Layout - Start Time Label"
# OWNER = "ORACLE"
# QUALIFIER_ATTRIBUTE_CATEGORY = "DISPLAY_LABEL"
# QUALIFIER_ATTRIBUTE18 = "EXCLUDE"
# QUALIFIER_ATTRIBUTE19 = "|CSV|"
# QUALIFIER_ATTRIBUTE20 = "N"
# LAST_UPDATE_DATE = "2004/05/24"
# END HXC_LAYOUT_COMP_QUALIFIERS
#
# END HXC_LAYOUT_COMPONENTS
#
# BEGIN HXC_LAYOUT_COMPONENTS "Payroll Timecard Layout - Start Time Field"
# OWNER = "ORACLE"
# REGION_CODE = "HXC_CUI_TIMECARD"
# REGION_CODE_APP_SHORT_NAME = "HXC"
# ATTRIBUTE_CODE = "HXC_TIMECARD_STARTTIME"
# ATTRIBUTE_CODE_APP_SHORT_NAME = "HXC"
# SEQUENCE = "220"
# COMPONENT_DEFINITION = "TEXT_FIELD"
# RENDER_TYPE = "WEB"
# PARENT_COMPONENT = "Payroll Timecard Layout - Table Layout Component"
# LAST_UPDATE_DATE = "2004/05/24"
#
#
# BEGIN HXC_LAYOUT_COMP_QUALIFIERS
# "Payroll Timecard Layout - Start Time Field"
# OWNER = "ORACLE"
# QUALIFIER_ATTRIBUTE_CATEGORY = "TEXT_FIELD"
# QUALIFIER_ATTRIBUTE1 = "N"
# QUALIFIER_ATTRIBUTE2 = "Y"
# QUALIFIER_ATTRIBUTE3 = "8"
# QUALIFIER_ATTRIBUTE4 = "1"
# QUALIFIER_ATTRIBUTE5 = "8"
# QUALIFIER_ATTRIBUTE7 = "OraTableCellText"
# QUALIFIER_ATTRIBUTE20 = "N"
# QUALIFIER_ATTRIBUTE21 = "N"
# QUALIFIER_ATTRIBUTE25 = "TIME_BUILDING_BLOCK_ATTRIBUTE"
# QUALIFIER_ATTRIBUTE27 = "StartTime"
# QUALIFIER_ATTRIBUTE28 = "StartTime"
# LAST_UPDATE_DATE = "2004/05/24"
# END HXC_LAYOUT_COMP_QUALIFIERS
#
# END HXC_LAYOUT_COMPONENTS

Note: commenting the previous code hides the OTL timecard Start time field.

5) FTP the file on the server with the FND command:
     FNDLOAD apps/apps@test 0 Y UPLOAD $HXC_TOP/patch/115/import/hxclaytlayoutsld.lct      XXAHM_hxczzhxclayt0000.ldt
6) Add the timecard to your OTL preferences and preview the new customization.

Using Salary Management

2010-05-10T10:39:00.000-07:00

Lots of people ask, what if we did not use the seeded oracle feature of Salary Management. Well, the impact will be the following:

1) Salary Administration tracks salary changes. That is, if we create an element, then we have to take care of updating the entry whenever a salary increase occurs; while in Salary administration, Oracle takes care of the history.
2) Salary changes can pass through an approval process (not automatically approved).
3) Salary administration automatically create a Basic Salary element (that one linked in salary basis) with the value.
4) The original Basic salary value will always be there, so if we use an element, then no need to define an input value to capture the original value, and another for the prorated (or paid) value.

Differences between HR:Security Profile & MO:Security Profile

2010-05-03T15:51:00.000-07:00

HR:Security Profile and MO:Security Profile are used for MOAC (Multi-Org-Access-Control).

HR:Security Profile is used to restrict the data in Human Resources according to the Business Group or whatever criteria you define in this security profile. Thus, for HR, it uses this secuity profile in its data exposure to the user.

MO:Security Profile acts the same but is used for Financials and Manufacturing applications. It restricts the access (site level or can be set at responsibility level) to certain operating unit (or whatever criteria defined in the security profile).

If there is no value at MO:Security Profile, then Financials and Manufacturing use the HR:Security Profile option for their data exposure to users.

HRMS Functional Consultant Tasks

2009-06-01T15:50:00.000-07:00

To summarize the main tasks an HRMS functional consultant performs in his/her career:

Gathers Data (Business) from customer or client (Scoping)
Carries out CRP's
Identifies any gaps between the existing business and the application
Proposes for a new business scenario if applicable
Delivers all project documentation and deliverables as appropriate