OAUG Training Tuesdays

Please note: Each session will be presented twice on the date listed. All sessions are scheduled to last one hour unless otherwise specified.

Session times are listed in U.S. Eastern (New York) Time. Click on the Eastern Time for a specific session to calculate the corresponding time in your time zone. Click on a session name to register for that session.

« View Previous Month View Current Month View Next Month » View OAUG Community Wednesdays View OAUG Community Thursdays
 
January 15, 2008
  • Session 1
    January 15, 2008 12:00 PM U.S. Eastern (New York) Time
    Security Management: Managing User Access to Your Company's Information
    In today’s world, lots of companies are focusing on their core competency and are outsourcing the other functions to different vendors. For example, a manufacturing company (information owner) can outsource the customer sales to different companies (henceforth called sales reps) depending upon the geographical areas /customer orientation or product expertise. Outsourcing would mean that the sales reps would have access to the company’s ERP. However, the company would like to restrict the information access to sales reps, so that one salesrep should not view or update other salesrep data. Similarly across departments within an organization, the users should not access other department’s data. With Oracle 11.5.10, organizations can use Data Security to manage permission assignments that control access to objects. Data Security policies can only be defined for applications that have been written to leverage the Data Security Framework. The Data Security Policy restricts operations so that they only can be performed on a subset of instances of the corresponding database object. Using the function developer responsibility, you can define the data security policy, which will restrict the access to an instance of an object (an object can be a business entity, for example – user, pricelists etc). Implementation of data security can be done in the following ways: • Creation of data security policy - Securing access to an object • Granting access to a set of functions, to a user or a group of users • A combination of above two Data security policies can reflect access to: • A specific instance (row) identified by a primary key value • All instances (rows) of an object • An instance set defined by a SQL predicate (WHERE clause) With the help of Oracle User Management, you can set up access control and security policies in Oracle Applications by defining roles, role inheritance hierarchies, role categories, and registration processes. These components specify the different levels of access to various application menus and data that are available. This paper explains the implementation of the Security policy using Oracle User Management for managing access to various business entities for example (but not limited to) Sales Orders, Pricelists and customer master information.
    Session Closed
    Presenter, Company: Tarun Dhawan, Oracle

  • Session 2
    January 15, 2008 8:00 PM U.S. Eastern (New York) Time
    Security Management: Managing User Access to Your Company's Information
    In today’s world, lots of companies are focusing on their core competency and are outsourcing the other functions to different vendors.

    For example, a manufacturing company (information owner) can outsource the customer sales to different companies (henceforth called sales reps) depending upon the geographical areas /customer orientation or product expertise.
    Outsourcing would mean that the sales reps would have access to the company’s ERP. However, the company would like to restrict the information access to sales reps, so that one salesrep should not view or update other salesrep data.
    Similarly across departments within an organization, the users should not access other department’s data.

    With Oracle 11.5.10, organizations can use Data Security to manage permission assignments that control access to objects. Data Security policies can only be defined for applications that have been written to leverage the Data Security Framework. The Data Security Policy restricts operations so that they only can be performed on a subset of instances of the corresponding database object.

    Using the function developer responsibility, you can define the data security policy, which will restrict the access to an instance of an object (an object can be a business entity, for example – user, pricelists etc).
    Implementation of data security can be done in the following ways:
    • Creation of data security policy - Securing access to an object
    • Granting access to a set of functions, to a user or a group of users
    • A combination of above two

    Data security policies can reflect access to:
    • A specific instance (row) identified by a primary key value
    • All instances (rows) of an object
    • An instance set defined by a SQL predicate (WHERE clause)

    With the help of Oracle User Management, you can set up access control and security policies in Oracle Applications by defining roles, role inheritance hierarchies, role categories, and registration processes. These components specify the different levels of access to various application menus and data that are available.

    This paper explains the implementation of the Security policy using Oracle User Management for managing access to various business entities for example (but not limited to) Sales Orders, Pricelists and customer master information.

    Available Seats: 22
    Presenter, Company: Tarun Dhawan, Oracle

January 22, 2008
  • Session 1
    January 22, 2008 9:00 AM U.S. Eastern (New York) Time
    Using the Approvals Management Engine (AME) for Self-Service Human Resources
    Get the most out of using AME with SSHR. Set up attributes, conditions, rules, and approval chains using your existing job hierarchies—then go further and learn how to increase the power of AME by capturing current transaction values and customizing the approvals Workflow to meet the most exacting business rules.
    Available Seats: 8
    Presenter, Company: Mary Hammes, Marquette University

  • Session 2
    January 22, 2008 12:00 PM U.S. Eastern (New York) Time
    Credit Management: An Easy Solution for Evaluating Customer Creditworthiness
    Every business grapples with the need to evaluate the creditworthiness of customers/prospects. This task becomes increasingly challenging with the growing customer base. Credit Analysts spend valuable time trying to manually gather, store and analyze information stored in disparate systems.
    Oracle Credit Management provides a seamless process for evaluating creditworthiness of customers and prospects. It provides a framework to capture and store a wealth of internal and external data including integration with D&B.
    The module is flexible to allow creation of credit policies tailored to meet any business needs.
    This paper is based on an implementation at TIBCO Software Inc., where the credit evaluation process is being streamlined using Oracle Credit Management module.

    Available Seats: 20
    Presenter, Company: Usha Raghavan, Ubex Corporation

  • Session 3
    January 22, 2008 5:00 PM U.S. Eastern (New York) Time
    Using the Approvals Management Engine (AME) for Self-Service Human Resources
    Get the most out of using AME with SSHR. Set up attributes, conditions, rules, and approval chains using your existing job hierarchies—then go further and learn how to increase the power of AME by capturing current transaction values and customizing the approvals Workflow to meet the most exacting business rules.
    Available Seats: 14
    Presenter, Company: Mary Hammes, Marquette University

  • Session 4
    January 22, 2008 8:00 PM U.S. Eastern (New York) Time
    Credit Management: An Easy Solution for Evaluating Customer Creditworthiness
    Every business grapples with the need to evaluate the creditworthiness of customers/prospects. This task becomes increasingly challenging with the growing customer base. Credit Analysts spend valuable time trying to manually gather, store and analyze information stored in disparate systems.
    Oracle Credit Management provides a seamless process for evaluating creditworthiness of customers and prospects. It provides a framework to capture and store a wealth of internal and external data including integration with D&B.
    The module is flexible to allow creation of credit policies tailored to meet any business needs.
    This paper is based on an implementation at TIBCO Software Inc., where the credit evaluation process is being streamlined using Oracle Credit Management module.

    Available Seats: 24
    Presenter, Company: Usha Raghavan, Ubex Corporation

January 29, 2008
  • Session 1
    January 29, 2008 9:00 AM U.S. Eastern (New York) Time
    Oracle Applications in a High-Volume, Configure-to-Order Environment
    Many businesses are continually striving to shorten cycle times throughout their manufacturing and distribution processes. This is particularly challenging for businesses that operate in a high-volume, configure-to-order environment.

    This presentation will demonstrate to attendees how Oracle Applications can effectively be used to support lean manufacturing within a high-volume, configure-to-order environment. The total solution presented will include support for the following business processes:
    • Manual and electronic order entry and processing
    • Automated product configuration based on customer input
    • Automated product pricing based on the customer’s chosen configuration
    • Integration with shop floor control systems and automated manufacturing equipment
    • Automated processing of Oracle manufacturing and distribution transactions

    The solution presented has been used to support a business that manufactures and ships over 25,000 items per day from seven manufacturing plants spread across the U.S.

    Technical details of the presentation will explain how this solution was accomplished with creative use of standard Oracle Applications functionality, and without invasive customizations to the Oracle Applications.

    Technical touch points will include:
    • How to programmatically invoke standard product configuration functionality
    • Integration with manufacturing shop floor control systems


    Available Seats: 8
    Presenter, Company: Glenn Gesell, OSI Consulting

  • Session 2
    January 29, 2008 12:00 PM U.S. Eastern (New York) Time
    Drop Ship Enhancements - An inclusive analysis
    The drop shipments’ functionality in R11i10 enables drop ship across sets of books and provides enhanced change management features that synchronize the Order Management and Purchasing applications. This paper elucidates these advanced facets of Drop Shipments, including return flow, and outlines the benefits, challenges and limitations in its implementation.

    Drop Shipments engender an organization fulfill customer demands from a vendor directly. The need to support enhancements in this functionality, within Oracle, stems from a multitude of developments in the manufacturing landscape - increased outsourcing of fully finished assemblies and global procurement, to mention just a few.

    In a conventional Drop Ship scenario, the material shipped by the vendor is logically received in a warehouse, within the operating unit of the selling organization. With 11.5.10, it’s now possible to select a warehouse that’s a part of a different operating unit, legal entity or set of books. Furthermore, intercompany accounting transactions can be between different sets of books. And any change in customer demand can be reflected in the company’s demands on the vendor, automatically.

    The two different scenarios that have been enhanced are Drop Ship across Sets of Books (1) and Distribution Center Drop ship (2). In (1), the sales order is placed in an operating unit and the receiving organization is chosen to be one from a different operating unit. The purchase requisitions and purchase order are created in the second operating unit. In scenario (2), the sales order and purchase requisition are placed in one operating unit and the purchase order in another. In both the scenarios, the requisition gets created in the operating unit of the warehouse. And the intercompany transactions can be performed when the delivery occurs in Purchasing the sales order line is fulfilled in Order Management.

    Change Management lets the change in customer demand (in Order Management), visible to Purchasing. As with normal changes, this would trigger a reapproval of the purchase order. This feature can be controlled by the use of a seeded processing constraint, which can either permit or forbid cascading the changes, after purchase order approval.

    Thus the enhanced features can be leveraged by companies that have the need to source strategically and meet the changing customer demands, while increasing their cost effectiveness. This functionality has augmented the existing one, significantly, and could lead to increased process efficiencies while reducing the need for application customizations.

    Available Seats: 10
    Presenter, Company: Krishnan Sundaresan, Fujitsu America, Inc.

  • Session 3
    January 29, 2008 5:00 PM U.S. Eastern (New York) Time
    Oracle Applications in a High-Volume, Configure-to-Order Environment
    Many businesses are continually striving to shorten cycle times throughout their manufacturing and distribution processes. This is particularly challenging for businesses that operate in a high-volume, configure-to-order environment.

    This presentation will demonstrate to attendees how Oracle Applications can effectively be used to support lean manufacturing within a high-volume, configure-to-order environment. The total solution presented will include support for the following business processes:
    • Manual and electronic order entry and processing
    • Automated product configuration based on customer input
    • Automated product pricing based on the customer’s chosen configuration
    • Integration with shop floor control systems and automated manufacturing equipment
    • Automated processing of Oracle manufacturing and distribution transactions

    The solution presented has been used to support a business that manufactures and ships over 25,000 items per day from seven manufacturing plants spread across the U.S.

    Technical details of the presentation will explain how this solution was accomplished with creative use of standard Oracle Applications functionality, and without invasive customizations to the Oracle Applications.

    Technical touch points will include:
    • How to programmatically invoke standard product configuration functionality
    • Integration with manufacturing shop floor control systems


    Available Seats: 16
    Presenter, Company: Glenn Gesell, OSI Consulting

  • Session 4
    January 29, 2008 8:00 PM U.S. Eastern (New York) Time
    Drop Ship Enhancements - An inclusive analysis
    The drop shipments’ functionality in R11i10 enables drop ship across sets of books and provides enhanced change management features that synchronize the Order Management and Purchasing applications. This paper elucidates these advanced facets of Drop Shipments, including return flow, and outlines the benefits, challenges and limitations in its implementation.

    Drop Shipments engender an organization fulfill customer demands from a vendor directly. The need to support enhancements in this functionality, within Oracle, stems from a multitude of developments in the manufacturing landscape - increased outsourcing of fully finished assemblies and global procurement, to mention just a few.

    In a conventional Drop Ship scenario, the material shipped by the vendor is logically received in a warehouse, within the operating unit of the selling organization. With 11.5.10, it’s now possible to select a warehouse that’s a part of a different operating unit, legal entity or set of books. Furthermore, intercompany accounting transactions can be between different sets of books. And any change in customer demand can be reflected in the company’s demands on the vendor, automatically.

    The two different scenarios that have been enhanced are Drop Ship across Sets of Books (1) and Distribution Center Drop ship (2). In (1), the sales order is placed in an operating unit and the receiving organization is chosen to be one from a different operating unit. The purchase requisitions and purchase order are created in the second operating unit. In scenario (2), the sales order and purchase requisition are placed in one operating unit and the purchase order in another. In both the scenarios, the requisition gets created in the operating unit of the warehouse. And the intercompany transactions can be performed when the delivery occurs in Purchasing the sales order line is fulfilled in Order Management.

    Change Management lets the change in customer demand (in Order Management), visible to Purchasing. As with normal changes, this would trigger a reapproval of the purchase order. This feature can be controlled by the use of a seeded processing constraint, which can either permit or forbid cascading the changes, after purchase order approval.

    Thus the enhanced features can be leveraged by companies that have the need to source strategically and meet the changing customer demands, while increasing their cost effectiveness. This functionality has augmented the existing one, significantly, and could lead to increased process efficiencies while reducing the need for application customizations.

    Available Seats: 19
    Presenter, Company: Krishnan Sundaresan, Fujitsu America, Inc.