Oracle HCM Tutorials

This blog is the next part of my previous one which was Business Groups in HRMS Business Group is part of MultiOrg model of Organizations The Multi-Org model provides a four level hierarchy that dictates how transactions flow through different business units and how those business units interact • Set of Books- GL- Balancing Entities/Funds • Business Group • Legal Entity -HR- Fin- Legislative Reporting • Balancing Entity • Operating Unit- AP, AR, PO, OE -Bal Segment 1, Bal Segment 2,Bal Segment 3 • Inventory Org MFG, INV, Ship There is one confusion between Oracle Financial and HRMS consultant, as they simply assume SOB is more meant for non HRMS module and BG is more for HRMS, in certain extend this is true.Lets investigate this on GRE\LE and OU as follows: Know something more for SOB • As covered in earlier post ,a set of books is a financial reporting entity that shares the three C’s that is Chart of accounts(accounting flexfield structure), functional currenc...

A business group is a basically Human Resources organization to which you assign employees. You assign each operating unit to a business group in the financial options setup. You can assign the same business group to different operating units including to operating units in different financial sets of books. You can setup a separate business group for each operating unit if you want to segregate and maintain each group of employees separately. Oracle provides one setup business group you can use. In case of not having HRMS (Full mode),what you have to do is ,to create at least one business group to cater requirement for Oracle Financials and Manufacturing, so that only the employees can perform some of application functionality , which are as follows: • Entry and approvals of purchase orders and requisitions require requisitioners, buyers, and approvers to be setup as employees. • Purchasing receiving staff must be setup as employees in order to use receiving screens. • Engine...

Very common thing, people get confuse why such type of naming convention oracle have used. Here is note for some of them: _ALL: Table holds all the information about different operating units. Multi-Org environment. You can also set the client info to specific operating unit to see the data specific to that operating unit only. _TL: are tables corresponding to another table with the same name minus the _TL. These tables provide multiple language support. For each item in the table without _TL there can be many rows in the _TL table, but all with different values in the LANGUAGE column. _B: these are the BASE tables. They are very important and the data is stored in the table with all validations. It is supposed that these tables will always contain the perfect format data. If anything happens to the BASE table data, then it is a data corruption issue. _F: these are date tracked tables, which occur in HR and Payroll. For these there are two date columns EFFECTIVE_START...

What are Shared Entities? Shared entities in the 11i eBusiness Suite allow the one-time definition of an object, and the use of that object across several products. Shared entities are "owned" by a single product for table purposes only. It does not designate the primary user or decision maker. eBusiness Shared Entity Examples Entity Description AOL Application Object Library Organizations Logical unit entities Locations Business sites (addresses) Employees Personnel who perform assigned tasks Sales Force Individuals credited with sales revenue Customers Buyers of the end product Suppliers Vendors we buy from Items Raw Materials, finished goods or services Unit of Measure ...

Self Service HR 1. Employee Self Service a. Personal Information i. Basic Personal Details ii. Address iii. Other Addresses iv. Phone number v. Dependents and benefits vi. Emergency Contacts b. Professional Details i. Education and Qualification ii. Other professional awards iii.Competency profile v. Resume c. My Information d. Appraisals e. Special Information f. Extra information g. Leave of Absence h. Payslip i. Manage payroll payments In the next blog , I will write about Manager Self Service functionality

OTL Processing, From Timecard to Batch Element for Payroll The purpose of this document is to provide users an overview of the OTL process flows and how the order of processing could impact payroll processing. This document highlights the tables that are impacted as time is entered in OTL and progressed to the batch element entry for payroll. This is a case history study that highlights issues uncovered due to incorrect process steps and two current bugs being worked on by Oracle Development. Issues highlighted in this document: 1. Overtime rules were not applied during the transfer of Retro batches (Transfer Time from OTL to BEE). In this issue any time interfaced to the professional timecard as ‘retro’ did not calculate overtime. Reference bug 3457385 where retro batches are not calculating overtime. Patch has just become available (April- 2004), depending on the HXT release you are on. Patch 3517194 for HXT.F, patch 3507727 for HXT.F.1 and patch 3385080 for HXT.G. 2. Time was double...