Implementing Oracle Services Procurement

This chapter covers the following topics:

• Licenses for Oracle Services Procurement
• Profile Options Used in Oracle Services Procurement
• Concurrent Programs Used in Oracle Services Procurement Business Flows
• Implementation Considerations in Oracle Services Procurement
• Overview of Implementing Oracle Services Procurement
• Overview of Setting Up Steps to Process the Procurement of Complex Work
• Setting Up Steps in Oracle Purchasing to Process the Procurement of Complex Work
• Setting Up Steps in Oracle Approvals Management to Process the Procurement of Complex Work
• Setting Up Steps in Oracle E-Business Tax to Process the Procurement of Complex Work
• Setting Up Steps in Oracle Procurement Contracts to Process the Procurement of Complex Work
• Overview of Setting Up Steps to Process the Procurement of Contingent Workers
• Setting Up Steps in Oracle iProcurement to Process the Procurement of Contingent Workers
• Setting Up Steps in Oracle Purchasing to Process the Procurement of Contingent Workers
• Setting Up Steps in Oracle Human Resources to Process the Procurement of Contingent Workers
• Setting Up Steps in Oracle Time and Labor to Process the Procurement of Contingent Workers
• Setting Up Steps in Oracle Internet Expenses to Process the Procurement of Contingent Workers
• Setting Up Steps in Oracle Projects to Process the Procurement of Contingent Workers

Licenses for Oracle Services Procurement

Prerequisite Licenses

To use Oracle Services Procurement, you must license and implement Oracle Purchasing.

Oracle Service Procurement Integration with Other Oracle E-Business Suite of Products

Oracle Services Procurement integrates and interacts with the other Oracle E-Business Suite products.

The following tables provide information on the features that you can use in the other Oracle Applications, if you have licensed and implemented these products:

Processing the Procurement of Complex Work

Feature	Application Required
Requisitions for Services	Oracle iProcurement
Vendor Questionnaires, Request for Quotation (RFQ), RFQ Analysis, Awards, Compare Quotes	Oracle Sourcing
Complex Work Contracts	Oracle Procurement Contracts
Quotes, Work Confirmations	Oracle iSupplier Portal
Procurement Services Invoice, Pay on Receipt, Retainage Release	Oracle Accounts Payable
Track Project Progress, Deliverables, Projections and Actuals, Deduction and Back Charge Processing, Change Management, Change Requests, Change Order, Reporting Analytics	Oracle Projects
Tax Structure (Tax Regimes, Tax, Tax Status, Tax Jurisdictions, Tax Recovery rates, Tax rates, Tax Rules)	Oracle E-Business Tax

Processing the Procurement of Contingent Workers

Feature	Application Required
Contingent Worker Requisitions	Oracle iProcurement
Contingent Worker HR Details	Oracle Human Resources or Oracle Self-Service
Contingent Worker Timecard and Labor Data	Oracle Time and Labor
Process for Sourcing, Procuring And Managing Contingent Worker Including Viewing Details of Timecard	Oracle iSupplier Portal
Import Contingent Worker Timecards with Purchase Order Integration	Oracle Projects
Contingent Workers as Scheduled Resource Allowing Search And Assign Resource to Active Projects	Project Resource Management
Contingent Worker Invoice	Oracle Accounts Payable
Contingent Worker Expense Reports	Oracle iExpenses

Profile Options Used in Oracle Services Procurement

A number of profile options govern the behavior of Oracle Services Procurement. During implementation, set a value for each profile option to specify how Oracle Services Procurement controls access to and processes data.

Profile options are grouped into the following categories:

• Prerequisite Profile Option

• Profile Options to Process the Procurement of Complex Work

• Profile Options to Process the Procurement of Contingent Workers

The following tables list the profile options with a reference to their Oracle Application, a brief description, and the business flow.

Prerequisite Profile Option

Profile Option	Oracle Application	Description
PO: Enable Services Procurement	Oracle Purchasing	The value Yes indicates that Oracle Services Procurement is licensed and installed. Setting this profile value to Yes will enable service line types in Oracle Sourcing and Oracle Purchasing. When the profile option is enabled, buyers can create lines with the following additional line types: Fixed Price Services Fixed Price Temp Labor Rate based Temp Labor

Profile Options to Process the Procurement of Complex Work

Oracle Services Procurement uses the following profile option in the procurement of complex work business flow.

Profile Option	Oracle Application	Description
POR : Amount Based Services Line Type	Oracle iProcurement	Determines the line type for amount-based non-catalog requests. An amount-based request is expressed in monetary terms - for example, 500 USD worth of service. The value selected should be distinct from the values selected for POR: Goods Line Type and POR: Rate Based Services Line Type. You can select only line types with a Purchase Basis of Services and a Value Basis of Amount for this profile option. If Oracle Services Procurement is licensed and implemented, then you can select a Value Basis of Fixed Price or Amount. For more information, refer to the Oracle iProcurement Implementation and Administration Guide.
POR: Default Currency Conversion Rate Type	Oracle iProcurement	Specifies the default exchange rate type. This rate applies when: Creating non-catalog requests. Converting an uploaded item's transactional price into a requester's functional price. Converting a punchout or transparent punchout item's transactional price into the functional price. Exchange rates cannot be found during contractor assignment. If you are converting prices of punchout or transparent punchout items, you must set this profile option to either Corporate or Spot (not User). Otherwise, the requester receives an error message during checkout that no exchange rate exists and cannot check out the item. For more information, refer to the Oracle iProcurement Implementation and Administration Guide.

Profile Options to Process the Procurement of Contingent Workers

Profile Option	Oracle Application	Description
PO: UOM class for Temp Labor Services	Oracle Purchasing	Controls the rate based temp labor line type. For a rate based temp labor line type, entry of unit of measure (UOM) is restricted to those in this UOM class. For more information, refer to the Oracle Purchasing User's Guide.
POR: Rate Based Services Line Type	Oracle iProcurement	Specifies the line type for rate-based non-catalog requests. A rate-based request is expressed as a monetary charge for each time period. The value selected must be distinct from the values selected for POR: Goods Line Type and POR: Amount Based Services Line Type. Select only line types with a Purchase Basis of Goods and a Value Basis of Quantity for this profile option. In Oracle iProcurement, requisition creation, the Services billed by quantity item type corresponds to the line type selected in the POR: Rate Based Services Line Type profile option. For more information, refer to the Oracle iProcurement Implementation and Administration Guide.
PO: Contractor Assignment Completion Warning Delay	Oracle Purchasing	Yes indicates that the contractor assignment completion notification is sent to the requester when the assignment is complete. For more information, refer to the Oracle Purchasing User's Guide.
PO: Amount Billed Threshold Percentage	Oracle Purchasing	Indicates the amount above which the amount billed exceeded threshold notification will be sent to the requester. For more information, refer to the Oracle Purchasing User's Guide.
POR: Contractor Expense Line Type	Oracle iProcurement	Indicates the line type that should be used for expense lines on contractor requests. For more information, refer to the Oracle iProcurement Implementation and Administration Guide.
POR: Reapproval after Contractor Assignment	Oracle iProcurement	Determines whether reapproval of the requisition is required after contractor assignment. Select Always to always require approval. Conditionally Required means that reapproval is required only if a change has been made that triggers reapproval – for example, at least one line amount has changed, or the requester modified the unit price, quantity, unit of measure, account, distribution, or project information on the requisition during the checkout that follows contractor assignment. If the new line amount is below the requester's approval limit, then only the requester's reapproval (no additional approval) is required. For more information, refer to the Oracle iProcurement Implementation and Administration Guide.
ICX: Days Needed By	Oracle iSupplier Portal	The Start Date on the contractor request defaults based on this profile option, which is also part of the requester's iProcurement preferences.
HR: Expand Role of Contingent Worker	Oracle Human Resources	Determines whether you can select contingent workers to perform many of the roles fulfilled by employees. For example, if you set this option to Yes, you can select a contingent worker to be a supervisor in the Assignment window and an authorizer in the Absence window. For more information, refer to the Oracle HRMS Configuring, Reporting, and System Administration Guide.
HR: CWK in Head Count Reports	Oracle Human Resources	Determines whether contingent workers are included in head-count reports. For more information, refer to the Oracle HRMS Configuring, Reporting, and System Administration Guide.
HR: Use Global Contingent Worker Numbering	Oracle Human Resources	Enables the global sequence for contingent-worker-number generation. This sequence is shared among all business groups. To set this profile option, you run the process "Change automatic person number generation to global sequencing". You cannot set this option in the System Profile Values window. For more information, refer to the Oracle HRMS Configuring, Reporting, and System Administration Guide.
HR: Contingent Worker Manager Actions Menu	Oracle Human Resources	Controls which Manager Actions menu SSHR displays for managers who are also contingent workers. If you create a custom Manager Actions menu for contingent workers, you must change this profile option to point to your custom menu. For more information, refer to the Oracle HRMS Configuring, Reporting, and System Administration Guide.
HR: Contingent Worker Personal Actions Menu	Oracle Human Resources	Controls which Personal Actions menu SSHR displays for users who are also contingent workers. If you create a custom Personal Actions menu for contingent workers, you must change this profile option to point to your custom menu. For more information, refer to the Oracle SSHR Deploy Self-Service Capability Guide.
MO: Operating Unit	Common Applications	Operating Unit value comes from this profile option and controls contingent workers' access to purchase orders.
HR: Business Group	Oracle Human Resources	Determines the business group linked to a responsibility. For more information, refer to the Oracle HRMS Configuring, Reporting, and System Administration Guide.
HR: Security Profile	Oracle Human Resources	Restricts access to the organization, positions and payrolls defined in the security profile. For more information, refer to the Oracle HRMS Configuring, Reporting, and System Administration Guide.
PA: Allow Time Entry of Negative Hours	Oracle Projects	Indicates whether you can enter negative hours on timecards in Oracle Time & Labor. For more information, refer to the Oracle Projects Implementation Guide.
PA: AutoApprove Timesheets	Oracle Projects	Indicates whether to automatically approve timecards submitted in Oracle Time and Labor. For more information, refer to the Oracle Projects Implementation Guide.
PA: Enable Business Messages on Time Entry	Oracle Projects	Indicates whether Oracle Time and Labor displays a business message. For more information, refer to the Oracle Projects Implementation Guide.
PA: Override Approver	Oracle Projects	Indicates whether you can enter an overriding approver for timecards in Oracle Time and Labor. For more information, refer to the Oracle Projects Implementation Guide.

Concurrent Programs Used in Oracle Services Procurement Business Flows

This topic provides information on the concurrent programs that you run when processing the following business flows in Oracle Services Procurement:

• Processing the procurement of complex work

• Processing the procurement of contingent workers

The following table lists the concurrent programs with a brief description and a reference to their Oracle Application.

Concurrent Program	Oracle Application	Description	Business Flow
PRC: Interface Supplier Costs	Oracle Projects	Supports the implementation option 'Import contingent workers time cards with PO integration'. Retrieves project-related supplier costs and interfaces them from Oracle Purchasing and Oracle Payables to Oracle Projects. For more information, refer to the Oracle Projects Fundamentals Guide.	Contingent Worker Procurement
PRC: Distribute Labor Costs	Oracle Projects	Supports the contingent labor integration with purchase orders, If integration is set up with Oracle Purchasing, then the labor-costing program derives the rate from the purchase order line. For contingent worker timecards with Oracle Purchasing integration, when you run the process PRC: Distribute Labor Costs, Oracle Projects uses rates from the related purchase order to calculate the costs. For more information, refer to Oracle Projects Fundamentals and Oracle Project Costing User Guide.	Contingent Worker Procurement
PRC: Distribute Total Burdened Costs	Oracle Projects	Creates the total burdened cost distribution lines for all transactions charged to burdened projects, even if the transaction is not burdened, to account for the total project costs in the cost WIP account. For more information, refer to the Oracle Project Costing User Guide.	Complex Work Procurement
PRC: Submit Interface Streamline Processes	Oracle Projects	Streamline processes submit and monitor a series of processes that must be run sequentially to complete a function. Refer to the topic Submitting Streamline Processes, Oracle Projects Fundamentals.	Complex Work Procurement Contingent Worker Procurement
PRC: Interface Expense Reports to Payables	Oracle Projects	Submits the Oracle Projects Interface Expense Reports to Payables process to transfer expense reports to the Payables Expense Report Interface tables. For more information refer to Oracle Projects Fundamentals.	Complex Work Procurement
PRC: Transaction Import	Oracle Projects	Uses predefined transaction sources to import transactions from other Oracle Applications such as Oracle Inventory, Oracle Project Manufacturing, Oracle Time and Labor, and Oracle Labor Distribution. For more information, refer to the Oracle Projects Implementation Guide.	Contingent Worker Procurement
PRC: Update Project Summary Amounts for a Single Project	Oracle Projects	Updates the project summary amounts with new cost, commitment, and revenue transactions and any new baselined budget versions. You can run this process as many times as you want. To submit the process for one project, submit the PRC: Update Project Summary Amounts for a Single Project process. For more information, see: Oracle Projects Fundamentals.	Complex Work Procurement
Retrieve Time from OTL	Oracle Purchasing	If Oracle Services Procurement is implemented and contract workers enter their time through Oracle Time and Labor, then use this process to generate receipts for the recorded time. You can complete the procure-to-pay flow by running the Pay on Receipt process. This process loads the time transactions into the Receiving Open Interface and then the Receiving Transaction Processor is automatically launched to import the receipts.	Contingent Worker Procurement

Implementation Considerations in Oracle Services Procurement

The following topic provides information on implantation considerations for the complex work and contingent worker business flow.

Implementation Considerations for the Complex Work Business Flow Available Line Types

The following table provides information on the different pay items available for various line types in a complex purchase order.

Line Type	Value Basis	Purchase Basis	Matching Basis	OSP Item	Pay Items Available
Goods	Quantity	Goods	Quantity	No	Milestone
Goods	Quantity	Goods	Quantity	Yes	Not available in Complex Orders
Amount	Amount	Services	Quantity	NA	Not available in Complex Orders
Fixed Price Services	Fixed Price	Services	Amount	NA	Milestone, Lump Sum and Rate
Fixed Price Temp Labor	Fixed Price	Temp Labor	Amount	NA	Milestone, Lump Sum and Rate
Rate based Temp Labor	Rate	Temp Labor	Amount	NA	Milestone, Lump Sum and Rate

Destination Types

The destination type is identified based on the selected document style.

The destination type for:

• Fixed price service line types can be Expense only.

• Goods line types can be Inventory and Expense.

Non-Financed Purchase Orders

For a non-financed Purchase Order document:

• The pay items need to add up to the total value of the line.

• The recoupment rate should be high enough to liquidate the advances paid.

Financed Purchase Orders

In a financed purchase order document:

• The line has its own delivery shipment.

• All the pay items are taken to be financed and billed using 'Prepayment' invoice only.

• The sum total of pay items and advances specified should be less than or equal to the total amount of the line.

• Recoupment rate should be high enough to liquidate the advances and the pay item amount.

• Accrue at Receipt is not supported for financed pay items.

• Encumbrance is not supported for financed purchase orders.

Implementation Considerations for the Contingent Worker Business Flow

Encumbrance

In Oracle Purchasing, you have the choice of encumbering a blanket purchase agreement or the requisition. For Pending contractor requests, the encumbrance is always done on the requisition. During contractor assignment, Oracle iProcurement temporarily unreserves (releases reserved) funds. The funds are re-reserved after contractor assignment is completed.

Jobs

Oracle Human Resources jobs are specific to a business group. Therefore, the job selected on the contractor request limits the deliver-to location on the requisition to those locations that belong to the preparer's business group.

Document Sourcing

If you have set up global blanket agreement or contract purchase agreement document sourcing, then Oracle iProcurement displays the source document information in the preferred supplier list on the contractor request if the following conditions are met. (Some of these conditions apply only to blanket, not contract, agreements.)

The source document's supplier and supplier site match a supplier and supplier site in the ASL for the selected job category. The start date entered on the contractor request must fall within the effective dates of the source document.

Price break information from the source document is used, based on the deliver-to location selected on the contractor request and the date the request was created. That is, if the date that the request was created is within the effective dates on the price break, then that price break is used. The line type on the source document must match the line type on the contractor request. For example, if a Type of Fixed Price Temporary Labor is selected on the contractor request, then only source document lines with this line type appear.

Note: Oracle iProcurement does not obtain new source document information if the requester changes the start date during contractor assignment or changes the requisition later using the Change button. If the currency on the global blanket agreement differs from the requester's functional currency, then Oracle iProcurement uses the exchange rate in the system to perform a currency conversion. If an exchange rate cannot be found, then Oracle iProcurement uses the exchange rate the POR: Default Currency Conversion Rate Type profile option determined.

Descriptive Flexfields

For contractor requests, descriptive flexfields do not appear in the shopping cart, even if you use Oracle Applications Framework personalization to display them.

Overview of Implementing Oracle Services Procurement

To implement Oracle Services Procurement, set the PO: Enable Services Procurement profile option to Yes.

Analyze your business requirements and complete the following steps to use Oracle Services Procurement.

• Setting Up Steps to Process the Procurement of Complex Work. See: Overview of Setting Up Steps to Process the Procurement of Complex Work

• Setting Up Steps to Process the Procurement of Contingent Workers. See: Overview of Setting Up Steps to Process the Procurement of Contingent Workers

Overview of Setting Up Steps to Process the Procurement of Complex Work

This topic provides an overview of setting up steps to process the procurement of complex work.

The following table lists the setup steps and a reference to their Oracle Application.

Step No.	Step	Application	Comments
Step 1	Set Up Document Styles	Oracle Purchasing	Required
Step 2	Define Purchasing Profile Options	Oracle Purchasing	Required
Step 3	Set Up Supplier Change Order Tolerance	Oracle Purchasing	Required
Step 4	Set Up Change Order Tolerance	Oracle Purchasing	Required
Step 5	Set Up Financial Options	Oracle Purchasing	Required
Step 6	Set Up Invoice Tolerance Template	Oracle Purchasing	Required
Step 7	Set Up Supplier Sites	Oracle Purchasing	Required
Step 8	Create Projects	Oracle Projects	Required
Step 9	Define Approval Rules	Oracle Approvals Management	Optional, configure approval rules based on business needs.
Step 10	Define Procurement Contracts	Oracle Procurement Contracts	Required
Step 11	Define the Tax Structure	Oracle E-Business Suite	Required

The following diagram shows the different setup steps in Oracle Applications for the complex work procurement process.

For instructions on how to complete each step, refer to the following topics:

• Setting Up Steps in Oracle Purchasing to Process the Procurement of Complex Work

• Setting Up Steps in Oracle Approvals Management to Process the Procurement of Complex Work

• Setting Up Steps in Oracle E-Business Tax to Process the Procurement of Complex Work

• Setting Up Steps in Oracle Procurement Contracts to Process the Procurement of Complex Work

Setting Up Steps in Oracle Purchasing to Process the Procurement of Complex Work

This topic describes the setup steps in Oracle Purchasing to process the procurement of complex work.

1. Define the Key Profile Option

   POR : Amount Based Services Line Type: You must define this profile option that determines how services are to be quantified and ordered on the contract document. To use the Complex Services processes, the value of this profile option must be set to Fixed Price Services, which means that services will be ordered as a lump sum amount.

   • Fixed Price Services: Services will be ordered as Lump Sum Amount

   • Amount Based: Services will be ordered as a quantity with unit price as 1

2. Set Up Document Styles

   Purchase order document styles allow organizations to control the look and feel of the application to match the usage of the purchasing document.

   Use the Document Styles page (Setup > Purchasing > Document Styles) to create and update purchase order styles. This page enables you to create document styles for complex work orders (Actuals and Finance).

   

   To create a document style for the complex work process:

   In the Create Document Style page:

   • Enter details such as the name, description and status.

   • Select the appropriate document types and enter the display name.

   • Specify the document controls.

   For more information on document types and document controls, refer to the Defining Document Styles topic in the Oracle Purchasing User's Guide.

   

   When Oracle Services Procurement is licensed and installed:

   • In the Commodities region, the purchase bases that apply to the complex work orders are goods and services. Note: The Temp Labor purchase basis is applicable to the procurement of contingent workers process only. If Services Procurement is implemented and you have enabled a Temp Labor basis, then select the Temp Labor check box to enable Price Differentials.

   • The Complex Payments region in the Document Styles page is enabled and available for update. The Complex Payments region enables you to set up complex work order styles.

   Define Pricing

   In the Pricing region, select the Enhance Pricing check box to enable the Pricing Transparency functionality.

   Set Controls

   Select the Deliverable Hold Control check box to initiate payment hold by deliverables under the Controls region. You can create a procurement contract deliverable that will place invoices on hold until the deliverable is submitted by the supplier and completed by the buyer. The Deliverable Hold Control option enables you to hold a payment independent of 'Pay when Paid'.

   Enable the Complex Payments Attributes

   • Check Advances if advance payments are to be allowed.

   • Check Retainage if withholding of a portion of the payment until all work under a contract is accepted is to be allowed.

   • Check Schedules if you want purchase orders using this document style to have schedules. The Schedules check box is not selected by default. If you select the Schedules check box, then the Purchase Order (in this case, the complex work order) using this document style will have schedules. When you save this document style, the Schedules check box is not updateable at a later point in time.

   • Check Progress Payments to enable partial payments during performance of the contract. If Progress Payments is enabled, at least one pay item must be selected.

     • Milestone - Enable for payments based on progress events. Enabled by default for Goods line type.

     • Rate - Enable when payment amount is pro-rated based on the percentage of work completed.

     • Lump Sum - Enable when payment amount is a fixed amount based on the percentage of work completed.

   • Initially, both check boxes (Schedules and Progress Payments) are unselected if Services Procurement is installed. You must select either Progress Payment or Schedules or both, otherwise an error message displays.

   • Enable Treat Progress Payments as Contract Financing if it applies to the style's progress payments. The check box Treat Progress Payments as Contract Financing allows every payment released for work performed on the progress payment schedule to be treated as a financing payment that are recouped from payments for deliveries on the contract.

   When the Progress Payments and Schedules check boxes are selected in the document style of the outcome document, users can create lines with or without pay items in Sourcing documents.

   • If the document style of the outcome document has Schedules and Progress Payments enabled, in the RFQ, if there are no pay items defined for those RFQ lines, then the lines are taken to be items which are to be received either at an Inventory location or at an Expense destination.

   • If the document style of the outcome document has Schedules and Progress Payments enabled, in the RFQ, if there are pay items defined, then those lines are taken to be Pay item lines and the pay items are copied on to the order document; progress of these pay items are tracked using Work Confirmations.

   If you select Advances and Retainage check boxes in the document style, then users can create standard purchase orders with advances and retainage.

   In the Complex Payments region, if you select the Advances, Retainage and Schedules check boxes and if the Progress Payments and Treat Progress Payments as Contract Financing check boxes are not selected, then you will be able to create Standard Purchase Orders with Advances and Retainage.

   However, if you select the Advances, Retainage and Schedules check boxes and if the Progress Payments and Treat Progress Payments as Contract Financing check boxes are not selected, then the document style supports the creation of Blanket Purchase Agreements as well.

   When you save the document style, you cannot update the style with Complex Payments changes (Advances, Retainage, Progress Payments, Treat Progress Payments as Contract Financing) at a later point in time.

   When the document style has Advances and Retainage enabled, then the following fields are available in the pages listed: Advance Amount, Recoupment Rate (%), Maximum Retainage Amount, Retainage Rate (%). Progress Payments Percentage is displayed when the Treat Progress Payment as Contract Financing check box is selected in the document style. The pages/documents are:

   • Create Negotiation Line

   • Review Negotiation Line

   • View Negotiation

   • Create Bid Line

   • Review Bid Line

   • View Bid

   • Analyze by Line

   • Award by Line

   • Amendment History

   • Create Template

   • PDF Document

   The following table displays the combination of various check boxes (controls) for different types of complex work orders using the Complex Payments region:

   Advances	Retainage	Schedules	Progress Payments	Treat Progress Payments as Contract Financing	Description
   Checked	Checked	Checked	Checked	Checked	This is a Financing Payments Complex Purchase Order. This order will have both Schedules and Pay Items Tab
   Checked	Checked	Checked	Checked	Unchecked	This is a Delivery Payments Complex Purchase Order. This order will have both Schedules and Pay Items Tab
   Checked	Checked	Checked	Unchecked	Unchecked	This is a Standard Purchase Order. This order will have only Schedules tab. Users can record information related to Advances and Retainage in Standard Purchase order.
   Checked	Checked	Unchecked	Checked	Unchecked	This is a Delivery Payments Complex Purchase Order. This Order will have only Pay Items Tab
   Checked	Checked	Unchecked	Checked	Checked	This is a Financing Payments Complex Purchase Order. This Order will have only Pay Items Tab
   Unchecked	Unchecked	Checked	Checked	Checked	This is a Financing Payments Complex Purchase Order. This Order will have both Schedules and Pay Items Tab. Advances or Retainage cannot be specified for the order
   Unchecked	Unchecked	Checked	Checked	Unchecked	This is a Delivery Payments Complex Purchase Order. This Order will have both Schedules and Pay Items Tab. Advances or Retainage cannot be specified for the order
   Unchecked	Unchecked	Checked	Unchecked	Unchecked	This is a Standard Purchase Order. This order will have only Schedules tab. Advances or Retainage cannot be specified for the order.
   Unchecked	Unchecked	Unchecked	Checked	Unchecked	This is a Delivery Payments Complex Purchase Order. This Order will have only Pay Items Tab. Advances or Retainage cannot be specified for the order
   Unchecked	Unchecked	Unchecked	Checked	Checked	This is a Financing Payments Complex Purchase Order. This Order will have only Pay Items Tab. Advances or Retainage cannot be specified for the order

   If Services Procurement is installed and if document styles exist, then the Schedules check box is unselected. You cannot update the Schedules check box for existing document styles.

3. Set Up Supplier Change Order Tolerance

   Auto-Approval Tolerances are specified for Supplier initiated Change Requests on the Progress Payment Schedule. Buyers can specify a tolerance based on a percentage or dollar amount of pay item quantity and pay item amount. If the requested change falls within the limits defined by this band, it is automatically approved and the contract is updated.

   

   Use the Supplier Change Order page (Setup : Tolerances and Routings ) to define tolerances and routing for buyer auto-acceptance. Oracle iSupplier Portal uses these tolerances.

4. Set Up Change Order Tolerance

   Auto-approval tolerances are specified for Buyer initiated changes on the Progress Payment Schedule. A tolerance is specified based on a percentage of pay item price, quantity and amount. If the requested change falls within the limits defined by this band, it is automatically approved and the contract is updated.

   Specify auto approval tolerance for pay item changes:

   • Pay Item Price

   • Pay Item Quantity

   • Pay Item Amount

   

   Use the Change Order page (Setup : Tolerances and Routings) to define tolerances for auto-approval of agreements, orders, and releases. Oracle Purchasing uses these tolerances.

5. Set Up Financial Options

   Set the Retainage Account for the Operating Unit in the Financial Options page (Setup: Organizations > Financial Options).

   

   Define one retainage account for the Operating Unit to account for funds withheld from suppliers doing business with the organization.

6. Set Up Invoice Tolerance Template

   The tolerance between Amount being invoiced and the amount planned on the Services Procurement contract or the work to date represented by the approved Work confirmations is defined in the Invoice Tolerance Template window. The variance is defined as both percentage–based and amount–based tolerances.

   The tolerance templates are defined for goods or services and the most appropriate templates will be assigned to the supplier sites. This allows the users to manage tolerances values centrally yet assign the policies at the trading partner location.

   

   Using an appropriate Payables responsibility, navigate to Setup: Invoice to open the Invoice Tolerance Template window.

7. Set Up Supplier Sites

   This setup task is required to record information about individuals and companies from whom the customer purchases goods and services. Tax registrations and profiles are defined for the supplier. Additionally, the buying Organization can specify Payables accounting defaults, the Invoice Match Option that will default to the purchase order, Invoice Tolerance Templates for Goods and Services, and a unique Retainage Rate for each Supplier Site.

   Users may maintain the retainage rate based on past performance and the contractor's history. So when a contract is created with this supplier site, the retainage rate defined here will default onto the contract.

   Navigate to the Buyer Work Center > Suppliers tab to add information about suppliers.

   

   

   

Setting Up Steps in Oracle Approvals Management to Process the Procurement of Complex Work

Oracle Approvals Management is a common module which provides users the ability to configure rules which determine the approvers within the enterprise for business transactions or activities.

• The Work Confirmation transaction type allows rule configuration for determining the most appropriate person to evaluate, certify and approve the work confirmation. This could be a field engineer, a project manager or even an architect.

• The Payables Holds Resolution transaction type allows rule configuration for determining the most appropriate person to research, negotiate, and resolve invoice tolerance holds.

• The Payables Invoice Approval transaction type allows rule configuration to support line level and document level approvals plus optional rules which allows users to forgo invoice approval if the invoice is matched to a purchase order.

You can use the delivered approval rules and transaction types or create your rules and transaction types to suit your business requirements. For more information on approval management, see: Oracle Approvals Management Implementation Guide.

Setting Up Steps in Oracle E-Business Tax to Process the Procurement of Complex Work

This topic describes the setup steps in Oracle E-Business Tax to process the procurement of complex work.

Oracle E-Business Tax provides a single point solution for managing your transaction-based tax requirements. E-Business Tax delivers tax services to all E-Business Suite business flows through one application interface. As a global system architecture, E-Business Tax is configurable and scalable for adding and maintaining country-specific tax content.

Use the appropriate Tax Administrator responsibility, Tax Configuration function to set up the following to process complex work orders:

• Tax regimes

• Taxes

• Tax statuses

• Tax jurisdictions

• Tax recovery rates

• Tax rates

• Tax rules

For more information about the setup steps in this section, refer to the Oracle E-Business Tax Implementation Guide And Oracle E-Business Tax User Guide.

1. Set Up Tax Regimes

   Tax regime is the system of regulations for the determination and administration of one or more taxes. Tax regime definition is used to identify the taxes that need to be applied on the purchase order document.

   

2. Set Up Tax

   A Tax is a distinct charge imposed by a government through a fiscal or tax authority. Every tax in Oracle E-Business Tax is defined under a tax regime.

   

3. Set Up Tax Status

   A Tax Status is the taxable nature of a product in the context of a transaction and a specific tax on the transaction. Tax statuses are defined to group one or more tax rates that are of the same or similar nature. Every tax status in Oracle E-Business Tax is defined under a tax and contains one or more tax rates.

   

4. Set Up Tax Jurisdictions

   The incidence of a tax on a specific geographic area is called a Tax Jurisdiction. A tax jurisdiction is limited by a geographical boundary that encloses a contiguous political or administrative area, most commonly the borders of a country.

   

5. Set Up Tax Recovery Rates

   A recoverable tax is a tax that allows full or partial recovery of taxes paid on purchases, either as a recoverable payment or as an offset against taxes owed.

   

6. Set Up Tax Rates

   A Tax Rate is the rate specified for a tax status. A tax status can have one or several tax rates. In addition, special tax rates may apply to a specific tax jurisdiction.

   

7. Set Up Tax Rules

   In Oracle E-Business Tax, a tax rule is a set of conditions that is used to determine the tax for a specific transaction.

   

Setting Up Steps in Oracle Procurement Contracts to Process the Procurement of Complex Work

If Oracle Procurement Contracts is installed and licensed, then you can create contract terms and apply them to sourcing negotiations . You can use contract terms to specify legal and other requirements for your negotiations.

Use the Contracts Terms Library Administrator responsibility to create and maintain clauses and contract templates in the Contract Terms Library. Use the Manage Contract Terms responsibility to create and maintain contract terms on negotiation documents.

Overview of Setting Up Steps to Process the Procurement of Contingent Workers

This topic provides an overview of each step you need to complete to set up steps to process the procurement of contingent workers.

The following table lists the setup steps and a reference to their Oracle Application.

Step No.	Step	Application	Comments
Step 1	Set Up Line Types	Oracle Purchasing	Required
Step 2	Create Jobs	Oracle Human Resources	Required
Step 3	Create Projects	Oracle Projects	To process project-based timecard entries
Step 4	Create Purchasing Categories and Assign to Category Set	Oracle Purchasing	Required
Step 5	Associate Jobs to Purchasing Categories	Oracle Purchasing	Required
Step 6	Enable/Disable Price Differential Lookup Codes	Oracle Purchasing	Required
Step 7	Create Suppliers	Oracle Purchasing	Required
Step 8	Define Purchasing Contingent Worker Profile Options	Oracle Purchasing	Required
Step 9	Create Information Templates	Oracle iProcurement	Optional
Step 10	Create Service Templates Using Smart Forms	Oracle iProcurement	Optional
Step 11	Create Category Descriptors to Use the Rate Card Feature	Oracle iProcurement Oracle Purchasing	Optional
Step 12	Create Contingent Workers	Oracle Human Resources	Required
Step 13	Define Users for Contingent Workers	Common Applications	Required
Step 14	Set Up Oracle HR Contingent Worker Profile Options	Oracle Human Resources	Required
Step 15	Define Timecards Layouts for Contingent Worker Time Entries	Oracle Time and Labor	Required
Step 16	Setup Preferences for Self-Service Timecard Entries	Oracle Time and Labor	Required
Step 17	Set Up Purchase Order Integration with Oracle Projects	Oracle Projects	Required to process project-based timecard entries
Step 18	Define Projects Contingent Worker Profile Options	Oracle Projects	Required to process project-based timecard entries
Step 19	Set Up Steps in Oracle Internet Expenses	Oracle iExpenses	Integration Oracle Projects, Oracle Payables, and Oracle iExpenses

For instructions on how to complete each step, refer to the following topics:

• Setting Up Steps in Oracle Purchasing to Process the Procurement of Contingent Workers

• Setting Up Steps in Oracle iProcurement to Process the Procurement of Contingent Workers

• Setting Up Steps in Oracle Human Resources to Process the Procurement of Contingent Workers

• Setting Up Steps in Oracle Time and Labor to Process the Procurement of Contingent Workers

• Setting Up Steps in Oracle Internet Expenses to Process the Procurement of Contingent Workers

• Setting Up Steps in Oracle Projects to Process the Procurement of Contingent Workers

Setting Up Steps in Oracle iProcurement to Process the Procurement of Contingent Workers

This topic describes the set up steps in Oracle iProcurement to process the procurement of contingent workers.

1. Create Information Templates

   Oracle iProcurement uses information templates to pass additional required information to the supplier. Common attributes such as supplier, price, currency, description of service and category are always captured on a service request. Any additional unique attributes are captured via the information template.

   Associate Information Templates to Purchasing Categories so that the template is visible during the Contractor Request flow in Oracle Procurement. For example, for a health care worker you may want to capture information on status of immunizations versus capturing information on knowledge of programming languages for an Engineer. The user can make any attribute either mandatory or optional and may reference default values.

   

   Information Templates are set up in Purchasing using the Define Information Template window. Using a Purchasing responsibility, navigate to Setup > Information Templates.

   Use the Information Template Association window to associate the template with an item or item category.

   

   For more information, refer to the Oracle iProcurement Implementation and Administration Guide.

2. Create Service Templates Using Smart Forms

   Requesters procure an item or service that is not found in the catalog. For these cases, they use a non-catalog request. The non-catalog request offers the ability to add an item or service to the shopping cart based on a description of the item or service. Through the use of smart forms, companies can conveniently control both the list of fields and whether a particular field is enterable or pre-defined. For example, create different services template for procuring services like legal services, painter, interior decorator. Legal services for visa applications, home purchases and will preparation could all be requested from the Legal Services Store. Each type of legal service could have an individual template so that the appropriate preferred supplier is communicated to the user and/or to ensure all mandatory attributes are captured on the service requisition.

   Service Templates are created by the Catalog Administrator in Oracle iProcurement. Navigate to the Smart Forms page and link the template to stores in iProcurement

   

   

3. Create Category Descriptors to Use the Rate Card Feature

   Hiring managers and purchasing users can view the rate card that provides details of the job and the standard rate that they should be paying for the job. Users can also view differential rates based on rate uplifts, offshore / onshore rates, markup driven rates, and location driven rates.

   Key benefits include:

   • Job Standardization via rate card support and standard rates for each job.

   • Benchmarking of job rates for specific jobs.

   • Ability to automatically identify preferred suppliers based on hiring needs.

   When creating contractor requests in Oracle iProcurement, the 'Use Standardized Job rates' option offers hiring managers the rate card, which provides a list of details about the job that will help the hiring manager to identify the right resource for the project. This region also provides the hiring manager with the ability to view the rate differentials and markup rates for the job in different locations.

   To enable requesters to use job standardization through the rate cards feature, complete the following steps:

   1. Create item categories using the Create or Update Item Category page in Oracle iProcurement.

   2. Associate a job to a shopping category using the Create or Update Job and Category Association page in Oracle Purchasing.

   3. Create and associate descriptors to a shopping category using the Manage Category Descriptors page in Oracle iProcurement.

   Create Item Categories:

   1. Log in using the iProcurement Catalog Administrator responsibility.

   2. Click the Schema tab and then the Item Categories subtab.

   3. Click Create Category in the Item Categories page. The Create Item Category page appears to create the item category.

      

   Associate a Job to a Shopping Category:

   For information on how to associate a job to a shopping category, see the Create Job and Shopping Category Association section in the Setting Up Steps in Oracle Purchasing to Process the Procurement of Contingent Workers topic.

   Create and Associate Descriptors to a Shopping Category:

   1. Log in to Oracle Purchasing.

   2. Navigate to the Associate Jobs with Categories page and click Create.

   3. In the Create Job and Category Association page, enter the details required to create the job and category association.

   When creating a job and category association, select the Shopping Category field to create category descriptors. The Manage Category Descriptors link is visible and active only if a shopping category is specified for the Job – Purchasing category combination.

   

   The Manage Descriptors page opens in Oracle iProcurement. and enables you to define descriptors for the shopping category. These descriptors are displayed in the contractor request as well as in other related documents. When a job is selected during contractor request creation in Oracle Procurement, then the descriptors associated to the shopping category are displayed for the hiring manager to provide the required details.

   To create a category descriptor, click Create in the Manage Category Descriptors page.

   

Setting Up Steps in Oracle Purchasing to Process the Procurement of Contingent Workers

This topic describes the set up steps in Oracle Purchasing to process the procurement of contingent workers. For more information on the steps discussed in this topic, refer to the Oracle Purchasing User's Guide.

Using Services Procurement, buyers create purchase orders to procure rate-based services.

1. Set Up Line Types in Oracle Purchasing

   Oracle Purchasing provides the line type feature to differentiate orders for goods from those for services or outside processing. In addition, the services related line types support a broad range of service categories including general business services, consulting services, and contingent labor. You use rate based line types when you are ordering services on a fee per unit basis. For example, you might order consulting services at $250 per hour.

   To process procurement of contingent workers, define rate based temp labor line type with 'Rate' as the value basis and 'Temp Labor' as the purchase basis. For Rate based temporary labor, Billing is based on a per unit rate such as per hour.

   • Value basis reflects how you wish to value the purchase. The 'Rate' value basis enables users to enter services by rate (price) and amount. Receive items by amount. The line types with a rate value basis the unit of measure class is restricted by the setting of the profile PO: UOM Class for Temp Labor Service.

   • Purchase basis indicates the nature of the purchase and determines the attributes that are required. Set up temporary labor purchase basis line types to enter purchasing documents to pay contingent worker providers.

   

   Create Line types in Oracle Purchasing (Setup > Purchasing > Line Types).

   Rate differentials such as overtime, holiday, shifts, etc. may be captured along with the base rate. Labor and expense budgets may be tracked separately.

2. Create Purchasing Category and Assign to Category Set

   For every item, there has to be a Purchasing Category set where the user defines the Structure name, Category, description and enablement for iProcurement. These categories are assigned to Purchasing category sets.

   

   Use the Categories window (Setup > Items > Categories > Category Codes > New) to define categories.

3. Associate Jobs to Purchasing Categories

   Jobs are created in Human Resource responsibility. Only jobs that are defined in Human Resource responsibility and assigned to a Purchasing Category are procured through Services Procurement. This setup is required for the entry of temp labor line types. When assigning a purchasing category, the user assigns a short job description and optionally defines additional job details such as skills and experience requirements. Job descriptions and details are displayed to the requester and are also communicated to the supplier.

   Use the Associate Jobs with Categories page (Setup > Purchasing > Job Category Association) to associate a purchasing category set to an HR job.

   

4. Create Job and Shopping Category Association

   The Shopping Category field lists all the shopping categories defined for the business group. Though it is optional to specify a Shopping Category, if you select one, the application establishes an association between the Job – Purchasing Category – Shopping Category.

   The Manage Category Descriptors link is visible and active only if a shopping category is specified for the Job – Purchasing category combination.

   

   Click the Manage Category Descriptors link to open the Manage Category Descriptors page. The Manage Descriptors page opens in Oracle iProcurement.

   For information on creating or updating job descriptors, refer to the Setting Up Steps in Oracle iProcurement to Process the Procurement of Contingent Workers topic.

   If buyers are negotiating offline with their suppliers, then create Standard Purchase Orders for rate based temp labor lines without any requisitions, agreements, sourcing events or other documents. The shopping category is defaulted in the Purchase Order line details page based on the selected job. Based on the Job – Purchasing Category – Shopping Category association, the descriptors get displayed in the line details page. The View Rate Card link next to the Job field, when clicked, opens the rate card details popup for the selected job.

   

   If Standard Purchase Orders are created from requisitions or as outcome documents of a Sourcing negotiation, then the descriptors and their values are copied from the source document and are displayed in the line details page.

   The action View Rate Card from the line details page enables the buyer to view the supplier – site combination and the corresponding source document related details.

5. Define Profiles Options Related to Process the Procurement of Contingent Workers

   • PO: Contractor Assignment completion warning delay

   • PO: Amount Billed Threshold Percentage

   • POR: Contractor Expense Line Type

   • POR: Re-approval After Contractor Assignment

   • ICX: Days Needed By

   • POR: Default Currency Conversion Rate Type

   See: Profile Options Used in Oracle Services Procurement

6. Enable/Disable Price Differential Lookup Codes

   A pre-defined list of price differentials is seeded. Users may disable some price differentials or create additional price differentials. Price differentials are expressed as a multiplier of the base rate. For example if the normal/base rate for a software engineer is 60USD per hour and the overtime rate multiplier is 1.5, overtime is charged at 90USD per hour (60 * 1.5).

   Use the Application Object Library Lookups window in the Application Developer responsibility to enable or disable the lookup codes for the PRICE DIFFERENTIALS for the lookup Type

7. Define an Approved Supplier List

   Using Define Approved Supplier List, the buyer optionally negotiates long-term service agreements in Oracle Sourcing.

   • Define one or multiple approved suppliers for each service category

   • Display approved suppliers during the contractor request flow

   

   Requests are released against the long-term service agreement using the pre-negotiated rates and terms. Approved suppliers are displayed to the requester during the requisition process. If a long-term agreement also exists for the supplier, the pre-negotiated rates are also displayed to the requester.

   Use the Approved Supplier List window (Supply Base > Approved Supplier List) in the Purchasing responsibility to define an approved supplier list.

8. Enable Suppliers for Pay on Receipt

   Define suppliers and supplier information.

   Navigate to the Buyer Work Center > Suppliers tab to create supplier information. To create invoices automatically from service receipts, ensure the supplier is enabled for Payment on Receipt.

   Pay on receipt is enabled in the Supplier page, Purchasing section, Self Billing tab. Set up supplier e-mail address for temporary labor suppliers. Provide an e-mail address for the Oracle iSupplier Portal user defined in the Users window for the supplier, supplier site, or supplier contact.

   

   For more information, see the supplier registration information in the Oracle iSupplier Portal Implementation Guide.

Setting Up Steps in Oracle Human Resources to Process the Procurement of Contingent Workers

This topic describes the set up steps in Oracle Human Resources to process the procurement of contingent workers.

A contingent worker is a non-employee people resource who works for the enterprise, and for whom the enterprise is responsible for their costs and expenses.

1. Create Jobs

   Oracle HRMS uses jobs to represent the duties people perform and the required skills. Define jobs for contingent workers based on your business requirements.

   

   Only jobs that are assigned a purchasing category are procured or negotiated through Services Procurement is done in Purchasing. Use the Job window Work Structure > Job > Description in the Human Resource responsibility to create required jobs.

2. Create Contingent Workers

   In Oracle Human Resources, the HR person type 'Contingent Worker' enables you to track the following information for contingent workers:

   • Contingent worker assignment history

   • Periods of service

   • Breaks in assignments

   • Positions

   • Supervisors

   • Worker and supplier relationships

   Note: Select the 'Projects Contingent Worker' person type to associate the contingent worker to a project in Oracle Projects. This person type controls the timecard layout for the contingent worker. If you select Contingent Worker Type, your timecard layout will not include the Project information.

   

   An HR personnel can use the following options to place contingent workers:

   • Create a contingent worker record using the People and Assignment windows in Oracle Human Resources.

   • Create a contingent worker record using the Contingent Worker Placement function in the Manager Self-Service responsibility. The HR user can place the contingent worker from a purchase order, Create Contractor Assignment link or directly navigate to the Contingent Worker Placement function from the Manager Self-Service responsibility.

   • Create a Contingent Worker Using Oracle Human Resources

     Navigate to the People window (Enter and Maintain > New) to create a contingent worker with all details such as Last and First Name, Birth Date, Social Security No., Action Type and Latest Start Date.

     

     Click the Assignment tab to navigate to the Assignment window and provide details such as the organization, job details, location, status, and supervisor name. You use the Supplier tabbed region to record information about the supplier providing the contingent worker to your enterprise. The procedure depends on whether you are using Oracle Services Procurement to provide purchase order information for contingent worker assignments.

     

     

     For more information on creating contingent workers using Oracle Human Resources, refer to the Oracle HRMS Workforce Sourcing, Deployment, and Talent Management Guide.

   • Create a Contingent Worker Using Oracle Self-Service Human Resources (Oracle SSHR)

     An HR personnel can create a contingent worker record using the Contingent Worker Placement function in the Manager Self-Service responsibility. The HR user can place the contingent worker from a purchase order, Create Contractor Assignment link or navigate directly to the Contingent Worker Placement function from the Manager Self-Service responsibility.

     Use the Contingent Worker Placement pages to create contingent worker details.

     

     In the Contingent Worker Placement pages, enter the details required to create the contingent worker record, such as the basic details, assignment status and supplier. If you navigate to this page directly from the purchase order notification, then the order details such as the purchase order number, line, and project details if any default to the page. Submit the placement record for approval after all the details.

     

     

     

     

     Depending on the approvals set in your enterprise, the placement is routed for approval.

     For more information on using Oracle SSHR to place contingent workers, refer to the Oracle Self-Service Human Resources Deploy Self-Service Capability Guide.

3. Define Users for Contingent Workers

   After the placement of a contingent worker, create an user for the contingent worker user and assign responsibilities to the user using the Define window (Security > User ) in the System Administrator responsibility.

   

   Assign the Self Service Time and Labor responsibilities to the contingent worker user to create timecard entries. For example, assign:

   • Contingent Worker Self-Service

   • Contingent Worker Time and Expense

   • Preferences SSWA

4. Link Multiple Purchase Orders to a Contingent Worker

   Oracle Services Procurement enables you to associate more than one purchase order or purchase order line to a contingent worker. If the task flow to use the PO_CWK_ASSOCIATIONS function is enabled, then you can use the Associate Purchase Order with Contingent Worker page to associate more than one purchase order or purchase order line to a contingent worker.

   Refer to the My Oracle Support document Set up for Task Flow: 1141005.1 to link multiple purchase orders with a contingent worker.

5. Set Up Profiles Options

   Oracle Services Procurement uses the following profile options in the procurement of contingent worker process:

   Set the following profile options:

   • MO: Operating Unit

   • HR: Business Group

   • HR: Security Profile

   • HR: Expand Role of Contingent Worker

   • HR: CWK in Head Count Reports

   • HR: Use Global Contingent Worker Numbering

   • HR: Contingent Worker Manager Actions Menu

   • HR: Contingent Worker Personal Actions Menu

   See: Profile Options Used in Oracle Services Procurement

Setting Up Steps in Oracle Time and Labor to Process the Procurement of Contingent Workers

This topic describes the set up steps in Oracle Time and Labor to process the procurement of contingent workers.

The following features in Oracle Time and Labor support the processing of contingent worker procurement:

• Single source of time entry

• Configurable timecard layouts for contingent workers

• Validation of time data from recipient applications

Oracle Time and Labor integrates with Oracle Services Procurement to provide visibility into Services Spending, controlling input of overtime and shift differentials of contingent workers, and validation of purchase orders against pre-authorized amounts.

For more information about the steps in this topic, refer to the Oracle Time and Labor Implementation and User Guide.

1. Define Timecard Layouts for Contingent Worker Time Entries

   The OTL layouts for contingent workers support:

   • Association of time entries to purchase orders

   • Automation of timecard approval routings

   • Generation of purchase order receipts from approved timecards

   Workers use a self service web page in the format of a timecard for timecard entries.

   

   Create different timecard layouts for each group of workers so that they only see the fields that are relevant to them.

   There are five types of layouts: for data entry, review, confirmation, and detail (corresponding to the web pages in the Self Service workflow), plus a layout for exporting data for disconnected entry.

   Following are the predefined OTL layout styles:

   • Projects layout: Using this layout, workers enter their time against a selected project, task, and type. Workers click on a Details button to enter comments against each project, task, and type combination.

   • Payroll Layout: Using this layout, workers enter a start and stop time, or a number of hours, for each day of the week for the selected hours type. This layout is suitable for workers who are submitting their time to Oracle HR or Payroll.

   • Projects with Payroll Layout: This layout is similar to the Projects layout except that the list of values for the Type field comes from the alternate name you have assigned to the worker (using preferences) for the Expenditure Elements alternate name type. So when a worker selects a type for a time entry, an element name is also recorded in the time store.

   • Work based Projects and Payroll Layout: Using this layout, workers enter their time against a selected project, task, task and cost code type, job, location, and work type. Workers click the Details button to enter comments against each project, task, and type combination.

   • Exception Layout: This layout displays one row where the worker selects an hours type and cost center, then enter the number of hours for each day of the week. Use this layout for workers who only need to submit timecards for exception reporting (such as time absent for sickness or vacation).

   Several layout styles are predefined. Use these as supplied, or copy and modify them. For example, modify a layout to remove a field that you do not use.

   For instructions on modifying layouts, refer to the white papers available on My Oracle Support:

   • Oracle Time & Labor Timecard Configuration, Note 304340.1

   • Timecard Audit Trail White Paper: Note 842159.1

2. Set Up Preferences for Self-Service Timecard Entries

   Preferences enable you to define rules about how individual workers or groups of workers can use the application. There are rules for the time store, such as which set of applications can retrieve data about a worker's time, and rules about Self-Service timecard entry, such as whether the worker can enter a negative number of hours. Choose which preferences workers can see, and which ones they can edit.

   For time entries based on integration with Oracle Purchasing or Oracle Projects, define Preferences using the Preferences window in the OTL Application Developer responsibility.

   

   

   Note: When you setup OTL- Oracle Projects integration, ensure that the OTL preference Project Payroll Integration is set in order to use the project timecard layouts intended for use with the HR rate source for labor costing. For more information on setting OTL preference, see Defining Preferences, Oracle Time and Labor Implementation and User Guide. For more information on using HR rates for labor costing, see: Using Rates for Costing, Oracle Projects Fundamentals Guide.

Setting Up Steps in Oracle Internet Expenses to Process the Procurement of Contingent Workers

Features in Oracle Internet Expenses support:

• Entry of expense reports on behalf of contingent workers

• Automated approval routings

• Payment to Supplier not the contingent worker

• Contingent worker expense processing

Buyers must have the Internet Expenses responsibility to create an expense report on behalf of the contingent workers. To use the contingent worker functionality in Internet Expenses, you must set up your contingent workers in Oracle HRMS.

For more information, see: Oracle Internet Expenses Implementation and Administration Guide.

Setting Up Steps in Oracle Projects to Process the Procurement of Contingent Workers

This topic describes the set up steps in Oracle Projects to process the procurement of contingent workers.

Oracle Projects enables you to define and utilize contingent workers on projects in the same capacities and manner as employees. Define requirements and perform searches for contingent worker candidates, and directly assign contingent workers to projects and tasks.

Contingent workers can enter timecards via preapproved batches or Oracle Time and Labor. You can set up Oracle Projects to calculate contingent worker labor costs based on the rates defined in the purchase orders you create to procure contingent worker services.

To facilitate processing of contingent worker expenses, you can optionally allow contingent workers to enter their expenses directly in Oracle Internet Expenses, or via Microsoft Excel expense entry and preapproved batches in Oracle Projects. You can also require the enterprise responsible for providing contingent worker services to invoice you for these expense costs and process the expense invoices in Oracle Payables.

To distinguish contingent worker labor and expense costs from employee costs, you can define AutoAccounting rules to separately account for contingent worker costs. As with other project costs, you can view the details of contingent worker labor and expense costs via Expenditure Inquiry, Project Status Inquiry, Project Performance Reporting, and in Discoverer workbooks. For more information about the setup steps in this section, refer to the Oracle Projects Implementation Guide and Oracle Projects Fundamentals.

To integrate Services Procurement contingent worker flow with Oracle Projects, complete the following steps

1. Create Projects

   Create projects (Projects > Projects Definition > Projects) using an appropriate Projects responsibility. Define the project with details of the Project Name, Number, Expenditure Type, Task and other project related details.

   

2. Set Up Purchase Order Integration with Oracle Projects

   Import Contingent Worker Timecards with Purchase Order Integration: Enable this option if you want to import contingent worker labor costs from timecards. When you select this option, contingent workers can select a purchase order when they enter timecards. Specifying a contingent worker purchase order on a timecard allows the labor cost to be imported via the timecard, and prevents interface of labor costs to Oracle Projects from supplier invoices that are associated with the purchase order.

   To enable this option, navigate to the Implementation Options window (Accounting > Setup > System).

   Click the Expand/Costing tab and select the check box Import Contingent Worker Timecards with Purchase Order Integration.

   

3. Enable Contingent Workers for Project Types

   In the Project Types (Set Up > Project > Project Types ) window, Enable the 'Contingent Worker Enabled' check box to include all purchase orders associated with contingent worker enabled projects available for selection when a contingent worker enters a timecard. If you do not enable this, only purchase orders associated with the project that the contingent worker entered on the timecard, are available for selection.

   

4. Define Oracle Projects Profile Options

   The following Oracle Projects profile options affect the procurement of contingent worker business flow.

   • PA: Allow Time Entry of Negative Hours

   • PA: AutoApprove Timesheets

   • PA: Enable Business Messages on Time Entry

   • PA: Override Approver

   See: Profile Options Used in Oracle Services Procurement

5. Set Up Auto Accounting to Process the Procurement of Contingent Workers

   Use the Assign AutoAccounting Rules in the Projects responsibility. Contingent Worker Labor is the function transaction the supports the contingent worker cost accounting in the the Labor Cost Clearing Account function.

   

   For more information on setting up the AutoAccounting feature to process the procurement of contingent workers, refer to Oracle Projects Fundamentals.

6. Implement Oracle Projects, Oracle Internet Expenses, and Oracle Payables Integration

   Implement Oracle Projects, Oracle Internet Expenses, and Oracle Payables integration to enable project-related expense report entry in Oracle Internet Expenses. For information, refer to the Oracle Projects Implementation Guide.

   The following flow diagram provides an overview of expense reporting in Oracle iExpenses to generate invoices in Oracle Projects.