This chapter provides an overview of business units in PeopleSoft Enterprise Strategic Sourcing and discusses how to define business units.
This section discusses:
Strategic Sourcing business units.
Event dates.
A business unit is an operational subset of an organization. It tracks and maintains its own set of events and their respective awards.
When you create business units for events, you can set the defaults for event dates and times.
If you are using PeopleSoft Enterprise Purchasing, sync the setIDs between the business units of both applications to ensure that purchase orders and contracts are correctly created when you award events. Specifically, the same setID should be used for the following record group IDs:
FS_38 (vendors).
FS_26 (locations).
DS_02 (freight and shipping codes).
FS_18 (items).
PO_04 (ship to addresses).
FS_18 (item categories).
You map the PeopleSoft Enterprise Purchasing business unit to the Strategic Sourcing business unit on the Purchasing business unit setup page. This enables you to associate multiple Purchasing business units to the same Strategic Sourcing business unit, which facilitates consolidating requisitions across multiple Purchasing business units.
See Defining PeopleSoft Purchasing Business Units and Processing Options.
The formal dates within each event consist of the calendar date and the time of day, for example, 02/14/2005 9:49AM PST.
There are four dates for each event:
Create: The date when you create the event, before it goes through the internal approval process and is made available for bidding.
Preview: The date that you can make available to potential bidders, allowing them to review the event as well as enter and save their bids, which they can post as soon as the event starts.
You can preview only auction and RFx (request for quote), not RFI (request for information) events.
Start: The date when bidders can begin to post bids for the event.
End: The date when the bidding closes.
This time can be extended; if a last-minute bid is entered, you can extend the end date to give earlier bidders the opportunity to counterbid.
To set up sourcing business units, use the Maintain Business Units component.
This section discusses how to:
Define a Strategic Sourcing business unit.
Set event dates.
See Also
Page Name |
Object Name |
Navigation |
Usage |
BUS_UNIT_TBL_A1 |
Set Up Financials/Supply Chain, Business United Related, Sourcing, Business Unit Definition |
Define the parameters of the business unit. Either click the Add button after adding a new value, or select a business unit by number from list of existing values. |
|
A1_DEFLT_DATE |
Set Up Financials/Supply Chain, Business United Related, Sourcing, Business Unit Definition |
Set the dates and times for previewing, starting, and ending an event. |
Access the Business Unit Definition page.
When creating a new Strategic Sourcing business unit:
Note. These fields are available for selection when you create new Strategic Sourcing business units.
Unit and Short Description |
Enter the name and description for the new Strategic Sourcing business unit. |
Default SetID |
(Optional) Select a value for this business unit. |
|
Click the Create BU button after you enter all the field information to save the data and create the business unit. If the business unit is unique, a new row is inserted into the setID table. |
Enter the values for the fields; these are the default values for events that are created for this business unit. You can change any of these defaults on a per-event basis when you create events.
Business Unit Definition
Location Code |
Enter default geographic locations for events within this business unit. |
Billing Location |
Enter mailing addresses for billings that are to be used for this business unit. This is only applicable to sell events. |
AM Unit (asset management unit) |
Enter the Asset Management Business Unit that is to be used for sell events within this business unit. Selected assets are based on the asset management business unit that is associated with the event business unit. |
Bill Source |
Enter the external and online systems from which PeopleSoft Enterprise Billing receives bills. When you integrate to PeopleSoft Enterprise Asset Management and sell an asset by using PeopleSoft Enterprise Strategic Sourcing sell event, the Strategic Sourcing system sends the asset sale information to PeopleSoft Enterprise Asset Management. PeopleSoft Enterprise Asset Management then sends that information to PeopleSoft Enterprise Billing to create the bill. The PeopleSoft Enterprise Billing system uses the bill source to identify that the bill originated from PeopleSoft Enterprise Strategic Sourcing. The system only displays this field if you have PeopleSoft Enterprise Asset Management installed. |
Dispatch Method |
Enter the default means by which bidders are notified: Email, Print, or Fax. |
Currency Code |
Enter the default currency that is to be used for events that are within this business unit. |
Rate Type |
Enter the default rate type that is to be used for events that are within this business unit. |
Allow Multicurrency Events |
Select to allow events to be created in currencies other than the default. |
Log History of Event Changes |
Select to indicate that you want to track the event change dates, times, and the user making changes to a sourcing event. |
Require New Version for Edits |
Select to indicate that a new event version must be created when an event is changed. Important! If you select this check box, you must create a new version every time you modify an event. |
Permit Award to Previous Round |
Select to indicate whether a previous event round can be awarded. If not selected, you can only award bids from the current round. |
External PO Integration |
Select to enable awarded events to be published to external purchasing systems such as:
The system automatically publishes the purchase order when you click the Post Award button on the Award Details page. With this selected, you can’t award buy events to PeopleSoft Enterprise Purchasing. Important! If you select this check box, you can't award buy events to PeopleSoft Enterprise Purchasing, you can only award events to an external purchasing system. |
Default Options for All Events
Allow Bidder XML Downloads |
Select to enable bidders to download events to an XML file. If this option is not selected, a PDF version of the sourcing event will be created; however, an XML version will not be created when the events are posted. |
Factor Header Score Into |
Select to indicate that you want the system to factor the header score into the total score for the event or the individual line score. If Total Score is selected, the header score will be factored into the total score of the event which is calculated by adding the weighted line scores plus the weighted header score. Select this option if you intend to award the entire event to one bidder. If Line Score is selected, a header score bid factor will automatically be added to each line within an event. The line score will be calculated by adding the weighted scores of each line bid factor plus the weighted header score. Select this option if you intend to award different lines within the event to different bidders, or if you intend to use the optimization engine to recommend sourcing awards. The optimization engine uses the bidders line scores, not total scores, to determine an ideal award allocation. |
Event Header Weighting |
Enter a default weighting to determine how the system weighs the header score in relation to the total or line score. For example, if the header score is factored into the total score and you set the default event header weighting to 20 percent, then create an event with three lines. Line 1 is weighted 50 percent, line 2 is weighted 20 percent, and line 3 is weighted 10 percent. The total weighting of the lines is 80 percent plus the defaulted weighting of the header (20 percent), totalling 100 percent. For example, if the header score is factored into the line score and you set the default event header weighting to 20 percent, then the sum of the remaining bid factors for each line must total 80%. For example, you could have the price bid factor with a weighting of 50% and warranty with a weighting of 30%. The remaining 20% would be the header score bid factor, which is automatically added to each line. |
Bid Quantity Rule |
Select the bid quantity rule that will default onto all lines in the event.
|
Bid Required on All Lines |
Select to indicate that the bidders must submit bids for all lines in the event. |
Start Price Rule |
Select a value to indicate the rule that the system is using as a basis for pricing:
|
Round/Version Display |
Select a value to indicate how the rounds should display to bidders:
|
RFx Event Default Options
Multiple Bids Allowed |
Select to allow multiple bids on RFx sourcing events. Auction events inherently allow multiple bids by the same bidder on the same event. |
Allow Edit of Posted Bids |
Select to enable bidders to edit their posted bids for RFx and RFI events. Bidders cannot edit their posted bids on auction events. |
Sealed Event |
Select to indicate the event is sealed, which means that the event originator cannot view either bids or bid history until the event has ended. This option is only available for RFx events. |
Display Bid Factor Weightings |
Select to display to bidders the weightings associated with bid factors for RFx and RFI events. Bid factor weightings are always displayed to bidders on auction events. |
Auction Event Default Options
Allow Proxy Bidding |
Select to enable bidders to use automatic proxy bidding. |
Rank Options |
Select a value:
Note. If you selected the Allow Proxy Bidding check box, this field is not available. |
Event Will Be |
Select a value to indicate the basis on which the event will be awarded:
Note. If you selected the Allow Proxy Bidding check box, Price Based is automatically selected because proxy auctions are based on price. |
Bidders Must Beat |
Select a value:
Note. If you selected the Allow Proxy Bidding check box, Winning Bid is selected. |
Display Winning Bid to Bidders |
Select this option if you want the winning bid to be displayed to all bidders. Note. If you selected the Allow Proxy Bidding check box, this field is not available. |
Bid History Display |
Select a value to indicate how to display the bid history to bidders:
|
Bidders Compete At |
Select either Event Level or Line Level. If Event Level is selected, bidders compete based on best total price or best total score. In some cases, a bidder may post a subsequent bid that has a worse score or price on one or more lines as long as the total score or price is better than their previous bid or the current winning bid. If Line Level is selected, bidders compete based on the best line price or line score. Note. If you selected the Allow Proxy Bidding check box, this field is not available. |
RFI Event Default Options
Respond to all Bid Factors |
Select to indicate that bidders must respond to all bid factors associated with sourcing events. |
Score RFI Event |
Select to indicate that you want the system to calculate a score for RFI responses. |
Access the Default Dates page.
Use this page to set and maintain defaults for the preview, start, and end dates of all events that are related to this specific business unit. These defaults can be adjusted on a per-event basis when you create individual events, at which time you can also provide for an automatic extension of the event.
Enter the values of event dates and times that you need to set:
Increment |
Enter the unit of time in days, hours, or minutes that you want to use to calculate the period. |
Start Time |
Enter when bidders can post their bids on the items offered. The start date of the event is relative to the create date; that is, X days, hours, or minutes after the create date. |
Preview Time |
(Optional) Enter the time when prospective bidders can review the items that are offered and enter their responses to bid factors, but not post the bid. The time for preview is relative to the start time, that is, X days, hours, or minutes before the start time. |
End Time |
Enter the time when bidders can no longer bid; the event closes pending award. The end of the event is relative to the start time, that is, X days, hours, or minutes after the start time. |