082406 35934 ppt

Oracle Online Training Materials – Usage Agreement

Oracle Online Training Materials – Usage Agreement

Use of this Site (“Site”) or Materials constitutes agreement with the following terms and conditions:

1. Oracle Corporation (“Oracle”) is pleased to allow its business partner (“Partner”) to download and copy the information, documents, and the online training courses (collectively, “Materials") found on this Site. The use of the Materials is restricted to the non-commercial, internal training of the Partner’s employees only. The Materials may not be used for training, promotion, or sales to customers or other partners or third parties.

2. All the Materials are trademarks of Oracle and are proprietary information of Oracle. Partner or other third party at no time has any right to resell, redistribute or create derivative works from the Materials.

3. Oracle disclaims any warranties or representations as to the accuracy or completeness of any Materials.  Materials are provided "as is" without warranty of any kind, either express or implied, including without limitation warranties of merchantability, fitness for a particular purpose, and non-infringement.

4. Under no circumstances shall Oracle be liable for any loss, damage, liability or expense incurred or suffered which is claimed to have resulted from use of this Site of Materials. As a condition of use of the Materials, Partner agrees to indemnify Oracle from and against any and all actions, claims, losses, damages, liabilities and expenses (including reasonable attorneys' fees) arising out of Partner’s use of the Materials.

Purpose & Disclaimer

Purpose:This document provides an overview of features and enhancements included in Release 12. It is intended solely to help you assess the business benefits of upgrading to Release 12. 

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Software License and Service Agreement, which has been executed and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. This document is for informational purposes only and is intended solely to assist you in planning for the implementation and upgrade of the product features described. 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 in this document remains at the sole discretion of Oracle. Due to the nature of the product architecture, it may not be possible to safely include all features described in this document without risking significant destabilization of the code. 

Disclaimer:

Multi-Org Access ControlAgenda

Introduction– Description– Benefits

Setup and Process– How to set up the feature– How to use the feature

Summary

Multi-Org Access ControlDescription

Multi-Org Access Control (MOAC)– Access multiple operating units from a single responsibility

– Enable shared services while maintaining operating unit security

Multi-Org Access ControlDescription

Multi-Org Access Control (MOAC)– With R12.0, contract administrators can be granted access to

multiple operating units from within a single applications responsibility

– Contract administrators can now manage contracts as well as the contract terms library setup across different operating units without switching responsibilities

– The following entities are multi-org access control enabled in the contract terms library:

Contract Templates Clauses Contract expert rules Clause Folders

Multi-Org Access ControlDescription

Tasks Set-up the contract

terms library (Clauses, Templates and Rules)

Create purchasing and sourcing documents such as Blanket Agreement, RFQ etc.

EMEA – 1 Reponsibility

EMEA – 2 Reponsibility

EMEA – 3 Reponsibility EMEA Responsibility

BELGIUMOperating Unit

HOLLANDOperating Unit

DENMARKOperating Unit

Perform tasks for multiple operating units without changing responsibilities

Variables and Sections are not enabled for multi-org access control. These are automatically available to all operating units.

Multi-Org Access Control Benefits

Improve efficiency– Easily create and access contract information from different

operating units– Improve Shared Services operations

Provide more information for decision making– Global consolidated view of contracts across operating units

Reduce Costs– Cut down processing time

Setup and Process

Multi-Org Access ControlSetup

Setup security profile/s for the implementation– You can setup one or more security profiles depending on the nature and

level of access you need to provide to different users

Assign the security profile/s to the profile option ‘MO: Security Profile’ for each responsibility used

Optionally setup the profile option ‘MO: Default Operating Unit’

Optionally setup the profile option ‘MO: Operating Unit’– This profile option is used to determine the relevant operating unit if no

value is defined for the ‘MO: Security Profile’ profile option

Set up the following information in the Organization Definition Form (was a profile option in previous releases and has now been migrated):

– OKC: Clause Sequence Category

Multi-Org Access Control Process – Search / Create Clauses

Select an Operating Unit while searching clauses

Specify Operating Unit during clause

creation

Multi-Org Access Control Process – Contract Templates

Select Operating Unit while searching template

Specify Operating Unit during

template creation

Multi-Org Access Control Process – Contract Expert Rules

Select Operating Unit while searching rules

Specify Operating Unit during rule creation

Multi-Org Access Control Process – Folders

Select Operating Unit while searching folders

Specify Operating Unit during folder creation

Once saved, the operating unit

cannot be changed

Summary

Multi-Org Access ControlSummary

Multi-org access control is a process that allows:– Contract administrators to view, create and manage

contracts as well as contract terms library setup across multiple operating units without switching responsibilities

Benefits• Enables shared service operations• Enhances visibility to contracts and setup data

XML Interface for Clause ImportAgenda

Introduction– Description– Benefits

Setup and Process– How to set up the feature– How to use the feature

Summary

XML Interface for Clause ImportDescription

XML interface for clause import– In Release 12.0, Procurement Contracts provides a

mechanism to import XML clause data that conforms to the XML schema published by Oracle

– In addition to importing clauses, users can also import user-defined variables and clause relationships

– The system validates the clause and variables embedded in the clause text prior to upload and prints a report for users to review

Note: The Open Interface based clause import has also been enhanced to support importing clause relationships and variables

XML Interface for Clause ImportBenefits

Comprehensive import capabilities– XML interface clause import process provides ability to

package and distribute clauses in a standard way. For example, FAR content providers can package and distribute FAR clauses to US Federal Agencies for import into the Terms Library

Setup and Process

XML Interface for Clause ImportSetup and Process

Place XML file in desired

location

Run concurrent

programValid XML

Review import log report. If

errors exist, fix data in

XML file

Parse XML & validate

Import process run in Validate mode

Already imported

Add/ Update clauses

Clause approval

status

Submit

Approver approves

Clause approved

No

YesYes

No

Yes

No

Pending Approval

Approved

Draft

XML Interface for Clause ImportProcess – Prepare XML File with Data

Prepare the XML file to conform to the XML schema published by Oracle. XML file can contain:– Clause information (title, clause text etc.). Clause text can

contain embedded variables– User-defined variables – Clause relationships (Alternate or Incompatible clauses)– Value-sets used in user-defined variables that are imported– Values for the value-sets that are imported

XML file may also be provided by a content vendor for import

Place XML file in the directory location specified by the profile option 'OKC: Clause Import XML File Location'

XML Interface for Clause ImportProcess – Import Clauses from XML File

XML File Name: Name of the XML file that contains the clause information Default Operating Unit: If Operating Unit is not provided in the XML file, this default is used Create as Global Clause: If the file does not identify whether the clause is created as global or

local, this default is used Clause Status: If no status has been provided in the XML file, this default will be used Validate Only: Set to ‘Yes’ if you want a dry run of the import to identify potential errors. Set to

‘No’ to import clauses into the library

XML Interface for Clause ImportProcess – Validate Import Data and Final Run

If you have chosen to run the import process in a ‘Validate’ mode, the system provides an output log file that details any errors in the XML data. For example:– XML related issues such as the XML file not being ‘well

formed’ – Duplicate clauses or duplicate relationships – Invalid variables used in clause text

Summary

XML Interface for Clause ImportSummary

XML Interface for clause import is a new process:– To upload your clauses into the contract terms library automatically

using the Oracle provided XML schema– You upload clauses and related information such as variables and

clause relationships after validating the information to minimize errors in the data

Benefits

• Streamlines the import process • Minimizes manual effort in creating clause library• Ensures data validation

Miscellaneous Authoring EnhancementsAgenda

Introduction– Description– Benefits

Setup and Process– How to use the feature

Summary

Miscellaneous Authoring EnhancementsDescription

Revert to Standard– Release 11i.10 allowed users to create non-standard clauses

either from scratch or by modifying a standard clause. With Release 12.0, users now have the ability to revert a clause to its standard version after it has been made non-standard. If the standard version originally used is not the most recent standard, the system will replace it with the latest active version

Assign Contract Administrators and Legal Contacts– Users can now assign a contract administrator and a legal

contact during the authoring process – This is key information for any follow-up or communication during

the lifecycle of the contract from negotiations to post-approval

Miscellaneous Authoring Enhancements Benefits

Revert to standard– Reduces time and effort to revert to standard– Promotes use of standard language

Contract Administrator and Legal Contact– Improves accountability on a contract

Process

Revert to StandardProcess – Make Clause Non-standard

Revert to Standard brings back the standard clause from which the non-standard clause was created

Revert to StandardProcess – Revert to Standard Confirmation

System displays the redline comparison between the non-standard version and the latest standard version

Non standard clause text

Standard clause text

Miscellaneous Authoring EnhancementsProcess – Contract Administrators and Legal Contact

Information

Navigate to Update Contract

Details Page

Enter Contract Administrator and Legal Contact for the contract

Summary

Miscellaneous Authoring EnhancementsSummary

Revert to Standard is a new feature– That allows authors of a contract to revert a clause to its standard

language after it has been made non-standard

Contract Administrator and Legal Contact are two new fields available during terms authoring– Capturing this for each contract provides key information for any

follow-up or communication during the lifecycle of the contract from negotiations to post-approval

Benefits

• Reduces time and effort to revert to standard• Promotes standard language use• Improves accountability on a contract