This document provides a training guide for using the Oracle EBS R12 Human Resources system. It covers topics such as starting Oracle applications, choosing a responsibility, navigating forms, getting help, and the core HR functionality including entering employee data, recruitment, defining work structures, and administration settings. The guide is intended to help FUJCCI HR staff learn the essential functionality of Oracle HRMS. It provides step-by-step instructions on common HR tasks in Oracle such as hiring, promotions, payroll, and system configuration.
This document provides an overview of Oracle Assets management and outlines the steps to set up Oracle Fixed Assets, including:
1. Creating an assets responsibility and assigning it to the IVAS11 user for setup
2. Defining profile values such as the GL ledger set and operating unit for the IVAS purchasing responsibility
3. Setting the GL ledger name profile option to 'ivas ledger' at the responsibility level for the IVAS_FixedAssets responsibility
Oracle Inventory is an enterprise application that enables companies to define part numbers, model organization structures, track perpetual inventory, maintain accurate inventory balances, plan material replenishments, and forecast demand. It provides flexfields for items, item catalogs, item categories, stock locators, account aliases, and sales orders. Key steps in implementation include designing flexfield structures, defining item categories and category sets, and assigning items to categories.
This document summarizes a presentation on cost accounting enhancements in Oracle E-Business Suite Release 12, including the transition from Material Accounting Components (MAC) to Subledger Accounting (SLA) for process costing. Key points include increased flexibility in discrete costing using SLA, mapping of process costing transactions and setup between MAC and SLA, an example of tracking purchase price variances by product line using either mapping sets or category accounting, and notes on discrete inventory period close and upgrade processes in R12.
Blanket purchase agreement and blanket release in oracle r12G Madhusudhan
Blanket purchase agreements and releases allow negotiating long-term supplier contracts while maintaining flexible delivery schedules. A blanket purchase agreement specifies negotiated item prices before actual purchasing. A blanket release is an actual order issued against the agreement, using the agreement's prices. Notifications can be set to alert about blanket agreement utilization and expiration.
The document discusses various topics related to fixed assets in Oracle Applications including:
1. There are three ways to add assets: quick additions, detail additions, and mass additions.
2. Depreciation is calculated by running the depreciation program for each book. This updates expense, accumulated depreciation, and other values.
3. Asset books are used to define depreciation rules and generate journal entries. The main types are corporate, tax, and budget books.
1) The document outlines the steps to configure Oracle Approvals Management (AME) for leave of absence (LOA) approvals in Oracle Self Service Human Resources (SSHR) Release 12. This involves creating an AME condition and rule to require approval from an employee's direct supervisor for LOA requests.
2) Key parameters for the AME setup include using the LOA transaction type, HR_IS_LEAVE_OF_ABSENCE_SS condition, and an approval action to require approvals up to the first supervisor.
3) Testing confirms that a new LOA request in SSHR routes to the employee's supervisor for approval, demonstrating that AME for LOA approvals has been successfully
This document provides steps to configure Landed Cost Management (LCM) in Oracle EBS R12.1.3. The steps include: applying required patches; creating new account codes for LCM; defining cost factors; defining LCM shipment types, organizations, and options; integrating with Oracle Advanced Pricing by setting profile options; and testing the LCM configuration. Optional steps include assigning items to the new inventory organization and opening a period for the new organization.
This document provides a training guide for using the Oracle EBS R12 Human Resources system. It covers topics such as starting Oracle applications, choosing a responsibility, navigating forms, getting help, and the core HR functionality including entering employee data, recruitment, defining work structures, and administration settings. The guide is intended to help FUJCCI HR staff learn the essential functionality of Oracle HRMS. It provides step-by-step instructions on common HR tasks in Oracle such as hiring, promotions, payroll, and system configuration.
This document provides an overview of Oracle Assets management and outlines the steps to set up Oracle Fixed Assets, including:
1. Creating an assets responsibility and assigning it to the IVAS11 user for setup
2. Defining profile values such as the GL ledger set and operating unit for the IVAS purchasing responsibility
3. Setting the GL ledger name profile option to 'ivas ledger' at the responsibility level for the IVAS_FixedAssets responsibility
Oracle Inventory is an enterprise application that enables companies to define part numbers, model organization structures, track perpetual inventory, maintain accurate inventory balances, plan material replenishments, and forecast demand. It provides flexfields for items, item catalogs, item categories, stock locators, account aliases, and sales orders. Key steps in implementation include designing flexfield structures, defining item categories and category sets, and assigning items to categories.
This document summarizes a presentation on cost accounting enhancements in Oracle E-Business Suite Release 12, including the transition from Material Accounting Components (MAC) to Subledger Accounting (SLA) for process costing. Key points include increased flexibility in discrete costing using SLA, mapping of process costing transactions and setup between MAC and SLA, an example of tracking purchase price variances by product line using either mapping sets or category accounting, and notes on discrete inventory period close and upgrade processes in R12.
Blanket purchase agreement and blanket release in oracle r12G Madhusudhan
Blanket purchase agreements and releases allow negotiating long-term supplier contracts while maintaining flexible delivery schedules. A blanket purchase agreement specifies negotiated item prices before actual purchasing. A blanket release is an actual order issued against the agreement, using the agreement's prices. Notifications can be set to alert about blanket agreement utilization and expiration.
The document discusses various topics related to fixed assets in Oracle Applications including:
1. There are three ways to add assets: quick additions, detail additions, and mass additions.
2. Depreciation is calculated by running the depreciation program for each book. This updates expense, accumulated depreciation, and other values.
3. Asset books are used to define depreciation rules and generate journal entries. The main types are corporate, tax, and budget books.
1) The document outlines the steps to configure Oracle Approvals Management (AME) for leave of absence (LOA) approvals in Oracle Self Service Human Resources (SSHR) Release 12. This involves creating an AME condition and rule to require approval from an employee's direct supervisor for LOA requests.
2) Key parameters for the AME setup include using the LOA transaction type, HR_IS_LEAVE_OF_ABSENCE_SS condition, and an approval action to require approvals up to the first supervisor.
3) Testing confirms that a new LOA request in SSHR routes to the employee's supervisor for approval, demonstrating that AME for LOA approvals has been successfully
This document provides steps to configure Landed Cost Management (LCM) in Oracle EBS R12.1.3. The steps include: applying required patches; creating new account codes for LCM; defining cost factors; defining LCM shipment types, organizations, and options; integrating with Oracle Advanced Pricing by setting profile options; and testing the LCM configuration. Optional steps include assigning items to the new inventory organization and opening a period for the new organization.
The document provides guidelines for implementing Oracle Learning Management. It outlines setting up flexfields, organizations, resources, content management, courses and offerings, class enrollment, financial setup, and profile options. Key steps include defining flexfield structures, creating organizations and locations, setting up the content server and folders, defining delivery modes and categories, creating courses and offerings, entering learners and managers, and configuring financial and system options.
This article aims to provide a comprehensive knowledge and understanding of the Sub ledger accounting (SLA) in Oracle E-Business Suite (EBS) R12. It uncovers some of implementation tips and techniques and also shows how users can meet their financial and reporting needs using SLA.
The article highlights how to use SLA functionality to automate and control various scenarios using specific business rules.
1. Compensation Elements Setup covers defining elements, making manual element entries, defining element input values, writing formulas, defining formula processing rules, linking elements, defining absence types, deleting element entries, and defining element balances.
2. To define an element, you enter dates, names, a classification, processing type and rules, currency, and other attributes. Elements represent compensation and benefit types or earnings and deductions.
3. Key element attributes include the primary classification, processing type (recurring or nonrecurring), termination rule, ability to allow multiple or additional entries, and indicators for payroll processing, indirect results, adjustments only, and third party payments.
Encumbrance accounting in oracle ebs r12Sam Elrashedy
This document provides an overview of encumbrance accounting in Oracle EBS R12. It discusses the purpose and key concepts of encumbrance accounting. It also describes the setup required in Oracle General Ledger, Purchasing, and Payables modules. Finally, it outlines the encumbrance accounting process and year-end activities.
Oracle EBS R12 Self service user manualFeras Ahmad
This 3-page document provides instructions for using the Employee Self Service functionality in Oracle EBS R12. It includes sections on:
1. An overview of Employee Self Service and what functions employees can perform such as updating personal information, viewing payslips, managing leaves, etc.
2. Detailed steps for changing personal information like basic details, phone numbers, addresses, emergency contacts and dependents.
3. Instructions include selecting the appropriate option to update vs correct details, filling out forms, reviewing changes, adding attachments, and submitting for approval.
The document provides a guide for employees on navigating and utilizing the key self-service features available in Oracle EBS R12.
This document describes the payment process request (PPR) setup in Oracle Payables R12, including table changes, functional steps, PPR status changes, and packages used to add or update PPR instructions and extract XML data. It provides details on creating a new payment format, payment document, payment process profile, and PPR template. It also lists the various PPR status changes and describes how to extract the XML data of format payment instructions.
Purchase Order Approval Using Approval Management EngineAh_Ismail
This document discusses setting up purchase order approval workflows using the Approval Management Engine (AME) in Oracle. It provides instructions on applying required patches, creating document styles, and making various AME configurations like defining attributes, conditions, action types, and rules. It also presents a customer case study where standard POs require approval by the Admin Manager, while contract release POs need approval from the Finance Manager. The case study is resolved by configuring different AME rules to handle each approval workflow.
This is very helpful technical guide to learn the complete process of Payroll in Oracle HRMS pertaining to following steps,
1. Running the Payroll and Reviewing the Results
2. Running the Prepayments,
3. Running the Costing,
4. Transferring the Payroll to General Ledger (GL)
5. Importing the Journals and Posting them
Thanks,
Faisal Anwar
firstfaisal@yahoo.com
+971 555749650
+92 335 0979700
The document provides instructions for setting up Oracle HRMS, including creating responsibilities, users, flex fields, business groups, locations, divisions, departments, jobs, positions, and hierarchies. Key steps include defining flex field structures for jobs, positions, competencies, grades, cost allocation, and people groups; creating a business group and attaching flex fields and profiles; adding locations, divisions, and departments; building organization hierarchies; and establishing jobs and positions.
This document provides instructions for using various functions in Oracle HRMS related to compensation elements setup, salary administration, compensation entry and reporting, payroll processes, and generating reports. It includes steps for defining elements, making element entries, setting up input values, writing formulas, administering salaries, entering payment methods, running payroll, and submitting processes and reports. The document is intended as a guide for ADMM Human Resources and Payroll staff to facilitate using the essential functionality in Oracle HRMS.
Elshayeb Expense Subinventory And Items ScenarioAhmed Elshayeb
The document discusses different types of items in Oracle Inventory and how they are treated for accounting purposes. It defines expense items, inventory expense items, and inventory asset items. It explains how the charge, budget, accrual, and variance accounts are defaulted for each item type and purchase order distribution based on destination type, subinventory, and organization parameters. Key points covered include expense vs. asset subinventories, accounts used at each step of the procure-to-pay process, and how the account generator builds accounts in Oracle Purchasing.
The document provides instructions for setting up Oracle Payables including:
1. Defining financial and payables options such as default accounts, payment terms, and taxes.
2. Creating a payables responsibility and attaching it to a user to allow access to payables functions.
3. Attaching the required GL ledger set, operating unit, and expense reimbursement profile options to the payables responsibility.
The document provides instructions for setting up Oracle Purchasing including:
1. Creating users, responsibilities, and defining security and control options
2. Setting up departments, jobs, positions, and employees in Oracle HRMS
3. Associating employees with users and defining buyers, financial options, and purchasing options
4. Defining approval hierarchies, groups, inventory items, locations, and other master data
The document discusses setting up organization parameters in Oracle Inventory. It recommends defining one organization as the item master organization where all items are defined. It then describes the different inventory parameters that can be defined for an organization, including item master organization, workday calendar, inventory parameters, costing information, account parameters, lot/serial parameters, ATP/picking parameters, inter-organization information, and warehouse parameters. These parameters control how inventory is managed and reported for the organization.
The document describes how to set up a leave accrual plan in Oracle HRMS. It involves creating elements to track opening balances, adjustments, and encashment. An accrual plan is then defined to calculate leave balances based on accrual bands. A function returns accrued leave as of a given date based on contract type and tables storing accrual data. The accrual formula uses this function to calculate accrued days between hire/contract dates and the calculation date.
The document discusses Oracle Approval Management (AME). AME defines approval rules to determine approval processes for Oracle applications. It generates approver lists and returns the next approver. Key components of AME include transaction types, attributes, conditions, actions, approver groups, and rules. AME provides a centralized rules repository and engine to define approval logic based on transaction data.
The document outlines the end-to-end AME configuration process for setting up approval workflows in Oracle Applications. It describes 12 steps, including logging in as the system administrator, defining attributes, conditions, action types, approver groups, and rules. It also demonstrates creating a sample requisition, and showing how the approval notifications are routed serially to the two approvers as defined in the workflow setup. On approval of the requisition by both approvers, the status is updated to 'Approved' and notification is sent to the requester.
The document provides an overview of Oracle Approval Management Engine (AME) concepts including:
- AME enables defining approval rules and processes for Oracle applications based on conditions and actions.
- Transaction types separate transactions into categories that may require distinct approval rules.
- A transaction's approval process includes an approver list and productions that can assign values to variables.
- At runtime, AME evaluates rules and recalculates approver lists as attribute values and data change to account for the most current situation.
The document provides guidelines for implementing Oracle Learning Management. It outlines setting up flexfields, organizations, resources, content management, courses and offerings, class enrollment, financial setup, and profile options. Key steps include defining flexfield structures, creating organizations and locations, setting up the content server and folders, defining delivery modes and categories, creating courses and offerings, entering learners and managers, and configuring financial and system options.
This article aims to provide a comprehensive knowledge and understanding of the Sub ledger accounting (SLA) in Oracle E-Business Suite (EBS) R12. It uncovers some of implementation tips and techniques and also shows how users can meet their financial and reporting needs using SLA.
The article highlights how to use SLA functionality to automate and control various scenarios using specific business rules.
1. Compensation Elements Setup covers defining elements, making manual element entries, defining element input values, writing formulas, defining formula processing rules, linking elements, defining absence types, deleting element entries, and defining element balances.
2. To define an element, you enter dates, names, a classification, processing type and rules, currency, and other attributes. Elements represent compensation and benefit types or earnings and deductions.
3. Key element attributes include the primary classification, processing type (recurring or nonrecurring), termination rule, ability to allow multiple or additional entries, and indicators for payroll processing, indirect results, adjustments only, and third party payments.
Encumbrance accounting in oracle ebs r12Sam Elrashedy
This document provides an overview of encumbrance accounting in Oracle EBS R12. It discusses the purpose and key concepts of encumbrance accounting. It also describes the setup required in Oracle General Ledger, Purchasing, and Payables modules. Finally, it outlines the encumbrance accounting process and year-end activities.
Oracle EBS R12 Self service user manualFeras Ahmad
This 3-page document provides instructions for using the Employee Self Service functionality in Oracle EBS R12. It includes sections on:
1. An overview of Employee Self Service and what functions employees can perform such as updating personal information, viewing payslips, managing leaves, etc.
2. Detailed steps for changing personal information like basic details, phone numbers, addresses, emergency contacts and dependents.
3. Instructions include selecting the appropriate option to update vs correct details, filling out forms, reviewing changes, adding attachments, and submitting for approval.
The document provides a guide for employees on navigating and utilizing the key self-service features available in Oracle EBS R12.
This document describes the payment process request (PPR) setup in Oracle Payables R12, including table changes, functional steps, PPR status changes, and packages used to add or update PPR instructions and extract XML data. It provides details on creating a new payment format, payment document, payment process profile, and PPR template. It also lists the various PPR status changes and describes how to extract the XML data of format payment instructions.
Purchase Order Approval Using Approval Management EngineAh_Ismail
This document discusses setting up purchase order approval workflows using the Approval Management Engine (AME) in Oracle. It provides instructions on applying required patches, creating document styles, and making various AME configurations like defining attributes, conditions, action types, and rules. It also presents a customer case study where standard POs require approval by the Admin Manager, while contract release POs need approval from the Finance Manager. The case study is resolved by configuring different AME rules to handle each approval workflow.
This is very helpful technical guide to learn the complete process of Payroll in Oracle HRMS pertaining to following steps,
1. Running the Payroll and Reviewing the Results
2. Running the Prepayments,
3. Running the Costing,
4. Transferring the Payroll to General Ledger (GL)
5. Importing the Journals and Posting them
Thanks,
Faisal Anwar
firstfaisal@yahoo.com
+971 555749650
+92 335 0979700
The document provides instructions for setting up Oracle HRMS, including creating responsibilities, users, flex fields, business groups, locations, divisions, departments, jobs, positions, and hierarchies. Key steps include defining flex field structures for jobs, positions, competencies, grades, cost allocation, and people groups; creating a business group and attaching flex fields and profiles; adding locations, divisions, and departments; building organization hierarchies; and establishing jobs and positions.
This document provides instructions for using various functions in Oracle HRMS related to compensation elements setup, salary administration, compensation entry and reporting, payroll processes, and generating reports. It includes steps for defining elements, making element entries, setting up input values, writing formulas, administering salaries, entering payment methods, running payroll, and submitting processes and reports. The document is intended as a guide for ADMM Human Resources and Payroll staff to facilitate using the essential functionality in Oracle HRMS.
Elshayeb Expense Subinventory And Items ScenarioAhmed Elshayeb
The document discusses different types of items in Oracle Inventory and how they are treated for accounting purposes. It defines expense items, inventory expense items, and inventory asset items. It explains how the charge, budget, accrual, and variance accounts are defaulted for each item type and purchase order distribution based on destination type, subinventory, and organization parameters. Key points covered include expense vs. asset subinventories, accounts used at each step of the procure-to-pay process, and how the account generator builds accounts in Oracle Purchasing.
The document provides instructions for setting up Oracle Payables including:
1. Defining financial and payables options such as default accounts, payment terms, and taxes.
2. Creating a payables responsibility and attaching it to a user to allow access to payables functions.
3. Attaching the required GL ledger set, operating unit, and expense reimbursement profile options to the payables responsibility.
The document provides instructions for setting up Oracle Purchasing including:
1. Creating users, responsibilities, and defining security and control options
2. Setting up departments, jobs, positions, and employees in Oracle HRMS
3. Associating employees with users and defining buyers, financial options, and purchasing options
4. Defining approval hierarchies, groups, inventory items, locations, and other master data
The document discusses setting up organization parameters in Oracle Inventory. It recommends defining one organization as the item master organization where all items are defined. It then describes the different inventory parameters that can be defined for an organization, including item master organization, workday calendar, inventory parameters, costing information, account parameters, lot/serial parameters, ATP/picking parameters, inter-organization information, and warehouse parameters. These parameters control how inventory is managed and reported for the organization.
The document describes how to set up a leave accrual plan in Oracle HRMS. It involves creating elements to track opening balances, adjustments, and encashment. An accrual plan is then defined to calculate leave balances based on accrual bands. A function returns accrued leave as of a given date based on contract type and tables storing accrual data. The accrual formula uses this function to calculate accrued days between hire/contract dates and the calculation date.
The document discusses Oracle Approval Management (AME). AME defines approval rules to determine approval processes for Oracle applications. It generates approver lists and returns the next approver. Key components of AME include transaction types, attributes, conditions, actions, approver groups, and rules. AME provides a centralized rules repository and engine to define approval logic based on transaction data.
The document outlines the end-to-end AME configuration process for setting up approval workflows in Oracle Applications. It describes 12 steps, including logging in as the system administrator, defining attributes, conditions, action types, approver groups, and rules. It also demonstrates creating a sample requisition, and showing how the approval notifications are routed serially to the two approvers as defined in the workflow setup. On approval of the requisition by both approvers, the status is updated to 'Approved' and notification is sent to the requester.
The document provides an overview of Oracle Approval Management Engine (AME) concepts including:
- AME enables defining approval rules and processes for Oracle applications based on conditions and actions.
- Transaction types separate transactions into categories that may require distinct approval rules.
- A transaction's approval process includes an approver list and productions that can assign values to variables.
- At runtime, AME evaluates rules and recalculates approver lists as attribute values and data change to account for the most current situation.
The document provides an overview of Oracle Approval Management Engine (AME) concepts including:
- AME enables defining approval rules and processes for Oracle applications based on conditions and actions.
- Transaction types separate transactions into categories that may require different approval rules.
- A transaction's approval process includes an approver list and productions that can assign values to variables.
- At runtime, AME evaluates rules and recalculates approver lists as approvals are received to account for changes.
Oracle Approval Management Engine (AME) defines approval rules and processes for transactions in Oracle applications. Key concepts include:
1) Approval rules specify conditions and actions that determine a transaction's approval process.
2) Transaction types categorize transactions that require distinct approval rules.
3) AME generates approver lists and productions to specify approvers and assign variable values for a transaction.
4) At runtime, the integrating application communicates with AME to manage approval processes, and AME recalculates approver lists as approvals are received.
This document provides an overview of requisition approval using Oracle Approvals Management (AME) within the Oracle eBusiness Suite. It describes the key concepts and components of AME including transaction types, attributes, conditions, actions, rules, and configuration variables. It also covers the requisition approval process flow, setup requirements in core purchasing, and parallelization concepts supported in later releases of AME.
This document provides instructions for setting up Oracle Approvals Management (AME) to handle purchase requisition approvals in Oracle E-Business Suite. It describes assigning AME roles to users, granting access to transaction types, and configuring AME attributes, conditions, rules, and approval groups. It also explains how to test the AME setup and enable AME approvals for purchase requisitions.
This document provides instructions for setting up Oracle Approvals Management Engine (AME) to handle purchase requisition approval workflows in Oracle E-Business Suite. It describes assigning AME roles to users, granting users access to transaction types, and configuring AME attributes, conditions, action types, and rules to determine the approval process for purchase requisitions based on item details. Screenshots are provided from the 11i version of AME but most details apply to later versions as well.
This document provides instructions for setting up and using life event checklists in Oracle HRMS R12. It includes steps for defining life events, eligibility profiles, checklists and tasks. It also describes how checklist tasks get automatically allocated to employees after a triggering life event. Background processing details are provided to further explain how checklists and tasks are allocated and managed in the system. The document seeks to help readers understand and properly utilize the checklist functionality in Oracle HRMS.
Authorisation Concept In SAP | http://sapdocs.infosapdocs. info
The document discusses authorization concepts in SAP systems. It explains that authorizations for users are created using roles and profiles, which are defined by the administrator. Roles contain authorizations that allow users to access transactions, reports, and applications. There are two ways to create new roles - copying an existing role or creating a new role based on business requirements. The process of creating a new role involves assigning transactions and programs to the role menu, defining authorizations, and generating an authorization profile.
1. The document provides instructions for navigating and using the basic features of the Workday HRIS system, including initiating employee or manager-led changes.
2. As an employee, you can update personal information by clicking "Personal Information" under "All About Me" and submitting changes for approval. As a manager, you can initiate transfers, promotions, or job changes for direct reports by selecting the employee and filling out relevant details before submitting.
3. Both employees and managers can check the status of initiated changes by viewing their workfeed notifications or clicking "Process Status" to see approval workflows.
The document describes the setup required for an automated lease approval workflow in Oracle Property Manager. Key steps include:
1. Creating employees and assigning supervisors in HRMS to define the approval hierarchy.
2. Configuring the seeded "PN: Lease Approval Workflow" in Workflow Developer Studio and linking it to the "oracle.apps.pn.lease.leasestatus" business event.
3. Setting up attributes, actions, conditions, and approver groups for the workflow in Oracle Approvals Management, and creating users to fulfill the necessary responsibilities for property manager, system administrator, and workflow administration.
This document discusses role mappings in Oracle Fusion, which control user access by automatically provisioning and restricting roles. It describes how to access role mappings, basic principles for auto-provisioning roles based on user attributes, making roles requestable, self-requestable, handling terminations, running auto-provisioning, and bulk loading users. Role mappings automate role assignments, restrict who can request roles, and are based on user attributes from HR records.
Oracle Procurement Cloud Release 8 includes several new features across Oracle Fusion Self Service Procurement, Oracle Fusion Purchasing, Oracle Fusion Sourcing, and Oracle Fusion Supplier Model. Key updates include simplified approval rules management in Self Service Procurement and Purchasing, new analytics for line of business managers, expanded descriptive flexfields in Sourcing, and updated supplier registration approval rules in the Supplier Model. Many of the new features are automatically enabled after upgrade, while some require additional configuration by administrators.
The document discusses the setup and configuration of credit checking in Oracle Order Management, including defining credit check rules, setting the credit check level at the order or line level, determining whether to use real-time or pre-calculated exposure amounts, and options for overriding manual releases of credit holds and defining conversion types between currencies. Credit checking in Oracle Order Management validates orders and lines against credit limits and business rules to determine if customers have sufficient available credit to process orders in advance of payment.
This document provides instructions for setting up key HRMS flexfields and other core configurations in Oracle HRMS. It describes how to define flexfield structures for jobs, positions, grades, people groups, competencies, and cost allocation. It also covers setting up descriptive flexfields, extra information flexfields, organizational structures, lookup types and values, payroll setup and more. The detailed steps allow an analyst to fully configure an Oracle HRMS implementation for a company.
The document discusses release management in BMC Remedy ITSM 7.6. It describes the release request lifecycle including stages like initiate, plan, build, test, deployment, and close down. It outlines roles like release coordinator, change manager, and activity assignee. It provides details on how to create release requests, add related change requests and activities, and move through the approval phases. The webinar aims to help users understand release management functionality in BMC Remedy.
This document provides instructions for setting up Oracle Purchasing. It outlines 18 steps for the basic setup including: creating users and responsibilities; defining departments, jobs, positions and employees; associating employees with users; defining buyers, financial and purchasing options; document security and approval hierarchies; purchasing periods; units of measure; inventory items; multi-org access control; locations; and more. It also provides details on configuring related modules like Oracle HRMS, including defining flexfields, jobs, positions, employees, and position hierarchies.
Workflow functional concept on openerp7Aziza Mohamed
The document discusses workflow functionality in OpenERP 7. It defines workflow as describing the evolution of documents over time through defined states and transitions. It provides an example of a holiday request approval workflow and steps for customizing it, including modifying states, activities, and transitions in the XML file. It also discusses how to hide buttons and control approvals based on user attributes like job role.
This document provides instructions for setting up Oracle Purchasing. It outlines 18 steps for the basic setup including:
1. Creating users and defining purchasing responsibilities
2. Setting profile options and adding responsibilities to users
3. Defining departments, jobs, positions, and employees
4. Associating employees with users, defining buyers, and financial and purchasing options
5. Defining document security, approval hierarchies, and controlling purchasing periods
This document provides instructions for setting up an automated approval management engine (AME) for purchase requisition approvals. It includes steps to assign AME roles, grant transaction type access, create a new transaction type, set up attributes, conditions, action types, approval groups, and rules. It also provides instructions for enabling AME for requisition approvals and testing sample requisitions.
Similar to Configuring Parallel Approvers Notification (20)
Oracle Fusion HCM Payroll Process Flow.pdfFeras Ahmad
This document outlines the key steps in the Oracle Fusion HCM payroll process flow, including:
1) Setting up legal entities, reporting units, consolidation groups, banks, and payment methods.
2) Configuring payroll definitions, elements, salary bases, element eligibility, and formulas.
3) Preparing employees for payroll by assigning payroll, salary basis, elements, and inputting values.
4) Running the payroll process which includes retro calculations, payroll runs, costing, prepayments, payments, transferring to GL, and archiving.
Configure Flexfield Parameters in Value Sets for Document Records.docxFeras Ahmad
Meg needs to create document records for contacts at her company Vision Corporation. To make this easier, a descriptive flexfield is configured to display a list of contacts for Meg to select from when creating new document records. This is done by defining a new segment in the document flexfield called "Contact" and creating a value set called "EMP_CONTACT" that retrieves contact names from the database based on Meg's person ID. When Meg creates a new document record, the flexfield segment will contain a list of her contacts to choose from.
Rock materials like compact rocks and digsaggregated rocks as well as binder materials like lime, plaster, and cement are used in construction. Concrete, made from a combination of aggregate and cement binder, is a common composite building material used to make pieces for buildings. Ceramic materials are produced from clay through processes of mixture, molding, and firing in ovens.
There are several methods for debugging the Fast Formula including ESS_LOG_WRITE, HR_TRACE, PAY_INTERNAL_LOG_WRITE, and ADD_RLOG. ESS_LOG_WRITE writes logs to the ESS log and HR_TRACE requires setting up a PL/SQL trace. PAY_INTERNAL_LOG_WRITE is for payroll processes. ADD_RLOG accepts formula ID, rule ID, and a message and writes to an Oracle Time and Labor table. The logs can then be viewed through monitoring pages which vary by team.
Oracle Fusion Cloud Payroll Costing QueryFeras Ahmad
This SQL query retrieves data from multiple payroll-related tables to provide costing and accounting information for different elements. It joins tables related to element types, links, classifications, cost allocations and accounts to return fields like company, department, account and intercompany values for both the cost and offset accounting distributions. The query filters for elements that have costing enabled and an eligibility link defined.
Oracle Fusion Cloud sensitive data access auditFeras Ahmad
This document discusses how to audit access to sensitive data in Oracle HCM Cloud. It explains that the Sensitive Data Access Audit page allows monitoring access to attributes like national IDs, addresses and phone numbers. Only users with the IT Auditor predefined role or a custom role granted the PER_VIEW_SENSITIVE_DATA_ACCESS_AUDIT_PRIV privilege can access the audit data. Enabling the ORA_HCM_SENSITIVE_DATA_VIEW_AUDIT_ENABLED profile allows logging sensitive data views to the PER_SENSITIVE_DATA_AUDIT table, where details on viewed persons, viewers, pages and times can be queried.
This SQL query joins data from multiple tables to retrieve employee information including the person number, name, job, department, termination date, and FTE. It limits the results to active US employees by checking that the effective dates for each record being joined overlap with the current date.
Legal Employer Details Query Oracle Fusion CloudFeras Ahmad
This SQL query selects registration name, number, address details including lines, city, state, country and postal code from three tables - xle_registrations, xle_entity_profiles and HZ_LOCATIONS. It joins the tables on legal entity ID from xle_entity_profiles to source ID in xle_registrations and location ID between xle_registrations and HZ_LOCATIONS to retrieve registration and address information for an entity.
Query Pre Payment details Oracle Fusion CloudFeras Ahmad
This document contains a SQL query that selects various payment-related fields from multiple tables in order to retrieve information about pre-payments, including the payment ID, amount, status, payroll and payment details, payee information, and more. The query joins together tables related to organizations, payment methods, payments, payrolls, people, and other financial information to extract the necessary data.
The Goal with performance details Oracle Fusion CloudFeras Ahmad
This document contains an SQL query that selects employee data from various database tables including employee number, name, hire date, email, manager details, department, job, rating and evaluation details. The query filters on goal weighting, evaluation status, rating code and legal employer to return ordered results.
All payroll elements with eligibility Oracle Fusion CloudFeras Ahmad
This document contains a SQL query that selects employee data including identification numbers, names, locations, departments, payroll information, pay amounts, and dates from various payroll and employee database tables. It joins these tables together on common fields like employee IDs, payroll IDs, and effective dates to retrieve the relevant information for payroll processing and reporting.
Payroll costing details Oracle Fusion Cloud HCMFeras Ahmad
This SQL query selects data from various PAY tables to retrieve payroll costing and allocation details. It joins tables like PAY_XLA_EVENTS, PAY_PAYROLL_REL_ACTIONS, PAY_COSTS, PAY_RUN_RESULTS to get fields like event ID, cost ID, payroll action IDs, costed value, currency code, element name, cost allocation keys, and term and assignment numbers. The query filters for costs that have been transferred to the general ledger.
Infolets and OTBI Deep link Actionable Reports - Configuration Work Book Feras Ahmad
This document provides information and instructions for configuring deep links from Oracle Transactional Business Intelligence (OTBI) reports and analyses to pages and objects in the Risk Management Cloud application. It includes sample deep link URLs for various application pages and objects, such as risks, controls, processes, and more. It also explains how to set the "interaction" property in OTBI analyses to create clickable links using these deep link URLs.
Query Worker Contracts Details Oracle Fusion CloudFeras Ahmad
This SQL query selects employee data from multiple tables, joining them on primary keys and foreign keys. It filters for active records where the effective dates include today's date. The query returns the employee number, name, job name, department name, and additional contract data, ordering by employee number, job name, and department name.
Query all roles and duties and privileges Oracle Fusion CloudFeras Ahmad
This document contains an SQL query that selects data from various tables to retrieve employee job role and privilege information. The query joins tables containing user accounts, roles, role memberships, privileges, and employee data to return fields including employee number, name, job role, duty role, assigned privileges, and navigation path for roles where the job role is either Employee or Line Manager. The results are ordered by employee number.
This document contains a SQL query that selects various payroll data including employee identifiers, names, locations, departments, pay amounts, and time periods from multiple payroll-related tables. The query joins these tables together on primary and foreign keys and filters on certain date ranges and payroll categories to retrieve the relevant payroll information for reporting purposes.
The document summarizes Oracle's HCM Cloud solution which provides a complete suite of human capital management functionality including global HR, recruiting, talent management, learning, time and attendance, absence management, payroll, and an AI-powered digital assistant. It offers these services for over 200 countries and jurisdictions. Key features highlighted include the digital assistant's ability to handle common HR transactions, global HR tools for workforce management and talent mobility, an HR help desk for employee inquiries, configurable time and attendance tracking, and integrated payroll processing that ensures regulatory compliance.
Oracle Fusion HCM vs E-Business Suite HRMSFeras Ahmad
This document compares Oracle EBS and Oracle Fusion, providing an overview of each system and their key differences. It outlines advantages of Fusion such as improved workflow, security, reporting capabilities, and use of newer technologies. Disadvantages of EBS discussed include more limited functionality and customizations needed for requirements like Malaysian tax rules. Oracle Fusion HCM Cloud is then described as incorporating features from other Oracle acquisitions with configurable templates, out of box integration, and centralized benefits administration. Benefits of the Cloud HCM option include no upfront costs, automatic updates, and mobile access.
2020 06-11 goverment KSA Summary VAT increaseFeras Ahmad
The document summarizes the transitional provisions for increasing the Value Added Tax (VAT) rate in Saudi Arabia from 5% to 15%, effective July 1, 2020. It outlines how the new VAT rate will apply based on the date contracts were signed or tax invoices were issued. For contracts signed before May 11, 2020, the 5% VAT rate will continue to apply until June 30, 2021. For contracts signed between May 11 and June 30, 2020, the 5% rate applies for supplies before June 30, 2020 and 15% after. Similar provisions apply for tax invoices issued on continuous supplies that straddle the VAT rate change date.
The Microsoft 365 Migration Tutorial For Beginner.pptxoperationspcvita
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
How information systems are built or acquired puts information, which is what they should be about, in a secondary place. Our language adapted accordingly, and we no longer talk about information systems but applications. Applications evolved in a way to break data into diverse fragments, tightly coupled with applications and expensive to integrate. The result is technical debt, which is re-paid by taking even bigger "loans", resulting in an ever-increasing technical debt. Software engineering and procurement practices work in sync with market forces to maintain this trend. This talk demonstrates how natural this situation is. The question is: can something be done to reverse the trend?
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Northern Engraving | Nameplate Manufacturing Process - 2024Northern Engraving
Manufacturing custom quality metal nameplates and badges involves several standard operations. Processes include sheet prep, lithography, screening, coating, punch press and inspection. All decoration is completed in the flat sheet with adhesive and tooling operations following. The possibilities for creating unique durable nameplates are endless. How will you create your brand identity? We can help!
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectorsDianaGray10
Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more.
The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications.
We’ll discuss and demo the benefits of UiPath Apps and connectors including:
Creating a compelling user experience for any software, without the limitations of APIs.
Accelerating the app creation process, saving time and effort
Enjoying high-performance CRUD (create, read, update, delete) operations, for
seamless data management.
Speakers:
Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP
Charlie Greenberg, host
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...Jason Yip
The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
Digital Banking in the Cloud: How Citizens Bank Unlocked Their MainframePrecisely
Inconsistent user experience and siloed data, high costs, and changing customer expectations – Citizens Bank was experiencing these challenges while it was attempting to deliver a superior digital banking experience for its clients. Its core banking applications run on the mainframe and Citizens was using legacy utilities to get the critical mainframe data to feed customer-facing channels, like call centers, web, and mobile. Ultimately, this led to higher operating costs (MIPS), delayed response times, and longer time to market.
Ever-changing customer expectations demand more modern digital experiences, and the bank needed to find a solution that could provide real-time data to its customer channels with low latency and operating costs. Join this session to learn how Citizens is leveraging Precisely to replicate mainframe data to its customer channels and deliver on their “modern digital bank” experiences.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor IvaniukFwdays
At this talk we will discuss DDoS protection tools and best practices, discuss network architectures and what AWS has to offer. Also, we will look into one of the largest DDoS attacks on Ukrainian infrastructure that happened in February 2022. We'll see, what techniques helped to keep the web resources available for Ukrainians and how AWS improved DDoS protection for all customers based on Ukraine experience
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Configuring Parallel Approvers Notification
1. 1
Configuring Parallel Approvers Notification
Using Oracle Approvals Management for
Oracle Self-Service Human Resources
(R11i10/R12)
An Oracle White Paper
November 2007
3. 3
1. Executive Summary
The Approval process in an organization may make use of Approver groups – where a group of people is
assigned to an Approver group. AME allows us to define approver groups as part of the approval process
and designate the group to approve a transaction approval. AME has the flexibility of allowing Parallel
Approvers Notification. The approval notification in this case will be triggered for all the members in
parallel within an approver group. However, the availability of this feature in integrating products depends
on whether this feature is implemented/supported in those products. This white paper intends to provide a
configurable option within SSHR to handle Parallel Notification of approvers in an approver group.
1.1 Release Level
Important: This document is meant for HRMS 11.5.10 FP K Rup1 and forward.
2. Introduction
AME provides us the flexibility to define the approval processes based on an organization’s requirements
without writing programming code. Business users can define the approval rules for the organization based
on the approval policies of their organization. If a business case requires approvers from a group of
approvers that does not exist as a chain of authority in an approver hierarchy supported by AME, then this
requires us to define an approver group containing the approvers. An Approver group must be assigned a
name, description, and members. The members must be ordered. The order number of the members
determines the order in which they are notified. The order numbers do not need to be unique. For example,
if we assign all of a group’s members the order number one, the group will typically be notified in parallel.
3. References
Implementing Oracle Approvals Management
http://metalink.oracle.com/cgi-bin/cr/getfile_cr.cgi?282964
Implementing Oracle Self-Service Human Resources (SSHR) 4.2
http://metalink.oracle.com/cgi-bin/cr/getfile_cr.cgi?284440
4. Parallel Approval Process
Approver-group parallelization is controlled explicitly via the approver-group order numbers that a
transaction type assigns the approver groups. An approver group determines its members’ order numbers
using the group’s Voting regime, and also the member order numbers assigned to static members or
generated for dynamic members. Dynamic members are assigned sequential member order numbers
according to the order in which the group’s SQL query returns the members. Approver-group voting
regimes can have any of four values serial, consensus, first-responder-wins and order number. The
4. 4
values determine not only the order numbers of the group members, but also whether all group members or
one amongst them must approve the item.
The scope of this white paper is limited to the ‘first-responder-wins’ voting regime only.
The first-responder-wins regime assigns group order number one to all members. All the members in the
group are notified. In this case, only the first responder must approve; all other members’ responses are
recorded but ignored.
5. Configuration for Parallel Approver Notification
SSHR can be configured to achieve the parallel notification of approvers within a group. This requires a
few set up steps, which are detailed below.
5.1 Pre-requisites
1. Access to CoreHR responsibility – HRMS Manager responsibility
2. Access to Approvals Management Business Analyst responsibility – Approver Group set up
3. Availability of ‘Position Control Roles’ Approver Type in AME setup
5.2 Setup Steps
1. Define Roles:
Using HRMS Manager responsibility define roles and assign the Person names to the roles who
are part of an approver group. For each approver group for which parallel notification is required,
define a corresponding role in the Maintain Roles form with the same members assigned to the
role as in the approver group.
Navigation: US HRMS Manager responsibility Transaction Maintenance Roles Maintain
Roles Users
2. Approver Group set up:
Using Approvals Management Business Analyst responsibility within AME, select the
Transaction Type and define attributes/conditions as required for the business case. Define the
approver group with Voting regime ‘first-responder-wins and add the Roles defined in Step 1 as
approver group members with Approver Type ‘Position Control Roles’. Add those roles to which
the corresponding group members were assigned whom we want to be the members of the
approver group. Give order number for the roles so that if we are using multiple roles/groups for
approval, the members of each of role will be notified based on the order number assigned to the
roles. Define Approval Rule with action type set to require approval from the approver groups.
Navigation: Approvals Management Business Analyst responsibility Business Analyst
Dashboard Select Transaction Type Define Attributes Conditions Define Approver
Groups Add Group Members (Roles) Define Rule
5. 5
3. Availability of ‘Position Control Roles’ Approver Type in AME setup
While defining Approver group, the dropdown for Approver Type under Add Group Members
should have ‘Position Control Roles’. This is determined by the AME set up at the time of
implementation. Using Approvals Management Administrator responsibility, navigate to
Approver Types via the quick link on the right side of the page. Check if PQH_Role is present in
the list of Approver Types. If Yes, cancel from the page and navigate to Configuration variables
via quick link. The ‘Allow All Approver Types’ variable should be set to Yes.
Important: This variable option cannot be reverted back to No once set to Yes.
Navigation: Approvals Management Administrator responsibility Admin Dashboard Quick
Links - Approver Types
Approvals Management Administrator responsibility Admin Dashboard Quick Links
Configuration Variables
Illustration
To illustrate the above setup steps, we will use the example of ‘Change Hours’ function in
Manager Self Service.
Setting up Roles
We will define two roles Role 1 and Role 2 and assign two users Antony Cyril, Antony Zery
and Antony Samuel, Antony Metilda to each role respectively.
Antony Cyril & Antony Zery are the members of the first approval group for which we require
parallel notification.
Similarly, Antony Samuel & Antony Metilda are the members of the second approval group for
which we require parallel notification.
Use the HRMS Manager responsibility to define roles.
8. 8
We will use the seeded AME Transaction Type for SSHR ‘Oracle Self Service Human
Resources’.
Use the Approvals Management Business Analyst responsibility to select the Transaction Type
from the Business Analyst Dashboard.
Click on Setup of the Transaction Type to define Attributes/Conditions/Action Types/Approver
Groups.
Alternatively, select the Transaction Type from the ‘Approval Process Setup’ window on the right
side of Business Analyst Dashboard and go to Attributes/Conditions/Action Types/Approver
Groups/Rules as required.
9. 9
OR
Defining Attribute
For this example we will use the existing attribute WORKFLOW_PROCESS_NAME. No action
needs to be performed in the Attribute window since we are using the seeded attribute.
10. 10
Defining Conditions
We will use the condition ‘WORKFLOW_PROCESS_NAME in
(HR_CHANGE_HOURS_JSP_PRC)’ where HR_CHANGE_HOURS_JSP_PRC is the seeded
SSHR function Change Hours.
Go to the Conditions tab to define the regular condition.
Click on Create to define a new condition
Search for the attribute WORKFLOW_PROCESS_NAME to define condition for the attribute.
11. 11
Defining Approval Groups
Create two Approval Groups, Group 1 and Group 2 corresponding to the two roles defined earlier.
For Group 1, Add ‘Approvers’ as ‘Role 1’ with order number 1 of Position Control Roles type
For Group 2, Add ‘Approvers’ as ‘Role 2’ with order number 2 of Position Control Roles type
Use Voting Regime ‘first-responder-wins’ for both the approver groups.
Go to Approver Groups tab to define the approver groups.
Click on Create to define a new Approver Group.
Group 1 with order number 1 and Voting Regime – First Responder Wins
12. 12
Click on Add Another Row under Group Members on the bottom of the Create New Approver
Group page
Add Role 1 as Approver of Approver Type Position Control Roles. The order number defaults to 1
Click Apply
Click on Create to add the next Approver Group
13. 13
Group 2 with order number 2 and Voting Regime – First Responder Wins
Add Role 2 as Approver of Approver Type Position Control Roles. The order number defaults to
1.Click Apply
Defining Rules
Define a Rule with Action Type ‘Require Approval from Group 1’ and ‘Require Approval from
Group 2’.
Go to Rules Tab. Click on Create to define a new Rule using the Approver Groups defined above
15. 15
Click on Next
Add Action of ‘Require Approval from Group 1’ of Action Type approval group – chain of
authority
Click on Add Action to add the second approver group – Group 2
19. 19
6. Change the Work Hours and click Next
7. Make changes to Pay if required. In this example we are not changing the Pay. Click Next
20. 20
8. Review the list of approvers generated by AME in the Change Hours: Review Page
Verify the list displays Role 1 and Role 2 as the approvers
8. Submit the transaction
10. Log in as Antony Cyril and check the workflow notification
21. 21
11. Verify the approval notification for the Change Hours of John, Jane is displayed
22. 22
12. Do not approve the notification, logout without performing any action on the notification
13. Log in as Antony Zery and check the workflow notification
14. Verify the approval notification for the Change Hours of John, Jane is displayed
23. 23
15. Parallel notification is achieved since both the members of the approver group received the
notification
16. Approve the notification in ZERYUSER (Antony, Zery) login
17. Login as Antony, Cyril and verify that the notification no longer displays in the Open
Notifications List. Verify the same for Antony Zery also
24. 24
18. The notification displays in the All Notifications list for Antony Cyril and Antony Zery.
19. Click on the notification to view the Action History
20. Log in Antony Samuel and check the workflow notification
25. 25
21. Verify the approval notification for the Change Hours of John, Jane is displayed
22. Do not approve the notification, logout without performing any action on the notification
23. Log in as Antony, Metilda and check the workflow notification
24. Verify the approval notification for the Change Hours of John, Jane is displayed
26. 26
25. Parallel notification is achieved since both the members of the approver group received the
notification. The members of this group are notified after approval from the first group (role 1)
since the order number of this group is 2.
26. Approve the notification in Antony, Metilda’s login
27. Login as Antony, Samuel and verify that the notification no longer displays in the Open
Notifications List.
27. 27
28. The notification displays in the All Notifications list as a closed notification for Antony,
Samuel and Antony, Metilda
29. Click on the notification to view the Action History
Note: If an approver in Role 2 rejects the notification, the rejection action appears in the action
history of the notification in ‘All Notifications’ list for the other members in Role 1 and
Role 2 with a status of closed as shown below. There is no rejection notification sent to
the previous approver in the chain in this case. This is existing functionality and this
behaviour is not limited to this workaround.
28. 28
7. Limitations Known
1. In the above example, if any member in group 2 performs return for correction, the return for
correction can only be done to that member in group 1 who acted upon it earlier. For the other
members of the two groups, the action history of the approval notification in ‘All Notifications’
list shows the return for correction action with a status of ‘closed’ for the notification.
2. Similarly if a member in group 1 returns for correction, the other group members are not
notified of the return for correction. For the other members of group 1, their ‘All Notifications’
list shows the action history of the notification with Return for Correction action and with a
status of ‘closed’ for the notification.
3. When approver is part of a role, the corresponding role-name would be appearing in the List of
approvers displayed in the Review page and in the notifications generated. The role-name to
which the approver belongs to replaces the actual approver name in the notifications and on the
review page. (Similar to how the role-names are displayed in the ‘From’ column in the above
screenshot under #29.)
4. The Roles defined are static and cannot be made dynamic. If there are changes to the approvers
assigned to the roles, then the roles need to be manually updated to reflect the changes. For
example, if a role comprises of three approvers and if one of them is terminated, then the
terminated approver must be manually removed from the role.
5. The notifications generated by using this workaround will not be available under the function
‘All Actions Awaiting Your Attention’ where the notifications list is derived based on recipient
being login person user. When this workaround based on roles defined in Oracle HRMS is used,
it is recommended to access notifications from homepage worklist or using the workflow user
web applications responsibility
8. Conclusion
The process described in this whitepaper is a configurable workaround to achieve Parallel Notification of
Approvers within an approver group in SSHR. Though this feature is available in AME, the integrating
products may or may not support this feature.
Keeping in mind the limitations of this workaround, it is a fairly straightforward process to achieve parallel
notification within SSHR.
Disclaimer: Although various combinations of scenarios have been explored and tested within the scope of
this whitepaper, there may be some complex scenarios applicable specifically to your business, which you
are required to test.