Skip to main content

Business Groups in HRMS

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.
• Engineering change order approver lists use the employee database to validate approvers.
• AP expense report features allow you to create suppliers from employee information and to generate expense report coding using employee default account numbers.
• iExpense requires users who enter or approve expense reports to be setup as employees.
• Fixed Assets allows you to optionally assign assets to employees for tracking purposes.
• Standard Workflow approvals of GL journal entries in Release 11 require approvers to be setup as employees.
• Standard Workflow approvals of AR credit memos in Release 11i require approvers to be setup as employees.
• AP may add invoice approval through AME , which will likely require approvers to be setup as employees.
There are few exceptions, where you have to understand when your installation site is having HR and Projects modules installed, as there are significant implications of business group and HR organizations.

In the next blog I will define that Business Group is part of MultiOrg model.

Comments

  1. Your article has beneficial for me, because i am also HRMS trainee, wish you all the best,,,

    ReplyDelete

Post a Comment

Popular posts from this blog

Oracle Payroll R12 - Payroll Processing 1

Hi , This is the last part of Payroll Tutorial, In this video , we will see how payroll process for an individual person through Quick Pay and how Payroll process for all Employees through Payroll Run Process and Prepayments process for payment distribution. In the next tutorial we will see more processes in detail for complete payroll processing.

Oracle Payroll R12 - Salary Basis

Hi All, This is the 3rd part of Oracle Payroll Tutorial , Salary Basis is the main Salary Component of Salary Structure. The Other Salary Components are driven by this components. So Ideally there should be one or two Salary Components.You can not attach multiple salary basis to single assignment of the employee. Kindly send your feed back.

Oracle Time and Labour

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