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.
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
This document provides an overview of inventory organization structures in Oracle Inventory. It discusses how to set up locations, define organizations and subinventories, and establish multi-organization structures. It also covers inventory parameters, costing methods, revision and serial number tracking, availability and sourcing rules. The document summarizes organization reports, profile options, and the relationships between items, attributes, statuses, and templates.
This document outlines the key setup steps required to implement the purchasing module in Oracle R12 Apps. There are 25 setup steps described including defining organizations, items, calendars, flexifields, approvals, suppliers, and various options. Completing these prerequisite setup steps is necessary before the purchasing module can be used. The blog link provided contains more details on each of the specific setup procedures.
Understanding credit check in oracle e business suiteOlumide Idowu
- Order Management Family Pack G introduced new credit check functionality in Oracle Order Management including line level credit checking, multi-currency credit checking, pre-calculated credit exposure, item category credit profiles, and organization default credit profiles.
- Key changes include being able to perform credit checks at the order line level instead of just the order header level, using pre-calculated credit exposure to improve performance, and setting up multi-currency credit limits to check exposure across currencies.
- Setting up these new features involves defining credit profiles, credit check rules, exposure calculation methods, and enabling automatic credit checking at the appropriate levels.
Oracle Inventory is one of Oracle's enterprise applications products that enables companies to define part numbers, model organization structures, track perpetual inventory, maintain accurate on-hand balances, plan material replenishments, and forecast anticipated demand. It provides several key flexfields including system items, item catalogs, item categories, stock locators, and account aliases. The flexfields must be designed and configured before implementing inventory functionality in Oracle.
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
This document provides an overview of inventory organization structures in Oracle Inventory. It discusses how to set up locations, define organizations and subinventories, and establish multi-organization structures. It also covers inventory parameters, costing methods, revision and serial number tracking, availability and sourcing rules. The document summarizes organization reports, profile options, and the relationships between items, attributes, statuses, and templates.
This document outlines the key setup steps required to implement the purchasing module in Oracle R12 Apps. There are 25 setup steps described including defining organizations, items, calendars, flexifields, approvals, suppliers, and various options. Completing these prerequisite setup steps is necessary before the purchasing module can be used. The blog link provided contains more details on each of the specific setup procedures.
Understanding credit check in oracle e business suiteOlumide Idowu
- Order Management Family Pack G introduced new credit check functionality in Oracle Order Management including line level credit checking, multi-currency credit checking, pre-calculated credit exposure, item category credit profiles, and organization default credit profiles.
- Key changes include being able to perform credit checks at the order line level instead of just the order header level, using pre-calculated credit exposure to improve performance, and setting up multi-currency credit limits to check exposure across currencies.
- Setting up these new features involves defining credit profiles, credit check rules, exposure calculation methods, and enabling automatic credit checking at the appropriate levels.
Oracle Inventory is one of Oracle's enterprise applications products that enables companies to define part numbers, model organization structures, track perpetual inventory, maintain accurate on-hand balances, plan material replenishments, and forecast anticipated demand. It provides several key flexfields including system items, item catalogs, item categories, stock locators, and account aliases. The flexfields must be designed and configured before implementing inventory functionality in Oracle.
Internal requisitions provide a mechanism for requesting inventory transfers between organizations. They allow tracking inventory as it moves between organizations and reducing costs. Key features include defining sourcing options, managing an inter-organization shipping network, and using the same process for internal and external requisitions.
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
Locator control in Oracle Inventory allows restricting items to specific storage locations called locators. This document outlines the steps to implement locator control at the organization, subinventory, and item levels including: 1) defining the stock locators flexfield, 2) setting locator control parameters, 3) defining locators, subinventories and assigning items, and 4) restricting items to specific locators and subinventories. Locator control provides accurate tracking of inventory locations for reporting and transactions.
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
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.
Oracle iProcurement is a self service based requisitioning application that controls employee purchasing. It is a key component of oracle advanced procurement, the integrated suite that dramatically cuts all the supply chain management costs. The Oracle iProcurement functionality provides the essentials for the ordering portion of the procurement process. This includes catalog content management, requisitioning, purchase order creation, and receiving orders. This webinar will deal in brief about the benefits and usages of Oracle iProcurement.
Agenda:
- Procurement process: Oracle iProcurement
- Indirect and Direct Sourcing
- Why are we switching to iProcurement?
- Various Benefits
- Oracle iProcurement Release 12 Enhancements
- Oracle iProcurement Overview
- Oracle iProcurement in Comprehensive Procure-to-Pay Flow
- Core Features of Oracle iProcurement
- Oracle Service Procurement Integration
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.
This document provides an overview of Oracle Advanced Pricing, which extends the pricing capabilities of Oracle's basic pricing module. It describes key features such as price lists, modifiers, formulas, and qualifiers that allow users to define pricing rules and adjustments. The pricing engine uses this information to select the appropriate price list, apply any eligible modifiers, and return the calculated price to calling applications.
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.
This document provides an overview of setting up a multi-organization structure in Oracle Financials R12. It discusses defining business groups, ledgers, legal entities, operating units, and inventory organizations. It also covers multi-org access control, preferences, and validation reports. The document outlines the steps to design an organization structure and then create and assign the necessary entities in the system to implement the multi-org functionality.
A trip represents a freight shipment from one location to another. It consists of at least two stops - a pick-up stop and drop-off stop. When an order is placed and lines are booked, Oracle Shipping Execution allows a transportation planner to automatically create a trip for each item from its inventory location to the customer's shipping address in one process.
1. 2-way matching verifies purchase order and invoice quantities match, 3-way adds receipt quantities, and 4-way adds acceptance documents.
2. Job hierarchy uses a single approval path while position hierarchy allows different approval paths for the same job. Setting up position hierarchy involves defining jobs, positions, mapping positions to jobs and documents, and setting approval groups.
3. Sourcing rules determine suppliers while bill of distributions determine warehouses to distribute items to.
This document provides an overview and tutorial on using Oracle Report Manager in R12. It discusses the presenter's background and objectives of the session. Key features of Report Manager are outlined, including how it provides an online repository for financial reports. The document then provides a case study example and goes through setting up Report Manager and a quick tutorial on creating a template, submitting a report, and viewing outputs. It concludes with tips, tricks and potential traps to be aware of when using Report Manager.
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 discusses configuring AP invoice line level approval using Approval Management Engine (AME) in Oracle Applications. It covers:
1. Enabling AME and invoice approval workflow
2. Creating line level attributes in AME like line amount and item type
3. Defining conditions and action types in AME
4. Setting up approval rules in AME
5. Testing the configuration using the AME test workbench
6. Viewing approval histories for invoices and lines
This document discusses Oracle's Transaction Account Builder (TAB) which is used to derive accounting flexfields for subledger transactions in Oracle Fusion Applications. TAB replaces prior account generator solutions and provides a more flexible and configurable way to default transaction accounts. The key building blocks of TAB include Transaction Account Definitions, Transaction Account Types, Account Rules, Mapping Sets, and Sources. Seeded TAB setup and configuration options are also described to help customers understand how TAB can be used to meet their specific account defaulting requirements.
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.
A business group is the highest level of organization and the largest grouping of employees across which you may report. A Business Group holds a complete, self-contained set of information on work structures, remuneration policies and employees. Each Business Group can have just one particular set of segments defined for its Job, Position, Grade, Employee Group and Cost Allocation key flex fields.
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.
R12 introduced a new Legal Entity architecture that separates the legal and operational aspects of an organization. The key changes include:
- Legal Entities are now distinct from Operating Units and can be mapped to multiple balancing segment values and ledgers. This allows companies to better model multi-entity structures.
- Legal Entity Configurator centralizes the setup and maintenance of legal entities, establishments, registrations, and other legal attributes.
- Legal associations link legal constructs like entities and establishments to business entities and enable tax calculations.
- The new design aims to better address legal requirements like local registrations and intercompany transactions between separate legal entities.
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.
Internal requisitions provide a mechanism for requesting inventory transfers between organizations. They allow tracking inventory as it moves between organizations and reducing costs. Key features include defining sourcing options, managing an inter-organization shipping network, and using the same process for internal and external requisitions.
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
Locator control in Oracle Inventory allows restricting items to specific storage locations called locators. This document outlines the steps to implement locator control at the organization, subinventory, and item levels including: 1) defining the stock locators flexfield, 2) setting locator control parameters, 3) defining locators, subinventories and assigning items, and 4) restricting items to specific locators and subinventories. Locator control provides accurate tracking of inventory locations for reporting and transactions.
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
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.
Oracle iProcurement is a self service based requisitioning application that controls employee purchasing. It is a key component of oracle advanced procurement, the integrated suite that dramatically cuts all the supply chain management costs. The Oracle iProcurement functionality provides the essentials for the ordering portion of the procurement process. This includes catalog content management, requisitioning, purchase order creation, and receiving orders. This webinar will deal in brief about the benefits and usages of Oracle iProcurement.
Agenda:
- Procurement process: Oracle iProcurement
- Indirect and Direct Sourcing
- Why are we switching to iProcurement?
- Various Benefits
- Oracle iProcurement Release 12 Enhancements
- Oracle iProcurement Overview
- Oracle iProcurement in Comprehensive Procure-to-Pay Flow
- Core Features of Oracle iProcurement
- Oracle Service Procurement Integration
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.
This document provides an overview of Oracle Advanced Pricing, which extends the pricing capabilities of Oracle's basic pricing module. It describes key features such as price lists, modifiers, formulas, and qualifiers that allow users to define pricing rules and adjustments. The pricing engine uses this information to select the appropriate price list, apply any eligible modifiers, and return the calculated price to calling applications.
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.
This document provides an overview of setting up a multi-organization structure in Oracle Financials R12. It discusses defining business groups, ledgers, legal entities, operating units, and inventory organizations. It also covers multi-org access control, preferences, and validation reports. The document outlines the steps to design an organization structure and then create and assign the necessary entities in the system to implement the multi-org functionality.
A trip represents a freight shipment from one location to another. It consists of at least two stops - a pick-up stop and drop-off stop. When an order is placed and lines are booked, Oracle Shipping Execution allows a transportation planner to automatically create a trip for each item from its inventory location to the customer's shipping address in one process.
1. 2-way matching verifies purchase order and invoice quantities match, 3-way adds receipt quantities, and 4-way adds acceptance documents.
2. Job hierarchy uses a single approval path while position hierarchy allows different approval paths for the same job. Setting up position hierarchy involves defining jobs, positions, mapping positions to jobs and documents, and setting approval groups.
3. Sourcing rules determine suppliers while bill of distributions determine warehouses to distribute items to.
This document provides an overview and tutorial on using Oracle Report Manager in R12. It discusses the presenter's background and objectives of the session. Key features of Report Manager are outlined, including how it provides an online repository for financial reports. The document then provides a case study example and goes through setting up Report Manager and a quick tutorial on creating a template, submitting a report, and viewing outputs. It concludes with tips, tricks and potential traps to be aware of when using Report Manager.
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 discusses configuring AP invoice line level approval using Approval Management Engine (AME) in Oracle Applications. It covers:
1. Enabling AME and invoice approval workflow
2. Creating line level attributes in AME like line amount and item type
3. Defining conditions and action types in AME
4. Setting up approval rules in AME
5. Testing the configuration using the AME test workbench
6. Viewing approval histories for invoices and lines
This document discusses Oracle's Transaction Account Builder (TAB) which is used to derive accounting flexfields for subledger transactions in Oracle Fusion Applications. TAB replaces prior account generator solutions and provides a more flexible and configurable way to default transaction accounts. The key building blocks of TAB include Transaction Account Definitions, Transaction Account Types, Account Rules, Mapping Sets, and Sources. Seeded TAB setup and configuration options are also described to help customers understand how TAB can be used to meet their specific account defaulting requirements.
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.
A business group is the highest level of organization and the largest grouping of employees across which you may report. A Business Group holds a complete, self-contained set of information on work structures, remuneration policies and employees. Each Business Group can have just one particular set of segments defined for its Job, Position, Grade, Employee Group and Cost Allocation key flex fields.
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.
R12 introduced a new Legal Entity architecture that separates the legal and operational aspects of an organization. The key changes include:
- Legal Entities are now distinct from Operating Units and can be mapped to multiple balancing segment values and ledgers. This allows companies to better model multi-entity structures.
- Legal Entity Configurator centralizes the setup and maintenance of legal entities, establishments, registrations, and other legal attributes.
- Legal associations link legal constructs like entities and establishments to business entities and enable tax calculations.
- The new design aims to better address legal requirements like local registrations and intercompany transactions between separate legal entities.
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 document outlines the steps to set up a position-based approval hierarchy in Oracle Applications to approve purchase order documents. The key steps include: defining employees, jobs, positions and assigning them; defining approval groups; assigning approval groups to positions; defining the position hierarchy; defining a buyer and users; and running a report to fill the employee hierarchy. It then provides an example of creating a purchase order, submitting it for approval, and observing it flow through the approval hierarchy based on the positions defined.
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 discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive function. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
This document provides instructions for setting up the inventory organization structure for Oracle Application R12. It includes steps for defining a primary ledger and operating unit, custom inventory responsibility, security profile, workday calendar, item master organization, locations, subinventories, and other foundational elements. The goal is to establish the necessary setup for Inbox Business Technologies to use Oracle Inventory functionality.
The document describes Oracle's purchasing requisition approval workflow. It discusses two methods for routing document approvals: approval hierarchies using job/position relationships, and employee/supervisor relationships from HR data. It provides details on setting up approval limits, hierarchies, and examples of how requisitions are routed through the approval process.
The document provides an overview of key features in Oracle Purchasing, including:
1) Basic setup such as defining users, employees, positions, buyers, multi-org access control, purchasing options, document security, and approval hierarchies.
2) Defining document types and security levels, as well as approval options.
3) Key purchasing configurations including document styles, periods, units of measure, and item setup in inventory.
4) Supplier and supplier list management which are central to the procurement process.
5) An overview of the Professional Buyer's Work Center which is a web-based interface for buyers to perform tasks like requisition management, purchase order creation, and purchase agreement setup.
This document provides a detailed overview of the procure-to-pay (P2P) process in Oracle SCM Purchasing R12, including how to create suppliers, requests for quotations (RFQs), purchase orders (POs), receipts, invoices, and post transactions to the general ledger. The presentation walks through each step, providing navigation instructions and explanations of key fields and status updates. It demonstrates the full P2P lifecycle from supplier setup to invoice payment and accounting close.
The document provides an overview of setting up and using Oracle Purchasing. It discusses key steps like defining organizational structures and flexfields, setting up suppliers, defining purchasing options and document types. It also describes the purchasing cycle from requisitions to purchase orders to receipts and payments. Key features of requisitions, RFQs, quotations, purchase agreements and purchase order types are summarized.
This document provides an overview of setting up Oracle General Ledger. It discusses defining ledger sets which includes creating a chart of accounts, calendar, currency, accounting setups and ledger sets. It also covers opening periods, journal entries, budgeting, reporting currencies, consolidations and generating standard reports. Specifically, it outlines the steps to create a chart of accounts including defining key flexfield segments, segments, value sets and qualifiers. It also describes defining period types and creating a new calendar.
Min max planning is an inventory planning method where a purchase requisition or move order is automatically created when the quantity reaches the minimum level set for a subinventory. It involves setting minimum and maximum quantities at the subinventory level and running a min max planning report to generate requisitions or move orders. The document provides step-by-step instructions on setting up min max planning at the subinventory level and running a test case to generate a requisition when the quantity falls below the minimum level.
This document discusses Oracle's purchasing functionality, including the process of creating a requisition, generating a purchase order, receiving goods, and the integration with other Oracle applications. It describes the major tables used for purchasing and receiving data, and it outlines the open interfaces and APIs available for purchasing, such as interfaces for requisitions, purchase documents, and receiving, as well as APIs for purchase order changes and cancellations. The overall goal is to discuss the purchasing process and how to integrate it with other Oracle modules.
This document provides an overview and objectives of an Oracle E-Business Suite training course. The course aims to provide a functional foundation for E-Business Suite fundamentals by demonstrating and practicing the new R12 user interface, E-Business Suite architecture, system administration fundamentals, and flexfields. Additional reference materials covered include Oracle documentation, Appsworld, MetaLink, and Oracle Technology Network. Upon completing the course, students should understand its purpose and topics, and know where to find more information.
Oracle Purchasing provides a comprehensive procurement solution that automates the entire procure-to-pay cycle. It allows purchasing professionals to reduce costs by processing requisitions, purchase orders, requests for quotation, and receipts quickly. Oracle Purchasing satisfies business needs such as replacing paper processing, regulating document access and approval, and providing related functions to finance, inventory, and customer order entry. Key benefits include automating the procure-to-pay cycle, improving supply base management, and adapting to any purchasing practice through configurable policies and open integration.
The document discusses evaluation of purchase management performance. It outlines various quantitative and qualitative metrics that can be used, including price advantage, inventory levels, and relations with suppliers. Internal and external agencies can evaluate performance. Methods include forms, flowcharts, checklists and key performance ratios. A purchase audit examines the organization, policies, procedures, evaluation and reporting of the purchase department.
The document describes the process of setting up an approval hierarchy in Oracle Apps. It involves defining jobs, positions and employees, building the position hierarchy, creating approval groups, assigning approvals, and setting the default hierarchy on document types. The example sets up a three-tier approval hierarchy for purchase orders, with purchaser, department head, and branch head approval levels based on purchase amount.
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 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.
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.
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 an overview of Oracle's Approvals Management Engine (AME). AME allows organizations to define automated approval processes and rules for transactions processed in Oracle E-Business Suite applications. It provides a framework for specifying approval rules using components like transaction types, attributes, conditions, actions, and approver groups. The document explains how to configure AME for a sample transaction type, purchase requisition approval, using these components. It also outlines the basic structure and components of AME, how applications integrate with AME, and the advantages it provides for approval automation.
Oracle Approvals Management (AME) is a tool that defines approval rules and processes for Oracle applications. It determines the approvers for a transaction based on attributes and conditions. AME generates an approver list, returns the next approver, and tracks the approval statuses. Key components of AME include transaction types, attributes, conditions, actions, approver groups, and rules. Rules associate conditions with actions to define the approval process. AME helps standardize and automate approvals across various modules and applications.
The document discusses challenges in specifying software systems and separating business rules from requirements. It provides an overview of capturing and documenting business rules, and using a requirements framework with traceability between rules and requirements. Process flows and use cases are examples given of where to identify business rules. The key point is that rules of decisions are not requirements, and managing them separately but traceably provides accuracy and agility.
The document provides an overview of the technical architecture of OpenIAM, an identity and access management solution. The architecture includes key components like an enterprise service bus, business process engine, messaging, scripting, presentation tier, security architecture, and more. OpenIAM takes a service-oriented approach and exposes over 30 services through the ESB for features like user management, authorization, provisioning, and reporting.
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.
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 new capabilities being introduced in Salesforce's Winter '07 release, including approval process automation, field updates, and outbound messages. It provides an overview of how approval processes can be defined and used to automate approval workflows. The document also describes Salesforce's new Approvals API, which allows accessing and updating approval records and requests programmatically.
A short & plain english definition of Business Rules, which are a key element in systems definition. In theory, you can express a system entirely through the constructs of Business Rules. However, in practice, there is a law of diminishing returns in this effort, which the practitioner begins to sense through experience. The need to identify business rules as early as possible in the discovery phase is increasingly driven by the possibility to feed these rules together with process maps and thereby automatically generate executable code
The document discusses regulatory requirements for trade reporting and monitoring from FINRA, NASDAQ, and other agencies. It covers requirements around accepting trades within 20 minutes on NASDAQ, reporting trades to the Order Audit Trail System (OATS) according to specific data elements and timestamps. FINRA can measure compliance for OATS and TRACE (Trade Reporting and Compliance Engine) based on metrics like late submissions and unmatched reports. The document also provides an example audit approach and discusses direct market access (DMA) tools, associated risks, and evolving governance/regulations.
The document provides guidance on assisting with policy development for client support by outlining the steps for modifying a system according to requested changes. It describes leading practices for change management processes including defining change models, roles and responsibilities, the standard change process flow with activities like planning, testing, approval and documentation, as well as approaches for expedited and emergency changes. It stresses the importance of change management tools and implementing a process improvement program to continuously assess and enhance the change processes.
Oracle hcm cloud configuring approval workflowFeras Ahmad
Oracle HCM Cloud uses human workflow automation to route approval tasks through a predefined sequence. It controls workflows for processes like hiring and promotions. Users can define simple or complex task routing policies. The system is integrated with HCM to determine approvers based on factors like supervision hierarchy, responsibilities, and job level. Workflows allow humans to interact with processes, such as approving purchases. They provide full task lifecycle management including rerouting, escalating, and setting deadlines. An example transfer workflow is configured to require approval from a user if the employee's current salary is over $9,000 and in the sales department. Workflows integrate with personnel records to update status.
Evaluating Service Organization Control ReportsJay Crossland
Service Organization Control (SOC) reports evaluate the controls at service organizations and their impact on user entities. With the Sarbanes-Oxley Act of 2002, user entities were required to thoroughly evaluate SOC reports from their service organizations. However, most user entities do not fully understand SOC reports and how to properly assess them. A comprehensive evaluation of a SOC report examines factors like the scope, standards used, control objectives tested, and any issues or deficiencies identified.
Itil v3 foundation study guide service transitionMuhammad Zamzani
Service Transition is concerned with managing changes to services and introducing new or changed services into the live environment. It aims to minimize disruption and ensure designs are properly implemented. Key activities include recording change requests, reviewing and authorizing requests, planning changes, coordinating implementation, and reviewing after implementation. Related processes are configuration management, change management, release and deployment management.
Business Systems Analyst Interview Questions and AnswersHireQuotient
The Business Systems Analyst plays a crucial role in bridging the gap between business needs and technical solutions within an organization. They are responsible for analyzing business processes, identifying system requirements, and facilitating the successful implementation of technology solutions.
The questions are designed to assess a candidate's knowledge, skills, and experience in these areas, enabling you to identify top candidates who can effectively analyze and optimize business systems to drive operational efficiency and meet organizational goals.
To read the full QnA article, visit https://www.hirequotient.com/blog/business-systems-analyst-interview-questions-and-answers
Improve your entire buying and settlement process end-to-end—or just part of it—with AutoKrew Purchase a.k.a Procurement Solutions. You’ll experience more speed, performance, reach, and usability once the right solution is seamlessly integrated with your ERP.
For Demo, Contact: info@autokrew.com / visit: www.autokrew.com or call +91-9537765656
Trusted Execution Environment for Decentralized Process MiningLucaBarbaro3
Presentation of the paper "Trusted Execution Environment for Decentralized Process Mining" given during the CAiSE 2024 Conference in Cyprus on June 7, 2024.
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
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.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...Tatiana Kojar
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
A Comprehensive Guide to DeFi Development Services in 2024Intelisync
DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum.
In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance.
In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape.
At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology.
Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
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.
Introduction of Cybersecurity with OSS at Code Europe 2024
Ame concepts
1. Oracle Approval Management Engine Concepts
Ranu Srivastava- Oracle Apps Consultant http://apps2fusion.com
Overview of Oracle Approvals Management ........................................................................................1
Implementing Oracle Approvals Management ......................................................................................5
Implementing Tasks Approvals Management.......................................................................................6
Implementing the Transaction Type ......................................................................................7
Attributes .............................................................................................................................8
Required Attributes .................................................................................................................9
How does AME use Attributes?.............................................................................................9
Planning Your Test Cases (test on AME work Bench) ..........................................................12
Administration ...........................................................................................................................12
Example of Setting Approval rules ....................................................................................................13
Administration ...............................................................................................................................14
Overview of Oracle Approvals Management
The purpose of Oracle Approvals Management (AME) is to define approval rules that determine the
approval processes for Oracle applications..
Approval Rules
2. Oracle Approval Management Engine Concepts
Ranu Srivastava- Oracle Apps Consultant http://apps2fusion.com
An approval rule is a business rule that helps determine a transaction’s approval process. Rules are
constructed from conditions and actions.
The approval rule’s if part consists of zero or more conditions, and its then part consists of one or
more actions. A condition consists of a business variable (in AME, an attribute) and
a set of attribute values, any one of which makes the condition true. An action tells AME to modify
a transaction’s approval process in some fashion
AME enables you to define rules that express a wide variety of approval rules. For example, rules
that:
• Require subject-matter-expert approval
• Require managerial approval
• Create exceptions for rules requiring managerial approval
• Substitute one approver for another in special cases
• Revoke a manager’s signing authority in special cases
• Grant a manager extra signing authority in special cases
• Generate a production that assigns a value to a variable name such as the value digital certificate
to the variable name eSignature.
• Send for-your-information notifications.
You can prioritize the approval rules. This enables you to apply rules of sufficient priority to any
given transaction.
Transaction Types
An application that uses AME to govern its transactions’ approval processes is termed an
integrating application. An integrating application may divide its transactions into
several categories where each category requires a distinct set of approval rules. Each set of rules is
called a transaction type. Different transaction types can use the same attribute name to represent
values that are calculated in different ways or fetched from different places. This allows several
transaction types to share approval rules (thereby implementing a uniform approval policy across
multiple
transaction types). A rule use occurs when a transaction type uses a particular rule for a given time
period, optionally at a given priority level.
A transaction’s approval process can have two components:
• List of approvers
3. Oracle Approval Management Engine Concepts
Ranu Srivastava- Oracle Apps Consultant http://apps2fusion.com
• Set of productions
Approver Lists
A transaction’s approver list has a hierarchical structure. The transaction’s approver list may contain
several items’ approver lists. Each item’s approver list may have three
sub-lists. Of these sub-lists, the authority sub-list can have a chain of authority generated by one or
more action types. Each approver group or chain of authority can contain multiple approvers.
Items
AME can generate an approver list for a transaction’s header, and a separate approver list for each
item in the transaction. A transaction type can define multiple item
classes. For example, a transaction type might generate separate approver lists for each
transaction’s header, line items, and cost centers. All transaction types include a
header item class, which always has one item (the transaction’s header). All other item classes are
optional.
Sub-Lists
An item’s approver list may contain three sub-lists:
• Pre-chain of authority
• Authority
• Post-chain of authority
The pre- and post-chain sub-lists contain zero or more approver groups; the authority sub-list
contains zero or more chains of authority.
Action Types
An action type is a set of actions having a common purpose. Each sub-list can contain approver
groups or chains of authority generated by several action types. For
example, actions in the absolute-job-level action type all generate chains of authority by ascending
the HR supervisory hierarchy until they reach a manager with a particular job level.
The actions differ according to the job levels they require.
Approver Groups
An approver group is a collection of approvers that you define. Typically, approver groups contain
subject-matter experts.
Chains of Authority
A chain of authority ascends a hierarchy of approvers that are normally defined in applications other
than AME, for example HRMS (supervisor position hierarchies). The
start point of the chain, and how far it ascends the hierarchy, usually varies between transactions.
You can also treat an approver group as a chain of authority. In this
case AME ignores the approver group’s group-specific properties. Generally, chains of authority
contain managers. Approver groups and chains of authority behave differently in certain
circumstances.
For example, when one approver forwards a notification requesting approval to another approver.
Otherwise, approver groups and chains of authority behave similarly.
Approvers
An approver has the following two properties:
• Approver Types
An approver type is any Workflow Directory Services originating system that defines entities, which
can receive Workflow notifications requesting an approval. For
example, the HR application defines its set of employees as a Directory Services originating
system, so an HR employee can be an approver.
• Approver Categories
AME can generate approvers belonging to either of two approver categories: action and
informational (for-your-information or FYI) approvers. Action approvers must
approve a transaction. FYI approvers merely receive a notification describing the transaction. The
exact content of all notifications depends on the application that
generates the notification.
Productions
4. Oracle Approval Management Engine Concepts
Ranu Srivastava- Oracle Apps Consultant http://apps2fusion.com
In AME, a production assigns a value to a variable name. For example, AME might generate a
production that assigns the value digital certificate to the variable name
eSignature. AME does not interpret the productions it generates. In fact, AME does not even define
any standard production variable names. Rather, it leaves these tasks
to integrating applications and their transaction types. AME generates two kinds of productions:
• Transaction-level productions that are variable name or value pairs associated with a whole
transaction.
• Approver-level productions are associated with specific approvers within a transaction’s approver
list.
What Happens at Run Time
Once you have defined a set of rules for a transaction type, and the application associated with the
transaction type is configured to use AME, the application communicates directly with AME to
manage the transaction type’s approval processes. Typically, the application communicates with
AME when a transaction is initiated in the application, and then each time an approver responds to
the application’s request for approval of the transaction, until all approvers have approved the
transaction. AME records each approval, and recalculates the approver list for a transaction each
time an approver responds to a request for approval of the transaction.
AME recalculates the approver list each time an approver responds. This enables AME
to account for several possible circumstances that can affect a transaction’s approver list:
• An attribute value changes, thereby affecting which conditions are true and so which
rules apply to the transaction.
• A condition or rule is added, changed, or deleted, again affecting which rules apply
to the transaction.
• A change occurs in the organizational hierarchy used by the transaction type’s set of
rules, thereby changing the membership of the applicable chain of authority.
• Currency exchange rates change, thereby affecting which conditions on currency
attributes are true and so which rules apply to the transaction.
By accounting for such changes, AME guarantees that transactions are always approved
according to the most current business data possible.
Approval Process Execution
Approval-Process Execution
Integrating applications can communicate with AME in many different ways. For example, an
integrating application can ask AME for a transaction’s entire approver
list, for the rules satisfied, or for the set of approvers the application should notify next.
The Standard Algorithm
Typically, an integrating application follows a simple procedure for managing a transaction’s
approval process:
1. Ask AME for a transaction’s entire approver list.
2. Display the approver list to the requestor, optionally prompting them to suppress or add
approvers.
3. Communicate any approver suppressions or additions to AME.
4. Ask AME whether the transaction’s approval process is complete, and if not, what approvers (if
any) to notify.
5. If AME indicates that no further approvals are required, stop.
6. Notify any approvers identified by AME in step 5.
7. Wait until an approver responds to a notification.
8. Communicate the response to AME.
9. Go to step 4.
Approver-Notification Order
The order in which AME presents approvers for notification at step 4 of the standard algorithm
depends on a variety of ordering modes and order numbers that together
5. Oracle Approval Management Engine Concepts
Ranu Srivastava- Oracle Apps Consultant http://apps2fusion.com
determine a unique ordering of the approvers in a transaction’s approver list.An ordering mode tells
AME how to order the collections of approvers at a given level of
the hierarchy constituting a transaction’s approver list. For example, the sub-list ordering mode
basically tells AME whether to notify pre-approvers at the same time as authority approvers, all
other things being equal. AME typically uses ordering modes, before a transaction is submitted to
AME for approval, where the number of things to be ordered is unknown. For example the
approvers generated by a particular action type maybe notified sequentially or in parallel.Order
numbers establish a fixed ordering of a collection of approvers at a given level of the hierarchy
constituting a transaction’s approver list, for example, the approvers in an approver group are
assigned order numbers. Order numbers are not necessarily unique. Thus several approvers in an
approver group can have the same order number. AME typically uses order numbers where you
know the number of things to be ordered before a transaction is submitted to AME for approval.
Implementing Oracle Approvals Management
Configuration Variables
The configuration variables you should consider when implementing approvals business
cases are:
• adminApprover
• allowAllApproverTypes
• allowAllItemClassRules
• allowFyiNotifications
• productionFunctionality
• purgeFrequency
6. Oracle Approval Management Engine Concepts
Ranu Srivastava- Oracle Apps Consultant http://apps2fusion.com
• repeatedApprovers
• distributedEnvironment
• currencyConversionWindow
• rulePriorityModes
• forwardingBehaviors
Mandatory Attributes
The mandatory attributes related to implementing approvals business cases are:
• ALLOW_DELETING_RULE_GENERATED_APPROVERS
• ALLOW_REQUESTOR_APPROVAL
• AT_LEAST_ONE_RULE_MUST_APPLY
• EFFECTIVE_RULE_DATE
• EVALUATE_PRIORITIES_PER_ITEM
• REJECTION_RESPONSE
• REPEAT_SUBSTITUTIONS
USE_RESTRICTIVE_ITEM_EVALUATION
• USE_WORKFLOW
• WORKFLOW_ITEM_KEY
• WORKFLOW_ITEM_TYPE
Approver Groups
You must create or include approver groups in your transaction type.
Rules and Rule Use If your organization has more than a few approvals rules, it can be useful to
represent the rules in an approvals matrix or a decision tree. An approvals matrix is just a table that
had one row per rule.
Implementing Tasks Approvals Management
To implement AME, you need to carry out the following steps:
1. Install the application.
AME’s installation routines and administration features determine which applications can use AME.
Installation and administration are typically jobs for a
technical specialist. Installation is generally done only once, and administrative tasks (using AME’s
Administrator Dashboard) are usually only necessary to enable a new
application to use AME, or to access or clear a transaction’s error log.
2. Set up AME security by completing the following:
• Attach the predefined roles to a user or group of users.
AME uses the Role Based Access Model (RBAC) to provide users access to AME functions. This
access model has the following predefined roles:
• Approvals Management Administrator
• Approvals Management Analyst
• Approvals Management System Viewer
• Approvals Management System Administrator
• Approvals Management Process Owner
Each of the five predefined roles has a specific set of functional grants. The grants provide users
access to AME. To enable functional grants, you must assign roles
to users using the User Management page. For information about accessing User Management
page, see: Oracle Applications System Administrator’s Guide
- Security.
Set up user access as follows:
1. Login as Administrator.
2. Select the User Management responsibility.
3. Select the Users page.
4. Search for the user to whom you wish to grant AME roles.
5. In the results table, click Update. In the Update User page, you can view
user details along with a list of roles available to the user.
6. Click Assign Roles.
7. Select the roles from the resulting list and click Apply.
7. Oracle Approval Management Engine Concepts
Ranu Srivastava- Oracle Apps Consultant http://apps2fusion.com
When you assign any of the five predefined roles to a user, you are indirectly assigning AME
responsibilities to the user. Grant data access to users.As AME restricts access to transaction types
using Data Security, you grant users access to the transaction types using the Grants page. Set up
user access as follows:
1. Login as Administrator.
2. Select the Functional Administrator responsibility.
3. Select the Grants tab.
4. Click Create Grant.
5. Select Specific User as grantee type.
6. Select the user as grantee key.
7. Select AME Transaction Types as object:
1. All rows: This grants access to all AME Transaction Types to the User
2. Instance: This grants access to a specific AME Transaction Type
specified by the following parameters: FND_APPLICATION_ID =>
Application ID of the application to which the transaction type belongs
TRANSACTION_TYPE_ID => Unique identifier of the AME Transaction
type within application
3. Instance set: This grants access to one or more AME Transaction Types
specified by the following parameters:
• Use the predefined instance set AME Transaction Type Instance Set.
• In the next page, select FND_APPLICATION_ID as Parameter1
and a wild card search string for TRANSACTION_TYPE_ID as
Parameter2.
8. In the next page there will be three options for instance type: select AME
Calling Applications as the permission set.
9. Review and Finish.
3. Set the user profile - AME:Installed
4. Configure transaction types.
An application administrator should review AME’s configuration-variable values as soon as AME is
installed and its security has been set up. AME has the following
kinds of configuration variables:
• Single-Valued Configuration Variables AME’s configuration variable distributedEnvironment has a
single value for the entire application. This variable describe various aspects of AME’s computing
environment. You must set its value for AME to function properly.
• Transaction-Type-Specific Variables
Other AME configuration variables can have a default value, as well as a value
for each transaction type. These variables are:
• adminApprover
• allowAllApproverTypes
• allowAllItemClassRules
• allowFyiNotifications
• currencyConversionWindow
• forwardingBehaviors
• productionFunctionality
• purgeFrequency
• repeatedApprovers
• rulePriorityModes
These variables determine many aspects of how AME generates a transaction type’s approval
processes and are similar to the mandatory attributes. The difference is, their values are always
constant for all transactions in the transaction type. Ensure you are satisfied with these variables’
default values before using AME.
Implementing the Transaction Type
To implement the transaction type, you need to specify or create, if required, the following
components of the approval process:
8. Oracle Approval Management Engine Concepts
Ranu Srivastava- Oracle Apps Consultant http://apps2fusion.com
1. Create item-class use (Optional).
2. Create transaction attributes (Optional). In AME, an attribute is a named business variable such
as TRANSACTION_AMOUNT, whose value AME fetches at run time, when it constructs
transactions’approver lists.
3. Create conditions (Optional). In AME, a condition specifies a list or range of attribute values
required to make a rule apply to a transaction. For example:
Example USD1000 < TRANSACTION_AMOUNT < USD5000
4. Create approver groups (Optional).
You can create AME rules to include one or more approver groups in a transaction’s approver list.
5. Prepare to use the action types. You add action types to a transaction type using the Action
Types tab.
• Predefined action and approver types
• Custom action and approver types
• Add approvals to existing approval types
• Preparing to use the Job-Level approval types
6. Define approval rules.
7. Test approval rules.
8. Create custom transaction types.
9. Configure Oracle applications to use AME.
Running the Approvals Management Post Upgrade Process : Management Post Upgrade
Process concurrent job
Attributes
Attributes are business variables with a single value for a particular transaction.
9. Oracle Approval Management Engine Concepts
Ranu Srivastava- Oracle Apps Consultant http://apps2fusion.com
Eg select item_quantity from some_application_table where transaction_id = :transactio
Mandatory Attributes
ALLOW_DELETING_RULE_GENERATED_APPROVERS
ALLOW_REQUESTOR_APPROVAL
AT_LEAST_ONE_RULE_MUST_APPLY
REJECTION_RESPONSE
USE_RESTRICTIVE_ITEM_EVALUATION
USE_WORKFLOW
WORKFLOW_ITEM_KEY
WORKFLOW_ITEM_TYPE
Required Attributes
ALLOW_EMPTY_APPROVAL_GROUPS
FIRST_STARTING_POINT_PERSON_ID
INCLUDE_ALL_JOB_LEVEL_APPROVERS
TRANSACTION_REQUESTOR_PERSON_ID
How does AME use Attributes?
When AME starts to calculate a transaction’s approver list at run time, it does the following:
1. It fetches the values of each attribute that is active for the transaction type.
2. After fetching all of the active attributes’ values, AME checks whether each of a transaction
type’s rules applies to the transaction.
Conditions
The if part of an approval rule consists of zero or more conditions. A condition is a statement that is
either true or false, for a given transaction.
10. Oracle Approval Management Engine Concepts
Ranu Srivastava- Oracle Apps Consultant http://apps2fusion.com
There are two types of conditions:
• Regular, which has Ordinary and Exception conditions eg 1,000 <= TRANSACTION_AMOUNT <
2,000
• List-modifiers : A list-modification condition checks for the presence of a given target approver at a
specific set of allowed locations in the default approver list. When the target approver is present in
an allowed location, we say that the default approver list satisfies the condition.
Actions
An action is an instruction to AME to modify a transaction’s approval process in the manner you
specify. Every action belongs to an action type. An action type is a collection of actions having
similar functionality
Action type Properties
Name, Action-Type Handlers, Rule Types, Allowed Approver Types, Voting Methods..
11. Oracle Approval Management Engine Concepts
Ranu Srivastava- Oracle Apps Consultant http://apps2fusion.com
Approver Groups An approver group can either be an ordered set of one or more approvers
(persons and/or user accounts) or it can be a list, which is dynamically generated at rule evaluation
time. A typical pre- or post-approval rule adds an approver group’s members (in order) to a
transaction’s approver list.
Example
COMP_APP_1 = {Jim Small} COMP_APP_2 = {COM_APP_1, Jane Smith} COMP_APP_3 =
{COMP_APP_2, Liz Large}
AME would evaluate the membership of COMP_APP_3 to be (Jim Small, Jane Smith, Liz Large}, in
that order.
If ITEM_CATEGORY in {COMPUTER_HARDWARE} and ITEM_AMOUNT <= 1,000
USD then require post-approval from the COMP_APP_1 group.
Example
If ITEM_CATEGORY in {COMPUTER_HARDWARE} and 1,000 USD < ITEM_AMOUNT <= 10,000
USD then require post-approval from the COMP _APP_2 group.
Example
If ITEM_CATEGORY in {COMPUTER_HARDWARE} and 10,000 USD < ITEM_AMOUNT then
require post-approval from the COMP_APP_3 group.
ALLOW_EMPTY_APPROVAL_GROUPS. When this attribute has the value ’true’, AME allows an
approver group not to have any members at run time.
when to use an approver group:
Using Approver groups for Pre- and Post-Approvals
Using Approver groups for Chain of Authority Approvals
Approver Group Properties Name, Description, Voting Regime, Active List(statuc & Dynamic
member list)..
Select ’PER:’||person_id from invoice_table where transaction_id = :transactionId and item_class = :itemClass
and item_id = :itemId
Rules : Creating rules and rule use are the main steps in the AME implementation process. Rule
associate one or more conditions with an approval in an if-then statement. Before you can create
rules, you must create conditions for the rules to use. You may need to create (or have a system
administrator create) some custom attributes and/or approvals. You may also need to create some
approver groups.
12. Oracle Approval Management Engine Concepts
Ranu Srivastava- Oracle Apps Consultant http://apps2fusion.com
Rule Types : There are eight rule types in AME. Seven of them provide rules that participate in
generating transactions’ approver lists; these are the approver-generating rule types. The eighth
generates productions.
• List-creation rules If TRANSACTION_AMOUNT < 1000 USD, then require approvals up to at least
job level 2.
• List-creation exceptions If TRANSACTION_AMOUNT < 500 USD and Exception: COST_CENTER
is in {0743}, then require approvals up to at least job level 1.
• List-modification rules If TRANSACTION_AMOUNT > 1000 USD and the final approver is: Kathy
Mawson, then require approvals at least one level up.
• Substitutions If TRANSACTION_AMOUNT < 500 USD and CATEGORY in
{MISCELLANEOUSOFFICE EXENSES} and any approver is: John Doe, then substitute Jane Smith
for the approver.
• Pre-list approval-group rules If TRANS_AMOUNT < 1000 USD and CATEGORY_NAME in
{Marketing Event}, then require pre-approval from Marketing Approvals Group.
• Post-list approval-group rules
• Combination Rules
• Production Rules
Rule Properties : Actions, Start and End Dates, Item Class
The purpose of rule priorities is to prioritize a transaction type’s rules and, at run time, remove
from the set of rules that would otherwise apply to a transaction, those
rules of insufficient priority. A rule priority is a positive integer associated with a rule within a
transaction type.
Planning Your Test Cases (test on AME work Bench)
While planning you implementation strategy, your implementation document, showing your approval
policies, should specify test cases sufficient to verify that your transaction type does the following
things according to your business rules:
• Fetch correct item IDs.
• Fetch correct attribute values.
• Evaluate the rule use correctly.
• Process the rule use priorities correctly.
• Process production rules and actions correctly.
• Produce the correct default approver list.
• For real transactions, handle inserted approvers correctly.
• For real transactions, handle suppressed approvers correctly.
• Process repeated approvers correctly.
• Parallelize a transaction’s approval process correctly.
• Process forwardings correctly.
Administration
The Administrator Dashboard is available only to users with the Application Administrator
responsibility. You can use this dashboard to maintain AME’s
configuration variables and transaction types. Additionally, you can view and analyze AME’s
runtime exceptions.An AME application administrator has many tasks. As an application
administrator, you can perform the following application and transaction-type administrative tasks:
• Set the configuration variables’ default values (application-wide values)
• Set the transaction type’s configuration variables’ values
• Create a transaction type
• Update a transaction type
• Delete a transaction type
• View the exception log
• Clear the exception log
13. Oracle Approval Management Engine Concepts
Ranu Srivastava- Oracle Apps Consultant http://apps2fusion.com
• Run the Setup report
Example of Setting Approval rules
Step1
Step2
Step3
Step4