19Define Purchasing Configuration

This chapter contains the following:

Define Common Purchasing Configuration

Purchase Order Line Types: Examples

These examples demonstrate why the line type feature is an important part of the purchase order. It enables you to clearly differentiate orders for goods from those for services.

Quantity-Based Purchasing

Use quantity-based line types when you want to specify the quantity, unit of measure, and unit price for the items you are ordering. Oracle Fusion Purchasing provides Goods as an initial quantity-based line type. You can modify this line type or create new quantity-based line types to satisfy your business needs.

This table provides an example of a line with the line type Goods.

Type Item Quantity UOM Price

Goods

AS54888

8

Each

$1,107

Fixed Price Services Purchasing

You can use fixed price-based line types when you want to order general business services by a fixed amount. Oracle Fusion Purchasing provides Fixed Price Services as an initial fixed price-based line type. You create an order for fixed price service by selecting a fixed price services line type, category, item description, and total amount of the service. You can receive and match fixed price services by amount.

This table provides an example of a fixed price-based line with the line type of Fixed Price Services.

Type Description Category Price

Fixed Price Services

Office Cleaning

Office Miscellaneous

$1,350

Create Document Style: Critical Choices

You can use purchasing document styles to control the look and feel of a purchasing documents in the application to match their business usage. Through reusable document styles, you can turn on or off various procurement features, thereby simplifying the user interface. In addition, document styles provide the ability to define purchasing document names that align more closely with the naming conventions of your organization's business.

When you create a purchasing document using a document style, disabled features are hidden. For example, if price breaks are not allowed on an agreement document style then agreements using this style will not display the price break region.

Commodities

You can create a document style for a specific commodity such as services. This document style optimizes field labels and presentation for that commodity, thereby simplifying purchase order entry.

Blanket Purchase Agreement

You can enable a document style for use with blanket purchase agreements. This document style could be used to limit the use of price breaks, for example. You can also give a document style a distinctive name. For example, a construction company might name their agreement styles Equipment Agreement and Supply Agreement to easily separate the two types of agreements.

Contract Purchase Agreement

You can enable a document style for use with contract purchase agreements utilizing the naming convention of your organization.

Reviewing the Delivered Document Style for Outside Processing: Explained

You can review the delivered document style for use with purchasing documents having outside processing items.

Use the Manage Document Styles task in the Setup and Maintenance work area, Procurement offering, Procurement Foundation functional area. On the Manage Document Styles page find and open the document style named Outside Processing Style. On the Edit Document Style page review the delivered settings:

  • Status is Active.

  • Purchase Basis is Goods.

  • Line Types is All. (For Goods only.)

  • The Outside Processing value is enabled.

    • The Configurations and Consignment Terms values are not enabled. These three values are mutually exclusive, only one can be enabled in a document style at a time.

  • Display names are enabled for Outside Processing Purchase Order, Outside Processing Blanket Agreement, and Outside Processing Contract Agreement.

    • For Outside Processing Blanket Agreement the Price Breaks Allowed value is set to Yes.

You cannot change the delivered Outside Processing Style. If needed, you can create a new document style with a different set of values for outside processing.

Defining a Document Style for Outside Processing: Procedure

You can create a new document style for purchasing transactions for outside processing items.

You cannot change the delivered document style for purchasing transactions for outside processing items. If needed, you can define a new document style for outside processing, using the Create Document Style page. You can find the page in the Setup and Maintenance Work area, Procurement offering, Procurement Foundation functional area, Manage Document Styles task.

To define a new document style for outside processing:

  1. Enter a name and description for the document style, and set the status to Active.

  2. Select the Purchase Bases: Goods, Services or Both.

  3. Set the Outside Processing Enabled option to Yes.

    The Outside Processing Enabled, Consignment Terms Enabled, and Configuration Ordering Enabled options are mutually exclusive. You cannot enable more than one of them in a document style.

  4. Set the Line Types: All or Specified.

  5. In the Purchase Order section enter the Display Name.

  6. In the Blanket Purchase Agreement and Contract Purchase Agreement sections, you can optionally enable the document style for those purchasing document types. Also enter display names for them. For blanket agreements you can also define whether or not price breaks are allowed.

For document styles having outside processing enabled, you cannot disable the Outside Processing Enabled option if any purchasing document is using the style.

Change Order Template: Explained

A change order template is a set of guidelines that enables an organization to specify what constitutes an internal change and what constitutes an external change to a procurement document during the course of its lifecycle.

Some of the document change terminology:

  1. External Change Order

  2. Internal Change Order

External Change Order

This is a type of change order that modifies an attribute or attributes that may be relevant to the supplier as defined in the change order template. Examples include changes to price, amount, or contract terms. This is also referred to as a supplier facing change order. In commercial organizations these types of changes are referred to as an amendment and in a Federal organization they are called MODs or modifications.

Internal Change Order

This is a type of change order that modifies an attribute or attributes that may not be relevant to the supplier as defined in the change order template. Examples includes changes to a descriptive flexfield or a certain category of attachments. These are also referred to as administrative changes.

Typically this will be a buyer or requester requested change order. That is a change order requested by a user whose role is either buyer or requester.

What's a purchasing document report template?

The purchasing document report layout is set by a purchasing document report template. The report template determines what information is displayed in the purchasing document report. the template also provides the headers, footers, text, style, and pagination of the printed document.

Your options for report templates include:

  • Use one of the delivered report templates.

  • Create a report template in RTF format and upload it to Oracle Business Intelligence Publisher (Oracle BI Publisher).

  • Copy and configure one of the delivered report templates using Oracle BI Publisher.

You can use the Configure Procurement Business Function task to select a document layout for each purchasing document type. You can find the task In the Setup and Maintenance work area, Procurement offering, Procurement Foundation functional offering.

Configuring Purchasing Document Reports: Procedure

As a procurement application administrator with the data model developer role, you can copy and configure new versions of the delivered purchasing document report templates. Use the report creation capabilities of Oracle Business Intelligence Publisher Enterprise (Oracle BI Publisher), and Oracle BI Publisher Desktop.

Aspects of copying and configuring delivered purchasing document report templates that are explained in this topic include:

  • Report templates.

  • Data models.

  • General steps to copy and configure a report.

Report Templates

Two predefined purchasing document report templates are delivered: Purchase Order PDF Report and Purchase Agreement PDF Report.

The reports have two main elements:

  • Procurement data source.

  • Report layout template.

Obtain the delivered report templates in Oracle BI Publisher, using the following path: Catalog/Shared Folders/Procurement.

You can configure new versions of the delivered reports by adding fields to the report layout, to include reporting attributes not shown in the delivered versions, such as:

  • Attributes from the delivered data model.

  • Additional attributes from tables not available in the delivered data model.

Data Models

Two data models are delivered, one for each purchasing document report: Purchase Order Data Model, and Purchase Agreement Data Model. Obtain them from Oracle BI Publisher, using the following path: Catalog/Shared Folders/Procurement.

Use the data models to:

  • See all of the fields that can be included in a report.

  • Retrieve fields from other tables that aren't included in the delivered data models.

  • Make changes to the data models for the two purchasing document types independent of each other.

Copy and Configure a Purchasing Document Report

To copy and configure a purchasing document report follow these general steps.

  1. Use Oracle BI Publisher to:

    1. Obtain the delivered data model and report template appropriate to the purchasing document type.

    2. Make a copy of them to configure into a new version, preserving the delivered versions unchanged.

    3. Edit the data model and export the XML.

    4. Download the report template.

  2. Use Oracle BI Publisher Desktop, in Microsoft Word, to:

    1. Import the data model to the copy of the report template.

    2. Modify the report template to add fields to the report that are not a part of the delivered report.

  3. Use Oracle BI Publisher to:

    1. Upload the modified report template to the catalog, making it available to other users.

The modified report template displays in the Configure Procurement Business Function task. You can find the task in the Setup and Maintenance work area, Procurement offering, Procurement Foundation functional area. For each affected business unit, you can associate the modified report template with the appropriate purchasing document type.

For more information refer to the white paper available on My Oracle Support (MOS): Document Publishing and Communication in Oracle Fusion Purchasing (document ID 1610339.1). The document:

  • Provides detailed procedures for using Oracle BI Publisher to copy and configure reports.

  • Includes a copy of the delivered XML data model.

Buyer Assignment Rules: Explained

Your organization's procurement buyers have different sets of expertise. Identifying the best buyer for a purchasing transaction can play a significant role in cost sensitive business procurement. As a procurement manager you can use buyer assignment rules to help with this process.

The application assigns a buyer to a requisition line only if a suggested buyer is not provided by the requester. The application assigns a buyer using the following steps, in order of precedence:

  1. Evaluate the buyer assignment rules, as set up in the Manage Buyer Assignment Rules task. Find the task in the Setup and Maintenance work area, Procurement offering, Purchasing Foundation functional area.

  2. Use the default buyer from the item definition in the deliver-to organization of the requisition line. Find the requisition line on the Process Requisitions page, in the Purchase Orders or Purchase Agreements work area.

  3. Use the default buyer from the Configure Procurement Business Function task. Find the task in the Setup and Maintenance work area, Procurement offering, Procurement Foundation functional area.

If the Use Same Buyer for all Lines in a Requisition profile option is enabled in the application, the buyer assigned to the first line will also be assigned to all other lines.

Creating Buyer Assignment Rules: Points to Consider

As a procurement manager, you can define buyer assignment rules that direct automatic routing of requisition lines to the most appropriate buyer for processing. The application uses the rules to assign buyers to requisition lines, when requisitions you create online or import are submitted for approval.

Define buyer assignment rules using the Manage Buyer Assignment Rules task. Find the task in the Setup and Maintenance work area, in the Procurement offering, Purchasing Foundation functional area.

These are the choices to consider when creating a buyer assignment rule:

  • Rule Sequence

  • Requisitioning BU

  • Commodity

  • Deliver-to Organization

  • Project

  • Supplier

  • Noncatalog Request

  • Exceeds Line Amount

  • Procurement BU

  • Buyer

Note: A value for rule sequence, procurement business unit, and buyer are required to create a rule. In addition, either a requisitioning business unit, or a commodity, or both are required.

Rule Sequence

Specify a number to control the sequence of evaluation of the rules.

  • Rules are evaluated in ascending order of the sequence number.

  • The sequence numbers have to be rational numbers (supporting decimals).

  • No two rules can have the same sequence number.

Commodity

Enter a Commodity that can be either a category or a group of categories. Define commodity-based rules at higher levels to avoid creating rules for each category.

Deliver-to Organization

Identify the deliver-to organization of the requisition line. This determines the item definition used to derive the default buyer.

Project

Specify the project identification, which the application matches to the requisition distribution. A requisition line is considered a match only if all the distributions have the same project.

Supplier

Enter the supplier, which the application matches to the requisition line.

Noncatalog Request

Indicate whether or not the requisition line is for a noncatalog request.

Upload Buyer Assignment Rules: Procedure

As a procurement manager, you can use spreadsheet processing to manage buyer assignment rules. Use this method when there is a large amount of data to manipulate.

Use the Manage Buyer Assignment Rules task. Find the task in the Setup and Maintenance work area, in the Procurement offering, Purchasing Foundation functional area.

Using Spreadsheet Processing

To use the spreadsheet, follow these steps.

  1. On the Manage Buyer Assignment Rules page, use the Manage in Spreadsheet button to save the spreadsheet file to your local computer. You can also use the Manage in Spreadsheet option from the Actions drop-down list.

  2. Once you save the file locally, open and complete the spreadsheet. The spreadsheet includes a worksheet containing instructions and a worksheet for creating and maintaining rules.

  3. After completing your entries in the spreadsheet, click Upload to move your changes to the application.

  4. The application validates your entries.

    1. View the overall outcome for your upload in the Status column of the spreadsheet.

    2. View highlighted spreadsheet cells for any errors.

  5. If there are errors, correct the errors in the spreadsheet and upload again.

FAQs for Define Common Purchasing Configuration

What's a document style?

Purchase order document styles allow organizations to control the look and feel of the application to match the usage of the purchasing document. Through reusable document styles, organizations can turn on or off various document attributes, thereby simplifying the user interface to fit their business needs.

What's a buyer assignment rule set?

As a procurement manager, you can use rule sets to manage a large number of assignment rules. You can group rules that share a common use under a name to filter search results.

Use the Manage Buyer Assignment Rule Sets Lookup task. Find the task in the Setup and Maintenance work area, Procurement offering, Purchasing Foundation functional area.

Define Procurement Configuration Options

Price Break Type: Critical Choices

You can select the default price break type for blanket purchase agreements from the Configure Procurement Business Function page. You can find the page in the Setup and Maintenance work area, in the Procurement offering, Procurement Foundation functional offering, Configure Procurement Business Function task.

Cumulative Pricing

Select Cumulative Pricing if you want to choose the price break by adding the current release shipment quantity to the total quantity already released against the purchase agreement line.

Note: Cumulative Pricing cannot be used with global agreements.

Non-Cumulative Pricing

Select Non-Cumulative Pricing if you want to choose the price break by using the individual release shipment quantity of the agreement line.

Choosing an Inventory Organization: Explained

You can create purchasing documents to replenish goods stocked in an organization's inventory. You can associate each of your procurement business units with one inventory item master organization from the Configure Procurement Business Function page. You can find the page in the Setup and Maintenance work area, Procurement Offering, Procurement Foundation functional area.

Choosing an Inventory Organization

When you associate your procurement business unit (BU) with an inventory organization, items you define in this BU become available throughout procurement. Do not change the Inventory Organization after you have already assigned one to a procurement BU.

Allow Retroactive Pricing: Critical Choices

Retroactive price updates automatically update existing purchase orders retroactively with price break quantities from the parent blanket agreement.

Open Orders Only

Choose this option to allow retroactive price updates to open orders with no receiving or invoicing activity.

All Orders

Choose this option to allow retroactive price updates to all orders irrespective of whether they have been received or invoiced.

Receipt Close Point: Explained

Used to select the close point, which is when the shipment is closed for receiving: You can override this option for specific items and orders.

Selecting the close point gives you more precise control over when the shipment is accounted for.

Note: The receipt close tolerance percentage must be set in combination with this setting.

Accepted

Ordered goods have passed inspection and are ready for use.

Delivered

Ordered goods have been delivered and are ready for use.

Received

Ordered goods have been received and are ready for use.

Match Approval Level: Critical Choices

A transaction status match combination after which the document may be considered approved for payment.

Note: The invoice match option in the purchase order schedule and the match approval level described here are independent options. The invoice match option determines whether Payables performs invoice matching to the purchase order or the receipt.

Two-Way

Purchase order and invoice quantities must match within tolerance before the corresponding invoice can be paid.

Three-Way

Purchase order, receipt, and invoice quantities must match within tolerance before the corresponding invoice can be paid.

Four-Way

Purchase order, receipt, accepted quantities from inspection, and invoice quantities must match within tolerance before the corresponding invoice can be paid.

Group Requisitions: Critical Choices

During automatic creation of purchase orders from requisitions use the following options to control how requisition lines are combined on order lines in the new document.

Group Requisitions

By default the requisitions are converted into purchase order lines individually. This option allows consolidation of requisition lines from across multiple requisitions into a single purchase order.

Select this check box to group requisitions into a single purchase order. The application will try to group all the requisitions which share the same:

  • Requisitioning BU and Sold-to BU

  • Document style

  • Supplier and site

  • Currency and conversion rates

  • Buyer

Group Requisition Lines

By default the requisition lines are combined into individual lines based on document type. This option determines whether each requisition line being fulfilled in the order will have its own order line or can be combined with other requisition lines. Select this check box to group requisition lines into the same purchase order line. The application will try to group requisition lines which share the same:

  • Line type

  • Item, item revision, item description, supplier item number, supplier configuration ID

  • Category

  • UOM

  • Source agreement and source agreement line

  • Requested delivery date (used optionally if the Use requested delivery date check box is selected)

  • Ship-to organization and location (used optionally if the Use ship-to organization and location is selected)

For all requisition lines being grouped into the same purchase order line, the application will further group these lines into schedules if they share the same:

  • Requested delivery date, ship-to location and ship-to organization

  • Destination type

Standard Purchasing Terms and Conditions: Explained

Standard terms and conditions outline any legal or functional constraints under which the purchase order or purchase agreement will be conducted. These terms and conditions apply to any orders executed by the procurement business unit and can be made available in all installed languages. Use the Define Purchasing Terms and Conditions page to enter standard terms and conditions for purchasing documents.

You can find the page from the Setup and Maintenance work area, in the Procurement offering, Procurement Foundation functional area, Configure Procurement Business Function task. On the Configure Procurement Business Function page, in the General section, click the Terms and Conditions button.

Standard terms and conditions are included with each purchasing document sent to the supplier.

Terms

Purchasing terms commonly indicate the buying organization's rules and expectations as related to pricing and payment.

Conditions

Purchasing conditions typically describe the buying organization's rules related to but not limited to delivery, acceptance of delivery, cancellations, additions to the approved order, and general behavior of the supplier during the course of the transaction.

Languages

Indicate that this set of terms or conditions are not to be made available in all installed languages by selecting the check box: Disable terms and conditions for all languages.

FAQs for Configure Procurement Business Function

What's a receipt close tolerance percent?

This setting is used in combination with the closing point to close a schedule for receiving. It is the allowable difference (expressed as a percentage) between the quantity stated on the order schedule and the actual quantity received. Quantities can vary up to this difference without preventing an automatic closed for receipt status. You can override this option for specific items and orders.

Note: You must also set the receiving close point.

For example, with a receipt close tolerance percent of 99 with a quantity ordered of 100 and a closing point of receipt the schedule would automatically be closed for receiving when 1 of the 100 are received.

What's a contract terms layout?

For purchasing documents, you can select a contract terms layout for the document type. These templates determine what information is displayed along with providing the headers, footers, text style, and pagination of the printed document. You can configure your own layout in RTF format and upload it to Oracle BI Publisher, or select one already provided.

Configure Requisitioning Business Function

Configure Requisitioning Business Function: Explained

The Procurement Application Administrator has access to the Configure Requisitioning Business Function page for setting up a business unit that has a requisitioning business function associated with it. The attributes specified here are used to default values and behavior of the application when users are creating requisitions and purchase orders for the requisitioning BU.

You can find the page in the Setup and Maintenance work area, in the Procurement offering, Procurement Foundation functional area, Configure Requisitioning Business Function task.

Requisitioning Section

Default Deliver-To Organization

The default organization is used as the deliver-to organization for a requisition line if it is a global location. This organization is used to derive the list of item master items that are accessible to the user when creating a requisition for the requisitioning BU.

Line Type

The Line Type is the value specified to be defaulted on requisition lines created for the requisitioning BU. Line Type can be modified.

One-Time Location

The One-Time Location is the location code to be defaulted as the deliver-to location for the requisition line when the requester specifies a one-time delivery address on a requisition. The location specified must be a global location that is enabled for the requisitioning BU.

Reapproval required for changes made during an active approval process

Reapproval required for changes made during an active approval process is applicable when allowing approvers to modify a requisition when it is routed for approval. It controls whether the requisition must be sent back for reapproval when the approver submits the modified requisition.

Group Requisition Import By

The Import Requisition process can be used to import requisitions from other Oracle or non-Oracle applications. On import, requisition lines are grouped first by requisition header number, then by the provided Group Code, then by the value set in the Group-by input parameter (None, Buyer, Category, Item, Location, or Supplier). The specified attribute is used as the default value for Group-by. All remaining requisition lines that have not yet been assigned a requisition number will be grouped together under the same requisition.

Allow One-Time Address

The One-Time Address is the location to be defaulted as the deliver-to location for the requisition line when the requester specifies a one-time delivery address on a requisition. The location specified must be a global location that is enabled for the requisitioning BU.

One-Time Location

The One-Time Location is the location code to be defaulted as the deliver-to location for the requisition line when the requester specifies a one-time delivery address on a requisition. The location specified must be a global location that is enabled for the requisitioning BU.

Create Orders Immediately after Requisition Import

Create orders immediately after requisition import controls whether the Generate Orders program will run immediately after the requisition import process is complete.

Enable Approval Override

Enable approval requirement for lines that are modified by the buyer.

Enable Supply Availability Details for Internal Transfers

When creating a requisition that includes internal transfer items, the source of supply can be modified.

When this is selected, availability information from each supply source for the transfer item is provided in the Select Supply Source dialog, accessed when Select Source is clicked for a transfer requisition line.

Context Values for Requisition Descriptive Flex-fields

You can define additional attributes of a requisition at the header, line, and distribution level using descriptive flex-fields. Specifying the context value pulls in the associated descriptive flex-fields when the user enters the requisition.

Purchasing Section

Default Procurement BU

A requisitioning BU can be served by multiple procurement business units. If a procurement BU cannot be determined based on information on the requisition line, the Default Procurement BU is used to process all requisition lines.

Price Change Tolerance

The Price Change Tolerance is applicable when there is a price change on the purchase order line associated with a requisition line. If the value is null, no checks will be performed. If the value is a valid numeric value, then any changes made to the price on the purchase order line must be within the tolerance percentage value, or the purchase order cannot be submitted. The tolerance can be specified using the tolerance percentage or tolerance amount. The more restricting of the two tolerances will take precedence if both are specified.

Ship-to Location

When the purchase order cannot derive a ship-to location, the specified Ship-To on the Requisitioning BU is defaulted.

Cancel Backing Requisitions

Cancel Backing Requisitions controls whether a backing requisition should be canceled when there is purchase order cancellation.

Options are:

  • Always: When canceling the purchase order, Oracle Fusion Purchasing also cancels the requisition.

  • Never: When canceling the purchase order, Oracle Fusion Purchasing does not cancel the requisition, therefore it is available for inclusion on another purchase order.

  • Optional: When canceling the purchase order, the buyer is given the option to cancel the requisition.

Multiple Legal Entities on Order

Control if a purchase order can contain ship-to organizations belonging to different legal entities.

Allow Requisition-To-Agreement UOM Conversion

If a requisition does not have an agreement specified, Allow requester-to-agreement UOM conversion is used to specify whether Requisition UOMs can be converted to Agreement UOMs during agreement sourcing. Checking this box indicates that agreements that meet the sourcing criteria, but have Agreement Line UOMs different from Requisition Line UOMs, can be considered during agreement sourcing. If the box is left unchecked, such agreements will not be considered.

Define Procurement Agents

Procurement Agent Security: Explained

Use the Manage Procurement Agents task to create and maintain a procurement agent's access to procurement functionality for a business unit. You can find the task in the Purchase Agreements and Purchase Orders work areas.

You can implement document security for individual document types such as purchase orders, purchase agreements, and requisitions. You can also control a procurement agent's access to manage activities for suppliers, negotiations, catalog content, and business intelligence spend data.

Key aspects for managing procurement agents are:

  • Understanding what a procurement agent is.

  • Implementing document security.

  • Navigating to the Manage Procurement Agents task.

What is a Procurement Agent?

Procurement agents are typically users with procurement roles such as:

  • Buyer

  • Catalog Administrator

  • Category Manager

  • Procurement Contract Administrator

  • Procurement Manager

  • Supplier Administrator

  • Supplier Manager

  • Supplier Qualification

They have procurement job responsibilities in the buying organization, such as creating purchase agreements, purchase orders, and related procurement functions. You must set up these users as procurement agents for them to manage procurement documents and perform other procurement actions.

Implement Document Security

The key elements for setting up procurement agent document security are:

  • Assigning the agent to a procurement business unit.

  • Enabling the agent's access to procurement actions.

  • Defining the agent's access levels to other agents' documents.

Locate the Manage Procurement Agents Task

Depending on your role and permissions, you can use the Manage Procurement Agents task in the following work areas:

  • Setup and Maintenance work area, Procurement offering, Procurement Foundation functional area.

  • Purchase Agreements and Purchase Orders work areas.

Create Procurement Agent: Critical Choices

Use the Manage Procurement Agents page to create or edit a procurement agent. With this task you can define an agent's access to procurement functionality within a procurement business unit.

You can find the page from the following work areas:

  • Setup and Maintenance work area, in the Procurement Offering, Procurement Foundation functional area, Manage Procurement Agents task.

  • Purchasing work area, Manage Procurement Agents task.

The following predefined procurement roles are controlled by procurement agent access configuration:

  • Buyer

  • Catalog Administrator

  • Category Manager

  • Procurement Contracts Administrator

  • Procurement Manager

  • Supplier Administrator

  • Supplier Manager

  • Supplier Qualification

Procurement BU

Assign the agent to one or more procurement business units (BU).

Action

Enable the agent with access to one or more procurement actions for each procurement business unit.

  • Manage Requisitions: Enable access to purchase requisitions.

  • Manage Purchase Orders: Enable access to purchase orders.

  • Manage Purchase Agreements: Enable access to blanket purchase agreements and contract agreements.

  • Manage Negotiations: Enable access to Sourcing negotiations, if implemented by your organization.

  • Manage Sourcing Programs: Enable access to track and manage sourcing programs.

  • Manage Catalog Content: Enable access to catalog content. This includes local catalogs, punchout catalogs, content zones, smart forms, information templates, and collaborative authoring.

  • Manage Suppliers: Enable access to create and update supplier information.

  • Manage Supplier Qualifications: Enable access to initiatives, qualifications, and assessments, if Supplier Qualification is implemented by your organization.

  • Manage Approved Supplier List Entries: Enable access to create and update approved supplier lists.

  • Analyze Spend: Used by the business intelligence functionality to enable access to view invoice spend information.

Access to Other Agents' Documents

Assign an access level to documents owned by other procurement agents for each procurement business unit.

Note: An agent can perform all actions on their own documents as long as they have procurement BU access.
  • None: The agent has no access to documents owned by other agents.

  • View: Permits the agent to search and view other agents' documents.

  • Modify: Permits the agent to view, modify, delete, and withdraw other agents' documents.

  • Full: Permits the agent full control of other agents' documents. This includes the view, modify, delete, withdraw, freeze, hold, close, cancel, and finally close actions.

Buyer Managed Transportation Setup

Buyer Managed Transportation Setup in Procurement: Explained

Before you can process procurement transactions using buyer managed transportation, you must enable the feature. You can also configure business units and supplier sites to support default actions, and transit times to support calculation of anticipated arrival dates.

Enable the Feature

To activate buyer managed transportation for use in procurement transactions, select the buyer managed transportation feature in the Procurement offering.

  1. In the Setup and Maintenance work area, select the Procurement offering.

  2. On the Setup: Procurement page, click the Change Feature Opt-in link.

  3. On the Opt-in: Procurement page, in the Features column for the Procurement offering, click the Edit icon.

  4. On the Edit Features: Procurement page, select the Buyer Managed Transportation check box, and click Done.

Configure Business Units

Optionally, you can configure the buyer managed transportation setting for a business unit (BU). Selecting the setting for a BU does the following:

  • Indicates your buying organization's intent to manage transportation for purchasing transactions for the business unit.

  • Enables default action for the selection of the setting in procurement transactions for the business unit.

To enable the buyer managed transportation setting for a business unit:

  1. In the Setup and Maintenance work area, select the Procurement offering.

  2. On the Setup: Procurement page, click the Procurement Foundation functional area, then click the Configure Procurement Business Function task.

  3. On the Specify Procurement BU dialog, select the Procurement BU, and click OK.

  4. On the Configure Procurement Business Function page's Main tab, General section, select the Buyer managed transportation check box.

  5. In the Purchasing section, you have the option to select the Default promised date from requested date check box. When selected, the buyer's requested date is used to populate the promised date field, in purchasing transactions for the business unit.

  6. Click Save.

Configure Supplier Sites

Optionally, you can configure the buyer managed transportation setting for a supplier site. Selecting the setting for a site does the following:

  • Indicates your buying organization's intent to manage transportation for purchasing transactions for the site.

  • Enables default action for the selection of the setting in procurement transactions for the site.

To enable the buyer managed transportation setting for a supplier site:

  1. In the Suppliers work area, select the Manage Suppliers task.

  2. Search for and select the supplier site.

  3. On the Edit Site page, Purchasing tab, Buyer Managed Transportation drop-down list, select Yes.

  4. Click Save.

Configure Transit Times

Optionally, you can configure the transit time between two locations to enable the calculation of anticipated delivery dates. To configure transit times:

  1. In the Setup and Maintenance work area, click the Tasks tab, and click Search.

  2. On the Search page, search for and select the Manage Transit Times task.

  3. On the Manage Transit Times page, set up transit information for the origin and destination locations.

    • Origin type, location and description.

    • Destination type, location and description.

    • Shipping method.

    • Transit time in days.

  4. Click Save.

The transit information you set up is used to calculate anticipated delivery dates on purchasing transactions, when the transportation is buyer managed. The anticipated delivery date is calculated as the requested or promised ship date plus the transit time in days.