This chapter provides an overview of purchasing item information and discusses how to:
Define purchasing item categories.
Define purchasing item attributes.
Update item vendor unit of measure conversion rates.
Capture item miscellaneous charges.
Set up item vendor price adjustment rules.
Update standard prices and business unit standard prices.
Select vendors based on item shipping location.
Create purchasing kits.
Defining values on the purchasing item information pages provides item-related processing information and default values that minimize errors and maximize productivity when creating purchasing transactions.
This section discusses how to:
Set up item catalogs.
Work with market codes.
With PeopleSoft Purchasing, you can define any number of item catalogs. These item catalogs can be tailored for individual, department, or corporate-wide use and can greatly reduce the repetitive tasks associated with service and material purchases, such as rent, supplies, and standing inventory.
With PeopleSoft catalog functionality, you can:
Assign default item catalogs tailored specifically to individual requesters.
Transfer item catalog information in electronic format into PeopleSoft catalogs.
PeopleSoft offers the ability to load and maintain items from various applications, including a process that loads and updates item information from a third-party or supplier to PeopleSoft Purchasing and an Item Loader process that synchronizes item information between systems.
These are the main steps involved in creating an item catalog:
Create the category that will serve as the first node in the catalog tree.
Create a catalog tree.
Assign catalogs to the requesters.
Associate an inventory item with a category.
To create the category that will serve as the first node in the catalog tree:
Access the Item Categories - Category Definition page in Add mode.
In the access requirements for the page, enter the setID and the category code that you want to use as the first node for the new catalog tree.
On the Item Categories - Category Definition page, enter required information, including account, description, short description, and currency code.
Save the category.
You may see warning messages about tolerances that have been left as zero (0.00000). For our current task, this is acceptable. Click the OK button to acknowledge the warning.
When the system asks if you want to update item catalogs with the category changes, click the No button because you have not yet created the target catalog tree.
In the future, once the catalog tree has been established, click the Yes button, and select the catalog to which you want to assign a new category.
To create a catalog tree:
Access the Tree Manager component.
Choose to create a new tree definition and enter a tree name.
On the Tree Definition and Properties page, enter the basic information: tree name, structure ID, effective date, description, category, use of levels, audit options, and performance options.
Click the OK button to accept the settings and close the Tree Definition and Properties page. When you do, the Enter Root Node for Tree page appears.
On the Enter Root Node for Tree page, create a tree level for the new tree.
If there is no existing level listed, click the Add Level button to access the Tree Levels page, where you can define the level that will be used by the entire tree you are creating. If there is an existing level, you may choose to select it.
Enter a level name on the Tree Levels page.
The level name that you define here can be any generic name, for example, LEVEL 1.
If the level does not already exist in the system, you will be transferred to the Tree Level Setup page.
On the Tree Level Setup page, enter further information about the level.
This includes information such as effective date, status, description, and short description.
Click the Apply button to save the settings. Click the OK button to return to the Enter Root Node for Tree page.
On the Enter Root Node for Tree page, create the first node by defining a value in the Root Node field.
This should be the name of the first node.
Click the OK button to accept and create the first node. When you do, the Tree Manager page appears.
On the Tree Manager page, click the Insert Detail button to create the detail node.
The Detail Value Range page appears.
On the Detail Value Range page, select the Dynamic Flag check box and click the Add button.
The system returns you to the Tree Manager page.
Save the new tree definition.
You have now successfully created an item catalog tree.
Click the Yes button when prompted to update item catalogs with the category changes.
Assign the new category to the new catalog.
Launch Tree Manager to verify that the nodes have been created correctly for the catalog.
To assign catalogs to the requesters:
Access the Requester Setup page, and enter the requester name in the access requirements.
Select the Use Only Assigned Catalogs check box.
In the Catalog Information scroll area, assign catalogs to the selected requester.
Select the Default check box for the catalog that the requester will use as their default catalog.
See Also
Defining Purchasing Item Categories
Enterprise PeopleTools 8.46 PeopleBook: PeopleSoft Tree Manager
Establishing Requesters and Defaults
If you are an existing PeopleSoft Purchasing customer, the conventional category codes are considered to be user defined and the market codes for these codes will be set to User Def (user defined) (01) in the Item Categories component after running the upgrade script. You can maintain the same coding scheme, as well as migrate to the new industry standard coding scheme, the Universal Standard Products and Services Classifications (UNSPSC). PeopleSoft eProcurement provides you with the Import CUP File process (PV_CP_LOAD) to load UNSPSC and their corresponding MarketSite items through a batch process.
Use the UNSPSC to classify products and services at two-, four-, six- and eight-digit levels, depending on your specific needs. Each subsequent level of detail describes a subset of all codes and descriptions preceding it in the code's hierarchy.
For example, ballpoint pens at the eight-digit level are a subset of writing instruments at the six-digit level, which is a subset of office supplies at the four-digit level. These descriptions are varying degrees of office equipment, accessories, and supplies at the two-digit level. You can add ninth and tenth digits to indicate the business relationship to the supplier, such as rental/lease, wholesale, retail, or original equipment manufacturer. Each UNSPSC is unique and enables unambiguous translation of the commodity's description into any language.
This table explains the UNSPSC coding hierarchy. In this example, leased addressing machines are assigned UNSPSC number 4410210510. They are classified as office equipment, accessories and supplies, one of 55 existing segments at the top level of the UNSPSC hierarchy.
Level |
UNSPSC |
UNSPSC Description |
Segment |
44 |
Office equipment, accessories, and supplies. |
Family |
44 | 10 |
Office machines and their supplies and accessories. |
Class |
44 | 10 | 21 |
Mail machines. |
Commodity |
44 | 10 | 21 | 05 |
Addressing machines. |
Business function identifier |
44 | 10 | 21 | 05 | 10 |
Addressing machines, leased. |
When you add a new category code using the Item Categories component, the system checks to see if the code consists of only numbers and has an even number of digits. If so, the system then assigns UN/SPSC (02) as the market code. If the category code does not meet these criteria, the system assigns User Def. (01) as the market code. You cannot modify the market code once you add the category code.
If the market code for the new category is set to UN/SPSC, the system looks at the code and determines if its ancestor codes must be created and creates them accordingly. The length of the ancestor codes that are automatically generated is based on the length of the category code that you just entered. For example, when you enter the category code 4410210510 and no ancestor codes exist, the system generates the following ancestor codes:
4400000000
4410000000
4410210000
4410210500
Upon saving the Item Categories component, the system asks if you want the item catalogs updated. If the answer is no, the catalog tree is not updated. If the answer is yes, the Update Catalog Tree page appears. If you are updating an existing code, the page displays the existing catalog information.
The relationship between CATEGORY_CD and CATEGORY_ID (a system-assigned sequential number) is one-to-one in the PS_ITM_CAT_TBL table. The relationship between an item (PS_MASTER_ITEM_TBL) and a category (PS_ITM_CAT_TBL) is many-to-one.
Note. Many different items can be mapped to one category. However, no one item can be mapped to more than one category.
For example, the following scenario is not supported: In setID SHARE, item 10002 is mapped to category code CYCLING (CATEGORY_ID = 00009). This means that for catalog ALL_PURCHASE_ITEMS, item 10002 belongs to the tree node CYCLING (due to dynamic range).
Because Tree Manager does not perform node assignment checks, for example, it is possible that you can create an item static range from 10001 to 10003 under another tree node, FISHING. This range violates the relationship previously described because, in this case, item 10002 is mapped to two categories, CYCLING and FISHING. It is best to avoid this scenario because it can create unpredictable results when you use the Order by Catalog function.
See Also
Defining Purchasing Item Categories
Days Late, Early Ship Rjct Days (days late, early shipment rejection days) |
Enter the acceptable number of days before or after a shipment date during which you will still receive the goods. |
Ext Price Tolerance /% Ext Price Tolerance (extended price tolerance/percentage extended price tolerance) |
Enter the matching tolerance amount and percentage for the extended price (amount multiplied by quantity) of the item. The extended price tolerance is the tolerance for the entire order, not just an individual item. |
Inspect ID (inspection ID) |
Displays the inspection IDs, which are established on the Inspection Routing page. |
Inspection Required |
Select this option to require inspection and to make the other inspection fields available for entry. |
Inspection UOM (inspection unit of measure) |
Select from the following: Standard: Select to perform inspections in the standard UOM set up on the Item Definition - General: Common page. Vendor: Select to perform inspections in the UOM used on the purchase order to the vendor. |
Lead Time Factor %, Ship to Priority Factor %, Price Factor %, Vendor Priority Factor % (lead time factor percent, ship to priority factor percent, price factor percent, vendor priority factor percent) |
If you select the Flexible sourcing method, enter the percentage weight that you want to give to lead time, price, ship to, and vendor priority. The higher the percentage that you give to one of the criteria, the more weight that criterion has. For example, if you want to select the vendor based only on lead time, you can give lead time a percentage weight of 100 percent and the vendor with the best lead time (regardless of price, ship to, or vendor priority) is selected. |
Partial Qty (partial quantity) |
Indicate the action that you want to take if you receive less than the quantity specified on the purchase order schedule. Select from: Open: Select to receive the partial quantity, leave the receipt line status as Open, and enable the receipt to be saved. Open/Error: Reject the partial quantity, leave the receipt line status as Open, and generate an error message. Open/Warn (open, but with a warning): Receive the partial quantity, leave the receipt line in Open status, and generate a warning message. Recvd (received): Receive the partial quantity and change the receipt line status to Recvd. Recvd/Warn (received with a warning): Receive the partial quantity and change the receipt line status to Recvd, but also generate a warning about the partial quantity. |
Receiving Required |
Select the receiving requirement for the item. Values are:
|
Reject Qty Over Tolerance (reject quantity over the tolerance limit) |
Select this check box to reject a quantity that surpasses the tolerance limits that you set. |
Sourcing Method |
Select from Basic, Cumulative Split, Flexible,and Sched Split (split schedule). This value appears by default from the category assigned to the item. |
Tolerance Over, Tolerance Under |
Select the amount or percentage over or under the tolerance selected that still enables a voucher match. |
Unit Price Tolerance/% Unit Price Tolerance (unit price tolerance/percent unit price tolerance) |
Displays the matching tolerance amount and percentage for the price of an individual item. |
To define purchasing item categories, use the Item Categories component (ITEM_CATEGORIES).
This section provides an overview of item categories and discusses how to:
Define item categories.
Update catalog trees.
Define item category control options.
Define item category vendor sourcing priorities.
If your installation includes PeopleSoft Purchasing, you must create categories for the items. You will be required to assign new items to a category on the Define Item - General: Common page. Category information helps reduce redundant data entry during both item setup and requisition and purchase order processing. The purchasing attributes of an item category are assigned as defaults to any item in that category.
Item categories can provide transaction information for requisitions, requests for quotes, contracts, and purchase orders. Item categories also serve as the organizational unit for item catalogs. In fact, item catalogs are a collection of item categories. Each item added to a category is automatically added to each catalog that contains that category.
For each category that you create, you can define purchasing attributes, such as general ledger account, primary buyer, lead time, price tolerances, and so forth. For example, you might create a category for outdoor equipment with a set of default purchasing attributes that apply to most of the outdoor equipment purchases. During item definition, every item that you assign to the outdoor equipment category receives the attributes of that category.
Note. If you don't order by item ID, category attributes will default to the item lines of requisitions, contracts, and purchase orders on which you specify the category codes. If you do order by item ID, the attributes default from the Item tables rather than the Category tables.
Page Name |
Object Name |
Navigation |
Usage |
CATEGORY_TBL |
Items, Define Controls, Item Categories, Category Definition |
Define item categories. |
|
CAT_PNLS_CATLG_SEC |
Change item categories or add a new item category on the Item Categories - Category Definition page and save. Click the Yes button when asked if you want to update catalogs with the category changes. |
Select the catalog tree to update with new category code information. |
|
ITM_CAT_BU_SEC |
Click the BU Attributes (business unit attributes) link on the Item Categories - Category Definition page. |
Assign a buyer to this category for each business unit. You may want to do this if you order by description and want a default buyer for this category by business unit. This setup is optional. The system uses the values set for the buyer at the item category level for all business units that are not specified here. |
|
CAT_PARENTAGE_SEC |
Click the Hierarchy link on Item Categories - Category Definition page. |
View information about where a category resides in the entire catalog tree hierarchy. |
|
VAT_DEFAULTS_DTL |
Click the VAT Default link on Item Categories - Category Definition page. |
Define VAT defaults. |
|
VAT_DEFAULTS_DTL |
Click the VAT Service Treatment Setup link on Item Categories - Category Definition page. |
Define service VAT treatment defaults. See Setting Up and Maintaining Service VAT Treatment Defaults. |
|
CATEGORY_TBL2 |
Items, Define Controls, Item Categories, Category Definition 2 |
Define the matching and receiving controls, sourcing controls, and miscellaneous controls and options for the category. Also use to set price tolerance defaults for items to trigger workflow exception notifications. PeopleSoft Purchasing and PeopleSoft Payables use matching controls to match receipts, purchase orders, and vouchers. Receiving controls specify how receiving users process items assigned to this category. These values become a part of the item default hierarchy and can default to purchase order lines where this category is specified. |
|
ITM_CAT_VND_PR_SEC |
Click the Priorities link on the Item Categories - Category Definition 2 page. |
Set the vendor priority and split sourcing allocation percentage for vendors for this category |
Access the Item Categories - Category Definition page.
Market Code |
Select the coding scheme that a category code is using. Values are: UN/SPSC (Universal Standard Products and Services Classification) (02) and User Def. (user defined) (01). |
Status |
Select a category status. Changing a category status from Active to Inactive means that you can no longer assign items to the category. This status change does not affect the existing and future PeopleSoft Purchasing transactions involving items in the inactivated category. For example, setting a category status to Inactive has no effect on orders that you have in progress that contain items tied to the newly inactivated category. You can also continue to add these items to the PeopleSoft Purchasing transactions using the usual methods, such as entering an item ID directly on the online page or using the Order By Catalog page or Item Search Criteria page. |
Lead Time Days |
Enter the number of lead-time days required for items in this category. This value is used in calculating the due dates for purchase order lines when the category you're defining is specified for a line on which no item ID is specified, the purchase order has no default due date, or no due date is specified on the line schedules. |
Account |
Select a valid account number to identify the general ledger account to be associated with the items in this category. This account number is used on transactions when no item ID is specified at the line level of a PeopleSoft Purchasing purchase order and no default account is specified for the transaction. |
Asset Profile ID |
Select an asset profile ID for the category. Asset profile IDs are transferred to PeopleSoft Asset Management when PeopleSoft Purchasing receives an item that specifies both an asset profile and an PeopleSoft Asset Management business unit. When you define a purchase order or requisition line using an asset category without specifying an item, the asset profile of that category becomes the default. Asset profile IDs are set up on the Asset Profile page. |
Usage Code |
Enter an ultimate use code to default on to purchasing transactions whenever this category is referenced on an ad hoc (order by description) line. In most cases, sales tax is computed as a use tax based on the tax code applicable to the ship to or usage destination. However, how merchandise is ultimately used may also result in a different tax rate within the same ship to or usage destination. |
Physical Nature |
Indicate if the object is a physical good or service. Values are: Goods and Services. |
Where Performed |
Select the location where the service is most often performed: Buyer's: Select if the service is physically performed at the buyer location. Ship From: Select if the service is physically performed at the ship from location. Ship To: Select if the service is physically performed at the ship to location Supplier's: Select if the service is physically performed at the supplier location. Note. This option is available only when the physical nature is service. |
See Also
Creating Requisition Schedules
Understanding PeopleSoft ChartFields
Processing Multiple Currencies
Access the Update Catalog Tree page.
Parent Category |
When the market code for the category is UN/SPSC (02), the Parent Category field is unavailable for entry because the system generates and maintains UNSPSC ancestor nodes automatically. You can select multiple catalog trees for updating. When the market code is User Def. (01), you must select a Parent Category value. Then click the Catalog Refresh button to retrieve the catalog trees to which the parent category belongs. You can select only one catalog tree for updating. Note. The category being modified is not available as a parent category when updating the catalog tree. |
Access the Item Categories - Category Definition 2 page.
Sourcing Controls
Accumulate Level |
If you select Cumulative Split in the Sourcing Method field, this field becomes available for entry. Select Run to accumulate the percentage for the vendor based on each run of the PO Calculations process (PO_POCALC), or select Schedule to accumulate based on each schedule. |
Cumulative Sourcing
In the Cumulative Sourcing group box, set the options for the cumulative sourcing method. The fields in this group box become available if you select Cumulative in the Sourcing Method field.
Year to Start |
Designates the year in which you want to start maintaining vendor history. You cannot specify a year in the future. Cumulative sourcing must be based on history and cannot occur in the future. |
Month to Start |
Enter the number of the month in which you want to start maintaining vendor history. Changing the value in this field triggers recalculation of historical quantities and amounts. History is always maintained from the first day of the start month to the first day of the end month. |
Number of Months |
Enter the number of months for which you want to keep vendor history. Changing the value in this field triggers recalculation of historical quantities and amounts. |
Start Date |
Displays the start day, which is calculated based on the values that you define for the Year to Start, Month to Start,and Number of Months fields. History is always maintained from the first day of the start month to the first day of the end month |
End Date |
Displays the date on which vendor history should be refreshed. This date is calculated based on the values defined for the Year to Start and Month to Start fields, plus the value in the Number of Months field. So if Month to Start is 1 and Number of Months is 3, the End Date will be 04/01. History is refreshed by the first run of the Cumulative Sourcing Update process (PO_POHISTUD) as soon as the current date is greater than or equal to the end date. |
Total Category Amount |
Displays the total merchandise amount for all vendors for this category for the historical period, in the category currency. |
Misc. Controls and Options
Close PO Under Percent Tol (close purchase order under percent tolerance) |
Enter an acceptable percentage of the total quantity that can be outstanding while still enabling the purchase order to be closed. If the quantity not yet received is less than or equal to the valued entered here, the PO RECON process (PO_PO_RECON) will treat the purchase order as fully received. |
RFQ Required (request for quote required) |
Select this check box if the item must go through the RFQ cycle before it can be included on a requisition or purchase order. |
See Also
Running the PO RECON Application Engine Process (PO_PORECON)
Running the PO Calculations Process
Updating Vendor History Dates and Amounts for Cumulative Sourcing
Access the Vendor Sourcing Priorities page.
Priority |
Enter a priority rank for the vendor. When the PO Calculations process selects a vendor for the item, it uses the priority ranking, with the lowest number (1) as the first choice. When you add another vendor, the next priority ranking is automatically assigned. |
Allocation Percentage |
If you selected Sched Split or Cumulative Split in the Sourcing Method field on the Item Categories - Category Definition 2 page, enter the allocation percentage for the selected vendor. |
Merchandise Amt (merchandise amount) |
Displays the total merchandise amount for this vendor for this category for the historical period, along with the category currency. |
See Also
Running the PO Calculations Process
Defining Purchasing Item Categories
To define purchasing item attributes, use the Purchasing Attributes component (PURCH_ITEM_ATTR). Use the PURCH_ITEM_ATTR_CI component interface to load data into the tables for this component.
If you have PeopleSoft Purchasing installed, you can use the Purchasing Attributes component to specify purchasing information for the items.
This section provides an overview of order multiple rounding rules and discusses how to:
Define purchasing item attributes.
Enter purchasing item specifications.
Define purchasing controls.
Define purchasing business unit attributes.
Define purchasing item vendor relationship attributes and priorities.
Define purchasing item vendor UOM and pricing information.
Enter item vendor UOM conversion rate changes.
Update purchase orders with item vendor UOM conversion rate changes.
In several industries like consumer goods and wholesale and distribution, for various economic and packaging reasons, suppliers will only ship certain items in multiples of a specific quantity. They can define the smallest quantity they are willing to ship for the item. Then when you create purchase orders to these suppliers you want a system that can utilize this information and calculates the rounding of the suggested order quantities to reflect the supplier’s specification to these suppliers.
PeopleSoft Purchasing gives you the ability to specify whether you want to have the system check for order multiples when you are ordering an item from a particular vendor and location on a purchase order. In addition, you can also specify the rounding rule you want to the system to use when its is calculating the correct order quantity multiple for this item on the purchase order. The two available rounding rules that you can choose are natural round and round up. Following are examples of the different types of rounding rules and there outcomes:
See the following table for quantity calculation examples using the different rounding rules:
Item |
Vendor |
Location |
Unit of Measure/Order Multiple |
Round Rule |
Order Quantity |
Suggested Order Quantity |
10005 |
SCM0000001 |
Main |
EA / 5 IP / 10 CS / 2 PT / 1 |
Natural Round |
14 EA |
15 EA |
10005 |
SCM0000001 |
Main |
EA / 5 IP / 10 CS / 2 PT / 1 |
Natural Round |
12 EA |
10 EA |
10005 |
SCM0000001 |
Main |
EA / 5 IP / 10 CS / 2 PT / 1 |
Round Up |
14 EA |
15 EA |
10005 |
SCM0000001 |
Main |
EA / 5 IP / 10 CS / 2 PT / 1 |
Round Up |
12 EA |
15 EA |
Access the Purchasing Attributes page.
PO Available Date, Unavailable (purchase order available date, unavailable) |
Indicate the dates within which the item can be added to a purchasing transaction. You can add an item between these two dates only. |
Standard Price |
Enter the standard price for the item purchased in its standard UOM. A standard price is required for each item and becomes the default price in transactions where another price, such as a vendor price or a contract price, is not defined for the item. An item's standard UOM is defined on the Item Definition - General: Common page. |
Standard Unit of Measure |
Displays the standard UOM used for pricing. The pricing UOM may be different from the stocking UOM. |
Last PO Price (last purchase order price) |
Displays the last price that was used on a purchase order for this item. When an item is initially set up, the standard price is also be the last price value. This field is updated by the Receiver Interface Push process (PO_RECVPUSH) and is used by the return-to-vendor transaction to cost the return and enable items to be returned to a vendor other than the original vendor of the order. |
Currency |
Select the currency of the standard price. |
Lead Time Days |
Displays the value appears by default from the Item Categories - Category Definition page. You can override the default value for individual items. |
Item Descr (item description) |
Enter a long description of the item up to 30 characters long. Enter a short description of the item up to 10 characters long. These descriptions can be used with PeopleSoft reporting and query tools instead of the standard 254-character description to distinguish the purchasing descriptions from the internally used item description established in the Item Definition component. These purchasing descriptions then also appear in the Description text box at the bottom of the page, where you can expand the descriptions to 254 characters. Whereas the long and short descriptions defined here are for internal use only, the description in the lower text box is used in all purchasing transactions and becomes available by selecting the description button or menu item on the PeopleSoft Purchasing pages. |
Asset Profile ID |
Displays the default from the Item Categories - Category Definition page. An asset profile ID on a purchase order, in conjunction with a PeopleSoft Asset Management business unit, indicates that PeopleSoft Asset Management is to be notified of the purchase of this item when it is received. |
Ultimate Use Code |
Select an ultimate use code to override the default tax rate for a location. In most cases, sales tax is computed as a use tax based on the tax code applicable to the ship to or usage destination. However, how merchandise is ultimately used may also result in a different tax rate within the same ship to or usage destination. |
Physical Nature |
Indicates whether an object is a physical good or service. |
Where Performed |
Select to indicate the location where the service is most often performed: Buyer's: Select if the service is physically performed at the buyer location. Ship From: Select if the service is physically performed at the ship from location. Ship To: Select if the service is physically performed at the ship to location. Supplier's: Select if the service is physically performed at the supplier's location. Note. This field is only available when you select a physical nature of Service. |
Primary Buyer |
Displays the default from the Item Categories - Category Definition page in the Define Item Control Data component. You can override the information for individual items. The primary buyer value is used as the default buyer when the item is added to a requisition. |
Associated Picture
The fields in this group box are used to attach image files or other documents to the item descriptions. You can attach any type of file that you have defined on the File Locations page. The file that you want to attach must reside in the file directory defined for the file type on the File Location page.
File Name |
Enter the name of the file that you want to attach. |
File Extension |
Enter the file extension, such as .bmp or .jpg. |
|
Click the Image Doc Launcher button to launch an attached file. This button is only available if you entered a file name and extension in the fields in the Associated Picture group box. |
See Also
Defining Purchasing Item Vendor UOM and Pricing Information
Defining Purchasing Item Categories
Access the Item Specifications page.
Item specifications that you enter on this page are not automatically carried to requisitions and purchase orders for the associated item unless you specify this by selecting the Copy to Transactions check box. If this check box is not selected, you must access the Include Item Specifications page to copy specifications on requisitions and purchase orders. Use the Include Item Specifications page to copy these specifications to the line comments for a transaction.
If you have selected Send to Vendor here, the Send to Vendor option on the Line Comments page for the transaction is automatically selected.
Comments |
Enter the specifications for the item using up to 2,000 characters. |
Copy to Transactions |
Select this check box to automatically copy the item specifications comments into the line comments when this item is referenced on a requisition or purchase order transaction. |
Send to Vendor |
Select this check box to make this specification information available to be sent to the vendor as part of the purchase order. |
Access the Purchasing Attributes - Purchasing Controls page.
Matching Controls
If you do not specify tolerance values for the business unit, the system uses tolerance values defined for the item's purchasing attributes.
The fields on this page match those on the Purchasing Business Unit Attributes page and the Purchasing Definition - Business Unit Options page.
Specify default price tolerances for the PeopleSoft Payables Matching process (AP_MATCH) that matches purchase orders, receipts, and vouchers to verify vendor charges. When you use matching with PeopleSoft Purchasing and PeopleSoft Payables to verify vendor charges, the system uses four price tolerances to determine whether the purchase order price and voucher price are within the tolerances and thus whether the purchase order and purchase order voucher match. These fields appear by default from the Item Categories - Category Definition 2 page. If you leave any of the tolerance fields set to 0 or blank, the system assumes a zero tolerance. If you don't want to use the tolerance fields, set the amount fields that you don't want to use to 9999999 and the percentage fields that you don't want to use to 100%.
Receiving Controls
Define tolerances to be used in receiving this item. These become the default values for purchase order lines when this item is selected. The values appear by default from the Item Categories - Category Definition 2 page.
If you do not specify tolerance values for the business unit, the system uses tolerance values defined for the item's purchasing attributes.
The fields on this page match those on the Purchasing Business Unit Attributes page and the Purchasing Definition - Business Unit Options page.
Include Past Due Kanban POs (include past due Kanban purchase orders) |
This field is available if you are using PeopleSoft Manufacturing, thus enabling you to receive by Kanban ID. Select this check box to include past-due Kanban purchase order quantities when the Receiver Load process searches for purchase orders to match up with Kanban IDs for receipt creation. If you select this check box, the Receiver Load process can receive a schedule whose due date has passed, but which still contains a quantity to be received. If you do not select this check box, the Receiver Load process searches for purchase orders based on the due date of the schedule. When using vendor replenishment with PeopleSoft Flow Production, select the Include Past Due Kanban POs check box to help ensure that the receipts and purchase orders have the opportunity to match up. Because vendor replenishment occurs frequently, if you set the Early Ship Reject Days value too low, the Kanban receiving process may not permit you to receive the material because it arrived too early. |
Inspect Sample Percent |
Enter the percentage of received units to inspect. This value is calculated using the Inspection UOM (inspection unit of measure) value. |
Sourcing Controls
Use Category Sourcing Controls |
Select this check box to use the sourcing controls set on the Item Categories - Category Definition 2 page. If you have set up vendors at the category level and select this check box for items using this category, then the vendors that you entered at the category must also be entered in the purchasing attributes. |
Misc. Controls and Options
Auto Select |
Select this check box if you want the AutoSelect Requisitions process (PO_REQSORC) to pick up the item when it sources requisition lines. If selected, the AutoSelect Requisitions process will include the item. If either of these conditions is not met, the AutoSelect Requisitions process will not include the item. |
Accept Any Vendor |
Select this check box if you can order an item without setting up vendors for the item. If you do not select this check box, you must establish an item-vendor relationship for the item on the Purchasing Attributes - Item Vendor page before you can include it on a purchase order. |
Accept Any Ship To |
Select this check box if you can order an item without setting up a ship to address for it. Note. This check box does not override the corresponding field set up for the item on the Purchasing Attributes - Item Vendor page. If you do not select the check box on either page, you must establish an item-vendor ship to relationship on the Item Ship To Locations page. |
Available in All Regions |
Select this check box if you want to bypass regional security. |
Contract Required |
Select this check box if you need a contract to order the item on a requisition or purchase order. If selected, you must specify a valid contract for the item on the purchase order when you use the item, or you must release the item from an active contract. |
RFQ Required (request for quote required) |
Select this check box if the item must go through the RFQ cycle before it can be included on a requisition or purchase order. If you do not select this check box, you can order the item directly. |
Stockless Item |
Select this check box if an agreement has been set up with the vendor to supply this item for par inventory replenishment. |
Close PO Under Qty Pct Tol (close purchase order under quantity percentage tolerance) |
Enter an acceptable percentage of the total quantity that can be outstanding while still enabling the purchase order to be closed. If the quantity not yet received is less than or equal to the valued entered, the PO RECON process will treat the purchase order as fully received. |
Ship Via |
Select a ship via method if you always want this item to be shipped using the method selected here. |
See Also
Defining Priority Vendors By Item Ship To Location
Defining Purchasing Item Vendor Relationship Attributes and Priorities
Understanding Purchase Order Reconciliation
Access the Purchasing Business Unit Attributes page.
If you do not specify tolerance values for the business unit, the system uses tolerance values defined for the item's purchasing attributes.
When you access this page to specify business-unit specific attributes, tolerance values appear by default from the item's purchasing attributes. To define zero tolerances on this page, you must manually clear the tolerance fields.
If you access this page, but do not enter any values and click OK to exit the page, the system records default tolerance values from the purchasing attributes to create business-unit specific values. Click Cancel instead to avoid this situation.
The fields on this page match those on the Purchasing Attributes - Purchasing Controls page and the Purchasing Definition - Business Unit Options page.
Access the Purchasing Attributes - Item Vendor page.
Vendor Priorities
Priority Loc (priority location) |
Select the ordering location for the item and vendor. The vendor default location appears by default. Several processes in PeopleSoft Purchasing use this field:
|
Vendor Attributes
Price Loc (price location) |
Select a vendor location. Vendor locations are set up on the Vendor Information - Location page. Location codes give you the flexibility to set up different pricing information for the same item-vendor combination, depending on which vendor location that you identify as the pricing location. |
Price Date |
Select the date used for effective-dated price adjustments: Due: Price adjustments based on the date the order was due to be received. PO (purchase order date): Price adjustments based on the date the order was placed. |
Price Qty (price quantity) |
Select a price quantity. Based on the selection, the system uses the Line or Schedule quantity to determine any applicable price breaks. |
Origin Country |
Select the country in which the item was originally manufactured. This information is generally required for the Intrastat Arrivals report; however, the PeopleSoft Intrastat Transaction Loader uses the field for return-to-vendor transactions (RTVs). If you leave the field blank, the transaction loader uses the country code of the shipping PeopleSoft Inventory business unit as the default value for RTVs. |
Region of Origin |
Select the region or department from which the item was initially shipped for return to vendor. This information is generally required for the Intrastat Dispatches report. If the initial shipping region or department for return to vendor is different than the one defined for the PeopleSoft Inventory business unit, enter a specific state code. The state code should belong to the country of the PeopleSoft Inventory business unit. If you leave the field blank, the Intrastat Transaction Loader uses the state code of the shipping PeopleSoft Inventory business unit as the default region of origin. This default value is also used if a state code does not belong to the country defined for the PeopleSoft Inventory business unit. |
Accept Any UOM (accept any unit of measure) |
Select this check box if this item can be ordered in any UOM from this vendor. If you do not select this check box, you must set up an item-vendor UOM relationship for each UOM in which the item can be purchased from the vendor. Note. This check box does not affect requisition processing. The system does not use this check box when displaying the available UOM's for an item on a requisition. |
Accept Any Ship To |
Select this check box if you want to receive the item from the vendor at any of the ship to locations. If you do not select this check box, you must establish an item-vendor ship to relationship on the Item Ship To Locations page. Note. This check box does not override the corresponding field set up for the item on the Purchasing Attributes - Item Vendor page. If you do not select the Accept Any Ship To check box on either page, you must establish an item-vendor ship to relationship on the Item Ship To Locations page. |
Stockless Item |
Select this check box if an agreement has been set up with the vendor to supply this item for par inventory replenishment. Note. If the Stockless Item check box was not selected for the item on the Purchasing Attributes - Purchasing Controls page, it won't be available at the item-vendor level on this page. |
Lead Time Days |
If you do not select the Use Item Standard Lead Time check box, this field is available for you to enter vendor-specific lead time values. |
Check Order Multiples |
Select this check box if you want to utilize order multiples for this item vendor and location. The system will check for order multiples for all the associated UOMs for this item vendor and location. |
Rounding Rule |
When utilizing order multiples specify the rounding rule you want the system to use so that calculations involving the item quantity ordered result in whole numbers. Options are:
|
See Also
Defining Priority Vendors By Item Ship To Location
Defining Purchasing Item Vendor Relationship Attributes and Priorities
Running the PO Calculations Process
Access the Vendor's UOM & Pricing Info page.
Unit Of Measure
Default |
Select a UOM in which the item can be purchased from the vendor. Select the Default check box to have the PO Calculations process use this UOM on the purchase order when this vendor is chosen to source this item to. When multiple UOMs are established for the item-vendor combination, users can select which UOM to use as the default. Select at least one. |
Min Qty, Max Qty (minimum quantity, maximum quantity) |
Enter the quantity limits for orders in the selected UOM. If you enter a requisition that does not fall within these quantities, you'll receive a warning. You do not receive an error because consolidation may bring the request within the defined limits. If the limits are not met when the request is processed by the PO Calculations process, you will receive an error. If you enter a purchase order that does not fall within these quantities, you'll receive an error and the system will use the standard UOM and item standard price. |
Order Quantity Multiple |
Enter the order quantity multiple for each item vendor and UOM. This field is utilized if you are using the order multiples functionality. A quantity of one appears by default. Note. The order multiple for the UOM will be applicable if the Qty Precision field value is Whole Nbr (whole number) only. |
Packing Details |
Click this link to access the Packing Details page. Use this page to enter packing volume and weight information for the item along with item package dimensions by vendor. |
Effective Dated UOM |
Click this link to access the Effective Dated UOM page. Use this page to enter effective-dated conversion rate changes along with packing detail information. |
Update PO |
Click the link to access the Update Purchase Order page. Use this page to update existing purchase orders with the new effective-dated UOM conversion rate changes. |
Conversion to Item Base UOM
If the vendor ordering UOM for the item is different from the item's standard UOM, specify how to convert the vendor UOM.
UOM Price Attributes
Qty Rcvd Tolerance % (quantity received tolerance percentage) |
Enter the quantity received tolerance percentage to be used in the receiving transactions for this item-vendor UOM combination. This field appears by default from the Purchasing Attributes - Purchasing Controls page. |
Standard Price Update Statusand BU Price Update Status (business unit price update status) |
Select from these options for updating standard prices, business unit standard prices, or both: No Update: Do not update prices. To Be Upd (to be updated): Price is updated on the date in the Eff Date (effective date) field. Note. If there are duplicate rows, the system uses these rules: If the effective dates are the same, the system checks the vendor priority. If multiple records are entered for the same vendor with the same effective date, the system selects the record with the standard UOM. Updated: Price has been applied. |
Matching Controls
Use Item Standard Tolerances |
Select this check box if you want to use the price tolerances established in the item's purchasing attributes. If not, specify the price tolerances in the tolerance fields provided. |
Access the Effective Dated UOM page.
Unit Of Measure
Effective Date |
Select the date when the new conversion rate become effective. The current date appears by default. |
Conversion Rate to Base UOM |
Enter the new conversion rate based on the base UOM. |
Update PO (update purchase order) |
Click this link to access the Update Purchase Order page. Use this page to update the existing purchase orders with the conversion rate change. |
Packing Details
Use all the fields in this section to specify the packing details for this effective date.
Other Information
OK |
When you click this button a message appears asking if you want to update the item vendor UOM with these changes. You can update the information or you can choose not to update the information. Note. When updating from this page, the Item Vendor UOM will be updated with the most current effective-dated UOM regardless of which effective date row is shown on this page. |
Access the Update Purchase Order page.
Search Criteria
You can access this page in a few different ways. If you access this page from the Vendor's UOM & Pricing Information page, most of the fields in the search criteria section of this page appear by default from that page. If you access this page from the Effective Dated UOM page, most of the fields in the search criteria section of this page appear by default from that page.
Effective Date |
The current date appears by default when this page is accessed from the Vendor's UOM & Pricing Information page. The effective date from the Effective Dated UOM page appears by default when this page is accessed from the Effective Dated UOM page. Select an effective date. |
PO Date Type |
Select the date type the system will use to retrieve the purchase orders for update. The system compares the effective date to the purchase order date type. Options are:
|
Search |
When you click this button the system displays in the Retrieved Rows group box all the purchase order schedules that match the search criteria entered. |
Retrieved Rows - PO Schedules
Sel |
Click this check box next to each purchase order schedule that you want to update with the new conversion rate change. Click the Select All link to select all the purchase order schedules. Click the Clear All link to clear all the purchase order schedules that you previously selected. |
PO ID (purchase order ID) |
Click this link to access the Maintain Purchase Order - Purchase Order page. Use this page to view and maintain the purchase order. |
Retrieved Rows - Detail
Select the Detail tab.
PO Conversion Rate |
Displays the existing purchase order conversion rate. |
New Conversion Rate |
Displays the new conversion rate that the system will use to update the purchase order schedules that you select. |
Other Buttons
Update Selected Rows |
When you click this button the system will recalculate the expected standard quantity and store the new conversion rate for all the selected purchaser order schedules. The new conversion rate that is used is from the most recent effective-dated row that appears on the Effective Dated UOM page compared against the effective date that you select in the search criteria. |
This section discusses how to update item vendor unit of measure conversion rates.
Page Name |
Object Name |
Navigation |
Usage |
PO_RUN_UPDIVUOM |
Items, Define Items and Attributes, Update Item Vendor UOM |
Initiate the Update Item Vendor UOM Application Engine process (PO_UPDIVUOM) which can update current and future item vendor unit of measure conversion rate changes. |
Access the Update Item Vendor UOM page.
Effective Date |
Select the effective date that you want to update the item vendor UOM conversion rate changes from. The item vendor UOM is updated with the most recent effective-dated UOM changes using the effective date you select on this page as the reference. The effective date you select on this page can be in the past, current, or in the future. Note. The timing for running this process is important. If the process runs after midnight, then you want to set the future conversion
rate date to the date the rate actually becomes effective. If it is run before midnight, you want to enter the future conversion
rate date as one day earlier. Alternatively, you can modify the selection criteria to select those where the effective date
is tomorrow. |
To define miscellaneous charges for item and category vendors, use the Item and Category Vendor Miscellaneous Charges component (ITM_CAT_VNDR_MC).
This section discusses how to assign miscellaneous charges and templates to items and categories.
Page Name |
Object Name |
Navigation |
Usage |
ITM_CAT_MC_CRITERA |
|
Enter the criteria for the miscellaneous charges that will appear on the Miscellaneous Charges - Miscellaneous page. |
|
ITM_CAT_VNDR_MC |
Click the OK button on the Miscellaneous Charges Selection page. |
Assign miscellaneous charges and miscellaneous charge templates to different item and category combinations. |
Access the Miscellaneous Charges - Miscellaneous page.
Category |
Select a value if you want to associate these miscellaneous charges with a category vendor business unit ship to location, category vendor business unit, category vendor combination, or category. Otherwise, leave the field blank. |
Item |
Select a value if you want to associate these miscellaneous charges with an item vendor business unit ship to location, item vendor business unit, item vendor combination, or item. Otherwise, leave the field blank. |
Vendor, Location, Ship To, Unit |
If you want to associate these miscellaneous charges with a combination that includes any of these fields, select a value for the field. |
Template ID |
To apply a template of miscellaneous charges, select the template ID. Miscellaneous charge templates are defined on the Misc Chg/Landed Cost Template (miscellaneous charge/landed cost template) page. |
Calc Method (calculation method) |
Select the method that you want to use to calculate this charge: FL (flat amount): A flat amount that you enter in the Amount field. FR (free): No charge applied. UNT (per unit amount): Calculates the charge based on the number of items on the purchase order line. VAL (percent of value): Calculates the charge based on a percentage of the material value. VOL (rate based on volume): Calculates the charge based on the total volume for the purchase order line. WT (rate based on weight): Calculates the charge based on the total weight for the purchase order line. |
Alloc Method (allocation method) |
Select the method to use to allocate the miscellaneous charge: None, Quantity,Volume, Weight, or Matl Value (material value). Charges are allocated based on the value of the items on each selected line. |
Merch Vendor (merchandise vendor) |
This check box setting appears by default from the miscellaneous charge's purchasing attributes on the Misc Charge/Landed Cost Defn page. If you select this check box, charges are paid to the purchase order vendor. If you do not select this check box, you can use the Vendor and vendor Location fields to designate a third-party vendor. |
See Also
Defining Miscellaneous Charges and Landed Costs
To set up vendor price adjustments, use the Price Adjustment component (PRICE_ADJUSTMENT).
This section provides an overview of item vendor price adjustments and discusses how to:
Define item vendor price adjustments.
Define item vendor price adjustment details.
With PeopleSoft Purchasing item vendor price adjustment features, you can define vendor price adjustments based on specific purchase order conditions, such as item quantity and ship to locations. The pricing schemes are ultimately used on purchase orders, where you can view the details of how a particular price was calculated.
You set up vendor price adjustments for items that have item-vendor relationships already established on the Purchasing Attributes - Item Vendor page. You can define as simple or as complex a pricing scheme as you need for each of the items. You can also define contract price adjustments on the PO Line Price Adjustment (purchase order line price adjustment) page and combine them with the vendor price adjustments to define specific contract pricing terms.
See Also
Defining Purchasing Item Vendor Relationship Attributes and Priorities
Entering Contract Purchase Order Line Price Adjustments
Page Name |
Object Name |
Navigation |
Usage |
PRICE_ADJUSTMENT |
Items, Define Items and Attributes, Price Adjustments, Price Adjustment |
Define the rules that the system should follow when calculating the vendor adjusted price from the vendor's base price. You can define effective-dated adjustment rule sequences for each item-vendor combination. |
|
PRICE_ADJUST_DTLS |
Items, Define Items and Attributes, Price Adjustments, Price Adjustment Details |
Define the quantities and adjustment methods for each of the price adjustment rules. |
Access the Price Adjustment page.
Calc Type (calculation type) |
For each adjustment rule, select one type of method by which adjustments will be calculated. Choose from: Increment Adjustments: Each valid adjustment is made against the current (base or adjusted) price. For example, if you have a base price of 100 and two percentage adjustments of -10 percent each, then the first adjustment is deducted from the base price of 100, for a current adjusted price of 90. The second adjustment of -10 percent is deducted from 90 for a final adjustment price of 81. Sum All Adjustments: Adjustments are summed and made against the original base price. For example, if you have a base price of 100 and two percentage adjustments of -10 percent each, the system takes the total adjustment of -20 and deducts it from the base price of 100 for a final adjusted price of 80. |
Seq (sequence) |
Enter the sequence number for each rule. Price adjustment rules are applied in ascending order. |
Dflt UOM (default unit of measure) |
Select this check box to use the default UOM for the item established on the Vendor's UOM & Pricing Info page. The system makes a default UOM adjustment when the UOM on the transaction is the same as the vendor default UOM or when the UOM on the transaction is not established for the item-vendor combination. |
UOM Match (unit of measure match) |
Select this check box to define an adjustment rule based on a specific UOM established for the item-vendor combination. |
UOM (unit of measure) |
If you selected the UOM Match check box, select the UOM that you want to use for adjustments. The item-vendor UOMs must first be established on the Vendor's UOM & Pricing Info page. |
Match Ship |
Select this check box to define an adjustment rule based on a specific ship to location code (setID/ship to) established for the item-vendor combination. |
SetID, Ship To |
Select the values if you selected the Match Ship check box. |
Hard |
Select this check box to indicate a hard price adjustment. This is an adjustment that the system uses to the exclusion of all other adjustments, even those with earlier sequence numbers. |
Stop Price |
Select this check box to indicate a final price adjustment. No further adjustments can be made after the system applies this adjustment. |
Ignore Flg (ignore flag) |
Select this check box to create a price adjustment scenario in which this price adjustment is ignored if the order qualifies for another adjustment. If no other adjustment applies, this adjustment will apply even if the Ignore Flg check box is selected. Suppose you have the following price adjustment conditions for an item: Apply a hard 10 percent discount if the UOM matches. Apply a 100 USD discount, but ignore this if another adjustment applies. The Ignore Flg is selected for this adjustment. If you order the item in the matching UOM, the 10 percent discount is applied and the 100 USD discount is ignored, according to the selected Ignore Flg option. If you order the item in a non-matching UOM, you qualify only for the 100 USD discount. Because this is the only adjustment that applies, the adjustment can be applied. |
See Also
Defining Purchasing Item Vendor Relationship Attributes and Priorities
Access the Price Adjustment Details page.
Copy Price Adj. Qty (copy price adjustment quantity) |
Click this link to define the same price break quantities for multiple adjustment details. Define the quantities for a location on the Price Adjustment Details page, then access the Price Adjustment page and insert a new row in the Adjustment by UOM scroll area. Return to the Price Adjustment Details page, access the newly inserted detail row, and click this link to copy the adjustment quantities from the previous definition to the new definition. |
Min Qty/Max Qty (minimum quantity/maximum quantity) |
Enter the minimum purchase order quantity allowed for this price. When you insert a new range, the minimum quantity for the new range defaults to the maximum quantity of the old range plus one. |
Adjusted Price |
Enter the adjusted price that you want. The adjustment amount/percent is automatically calculated and appears. Note. This column is provided for informational purposes only. If you have multiple adjustments for a particular transaction, the final adjusted price will not equal any of the adjusted prices calculated for the adjustment rules. The adjusted price provides an idea of what would happen if only the single adjustment was applied. |
This section provides overviews of price updates and the Price Update process and discusses how to:
Use standard price and business unit standard price updating online.
Use standard price and business unit price batch updating.
Run the Price Update Process.
You can also update future effective-dated prices by running an application engine process.
Note. You can use Item Catalog Maintenance to update item data for multiple items at one time by extracting them from the production tables into the item staging tables where you can then alter the data.
See Also
Using Item Catalog Maintenance
Your PeopleSoft system may have multiple prices for an item, including the item's standard price, item/vendor price, and standard price by business units. In addition, if a contract is in place for an item, contract pricing may override other prices. At times you may need to update prices in multiple places to keep information current when prices change and to prevent errors during the PO Build process.
The price update feature enables you to implement price changes by:
Automatically updating an item's standard price whenever an item/vendor price with a current effective date is updated using the Vendor's UOM & Pricing Info page.
Updating the item's standard price based on an Item/Vendor price that was entered in the past for an upcoming effective date.
After the future effective-dated prices are entered, and the Price Update process is run on or after the date that the Item/Vendor price becomes effective, the item's standard price is updated to reflect the new item/vendor pricing.
Automatically updating an item's business unit standard price whenever an item/vendor price is updated using the Vendor's UOM & Pricing Info page.
Updating the item's business unit standard price based on an Item/Vendor price that was future effective-dated at the time that it was entered.
After the future effective-dated prices are entered, and the Price Update process is run on or after the date the price becomes effective, the item's standard price is updated to reflect the new item/vendor pricing.
Updating standard prices with the current effective item/vendor prices and business unit standard prices that are loaded through the Item Loader.
Note. Changing an item's contract price does not automatically trigger changes to item/vendor pricing or item standard prices. Contract pricing is a special pricing for purchases meeting specific criteria. Not all purchases may qualify for contract pricing; therefore, the contract price does not exist on the item definition. The system automatically assigns a contract to a purchase order when the criteria are met.
See Also
The Price Update process scans the Item/Vendor tables for dates that have become effective and calculates the new standard price or business unit standard price based on the price entered for that effective date on the Vendor's UOM & Pricing Info page. It also scans for prices that have been loaded into the system with the Item Loader.
You must run the Price Update process to pick up any future effective-dated prices that have become effective and to calculate the new prices. You can also use this page to update a price that is currently effective or to update a price that is effective within a range of dates.
You must choose to use either the current date or date range. If you select the Date Range option, you must select a range of dates. The process compares the Item/Vendor Price record's effective date to the current date or the date range to determine if the price is in effect. The process applies updates in the order of effective date, applying the most current effective date as the end result.
You will probably want to schedule the Price Update process to run regularly if the system includes many price changes.
To update standard prices and business unit standard prices online:
Enter the Vendor's UOM & Pricing Info page for the item and vendor that must be updated.
Change the pricing on the current row in the UOM Attributes group box or insert a new row with a new price.
Note. In order to prompt the automatic price change feature, the row selected for the price change cannot have a status of Inactive. If the row is inactive, an error message appears when the changes are saved.
Select To Be Upd (to be updated) in the Standard Price Update Status field to apply the price change to the item's standard price on the Purchasing Attributes - Purchasing Attributes page.
Select ToBe Upd (to be updated) in the BU Price Update Status field to apply there price change to the standard prices by PeopleSoft Purchasing business unit.
You must also select the Update Business Unit Price check box on the Purchasing Business Unit Attributes page because the business unit is not specified on the Vendor's UOM & Pricing Info page.
Note. To use the price as a reference, or use another vendor price, for example, you can select No Update instead of To Be Upd.
Verify that you have selected only one item/vendor price to update the item's standard prices.
If multiple item/vendor prices are selected when the item changes are saved, the system will prompt the user to proceed with the new selected item/vendor price or keep the previous selected price.
Click the OK button on the Vendor's UOM & Pricing Info page.
Save the Purchasing Attributes - Item Vendor page.
The system updates the standard prices as follows:
If you selected To Be Upd (to be updated) in the Standard Price Update Status field, and the new price is effective currently, the new price appears in the Standard Price field of the Purchasing Attributes - Purchasing Attributes page.
When the price is updated, the value in the Standard Price Update Status field on the Vendor's UOM & Pricing Info page will default to Updated.
If necessary, the UOM and currency of the item/vendor price are converted from the vendor UOM and currency code to the standard UOM and currency code located on the Purchasing Attributes - Purchasing Attributes page.
If you selected To Be Upd (to be updated) in the BU Price Update Status field, and the price is effective currently, all business units that match the setID/item combination and that have the Business Unit Update Price check box selected on the Purchasing Business Unit Attributes page will have the new price applied.
When the price is updated, the value in the BU Price Update Status field on the Vendor's UOM & Pricing Info page will default to Updated.
If necessary, the UOM and currency of the item/vendor price are converted from the vendor UOM and currency code to the standard UOM and currency code located on the Purchasing Attributes - Purchasing Attributes page.
Any future effective-dated prices will take effect once the Price Update process has run on or after the effective date.
Note. To convert the item/vendor UOM to the item's standard UOM, the vendor override conversion factor is used (if one exists). When no vendor override exists, the conversion factor for the Inventory Item UOM setup process is used (INV_ITEM_UOM). If that conversion rate does not exist, the Units of Measure page is used to determine the conversion factor. If there is no row on the Units of Measure page that coincides with the item/vendor UOM (from UOM) and the item standard UOM (to UOM), an error message appears.
Note. To convert the item/vendor currency to the item's standard currency, the CUR_RT_TBL record is used to determine the conversion factor. If there is no row on this record that coincides with the item/vendor currency code (from currency code) and the item standard currency code (to currency code), an error message appears.
To update standard prices with data entered using the Item Loader:
Select the items that you want to update in the Item Loader.
Access the Item Loader page.
In the Item Load Type field, select Item Pricelist.
This processes item data staged with the Item Price List EIP message, ITEM_PRICELIST_LOAD.
Select Update Standard Price to update the item standard price when a currently effective item/vendor UOM price record is loaded, and set the Standard Price Update Status to To Be Upd for the future effective-dated records.
Select Update Business Unit Price to update business unit standard prices when a currently effective item/vendor UOM price record is loaded, and set the BU Price Update status to To Be Upd for the future effective-dated records.
To update business unit prices, you must also select the Update Business Unit Price check box for all items on the Purchasing Business Unit Attributes page.
Mark items on the Purchasing Business Unit Attributes page for standard price updating at the business unit level.
Select the Update Business Unit Price check box and click the OK button to save the changes.
When updating with prices loaded using the Item Loader, this step enables business units that match the setID/item combination to have the new price applied.
For any future effective-dated prices, run the Price Update process on or after the effective dates.
Access the Price Update page.
Use the page controls to select criteria for the price updates.
The Price Update process scans the Item/Vendor tables for dates that have become effective and calculates the new standard price based on the price entered for that effective date on the item/vendor UOM price entered with the Item Loader.
See Also
Access the Price Update page.
You can use the filter controls on this page to limit the prices to be updated.
Date Range
As of Date |
Select to process prices that are currently effective. |
Date Range |
Select to process prices that are in effect within the range that you specify in the Date From/Date To fields. |
To define item ship to locations, use the Item ShipTo Locations component (ITM_SHIPTO_VNDR). Use the ITM_SHIPTO_VNDR_CI component interface to load data into the staging tables for this component.
This section discusses how to define priority vendors for specific item/ship to location combinations.
Note. The PO Calculations process selects a vendor for an item/ship to location combination based on the definition on this page (if the Override Suggested Vendor option is selected on the Sourcing Controls page).
Page Name |
Object Name |
Navigation |
Usage |
ITM_SHIPTO_VNDR |
Items, Define Items and Attributes, Item Ship To Locations |
Set up a prioritized list of vendors and vendor locations for a particular item and ship to location combination. |
Access the Item Ship To Locations page.
ShipTo SetID, Ship To |
Select each shipping location that you're defining for the item. Ship to location codes are established on the Ship To Locations page. |
Include in Planning |
Select this check box to enable purchase options to be created in PeopleSoft Supply Planning for the PeopleSoft Inventory business unit related to this ship to location. The purchase option then enables the creation of new purchase orders through PeopleSoft Supply Planning for this PeopleSoft Inventory business unit. If this check box is not selected at the item-ship to level, it will not be available at the item ship to vendor level on the grid. |
Vendor |
Select a vendor. Available vendors are those for which item vendor relationships have been established on the Purchasing Attributes - Item Vendor page. |
See Also
Defining Purchasing Item Vendor Relationship Attributes and Priorities
Defining Priority Vendors By Item Ship To Location
To define purchasing kits, use the Purchasing Kit component (ITM_CONFIG_TBL).
This section provides an overview of purchasing kits and lists the page used to create purchasing kits.
A purchasing kit is a set of components that comprise two or more items. Purchasing kits contain items and quantities that are often ordered together.
When you enter a requisition or purchase order, you can order by purchasing kit ID to capture all items and quantities in the kit instead of entering each item and quantity separately.
When you enter a purchasing kit ID on a transaction line, the system creates a separate line for each of the kit's component items. The quantity of each line item defaults to the quantity of that item per kit multiplied by the number of kits that you order. For example, if a kit includes one CD-ROM drive and two speakers and you order two kits, the system generates a line for the CD-ROM drive with a quantity of two and a line for the speakers with a quantity of four.
The account and alternate account you define on the purchasing kit definition will appear on the requisition distribution line when you associate a purchasing kit with a requisition.
Page Name |
Object Name |
Navigation |
Usage |
PURCH_KIT_TBL |
Items, Define Items and Attributes, Purchasing Kit Definition |
Define purchasing kits. |