1 / 73

R12 Enhancements to Oracle Project Contracts

R12 Enhancements to Oracle Project Contracts. TBD. Agenda. R12 Release Overview Usability Enhancements Security Enhancements Improved Integration with Supply Chain Applications Multi-Org Access Control Success Story.

claudia-becker
Download Presentation

R12 Enhancements to Oracle Project Contracts

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. R12 Enhancements to Oracle Project Contracts TBD

  2. Agenda • R12 Release Overview • Usability Enhancements • Security Enhancements • Improved Integration with Supply Chain Applications • Multi-Org Access Control • Success Story

  3. The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remain at the sole discretion of Oracle.

  4. Solicit or Bid Project Owner / Manager Author/Execute Contract Customers Change Management Solicitations Contract Manager Sell Bid/Proposal Sell Side Contract Procure/ Subcontract Secure, Central Contract Repository Contractors & Subcontractors Manage Funds Purchasing Buy Subcontracts(w/Flowdown) Track Deliverables Standard Library: T&Cs, Articles SOWs Deliverables Suppliers Bill & Collect Purchase Orders Integration Other Application Components Role-Based Access Planning Procurement Manufacturing Shipping Projects Finance Project Contracts Overview

  5. Improvements in Release R12 In Release 12 (R12), Project Contracts provides improved usability, enhanced access control in contract authoring and Deliverable Tracking System (DTS), and better visibility to project contracts information from other supply chain applications. The new features are: • Usability Enhancements • Security Enhancements • Improved Integration with Supply Chain Applications • Multi-Org Access Control

  6. Agenda • R12 Release Overview • Usability Enhancements • Security Enhancements • Improved Integration with Supply Chain Applications • Multi-Org Access Control • Success Story

  7. Usability Enhancements in R12 • When copying a contract, users can also copy project and task information from the original contract in addition to lines, parties, articles, terms and conditions, standard notes information (which is currently supported). • Contract administrators can permanently delete unwanted contracts in ‘Entered’ or ‘Canceled’ status to reduce the risk of such contracts being accidentally acted upon or being referred to in other contracts. This also helps the administrators to reduce clutter while searching contracts. • During contract approval, approvers can provide review comments that are included in the reply notification to the requestor. • Project task information will be defaulted from the contract header to the lines • The billing event user interface has been improved to support multi currency billing.

  8. UI Enhancements to Billing Event Details Form Description • Multi currency Billing • Display of Price and Amount information in Deliverable and Billing Currency • Indication to reinitiate billing in cases of inconsistent billing information in Project Contract and Project Billing Benefits • Indicates if project allows multi-currency billing

  9. UI Enhancements to Billing Event Details FormHow to use this feature • Details on the Billing Event Details Form • Deliverable unit price / currency (source: DTS) • Checkbox to indicate if project associated to contract is multi-currency billing (MCB) enabled • Billing Currency • If not MCB enabled, Billing Currency defaults to project’s functional currency and is not editable • If MCB Enabled, then Billing Currency defaults to Deliverable Currency and is editable • Billing Unit Price • Bill Amount • Revenue Amount • Bill Quantity • Initiate Billing or Re-Initiate Billing button

  10. Multi-Currency Billing UI Enhancements to Billing Event Details FormHow to use this feature

  11. Re-initiate Billing indicates that billing event on Project Contracts and Project Billing needs to be synched up UI Enhancements to Billing Event Details FormHow to use this feature

  12. Agenda • R12 Release Overview • Usability Enhancements • Security Enhancements • Improved Integration with Supply Chain Applications • Multi-Org Access Control • Success Story

  13. Access Security for DeliverablesRelease Information To prevent unauthorized modifications to contract deliverables, the existing security framework has been enhanced in R12 to allow role-based access to view/edit/initiate deliverables. • Available from 11.5.9 • Users need to uptake patch 4298464

  14. Access Security for Deliverables Description • Security framework for controlling user activities on the Deliverables Tracking System • Users can be setup to: • No Access / View Only / Update deliverables on DTS • No Access / Allow Access to Deliverables-Based Billing • No Access / Allow Access to downstream actions on DTS • Initiate Shipping • Initiate Planning • Initiate Purchasing Benefits • Reduces business risk of unwanted or unwarranted changes to deliverables

  15. Access Security for DeliverablesHow to use this feature • A user is assigned to a contract in a specific role • The role is tied to a menu that allows access to functions • Thus user will be able to access only the functions associated with this role Contract User  Role Menu Function Function Function

  16. Access Security for DeliverablesHow to setup this feature • Step 1: Function Based Security Setup • Responsibility: System Administrator • Navigation: Application / Menu • Create a new menu or modify an existing menu • Following functions on this menu are used to deliver deliverables access control • Contract Deliverables Tracking • Contract Deliverables Tracking: Update • Deliverables Tracking: Initiate Shipping • Deliverables Tracking: Initiate Planning • Deliverables Tracking: Initiate Purchasing • Deliverable-Based Billing

  17. Functions that are used for the deliverables access control requirements Access Security for DeliverablesHow to setup this feature

  18. Access Security for DeliverablesHow to setup this feature • Deliverables Tracking System • No Access • Do not grant access to functions Contract Deliverables Tracking and Contract Deliverables Tracking: Update • Removes Deliverables Tracking System from the Actions menu on Contract Organizer and Find windows • View Only • Grant access to function Contract Deliverables Tracking • Do not grant access to function Contract Deliverables Tracking: Update • Update • Grant access to both functions Contract Deliverables Tracking and Contract Deliverables Tracking: Update

  19. Access Security for DeliverablesHow to setup this feature • Control access to Initiate Shipping, Initiate Planning, Initiate Purchasing • No Access • Do not grant access to functions Deliverables Tracking: Initiate Shipping, Deliverables Tracking: Initiate Planning, Deliverables Tracking: Initiate Purchasing • Removes Initiate Shipping, Initiate Planning, Initiate Purchasing actions from the Actions menu on DTS • Access • Grant access to functions Deliverables Tracking: Initiate Shipping, Deliverables Tracking: Initiate Planning, Deliverables Tracking: Initiate Purchasing

  20. Access Security for DeliverablesHow to setup this feature • Deliverables Based Billing System • No Access • Do not grant access to function Deliverables-Based Billing • Removes Deliverables-Based Billing from the Actions menu on Contract Organizer and Find windows • Update • Grant access to the function Deliverables-Based Billing

  21. Access Security for DeliverablesHow to setup this feature • Step 2: Role Based Security Setup • Responsibility: Project Contracts Super User • Navigation: Security / Roles • Roles Form • Create a new role (or query an existing role) • Associate user role with the appropriate menu • Check the Enforce role-based security checkbox • Define additional access rules as required • Run the concurrent requests ‘Generate Access Rule’ and ‘Generate Secure View’

  22. Associate appropriate user menu to the roles Access Security for DeliverablesHow to setup this feature

  23. Access Security for DeliverablesHow to setup this feature • Step 3: Contract Access Setup • Responsibility: Project Contracts Super User • Navigation: Security / Contract Accesses • Security Role Assignments Form • Select employee • Select contract, program, or site level setting • Specify the user’s role

  24. Access Security for DeliverablesHow to setup this feature Specify the employee’s role at a contract, program or site level

  25. Agenda • R12 Release Overview • Usability Enhancements • Security Enhancements • Improved Integration with Supply Chain Applications • Multi-Org Access Control • Success Story

  26. Improved Integration with Supply Chain Apps In Project Contracts, administrators can specify the list of print forms (such as DD250) required during contract execution. With R12, user can configure to display print forms information in different flow down areas of various applications as required. For example, it can be configured to have DD250 print forms information displayed to the users in shipping. Other key enhancements include a warning message when the same project hierarchy is linked to multiple contracts.  This is required for government contracting organizations that do cost-plus contracts with progress billing.

  27. Flowdown of Print Forms Information Description • Users can now view the Print Forms information in other systems : • Shipping • Purchasing • Work In Progress • Billing Benefits • Print Forms information available to other systems such as Shipping, Procurement, WIP, and Billing • Improve downstream business efficiencies • Avoid shipping or processing orders without relevant documentation

  28. Example of flowdown from Shipping transactions. Flowdown info shows Print Forms associated with the Contract/Line Flowdown of Print Forms InformationHow to use this feature

  29. New tab for Print Forms flowdown Specify business areas to flowdown the Print Forms info Flowdown of Print Forms InformationHow to setup this feature

  30. Specify Effective Date for Programs Description • User can specify the active duration of a Program (From – To) • Assign only active programs to a contract or funding pool Benefits • Avoid assigning an inactive Program to a contract or a funding pool • Reduce potential user mistakes

  31. Specify Effective Date for ProgramsHow to use this feature • Contract Authoring Workbench, Funding Pool Form • User can associate the contract or funding pool with a specific program • Only active programs will be displayed in the program LOV • Security Role Assignments Form • Employee access can be defined at a program level • Only active programs will be displayed in the program LOV

  32. Specify effective dates for the Program Specify Effective Date for ProgramsHow to setup this feature

  33. Default Top Task from Contract Header to Lines Description • User can specify Top Task on the contract header • Top Task will default to contract lines Benefits • Increases efficiency - eliminates the need for manual entry of top task on contracts with many lines

  34. Default task on the contract header defaults to new lines in the contract Default Top Task from Contract Header to Lines How to use this feature

  35. Default Due Date based on Days ARO Description • Due Date on contract line will be automatically updated to Award Date (specified on the header) + Days ARO (specified on the line) • Award Date: 01-JAN-2006 • Days ARO: 30 • Due Date = 31-JAN-2006 Benefits • Eliminates the need for manual entry of due dates • Eliminates the need to update the due dates manually for each contract line when award date is changed

  36. Due date = Award date + Days ARO Default Due Date based on Days AROHow to use this feature

  37. Warning when user changes the Award date and has Days ARO already specified on the line Default Due Date based on Days AROHow to use this feature

  38. Flowdown of DO # / Master Agreement # Description • When a Delivery Order is created in OKE using a Master Agreement, the user can see the concatenated Delivery Order # / Master Order # in OKE • This feature flows down the concatenated information to other applications so that users know which master contract the order is against Benefits • Users in applications such as Shipping and Procurement can easily identify the master agreement associated with the delivery order

  39. Concatenated Delivery Order # / Master Agreement # Flowdown of DO # / Master Agreement # How to use this feature

  40. Concatenated Delivery Order # / Master Agreement # Flowdown of DO # / Master Agreement # How to use this feature

  41. Agenda • R12 Release Overview • Usability Enhancements • Security Enhancements • Improved Integration with Supply Chain Applications • Multi-Org Access Control • Success Story

  42. Multi-Org Access Control • Oracle Project Contracts leverages the Multi-Org Access Control model • Allows users to author contracts and templates in multiple operating units without switching responsibilities • When Multi-Org Access Control is implemented, users can only access contracts authored in operating units that are listed in the security profile assigned to their responsibility

  43. Same Project Hierarchy on Multiple Contracts Description • Provision to decide whether same Project Hierarchy can be used on multiple Contracts • Options are • Allow • Allow With Warning • Do Not Allow Benefits • Flexibility to handle different business scenarios to allow / disallow project hierarchy usage

  44. Same Project Hierarchy on Multiple ContractsHow to use this feature • Example Contract C1 Contract C2 Project P1 • P1A • P1B • P1B1 • P1B2 • P1B3

  45. Same Project Hierarchy on Multiple ContractsHow to use this feature • Allow Contract C1 Contract C2 Project P1 • P1A • P1B • P1B1 • P1B2 • P1B3 Multiple contracts can be referenced using the same project hierarchy

  46. Same Project Hierarchy on Multiple ContractsHow to use this feature • Allow With Warning Contract C1 Contract C2 Project P1 • P1A • P1B • P1B1 • P1B2 • P1B3 ! C1 linked to project P1B User gets a warning when he tries to link C2 to P1B2

  47. Same Project Hierarchy on Multiple ContractsHow to use this feature • Do Not Allow Contract C1 Contract C2 Project P1 • P1A • P1B • P1B1 • P1B2 • P1B3 C1 linked to project P1B User gets an error message when he tries to link C2 to P1B2. This action is not allowed

  48. Same Project Hierarchy on Multiple ContractsHow to setup this feature • Responsibility: Project Contracts Super User • Navigation: Edit / Preferences / Profiles / OKE: Same Project Hierarchy on Multiple Contracts • Allow • Allow With Warning • Do Not Allow

  49. View Notes on Approval of Contract Description • Approver can add notes/comments after approving a contract. This feature allows the submitter of the contract to see the approver’s notes Benefits • Handles the Contract users requirement to have ‘approve with comments’ functionality • Improves efficiency of the approval process

  50. Approver approves with comments View Notes on Approval of Contract How to use this feature

More Related