19Define Self Service Procurement Configuration

This chapter contains the following:

Manage Information Template Descriptive Flexfields

Information Template: Explained

An information template is used to gather additional information from a user. It can be assigned to an item, a category, or a request form. Information templates are used in the creation of a Request Form to provide the flexibility to add additional attributes in a request form in order to gather required information from a user. Information templates are also applicable to item master items and purchasing categories.

The data entered for an information template, which is associated with a request form, item or category, is available as attachments in downstream products (such as Purchasing) after the requisition is approved. When creating an information template, the catalog administrator selects the attachment category that determines if the attachment will be available to the supplier or buyer.

Using Information Templates

Information Templates are created in a Procurement Business Unit and are available to Requisitioning Business Units serviced by that Procurement BU. In the event where a Requisitioning BU is serviced by multiple Procurement BUs, and more than one service provider had assigned an information template to an item or category, applicable information templates from all service provider Procurement BUs will be returned.

Information templates are available to the user if the items or request forms that the information templates are associated with are available to the preparer.

Procurement catalog administrators can define a unique information template name so they are easily identifiable in a request form. Information template header information provides users the ability to specify a non-unique Display Name, while creating information templates with unique information template names. For example, more than one procurement BU can maintain information templates to collect business card information. The same Display Name, Business card information, can be used on these information templates to indicate the purpose of these templates when displayed in Oracle Fusion Self Service Procurement. Procurement Catalog Administrators can also define an information template section description or instruction text providing users with specific instructions on how to fill out the form.

Information templates can only be deleted if they are not referenced. An information template is considered referenced if it is applied on any requisition lines, whether in completed or incomplete state. This is to prevent deletion of an information template that is currently in use.

Once an information template is deleted, it is no longer returned on the Manage Information Templates page.

Adding Attributes

Information template attributes are maintained as Descriptive Flexfields.

Attributes first need to be set up in the Descriptive Flexfields application, and the catalog administrator specifies the descriptive flexfield context on the Create and Edit Information Template page to apply the list of attributes.

For example, the catalog administrator set up a context Business Cards Marketing, with the following context sensitive fields:

  • Job Title

  • Organization

  • Office Location

When creating an information template, the catalog administrator can then specify in the Attribute List field the context Business Cards Marketing, which will associate the attributes to the information template.

Note: The maximum number of attributes that can be created for an information template is fifty.

Existing information attributes are maintained as attachments downstream, such as in Purchasing.

Supported Attributes

The following attribute types are supported by descriptive flexfields:

  • Text: Text attributes can be setup using descriptive flexfield to be added to an information template. For example, the procurement catalog administrator can create an information template called Business Card Information USA to be used for collecting related information when ordering business cards. Examples of text typed fields are Name, Title, Address and so on.

  • Number: Procurement catalog administrators can create number types attributes using descriptive flexfields, to be used in an information template. For example, region code, telephone, and area code.

  • Standard Date, Standard DateTime and Time: Procurement catalog administrators are able to define date format attributes in descriptive flexfields, to be used in an information template. This allows for automatic date formatting according to globalization requirements, since 09/01/2007 may mean September 1, 2007 in the US, but January 9, 2007 in others.

  • List of Values: Value sets can be added to Information Templates through descriptive flexfields as List of Values. Implementing attributes as List of Values allows enforcement of values that can be populated in these fields. For example, as part of an address, the Country field can be implemented as list of values containing only countries that are applicable.

  • Choice Lists: Choice lists make use of value sets as well, similar to List of Values.

End Dates

Procurement Catalog Administrators can specify an End Date on an information template. An information template is inactive if the system date is more than or equal to the End Date.

When an information template is inactive, it will no longer be applied when items (to which this information template is assigned) are added to the requisition. Requisitions created with lines that are associated to this information template will continue to display the information template information.

For incomplete requisitions, the inactive information templates are no longer available at the time the requisition is retrieved.

For copied and withdrawn requisitions, information templates are also no longer available if the information template is inactive at the time the requisition is copied or resubmitted.

Manage Catalog Category Hierarchy

Category Hierarchy: Overview

A category hierarchy presents a hierarchical view of the catalog to users. Category hierarchies allow administrators to create a parent category that includes child categories. When users navigate through the parent category, the child categories appear, helping users to navigate quickly to the category containing the products they need.

There are three different types of category hierarchy in Procurement.

  • Procurement Category Hierarchy: Used by Purchasing, Self Service Procurement, and Suppliers.

  • Browsing Category Hierarchy: Used in Self Service Procurement.

  • Products and Services Hierarchy: Used in Suppliers.

Category Hierarchy: How Browsing Categories and Item Categories Fit Together

If you manage a large number of products and services, you may need a way to organize the products in the catalog to make it easier for users to navigate to the products they want to buy. The category hierarchy presents a hierarchical view of the catalog to users.

Categories are used to classify items. Category hierarchies allow you to create a parent category that includes child categories. When users navigate through the parent category, the child categories appear, making it easier to quickly find the products they need.

You can develop your own method of categorizing products or you can use standard coding systems such as UNSPSC. Some of the benefits of adopting a standard coding system are visibility of spend analysis throughout the corporation, cost control optimization, and ability to explore all the e-commerce capabilities.

The figure below shows the category hierarchy for a catalog. There are two types of categories in the catalog that define a catalog hierarchy: browsing categories and item categories. It is not required to have the same number of levels in all branches of the hierarchy.

Category hierarchy diagram showing browsing category
hierarchies, and related item category UNSPSC codes

Browsing Categories

Browsing categories are also known as navigation categories. They define the category hierarchy for category browsing. The category hierarchy helps users browse for catalog items. Browsing categories can be either a parent or child to another category, but cannot contain any items. Browsing categories are optional and companies can decide what categories should be enabled for browsing.

You can associate catalogs (local, punchout, informational) and request forms to the browsing categories. When user navigates to the category, the associated content type will be displayed. An alternative to setting up browsing categories is to tag punchout, informational, and request forms with keywords, so that users can find them when performing basic search.

Item Categories

Item categories are used to group items for various reports and programs. An item category is a logical classification of items that have similar characteristics. For Procurement, every item must belong to an item category. You can:

  • Place item categories under browsing categories.

  • Search the catalog and sort by item category name. The item category name is displayed in the search pages.

  • Bulk load by item category code.

Category Hierarchy with Catalog Association: Explained

Users can search for all content (local content, punchout, request forms, informational content) regardless of how the content is grouped. Administrators can group punchout, informational catalogs, and request forms by category, and the browsing feature will also retrieve punchout, informational catalogs, and request forms together with local content.

Local content (item master items and agreement lines) is associated with purchasing categories. Request forms, punchout, and informational catalogs can optionally be associated with any level of the category hierarchy (browsing or purchasing category).

Hierarchy With Associated Catalog Content

When you associate the punchout, informational, local, and request form to a category, the application's parser travels up and down the tree to associate the punchout, informational, local and request form content with all the browsing and purchasing categories of the same branch. Item master items, and agreement items are indexed with their corresponding purchasing categories. For example, in the illustration below, when you navigate down the branch from Information Technology browsing category to the Computer Servers purchasing category, the search results will always include the Dell USA punchout, which is associated with Computers. The application associates the punchout catalog Dell USA with the categories of the same branch as Computers which are Information Technology, Components for Information Technology, Computers, and Computer Servers.

The informational catalog How to Request Computer Services is associated with the browsing category Information Technology. As you navigate the Information Technology branch, the Informational Catalog is seen at the level of Information Technology, Components for Information Technology, System Cards, Computers, Memory Module Cards, and Computer Servers.

Local catalog items are also included in browsing results. Using the example in the figure below, items in BPAs with suppliers Techworks or Zones Corporate that are tied to the purchasing categories Memory Module Cards or Computer Servers will show up as you navigate down the Information Technology branch, based on the content available to you from the content zone.

The procurement catalog index is automatically updated after any changes to the hierarchy are saved.

The figure below shows a catalog category hierarchy structure.

Catalog category hierarchy structure

How can I configure what appears in top categories?

You can configure which categories are included in the Requisitions page Top Categories panel using the Manage Catalog Category Hierarchy page. Select the Featured Category check box for a category to include it in the Top Categories panel.

Assign Returned Requisition Lines to Previous Buyer: Explained

Configure the application to assign returned requisition lines to the previously assigned buyer with the site-level profile option Retain Last Assigned Buyer on Requisition Line.

If enabled, when a requester resubmits a returned line, the line is reassigned to the buyer that returned it. Buyer assignment rules are not invoked when returned requisition lines are resubmitted, but are invoked for other active lines, such as those with Rejected, Withdrawn, or Incomplete status. Set the Retain Last Assigned Buyer on Requisition Line (POR_RETAIN_LAST_ASSIGNED_BUYER) profile option to Yes to enable this feature. It is located in the Setup and Maintenance work area, on the Manage Administrator Profile Values page. The default value for the Retain Last Assigned Buyer on Requisition Line profile option is No.

Assign All Requisition Lines to the Same Buyer: Explained

Configure the application to assign all lines in a submitted requisition to the same buyer with the site-level profile option Use Same Buyer for all Lines in a Requisition.

If enabled, when a requester submits a requisition, the buyer assigned to the first requisition line is used as the buyer for all lines in the requisition. In the Setup and Maintenance work area, on the Manage Administrator Profile Values page, set the Use Same Buyer for all Lines in a Requisition (POR_ASSIGN_REQ_SAME_BUYER) profile option to Yes to enable this feature. The default value for the Use Same Buyer for all Lines in a Requisition profile option is No. If a buyer cannot be derived for the first line of a requisition, then no buyer is assigned to other lines of the requisition. A procurement agent who has access to other agents' documents can process all such lines on the Process Requisitions page User-specified buyers on any lines other than the first are overwritten with the buyer assigned to the first line if this feature is enabled.