You do not have permission to edit this page, for the following reason:
You can view and copy the source of this page:
Return to Biz Apps Release Notes.
The 7.12 Release introduces significant enhancements to the Icertis Contract Management (ICM) Sourcing Business Application. It strives to improve user experience and usability by continually improving ICM functionalities and the user interface.
The key enhancements of this release include:
Enhancing the RFx Summary Report and RFx Details Report to provide a consolidated view of data for RFx with various categorization, thus providing the visibility to top management on sourcing activities and helping them to take more informed decisions.
These release notes provide an overview of the enhancements to ICM Experience for Sourcing.
571048 – Displaying full names of supplier contacts
Previously, when selecting a supplier contact, only the first name of the supplier contact was displayed.
With this release:
The supplier contact full name column will be displayed by default on the supplier contact selection page, supplier contact details page and grid view of the supplier contact association.
This makes it is easier for buyers and administrators to identify and select the correct supplier if there are multiple suppliers with the same first name.
Note: This is applicable for RFx, RFI, Rounds and Bulk Agreements.
571053 – Displaying names of external and internal attachments as uploaded by the user
Previously, when downloading the RFx package, the name of the downloaded package displayed names that were not the same as the folder structure of the RFx, and also created duplicate files. This made it difficult to identify the file that was uploaded and downloaded.
Now,
Note: This is applicable to both RFx and RFI.
627740 – Ability to use any masterdata for supplier and supplier contacts
Previously, to add supplier contacts, the buyer could select them from a list of supplier and supplier contacts in the Supplier window. This list of contacts belonged to a particular masterdata contract type. The customers had their own masterdata contract type for maintaining supplier and supplier contacts.
Now, buyers can use any supplier and supplier contact masterdata contract type to add suppliers.
Note: This is applicable to RFx and RFI.
573430 – Sourcing entities workflow revamp
The workflow for Sourcing has been revamped to make it specific for Sourcing, in order to support the flexibility that is required in sourcing. The following enhancements have been made to the RFx, round, bid and awarding workflow respectively.
590362 – Displaying bids of all suppliers to buyers throughout RFx lifecycle
Previously, buyers could view bids only after they were submitted by the suppliers. However, it was not possible to know whether the supplier had submitted the bid (in case of open RFx), or if the supplier had submitted or declined it until it was closed (in case of sealed bid).
Now, buyers can now view the status of bids for each supplier, regardless of whether the RFx is an open or sealed envelope, depending on the status of the bid.
These statuses include:
</ul>
</ul>
</ul>
Note: The bid responses are displayed or hidden based on whether the bid was submitted or not submitted by the suppliers.
</ul>
</ul>
Buyers can view the status of the RFx depending on the status of the round, bid and the type of RFx. They can view the status of the bid at any time, but cannot view the bid response until it is submitted by the supplier.
</ul>
</ul>
</ul>
572078 – Availability of bid analysis attributes and values in the bid analysis Excel
The bid analysis Excel will contain all the bids, for all the suppliers, for all the rounds. The bid analysis will also contain currency information of bid currency and RFx primary currency, along with bid analysis attributes converted to RFx primary currencies.
An attribute for bid analysis is defined in the masterdata. Users can add the bid analysis attribute for each RFx item and specify its value while creating an RFx or associated document. This helps the buyer to get all the information in the Excel sheet to be able to easily analyze a bid for a supplier.
Buyers can now:
Note: Minimum one round has to be completed for any bid analysis.
560481 – Ability to copy RFx/RFI
Procurement team often uses the same template, line items, questions and attachments for repetitive procurement of similar category items. Previously, as RFx/ RFI could not be copied, buyers had to create multiple sourcing events manually with different suppliers several times using the same line items, questions, attachments, etc.
Buyers now have the capability to copy the RFx which helps reduce the timelines and avoids duplication of efforts for similar RFx creation. Additionally, as procurement involves globally distributed buyers’ team, they clone the sourcing event at the regional level and link them to one another. Linking the copied RFx to the original RFx can be achieved by enabling the Link To RFx flag on the Copy Record window.
Along with the RFx, users also have the ability to select any associated documents (line items, questions, attachments, etc.) where the Allow Copy with Associations flag is enabled at the contract type level. By default, the flag is disabled, hence only the RFx is copied without its associations.
Now:
When copying the RFx:
The changes can be viewed in the History audit log on the RFx Details page.
Note:
This is applicable for RFx and RFI.
560526 – Modify RFx
Buyers require a provision to add, remove or edit certain parts of the RFx, as all the required criteria or business requirements may not be available at a glance during the RFx creation.
With this release, ICM provides the ability to modify a RFx which is in Approved or later status until the awarding is initiated.
When RFx modification is initiated:
</ul>
If any of the keys is enabled, then buyers can make changes to supplier/ supplier attachment/ questions respectively when RFx is in modification. If the key is disabled, then respective changes will not be allowed when RFx is in modification.
For RFx modification approval, the Administrator can configure rules to set the Approver. Approver can approve or reject the changes:
When no Approver has been added, the RFx is auto-approved.
567274 – Ability to evaluate suppliers for RFx
Users require a provision to evaluate the RFx for various suppliers on their capabilities. Also, they want to provide the scores for better information that will help them in the awarding process.
Now, buyers and administrators can conduct a review, and evaluators can score the suppliers as well as provide feedback upon the supplier submissions.
Buyers can now:
Assigned evaluators will now:
The Start Evaluation button will be available only after the round is closed.
567584 – Introducing Currency Support in Sourcing
Previously, ICM did not support using multiple currencies at an organization level that could be used in sourcing events.
With this release, ICM Administrators can now:
</ul>
Note: Every currency added to the currency master must have a validity period that allows using currencies in different entities.
</ul>
</ul> Note: Duplication of exchange rates for same currency and same validation is not allowed.
</ul>
</ul> The activities performed by the buyer relevant to the currency selected for an RFx are logged in the RFx History.
</ul>
</ul>
</ul>
Note: The applicable RFx exchange rate is available to both the buyers and suppliers.
</ul>
573435/573436 – Ability to add bulk line items to RFx
The bulk associations capability has enabled ICM to handle a large number of associations in the tune of thousands, by presenting itself as a lightweight association as well as tremendously improving performance. The Sourcing event can include many line items for an RFx ranging from 500 to 50,000 maximum. In Sourcing, line items are considered as associations.
The bulk association configuration has now been simplified by providing aEnable Bulk Processing flag at contract type definition level which triggers a set of defaults that has been intentionally restricted. The end user experience for the bulk association has not changed from the way that the conventional association is handled from the UI, rather the underlying data structure has been further enhanced to make it go the distance.
Performance has been the key while introducing and designing this new association, which has given way to the new type of instance, namely the Proxy Instance, which is retrieved in every GET call. The actual instances are referred by using this proxy instance, thereby reducing the load on the GET APIs. Specialized GET and SET APIs have also been introduced for bulk associations to improve its adaptability and ease-of-use.
Bulk associations have very effectively consumed the Elastic Search Bulk API to sync a large set of data at one go, rather than the traditional way of one instance at a time, adding to the boost in performance.
Bulk association is enhanced to be able to address the large volume of data that Sourcing apps require. These enhancements include:
404532 – Ability to edit round start and end dates
Previously, when the round was scheduled or open, buyers could not change the round start and end dates. However, in Sourcing, timelines are likely to change for various reasons, internal or external, which could not be achieved earlier.
Buyers can now edit the round start and end date when the round is in Draft, Waiting for Approval, On Hold, Open or Approved statuses.
You can make changes only to the round end date when the round is in Open state. The changes made to the round start and end date are captured in the History on round Details page.
It is not mandatory to run the approval workflow for the round after changing the Planned Start Date and Planned End Date
Now, buyers will be able to view the validations for the prerequisite and mandatory contracts for the shortlisted suppliers only. For a shortlisted supplier, if all the prerequisite contracts are inactive, or if any one of the contracts is active but not in Approved or later state, then the validations will be displayed. For example, if there is one shortlisted supplier with two prerequisite contracts NDA 1 (in Draft state) and NDA 2 (in Waiting for Approval state), then validations will be displayed.
The validations will not be displayed for shortlisted suppliers when at least one active prerequisite contract exists, and all such contracts are in Approved or later state. For example, if there is one shortlisted supplier with two prerequisite contracts NDA 1 (in Approved state) and NDA 2 (in Expired state), no validations will be displayed since one of the two prerequisite contracts (NDA 1) is in Approved or later state.
625383 – Prerequisite and mandatory contract validations for linked agreements
Buyers have the option to select mandatory and prerequisite contracts while creating the RFx. The attributes for mandatory and prerequisite contracts are interlinked. The prerequisite contracts are derived from the mandatory contracts. So, if the buyers select the following contracts – NDA, Warranty Agreement, Fixed Cost Agreement as mandatory, then they have the option to select one, more than one or all as prerequisite contracts.
For example, if an NDA is the prerequisite contract for accessing the RFx, then the validations are done such that ICM expects that the instance of an NDA contract type for all the suppliers is associated with the RFx and contract should be in Approved status. Similarly, if contract types are made mandatory, then the instances of these should exist before RFx is sent for approval.
576084 – Addition of the RFx Change History Report
Previously, the Sourcing application provides the change history of rounds, bids and awarding separately for rounds and bids within the RFx.
Now, the Change History Report has been introduced, which provides a consolidated view of all actions for entity. This will help the procurement team to view the entire history of rounds, bids and awarding within a RFx, at a glance for auditing purposes.
This report is accessible only to buyers (not suppliers), from within a RFx transaction, hence only authorized users with access to a RFx can view this report. All the latest updated information captured at the point of time when the report is generated will be displayed in it.
The Change History Report can be generated by applying the following filters - Entity Type, User Name, User Role and Supplier Name. By default, the report is filtered on Entity Type as RFx/RFI. Based on the requirement, users can change filters. The report provides details with columns such as Date & Time, Event, Entity Type, Entity Name, User Name, User Email, User Role, Supplier Name, Notes, Attribute Name, Previous Value and New Value.
Note:
573599 – Enhancements to Sourcing reports
The RFx Summary Report and RFx Details Report provide a consolidated view of data for RFx with various categorizations, thus providing the visibility to top management on sourcing activities and helping them to take more informed decisions.
You do not have permission to edit this page, for the following reason:
You are not allowed to execute the action you have requested.
You can view and copy the source of this page:
Return to Biz Apps Release Notes.