Professional Documents
Culture Documents
EBS 122 Cum RCD CLM
EBS 122 Cum RCD CLM
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document ii
3.3.2.2. Enhancement to Advanced Shipment Notification 12
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.2. Option Lines 17
3.5.2.3. FAR/DFARS-Compliant Document Numbering and Line Numbering 18
3.5.2.4. Federal Pricing Contracts and Complex Pricing Calculation 18
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.3.3. Option Line Enhancements 23
3.5.4. Release 12.2.1 24
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
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document iii
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.6. Oracle Sourcing 34
3.6.1. Overview 34
3.6.2. Release 12.1.3+ 34
3.6.2.1. Line – Sub-line Structures 34
3.6.2.2. FAR/DFARS-Compliant Document Numbering and Line Numbering 34
3.6.2.3. Federal Pricing Contracts and Complex Pricing Calculation 34
3.6.2.4. FedBizOpps Integration 35
3.6.2.5. Option Lines 35
3.6.2.6. Solicitation Amendments and System Generated Descriptions 35
3.6.2.7. Capture Federal Attributes and Nomenclature Specific to Federal Contracting Processes 35
3.6.2.8. Capture and Storage of Historical Point in Time Information 35
3.6.2.9. Solicitation Documents Printing as per Standard Federal Forms 36
3.6.2.10. Online Offer Entry * 36
3.6.2.11. Sort and Delete Suppliers from Invited Suppliers Page 36
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document iv
3.6.3. Release 12.2 36
3.6.3.1. Add Requisition Lines to a Draft Solicitation 36
3.6.3.2. Grouping of Lines 37
3.6.3.3. Mass Update of Field Values 37
3.6.3.4. Purchase Requisition References Across Multiple Solicitation Lines 37
3.6.3.5. Option Line Enhancements 37
3.6.3.6. Acceptance and Inspection Location 38
3.6.4. Release 12.2.1 38
3.6.4.1. Offer Withdrawal 38
3.6.4.2. Track Amendment Acknowledgements 38
3.6.4.3. Multiple Awards and Umbrella Program 38
3.6.4.4. Unsolicited Lines 38
3.6.4.5. Multiple Active Offers 39
3.6.4.6. ORCA Integration 39
3.6.5. Release 12.2.2 39
3.6.5.1. Vendor Eligibility Check (EPLS check) 39
3.6.5.2. Protest Tracking 39
3.6.5.3. Exhibit Lines (ELINs) and Contract Data Requirements Lists (CDRLs) 39
3.6.5.4. Event-Based Deliveries 40
3.6.5.5. Integration with WDOL 40
3.6.5.6. Small Business Coordination Records (SBCRs) 40
3.6.6. Release 12.2.4 40
3.6.6.1. Mass Update of Buyers 40
3.6.7. Release 12.2.5 40
3.6.7.1. Solicitation Amendment After Close Date 40
3.6.8. Release 12.2.7 41
3.6.8.1. Apply Templates on Draft Solicitations 41
3.6.9. Release 12.2.8 41
3.6.9.1. Uptake revised DD-2579 form and enhancements to SBCR 41
3.6.9.2. Sourcing Usability Enhancements 41
3.6.10. Release 12.2.9 41
3.6.10.1. Approvals Management Engine for Solicitation Approvals 41
3.6.10.2. SAM (System for Award Management) indicator while selecting supplier 41
3.6.10.3. Offer Received time made non-mandatory while creating surrogate quote 42
3.6.10.4. Award and Complete as a new action if there is single quote for solicitation 42
3.6.11. Release 12.2.10 42
3.6.11.1. Operating Unit Specific Information in Solicitation and Offer 42
3.7. Oracle Contract Lifecycle Management for Public Sector Command Center 42
3.7.1. Overview 42
3.7.2. Release 12.2.8+ 42
3.7.2.1. Acquisition Plans 42
3.7.2.2. Requisitions 42
3.7.2.3. Solicitations 43
3.7.2.4. IDVs 43
3.7.2.5. Awards 43
3.7.3. Release 12.2.9++ 43
3.7.3.1. Liquidate Funds 43
3.7.3.2. Cancel Requisitions 44
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document v
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
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
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
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Release Overview 4
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Release Overview 5
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+
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle iProcurement 7
3.2.3. Release 12.2
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle iProcurement 8
3.2.6. Release 12.2.5
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle iProcurement 9
3.2.7. Release 12.2.6
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle iProcurement 10
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
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle iProcurement 11
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle iSupplier Portal 12
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+
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Procurement Contracts 15
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Procurement Contracts 16
3.4.6. Release 12.2.5
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Purchasing 17
3.5.2.3. FAR/DFARS-Compliant Document Numbering and Line Numbering
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).
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Purchasing 18
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Purchasing 19
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.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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Purchasing 20
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Purchasing 21
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Purchasing 22
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Purchasing 23
3.5.4. Release 12.2.1
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Purchasing 24
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Purchasing 25
actions (suspend, re-assign, manual complete, cancel) performed on the assignment by the
workload administrator.
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Purchasing 26
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Purchasing 27
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Purchasing 28
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Purchasing 29
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Purchasing 30
• 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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Purchasing 31
• 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.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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Purchasing 32
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.4. SAM (System for Award Management) indicator while selecting supplier
in Awards and IDVs
Option provided to differentiate supplier created in SAM and imported into application
to the suppliers created in the application manually.
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Purchasing 33
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Sourcing 34
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Sourcing 35
for the critical data on an approved document. A formal amendment is created to update
these details on an approved document.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Sourcing 36
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Sourcing 37
3.6.3.6. Acceptance and Inspection Location
CLM now allows users to specify acceptance and inspection locations for solicitation
Lines.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Sourcing 38
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Sourcing 39
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Sourcing 40
3.6.8. Release 12.2.7
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.2. SAM (System for Award Management) indicator while selecting supplier
A new indicator provided to differentiate supplier created in SAM to the suppliers
created in the application manually. SAM Suppliers appear with the indicator.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Sourcing 41
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.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),
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content DocumentOracle Contract Lifecycle Management for Public Sector Command Center 42
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++
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content DocumentOracle Contract Lifecycle Management for Public Sector Command Center 43
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).
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content DocumentOracle Contract Lifecycle Management for Public Sector Command Center 44