EBS_122_Cum_RCD_CLM

ORACLE E-BUSINESS SUITE
RELEASE CONTENT DOCUMENT
Oracle Contract Lifecycle Management for

Public Sector
Releases 12.1 and 12.2
Prepared by Oracle E-Business Suite Product Development
Last Updated: June 9, 2023
Copyright © 2023, Oracle and/or its affiliates.

Table of Contents
1. Disclaimer 1
2. Introduction 2
2.1. Purpose of Document 2
3. Oracle Contract Lifecycle Management for Public Sector 3
3.1. Release Overview 3
3.2. Oracle iProcurement 6
3.2.1. Overview 6
3.2.2. Release 12.1.3+ 6
3.2.2.1. Line/Sub-Line Structures 6
3.2.2.2. Option Lines 6
3.2.2.3. FAR/DFARS-Compliant Document Numbering and Line Numbering 6
3.2.2.4. Federal Pricing Contracts and Complex Pricing Calculation 6
3.2.2.5. Incremental Addition of Funds 7
3.2.2.6. Requisition Amendment 7
3.2.2.7. Federal Attributes 7
3.2.2.8. Support for Tax Calculation 7
3.2.2.9. Ability to change POET information on Requisition Amendment 7
3.2.3. Release 12.2 8
3.2.3.1. Option Line Enhancements 8
3.2.3.2. Purchase Requisition Lines Without Distributions 8
3.2.4. Release 12.2.2 8
3.2.4.1. Military Inter-Departmental Purchase Requests (MIPRs) 8
3.2.5. Release 12.2.3 8
3.2.5.1. Automatic Updates to Encumbrance (GL) Date 8
3.2.6. Release 12.2.5 9
3.2.6.1. PR Amendment Attachment History 9
3.2.6.2. Copy Attachments to PR Amendments 9
3.2.6.3. Additional Enhancements to Military Inter-Departmental Purchase Requests (MIPRs) 9
3.2.6.4. View Solicitation Details 9
3.2.6.5. Requisition Amendment Details in Approval Notification 9
3.2.7. Release 12.2.6 10
3.2.7.1. Purchase Request Data Standard (PRDS) Outbound and Related Enhancements 10
3.2.7.2. Visibility into Procurement Activities 10
3.2.7.3. Active Items Displayed to Requester 10
3.2.8. Release 12.2.7 10
3.2.8.1. Purchase Request Data Standard (PRDS) Inbound 10
3.2.8.2. Military Interdepartmental Purchase Request (MIPR) Usability Improvements 11
3.2.9. Release 12.2.8 11
3.2.9.1. Ability to move funds between lines in Requisition 11
3.2.9.2. Purchase Request Data Standard (PRDS) Inbound Enhancements 11
3.2.9.3. Purchase Request Data Standard (PRDS) Outbound Enhancements 11
3.2.10. Release 12.2.9 11
3.2.10.1. PRDS enhancement to support MIPRs 11
3.2.11. Release 12.2.10 11
3.2.11.1. Operating Unit Specific Information in Requisitions 11
3.2.11.2. SAM (System for Award Management) indicator while selecting supplier in Requisitions 12
3.2.11.3. Release funds to backing Requisition 12
3.2.11.4. Moving funds across lines with backing PR in one modification 12
3.2.12. Release 12.2.12 12
3.2.12.1. Intragovernmental Requests to Track Commitments against GT&C 12
3.2.13. Release 12.2.13 12
3.2.13.1. Change IGT Requisition to Modify IGT order 12
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document ii
3.2.13.2. Ability to Create IGT Requisitions with an Amount-based Line Type 12
3.2.13.3. Ability to Group IGT Requisition Lines while Creating IGT Order 12
3.3. Oracle iSupplier Portal 13
3.3.1. Overview 13
3.3.2. Release 12.1.3+ 13
3.3.2.1. Enhanced Award and IDV information 13
3.3.2.2. Enhancement to Advanced Shipment Notification 13
3.3.2.3. Supplier Changes * 13
3.4. Oracle Procurement Contracts 14
3.4.1. Overview 14
3.4.2. Release 12.1.3+ 14
3.4.2.1. Acquisition Plan Summary 14
3.4.2.2. Enhancement to Suggested Sections for Clauses by Contract Expert 14
3.4.2.3. Amendment and Modification Section (Clauses) 14
3.4.2.4. Enhanced Variables Support 14
3.4.2.5. Deletion of Provisional Sections from Solicitation to Award 15
3.4.2.6. Apply Multiple Templates to a Sourcing or Purchasing Document ** 15
3.4.2.7. APIs for Importing Templates, Rules, Questions and Constants ** 15
3.4.2.8. New Clause Descriptor Field ** 15
3.4.2.9. Clause Mandatory Attribute at Rule level ** 15
3.4.3. Release 12.2 15
3.4.3.1. Instruction Text 15
3.4.3.2. Multi-Row Variables 15
3.4.3.3. Display Clause Number and Sort by Clause Number 16
3.4.4. Release 12.2.2 16
3.4.4.1. Integrated Clause Logic Service 16
3.4.5. Release 12.2.3 16
3.4.5.1. Document Numbering for Acquisition Plan and Small Business Coordination Record 16
3.4.6. Release 12.2.5 17
3.4.6.1. Managing Deliverables of the Contract 17
3.4.7. Release 12.2.10 17
3.4.7.1. Print Full Clause Text of Include by Reference Clauses 17
3.5. Oracle Purchasing 17
3.5.1. Overview 17
3.5.2. Release 12.1.3+ 17
3.5.2.1. Line/Sub-Line Structures 17
3.5.2.5. Capture Federal Attributes and Nomenclature Specific to Federal Contracting Processes 18
3.5.2.6. Incremental Addition of Funds 18
3.5.2.7. Modifications and System-Generated Description 19
3.5.2.8. IDV Constraints 19
3.5.2.9. Orders Referencing IDVs 19
3.5.2.10. Document Printing in Standard Federal Forms 20
3.5.2.11. Capture and Storage of Historical Point in Time Information 20
3.5.2.12. Enhanced Electronic Signature * 20
3.5.2.13. Warrants * 20
3.5.2.14. Workload Assignment and Milestones * 21
3.5.2.15. Purchase Requisition Line to Fund Modification * 21
3.5.2.16. Contract Closeout * 21
3.5.2.17. Contract Action Reporting to FPDS-NG * 22
3.5.2.18. Reports * 22
3.5.2.19. Support for Taxes 23
3.5.3. Release 12.2 23
3.5.3.1. Grouping of Lines 23
3.5.3.2. Purchase Requisition References Across Multiple Awards or Award Lines 23
3.5.4. Release 12.2.1 24
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document iii
3.5.4.1. Contract File 24
3.5.4.2. Multiple Modifications (Multi-Mod) 24
3.5.4.3. Novation 24
3.5.4.4. Concurrent Modifications 25
3.5.4.5. Mass Update of Field Values 25
3.5.4.6. Multiple Awards and Umbrella Programs 25
3.5.4.7. Enhancements to Workload Assignments 25
3.5.4.8. Automatic Updates to Encumbrance (GL) Date 26
3.5.4.9. ORCA Integration 26
3.5.4.10. ACRN 26
3.5.4.11. EDA Integration 26
3.5.5. Release 12.2.2 26
3.5.5.1. Post Award Requests 26
3.5.5.2. Exhibit Lines (ELINs) and Contract Data Requirements Lists (CDRLs) 27
3.5.5.3. Undefinitized Contract Actions (UCAs) 27
3.5.5.4. Support Military Inter-Departmental Purchase Requests (MIPRs) 27
3.5.5.5. Vendor Eligibility Check (EPLS Check) 28
3.5.5.6. Protest Tracking 28
3.5.5.7. Contract Closeout 28
3.5.5.8. Payment Instructions and Payment Terms 28
3.5.5.9. Event-Based Deliveries 29
3.5.5.10. Integration with WDOL 29
3.5.5.11. Changes to Awards and Modifications 29
3.5.5.12. Small Business Coordination Records (SBCRs) 29
3.5.6. Release 12.2.5 29
3.5.6.1. Unlinking Requisitions from Award documents 29
3.5.6.2. Buyer Reassignment in Demand Workbench 30
3.5.6.3. Link to Requisition Lines using PO BSO Web Services 30
3.5.7. Release 12.2.6 30
3.5.7.1. Procurement Data Standard (PDS) Inbound 30
3.5.8. Release 12.2.7 30
3.5.8.1. Purchasing Usability Enhancements 30
3.5.9. Release 12.2.8 30
3.5.9.1. Improvements to Workload Assignments 30
3.5.9.2. Manage assignment for all lines of requisition 31
3.5.9.3. One step unlinking and relinking requisition/PAR on same modification 31
3.5.9.4. Nomenclature Changes for PDF Actions 31
3.5.9.5. Ability to view Point-in-Time PDF 31
3.5.9.6. Ability to view requisition lines added to specific modification document 31
3.5.9.7. Procurement Data Standard (PDS) Enhancements 31
3.5.9.8. Contract printing Enhancements 32
3.5.10. Release 12.2.9 32
3.5.10.1. EBTax Support for CLM Purchasing 32
3.5.10.2. Ability to identify if Award has pending modification 32
3.5.10.3. Ability to see changed lines in edit modification 32
3.5.10.4. Ability to see changes in the award over a period of time 32
3.5.11. Release 12.2.10 32
3.5.11.1. Global and Local Document Styles (Document Style with Operating Unit) 32
3.5.11.2. OU based Attribute Templates 33
3.5.11.3. Operating Unit Specific Information in Award and IDV 33
3.5.11.4. SAM (System for Award Management) indicator while selecting supplier in Awards and IDVs 33
3.5.11.5. Interface Intragovernmental Transactions to G-Invoicing 33
3.5.12. Release 12.2.11 34
3.5.12.1. Contract Opportunities Posting to SAM using REST services 34
3.5.12.2. Pull Groups from G-Invoicing to support Intragovernmental Transactions 34
3.5.12.3. Interface Intragovernmental Order Modifications to G-Invoicing 34
3.5.12.4. Pull and Push Performance Transactions and Display to User 34
3.5.12.5. G-Invoicing 4.1 Compatible Changes, Support DII and Originating Partner Indicator 34
3.5.13. Release 12.2.12 35
3.5.13.1. Simplified Creation of IGT Orders from IGT Requisitions 35
3.5.13.2. ‘Share with Servicing Agency’ Action Included in Approval Workflow 35
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document iv
3.5.13.3. Support for Seller Facilitated Orders (SFO) 35
3.5.13.4. Support for Authoring of Intragovernmental Orders through the G-Invoicing System 35
3.5.13.5. Ability to Cancel IGT Order Line or Schedule 35
3.5.13.6. Ability to Close and Re-Open IGT Orders 35
3.5.13.7. Ability to View Groups Information and Check Request Status 36
3.5.13.8. Performance Transaction Integration with Receiving and Payables 36
3.5.13.9. Vendor Eligibility Check using REST API 36
3.5.13.10. Support for Unique Entity Identifier (UEI) 36
3.5.13.11. Ability to Get ORCA Details Using REST API 36
3.5.14. Release 12.2.13 36
3.5.14.1. API to create modification to de-obligate funds on an Award 36
3.5.14.2. Novation through webservice 36
3.5.14.3. Ability to use external IDV value to query awards 37
3.5.14.4. Supplier contact as free text while creating award 37
3.5.14.5. Improvements to query unassigned requisition lines in demand workbench 37
3.5.14.6. Ability to Print 7600B for IGT Orders 37
3.5.14.7. Ability to Pull Open In-flight Orders from G-Invoicing and Create as New IGT orders 37
3.5.14.8. Ability to Support Treasury’s 7600EZ Process 37
3.5.14.9. Administrative Change for Seller Facilitated Orders (SFO) 37
3.5.14.10. Ability to Outright Reject SFO 37
3.5.14.11. API Payload Migration to JSON for GT&V 37
3.5.14.12. Object Class Code as Required Attribute in IGT Order 38
3.6. Oracle Sourcing 38
3.6.1. Overview 38
3.6.2. Release 12.1.3+ 38
3.6.2.1. Line – Sub-line Structures 38
3.6.2.4. FedBizOpps Integration 39
3.6.2.6. Solicitation Amendments and System Generated Descriptions 39
3.6.2.7. Capture Federal Attributes and Nomenclature Specific to Federal Contracting Processes 39
3.6.2.8. Capture and Storage of Historical Point in Time Information 40
3.6.2.9. Solicitation Documents Printing as per Standard Federal Forms 40
3.6.2.10. Online Offer Entry * 40
3.6.2.11. Sort and Delete Suppliers from Invited Suppliers Page 40
3.6.3. Release 12.2 40
3.6.3.1. Add Requisition Lines to a Draft Solicitation 40
3.6.3.2. Grouping of Lines 41
3.6.3.3. Mass Update of Field Values 41
3.6.3.4. Purchase Requisition References Across Multiple Solicitation Lines 41
3.6.3.6. Acceptance and Inspection Location 42
3.6.4. Release 12.2.1 42
3.6.4.1. Offer Withdrawal 42
3.6.4.2. Track Amendment Acknowledgements 42
3.6.4.3. Multiple Awards and Umbrella Program 42
3.6.4.4. Unsolicited Lines 42
3.6.4.5. Multiple Active Offers 43
3.6.4.6. ORCA Integration 43
3.6.5. Release 12.2.2 43
3.6.5.1. Vendor Eligibility Check (EPLS check) 43
3.6.5.2. Protest Tracking 43
3.6.5.3. Exhibit Lines (ELINs) and Contract Data Requirements Lists (CDRLs) 44
3.6.5.4. Event-Based Deliveries 44
3.6.5.5. Integration with WDOL 44
3.6.5.6. Small Business Coordination Records (SBCRs) 44
3.6.6. Release 12.2.4 44
3.6.6.1. Mass Update of Buyers 44
3.6.7. Release 12.2.5 45
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document v
3.6.7.1. Solicitation Amendment After Close Date 45
3.6.8. Release 12.2.7 45
3.6.8.1. Apply Templates on Draft Solicitations 45
3.6.9. Release 12.2.8 45
3.6.9.1. Uptake revised DD-2579 form and enhancements to SBCR 45
3.6.9.2. Sourcing Usability Enhancements 45
3.6.10. Release 12.2.9 45
3.6.10.1. Approvals Management Engine for Solicitation Approvals 45
3.6.10.2. SAM (System for Award Management) indicator while selecting supplier 46
3.6.10.3. Offer Received time made non-mandatory while creating surrogate quote 46
3.6.10.4. Award and Complete as a new action if there is single quote for solicitation 46
3.6.11. Release 12.2.10 46
3.6.11.1. Operating Unit Specific Information in Solicitation and Offer 46
3.6.12. Release 12.2.12 46
3.6.12.1. Ability to Provide Payment Office Details in Solicitation 46
3.7. Oracle Contract Lifecycle Management for Public Sector Command Center 46
3.7.1. Overview 46
3.7.2. Release 12.2.8+ 46
3.7.2.1. Acquisition Plans 47
3.7.2.2. Requisitions 47
3.7.2.3. Solicitations 47
3.7.2.4. IDVs 47
3.7.2.5. Awards 47
3.7.3. Release 12.2.9++ 48
3.7.3.1. Liquidate Funds 48
3.7.3.2. Cancel Requisitions 48
3.7.4. Release 12.2.11 48
3.7.4.1. New Attribute Group to track Quantities and Amount details 48
3.7.4.2. Sequential data load uptake 48
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document vi
1. Disclaimer
This Release Content Document (RCD) describes product features that are proposed for
the specified releases of the Oracle E-Business Suite. This document describes new or
changed functionality only. Existing functionality from prior releases is not described. It
is intended solely to help you assess the business benefits of upgrading to the specified
release of the Oracle E-Business Suite.
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Purpose of Document 1
2. Introduction
2.1. Purpose of Document

This Release Content Document (RCD) communicates information about new or changed
functionality introduced in Oracle E-Business Suite Releases 12.1, and in subsequent
Release Update Packs (RUPs) and off-cycle patches. For your convenience, it also
includes new or changed functionality introduced in the RUPs for Release 12, including
12.0.2 through 12.0.7 and R12.2.
The features and enhancements described in this document are grouped by product, and
then by the release in which they first became available, for example, “Release 12.1.1”.
Features released in an off-cycle patch have a special designation – for example, a feature
released after 12.1.3, but before 12.2, is designated as “Release 12.1.3+”.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Purpose of Document 2
3. Oracle Contract Lifecycle Management for Public Sector
3.1. Release Overview

Oracle® Contract Lifecycle Management for Public Sector (CLM) is a comprehensive
solution for managing end-to-end business processes for both routine and complex
acquisitions made by federal agencies. This offering is an extension of the current
Advanced Procurement Suite in Oracle E-Business Suite and enables federal agencies to
perform all procurement activities within a fully integrated ERP environment. By
including core contract writing functionality within the ERP, the Oracle Contract
Lifecycle Management application eliminates costly and difficult-to-maintain integrations
with niche procurement applications, and also eliminates the data transformation and
reconciliation issues that accompany them. While supporting FAR, DFARS, and other
agency regulations that define the federal business processes, CLM allows a fully
integrated procure-to-pay process flow within the ERP and maximizes benefits to the
federal customer base. CLM enables contracting officers to drive operational excellence
in federal procurement functions and helps agencies cut procurement costs dramatically.
By providing end-to-end business intelligence with a single source of data, CLM also
provides data transparency and visibility and supports contracting officers with strategic
planning and improved decision making.
From the creation of demand through a purchase request, through the initiation of a
solicitation document and related negotiations, and to the subsequent award of a contract
document to a supplier or provider, CLM provides fully integrated, end-to-end acquisition
and contract writing capabilities. CLM supports complex acquisition requirements such
as line item/sub-line item (CLIN/SLIN) administration as well as generating and printing
standard federal forms, configurable and extensible document numbering, complex
pricing in accordance with FAR Part 16 requirements, and incremental addition of funds.
Also supported are features useful to procurement offices including acquisition plan
administration. The comprehensive solution includes purchase request amendments,
solicitation amendments, as well as contract modifications to streamline the change
processes in transaction documents. Out-of-the- box integrations with the Integrated
Acquisition Environment (IAE), such as FedBizOpps and FPDS-NG, complete the CLM
solution for government procurement and acquisition offices.
At a high level, the following features have been introduced:
• Acquisition planning capabilities
• Contract line item/sub-line item (CLIN/SLIN) structures
• Configurable document numbering
• Complex pricing contract types ( as per FAR Part 16)
• Option lines and exercising of options
• Incremental funding capability
• Support for multiple document types (delivery orders, BPA call orders, awards,
agreements, IDIQ contracts)
• Out-of-the-box support for various federal attributes in requisition, solicitation
and award documents
• PR amendments and solicitation amendments
• Award modifications
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Release Overview 3
• Standard federal forms capability including System Generated Descriptions for
changes in a modification
• Capture and storage of historical point in time information
• FedBizOpps integration
• FPDS-NG integration
• Support for workload assignment
• Warrant enforcement
• Support for electronic signature by the supplier and contracting officer
• Out-of-the-box integration with R12 Federal Financials
• Terminology changes to better align existing naming conventions with federal
terminology—for example, a negotiation will be referred to as a solicitation.
• Novations and multiple modifications
• Concurrent modifications
• Electronic contract file
• Unsolicited lines
• Post award requests
• Support for ELINs and CDRLs
• Military Inter-departmental Purchase Requests (MIPRs)
• Integration with ORCA(SAM)
• Integration with EPLS (SAM)
• EDA Integration
• WDOL Integration
• Clause Logic Service Integration
• Undefinitized contract actions and contingency contracts
• Protest tracking
• Small business coordination records
• Payment instructions
• Automated contract closeout
Many other features are also available in CLM.
The technology stack for Oracle E-Business Suite Release 12.2 takes advantage of the
latest Oracle and third-party technologies for the database, application tiers, and Java.
Important Notes:
1. The CLM offering is an extension of the current Advanced Procurement Suite. Most
existing capabilities in Oracle iProcurement, Oracle Sourcing, Oracle Purchasing,
Oracle iSupplier Portal, Oracle Procurement Contracts, and Oracle Services
Procurement are supported in CLM. As per the conventions of the Release Content
Document, only new enhancements and functionality are described below.
2. Some new enhancements are available to all customers of Procurement products. In
other words, this functionality is available whether or not Oracle Contract Lifecycle
Management for Public Sector is licensed. These general features are listed in the Release
Content Document for Procurement, Releases 12.1 and 12.2 (inclusive of 12.0.2 –
12.0.7). Be sure to check this additional RCD to obtain a more complete description of
functionality for a given release.
3. This Release Content Document (RCD) communicates information about new or
changed features and enhancement introduced in the base CLM release and in subsequent
Release Update Packs (RUPs) and off-cycle patches. Functionality available through the
latest CLM release is marked with an asterisk (*). Customers can uptake cumulative Patch
11779376:R12.PO.C on top of the base feature patch 99354180 to take advantage of these
features as well as the ones released before. Features in Oracle Procurement Contracts
marked with a double asterisk (**) are available through the application of patch
12332531:R12.OKC.B.
4. Licenses for Advanced Procurement products, in addition to Oracle Contract
Lifecycle Management for Public Sector, will enable users to access all the functionality
described in this document. The actual certification date for some of these technologies
may not coincide completely with the release date of Oracle E-Business Suite, especially
on certain platforms. Before planning to upgrade your Oracle E-Business Suite 12.1
instance to a new version of such technologies, please ensure that the technology is
certified and available for your platform by reviewing the information available in the
Certify system on My Oracle Support.
3.2. Oracle iProcurement
3.2.1. Overview
CLM enables procurement professionals from federal agencies to perform a wide range
of requisitioning activities prior to solicitation, from routine to complex. Requesters can
create, manage, and track their requisitions using an intuitive web interface, while
agencies can ensure that preferred pricing agreements are reflected in every requisition.
The following features are introduced in Oracle iProcurement as part of CLM.
3.2.2. Release 12.1.3+
3.2.2.1. Line/Sub-Line Structures

When creating requests for goods or services, requesters can define lines as either priced
or informational, and can organize them into complex line and sub-line structures, in
compliance with federal regulations. Items from both shopping catalogs and non-catalog
items can be placed as a line or sub-line on the requisition. While creating solicitations or
awards from requisition lines, the contracting professional is able to copy the entire
line/sub-line structure from the requisition documents.
3.2.2.2. Option Lines

Requesters can include option lines in requisition and requisition amendments. Option
lines can be associated with base lines and often involve follow-up work. Option lines
behave similarly to regular lines except that they are not funded until they are exercised
after contract award. Lines and sub-lines can be set as option lines, and the requester can
enter the option duration. Using a requisition amendment, the requester can flag an option
line as exercisable, and add funds to the option line.
3.2.2.3. FAR/DFARS-Compliant Document Numbering and Line Numbering

CLM provides the ability to assign complex document numbers to requisition documents.
It allows users to configure a segment-driven numbering format for requisitions and
requisition amendments. Based on the numbering configuration, the appropriate document
number gets automatically assigned to requisition documents, and the requester can
modify the assigned document number.
Requisition lines are automatically numbered in accordance with line/sub-line numbering
conventions used in federal agencies. The requester has flexibility to modify the system-
assigned line number.
3.2.2.4. Federal Pricing Contracts and Complex Pricing Calculation

Requisition lines can be created for various federal pricing contracts (in accordance with
FAR Part 16) such as Firm Fixed Price, Fixed Price Level of Effort, and so on. For these
pricing contracts, the requester can provide values for various pricing attributes specific
to the respective contract type and calculate the estimated cost of the line. The requester
can also specify an appropriate cost constraint indicator, such as Not Separately Priced,
No Charge, Not to Exceed, and so on. The cost constraint indicator is stored and carried
forward to solicitations and orders.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle iProcurement 6
3.2.2.5. Incremental Addition of Funds
In CLM, the requester can create partially funded requisitions, allowing the funded value
to be different from the estimated cost of the requisition. Lines in a requisition can be fully
funded, partially funded, or not funded at all. In the case of partially funded or unfunded
lines, the requester can update the funded value using a purchase requisition amendment.
3.2.2.6. Requisition Amendment

Requisition Amendments in CLM enable the requester to make changes to approved
requisitions, as is sometimes required during the procurement cycle. The requester can to
create a requisition amendment even after requisition lines have been solicited, offers have
been received, and a draft award has been created. Using requisition amendments, users
can perform multiple actions such as:
• Changing line item information
• Adding funds to partially funded lines
• Adding new lines for goods and services
• Canceling existing lines
Line changes in requisition amendments are made available to contracting professionals,
who can then implement the changes in the solicitation or award documents. Additionally,
users can see a history of all the amendments made to a requisition and they can also
compare changes made through a specific amendment on the conformed requisition.
3.2.2.7. Federal Attributes

In CLM, a number of fields in the requisition document are specific to federal use. These
fields facilitate the management of the federal requisitioning process, and include, for
example, DPAS Rating, Priority Code, Customer Project Code, Requesting Office, and
Contact Details. The requester can enter appropriate values for these fields as part of the
requisition header, lines, or accounting distribution information. Certain fields like
Suggested COTR Office and Priority Code can be used as search parameters for
requisition documents.
To simplify the requisition creation process, the requester can set up default values for
details about federal offices. CLM also offers flexible scalability in configuring and
capturing additional federal attributes to meet agency-specific business requirements.
3.2.2.8. Support for Tax Calculation

Non-US federal users of CLM can enable support for tax calculation for purchase
requisitions created in CLM. Taxes are calculated for CLM purchase requisitions using
Oracle E-Business Tax. CLM PR distributions can be funded to the extent of the purchase
requisition line amount plus non-recoverable taxes.
3.2.2.9. Ability to change POET information on Requisition Amendment

With this enhancement, users can modify Project, task, expenditure organization and type
(POET) details during requisition amendment. This will ensure proper funds allocation.
3.2.3. Release 12.2
3.2.3.1. Option Line Enhancements

Requesters can create option lines without having to refer to a base line. Unlike an option
line with a base line reference, an option line without a base line reference can flow into
downstream documents (sourcing and purchasing) independently.
Requesters can copy and replicate one or more requisition lines as regular lines and option
lines, and can select whether base line references should be maintained. Requesters can
also use the enhanced Copy feature to create option structures, in which a new optional
CLIN-SLIN structure can be created such that each option SLIN in the new structure refers
to priced SLINs of the original structure as base lines. Moreover, the Copy feature has
been enhanced to allow the system to default or derive need-by dates, period of
performance dates, and option from and to dates on option lines.
3.2.3.2. Purchase Requisition Lines Without Distributions

CLM now enables requesters to create requisitions without distributions and to submit
them for approval. Such requisitions can be fully approved without distributions, or the
approvers can add fund sources during the requisition approval process. After the
requisition is approved and when the source of funds is known, the requester can specify
the source of funds either through an amendment to the same requisition, or through a new
requisition.
3.2.4. Release 12.2.2
3.2.4.1. Military Inter-Departmental Purchase Requests (MIPRs)

CLM allows users to create Military Interdepartmental Purchase Requests (MIPRs). This
feature is specific for the Department of Defense (DoD) and can be turned on or off by
implementing agencies depending on their need. MIPRs sent by another agency can also
be entered in the CLM system and can be accepted by the receiving agency prior to
processing. The standard forms for MIPR creation (DD448) and acceptance (DD448-2)
are generated within the CLM system.
CLM supports both Reimbursement (Category I) and Direct Citation (Category II) types
of MIPRs. MIPR documents can be amended to make changes to requested items, to fund
citations, and so on. MIPR documents in CLM behave like regular purchase requests,
including commitment of funds. MIPRs can be assigned to a buyer's workload and can
used to autocreate awards. An autocreated award has the MIPR reference and can be
obligated and transacted for receiving and invoicing, depending on the type of MIPR
reference.
3.2.5. Release 12.2.3
3.2.5.1. Automatic Updates to Encumbrance (GL) Date

While creating purchase requisitions, requesters need not manually update the
encumbrance date for each distribution of a line. If the encumbrance (GL) date is within
a closed period, and is therefore invalid, the application automatically displays the system
date as the encumbrance date. To use this feature, the profile option PO: Validate GL Date
Period must be set to the new value Re-default.
3.2.6. Release 12.2.5
3.2.6.1. PR Amendment Attachment History

Amendment Action History now includes updates made to the attachments along with the
name of the user who made the update and the date and time of update. This allows users
to track the attachments added to the base document, to the conformed copy, or to each
amendment.
3.2.6.2. Copy Attachments to PR Amendments

Oracle CLM iProcurement now offers to copy the attachments when an amendment is
created. By default, all of the attachments from the conformed copy will be copied to the
amendment. However, users can update or delete any of these attachments and add new
attachments before the amendment is created.
3.2.6.3. Additional Enhancements to Military Inter-Departmental Purchase

Requests (MIPRs)
With this release of CLM, the DD448 document for MIPR can be automatically generated
upon the submission of a requisition of type MIPR. This document can be generated even
when the requisitions are in a status of Draft or In Process.
CLM now supports an MIPR Assisting Office, which is a third-party agency outside the
requesting office. An MIPR Assisting Office is considered a supplier, and their contacts
and locations are part of the supplier definition within Oracle E-Business Suite. However,
to identify a supplier as an MIPR Assisting Office, the new business classification code
MIPR Assisting Agency has been introduced for suppliers. A supplier classified as an
MIPR Assisting Agency would have their contacts and locations available during the
creation of an MIPR.
Users can now attach external documents to an MIPR during its acknowledgement in the
Acknowledge MIPR Acceptance page.
3.2.6.4. View Solicitation Details

Buyers and contracting officers are now able to view the solicitation details from the
requisition details.
3.2.6.5. Requisition Amendment Details in Approval Notification

Approvers can now view requisition amendment details, which indicate the changes made
in the amendment, in the approval notification itself. It is no longer necessary to navigate
to the requisition document to check the changes.
3.2.7. Release 12.2.6
3.2.7.1. Purchase Request Data Standard (PRDS) Outbound and Related

Enhancements
With this enhancement, CLM has the capability to generate Purchase Request Data
Standard (PRDS) XML for users. Run the new concurrent program for approved
requisitions, and also generate PRDS XML files automatically. This enhancement
establishes standard and accurate data that is in compliance with Department of Defense
standards. The purchase requisition is also the source for critical data used in contract
awards, and thus accurate PRDS XML generation is more significant.
Now PRDS XML can be generated automatically or by running a new concurrent
program. This enables purchase requisitions to be converted into XML in PRDS format
which can be sent to other agencies. PRDS processing information will be recorded in
the PRDS Action History page. The system also enables adding custom action and
relevant information in PRDS action history. The final approver of the requisition is
notified when the PRDS XML file is successfully generated.
3.2.7.2. Visibility into Procurement Activities

Oracle Contract Lifecycle Management enables requester visibility into procurement
operations, for the entire life cycle of procurement activities.
• Requesters can view the requested item or services downstream procurement
status for example, Solicitation Published, Award Approved, etc.
• Requesters are provided with the Procurement Action History that displays
procurement activities for requested items and services.
3.2.7.3. Active Items Displayed to Requester

With the latest release, when a requester searches for an item associated with an Indefinite
Delivery Vehicle (IDV), the system checks whether the system date falls between the IDV
start date and IDV end date. If so, the item is valid and active and is displayed to the
requester. If an item becomes inactive during the approval process, it will be highlighted
for the approvers in the requisition approval notification.
3.2.8. Release 12.2.7
3.2.8.1. Purchase Request Data Standard (PRDS) Inbound

With this enhancement, CLM has the capability to receive Purchase Request in Purchase
Request Data Standard (PRDS) format from an external system. The PRDS is a way for
the DoD to standardize the PR data. The establishment of accurate and standard data is
critical since the purchase request (PR) is the source of critical data used in contract
award. It helps DoD to achieve traceability and transparency of contract expenditures, by
properly link requirements, as documented in purchase requests (PRs).
3.2.8.2. Military Interdepartmental Purchase Request (MIPR) Usability
Improvements
With this release, MIPR has been further improved from a usability standpoint.
Requesters can now perform the following activities more easily.
• Requester’s from requesting agency can now send MIPR to multiple recipients.
Similarly, users from assisting agency can send MIPR Acceptance to multiple
recipients.
• Requesters in requesting agency can also record and track the MIPR acceptance
responses received from assisting agency.
• MIPR authorizing officer signature will be printed in MIPR (DD 448) form and
MIPR Acceptance (DD 448-2) form.
• Users at assisting agency can now enter the requesting agency details which can
be printed on MIPR Acceptance (DD 448-2) form.
3.2.9. Release 12.2.8
3.2.9.1. Ability to move funds between lines in Requisition

With this enhancement, requesters can move funds from priced CLIN to info SLIN with
a single click. A new action, ‘Convert funds to info SLIN’ introduced to auto create info
SLIN and distribute funds from parent contract lines.
3.2.9.2. Purchase Request Data Standard (PRDS) Inbound Enhancements

A new REST service created to receive Purchase Request in Purchase Request Data
Standard (PRDS) that avoid setting separate SOA server. With this enhancement PRDS
support amendment process and user defined attributes (UDA).
3.2.9.3. Purchase Request Data Standard (PRDS) Outbound Enhancements

With this enhancement, CLM has the capability to generate Purchase Request data in
Purchase Request Data Standard (PRDS) format. PRDS outbound XML file will be
generated when requisition or amendment are approved.
3.2.10. Release 12.2.9
3.2.10.1. PRDS enhancement to support MIPRs

With this enhancement, CLM has the capability to create and amend MIPR-Own
type requisitions using PRDS format. Users can update MIPR acceptance or
acknowledgement using PRDS format.
3.2.11. Release 12.2.10
3.2.11.1. Operating Unit Specific Information in Requisitions

Agencies can create multiple attribute templates based on operating unit for requisitions,
this will enable organizations to have user defined attributes in requisitions based on
business need and users can only see information related to particular operating unit.
3.2.11.2. SAM (System for Award Management) indicator while selecting supplier
in Requisitions
Option provided to differentiate supplier created in SAM and imported into application
to the suppliers created in the application manually.
3.2.11.3. Release funds to backing Requisition

With this enhancement, when funds are decreased in award line via modification, the
funds will remain in the requisition as commitment so that it can be used for funding
another contract line.
3.2.11.4. Moving funds across lines with backing PR in one modification

Users can move or adjust funds along with requisition reference, from one contract line
to another with in the same award using single modification document. This helps users
avoid creating multiple modifications.
3.2.12. Release 12.2.12
3.2.12.1. Intragovernmental Requests to Track Commitments against GT&C

As part of the federal G-Invoicing compliance requirements, the requisition process in
iProcurement has been enhanced to track commitments against each GT&C for
intragovernmental requisitions and to enable IGT order creation by selecting IGT
requestion line(s). Federal users can create IGT requisitions by providing the required
GT&C, Requesting and Servicing agency reference information. Once the PR is
approved, the requisition line(s) will be available in the demand workbench for addition
to an IGT order.
The GT&C number, & internal Contract Number have been added as search attributes in
the Requisition Summary (advanced search), Line Summary and Line Details pages.
The existing MIPR process has been modified to include the MIPR-Own process in IGT
requisitions and MIPR-Others option in the Non-Catalog Requests page.
3.2.13. Release 12.2.13
3.2.13.1. Change IGT Requisition to Modify IGT order

Program management office users or buyers can now initiate change to IGT requisition
lines. When the change is approved by the program management office, the changed
requisition lines are available on the demand workbench for contracting officers or
buyers to implement the change on the existing IGT order by creating a modification.
3.2.13.2. Ability to Create IGT Requisitions with an Amount-based Line Type

Program management office users can now create IGT requisitions with an amount-
based line type. So, instead of specifying a quantity & item price while creating a non-
catalog request, users can simply provide an amount for the line.
3.2.13.3. Ability to Group IGT Requisition Lines while Creating IGT Order
Multiple IGT requisition lines can be grouped to create an IGT order with a single line
and multiple schedules, when the selected requisition lines all have the same item
description, category id, order type lookup code, Purchase Basis, matching basis, Unit of
measurement, & Source Document ID.
3.3. Oracle iSupplier Portal

3.3.1. Overview
CLM enables federal agencies to improve the efficiency of the acquisition process by
allowing suppliers to actively collaborate in the procurement process. Contracting
professionals can streamline all supplier communication through a secure internet-based
portal. Suppliers can access real-time information on awards, modifications, delivery
information, and payment status. This two-way collaboration enables suppliers to submit
bilateral signatures, shipment notices, work confirmations, and invoices, and also allows
them to self-administer their profile information.
The following features are introduced in Oracle iSupplier Portal as part of CLM.
3.3.2. Release 12.1.3+
3.3.2.1. Enhanced Award and IDV information

Oracle CLM iSupplier Portal is enhanced to enable suppliers to access the latest awards
and IDV information and to drill down to information that is specific to federal
procurement features, such as line/sub-line structures, options information, pricing
contracts, and pricing information. Using iSupplier Portal, supplier users can print various
award and IDV documents in government prescribed document formats.
In addition, suppliers can view all the modification details created for the award and IDV
documents. Suppliers can also sign modification documents that require bilateral
signature.
3.3.2.2. Enhancement to Advanced Shipment Notification

Suppliers can enter Advanced Shipment Notices (ASNs), Advanced Shipment Billing
Notices (ASBNs), and Work Confirmations for appropriate lines of the award document.
The system permits suppliers to create ASNs and ASBNs to the extent of funds availability
for these lines.
3.3.2.3. Supplier Changes *

CLM provides the ability to capture multiple business classification details about
suppliers, such as Minority Owned, Veteran Owned, and so on. This information can be
captured for each distinct DUNS number of the supplier and is stored at the supplier-site
level. The business classification details can also be entered at the supplier level or an
address level, and then defaulted for the supplier site when a site is created for the supplier
using a particular supplier address. CLM also provides the ability to search for suppliers
based on their business classification information.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle iSupplier Portal 13
3.4. Oracle Procurement Contracts
3.4.1. Overview
Oracle Procurement Contracts is the enterprise application that creates and enforces better
purchasing contracts. It is a key component of Oracle Advanced Procurement, the
integrated suite that dramatically cuts supply management costs.
CLM helps procurement professionals streamline their contracting process by enforcing
better contract compliance. CLM leverages the capabilities built into the Oracle
Procurement Contracts module to manage and maintain contracts using different
transaction documents such as solicitations, awards, orders, and IDVs.
The following features are introduced in Oracle Procurement Contracts as part of CLM.
3.4.2. Release 12.1.3+
3.4.2.1. Acquisition Plan Summary

CLM provides the capability to address the common, but non-standardized, need across
the federal government to coordinate and plan acquisition efforts. The Acquisition Plan
Summary document provides the flexibility to support simple cases, where minimal
information is required, and complex cases, where more data is captured. This function is
typically performed as a pre-solicitation activity.
Users can perform a combination of actions using the Acquisition Plan Summary,
including capturing information related to the procurement purpose, solicitation method,
extent of competition, potential vendors, supporting attachments in multiple formats, and
other activities associated with a typical procurement cycle. The Acquisition Plan
Summary may be routed through an approval chain before being finalized. CLM also
supports the capability to print draft and finalized copies of the Acquisition Plan Summary
document.
3.4.2.2. Enhancement to Suggested Sections for Clauses by Contract Expert

In CLM, contracting professionals can associate multiple sections to a clause. A clause is
associated with multiple values of any system variable and for each such value a section
name is associated in Contracts Terms Library. When Contract Expert is run in the
contract authoring flow, the clause can be automatically placed in the associated section
name based on the value of defined system variable in the document.
3.4.2.3. Amendment and Modification Section (Clauses)

Using CLM, contracting professionals can define a section on a solicitation amendment,
award, or IDV modification document and place in it all of the terms and conditions
specific to the amendment or modification. These terms and conditions are available only
for the amendment or modification document and are not merged with the conformed
documents.
3.4.2.4. Enhanced Variables Support

In CLM, the Contracts Terms Library has enhanced the Variables feature to support the
new federal attributes that have been introduced. Contract administrators and buyers can
use these federal attributes as variables in standard and non-standard clause text.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Procurement Contracts 14
3.4.2.5. Deletion of Provisional Sections from Solicitation to Award
A number of clauses are specific to a sourcing (solicitation) document and should not
move to the award document. These are termed provisional clauses.
The user can create provisional sections and indicate that they are provisional. These
sections and their clauses will not flow to the award document when the award is created
from the solicitation document. Setting up this feature requires listing each section that
should be provisional.
3.4.2.6. Apply Multiple Templates to a Sourcing or Purchasing Document **

Oracle CLM Procurement Contracts allows the buyer to select and add multiple templates
to a sourcing or purchasing document. All the clauses and deliverables from the new
templates will flow into the document. The Contract Expert rules will, however, be from
the original template and the rules from the additional templates will not flow into the
document. The buyer can also view the different templates that have been added to any
document.
3.4.2.7. APIs for Importing Templates, Rules, Questions and Constants **

These APIs will be available out-of-the-box and can be used by any customer to both
create new entities and update existing templates and rules. The APIs will return error and
warning messages that can be processed and analyzed by the customer.
3.4.2.8. New Clause Descriptor Field **

A hidden field, Clause Descriptor, has been added to the Contract Template, Rules
Definition, and Contract Terms pages. This field can be updated from the Contract
Template and Rules Definitions page. The list of values for this field come from a user-
defined lookup.
3.4.2.9. Clause Mandatory Attribute at Rule level **

Users can specify if the clause suggested by expert is mandatory or not at the rule
definition level. If the user does not specify a value for the Mandatory field, the system
uses the template level setup to determine whether an expert suggested clause should be
added as mandatory or optional.
3.4.3. Release 12.2
3.4.3.1. Instruction Text

Clauses in a document often contain links to external websites where additional
information is available. Clicking on a links to an external site takes the user directly to
the destination page. You can add the destination URL in the instruction text of the clause
with the appropriate HTML tags. This makes the URL available as a hyperlink that
displays in the clause details page.
3.4.3.2. Multi-Row Variables

In earlier releases, the variable field in a clause for a document accepted single values
only. However, it is sometimes a requirement to provide multiple values for a single
variable in the form of an n × n matrix. For example, the variable Contact Number can
have 3 columns—Country, City, and Number, each with multiple rows. Users can now
leverage the User Defined Attribute framework to set up attribute groups and refer to these
groups in Multi-Row Variables.
The variable creation page allows the user to designate the variable as multi-row and to
associate attributes and printing RTF templates with it. The variable, when available in a
Sourcing or Purchasing document, will allow the user to enter multiple rows, in
accordance with the attribute values specified, and this information will be printed in the
PDF document as per the defined RTF template. This feature is available for buyer-
updateable variables and does not support PL/SQL values.
3.4.3.3. Display Clause Number and Sort by Clause Number

The clause number is very important for contracting professionals working with contract
documents. It is often used for searching, updating, or adding clauses. The clause number
is now made available on different contract pages such as the Contract Terms page, the
Search Results page for clauses, and the Summary page after Contract Expert is run.
Clauses in a section must be sortable by the clause number. There is a button which will
sort all the clauses in a section by the clause number. This function is optimized for the
federal clause numbering scheme <NUMBER 1>.<NUMBER 2>-<NUMBER 3><some
text> and performs an alphanumeric sort based on the clause number. A code hook is
provided that contains the clause sorting logic. If a different logic is needed (for example,
if the numbering scheme is different), then implementers can modify the code hook with
their custom logic.
3.4.4. Release 12.2.2
3.4.4.1. Integrated Clause Logic Service

The Clause Logic Service (CLS) is a web service designed to aid in the procurement
process within the Department of Defense and other federal agencies. The main objectives
are to ensure consistent inclusion of provisions and clauses in procurement documents and
to improve the integrity of contracts. CLM allows the user to navigate to the Clause Logic
Service site from the context of a solicitation or an award or IDV document and update
the necessary values on the CLS site. The contracting specialist can initiate an action
within the solicitation or award or IDV document that retrieves the clauses from CLS and
adds them automatically to the document.
3.4.5. Release 12.2.3
3.4.5.1. Document Numbering for Acquisition Plan and Small Business

Coordination Record
Acquisition Plan Summary and Small Business Coordination Record documents can be
numbered in various ways. The numbering of these documents depends on the value of
the profile option Contract Repository Auto-Numbering Enabled. The profile option, set
at site level, determines whether the document number is system-defined or manual.
3.4.6. Release 12.2.5
3.4.6.1. Managing Deliverables of the Contract

Various stakeholders like the award administrator, contracting officer, buyer, contract
administrator, contract office representative (COR) and contract office technical
representative (COTR) can now view and manage the deliverables of an award or contract
document.
3.4.7. Release 12.2.10
3.4.7.1. Print Full Clause Text of Include by Reference Clauses

With this enhancement, contracting officer can decide to print full text of the clause
created as IBR (Include by Reference) in library, while printing award or modification
document.
3.5. Oracle Purchasing

3.5.1. Overview
CLM helps procurement professionals streamline their award and IDV processing. CLM
leverages the capabilities built into the Oracle Purchasing module to manage awards,
orders and IDVs. Oracle Purchasing provides a robust workbench for buying professionals
to manage all procurement activities.
CLM uses the purchase orders and agreements available in Oracle Purchasing to support
various documents used in the federal contracting process such as IDVs (BPAs, BAs,
BOAs, and ID/IQ contracts), awards (standalone contracts and purchase orders) and orders
(delivery orders and BPA calls).
The following features are introduced in Oracle Purchasing as part of CLM.
3.5.2. Release 12.1.3+
3.5.2.1. Line/Sub-Line Structures

In accordance with government regulations, CLM enables contracting professionals to
establish a complex contract line item/sub-line item (CLIN/SLIN) hierarchy in award,
IDV and modification documents. Creation of both informational lines and priced lines
are supported in award and IDV documents. Within an award or IDV document,
CLIN/SLIN structures can be copied and rearranged.

CLM enables contracting professionals to specify lines as option lines in an award, order,
or IDV. Option lines are lines that are not initially funded and cannot be received and paid
for unless the option is exercised. The contracting professionals can exercise option lines
through a formal modification document.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Purchasing 17
CLM provides contracting professionals with the flexibility to create a configurable,
intelligent numbering format for awards, orders, IDVs, and modifications in accordance
with federal government regulations. A document number is generated based on the
numbering setup, and the user can modify the defaulted document number as long as the
document is in draft mode.
The line numbers in CLM are generated according to federal government regulations and
this feature is available as an out-of-the-box-solution. CLINs are automatically numbered
with four-character strings (0001, 0002, and so on) that may be modified by the user. The
corresponding SLINs are inherit the CLIN number and are then appended with a two-
character string, which is either alphabetic (0001AA, 0001AB) or numeric (000101
000102), depending on whether they are priced or informational sub-lines, respectively).

In accordance with FAR Part 16, using CLM, contracting professionals can price awards,
orders, IDVs, and modifications by selecting the appropriate federal contract type such as
Firm Fixed Price, Cost Plus Award Fee, Time and Materials, Cost Sharing, and so on.
This forms the basis for determining the price payable to a vendor. Depending on the
specified contract type, users are prompted to enter additional pricing attributes for the
line and the total line amount is calculated automatically. CLM also provides users with
the ability to mark priced lines with cost constraints like Not Separately Priced, Not to
Exceed, et cetera.
3.5.2.5. Capture Federal Attributes and Nomenclature Specific to Federal

Contracting Processes
CLM offers the ability to capture information specific to federal government business
processes and practices at the header, line, shipment, and distribution levels. Some of the
information includes addresses and contact details for various offices involved in federal
contracting, such as the COTR Office and Property Administration Office. To reduce data
entry effort, the office details are captured as part of user preferences and are defaulted
when the document is created. DPAS Rating, NSN numbers, and FSC/PSC codes are
examples of additional federal attributes that are captured as part of awards and IDVs in
CLM.
CLM ensures that the relevant federal attributes that have been captured in earlier stages
of the procurement cycle move seamlessly from one document to another, as in a flow
from a requisition to solicitation to offer through award.
CLM supports the usage of appropriate specific federal government terms across all user
interfaces and menus to ensure familiarity and ease of use for federal users.
3.5.2.6. Incremental Addition of Funds

With CLM’s incremental funding feature, contracting professionals can create and
approve awards and orders that are fully funded, partially funded, or not funded at all.
Users can incrementally fund the award or order lines using modifications by adding funds
to an existing distribution or adding new distributions to an existing line.
CLM also enforces the rule that it is not possible to receive and pay beyond the funded
line amount, thereby ensuring that the payment cannot be more than the available funds.
3.5.2.7. Modifications and System-Generated Description
With CLM’s modification feature, contracting professionals can create a formal
modification document to capture the changes or the updates made to an approved award
or IDV document. Modifications are created and maintained as separate documents within
the CLM system. During the modification processing, CLM allows users to continue
transactions on the original award or IDV, including receipts, invoices, orders referencing
the IDV, and so on. Users can approve the modification document with the help of a
configurable approval process. When the modification document is approved, the changes
are merged with the original award or IDV (the base document).
Contracting professionals can perform the following transactions using a modification:
• Add funds incrementally.
• Perform a no-cost cancellation of an award.
• Partially terminate an award or line, for default or convenience.
• Exercise options.
• Enable the supplier to indicate acceptance by signing the document.
• Specify a proxy signature on behalf of the supplier.
• View the changed delta values for the pricing fields (quantity, pricing, line
amounts and so on).
Document Builder can be used to add new requisition lines to a modification.
A System Generated Description contains the statements describing the changes carried
out through a modification. This description is generated automatically prior to
finalization and approval of the modification. Modifications are rendered on SF30 forms.
3.5.2.7.1. Capture Change Values in Modifications
For quantity-based lines, users can capture the previous, changed and current line
values for the quantity field at the modification line, schedule, and distribution levels.
Within a modification document, users can specify the incremental changes in the
funded values at the distribution level.
3.5.2.7.2. Update without Modification

Users can update Contracting officer Technical Representative (COTR) address
details and supporting documents on an approved award without a modification.
3.5.2.8. IDV Constraints

In CLM, IDVs can be created with applicable terms and conditions along with complex
ordering and pricing arrangements including quantity-based pricing. CLM supports
creation of IDVs with various constraints like maximum and minimum amounts or
quantities that need to be ordered, maximum or minimum amount sthat need to be ordered
over the life of the IDV, and so on. When orders are created against these IDVs, CLM
ensures that the ordering constraints are honored before these orders are approved.
3.5.2.9. Orders Referencing IDVs

CLM enables contracting professionals to create orders referencing IDVs (for example,
BPAs, basic agreements, and BOAs). Users can create orders with IDV references directly
from purchase requisitions or from an offer that has been awarded to a vendor. CLM
ensures automatic defaulting of information to these orders from various sources such as
purchase requisitions, solicitations, offers, and IDVs as well as from some user
preferences. By providing the IDV and IDV line references in the Document Builder
feature of CLM, users can create orders referencing IDVs. Similarly, by providing IDV
and IDV line references at the time of creating surrogate offers, orders referencing IDVs
can be created. CLM also ensures that the IDV ordering constraints are met when such
orders referencing IDVs are submitted for approval.
3.5.2.10. Document Printing in Standard Federal Forms

CLM enables contracting professionals to print awards, orders, IDVs, and their
modification documents in the appropriate government prescribed forms (SF26, SF30,
SF33, SF252, SF1442, SF1449, and OF347). CLM supports UCF, CSI, and Construction
formats for these forms. The face page for each form is delivered with CLM.
3.5.2.11. Capture and Storage of Historical Point in Time Information

Awards, orders, and IDVs created in CLM store point in time information for key data
elements such as COTR office address, Issuing Office address, Ship-To Address, and
Vendor Address details including DUNS information, CAGE code, DBA and physical
address, and the vendor’s socio-economic information. This information is captured and
stored as it exists when the original document is approved. Users can view this point in
time information on any award, order, or IDV any time after the approval of the document.
If this information needs to be changed, then a modification can be created for the award,
order or IDV.
3.5.2.12. Enhanced Electronic Signature *

CLM provides the ability to capture an electronic version of the contracting officer’s
signature on documents like awards, IDVs, and modifications. System administrators can
define whether or not it is mandatory to capture the electronic version of the contracting
officer’s signature, and can designate individuals as contracting officers.
If a signature is required, then on final approval a notification is sent to the assigned
contracting officer for their signature, regardless of whether or not the contract is bilateral.
When the contracting officer is signing the document the officer’s credentials are
revalidated and the system captures the necessary information for the e-signature. Once
the e-signature has been captured in a document, a representation of the contracting
officer’s signature is displayed at the appropriate location on the printable (PDF)
document.
CLM provides the capability to capture the supplier’s signature in the case of bilateral
contracts. This enhancement allows the supplier’s signature to be printed on the award
document at the appropriate location in the rendered bilateral contract.
3.5.2.13. Warrants *
A warrant is the authority granted to the contracting officer by the federal government that
authorizes him/her to obligate money on behalf of the government. CLM provides the
ability to associate a warrant with a contracting officer. Warrants are defined in the system
with information that includes the warrant name, issuing office, warrant amount and
document types to which the warrant applies. A warrant can be associated with one or
more users. The association between the warrant and the user will determine whether or
not the user has the appropriate authority to approve and to apply an electronic signature
to the award, IDV and modification.
Warrants are validated at the time of document submission as well as during final approval
and signature of the document. The system validates that the document’s total amount is
equal to or less than the limit indicated on the contracting officer’s warrant. In the case of
a modification document, the warrant validation considers the absolute values of the line
change amounts.
3.5.2.14. Workload Assignment and Milestones *

CLM provides the ability to establish workload assignments for requisition lines. A
workload administrator can create a workload assignment for different contracting officers
and assign one or more requisition lines to each assignment. CLM also enables the
workload administrator to effectively manage the workload assignments for all
contracting officers. A workload administrator can add new lines or delete lines from the
existing assignments, suspend an assignment, resume a suspended assignment, and
manually complete an assignment.
Assignments can be associated with one or more milestones. A milestone is defined by its
name, description, type (system or user-defined), estimated number of days for
completion, and the assigned buyer. A set of milestones can be associated with an
assignment with the help of a milestone template or the individual addition of milestones
to an assignment.
Upon assignment creation, the assigned buyer is notified with their assignment details. As
the milestones are reached, the milestone completion information is updated manually for
user-defined milestones or automatically for system-defined milestones. The system
provides the infrastructure to track the data required to calculate the Procurement Action
Lead Time (PALT) for the assignment.
3.5.2.15. Purchase Requisition Line to Fund Modification *

CLM allows users the flexibility to add funds to an approved award through an amendment
to the original requisition as well as through a new requisition. Users can choose funds
from a requisition line and link it to the appropriate award line in a modification, for the
purposes of funding the exercising of an option, adding additional funding to a partially
funded line, or adding new scope with associated funding to an existing line.
3.5.2.16. Contract Closeout *

As part of the award administration process, a user can manually mark a contract as closed
once all activity has concluded against the contract. On approved CLM awards and IDVs,
a Close action gives the user the option to mark the document as contractually closed.
Additionally, a closeout indicator allows the user to specify the current closeout status:
Physically Complete, Administratively Complete, In Closeout, or Closed Out.
Once a document has been closed out, no new actions (such as modifications) can be made
against the document. If subsequent actions are needed, the system allows the user to
reopen the document and update it, and then mark it as closed again. There is no limit to
the number of times a document can be closed, reopened, and closed again.
Note: Contract Closeout functionality has changed in CLM Release R12.2.2 to include
multiple new features. If you are using release R12.2.2 or later, please refer to the section
Contract Closeout under R12.2.2 for the revised Contract Closeout features.
3.5.2.17. Contract Action Reporting to FPDS-NG *
According to Federal Acquisition Regulation 4.602 (FAR 4.602), federal agencies are
required to report contract actions in a central repository called FPDS-NG (Federal
Procurement Data System – Next Generation). FPDS-NG is an external application
maintained by Global Computer Enterprises that collects the contract data from all federal
agencies for reporting purposes. Congress and federal departments use FPDS-NG to track
small business goals, report numbers and amounts of contracts to date, show geographical
placement of contracts, and summarize contract data for a specific contractor. CLM
provides the ability to report contract actions to the FPDS-NG system.
Real-time integration allows users to interact with the FPDS-NG system through
interfaces provided within CLM. Users can seamlessly punch out to FPDS-NG from the
Contracts user interface (awards and IDVs) and initiate creation of a Contract Action
Report (CAR) in the FPDS-NG site. Users can also identify a reason for not reporting or
define a reason for exemption prior to the document being fully approved.
CLM enables the following as part of the FPDS-NG integration:
• Create a CAR – Users can initiate CAR creation from CLM. When a CAR is created
on the FPDS-NG site, the CAR is pre-filled with the data transmitted from CLM.
• View or Update a CAR – CLM enables users to seamlessly punch out to the FPDS-
NG site to view or update a CAR.
• Authenticate a CAR – Users can initiate CAR authentication from CLM using the
Authenticate CAR action. If the CAR has already been completed in all aspects, the
CAR will be authenticated on the FDPS-NG site. If the CAR is not complete, CLM
displays errors and warnings to the user.
• Link or unlink a CAR – CLM provides the ability to link a contract to an existing
CAR on FPDS-NG site. If a CAR was created independently on the FPDS-NG site,
the user can link the existing CAR to the contract in CLM. The user can also unlink a
CAR from CLM system.
• Change a PIID – When a document number is changed in CLM, the corresponding
Procurement Instrument Identification Number (PIID) must be changed on the FPDS-
NG site. CLM provides the Change PIID action to update the PIID.
• Delete a CAR – CLM also provides the ability to permanently remove a CAR from
the FPDS-NG site.
The CLM system ensures that a contracts has a corresponding authenticated CAR reported
on FPDS-NG or that a valid justification is specified for not reporting, before the contract
can be submitted for approval. Additionally, System Administrator functions have been
established for managing user accounts and properly configuring the FPDS-NG module
for a seamless integration.
3.5.2.18. Reports *
CLM provides the ability to generate reports showing information in compliance with the
requirements of FPDS-NG, FedBizOpps, and CCR. Reports can be generated for awards
based on COTR and for purchase requisitions and their corresponding amendments. A
report is available to provide information on the status of various award documents. Users
have the flexibility to build their own custom reports using the information available in
CLM.
3.5.2.19. Support for Taxes
Non-US Federal users of CLM can enable support for tax calculation for award documents
created in CLM. Taxes are calculated for CLM award documents using Oracle E-Business
Tax. CLM award distributions can be funded to the extent of the award schedule amount
plus non-recoverable taxes.
3.5.3. Release 12.2
3.5.3.1. Grouping of Lines

When purchase requisitions are used to create lines in an award document, it is likely that
there are multiple requests for the same or similar goods and services. While placing these
lines into an award, contracting professionals have the option to group these same or
similar requisition lines into a consolidated line in the award.
Contracting professionals can opt to group the requisition lines by one of two grouping
methods: Default or Requisition. The Default method of grouping enables users to group
based on fields such as Item, Unit of Measure, and Category that have the same values as
the basis. The Requisition method of grouping enables users to place individual requisition
lines on the solicitation. Both methods are available to users during the AutoCreate
process in Demand Workbench.
3.5.3.2. Purchase Requisition References Across Multiple Awards or Award Lines

In CLM, a single purchase requisition line can be referenced across multiple lines in the
same award or even across multiple awards. Using this new feature, a single PR line with
funds can be referenced across multiple award lines for utilizing funds. When the awards
are approved, the funds reserved in the backing requisitions are liquidated only to the
extent used within that particular award. This allows the remaining funds on the PR to be
either liquidated by the requestor or used by the contracting professional for funding other
awards. This feature also enables a PR line to be referenced against any award line without
regard to their respective line types, such as goods, amount-based, and so on. Only the
funds information is used from the referenced PR; the other attributes from the PR are not
defaulted to the awards. This feature also allows users to create award lines that have no
distributions or that have distributions that are less than the line amount.

Contracting specialists can create option lines without having to refer to a base line. Option
lines without a base line reference can exist independently. When requesters create option
CLINs without base line references in purchase requisitions, these can be added to the
Document Builder in the Demand Workbench by selecting those lines.
Contracting specialists can copy and replicate one or more award or IDV lines as regular
lines and option lines, and can choose whether base line references should be maintained.
Contracting specialists can also use the enhanced Copy feature to create option structures,
in which a new optional CLIN-SLIN structure is created wherein each option SLIN in the
new structure references priced SLINs of the original structure as base lines. Moreover,
the Copy feature has also been enhanced to let the system default or derive the Need-by
dates, Period of Performance dates, and option From and To dates on option lines.
3.5.4. Release 12.2.1
3.5.4.1. Contract File

CLM provides the ability to maintain a virtual contract file. Throughout the procure–to-
pay cycle, for a given contract document, the system builds a contract file that will
essentially be a view of the related files. A contract file is analogous to a folder that
contains related documents for a given contract. Users can query the contract file based
on parameters such as document number, supplier, issuing office, and buyer.
When the user opens a contract file, it displays all the related document information such
as referencing documents (PR, solicitation), supporting documents and attachments, and
a PDF version of the contract as well as post award administration documents such as
modifications. The user can drill down to view all the contents of the individual referenced
documents.
3.5.4.2. Multiple Modifications (Multi-Mod)

Users can create modifications for multiple CLM awards and IDVs at the same time within
a single user interface. This feature, referred to as Multiple Modifications (or Multi-
Mods), helps the contracting officer ease the burden of implementing certain
administrative changes uniformly across different awards and IDVs with minimal user
intervention.
Users can select multiple award documents or IDV documents, or both award and IDV
documents, and specify administrative updates such as changes in addresses or clauses.
After the documents are selected and the changes specified, modifications are generated
for each of the selected documents. The modifications can be created as drafts or directly
submitted for approval. Draft documents can later be accessed for updating and
subsequently submitted individually for approval. When the modifications generated from
the Multi-Mod process are fully approved, the changes are merged in the conformed
document the same way that regular modification documents are merged in the base
document.
3.5.4.3. Novation
With CLM’s Novation feature, it is possible to change the supplier information on existing
approved contracts. A vendor change may be required when the vendor is part of a merger,
acquisition, or sale or any similar business reorganization process. When a Novation
agreement is received from the vendor and is ready for signing, the users can use the
Multiple Modifications feature to create modifications for novation.
Novation could happen for a name change of a vendor or for a vendor change. For name-
change scenarios, the vendor is still retained in the contract, but the name is updated
through a modification. For the vendor change type of novation, the vendor on a contract
can be changed. Contracting officers can select the contracts on which to change the
vendor in accordance with the novation agreement. For the selected agreements, the
system warns the users about any unprocessed documents such as unmatched receipts or
unpaid invoices. The users can correct these issues or ignore the warnings and proceed
with the vendor change. Any changes to downstream documents such as receipts and
invoices are handled by users according to the business processes of their agencies.
3.5.4.4. Concurrent Modifications
CLM allows one or more users to create multiple draft modifications concurrently for the
same award or IDV. Each draft modification is created from the conformed document and
contains the award or IDV data as it currently exists on the conformed document when the
modification is created. Concurrent updates by multiple users can be made to different
attributes within the various sections of a document such as the header, contract terms,
addresses, and the lines, shipments, and distributions.
Users then approve concurrent modifications in any sequence as they do not need to be
processed in the order in which they were initiated. When the modifications are approved,
the conformed document is updated with the most recent data from each modification and
synchronize action updates other draft modifications with the changes as appropriate. All
existing modification features such as Supplier Signature, System Generated Description,
Document Numbering, and Approvals are also supported for concurrent modifications.
3.5.4.5. Mass Update of Field Values

CLM provides the ability to mass update certain field values on multiple or all lines,
schedules, or distributions in draft award or IDV modification documents. Contracting
professionals can use the Global Update feature to update field values such as Need-By
Date, or Customer Project Code across multiple lines, schedules, or distributions in a
single action. They can add a new value (replacing a blank or null value) or update existing
values across lines, schedules, or distributions using Global Update.
3.5.4.6. Multiple Awards and Umbrella Programs

Umbrella programs are used to track spending for a specific requirement for which ID/IQ
contracts with multiple suppliers are created. Contracting professionals can define and
maintain umbrella programs in the system.
CLM enables contracting professionals to create multiple ID/IQ contracts for multiple
suppliers meeting a specific requirement, and associate them with an umbrella program.
Through a Fair Opportunity Notice process, specific requirements for procurement under
the umbrella program are re-competed within the closed supplier group. When the most
suitable supplier is selected, an Order off IDV that references the umbrella program is
created.
3.5.4.7. Enhancements to Workload Assignments

Workload Assignment pages have been incorporated in the Buyer Work Center to improve
usability.
Workload administrators and contracting specialists can configure and save search filters
on assignments, making it easier for users to build queries that show the active
assignments of a user or a team, assignments with milestones due in the next week,
suspended assignments, and so on.
It is also possible to track the start date, estimated duration, estimated completion date,
and actual completion date on each milestone and on the assignment as a whole.
Workload administrators can re-assign one or more workload assignments from one owner
to another. The old and new owners are notified of the change of ownership. The
Workload Assignment page has a new Action History region to maintain a log of all
actions (suspend, re-assign, manual complete, cancel) performed on the assignment by the
workload administrator.
3.5.4.8. Automatic Updates to Encumbrance (GL) Date

With this release, buyers need not manually update the encumbrance date for each
distribution for a line while creating purchase orders or awards. If the date is within a
closed period, and is invalid, the application automatically displays the system date as the
encumbrance date. To use this feature, the profile PO: Validate GL Date Period must be
set to the newly introduced value Re-default.
3.5.4.9. ORCA Integration

In CLM, the contracting officer can extract the Reps and Certs information for one or
more suppliers directly from the external ORCA system. The contracting officers can
extract the Reps and Certs information for the award’s supplier based on the supplier’s
DUNS number. Contracting officers can even specify the period for which they want this
information. CLM gets this information directly from ORCA and the contracting officers
can view this information as PDF files within the CLM document without ever needing to
access the external ORCA website. These files are also stored as part of the awards and
can be viewed at a later point in time. When a solicitation is awarded and the award
documents are created, if ORCA information was extracted for the solicitation document,
this information is automatically saved with the outcome award.
3.5.4.10. ACRN
CLM enables contracting professionals to automatically generate Account Classification
Reference Numbers (ACRN) to meet DFARS requirements. An ACRN is a two-digit
code, such as AA or AB, that is generated for each unique LOA (Line of Accounting) in
the contract. The numbering is predefined and complies with the DFARS requirements.
The LOA is the accounting classification information (charge account or external account)
at the distribution level. ACRNs are generated automatically when a distribution is saved.
The contracting professional can edit the ACRNs in draft award documents. When a
document is submitted for approval, the system ensures that all ACRNs are valid and
displays an error message if the ACRN is invalid.
3.5.4.11. EDA Integration

CLM offers the ability to generate the PDS XML files out of the box. The current PDS
XML version supported is Version 2.3. The EDA Index file and the PDF files can also be
generated. These files are generated by the system for each award, IDV, order, or
modification document and are stored in a specific location. These files can then be
accessed by users and sent for processing by the Department of Defense’s Global
Exchange (GEX).
3.5.5. Release 12.2.2
3.5.5.1. Post Award Requests

Using CLM, users can initiate and execute post-award administration in an efficient
manner: changes to an approved award need not be carried out through the modification
process only. The modification process is time-consuming and requires formal approvals.
In Department of Defense (DoD) business scenarios, where there are long-term, complex
awards in the system with multiple users working on them, the most common
requirements are to create a large number of change requests for funding and scope
changes to the contract. The post-award request serves as a flexible and quick change
request document for such requirements.
Users can create a post-award request to change header level information, add
attachments, add new lines to an existing contract, or changing existing line information
to include funding and delivery information for the award.
Post-award requests are separate documents that are created, approved, and maintained in
the CLM system. Users can move the changes on post-award requests into formal
modifications. During the modification process, the contracting officer accepts and
incorporates these changes, and the system automatically updates the base award with the
changes when the modification is approved. Post award requests are a quick and easy way
to effect changes to approved documents.
3.5.5.2. Exhibit Lines (ELINs) and Contract Data Requirements Lists (CDRLs)
Contracting specialists can create exhibits in CLM and associate them to contract lines.
Exhibits are documents referred to in a contract. Exhibits can be established either as
exhibit lines (ELINs) or as data deliverables called Contract Data Requirements Lists
(CDRLs). An exhibit can also be either priced or not separately priced within a CLM
contract. CLM numbers the exhibits in accordance with regulations (A001, A002 and so
on. CDRLs are printed in CLM using the default standard form DD1423. Exhibit lines are
printed similarly to normal lines. CLM allows contracting users to copy an entire exhibit
along with its contents as a new exhibit within the same document. Users can also convert
standard lines to exhibit lines and vice versa.
3.5.5.3. Undefinitized Contract Actions (UCAs)

CLM enables Contracting Professionals to perform undefinitized contract actions on an
award or modification document line by marking a contract line as undefinitized.
Undefinized contract actions are contract actions for which contract terms, specifications,
or prices for the goods and services are not finalized when the initial contract is issued.
Users can perform changes on an existing contract that is already included in the scope of
the contract, but needs to be priced (un-priced change orders). They can also bring in new
requirements, which were not part of the scope of an existing contract, and add them as
new line items in an existing contract through modification documents. The execution of
a line marked as undefinitized can continue to the extent of funds available for the line.
Once the contracting professionals and vendors finalize the terms and conditions of the
contract, they can definitize one or more undefinitized contract actions through
definitizing modifications.
3.5.5.4. Support Military Inter-Departmental Purchase Requests (MIPRs)

CLM supports the use of Military Interdepartmental Purchase Requests (MIPRs) for
creating contracts within the CLM system. This feature is specifically for the Department
of Defense (DoD) and can be turned on or off by implementing agencies depending on
their need. MIPRs in CLM behave very similarly to other purchase requests. CLM
supports both MIPR (own) and MIPR (other agencies). MIPR (own) are PRs created
within the CLM system by the agency, but are typically contracted by another agency.
MIPR (other agencies) are requests received from other agencies, which are used to create
contracts in the accepting agency.
The MIPR feature in CLM supports the transactional flows for both the Reimbursement
(Category I) and Direct Citation (Category II) business flows. Again, the MIPR solution
supports the business flow both from the sending agency’s as well as the receiving
agency’s perspective.
3.5.5.5. Vendor Eligibility Check (EPLS Check)

Vendor Eligibility Check or Excluded Parties List System (EPLS) is a requirement for
contracting specialists to check the vendor’s eligibility status during the award process.
The purpose of EPLS is to provide a single comprehensive list of suppliers that are listed
as debarred or otherwise ineligible to do business with the government. In CLM, this is
performed through an automated check with SAM (System for Award Management),
whereby the contracting professional can verify whether the supplier is part of the
debarred list and take the necessary actions.
3.5.5.6. Protest Tracking

CLM provides the ability to capture protests logged by vendors against an award decision.
CLM users can create a new protest in the system and update all the necessary information
including document details, protestor information, and filing and resolution dates, and can
upload attachments and set the proper protest status. The protest will provide the ability
to notify other users, and to share attachment details. Flexible access controls are available
to share the protest information with other users. The contracting specialists can review
the protest information and take appropriate actions within CLM regarding the documents
under protest. Comprehensive search options are available to locate the required protest
document.
3.5.5.7. Contract Closeout

As part of the award administration process, a user can initiate closeout for a contract once
all activity against the contract has concluded. CLM provides sufficient flexibility for
users to initiate close out of different contracts either by an automatic, system-driven
closeout process or through a manual process. Users can initiate the closeout process on
an approved CLM award or IDV through a Closeout Checklist and by assigning different
responsible parties. Users can complete the closeout process by creating a Contract
Completion Statement (DD1594). Users can also receive an automatic notification when
a contract is due for closeout. Users can define staging and retention periods for contracts
in accordance with FAR requirements. Changes to closed out contracts can be made by
re-opening the documents for further changes.
3.5.5.8. Payment Instructions and Payment Terms

CLM allows user to capture payment instructions and payment terms in accordance with
DFARS requirements. Users can specify the payment instructions either at a header or line
level, indicating the sequence in which the funds should be used by the payment authority
in disbursing the funds against the contract. Users can also specify how the advances will
be paid by specifying appropriate payment terms on a contract. The payment instructions
specified are honored during invoice matching for standard invoices and debit and credit
memos.
3.5.5.9. Event-Based Deliveries
In CLM, contracting specialists can specify the delivery dates for various goods and
services based on an event. For events such as After Date of Contract and After Notice of
Award, the system itself will calculate the delivery dates, based on the date of approval of
the contract and the number of days specified. For other events, such as After First Article
Test Approval or After Production Lot Test Approval or Date of Notice to Proceed
Receipt, the users can to specify the dates manually through a modification once the dates
are finalized. Users can also add to the list of events for which they can specify the date
manually through a modification.
3.5.5.10. Integration with WDOL

For contracts that require wage determinations, users of CLM can access the Wage
Determinations Online (WDOL) site from within CLM and search and identify the
appropriate wage determinations. They can specify this wage determination URL within
the contract document, which is used by CLM to locate the wage determination, and store
it as a hyperlinked attachment to the contract document for future references.
3.5.5.11. Changes to Awards and Modifications

Users can now update the Unit of Measure (UOM) for lines through a contract
modification. However, the UOM cannot be changed once the goods or services are
received fully or partially or if any advance payments are made. Using CLM, contracting
specialists can also flag contracts as contingency contracts. Such contingency contracts
can be routed through a different approval chain based on approval setup.
Contracting specialists now can create awards without any distributions. CLM allows
users to specify acceptance and inspection locations for various award lines.
There is also a new feature in CLM to flag procurement of services as severable and non-
severable services. There are built-in validations to ensure that only appropriate funds can
be allocated to lines that are indicated as severable or non-severable services, in line with
regulations.
3.5.5.12. Small Business Coordination Records (SBCRs)

A Small Business Coordination Record is a document that facilitates collaboration
between the contracting specialist of an agency and Small Business Administration (SBA)
Representative, to make a joint determination for a Set-Aside. CLM’s SBCR feature for
modifications allow users to perform collaborative authoring, approve, sign, revise and
withdraw the SBCR document using workflow-based automation.
3.5.6. Release 12.2.5
3.5.6.1. Unlinking Requisitions from Award documents

CLM provides users the ability to manually link the award document line with purchase
requisition lines. The user can manually specify the PR line references for each of the
shipments in the award document. However, there is a need, at times, for the contracting
officer to unlink the linked requisitions for the award line, shipment, or distribution and
re-link it with another requisition document. With this release of CLM this is now
possible.
3.5.6.2. Buyer Reassignment in Demand Workbench
The buyer reassignment functionality has been simplified, allowing the contracting officer
to select the requisition from the buyer’s pool and reassign it to another buyer from
Demand Workbench itself.
3.5.6.3. Link to Requisition Lines using PO BSO Web Services

The Business Service Objects Web Service now supports the linking of requisition lines
with award or modification documents. The linking can be done at line-location level with
multiple requisition lines for a given line location. Also, for each requisition line, the
required requisition distribution as well as the funds to be used from the distribution can
be specified. Distributions are automatically created for each requisition line.
3.5.7. Release 12.2.6
3.5.7.1. Procurement Data Standard (PDS) Inbound

CLM has the capability to receive purchasing documents in PDS (Procurement Data
Standard) format and create an award, IDV, or modification, using Service Invocation
Framework and BSO Web Services, to transform PDS XML.
3.5.8. Release 12.2.7
3.5.8.1. Purchasing Usability Enhancements

CLM Purchasing has been improved with the following enhancements:
• PO Business Service Objects (BSO) Webservices now supports FPDS-NG CAR
information in CLM Awards/Modifications. This helps the organization not to
re-authenticate the CAR information again in FPDS-NG.
• Contracting Officer can view 'Total Change in Fund Value' upfront on the
Modification document without navigating to line details.
• Contracting Officer can select supplier by DUNS and/or CAGE on
Award/Modification/IDV so that users are not required to enter supplier,
supplier site details manually.
• Alert the Contracting Officer/Approver with ‘Save time and Submit time
validations’ during approval edit for Award/IDV/Modification so that the
organization compliance has been met.
• Contracting Officer can add all lines of requisition on to a downstream
purchasing document with one click. It improves the user experience and saves
considerable time for the Contracting Officer.
3.5.9. Release 12.2.8
3.5.9.1. Improvements to Workload Assignments

Workload Assignment pages of buyer work center are enhanced to improve usability.
• Users can now see award number, award status and assignment type in view
buyer workload details, and view workload assignment page. The Award
number has hyperlink to see award details.
• Users can now modify the start date of an assignment so that they can provide
the actual start date of an assignment.
• Contracting officer can create miles stone with sequence number with in
assignment, which will further used for easy sorting.
• Contracting officer can add attachments while updating workload assignment.
3.5.9.2. Manage assignment for all lines of requisition

Contracting Officer can add/remove all lines of requisition on to an assignment with one
click. It improves the user experience and saves considerable time for the Contracting
Officer.
3.5.9.3. One step unlinking and relinking requisition/PAR on same modification

With this enhancement, users can unlink requisition/ Post Award Request (PAR) from
one award line and link to another line with in the same modification document. This
will avoid creation of multiple modification documents and saves considerable amount
of time for contracting officers.
3.5.9.4. Nomenclature Changes for PDF Actions

The action ‘View Conformed Document PDF’ renamed as ‘View Conformed PDF with
Applied Changes’. This is applicable for modifications which are not approved and this
action will generate PDF document to see the conformed copy as if the changes are
approved and merged. It helps contracting officers and award administrators to simulate
the changes on award.
The action ‘View PDF’ in award summary and detail pages is renamed as ‘View
Conformed PDF’ for the approved mods, which has revision greater than zero.
3.5.9.5. Ability to view Point-in-Time PDF

With this release, CLM Purchasing provides ability to view conformed copy of an award
with respect to specific modification. This gives an idea of what has changed with in the
award with respect to modification.
3.5.9.6. Ability to view requisition lines added to specific modification document

CLM users can now see requisition lines against modifications. View Requisitions
action in modification summary page will display requisition lines added through
selected modification. This helps contracting officers to know requisitions used in
specific modification and its status.
3.5.9.7. Procurement Data Standard (PDS) Enhancements

PDS import capabilities improved with the following enhancements.
• With this release, a new REST service created for PDS import, which helps in
avoid setting a separate SOA server.
• The new REST service support multiple versions of PDS simultaneously
• This helps in creating suppliers, supplier contacts, locations and location contact
on the fly by importing supplier data from ‘System for Award Management’
(SAM)
• It helps in importing clauses, provisions, articles and other terms and conditions
through PDS
• It helps in importing attachments used in purchasing documents through PDS
• The new REST service can function in asynchronous mode.
3.5.9.8. Contract printing Enhancements

CLM enables the buying organization to print contracts in appropriate standard forms.
Latest recommendations incorporated as per the FAR guidelines while printing
commercial contract. With this enhancement, Import API supports import of dynamic
sections and users now can rely more on contract expert engine to avoid more number of
static contract templates.
3.5.10. Release 12.2.9
3.5.10.1. EBTax Support for CLM Purchasing

With this enhancement, Contract Lifecycle Management 12.2 version now support
EBTax. Enabling EBTax for CLM will provide additional capability of auto calculating
and defaulting the tax for documents such as Requisition, Requisition Amendment,
Award and Modifications.
3.5.10.2. Ability to identify if Award has pending modification

Users can see an icon in awards summary page, if the award has a pending modification.
This will help users to identify the award and update the existing modification instead of
creating another modification document.
3.5.10.3. Ability to see changed lines in edit modification

Users can see an icon against the line, schedule or distribution, if any of the existing
award line, schedule or distribution is changed. This will help users to identify the
changed/updated line especially when award has more lines.
3.5.10.4. Ability to see changes in the award over a period of time

With this enhancement, users can see the changes happened on an award for all the
attributes in award summary, line, schedule and distribution. This will help contracting
officers to know and compare the changes related to specific award.
3.5.11. Release 12.2.10
3.5.11.1. Global and Local Document Styles (Document Style with Operating Unit)
Organization unit is added in the document style page to make document style as global
or local. If the document style carries specific OU, then it is used or restricted for that
particular operating unit. If there is no specific operating unit in document style, then it
is applicable for all OUs.
With this enhancement, administrator can create or convert existing document styles to
make it available only for a particular operating unit and help in restricting document
styles based on OU while creating award.
3.5.11.2. OU based Attribute Templates
Attribute templates can be created in purchasing to enter or record specific information
while creating procurement documents. This is now enhanced to support attribute
templates based on operating unit. The templates for Awards (Header, Line, Shipment
and Distribution level) and IDVs (Header, Line level) are linked to operating unit with
the document style which carries specific OU and the templates for Requisition (Header,
Line level), Solicitation (Line level) and Offer (Line level) can be created by specifying
respective OU.
3.5.11.3. Operating Unit Specific Information in Award and IDV

Agencies can create multiple attribute templates based on operating unit for Awards and
IDVs. This will enable organizations to have user defined attributes in procurement
documents based on business need and users can only see information related to
particular operating unit.
in Awards and IDVs
Option provided to differentiate supplier created in SAM and imported into application
to the suppliers created in the application manually.
3.5.11.5. Interface Intragovernmental Transactions to G-Invoicing

G-Invoicing (G-INV) is a web-based application created to efficiently manage
Intragovernmental (Intragov) Buy/Sell transactions between two federal agencies from
the agreement of the General Terms & Conditions (GT&Cs) to the IPAC payment
notification. The United States Department of the Treasury’s Bureau of the Fiscal
Service offers this G-Invoicing to all Federal agencies.
G-Invoicing solution in CLM or core Purchasing help agencies to exchange GT&C,

Orders and attachment information to and from G-Invoicing using REST services
specified by FIDS (Federal Intragovernmental Data Standards).
GT&C (General Terms & Conditions) is an Intra-agency agreement between requesting

agency and servicing agency that will be created in G-Invoicing application and can be
imported/pulled into CLM or Core Purchasing.
IGT Order (Intragovernmental Order) is a fiscal obligation between agencies that can be
initiated in CLM or core Purchasing and send/push to G-Invoicing for servicing agency
to review and approval. Once the order is accepted, the servicing agency information
will be pulled and synced to the existing order.
3.5.12. Release 12.2.11
3.5.12.1. Contract Opportunities Posting to SAM using REST services

In an effort to improve how vendors do business with the federal government,
the General Service Administration (GSA) announced that it will be consolidating
different websites into one single site, SAM (System for Award Management). As part
of this transition, the existing FedBizOps website will be moving to SAM which will
support an API to allow posting of contract opportunities from an agency’s ERP to SAM
via REST service. The Oracle Contract Lifecycle Management API to post contract
opportunities has been enhanced to enable integration to SAM.
3.5.12.2. Pull Groups from G-Invoicing to support Intragovernmental

Transactions
Within the Treasury G-Invoicing system, Organization groups have been introduced to
allow Federal Program Agencies (FPAs) to setup a hierarchical agency structure rather
than the traditional flat model. Contract Lifecycle Management pulls these groups,
related information and usage while accessing the Intragovernmental transactions (IGT)
that are sent or received with the G-Invoicing system. Groups can be created as securing
attributes, allowing validation of intragovernmental transactions.
3.5.12.3. Interface Intragovernmental Order Modifications to G-Invoicing

Requesting agency users can create modifications to intragovernmental orders and push
these changes to the G-Invoicing system for servicing agency approval. The
modification details will be synchronized back to the requesting agency, following
servicing agency acceptance or rejection of the modification.
3.5.12.4. Pull and Push Performance Transactions and Display to User

The Performance Transaction within the G-Invoicing system is used to indicate that the
IGT buy/sell activity that has been agreed upon between Requesting and Servicing
Agencies has been completed. Performance is of 3 types
a. Advance
b. Delivered or Performed
c. Deferred Payment
Contract Lifecyle Management pulls the performance transactions that have been pushed
into the G-Invoicing system from a Servicing Agency and displays all the related
information. The Requesting Agency user can record ‘Received’ or ‘Accepted’ quantity
against delivered performance and push the received or accepted performance details
back to the G-Invoicing system.
3.5.12.5. G-Invoicing 4.1 Compatible Changes, Support DII and Originating

Partner Indicator
The following technical updates were made to the G-Invoicing integration:
• Document Inheritance Indicator (DII) and Originating Partner options are
provided in GT&C.
• The status code of SSA (Shared with Servicing Agency) is changed to SP2 in
Order xml.
• IGT Orders service is upgraded to V2_0 in line with G-Invoicing system.
3.5.13. Release 12.2.12
3.5.13.1. Simplified Creation of IGT Orders from IGT Requisitions

A new page has been added to the Demand Workbench in the Buyer Work Center to
provide visibility to all approved IGT requisition lines, so that buyers can filter and
select these to create IGT orders. Once approved, these orders can be shared with the
seller or servicing agency to get acceptance via G-Invoicing.
3.5.13.2. ‘Share with Servicing Agency’ Action Included in Approval Workflow

The manual action on an IGT order to ‘Share with Servicing Agency’ has been
automated & included into the approval workflow. Buyers or requesting agency users
are no longer required to perform this action as it has been included by default with the
final approver that is funding official approval.
3.5.13.3. Support for Seller Facilitated Orders (SFO)

A Seller Facilitated Order (SFO) is an Intragovernmental Order that has been initiated
by the seller/servicing agency. SFOs will be passed to the respective buying/requesting
agency through the G-Invoicing platform for buyer acceptance. Support is now provided
to pull any applicable SFO into Purchasing where it will automatically be created as an
IGT order in Incomplete status. This will allow a buyer to review the order details and
send it for internal approval.
3.5.13.4. Support for Authoring of Intragovernmental Orders through the

G-Invoicing System
The existing Intragovernmental Orders interface program has been enhanced to allow
automatic creation of IGT orders that have been authored and approved in the G-
Invoicing system. Federal agencies can now configure the interface program to pull any
of their approved orders from G-Invoicing so that when the approved order is pulled into
Purchasing, the obligation entries will be posted automatically. The performance
transactions also can be pulled for these orders.
Administrators need to set the ‘Create and approve IGT orders’ to either E-Business
Suite or G-Invoicing as appropriate in the G-Invoicing options page.
3.5.13.5. Ability to Cancel IGT Order Line or Schedule

Modification functionality has been improved to allow Lines or Schedules on an IGT
order to be marked as canceled and for these changes to be pushed to the G-Invoicing
system & actioned accordingly.
3.5.13.6. Ability to Close and Re-Open IGT Orders

The G-Invoicing system only allows IGT order to be closed by the requesting agency.
Buyers can now close an IGT order when the order quantity is equal to the billed
quantity and this change will be pushed to G-Invoicing to update the status and allow
this change to be pulled by the servicing agency.
Requesting agencies can create a modification to re-open an IGT order previously set to
closed status, and the intragovernmental orders interface program re-opens the order in
G-Invoicing.
Agencies can also pull IGT orders that were closed using the G-Invoicing system and
they will update the corresponding existing order to close status when Purchasing or
CLM is used as a financial record system.
3.5.13.7. Ability to View Groups Information and Check Request Status

Agencies are now able to view Group hierarchy, details and associated TAS/BETC
information pulled from the G-Invoicing system. This will help administrators ensure the
accuracy of the TAS/BETC setup details in the Federal Administrator responsibility. A
new status page is available to track push, pull request status, & the response xml from
the G-Invoicing system.
3.5.13.8. Performance Transaction Integration with Receiving and Payables

The performance transactions generated by a servicing agency into the G-Invoicing
system will now be pulled into the Receiving and Payables applications through the
respective open interfaces. This ensures that the various performance transactions -
Advance, Delivered Performance, Received, Adjustment Performance - will generate,
based on ‘Performance type’ and ‘FOB point’ the appropriate prepayment, receipts,
standard invoice & credit note documents.
3.5.13.9. Vendor Eligibility Check using REST API

The existing vendor eligibility check SOAP API has been changed to a REST API to
meet federal system integration standards.
3.5.13.10. Support for Unique Entity Identifier (UEI)

The US federal government now uses the Unique Entity Identifier (UEI) to provide an
identity to each entity doing business with the federal government. UEI assignment is
managed through SAM (System for Award Management). Contract Lifecycle
Management for Public Sector will now display the UEI in CLM and uses it in retrieving
vendor details.
The UEI replaces the previously used DUNS reference.
3.5.13.11. Ability to Get ORCA Details Using REST API

The existing SOAP API to get ORCA details has been enhanced to support a REST call
to SAM to get the latest ORCA details.
3.5.14. Release 12.2.13
3.5.14.1. API to create modification to de-obligate funds on an Award

CLM customers can now use an API to create modification to de-obligate funds on an
approved Award and this will automatically create the modification needed to de-
obligate the funds.
3.5.14.2. Novation through webservice

Using webservices like PDS and BSO, contracting officers can now modify the suppliers
on a current award as part of a novation procedure.
3.5.14.3. Ability to use external IDV value to query awards
Contracting officers can now select an external IDV from the list of values from the
award summary page and query the awards based on this input.
3.5.14.4. Supplier contact as free text while creating award

Contracting officers can now provide a supplier contact as free text in the supplier
details of addresses page when there is no contact defined for the selected supplier.
3.5.14.5. Improvements to query unassigned requisition lines in demand

workbench
Contracting officers can now query requisition lines sourced through an IDV without
assignment reference as unassigned.
3.5.14.6. Ability to Print 7600B for IGT Orders

Contracting officers and buyers can now print the 7600B for IGT orders. The 7600B will
be generated when the order or modification is submitted, and it will be added as an
attachment to the order and notification.
Documents can now be attached by users for an IGT order in any state. Users can also
add the attachment from the notification as well.
3.5.14.7. Ability to Pull Open In-flight Orders from G-Invoicing and Create as
New IGT orders
The Oracle G-Invoicing solution is enhanced to pull open in-flight orders in bulk from
the G-Invoicing system and create them as new IGT orders within Purchasing.
3.5.14.8. Ability to Support Treasury’s 7600EZ Process

The Oracle G-Invoicing solution is enhanced to pull 7600EZ invoice and create as
payable invoice when it is in settled status. The IGT performance page allows user to
accept or reject 7600EZ invoice and the information will be pushed to G-Invoicing.
When the reject or reverse invoice is in settled status, the transaction will be interfaced
to AP to create a credit memo to initiate a refund process.
3.5.14.9. Administrative Change for Seller Facilitated Orders (SFO)

Contracting officers or buyers can now create admin modification to a SFO and push it
to G-Invoicing on an approved order.
3.5.14.10. Ability to Outright Reject SFO

Contracting officers or buyers can now reject a SFO and push to G-invoicing without
any changes to the order.
3.5.14.11. API Payload Migration to JSON for GT&V

The Oracle G-Invoicing solution is enhanced to support JSON payload apart from
existing xml payload for GT&C.
3.5.14.12. Object Class Code as Required Attribute in IGT Order
Contracting officers or buyers are now required to provide the requesting object class
code in distribution details for all the lines of IGT orders.
3.6. Oracle Sourcing

3.6.1. Overview
CLM enables agencies to improve the effectiveness and efficiency of their solicitation and
pre-awarding processes. Using CLM, contracting professionals can give structure to the
entire solicitation process, greatly reducing the time and effort required to perform each
activity in the solicitation cycle. Contracting professionals use templates and flexible
document styles to quickly create various solicitations. They consolidate the demand
coming from similar purchase requisitions into larger, consolidated solicitations for
procurement processing efficiency and better pricing for the government. In CLM, bids
can be gathered in a consistent and structured format, and the online analysis capability
can be used for better awarding decisions.
The following features are introduced in Oracle Sourcing as part of CLM.
3.6.2. Release 12.1.3+
3.6.2.1. Line – Sub-line Structures

Contracting professionals can establish a complex contract line item/sub-line
(CLIN/SLIN) structure in solicitation documents in accordance with government
regulations. Creation of both informational lines and priced lines are supported in CLM
solicitation documents. Within a solicitation document, CLIN/SLIN structures can be
copied and can also be rearranged.

CLM provides the ability to create a configurable, intelligent numbering format for
solicitations in accordance with federal government regulations. Based on the
configuration, a document number will be generated automatically on the solicitation and
solicitation amendment documents and users can modify the defaulted document number
provided the document is in draft mode.
Lines for solicitation or solicitation amendments are automatically numbered in
accordance to line/sub-line numbering conventions used in federal agencies. CLINs are
automatically numbered with four-character numeric strings (0001, 0002, and so on)
which can be modified by the user, while SLINs have appended a two-character string
(0001AA, 0001AB, or 000101, 000102). The contracting professional can modify the
system-assigned line number.

In CLM, the contracting officer is able to price solicitations and solicitation amendment
lines using federal contract types such as Firm Fixed Price, Cost Plus Award Fee, Time
and Materials, Cost Sharing, and so on. This is the basis that determines the pricing
structure that the vendor will use to submit a bid. Depending on the specified contract
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Sourcing 38
type, vendors enter additional pricing attributes for the line, and the total estimated line
amount is calculated automatically.
CLM lines also support cost constraints such as Not Separately Priced, No Charge, Not to
Exceed, etc. Both contract types and cost constraints are applicable to priced lines. The
contract types and cost constraints are applicable to quantity- and amount-based line types.
3.6.2.4. FedBizOpps Integration

CLM enables the buying organization to send a synopsis to the FedBizOpps (FBO)
website as required by federal mandate. The buying organization can now send the pre-
solicitation notice and solicitation information to FedBizOpps in the prescribed XML
schema that can be readily used by FBO. As amendments to the solicitation are released,
FBO may be again notified as per standards.

CLM enables the contracting professional to establish option lines in solicitations—lines
that can be exercised later through a modification to the award, if desired. Option lines
can be associated with base lines and often involve follow-up work. Option lines behave
similarly to regular lines except they are not funded until the option is exercised through
a formal award modification document. In a solicitation document, the buyer can add
option lines. Offer documents may contain suppliers’ responses to the option lines.
3.6.2.6. Solicitation Amendments and System Generated Descriptions

The solicitation amendment functionality in CLM enables contracting professionals to
make changes to existing approved solicitations. Such changes may be made to any level
within the line item hierarchy—for example, to the solicitation header fields or to the
solicitation controls. The amendment document is maintained as a separate document and
is merged with the original document after approval. The system maintains the list of all
the amendments and the changes made in different amendments. A solicitation document
may or may not be cancelled using a formal solicitation amendment document.
A System Generated Description, containing the statements describing the changes carried
out through a solicitation amendment, is generated automatically. This description gets
printed as part of the standard federal forms that are generated for amendments. The
generated statements can be configured to meet the needs of individual agencies.
3.6.2.7. Capture Federal Attributes and Nomenclature Specific to Federal

Contracting Processes
In CLM, solicitation documents support various attributes specific to the federal
government business processes. These attributes include document data that resides on the
solicitation header such as Set Aside Status, Project Code, DPAS Rating, et cetera, and
specific attributes at the solicitation-lines level such as NAICS, FSC/PSC, and. A separate
page captures the federal-specific office addresses such as the Issuing Office, COTR
Office, Requesting Office, Property Administration Office, etc. To reduce the data entry
effort, offices and contact details can be defaulted in a solicitation based on user
preferences.
CLM has implemented some changes to document names, reports, menus, and other
existing entities within the application in order to better align existing naming conventions
with federal terminology. For example, in CLM a negotiation is called a solicitation, and
a quote is called an offer.
3.6.2.8. Capture and Storage of Historical Point in Time Information

CLM ensures that for some of the prescribed data fields like COTR office address, Issuing
Office address, and Ship-To Address, the information does not change in the solicitation
document after approval just because the primary reference data is changed. This ensures
auditability for the critical data on an approved document. A formal amendment is created
to update these details on an approved document.
3.6.2.9. Solicitation Documents Printing as per Standard Federal Forms

CLM enables the buying organization to print solicitations in appropriate standard forms
such as SF18, SF33, SF1449, SF1447, and SF1442. The Uniform Contract Format (UCF)
is the most commonly used standard federal format. UCF involves combining the
Standard Form with solicitation or award data organized in sections B-M (or B-J for
awards). Other formats that exist for specific types of purchases (commercial items,
construction) are also supported in CLM.
3.6.2.10. Online Offer Entry *

Suppliers can now directly create offer documents online in response to a solicitation
document. Suppliers can log in to the application using the Sourcing Supplier
responsibility and view all solicitations that are open to all suppliers or for which they
have been invited to participate.
The supplier can view the solicitation details, send the participation acknowledgement to
the buyer, and create an offer online. Suppliers can review all the solicitation information
including header-level requirements, lines, and contracts terms. In the online offer-
creation process, the supplier can enter the header requirements, line details including
some of the Federal attributes, IDV reference and contract variables.
The supplier can also leverage other features of the online offer process like online
discussions in which the supplier can communicate with the buyer and view offer history.
3.6.2.11. Sort and Delete Suppliers from Invited Suppliers Page

In previous releases, the Invited Suppliers page allowed deletion of invited suppliers one
record at a time. Now, multiple suppliers may be removed at once. In addition, suppliers
can now be sorted alphabetically by supplier name for easier navigation to the desired
supplier record.
This feature is forward-ported to 12.2.5.
3.6.3. Release 12.2
3.6.3.1. Add Requisition Lines to a Draft Solicitation

A buyer can add requisition lines from the Demand Workbench to a draft solicitation or
an amendment solicitation document. The buyer can also select requisition lines and create
a new draft solicitation from the Document Builder. However, the buyer may want to add
some additional requisition lines to the solicitation. In such a situation, the buyer navigates
to the Demand workbench, selects the requisition lines, provides the solicitation number,
and adds the lines to the solicitation. Alternatively, the buyer navigates to the Demand
Workbench by selecting Add Requisition Line from the Lines tab in a draft solicitation
document. This provides a lot of flexibility to the buying organization in the solicitation
creation process, because the buyer can add demand to the draft solicitation any time
during the solicitation-creation process.
3.6.3.2. Grouping of Lines

When purchase requisitions are used to create lines in a solicitation document, it is likely
that there are multiple requests for the same or similar goods and services. While placing
these lines on to a solicitation, Contracting professionals have the option to group these
same or similar requisition lines into a consolidated line in the solicitation.
Contracting professionals can opt to group the requisition lines by one of two grouping
methods: Default or Requisition. The Default method of grouping enables users to use
fields such as Item, Unit of Measure, or Category that have the same values as the basis
for grouping lines. Thus if three lines have the same value in the Item field, they are
consolidated into one line. The Requisition method of grouping enables users to place
individual requisition lines on the solicitation. Both methods are available to users during
the AutoCreate process in Demand Workbench.
3.6.3.3. Mass Update of Field Values

CLM provides the ability to mass update certain field values on multiple or all lines in a
draft solicitation/ solicitation Amendment documents. Contracting Professionals can use
the Global Update feature to update field values such as Need-By Date, Customer Project
Code, etc, across multiple lines/schedules/distributions in a single action. They can add a
new value (replacing a blank / null value) or update existing values across
lines/schedules/distributions using Global Update.
3.6.3.4. Purchase Requisition References Across Multiple Solicitation Lines

In CLM, a single purchase requisition (PR) line can be referenced across multiple lines
within the same solicitation. Using this new feature, a single PR line having funds can be
referenced across multiple solicitation lines for the purpose of utilizing these funds. Only
the funds information from the referenced PR is used. The other attributes from the PR
are not defaulted into the solicitation lines. This feature also allows users to create award
priced SLINs to multiple vendors.

Sourcing buyers can create option lines without having to reference a base line. Unlike
option lines with a base line reference, option lines without a base line reference can
independently flow into downstream documents (purchasing). When requesters create
option CLINs without base line references in purchase requisitions, these can be added to
the Document Builder in the Demand Workbench by selecting the check box for such
lines.
Sourcing buyers can now copy and replicate one or more solicitation lines as regular lines
and option lines, and can opt to maintain the base line references. Sourcing buyers can
also use the enhanced Copy feature to create option structures, where a new optional
CLIN-SLIN structure can be created such that each option SLIN in the new structure refers
to priced SLINs of the original structure as base lines. Moreover, the Copy feature has
been enhanced to let the system default or derive Need-By dates, Period of Performance
dates, and option From and To dates on option lines.
When suppliers respond to solicitations with option lines, the system now displays offer
totals with and without option lines, thereby making the offer comparison process much
easier.
3.6.3.6. Acceptance and Inspection Location

CLM now allows users to specify acceptance and inspection locations for solicitation
Lines.
3.6.4. Release 12.2.1
3.6.4.1. Offer Withdrawal

CLM enables suppliers to withdraw offers submitted on a solicitation. A new solicitation
control has been added to let Sourcing buyers determine whether suppliers are allowed to
withdraw submitted offers for a solicitation. Offer withdrawal is allowed only until the
solicitation is open for bidding. Surrogate withdrawal is also possible, in which the
Sourcing buyer withdraws surrogate offers on behalf of the supplier.
3.6.4.2. Track Amendment Acknowledgements

Sourcing buyers can use the enhanced Supplier Activities page to track which of the
invited suppliers have acknowledged amendments made to the solicitation. The Supplier
Activities page displays a chronological log of all supplier activities on the solicitation.
3.6.4.3. Multiple Awards and Umbrella Program

CLM provides the ability to Sourcing buyers to create multiple ID/IQ contracts against
multiple suppliers meeting a specific requirement, as an outcome of a solicitation process.
These ID/IQ contracts can optionally be linked to one or more umbrella programs.
Umbrella programs can be used to track spending for a specific need for which ID/IQ
contracts with multiple suppliers are created.
CLM also provides the ability to create and publish Fair Opportunity Notices to a closed
group of suppliers with which the procuring agency has ID/IQ contracts established.
Typically all eligible suppliers under an umbrella program are invited to respond a Fair
Opportunity Notice in order to identify the most suitable supplier for a delivery order. The
outcome of a Fair Opportunity Notice is typically an order referencing an IDV that refers
to the umbrella program.
3.6.4.4. Unsolicited Lines

Suppliers can add unsolicited lines in an offer document in response to a solicitation. In
some situations, it is easier for the suppliers to respond to the solicitation by providing
their own line structures. For example, the solicitation may have a single line, CLIN1.
However, in response, the supplier may provide the following structure: Informational
CLIN1 with SLIN1 and SLIN2.
Buyers can allow suppliers to add unsolicited lines in an offer document in response to a
solicitation by means of a new control in the Solicitation Controls page. The supplier can
create unsolicited lines (amount- or quantity-based) in the offer document and also provide
the line description and pricing details. The buyer can also allow suppliers to provide line
category, unit of measure, cost constraint, or contract type, or default these values from
the solicitation using further controls in the Negotiation Configuration page. The supplier
can link the unsolicited line to one or more solicitation lines and designate the unsolicited
lines as alternate or additional, as applicable. Buyers can also enter unsolicited lines on
behalf of the suppliers during the surrogate offer creation process.
3.6.4.5. Multiple Active Offers

A supplier user can create multiple active offers for the same solicitation. This is required
when the supplier can offer multiple solutions that can meet the buyer’s requirements. The
buyer can allow suppliers to provide multiple active offers through a control option in the
Solicitation Controls page. All the suppliers’ active offer are also available for comparison
in analyze and award flows. Buyers can also enter multiple offers for a supplier using the
surrogate offer process. The system allows the buyer to create separate award documents
for all the lines awarded from each active supplier offer.
3.6.4.6. ORCA Integration

In CLM, the contracting officer can extract the Reps and Certs information for one or
more suppliers directly from the external ORCA system. Once offers are received from
suppliers and the solicitation is closed for further offers, the contracting officers can
extract the Reps and Certs information for the supplier based on the DUNS number of the
supplier. They can even specify the period for which they want this information. CLM
gets this information directly from ORCA and the contracting officers can view this
information as PDF files within the CLM document without ever needing to access the
external ORCA website. These files are also stored as part of the solicitations and can be
viewed any time later. When a solicitation is awarded and the award documents are
created, if ORCA information was extracted for the solicitation document, this
information is automatically propagated to the award.
3.6.5. Release 12.2.2
3.6.5.1. Vendor Eligibility Check (EPLS check)

Vendor Eligibility Check, or Excluded Parties List System (EPLS), is a requirement for
contracting specialists to check the vendor’s eligibility status during the solicitation
process. The purpose of EPLS is to provide a single comprehensive list of suppliers that
are listed as debarred or otherwise ineligible to do business with the government. In CLM,
this is performed through an automated check with SAM (System for Award
Management), whereby the contracting professional can verify whether the supplier is part
of the debarred list and take the necessary actions.
3.6.5.2. Protest Tracking

Vendors responding to solicitations may lodge protests for various reasons. To track these
protests, CLM users can create a new protest and update all the necessary information
including document details, protestor information, filing and resolution dates, and can
upload attachments and set the proper protest status. The notification feature can be used
to notify other users about the protests. Flexible access controls ensure that users view
only appropriate data. The contracting specialists can review the protest information and
take appropriate actions within CLM with respect to the solicitation referred to in the
protest. Comprehensive search options are available to locate the required protest
document.
3.6.5.3. Exhibit Lines (ELINs) and Contract Data Requirements Lists (CDRLs)
Contracting specialists creating solicitations can include exhibits in their documents.
Exhibits are documents that are referenced to contract lines in a solicitation. Exhibits can
either be lines (ELINs) or data deliverables called Contract Data Requirements Lists
(CDRLs). An exhibit can either be priced or not separately priced. In CLM, exhibit lines
and CDRLs are by default numbered in accordance with regulations (A001, A002, and so
on). CDRLs are printed in CLM using the default standard form DD1423 and exhibit
lines are printed similarly to other lines, but are shown under a different section in the
various standard forms. Users can copy exhibits as well as convert standard lines to exhibit
lines or vice versa.
3.6.5.4. Event-Based Deliveries

In CLM, contracting specialists can specify the delivery dates for various goods and
services based on an event. For events such as After Date of Contract and After Notice of
Award, the system itself will calculate the delivery dates, based on the date of approval of
the contract and the number of days specified. For other events, such as After First Article
Test Approval or After Production Lot Test Approval or Date of Notice to Proceed
Receipt, the users can to specify the dates manually through a modification once the dates
are finalized. Users can also add to the list of events for which they can specify the date
manually through a modification
3.6.5.5. Integration with WDOL

For contracts that require wage determinations, users of CLM can access the Wage
Determinations Online (WDOL) site from within CLM and search and identify the
appropriate wage determinations. They can specify the wage determination URL within
the contract document, which is used by CLM to locate the wage determination, and store
it as a hyperlink attachment to the contract document for future references.
3.6.5.6. Small Business Coordination Records (SBCRs)

Small Business Coordination Record is a document that facilitates collaboration between
the contracting specialist of an agency and a Small Business Administration (SBA)
representative, to make a joint determination for a Set-Aside. CLM’s SBCR feature for
solicitations allow users to perform collaborative authoring, approve, sign, revise and
withdraw the SBCR document using workflow based automation.
3.6.6. Release 12.2.4
3.6.6.1. Mass Update of Buyers

It is sometimes necessary to change the buyer on a solicitation document. For example, if
a buyer leaves the organization, their negotiations must be reassigned. A new concurrent
program now allows you to add a new buyer to existing solicitation documents based on
the parameter values provided.
3.6.7. Release 12.2.5
3.6.7.1. Solicitation Amendment After Close Date

CLM provides users the ability to create amendments on closed solicitation, thus allowing
contracting officers to create amendments to solicitation even after the close date is
reached.
3.6.8. Release 12.2.7
3.6.8.1. Apply Templates on Draft Solicitations

Consistent availability of Solicitation Templates makes it easier to maintain standards
defined in templates. To avoid replacing active data, when applying a template the
current data takes precedence over data defined in the template, (An exception is
template negotiation style, which does replace a different style specified on a draft
solicitation).
Applying a template is now available if a template has not already applied for the
following:
• On draft solicitations, such as created through copy or document builder
• Creating a RFX from a Purchasing BPA (renegotiating an agreement)
3.6.9. Release 12.2.8
3.6.9.1. Uptake revised DD-2579 form and enhancements to SBCR

Small Business Coordination Record (SBCR) page enhanced to support latest version of
DD-2579, which is a management tool to screen proposed acquisitions to ensure that an
equitable opportunity provided to small and disadvantaged business to participate in the
proposed acquisition. This help contracting officer to generate DD-2579 as per DFARS
guidelines.
3.6.9.2. Sourcing Usability Enhancements
With this release, Contracting Officer can select supplier by DUNS and/or CAGE on
‘Create Surrogate Offer’, ‘Manage Draft Surrogate Responses, ‘Add Suppliers’ page of
solicitation creation and ‘Create Award’ page, so that users are not required to enter
supplier, supplier site details manually.
3.6.10. Release 12.2.9
3.6.10.1. Approvals Management Engine for Solicitation Approvals

Oracle Sourcing users now have the option to use the Approvals Management Engine
(AME) for approving Solicitation documents before publishing them. Approvers can be
defined either in parallel or in sequential manner using AME. Enterprises can use the
predefined AME transaction type or can create a custom transaction type based on their
business requirements. Buyers can add ad hoc approvers using the Approval Options
page.
A new indicator provided to differentiate supplier created in SAM to the suppliers
created in the application manually. SAM Suppliers appear with the indicator.
3.6.10.3. Offer Received time made non-mandatory while creating surrogate quote
Offer received time made non-mandatory while creating surrogate quote. This help
contracting officers/contracting specialists quickly create/upload surrogate quotes in the
application.
3.6.10.4. Award and Complete as a new action if there is single quote for
solicitation
A new action ‘Award and complete’ introduced to avoid multiple actions if there is a
single quote against the solicitation. With this action, contracting officers need not
perform ‘award by offer’ first and then ‘complete award’ process, the quote selected
automatically and he can click on this new action to complete the process.
3.6.11. Release 12.2.10
3.6.11.1. Operating Unit Specific Information in Solicitation and Offer

Agencies can create multiple attribute templates (at header and line level) based on
operating unit for solicitation and offer (at line level). This will enable organizations to
have user defined attributes in solicitation based on business need and users can only see
attributes related to selected operating unit.
3.6.12. Release 12.2.12
3.6.12.1. Ability to Provide Payment Office Details in Solicitation

The Payment Office option is included in the Addresses region of the solicitation and
preference pages. Optionally, agency users can add payment office details to a
solicitation and these details will carry forward to the IGT Order, when the solicitation is
awarded to a supplier.
3.7. Oracle Contract Lifecycle Management for Public Sector Command

Center
3.7.1. Overview
Oracle Contract Lifecycle Management for Public Sector Command Center provides
actionable insights on a single page that contain metrics, charts, graphs and other data
that help both contracting officers and project managers to track their workload and
review on areas that require immediate attention. Command centers are available for
both contracting office and Program Management Office.
3.7.2. Release 12.2.8+
The following functionality requires Oracle Enterprise Command Center
Framework Release 12.2 V2
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content DocumentOracle Contract Lifecycle Management for Public Sector Command Center 46
3.7.2.1. Acquisition Plans
Acquisition plan dashboard shows metrics such as plans that are Pending
Approval, Expiring Plans in next 30days and Rejected Plans. Charts in this
dashboard help PMO users to analyze acquisition plans status and track
milestones due or overdue. Results table with attribute groups provides
information about acquisition plans data and user can update the plans in source
system.
3.7.2.2. Requisitions
Requisitions dashboard has metrics such as pending approval, rejected
requisitions and Requisition lines for which options due for exercising. Charts in
requisitions dashboard help users to track requisition status, acquisition status
and funding status. Users can analyze requisitions for specific project(s),
FSC/PSC codes, Contract type, category or item. Results table help users in
quickly checking the transactional information about requisitions. Contracting
Officers can see unassigned requisition and review the current work of
contracting specialist to create assignment.
Requisitions dashboard help PMO users to stay alert and to have a quick review
to check if any requisition that need their immediate attention and for
Contracting Officers, it helps in prioritizing unassigned requisitions and assign it
to contracting specialist.
3.7.2.3. Solicitations
Solicitation dashboard has metrics such as amendments, pending approval,
pending SBCRs, open protests, FBO exception reasons and deliverables that are
due. Charts in solicitation help contracting officer to track status and time taken
for each phase of solicitation process. Results table with attribute groups
provides transactional information about solicitation and CO can directly click on
view to check the document from transactional system.
3.7.2.4. IDVs
IDV dashboard has metrics such as expiring IDVs, Awaiting signatures, pending
approval, pending CAR authentication and pending J&A postings.
Charts in IDV dashboard help contracting officer to track status and utilization.
Results table provides transactional information about awards and CO can
directly click on view to check the document from transactional system.
3.7.2.5. Awards
Awards dashboard provide information about awards that are pending for
approval, awaiting signature, pending CAR authentication, pending J&A
postings. Dashboard also alerts contracting officer about options, deliverables,
closeout tasks that are due and protests that are open so that CO can take
immediate action.
Charts in awards dashboard help contracting officers in analyzing award amount,
funded value, billed amount and set aside amount for all the awards related to
specific project, supplier, contract type, requesting office, issuing office, etc.
Results table provides transactional information about awards and CO can
directly click on view to check the original document from transactional system.
Awards dashboard also accessible for PMO users to track the progress of
contractual documents.
3.7.3. Release 12.2.9++
3.7.3.1. Liquidate Funds

The liquidate action is used to unreserve funds from partially utilized
requisition(s) or requisition lines(s). If there are any funds remaining on a
requisition and they will not be used to fund any award, then these remaining
funds can be liquidated. Using the command center filters, users can select a date
range along with the liquidatable flag from the available refinements to review
the list of requisition lines that can be liquidated.
3.7.3.2. Cancel Requisitions

Requisition(s) or requisition lines(s) that are approved but not placed on any award can
be cancelled using the Cancel action. Once the requisition is cancelled, the funds will go
back to the budget pool and the requisition status will be updated to Cancelled so that the
requisition is no longer used in any process. Using the command center filters, users can
select a date range and requisition in pool flag to get the list of requisitions that are not
yet placed on any award or solicitation. Users can also select project details from
available refinements to filter data further to review and cancel requisition(s) or
requisition lines(s).
3.7.4. Release 12.2.11
The following functionality requires Oracle Enterprise Command Center
Framework Release 12.2 V7
3.7.4.1. New Attribute Group to track Quantities and Amount details

Users can now track the quantities and amounts for a requisition line in the
requisitions dashboard. A new attribute group is added to view quantity
delivered, quantity cancelled and remaining quantity for goods-based lines;
amount delivered, amount cancelled and remaining quantity for amount-based
lines.
3.7.4.2. Sequential data load uptake

Sequential data load is the process of running data load per identifier that is
Operating Unit in CLM Command Center. Administrators can now run full load
for an operating unit without data set reset for an operating unit. This will
improve the performance of data load since it segregates the data load into
multiple parts.

EBS_122_Cum_RCD_CLM

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EBS_122_Cum_RCD_CLM

Uploaded by

Copyright:

Available Formats

ORACLE E-BUSINESS SUITE

RELEASE CONTENT DOCUMENT

Oracle Contract Lifecycle Management for

Prepared by Oracle E-Business Suite Product Development

Last Updated: June 9, 2023

Copyright © 2023, Oracle and/or its affiliates.

2.1. Purpose of Document

3.1. Release Overview

Many other features are also available in CLM.

3.2.2.1. Line/Sub-Line Structures

3.2.2.2. Option Lines

3.2.2.3. FAR/DFARS-Compliant Document Numbering and Line Numbering

3.2.2.4. Federal Pricing Contracts and Complex Pricing Calculation

3.2.2.6. Requisition Amendment

3.2.2.7. Federal Attributes

3.2.2.8. Support for Tax Calculation

3.2.2.9. Ability to change POET information on Requisition Amendment

3.2.3.1. Option Line Enhancements

3.2.3.2. Purchase Requisition Lines Without Distributions

3.2.4.1. Military Inter-Departmental Purchase Requests (MIPRs)

3.2.5.1. Automatic Updates to Encumbrance (GL) Date

3.2.6.1. PR Amendment Attachment History

3.2.6.2. Copy Attachments to PR Amendments

3.2.6.3. Additional Enhancements to Military Inter-Departmental Purchase

3.2.6.4. View Solicitation Details

3.2.6.5. Requisition Amendment Details in Approval Notification

3.2.7.1. Purchase Request Data Standard (PRDS) Outbound and Related

3.2.7.2. Visibility into Procurement Activities

3.2.7.3. Active Items Displayed to Requester

3.2.8.1. Purchase Request Data Standard (PRDS) Inbound

3.2.9.1. Ability to move funds between lines in Requisition

3.2.9.2. Purchase Request Data Standard (PRDS) Inbound Enhancements

3.2.9.3. Purchase Request Data Standard (PRDS) Outbound Enhancements

3.2.10.1. PRDS enhancement to support MIPRs

3.2.11.1. Operating Unit Specific Information in Requisitions

3.2.11.3. Release funds to backing Requisition

3.2.11.4. Moving funds across lines with backing PR in one modification

3.2.12.1. Intragovernmental Requests to Track Commitments against GT&C

3.2.13.1. Change IGT Requisition to Modify IGT order

3.2.13.2. Ability to Create IGT Requisitions with an Amount-based Line Type

3.3. Oracle iSupplier Portal

3.3.2.1. Enhanced Award and IDV information

3.3.2.2. Enhancement to Advanced Shipment Notification

3.3.2.3. Supplier Changes *

3.4.2.1. Acquisition Plan Summary

3.4.2.2. Enhancement to Suggested Sections for Clauses by Contract Expert

3.4.2.3. Amendment and Modification Section (Clauses)

3.4.2.4. Enhanced Variables Support

3.4.2.6. Apply Multiple Templates to a Sourcing or Purchasing Document **

3.4.2.7. APIs for Importing Templates, Rules, Questions and Constants **

3.4.2.8. New Clause Descriptor Field **

3.4.2.9. Clause Mandatory Attribute at Rule level **

3.4.3.1. Instruction Text

3.4.3.2. Multi-Row Variables

3.4.3.3. Display Clause Number and Sort by Clause Number

3.4.4. Release 12.2.2

3.4.4.1. Integrated Clause Logic Service

3.4.5. Release 12.2.3

3.4.5.1. Document Numbering for Acquisition Plan and Small Business

3.4.6.1. Managing Deliverables of the Contract

3.4.7.1. Print Full Clause Text of Include by Reference Clauses

3.5. Oracle Purchasing

3.5.2.1. Line/Sub-Line Structures

3.5.2.2. Option Lines