Skip to main content

Operating Unit vs Business Group

• With Multi-Org you can define an owning Operating Unit and associate this with a profile option -MO:Operating Unit. When you define data or execute a business process within Oracle Financial, then the system automatically attaches the id of your Operating Unit organization to the data or transaction.
• With Business Group security model in HRMS you can secure data and processes by id of the Business
Group.However, in HRMS, the Business Group id is closely related to the country of operation, and not simply a division or line of business.
• Both look the same but it is important to realize that these are distinct and different mechanisms for two different functional areas. This is especially true for any global implementation of HRMS where the data for each country exists within a single business group but Operating Units exist across many countries, and business groups.

Comments

  1. Can the above statements be explained via some example please ..This would really help us to understand the basic differences
    Please Sajid

    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