Users need to be able to distinguish between, and transact, federal and non-federal documents. In a CLM instance, the user needs to have the ability to transact with both federal as well as non-federal documents (even within the same Operating Unit). A CLM user should be able to access either federal documents or non-federal documents. However, for other users such as Receiving users or Payables users, view-only access is provided for both federal as well as non-federal documents transactions.
In order to enable users to have access to the core CLM features, the following setup steps need to be performed:
Add the following CLM seeded responsibilities for your users, as relevant, using the System Administrator responsibility:
CLM Purchasing Contracting Professional
CLM Purchasing Super User
CLM Sourcing Contracting Professional
CLM Sourcing Super User
CLM Sourcing Team Member
CLM iProcurement
Note: When creating custom responsibilities, please ensure that the seeded CLM responsibilities should be replicated, and then modified as per your business requirements.
Before creating a custom responsibility, run the concurrent program Function Security Reports (Report Set) to detail the menu structure and function information of any seeded responsibility. This can be used as the basis to build the custom menus / responsibilities.
Function Security: If custom responsibilities are using a menu which includes the submenu Purchasing Home Page for Buyers (PO_BUYER_HOME_PAGE), ensure the following menu exclusions are present in the responsibility definition. If the responsibility is for viewing/editing CLM documents, then exclude the menus PO Order Tab and PO Agreement Tab. If the responsibility is for viewing/editing non-CLM documents then exclude the menus CLM Purchasing Orders Tab and CLM Purchasing Agreements Tab.
The function Generate Description for Solicitation Amendment (PON_GENERATE_DESCRIPTION_FN) is relevant for CLM Sourcing responsibilities. If excluded, user cannot generate/view the change description, since the action will not appear in the Solicitation Amendment page.
The function Allow User to Edit the System Generated Description ( PO_CLM_CHGDES_ALLOW_EDIT ),when present in the menu of a responsibility, enables the user to edit the System Generated Description. This is relevant for the CLM responsibilities.
The function System Generated Description (PO_GENERATE_DESCRIPTION) is relevant for CLM responsibilities. If excluded, user cannot generate/view the change description, since the action will not appear in the modification page.
Function security has been implemented to enable or disable seeded views in Buyer Work Center: The non-CLM views menu PO_VW_FUNCTIONS must be included in all non-CLM responsibilities. The CLM views menu PO_CLM_VW_FUNCTIONS must be included in all CLM responsibilities.
Enable the following profile option values:
| Sl. No. | Profile Option Name | Set at which Level | Value |
|---|---|---|---|
| 1. | FND: Industry ID | site level | Public Sector - National Government |
| 2. | PO: CLM Installed | site level | Yes |
| 3. | PO: CLM Enabled | responsibility level | Yes |
| 4. | PO: Enable IDV In Document Builder | site level | Yes |
For PO (Purchasing) documents, the CLM Enabled checkbox at the Document Styles page enables you to make a Purchasing document CLM enabled or not.
For PON (Sourcing) documents, there is no CLM Enabled checkbox at the Document Styles page. The new seeded document type - Solicitation - is CLM enabled. The non-FAR documents in Sourcing are: RFI, RFQ, Auction. The Sourcing FAR document is: Solicitation.
Implementers need to note that there are different steps used to enable transaction documents as CLM documents.
| Type of Document | Control Level | Description |
|---|---|---|
| Purchasing Documents | Document Style | A new flag at the Document Style level has been added to indicate whether the document style is CLM Enabled or not. The checkbox (flag) is called CLM Enabled. |
| Solicitation Documents | Document Type | A new document type - Solicitation - is automatically CLM enabled. |
| Requisitions | Document Header | A flag has been added at the requisition header level to indicate if it’s a CLM requisition or not. Therefore if the user logs in with a CLM responsibility and creates a requisition, the flag is automatically selected as being CLM enabled. |
If the value of the profile option PO: CLM Installed is set to Yes, then iSupplier Portal users have access to both FAR and non-FAR documents. If the value of the profile option PO: CLM Installed is set to No, then iSupplier Portal users have access to only non-FAR documents.
CLM features are available for those documents that have CLM Enabled check box selected (for Purchasing) and header flag selected for Requisition. For Sourcing, CLM features are available for those documents that have a Document Type Solicitation. When the profile option PO: CLM Enabled is set to Yes for a given responsibility, the user can create and view only those documents that are CLM enabled.
For a given responsibility, if the value of the profile option PO: CLM Enabled is set to Yes, the CLM features are available for the user. Features such as Document Numbering, CLIN/SLIN, Options, Pricing, Funding, etc., are available for use.
Document search is restricted to CLM documents only. The user also sees additional search criteria that can be used in searches.
All Lists of Values (LOVs) have their display lists governed by the profile option settings. Thus only those values relevant for CLM display in the LOVs.