This chapter provides an overview of procurement options and discusses how to:
Define miscellaneous charges and landed costs.
Define miscellaneous charges and landed cost templates.
Define SpeedCharts.
Define payment terms.
Establish additional payment processing options.
Define late interest charges.
Define credit card issuers.
Define vendor freight groups.
Define ship to locations.
Define origin codes.
Prepare to dispatch by fax and email.
Define inspection procedures.
Define manufacturer IDs.
Establish model relationships to manufacturers.
Set up standard comments.
Define account receivables integration options for vendor rebates.
Create requisition change order templates.
Create purchase order change order templates.
Define change map templates.
Define buyers.
Define requesters.
Use Requisition Loader defaults and overrides.
Use purchase order Loader defaults and overrides.
Define contract control parameters.
Set up tax vendor product codes cross reference.
Define vendor control parameters.
Define vendor pay group codes.
Define vendor conversation keywords.
(USA) Enter vendor government certifications.
Establish matching and document association options.
Specify voucher build criteria.
Define document tolerances.
To define bank replacement rules, use the Bank Replacement Rules component (BANK_RPL_RULE_DEFN).
In addition to the tables that all PeopleSoft applications share, there are tables specific to PeopleSoft Payables and PeopleSoft Purchasing that form the foundation of the procurement system. Before you begin entering requisitions, purchase orders, or vouchers, you need to configure these tables to define the accounts payable and purchasing environments. Use the pages described in this chapter to configure these tables. Most of these pages can be found in the Set Up Financials/Supply Chain, Product Related, Procurement Options menu.
This chapter does not discuss all of the components found in that menu, however. The following table lists the procurement option components and pages that we discuss in the PeopleSoft Payables PeopleBook:
Component |
Page Names |
Chapter |
|
See Processing Drafts. |
|
AP Aging Cycle |
||
Bank Replacement Rule |
||
Draft Sight Codes |
See Processing Drafts. |
|
Reschedule Payments |
||
|
||
All within the Withholding menu. |
All pages |
|
All within the Reports menu. |
All pages |
See Payables Reports. |
Regional Financial Code |
||
Payment Schedule Restrictions |
||
Spending Region Install Option Spending Region Definition |
To define miscellaneous charges and landed costs, use the Misc Charge/Landed Cost Defn component (miscellaneous charge and landed cost definition component) (CM_LC_COMPONENT).
This section discusses how to define miscellaneous charges and landed costs.
See Also
Defining Miscellaneous Charges and Landed Costs
Access the Misc Charge/Landed Cost Defn page.
Landed Cost Component Info
Cost Element |
Select a cost element for the miscellaneous charge. A cost element is a type of cost such as freight or handling costs. |
Landed Cost Group |
Select the landed cost group to which this miscellaneous charge belongs. Landed cost groups are defined on the Misc Chg/Landed Cost Template page. |
% Ext Amount Tolerance (percent extended amount tolerance) |
Select a total amount tolerance percentage. The tolerance amount is used to automatically close purchase orders and receipts for landed costs if the invoice amount is within tolerance of the purchase order amount. |
Qty Rcvd Tolerance % (quantity received tolerance percent) |
Select a percent tolerance for received quantities. The tolerance is used to automatically close purchase orders and receipts for landed costs if the invoice quantity is within tolerance of the purchase order. |
Accrue Charge |
Select if the miscellaneous charge is to be included in inventory value at putaway. If this check box is cleared, the charge is expensed upon invoicing. |
See Also
Defining Miscellaneous Charges and Landed Costs
To define miscellaneous charge and landed cost templates, use the Misc Chg/Landed Cost Template component (miscellaneous charge and landed cost template component) (CM_LC_TEMPLATE).
This section discusses how to define miscellaneous charge and landed cost templates.
See Also
Defining Miscellaneous Charges and Landed Costs
To define SpeedCharts, use the SpeedChart component (SPEEDCHART).
This section provides an overview of SpeedCharts and discusses how to:
Define SpeedCharts.
Use multiple SpeedCharts with requisitions.
Enter multiple SpeedCharts on requisitions.
Use multiple SpeedCharts with purchase orders.
Enter multiple SpeedCharts on purchase orders.
SpeedCharts greatly increase data entry efficiency by reducing the number of keystrokes required to enter frequently used ChartField combinations. SpeedChart codes can be defined with multiple accounting distributions and are used by entering the SpeedChart code during data entry instead of the individual ChartField combinations.
The system automatically prorates accounting line amounts according to the proration percentages defined on the SpeedChart. You can define a skeleton SpeedChart where the total percentage is zero if you need to enter requisitions, purchase orders, or vouchers where the ChartField values are constant but the accounting line amounts vary.
For example, suppose that all departments in the organization use express mailing services, but the actual charge for any one department varies from month-to-month. In this case, a specific percentage does not apply to each distribution accounting line. When you use this type of SpeedChart, during data entry you supply the accounting line amounts. When needed, you can define SpeedCharts based on an item's unit of measurement weight rather than by percentage.
As another example, suppose that you set up a SpeedChart to define a distribution for equipment upgrade expenses so that each department is billed a percentage of the total amount. The system automatically prorates distribution line amounts according to the proration percentages defined on the SpeedChart. The distribution line with the largest amount receives any remainder caused by rounding the distributions. Once you set up the SpeedCharts, you can generate a report that displays information about the SpeedCharts.
It is important to understand the difference between PeopleSoft SpeedCharts and PeopleSoft SpeedTypes. PeopleSoft SpeedCharts enable you to group together and name an unlimited number of ChartField combinations, while PeopleSoft SpeedTypes enable you to assign a code to a single ChartField combination.
Vouchers, purchase orders, and requisitions use accounting information from the control hierarchy. This information is ignored when you use SpeedCharts.
See Also
PeopleSoft Source to Settle Common Information Reports
Multiple SpeedChart functionality provides you with the ability to choose whether you want to override or append multiple SpeedCharts to existing ChartField values; existing single SpeedChart functionality always overwrites existing ChartField values. Use Multiple SpeedChart to automatically calculate distribution quantities, amounts, and percentages regardless of the selected distribution method; existing single SpeedChart functionality does not automatically calculate these values when distributing by quantity.
Page Name |
Object Name |
Navigation |
Usage |
SPEEDCHART |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Management, SpeedChart, SpeedChart |
Define SpeedChart codes for frequently used ChartField combinations to increase data input efficiency by reducing the number of keystrokes. |
|
REQ_SCHEDULE |
Purchasing, Requisitions, Add/Update Requisitions, Schedule |
Specify multiple shipping schedules for each requisition line and define multiple distributions for each schedule. |
|
REQ_DISTRIB_DETAIL |
Click the Distribution link on the Maintain Requisitions - Schedule page. |
Enter distribution details for each requisition schedule. Define accounting distributions for each schedule. Assign internal delivery location, asset, project, and inventory information to distributions. |
|
PO_SCHEDULE |
Purchasing, Purchase Orders, Add/Update Purchase Orders, Schedule |
Specify ship to locations, quantities, due dates, comments, sales and use tax amount, miscellaneous charges, price adjustments, and multiple distributions to purchase order schedules. |
|
PO_SCHED_DISTRIB |
Click the Distributions link from the Maintain Purchase Orders - Schedule page. |
Define multiple distributions for a purchase order schedule. |
|
RUN_POSPCHARTS_OL |
Click the Multi-SpeedCharts link on the Distributions page. |
Assign multiple SpeedCharts to a single purchase order schedule to create applicable distribution lines. |
Access the SpeedChart page.
Total Percent |
Indicates the total of the proration percentages that you selected for the SpeedChart lines. |
Security Option
Universal (All Users) |
Select to make a SpeedChart available to all users. |
One User |
Select to make a SpeedChart available to one user. When you select this option, enter a value in the adjacent field. |
Permission |
Select a permission level that users need to have to access the designated SpeedChart. When you select this option, enter a value in the adjacent field. |
Note. You must enter at least two ChartField distributions unless you use the Universal user, in which case you can enter a single ChartField distribution.
Definition
Enter Percentages |
Select to distribute cost by a percentage of the total amount. When you select this option, enter a proration percent value for each SpeedChart line. |
Enter Weights |
Select to distribute cost by item unit of measurement weight. When you select this option, enter a proration weight value for each SpeedChart line. |
UOM (unit of measurement) |
Select a unit of measurement for distributing cost by weight. |
Access the Distribution Information page.
Open Qty (open quantity) |
If the Distribute by option is set to Qty, displays the quantity on the schedule available to be sourced to a purchase order. |
Open Amt (open amount) |
If the Distribute by option is set to Amt, displays the amount on the schedule available to be sourced to a purchase order. |
Multi-SpeedCharts |
Click to access the Multiple SpeedCharts page, where you can assign multiple SpeedCharts to a single requisition schedule. |
See Also
Entering Distribution Information
Access the Multiple SpeedCharts page.
Note. The field labels and values on this page adjust depending on the field value in the Distribute by field. If the field value is set to Quantity, fields reflect quantity-based values. If the field value is set to Amount, fields reflect amount-based values.
Distribute by |
Displays according to the Distribute by option selected on the Distribution Information page. Values are: Quantity: If the requisition distribution is distributed by quantity and the distribution is associated with an inventory item with applicable rounding rules, the distributed quantity is rounded to whole numbers. The quantity in the last distribution line generated for the SpeedChart may be a decimal or a whole number. If the distribution is not associated with an inventory item with applicable rounding rules, the quantity may be distributed as decimals or whole numbers. Amount: If the requisition distribution is distributed by amount, the amount may be distributed as decimals or whole numbers. |
Req Qty (requisition quantity) |
If the Distribute by option is set to Quantity, displays the requisition schedule quantity. |
Amount |
If the Distribute by option is set to Amount, displays the requisition schedule amount. |
Remaining Amount |
If the Distribute by option is set to Amount, displays the requisition schedule amount remaining to be distributed. This is the Amount value less the sum of distributed amounts on the Distribution Information page and Multiple SpeedCharts page. |
SpeedChart |
Enter a SpeedChart value. You cannot enter duplicate SpeedChart values on this page. |
Quantity to Distribute |
If the Distribute by option is set to Quantity, enter the quantity you want to distribute using the selected SpeedChart. |
Amount to Distribute |
If the Distribute by option is set to Amount, enter the amount you want to distribute using the selected SpeedChart. You can have the system automatically calculate SpeedChart distribution quantities and amounts, manually enter values, or use a combination of these options. If you do not specify an associated quantity or amount in the Quantity to Distribute or Amount to Distribute field, the system populates distributions with ChartField values based on the selected SpeedChart and sets the distribution quantities, amounts, and percentages on the Distribution Information page to zero. This enables you to manually enter the data. If you enter an associated quantity or amount, the system populates distributions with ChartFields values based on the selected SpeedChart and automatically calculates and populates the distribution quantities, amounts, and percentages on the Distribution Information page. When you enter a SpeedChart and an associated quantity or amount for distribution, the system validates the quantity or amount entered. You cannot select the Append process option and enter a quantity or amount that is greater than the original remaining quantity or amount for the schedule. You cannot select the Overwrite process option and enter a quantity or amount that is greater than the quantity or amount for the schedule. |
SpeedChart Process Options
Append |
Select to have the SpeedChart selections added to existing distributions. If selected, you can enter a total Quantity to Distribute or Amount to Distribute value up to the original remaining quantity or amount. |
Overwrite |
Select to have the SpeedChart selections overwrite existing distributions. If selected, you can enter a total Quantity to Distribute or Amount to Distribute value up to the requisition schedule quantity or amount. |
Access the Distribution page.
Multi-SpeedCharts |
Click to access the Multiple SpeedCharts page, where you can assign multiple SpeedCharts to a single purchase order schedule. |
See Also
Creating Purchase Order Distributions
Access the Multiple SpeedCharts page.
Note. The field labels and values on this page adjust depending on the field value in the Distribute by field. If the field value is set to Quantity, fields reflect quantity-based values. If the field value is set to Amount, fields reflect amount-based values.
To define payment terms, use the following components:
Payment Terms Timing Codes (PYMT_TERMS_TIMING).
Payment Terms - Single Payment (PYMT_TERMS_SINGLE)
Payment Terms - Multi Payment (PYMT_TERMS_MULTI)
This section provides on overview of payment terms and discusses how to:
Define payment terms timing codes.
View payment terms by timing code.
Calculate example payment due dates.
Define single payment terms.
View multipayment terms that use a single payment term.
Define multipayment terms.
Calculate example payment data for a payment term.
View installment details for a multipayment installment.
Payment terms are used to calculate net due date, discount due date, and discount amount calculations. You need to define the payment terms and timing methods that the system uses for vendor payments. The system supports percentage and fixed amount discount calculations. Payables uses these payment terms and timing methods to schedule payments for invoices and to calculate amounts remitted to vendors.
You can establish separate payment terms for single and multiple payments. Before you can establish the actual payment terms, however, you must define a payment terms timing for each time frame that you reference in the payments. You do this on the Payment Terms Timing Codes page. Once you have established timing codes, you can set up payment terms for single payments. Timing codes are directly referenced in single payment terms and must be defined as a prerequisite to defining single payment terms. Single payment terms are directly referenced in multiple payment terms, and likewise must be defined first.
Page Name |
Object Name |
Navigation |
Usage |
PYMT_TERMS_TIMING |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Payments, Payment Terms Timing Codes, Payment Terms Timing Codes |
Define payment terms timing codes for each time frame that you reference in the payments. These codes define the number of days or months that must be added to the basis date to calculate the scheduled pay date. |
|
TIMING_WHERE_USED |
Click the Search Where Used link on the Payment Terms Timing Codes page. |
View payment terms that use the timing ID. |
|
TIMING_CLC_DUE_DTS |
Click the Calculate Example Due Dates link on the Payment Terms Timing Codes page. |
Calculate the payment due date for the timing ID, based on the basis date that you enter. |
|
PYMT_TERMS_SINGLE |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Payments, Payment Terms - Single Payment, Payment Terms - Single Payment |
Define valid payment terms for single payments. You enter payment terms using payment terms timing codes. You must have already defined at least one payment terms timing ID on the Payment Terms Timing Codes page. |
|
SNGL_TRMS_WHR_USED |
Click the Search Where Used link on the Payment Terms - Single Payment page. |
View the multipayment terms IDs that uses the selected single payment terms ID. |
|
PYMT_TERMS_MULTI |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Payments, Payment Terms - Multi Payment, Payment Terms - Multi Payment |
Define multipayment terms by grouping single payment terms for payments split into multiple payments or installments. You enter multiple payment terms using two or more single payment terms. You must have already defined payment terms timing codes and single-payment terms. |
|
MLT_TR_CLC_PAY_DTA SNG_TR_CLC_PAY_DTA, |
Click the Calculate Example Payment Data link on the Payment Terms - Single Payment page or the Payment Terms - Multi Payment page. |
Calculate example payment data for the Payment Terms ID based on currency, gross amount or basis amount, and basis date. This enables you to perform a what-if examination of the effect of various parameter settings on the calculated result, before you save a particular term's definition. |
|
EXMN_INST_DETAIL |
Click the Examine Installment Detail button on the Calculate Example Payment Data page that you access from the Payment Terms - Multi Payment page. |
View single payment data for scheduled multipayment installments based on gross amount, discount, and basis date parameters. |
Access the Payment Terms Timing Codes page.
Use the Timing Basis Option and Timing Adjustment group boxes to specify timing options. The Timing Basis Option group box enables you to select a basic calculation approach. The Timing Adjustment group box enables you to fine tune this approach by adding or subtracting a fixed number of days, months, or years.
PeopleSoft supports these timing methods:
Add days to the basis date.
Select the timing basis option of None (Basis Date) and set the day increment counter to the number of days that you want to add. A variety of user-determined basis dates, such as the invoice date, are supported. You define these basis dates when you set up the Payables control hierarchy, and can override them on the voucher. In the example above, the timing code is defined as 10 days after the basis date.
Add days and number of months to the basis date.
Select the timing basis option of None (Basis Date) and set the day increment and month increment counters to the number of days and months that you want to add.
Due on a specific day relative to the month.
Select the timing basis option of End of Relative Month. Leave the counter at zero if the payment is to be made at the end of the month. Entering a value in the End of Relative Month field changes the month that is used. Entering a value in the Day Increment field adds days. For example, if you set the End of Relative Month counter to -1 (designating the end of prior month) and enter 10 in the Day Increment field, a basis date of 7/26/00 gives you a due date of 7/10/00. The field values tell the application to calculate the due date by returning to the end of the previous month and adding 10 days.
Due on a specific day.
Select Fixed Month/Day Values and select the month due and day due. The Day Due option enables you to specify, for example, end-of-quarter dates such as 03/31, without fixing the particular year value.
Due on a specific date.
Select Specific Due Date and enter the date.
Example of Using Timing IDs to Define Payment Terms
Suppose that you want to create timing IDs for the standard payment terms of 2 percent, 10 days, and net 30 days. First, establish a timing ID of 10 days, with a day increment of 10 days, and a timing ID of 30 days with a day increment of 30 days. Then, use these two timing IDs when defining the actual payment terms.
Or, suppose that you want to create a timing ID for payments due on the 15th day of the month. For this timing ID, select End of Relative Month as the timing basis option and set the counter to -1 to indicate the last day of the prior month as the start day to which the relative day value of 15 is added. This ensures that the resulting date falls within the current month. Then, enter 15 in the Day Increment field.
Access the Payment Terms Timing Codes - Search Where Used page.
Net Terms Occurrences |
Displays the number of times that the timing ID is used within the net calculation of the payment terms ID. This value is greater than one if the terms are split and a timing ID is used more than once. This is more likely to occur in the discount calculation than in the net. |
Discount Terms Occurrences |
Displays the number of times that the timing ID is used within the discount calculation of the payment terms ID. |
Access the Payment Terms Timing Codes - Calculate Example Due Dates page.
Basis Date |
Select the timing calculation basis date. The default value is the current date. |
Click the Calculate Due Date button to calculate the due date. The system calculates the due date and populates the Due Date field. |
|
Due Date |
Displays the due date calculated based on the timing ID specified on the Payment Terms Timing Codes page and the basis date value. |
Access the Payment Terms - Single Payment page.
Payment Terms Control
Terms Applicability |
Describes the customers or vendors to which these payment terms apply. |
Split Net Terms |
Select to define payment terms that contain multiple net terms and any associated discounts. This allows for a variable due date depending on the invoice date. For example, select this option to use one timing ID if the basis date is between the 1st and 15th, and another timing ID if the basis date is between the 16th and end of the month. Split terms definitions enable you to set up variable net due date terms. There are terms that, depending on the basis date, result in more than one possible set of net or discount due dates. Note. The split payment terms functionality cannot calculate staggered discount payments, which are graduated discounts that are based on a certain number of days past the invoice date (for example, a 2% discount when paid within seven days, then a 1% discount when paid within fourteen days, then zero discount when paid within thirty days). |
Number of Terms |
Indicates the number of terms that apply to this single payment term. This field is available when you select the Split Net Terms check box. |
Net Due Terms
Basis From Day |
Indicates the beginning day of the basis day range. The basis date's day value must be equal to or greater than this day, or the terms definition does not apply. This field is available when you select the Split Net Terms option. |
Basis To Day |
Indicates the ending day of the basis day range. The basis date's day value must be equal to or less than this day, or the terms definition does not apply. This field is available when you select the Split Net Terms option. |
Note. All available days, 1 to 31, must be accounted for in the basis from day and basis to day range.
Timing ID |
Displays the timing ID used to calculate the net payment due date for this day range within the single payment term. |
Rebate Term Available |
Select if the terms you are defining include rebate terms. Rebate terms are calculated as: Days payment precedes due date * Daily rebate percentage, not to exceed a maximum percentage of the amount due. There are special edits performed when you enter vouchers with rebate terms. |
Daily Rebate Percent |
Enter the daily rebate percentage to be applied to the days the payment precedes the due date. |
Maximum Rebate Percent |
Enter the maximum percentage of the amount due that is available as a rebate. |
Discount Terms Available |
Select if the terms that you are defining include discount terms. |
Discount Terms
Timing ID |
Displays the timing ID used for the discount portion of this single payment term. |
Adjustment Days |
Displays the number of days used to adjust the discount due date for this single payment term. Use this field to define flexible discount terms by specifying either "basis date relative" or "due date relative" discount due dates. This is useful if the discount terms are often calculated as, for example, 2 percent for the first 10 days following the start-of-terms (basis) date, or 2 percent up to 10 days before the payment due date. |
Discount Terms Percent |
Displays the discount percent that is applied to the invoice gross amount to calculate the discount amount. |
Note. The discount is less nonmerchandise charges, freight, miscellaneous charges, and sales tax. In a value-added tax (VAT) environment, you may configure the system to include VAT in the amount upon which the discount is calculated.
Discount Terms Amount |
Displays the flat amount discount that is applied to the invoice. Entering a value in this field causes a constant amount to be used for the discount regardless of the invoice amount. The discount terms amount value is applied using the transaction currency units defined for the voucher. The particular currency to use is not defined here, but is determined by context. |
Access the Payment Terms - Single Payment page - Search Where Used page.
Multi-Payment Terms ID |
Displays the multipayment terms IDs that include the single payment terms you are searching on. |
Number of Terms |
Displays the number of installments contained within the multipayment terms ID. |
Number of Occurrences |
Displays the number of times that this payment terms ID is used within the multipayment terms. |
Access the Payment Terms - Multi Payment page.
Payment Terms Control
Terms Applicability |
Describes the entities to which these payment terms apply. For example, the value in this field can tell you if the terms apply to the vendor, the customer, or both. |
Number of Installments |
Displays the number of installments for the multipayment terms. |
Installment Terms
Use the Installment Terms grid to determine the installment terms. The calculated due date for each installment becomes the basis date for the next sequential installment.
Single Terms ID (single payment terms ID) |
Specify the single payment terms ID for each installment. |
Installment Percent |
Change the installment percentage. The system initially calculates the installment percentage based on the number of installments that you specify. For example, if you set the number of installments to 2, the system inserts two rows in the installment terms grid and sets the installment percent for each row to 50.000. You may change this value. |
Freeze Pct (freeze percent) |
Select to freeze or set the installment percentage at the entered amount. Freezing the percentage prevents the system from trying to recalculate it. The freeze percent settings are session-temporary only. They are not saved as part of the terms definition, but are only used during initial setup to help allocate the wanted percentage to each installment. For example, suppose that the display is initialized to two installments of 50 percent each. To set up terms with three installments with a 40 percent/30 percent/30 percent split, entering 40 percent for the first installment automatically sets the Freeze Pct check box for it and results in 60 percent being allocated to the unfrozen second installment. From this point, you can increment the number of installments from two to three, and the unfrozen percentage is now split between the second and third installments. |
Access the Calculate Example Payment Data page.
Calculation Parameters
Currency |
Select the transaction currency. The currency selected affects the rounding decimal units for the calculated discount amount. |
Gross Invoice Amount |
Displays the total payment amount to be scheduled for the voucher—for example, the gross amount owed to the vendor. |
Terms Basis Amount |
Enter the terms basis amount. If the payment terms include a provision for discounts, you can use this field to simulate a mix of discount-applicable and nondiscount voucher lines by entering the total applicable amount here. The default field value is equal to the gross invoice amount value, meaning that the default is 100 percent discount-applicable. Select the Use Basis Amount check box to make this field available for entry, and enter a different value. |
Use Basis Amount |
Select to make the Terms Basis Amount field available for entry, thus enabling you to override the default value. |
Basis Date |
Select the basis date. The system populates this field with the current date by default. |
Click the Calculate Example Payment Data button to calculate the payment data based on the values entered on the page. |
Calculation Results
When accessed from the Payment Terms - Single Payment page, this grid is labeled Calculation Results - Single Payment Alternatives. When accessed from the Payment Terms - Multi Payment page, this grid is labeled Calculation Results - Scheduled Installments. The grids display payment and due date information based on the values entered in the Calculation Parameters group box calculated against values entered on the originating Payment Terms page.
Net Due Date |
Displays the net due date based on the basis date value and the terms defined on the originating Payment Terms - Single Payment page or Payment Terms - Multi Payment page. The calculated due date for each installment becomes the basis date for the next sequential installment. |
Net Amount |
Displays the net amount due based on the gross amount value calculated against any applicable discount terms entered on the originating Payment Terms - Single Payment page or Payment Terms - Multi Payment page. |
Discount Due Date |
Displays the due date for qualifying for a discount on the net amount based on the basis date and terms defined on the originating Payment Terms - Single Payment page or Payment Terms - Multi Payment page. |
Discount Amount |
Displays the amount of the discount based on the basis amount calculated against any applicable discount terms entered on the originating Payment Terms - Single Payment page or Payment Terms - Multi Payment page. |
|
Click the Examine Installment Detail button to access the Examine Installment Detail page. |
Access the Examine Installment Detail page.
Calculation Parameters
This group box displays the parameters you defined on the Calculate Example Payment Data page.
Calculation Results - Single Payment Alternatives
The Calculation Results - Single Payment Alternatives group box displays payment and due date information based on the values in the Calculation Parameters group box calculated against values entered on the originating Payment Terms - Multi Payment page.
Net Due Date |
Displays the net due date based on the basis date value and the terms defined on the originating Payment Terms - Multi Payment page. |
Net Amount |
Displays the net amount due based on the gross amount value calculated against any applicable discount terms entered on the originating Payment Terms - Multi Payment page. |
Discount Due Date |
Displays the due date for qualifying for a discount on the net amount based on the basis date and terms defined on the originating Payment Terms - Multi Payment page. |
Discount Amount |
Displays the amount of the discount based on the basis amount calculated against any applicable discount terms entered on the originating Payment Terms - Multi Payment page. |
Installment Number |
Displays the installment sequence assigned to this single payment. |
To establish additional payment processing options, use the following components:
Payment Handling Codes (PYMNT_HNDL_CD_PNL)
Payment Messages (PYMNT_MSG)
This section discusses how to:
Define payment handling codes.
Establish standard payment messages.
Page Name |
Object Name |
Navigation |
Usage |
PYMNT_HNDL_CD_PNL |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Payments, Payment Handling Codes, Payment Handling Codes |
Enter codes that indicate how to handle individual payments. Payment handling codes help determine the order in which payments are generated—typically they are used to determine the order in which checks are printed. You must enter at least one code for the system to process payments. |
|
PYMNT_MSG |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Payments, Payment Messages, Payment Message |
Enter standard payment messages for printing on payment advices. |
Access the Payment Handling Codes page.
Payment handling codes work with sequence numbers to determine the order in which payments get generated (that is, typically, the order in which checks get printed) within a pay cycle. Payments with the same handling code get generated together. A higher handling code sequence number causes a payment to be generated last; for checks this means that payments with handling codes of a higher sequence number are printed last and end up on the top of the pile.
Payment Handling |
Enter a payment handling code to indicate how you want to handle individual payments. PeopleSoft delivers the following codes, but you can add your own:
The payment handling code defaults onto the payment from the voucher origin associated with the user or the vendor, but it can be overridden on the voucher. When you set up bank accounts, you can define a high dollar amount that, when reached, causes the payment handling code on a voucher automatically to switch toHD (high dollar payment). |
Sequence Number |
Determines the sort sequence of the payments generated. Note. If you are entering multiple payment handling codes, keep a gap between the sequence numbers so that you can subsequently add additional codes between the existing ones. |
Note. Typically, multiple scheduled payments to one vendor in a pay cycle are bundled into one payment. This is not the case when the scheduled payments have different payment handling codes. In the last instance, the system produces one payment for each handling code.
See Also
Access the Payment Messages page.
You can print the messages entered on this page on the payment advice by selecting them from the Payments page in the Voucher component.
Description |
Enter a description for the payment message. |
Payment Message |
Enter the text of the payment message, up to 70 characters. You can have multiple messages for each message code. |
See Also
Entering Payment Information for Vouchers
To define late interest charges, use the following components:
Late Interest Charges (LATE_CHRG_TBL).
Late Chrg Chartfield Override (late charge ChartField override) (LATE_CHRG_CF).
Payment Reason Codes (PYMNT_REASON_CD).
This section provides an overview of late interest charges and discusses how to:
Define late interest charges.
Override late charge ChartFields.
Define payment reason codes.
If you enable late interest charges on the Installation Options - Payables page, the system can automatically calculate interest charges for late payments to vendors. Once you have set up the late interest charges, you can define late charge options at the Payables business unit, origin, vendor and voucher levels of the control hierarchy.
Late interest charge calculation is primarily a U.S. federal feature.
Note. Late charges are calculated during pay cycle processing. They are calculated on the voucher gross amount and, once calculated, converted from the invoice currency to the payment currency, if necessary.
See Also
Calculating Late Interest Charges
Page Name |
Object Name |
Navigation |
Usage |
LATE_CHRG_TBL |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Payments, Late Interest Charges, Late Interest Charges |
Define late charge interest rates. |
|
LATE_CHRG_CF |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Payments, Late Interest Chrg Chartfields, Late Charge ChartField Override |
For a particular Fund Code, replace particular ChartField values for the late interest charge distributions defined on the Accounting Entry Template and by inheritance. |
|
PYMNT_REASON_CD |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Payments, Payment Reason Codes, Payment Reason Codes |
Assign reason codes to late payments to explain why the payments are late. |
|
LATE_CHRG_SBP |
Click the Late Charge link on the Payments page in the voucher component. |
Override late interest charge information for a voucher. |
Access the Late Interest Charges page.
Interest and Minimum Amount
Interest Rate |
Enter the interest rate used to calculate late charges. |
Minimum Pay Amount |
Enter a threshold for the calculated late interest charge below which it will not be paid. |
Penalty |
Check to indicate that this is a late charge assessed directly by the vendor. Such charges are reported in Section E (Other Penalties) of the Prompt Payment Report (APS2001). |
Interest Calculation Days
Days in Year |
Enter the days in the year based on the business needs. Some organizations choose 365 but, for others, 360 is a better choice. |
Simple Interest Days |
Enter the days subject to simple interest. The system calculates compound interest on the number of days the payment is past due minus the number of simple interest days. |
Max Pay Days (maximum pay days) |
Enter the maximum number of days the system computes interest. |
Access the Late Charge ChartField Override page.
Late charges are charged to late charge accounting entries generated by the late charge distribution defined on the Accounting Entry Template and by inheritance. You can override these distributions with other ChartField values for a particular Fund Code.
For example, if the budget has expired, you could override late charge ChartFields to hit an active budget. In this case, if you override the ChartFields, you must enter a budget start date, budget end date, and account. The additional ChartFields are optional for override.
Access the Payment Reason Codes page.
Definition Option
User Applied |
Select to manually assign reason codes to individual payments at the voucher level. |
System Applied |
Select to automatically inserts reason codes at the business unit definition level. |
Reason Code Type
Early and Late |
Indicate whether this reason code applies to a payment that is early or one that is late. |
To define credit card vendors, use the ProCard Card Issuers component (CC_CARD_TBL).
This section discusses how to enter card issuer information.
Page Name |
Object Name |
Navigation |
Usage |
CC_CARD_TBL |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Purchasing, ProCard Card Issuers, Card Issuer |
Enter details about procurement/corporate card vendors and link the details to a vendor ID. The vendor ID controls the bank account and other important vendor attributes for that card provider. You must have already set up the vendor ID for the card provider in the Vendor Information component. |
|
VAT_DEFAULTS_DTL |
Click the VAT Default link on the Card Issuer page. |
Define VAT defaults for the card provider. |
|
CC_CARD_TBL_CF |
Click the Setup Prepayment ChartFields link on the Card Issuer page. |
Define prepayment ChartFields. |
Access the Card Issuer page.
Credit Card Provider Record
AP Business Unit (accounts payable business unit) |
Select the PeopleSoft Payables business unit which the system will use to settle charges for this card provider. |
Vendor ID |
Select the vendor associated with this corporate card provider. This is the vendor that is used for payment and posting purposes. |
Vendor Location |
Select the vendor location for this card provider. |
Corporate Number |
Enter a corporate number if the business uses corporate numbers to reference credit card vendors. The system uses this optional field for reporting and informational purposes. |
Load Level 3 Data |
Select this check box to enable loading detailed transaction information from the card provider. |
Bill Includes Tax (if applied) |
Select if the transaction amount on the bank statement includes a tax amount (tax inclusive). Based on this setting, the system can accurately calculate the merchandise amount and the tax amount, if the proper tax code or tax percentage is provided (either by the bank statement or by the employee performing the statement reconciliation). If a bank captures the transaction amount and tax amount separately, or supports, captures, and provides level two (item information, tax information) and level three information (account information, charge code), then clear the Bill Includes Tax (if applied) check box. Corporate card providers can support multiple levels of data capturing. Some credit card providers can single out taxes on the statement, and others simply include the tax in the total amount. |
Bill Includes VAT (if applied) |
Select this check box if the transaction amount on the bank statement includes VAT. |
VAT Default |
Click this link to access the VAT Defaults Setup page. Use this page to define VAT defaults for the card provider. |
Notify Pending Reconciliation |
Enter the number of days after a billing cycle that users have to review and reconcile their statements before the system processes the Voucher Build Application Engine process (AP_VCHRBLD). |
Expiration Grace Days |
Enter a grace period which you want to prevent card usage before the cards stated expiration date. |
Prepayment Voucher Default
Create Prepayment Voucher |
Select this check box if you want to automatically stage a prepayment voucher when loading statements from this procurement card provider. |
Prepayment Voucher Options |
Select the prepayment voucher option. Values are:
|
Payment Terms ID |
Select the payment terms. The system will use this field to determine when based on the statement date the prepayment will be scheduled to pay. |
Setup Prepayment ChartFields |
Click this link to access the Card Issuer - Setup Prepayment ChartFields page. Use this page to define prepayment ChartFields. This link is only available if you select the prepayment voucher option of Specify. |
See Also
To define vendor freight groups, use the Vendor Freight Group component (PO_VNDR_FRT_GRP).
This section discusses how to create vendor freight groups.
Page Name |
Object Name |
Navigation |
Usage |
PO_VND_FRT_GRP |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Purchasing, PO Vendor Freight Group, Vendor Freight Group |
Create vendor freight groups by grouping vendor locations under a single freight group code. |
Access the Vendor Freight Group page.
Vendor Freight Info
Displays the TRFT rule code, which determines how the system calculates transportation lead times and freight charges. |
|
Global |
Select to apply the TRFT rule code to all the vendors. If you select this option, you don't need to fill in the Vendor Freight Group scroll area fields. All of the vendors are subject to the TRFT rule code that you select. |
To define ship to codes, use the Ship To Codes component (SHIP_TO_CODES).
This section discusses how to:
Create ship to locations.
Specify ship to location sales and use tax defaults and exceptions.
Specify ship to location vendor order locations.
When you define the general options for the PeopleSoft system, you set up location definitions to store address information for the various locations of the organization. You can identify these locations as ship to locations, which are places where you receive goods from vendors.
You can assign ship to locations to PeopleSoft Purchasing requesters and buyers to create default shipping information for requisition and purchase order schedules. This default information passes through the system when you create transaction documents. For example, the system passes the requisition ship to location to the purchase order schedules when the requisition is sourced.
You can also update the PeopleSoft Purchasing user preferences to create default shipping information for requisitions and purchase orders.
In the PeopleSoft Purchasing system, the ship to location carries the sales and use tax (SUT) information, specifying how sales and use taxes are handled for items shipped to that location. Normally, the SUT is based on the ship to location or the ultimate use of the items. However, different geographic locations have different SUT regulations. For this reason, different locations and different items can be taxed at varying rates. PeopleSoft Purchasing enables you to indicate tax exception information for each ship to location. You can also specify various combinations of ultimate use, vendor location, item category, and item ID data that are either taxable or nontaxable. When you create a purchase order or voucher, the system uses the SUT default information to determine the appropriate tax rate. The system uses the data that most closely matches the purchase order schedule line or voucher line.
The ship to location also carries vendor order location information so that you can associate specific vendor locations with each ship to location. This enables you to order goods from the closest or preferred vendor location. For example, suppose that most of the offices are located on the East Coast of the U.S. You normally order from the vendor's New York location, but you also have one office on the West Coast. For this office, you might want to place the orders with the vendor's San Francisco location. To do this, specify a vendor order location for the San Francisco office.
Note. When you need purchased goods drop-shipped to a one-time use site that is not one of the existing locations, define a one-time ship to address on either the requisition or purchase order by using the One Time Address Default page (header-level) and the One Time Address page (schedule-level). Because you use this address only once, there is no need to create a new location or ship to location.
See Also
Entering Purchase Order Schedule One-time Address Information
Creating One-Time Requisition Default Addresses
Page Name |
Object Name |
Navigation |
Usage |
SHIPTO_HDR |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Purchasing, Ship To Locations |
Create ship to location IDs that designate existing location IDs as places where you receive goods from vendors. You must specify an existing location ID as the ship to ID. |
|
SUT_DFLT_TBL |
Click the Sales/Use Tax link on the Ship To Locations page. |
Specify default sales and use tax information for each ship to location. The sales and use tax rates are normally based on the final destination of the shipment (the ship to location). Indicate exceptions to the normal tax rate for each ship to location, and indicate whether the tax exception status is Active or Inactive. |
|
SHIPTO_VNDR_LOC |
Click the Vendor Order Location link on the Ship To Locations page. |
Specify a vendor order location for a ship to location, and indicate the applicable sales and use tax for the vendor order location. |
Access the Ship To Locations page.
Ship To Details
Status |
Specify a status for this ship to location. The status takes effect on the effective date. Values are: Active and Inactive. |
Distribution Network SetID |
Displays the distribution network setID for the ship to location. The distribution network setID identifies the entire distribution network. |
Distribution Network Code |
Displays the distribution network code for this ship to location. The distribution network code identifies a subset of the entire distribution network. |
Inventory Unit |
Displays the inventory business unit for this ship to location. The inventory business unit is where items shipped to the ship to location are actually stocked. |
Receiving Business Unit |
Displays the default receiving business unit for use by the Receive Load process (PO_RECVLOAD). |
Region SetID and Region |
Displays the region setID and region for this shipto location. |
Send Expected Receipt |
Select to send purchase orders that you expect to receive at the ship to location to the location by using XML. |
Copy to Transactions |
Select to copy delivery instructions text for this ship to location to the purchase order. |
Send to Vendor |
Select to send delivery instructions text for this ship to location to the vendor. |
Access the ShipTo Sales/Use Tax Default page.
Tax Exception
Exception Type |
Select an exception type. This field designates whether the ship to location is a tax exception. Options are: Direct Pay: For this location, tax is paid directly to the tax agency rather than to the vendor. Exempt: This location is not subject to sales or use tax. None: This location does not have a tax exception. |
Excptn End Date (exception end date) |
Displays the exception end date. Required if the exception type is Direct Pay. |
Sales/Use Tax Exception Certif (sales and use tax exception certificate) |
Required if the exception type is Direct Pay. Applies to PeopleSoft, Taxware, and Vertex calculations. |
Calculation Parameters
Calculation parameters are applicable only to Taxware and Vertex, providing these third-party tax applications with tax calculation rules for the ship to location. These applications use the GeoCode for the ship to location to apply these rules to the appropriate tax calculation algorithms. They may also use the GeoCode for the order acceptance location, ship from location, and (Taxware only), the place of order origin.
Indicates that the VAT amount must be taxed and added to the net-extended amount before calculating SUT. This field is information-only. Tax applicability of VAT amounts is determined as part of VAT setup. See Working with VAT. |
|
Include Freight |
Indicates that the freight amount must be taxed and added to the net-extended amount before calculating SUT. This option is used for Taxware only. |
Include Discount |
Indicates that PeopleSoft calculates any applicable discount and passes the discount amount to Taxware or Vertex. |
Include Misc Charges (include miscellaneous charges) |
Indicates that any other charges must be taxed and added to the net-extended amount before calculating SUT. |
Use these fields to specify further tax information for the ship to location. The value in the Sales/Use Tax Applicability field must match the value in the Exception Type field as follows:
If the exception type is Direct Pay, then SUT applicability must be Direct Pay.
If the exception type is Exempt, then SUT applicability must be Exempt.
If the exception type is None, then SUT applicability must be Taxable.
These rules apply to PeopleSoft, Taxware, and Vertex calculations. All values are copied to the payables voucher.
See Also
Integrating with Sales and Use Tax Applications
Setting Up Sales and Use Taxes and Value-Added Taxes (VAT)
Access the ShipTo Vendor Order Location page.
Vendor Order Location
Vendor SetID |
Displays the vendor setID. This field value determines the values available for the vendor ID. |
Apply to All Vendors |
Select to indicate that the SUT Flag option applies to all vendors. |
Vendor ID |
Displays the vendor ID. Only values for the selected vendor setID are available. This field determines the values available for the order vendor location. |
Order Vendor Loc (order vendor location) |
Displays the vendor order location that you want to associate with the ship to location. The vendor location that you select here is the primary attribute used for calculating item pricing. |
Designate the SUT applicability for the ship to vendor order location. Values are: None, Sales, and Use. |
To define origin codes, use the Origin Codes component (PO_ORIGIN_CODES).
This section discusses how to define origin codes.
Origin codes identify places in the system from which transactions originate. For example, you can define origin codes to indicate online entry, fax, or email. You can also use these codes to identify departments or groups within the organization. Origin codes enable you to group the transactions, and they provide an additional level from which information can appear by default in transactions.
PeopleSoft Purchasing and PeopleSoft Payables share the same procurement origin code table. This enables the Payables Voucher Build process to build vouchers from PeopleSoft Purchasing receipts, non-purchase order receipts, purchase orders, and contracts, regardless of the origin code default values. Because these two applications share origin codes, PeopleSoft Payables is able to recognize default origin codes regardless of where they are set.
Page Name |
Object Name |
Navigation |
Usage |
ORIGIN_PO |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Purchasing, PO Origin Codes, Origin Codes |
Create a code that identifies the originator of a transaction in the system. |
To define fax cover letter, fax location, file location options, and purchasing dispatch configurations, use the Fax Cover (FAX_COVER), Fax Location (FAX_LOCATION), File Location (FILE_LOC), and Purchasing Dispatch Configuration (PO_DISP_CON) components.
The PeopleSoft Purchasing dispatch mechanism and setup procedures are universal to purchase orders, contracts, requests for quotations (RFQs), and RTVs. Dispatching these transactions by fax and email requires the additional setup steps discussed here. Dispatching by print, phone, and electronic data exchanges (EDX) does not require additional setup.
To set up the system to dispatch transactions by fax or email:
Access the File Locations page to set up valid file extensions and directory locations.
Access the Fax Location page to define the file extension to be used to create the fax control file.
Access the Dispatch Configuration page to specify the file extensions and, consequently, the output directories to be used for fax and email dispatch processes.
Access the Purchase Order Images page to set up the system to print a logo or signature on the purchase orders.
Access the Fax Cover Letters page to select the fax cover letters in the system to use when dispatching by fax.
Tips for Dispatching and Printing Transactions
The following may be setup issues:
The entry in the SQRDIR set in the PSSQR.INI (Microsoft Windows environment) or PSSQR.UNX (UNIX environment) file must be correctly defined and pointed to the correct BINW where the Structured Query Report (SQR) executables are installed.
PeopleSoft delivers an undefined (dummy) SQRDIR to enable you to install the SQRs in a location that best suits the configuration. If the SQRDIR is not pointing to the correct BINW directory, certain features will not work as designed. For example, comma-separated values files, enhanced HTM files, and Postscript files will not be produced correctly.
If the output format is Postscript and the document is printing beyond the left margin, you may solve this problem by modifying the POSTSCRI.STR file located in the BINW.
Modify POSTSCRI.STR as follows, to increase the left margin setting:
/lmarg LM 720 mul def % Left margin
The email dispatch method is designed to work with a Simple Mail Transfer Protocol (SMTP) gateway.
The settings for the SMTP gateway have to be entered when you set up a Process Scheduler Server.
Page Name |
Object Name |
Navigation |
Usage |
FILE_DIR_FS |
Set Up Financials/Supply Chain, Common Definitions, File Locations and Images, File Locations |
Define file locations by specifying the file extensions that you want the system to recognize. As part of defining file extensions, you can specify the file directory locations that the system searches to find attachments for the purchase orders, contracts, and so on. You can also specify file extensions that designate the email output, fax output, and fax control files. As part of defining these file extensions, you can define the file server directories where various dispatch processes create output files. Depending on the context of use, these file extensions are not necessarily conventional file extensions such as .DOC and .BMP, but can be any 3-character code that you use to recognize a file type. |
|
FAX_LOCATION |
Set Up Financials/Supply Chain, Common Definitions, Location, Fax Location |
Set up fax locations by defining business-unit-level information that enables dispatch processes to construct appropriate dispatch fax numbers. The information defined on this page also enables dispatch processes to assign proper extensions to the fax control files that they produce. |
|
PO_DISP_DEST |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Purchasing, Dispatch PO Configuration, Dispatch Configuration |
Define dispatch configurations by entering information that enables the system to identify how to handle output files when you dispatch by either email or fax. |
|
BUS_UNIT_PM_IMAGE |
Click the Define Images link on the Purchasing Definition - Business Unit Definition page. |
Define a file directory location for an image that you want to print on the purchase orders. |
|
PO_FAX_COVER_LTRS |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Purchasing, Fax Cover Letters |
Define fax cover letters by selecting the fax cover letters in the system to use when dispatching by fax. |
Access the File Locations page.
Throughout PeopleSoft applications, you can append various documents and other items—such as Microsoft Excel spreadsheets, ASCII files, or blueprints—as attachments. You can also route output from certain background processes, such as dispatching purchase orders, to a vendor using email, fax, or EDX. Please note that an external file—for example, a Microsoft Word document—that is attached to a purchase order is not included in the output file when that purchase order is dispatched or printed.
To use attachments, you must define the default locations, or file directories, for the documents that you use within the PeopleSoft system. You must also specify a server's location to route process output to the correct server.
You must set up a file location for each type of file that resides on a particular server. By categorizing file types and storing them in the same file directory, the system can easily locate the different types of files used as multimedia attachments or for server processing.
The file extensions that you define here are used for retrieving file directory information for the defined file types. This information is not used by PeopleSoft Purchasing dispatch processes to determine the file extensions of the output files that they create.
The actual extensions of the output files created by the dispatch processes are based on the output format that you specify for the dispatch on the Process Scheduler Request page. For example, if you select an output format of HP, LP, PS, or OTHER, the system creates the output file with a .LIS file extension.
File Ext (file extension) |
Specify the file extension for each type of attachment. Depending on the context of use, these file extensions are not necessarily conventional file extensions such as .DOC and .BMP, but can be any 3-character code that you use to recognize a file type. For example, enter DOC for Microsoft Word document files and BMP to designate bitmap files. You can also enter FAX to designate fax output files or CTL to designate fax control files. This value serves as the primary key. The actual file extensions for output files for faxes and emails are ultimately determined by the format that you select for the dispatch on the Process Scheduler Request page. |
File Directory |
Enter the location path to be used by PeopleSoft Purchasing online page PeopleCode to determine where to retrieve file attachments. This is the directory where the file attachments for purchase orders, contracts, and so on are stored. Use this syntax to define the file directories: http://host_name/folder_name/. Be sure to include the last slash (/). The actual file directory that http://host_name is translated into is determined by the web server that you install along with its configuration. For example, for a Microsoft IIS web server, http://host_name is translated into C:\Inetpub\wwwroot\ by default. For an Apache web server, the translation of http://host_name is determined by the content of the httpd.conf file. If there is no Alias directive specified in this file, then the entry for DocumentRoot is used, which is normally C:\Program Files\Apache Group\Apache\htdocs\. If there is an Alias directive specified, then the translation is based on the entry for the corresponding Alias entry. For example, with Alias /image/ftp/pub/image, a request for http://host_name/image/pslogo.gif causes the server to return the file /ftp/pub/image/pslogo.gif. The folders specified as file locations need to be designated as shared folders in order for them to be accessible to users over a browser. For network (LAN) file directories, directory formats include:
|
File Directory - Server |
Enter a location path to a file server directory where you want dispatch processes to save the output files that they create. This is the file server directory where the POPO005.SQR (PO Dispatch), POCNT100.SQR (Contract Dispatch), PORFQ01.SQR (RFQ Dispatch), and PORT001.SQR (RTV Dispatch) SQR dispatch programs create output files. The value in this field is used primarily by PeopleSoft Purchasing dispatch processes. Use this syntax to define these file server directories for the Microsoft Windows environment: \\server_name\folder_name\. Be sure to include the last slash (\). If the PeopleSoft Process Scheduler server and output directory are on the same computer, use this syntax to define the file server directories: c:\folder_name\. Be sure to include the last slash (\). The folders specified as file locations need to be designated as shared folders in order for them to be accessible to users by browser. The fax control file is always written to the same file location as the fax output file. Although you can specify a different file location for the fax control file, it will be ignored. You can specify the file extension for the fax control file on the Fax Location page. |
See Also
Enterprise PeopleTools 8.46 PeopleBook: PeopleSoft Process Scheduler
Access the Fax Location page.
You can fax documents directly from within PeopleSoft applications. You can also route output from certain background processes, such as dispatching purchase orders, to a vendor by way of fax.
To fax documents, you must define the business-unit-level information that enables dispatch processes to construct appropriate dispatch fax numbers, and assign proper extensions to the fax control files that they produce.
When you send a fax to a vendor, the system compares the location information with the vendor's telephone information, to determine which parts of the fax number to ignore and which additional numbers to dial. You enter vendor fax information on the Phone Information page in the Vendor Information component.
Control File Extension |
Designate the file extension to be used for the fax control files. The directory for the fax control file is based on the directory defined for the fax output file. The fax control file is always created in the same file directory in which the fax output file is created. The output directory for the fax file is defined on the Dispatch Configuration page. A fax control file contains the information necessary to send a fax, such as which files to send, dialing instructions, and telephone numbers to dial. The file extension that you enter must have first been defined on the File Locations page. |
Access the Dispatch Configuration page.
With PeopleSoft Purchasing, you can phone in the purchase orders or other transactions, you can print and mail them to the vendors, or you can use email or fax to dispatch them. If you are dispatching by email or fax, you need to set up one dispatch configuration for each of the setIDs.
This dispatch configuration specifies the file extensions to be used to derive the file directory locations to use for the creation of email and fax output files. The system matches the output file extensions that you define on this page with the File Directory - Server field values that you defined on the File Locations page, to determine which file directory to use.
For faxing, you also need to designate the fax server and extension that identifies the fax cover letter.
Email File Extension |
Select the 3-character code that identifies the email output files. This code is used to derive the file directory location to be used when creating the email output file. These file directory locations are defined on the File Locations page. When processing for email, the dispatch programs use the value entered here (combined with the selected setID) to search the PS_FILE_DIR_FS table for the FILE_DIR_SERVER field to determine the directory in which to create the output file. The actual file extension of the output file is determined by the output format selected on the Process Scheduler Request page. For example, if the selected output format is PDF, then the file extension assigned is .PDF. If the selected output format is HP, then the file extension assigned is .LIS. |
Use the FAX Server Setup group box to define the setup information for dispatching by using a fax server.
Fax Sender |
Enter the fax server name. This value appears in the From field in the fax control file. |
File Extension |
Select the 3-character code that identifies the fax output files. This code is used to derive the file directory location to be used when creating the fax output file. These file directory locations are defined on the File Locations page. When processing for fax, the dispatch programs use the value entered here (combined with the selected setID) to search the PS_FILE_DIR_FS table for the FILE_DIR_SERVER field, to determine the directory in which to create the output file. The actual file extension of the output file is determined by the output format selected on the Process Scheduler Request page. For example, if the selected output format is PDF, then the file extension assigned is .PDF. If the selected output format is HP, then the file extension assigned is .LIS. |
Cover Letter File Extension |
Enter the extension that identifies the fax cover letter files. The dispatch programs join the cover letter file name that you specify on the applicable run control page with the selected cover letter file extension. The dispatch program then writes the combined information to the fax control file. Determining the value to enter in this field, as well as which cover letter file name to use, is mainly determined by the fax software that you use. For example, with some fax software packages, you cannot use just any document as a cover letter, but rather the software provides you with tools to create a set serialized cover letter managed by that software. In this case, you can use the serial number as the cover letter file name and leave the cover letter file extension blank. |
Fax Location |
Enter the business unit where the fax server is set up. Fax locations are defined on the Fax Location page. |
See Also
Enterprise PeopleTools 8.46 PeopleBook: PeopleSoft Process Scheduler
Access the Fax Cover Letters page.
If you create fax cover letters in the system, you can identify them with file names and descriptions. When you dispatch purchasing transactions by fax, you can specify the fax cover letter that you want to use by selecting one of the short descriptions defined on this page.
List of Fax Cover Letters
Use the List of Fax Cover Letters group box to identify the fax cover letters in the system that users can select from when dispatching purchasing transactions by fax.
Short Desc (short description) and Description |
Enter short and long descriptions of the fax cover letter. Users can search by the short description and use the long description to verify that they have located the cover letter that they want to use. |
File Name |
Enter a distinct file name for the fax cover letter files that the business uses. Do not include the file extension in the file name. You can create as many cover letter files as you want. The dispatch programs join the cover letter file name that you specify on the applicable run control page with the selected cover letter file extension. The dispatch program then writes the combined information to the fax control file. The value to enter in this field, as well as what cover letter file extension to use, is mainly determined by the fax software that you use. For example, with some fax software packages, you are unable to use just any document as a cover letter, but rather the software provides you with tools to create a set serialized cover letter managed by that software. In this case, you can use the serial number as the cover letter file name and leave the cover letter file extension blank. |
To define inspection routings, use the Inspection Routing component (ROUTINGS).
Inspection routings are sets of inspection instructions for receiving users. You can assign inspection routings to specific items in the Item table. Receiving users see the inspection instructions when they receive those items. For example, if you often purchase an item made to precise specifications, inspection routings enable you to define procedures for verifying the acceptability of received quantities of that item.
You identify each routing with an inspection ID and define any number of instructions for it. For each instruction, you can also create any number of effective-dated inspection instructions.
Page Name |
Object Name |
Navigation |
Usage |
ROUTING |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Purchasing, Inspection Routings, Inspection Routing |
Specify procedures for receiving users to inspect items in the item table for acceptability. |
Access the Inspection Routing page.
Batch Sequence
Batch Sequence |
Designate the order in which inspection instructions should be performed. The system automatically increments the sequence numbers in the order that they are entered. You can override this sequence by entering a new number for any instruction and saving the changes. The system reorders the inspection instructions in sequential order the next time that you access the page. |
Inspection Status
Run Time |
Indicate the estimated time required for the inspection operation. |
Operation Time Type |
Specify the inspection quantity on which the runtime value is based. Values are: Per Unit: Indicates that the inspection operation runtime is based on inspection of a single item. Per Batch: Indicates that the inspection operation runtime is based on inspection of a batch of items, such as a representative sample from an entire shipment. |
See Also
To define manufacturers, use the Manufacturer component (MANUFACTURER).
This section discusses how to create manufacturer IDs.
PeopleSoft Purchasing can link items to multiple manufacturers by using the manufacturer ID and the manufacturer's item ID.
This optional feature is useful for items that you purchase that are produced by more than one manufacturer. If you choose to establish manufacturer IDs, you can assign them to items so that they appear as default values on purchasing transactions. Alternatively, you have to manually specify the manufacturer on the purchasing transaction.
Page Name |
Object Name |
Navigation |
Usage |
MANUFACTURER |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Purchasing, Manufacturer |
Create manufacturer IDs for the manufacturers of items that you purchase. |
Access the Manufacturer page.
Assign a default UPN type code. A manufacturer may use more than one type of UPN. Typical practice is for a manufacturer to use one type of UPN most of the time. |
See Also
Using Universal Item Identifiers
This section lists the page used to establish model relationships to manufacturers.
See Also
Page Name |
Object Name |
Navigation |
Usage |
MFG_MODEL |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Purchasing, Manufacturer Model Relation |
Establish the relationship of models to manufacturers. |
To set up standard comments and standard comment types, use the Standard Comments (STANDARD_COMMENTS) and Standard Comment Type (STD_COMMENT_TYPE) components.
This section discusses how to set up the standard comments.
You can record frequently made comments as standard comments, which you can conveniently add to purchasing transactions. To set up standard comments:
Define comment type codes to identify the types of comments.
Define standard comments for each comment type.
For example, you can define a standard comment type of SHP for specific shipping instructions, and then enter each of the standard shipping comments under that comment type. On the Purchase Order Comments page, you only need to enter SHP in the Std Comment Type (standard comment type) field, and then select the appropriate comment ID from the list of standard shipping comments.
You can use this feature to set up the organization's terms and conditions as a standard comment, so that they are available for selection on the Purchasing Definition - Business Unit Definition page. This terms and conditions comment can be printed upon dispatching the purchase order, when you select the Print BU Comments check box on the Dispatch Purchase Orders page.
Page Name |
Object Name |
Navigation |
Usage |
STD_COMM_TYPE_PO |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Purchasing, Standard Comment Type, Std Comm Type |
Define standard comment types to use for organizing and searching for the standard comments that you attach to purchasing transactions. |
|
STD_COMMENTS_PO |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Purchasing, Standard Comments |
Define frequently used comments. You must have already defined standard comment types on the Std Comm Type page. |
See Also
Entering Purchase Order Header Comments
To define account receivables integration options for vendor rebates, use the Receivables Integration component (VRBT_AR_BU_OPTIONS).
This section discusses how to define account receivables integration options for vendor rebates.
Page Name |
Object Name |
Navigation |
Usage |
VRBT_AR_BU_OPTIONS |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Purchasing, Receivables Integration, AR Integration |
Define PeopleSoft Receivables integration options for the PeopleSoft Purchasing vendor rebate functionality. PeopleSoft Purchasing vendor rebate claims management functionality creates pending items for expected payment for a vendor rebate claim and sends those pending items to PeopleSoft Receivables. In addition, PeopleSoft Receivables sends payments received against those vendor rebate claims back to PeopleSoft Purchasing. These options assist in that integration processing. |
Access the AR Integration page.
Before you access this page you must specify the claim type you are defining account receivables integration options for. You will want to select a Claim Type of Vendor Rebate if you are defining options for use with PeopleSoft Purchasing vendor rebates and Claimbacks if you are defining options for use with PeopleSoft Order Management claimbacks.
Group Type |
Select the receivables group type. This group is a postable entity, a collection of pending items that are ready to post in PeopleSoft Receivables. |
Origin ID |
Select the receivables origin ID. The system uses the origin IDs to classify groups of pending items based on how they are created or brought into the system. |
Credit Entry Type |
Select the receivables credit entry type for check, direct debit, draft or EFT settlement method. An entry type categorizes the pending items and the system uses them to create or update items. |
Debit Entry Type |
Select the receivables debit entry type. |
Credit Memo CR Entry Type (credit memo credit entry type) |
Select the credit entry type for the credit memo settlement method. |
Credit Memo Base Amt Reason (credit memo base amount reason) |
Select the credit memo base amount entry reason code used by the system to identify the base amount for the credit memo settlement method. |
Cash Base Amount Reason |
Select the cash base amount reason code used by the system to identify the base amount for the check, direct debit, draft or EFT settlement method. |
Credit Memo Vat Amount Reason (credit memo value added tax amount reason) |
Select the credit memo VAT amount entry reason code used by the system to identify the VAT amount for the credit memo settlement method. |
Cash VAT Amount Reason (cash value added tax amount reason) |
Select the cash VAT amount reason code used by the system to identify the VAT amount for the check, direct debit, draft, or EFT settlement method. |
VAT Transaction Type (value added tax transaction type) |
Select the VAT Transaction Type used by the system when creating pending items if the PeopleSoft Receivables business unit is VAT enabled. The VAT Transaction Type should corresponds to a VAT Out of Scope value. Note. VAT will be accounted for in PeopleSoft Payables. VAT fields are displayed if VAT is applicable for the business unit. |
See Also
Setting Up Group Types and Group Origins
Setting Up Entry Types and Reasons
To define the requisition change order template, use the Requisition Change Order Template component (CHNG_ORD_TMPLT_REQ).
You use the Requisition Change Order template to define which fields trigger a change order through the online requisition pages. The Change Order template is a system-delivered template.
Manage the Change Order template by defining which fields you allow to be changed for each record. The requisition uses all fields on the Change Order template to trigger a change order.
Page Name |
Object Name |
Navigation |
Usage |
CHNG_ORD_TMPLT_REQ |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Purchasing, Req Change Order Template, Req Chng Ord Template |
Define requisition change order templates by adding or deleting fields on the requisition change order template. |
Access the Req Chng Ord Template page.
Record
Use the Record group box to define the change order template. The fields are part of the record.
Fields |
Select a record name, and then use the group box to define or update the fields for the record. The record corresponds to the area of the requisition that, if changed, generates a change order. Options include: REQ_HDR (requisition header): Select to work with the fields on the requisition header record. REQ_LINE (requisition line item): Select to work with the fields on the requisition line item record. REQ_LINE_SHIP (requisition line shipping schedule): Select to work with the fields on the requisition line shipping schedule. |
Fields
Use the Fields group box to define the specific fields on the change order template. If any of these fields are changed on a requisition, the system generates a change order.
Field Name |
Enter or update a field name, which indicates the field on the designated record that, if changed, prompts the system to generate a change order. |
Label Type |
Enter a field label type, which the system uses to determine how to display this field on the Change Ord Rqsts page. |
To include a field on the change order template that appears only on a view, you must add that field to the page and render it visible, for it to be a selectable field on the template.
The text that appears when you view Get Label Text is what you see as the field name in the change history inquiry.
See Also
Creating Purchase Orders Online
To define purchase order change order templates, use the Purchase Order Change Order Template component (CHNG_ORD_TEMPLATE).
This section discusses how to define purchase order change order templates.
If you change a purchase order after you have dispatched it to a vendor, you need to send the vendor a change order. Because you don't send every field on a purchase order to the vendor, the only fields that are part of the change order are the ones that are on the dispatched purchase order. For example, if you change a quantity on a purchase order line, the vendor needs to be notified because the quantity is part of the dispatched purchase order. On the other hand, if you change a distribution account code, you do not need to notify the vendor because account codes are never dispatched to the vendor.
Use these change order templates to specify definitions of a change order. Specify which changed fields cause the system to generate and transmit a change order to the vendors.
PeopleSoft ships a predefined change order template with the system. You can use this template, modify it, or create your own.
You must have corresponding change order records for each type of purchase order record that you want to transmit. For example, there must be a header change record if you want to change the purchase order header, and there must be a line change record if you want to change the purchase order lines. PeopleSoft Purchasing provides change order records for headers, lines, and shipping records. These change order records correspond to the different records used by the purchase order dispatch process.
See Also
Dispatching and Printing Purchase Orders
Creating Purchase Orders Online
Page Name |
Object Name |
Navigation |
Usage |
CHNG_ORD_TEMPLATE |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Purchasing, PO Change Order Template, PO Chng Ord Template |
Create and define templates that specify which purchase order fields, when changed after dispatch, cause the system to generate a change order. |
Access the PO Chng Ord Template page.
Record
Record |
Select a record type, and then use the Fields group box to define the change order fields in the record type. The record type corresponds to the area of the purchase order that, if changed, generates a change order. Values are: PO_HDR (purchase order header): Select to work with the fields on the purchase order header record. PO_LINE (purchase order line item): Select to work with the fields on the purchase order line item record. PO_LINE_SHIP (purchase order line shipping schedule): Select to work with the fields on the purchase order schedule. |
Fields
Field Name |
Indicates the field on the designated record that, if changed through online entry or a batch process, prompts the system to generate a change order. |
Label Type |
Select a label type. The system uses the label type to determine how this field appears on the Change Ord Rqsts page. Values include: Custom: Indicates a field label that you specify. When you select Custom, an edit box appears. Enter the custom label for the field. This label appears on the Change Order Requests page. Page: Indicates a field label taken from another page. When you select Page, the Page Name field becomes available for entry. Enter the page object name from which you want to take the field label. The label for the field name, as it is defined on the page that you entered, appears on the Change Order Requests page. For example, if you select the BILL_LOCATION field and then select the Page Name value PO_HDR, the label that appears on the Change Order Request page is the BILL_LOCATION label from the purchase order header page. Rec Long (record long): Indicates a field label taken from the long version of record field text defined for the field. This label appears on the Change Order Requests page. Rec Short (record short): Indicates a field label taken from the short version of the record field text that is defined for the field. This label appears on the Change Order Requests page. |
Get Label Text |
Click to view field name labels for Page, Rec Long, and Rec Short label types. |
To define change map templates, use the Change Map Template component (CHNG_MAP_TEMPLATE).
This section discusses how to create change map templates.
When you dispatch a purchase order to a vendor, the vendor acknowledges receipt of that purchase order. Sometimes the acknowledgement includes information that requires you to change the purchase order; for example, the vendor may not have the wanted quantity of an item or may not be able to deliver the items at the purchase order price. If you are using EDX with the vendors, these acknowledgements may arrive electronically directly into the PeopleSoft Purchasing system.
When vendor acknowledgements arrive in the system by using EDX, you can run a multiprocess job (XML Inbound process) that enables you to extract purchase order data from vendor acknowledgements and stages it into the following temporary tables for different parts of purchase order transactions:
PO_HDR_EC
PO_LINE_EC
PO_LINE_SHIP_EC
The Change Load process loads data from the previous EC tables. Based on the change map template, the process compares staged source record fields and field values (PO_HDR_EC, PO_LINE_EC, PO_LINE_SHIP_EC) with target system record fields and field values (PO_HDR, PO_LINE, PO_LINE_SHIP). If a difference exists, the Change Load process creates change requests (CHNG_RSQT, CHNG_RQST_DTL).
Based on the Change Order template, the Change Purchase Order process (PO_POCHNG) creates the necessary change orders from these change requests. The Change Purchase Order process takes the change order information and creates change history records (PO_CHNG_HDR, PO_CHNG_LINE, PO_CHNG_SHIP), and then updates target system records with the changes.
Page Name |
Object Name |
Navigation |
Usage |
CHNG_MAP_TEMPLATE |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Purchasing, Change Request Mapping, Change Map Template |
Create templates that are used to compare staged purchase order acknowledgement record fields and field values with target purchase order system record fields and field values. If a difference exists, change request records are created by the Change Load process. |
Access the Change Map Template page.
Source |
Identifies the change request source for the template. |
Record
Target Recname (target record group name) |
Displays the target record group name. The target record is the system record that is updated with data from the source record. Individual target system record fields are updated with data from individual source record fields. |
Fields
Source Recname (source record table name) |
Enter the source record name. Values include: PO_HDR_EC: EDX record for purchase order header data. PO_LINE_EC: EDX record for purchase order line data. PO_LINE_SHIP_EC: EDX record for purchase order schedule data. |
Source Transaction Fieldname |
Displays the source field name. This is an individual field in the source record that contains data to be transferred to a target system record. |
Target Fieldname |
Displays the target system field name. This is an individual field in the target system record to which the source data is transferred. |
To define buyers, use the Buyer Setup component (BUYER_TBL).
This section discusses how to establish buyers and defaults.
The values that you enter for the buyer on this page appear by default on the purchasing transactions created by this buyer. If you do not define values for fields on this page, you need to manually enter this information when you create purchasing transactions.
Page Name |
Object Name |
Navigation |
Usage |
BUYER_TBL |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Purchasing, Buyer Setup |
Establish users as buyers and define sets of purchase order defaults for each buyer. |
|
PO_SPEND_BUYER |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Purchasing, Buyer Setup, Dashboard |
Define what time frame the buyer wishes to view for the spend analysis graphs on the SRM Dashboard. See Using the Supplier Relationship Management (SRM) Dashboard. |
Access the Buyer Setup page.
Buyer |
Displays the user description that you entered on the User Profiles - ID page when you created the buyer's user ID. You can set up only established users as buyers. |
Status |
Select the status of the buyer. Values include Active and Inactive. If you select Inactive, the Substitute Buyer field becomes available for entry. |
The Department SetID, ShipTo SetID, Location SetID, and PO Origin SetID fields work together when you establish department, ship to, location, and origin default information for buyers. After you select a setID for each of the defaults, the system enables you to select only the defaults associated with that setID.
Department |
Select the default department for the buyer. The system uses this value as the department on all purchasing transaction distribution lines created by the buyer. |
Ship To |
Select the default ship to location for the buyer. The system uses this value as the ship to on all purchase order schedule lines created by the buyer. |
Location |
Select the default location for the buyer. The system uses this value as the location on all purchase order distribution lines created by the buyer. This is the internal final destination of the item once the vendor has delivered it to the organization. |
Origin |
Select the default origin for the buyer. The system uses this value as the origin on all purchase order headers created by a specified buyer. |
Substitute Buyer |
Displays the substitute buyer. This field becomes available for entry when the Status field is set to Inactive. For example, use this field when a buyer leaves the organization and you want to remove the buyer's name from the system, but don't want to manually change the buyer name in each of the control tables. Supplying the substitute buyer name automatically changes references to the inactive buyer name to the new substitute buyer name. Before you save, the system prompts you to be sure that you want to change the buyer in these tables: PS_ITM_CAT_TBL, PS_ITM_CAT_BU, PS_PURCH_ITEM_ATTR, PS_PURCH_ITEM_BU, and PS_VENDOR_LOC. |
Default PO Status
Open |
Indicates that purchase orders that the buyer creates are initially set to Open status and must be approved by an authorized user. Approval rules set at the business unit level determine whether the status of the purchase order changes to Approved or Pending Approval. |
Pending Approval/Approved |
Indicates that purchaser orders that the buyer creates are set to Pending Approval or Approved status, depending on the approval rules set at the business unit level. |
Override Procurement Card
This group only appears if the buyer can use a procurement card. Otherwise, this group box will be hidden.
Card Number |
The procurement card number appears that you selected as the buyer default on either the Assign Proxies page under the Security menu or the Assign Proxies page under the Cardholder Profile - Card Data page. You can change the procurement card number to another procurement card number. Only the procurement cards that are valid for this buyer are available for selection. |
Card Type |
Displays the card type associated with the procurement card. |
Expiration Date |
Displays the expiration date for this procurement card. |
Use Procurement Card as default payment method on Purchase Orders |
Select this check box if you want to use the procurement card you select on this page as the default payment method when creating a purchase order. |
Reporting Entity |
Select the reporting entity to which this buyer will be assigned. The reporting entity determines which Purchasing Business Unit's purchase orders will be included in the spend analysis graphs. Additionally, the reporting entity specifies a calendar so that delivery schedules can be bucketed into the appropriate periods. |
Prior Periods |
Specify the number of periods prior to the current period that should appear on the spend analysis graphs |
Future Periods |
Specify the number of periods after the current period that should appear on the spend analysis graphs |
See Also
Enterprise PeopleTools 8.46 PeopleBook: Security Administration
Establishing Procurement Card Security
To define requesters, use the Requester Setup component (REQUESTOR_TBL). Use the REQUESTOR_TBL_CI component interface load data into the tables for these components.
This section discusses how to establish requesters and defaults.
You can define default information for requesters and assign any number of item catalogs, including a default catalog, to each requester. This streamlines requisition data entry for each requester, because default information appears on requisitions automatically. You can then authorize established purchasing users to enter and process requisitions for all or specific requesters.
When you stage requisition data from any third-party application, you must set up requesters in the PeopleSoft system and in the third-party application for the enterprise integration point (EIP) to work as designed.
Page Name |
Object Name |
Navigation |
Usage |
REQUESTOR_TBL |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Purchasing, Requester Setup |
Establish default information for requesters. |
Access the Requester Setup page.
Requester |
Displays the name of the requester as well as the user description that you entered on the User Profile - ID page when you created the requester's user ID. Only established users can be set up as requesters. |
Requisition Default Values
The ShipTo SetID, Location SetID, and PO Origin SetID, fields work together when you establish ship to, location, and origin default information for requesters. After you select a setID for each of the defaults, the system enables you to select only the defaults associated with that setID.
Ship To |
Select the default ship to location for the requester. The system uses this value as the ship to location on all requisition schedule lines created by the requester. |
Location |
Select the default location for the requester. The system uses this value as the location on all requisition distribution lines created by the requester. This is the internal final destination of the item once the vendor has delivered it to the organization. |
Origin |
Select the default origin for the requester. The system uses this value as the origin on all requisition header lines created by the requester. |
Currency |
Displays the default currency associated with the requester. |
Use Only Assigned Catalogs |
Select to enable requesters to access only the catalogs relevant to their needs. Use the Catalog Information scroll area to define which catalogs are available to the requester. Keep these guidelines in mind if the requesters are restricted to using certain catalogs:
|
Consolidate with other Reqs (consolidate with other requisitions) |
Select if you want requisitions created by the requester to be consolidated during the PO Calculations process (PO_POCALC). The process uses this setting to determine whether the schedule can be consolidated with items from other requisitions. |
Price Can Be Changed on Order |
Select to enable a buyer to change item prices requested by the requester. If you do not select this check box, you cannot alter item prices on purchase orders. |
Defaults Inventory BU (defaults inventory business unit) |
Select to specify the default inventory business unit to be associated with the item in the requisition distribution. If you do not select this check box, the inventory business unit does not appear by default in the requisition distribution. |
Department |
Select the default department for the requester. The system uses this value as the department on all requisition distribution lines created by the requester. |
Requisition Status
Open |
Select to indicate that a requisition created by the requester remains in open status when saved. A requisition is not eligible to enter the approval process until an authorized user changes its status to Pending Approval. |
Pending |
Select to indicate that a requisition created by the requester is assigned a pending approval status and is eligible to enter the approval process when saved. |
Override Procurement Card
This group only appears if the requester can use a procurement card. Otherwise, this group box will be hidden.
Card Number |
The procurement card number appears that you selected as the requester default on either the Assign Proxies page under the Security menu or the Assign Proxies page under the Cardholder Profile - Card Data page. You can change the procurement card number to another procurement card number. Only the procurement cards that are valid for this requester are available for selection. |
Card Type |
Displays the card type associated with the procurement card. |
Expiration Date |
Displays the expiration date for this procurement card. |
Use Procurement Card as default payment method on Requisitions |
Select this check box if you want to use the procurement card you select on this page as the default payment method when creating a requisition. |
Catalog Information
Default |
Select to designate a default catalog for a requester. Optionally, you can assign any number of catalogs and designate one of them as the requester's default catalog. When you select this option, the default catalog automatically populates the catalog on the Order by Catalog, Category Search, and View Hierarchy pages. |
See Also
Viewing Catalog Category Hierarchies
Entering Requisition Header Information
Establishing Procurement Card Security
To define requisition loader default options, use the Requisition Loader Default component (REQ_LOADER_DFL).
This section discusses how to:
Define Requisition Loader defaults.
Define Requisition Loader overrides and options.
The Purchasing Requisition Loader Application Engine process (PO_REQLOAD) loads requisitions from various sources, such as other PeopleSoft applications or external sources in PeopleSoft Purchasing. Use the Requisition Loader Defaults - Req Loader Defaults page and Requisition Loader Defaults - Overrides and Options page to define default and overriding values for requisitions that the Purchasing Requisition Loader process loads from these sources.
When these requisitions arrive in PeopleSoft Purchasing, especially in the case of non-PeopleSoft sources, some of the requisition information might be missing. Entering values on the Requisition Loader Defaults - Req Loader Defaults page enables you to set default values that populate the appropriate fields on loaded requisitions. The values that you enter on the Requisition Loader Defaults - Req Loader Default page are used as defaults when the values are not already provided in the system.
In addition, some requisitions might enter PeopleSoft Purchasing with values that you want to change. Entering values on the Requisition Loader Defaults - Overrides and Options page enables you to override or replace existing values on loaded requisitions with values that you specify. You can also select options that affect the statuses of the requisitions and how the PeopleSoft Purchasing Requisition Loader process builds them.
See Also
Access the Requisition Loader Defaults - Req Loader Defaults page.
Requisition Loader Defaults
System Source and Requesting Loader Bus Unit (requesting loader business unit) |
The system source and requesting loader business unit you entered to access the page display. |
Business Unit |
Select the default PeopleSoft Purchasing business unit that will appear on the requisitions. If you want to use multiple business units for the same system source, you must set up a separate Requesting Loader Bus Unit (requesting loader business unit) for each business unit you want to use. The GL Unit field that displays on this page is the one that is associated with the PeopleSoft Purchasing business unit that you select. The GL Unit field is not available for modification. |
Requestor |
Select the name of the requester that will appear on the requisitions. |
Origin |
Select the origin default value that will appear on the requisitions. |
Ship To |
Select the default ship to business unit that will appear on the requisitions. The system will populate this field with the default value assigned to the requester if it isn't specified. |
Price Can Be Changed on Order |
Select this check box to enable the prices for items to be changed on the purchase orders. |
GL Unit(PeopleSoft General Ledger business unit) |
The PeopleSoft General Ledger business unit appears by default from the PeopleSoft Purchasing business unit that you selected in the Business Unit field. This PeopleSoft General Ledger business unit will appear on the distribution information for the requisitions. |
ChartFields |
Select the different ChartFields that will appear as defaults on the requisitions. |
Asset Information |
Click this link to access the Asset Information page where you can enter asset information for the item. Note. This link is not available for a PeopleSoft Maintenance Management (WM) system source. |
Access the Requisition Loader Defaults - Overrides and Options page.
Requisition Loader Overrides
Use the Requisition Loader Overrides group box to set values that override the existing values on requisitions built by the Purchasing Requisition Loader process.
Entry Event |
Select a value to override any default entry event codes entered at the business unit level or on the Requisition Loader page. Entry events codes are used to generate supplemental accounting entries. |
Requisition Loader Options
ChartField Status
ChartField Status |
Select the status to be used on requisitions. Values are:
|
Requisition Status
Use the Requisition Status group box to transfer a status to the corresponding fields on the requisition.
Open |
Select this option to give all requisitions a status of Open when they are loaded. |
Pending |
Select this option to give all requisitions a status of Pending when they are loaded. |
Approved |
Select this option to give all requisitions a status of Approved when they are loaded. |
See Also
Establishing Purchasing Options
Understanding ChartField Combination Editing
To define Purchase Order Loader default options, use the Purchase Order Loader Defaults component (PO_LOADER_DFL).
This section discusses how to:
Define Purchase Order Loader overrides and options.
Enter default asset information.
The PO Stage Load process (PO_POSTAGE) loads staging tables with entries from PeopleSoft Supply Planning and PeopleSoft Manufacturing for later purchase order creation. PeopleSoft Supply Planning and PeopleSoft Manufacturing do not have all the information required to create a purchase order. The PO Stage Load process also loads staging tables with entries from purchase order change order requests. Use this component to identify new lines and schedule defaults.
The PO Loader Defaults page enables you to set default values to populate fields on purchase orders loaded by the PO Stage Load process. If information is missing, the default values populate the appropriate ChartFields.
Some purchase orders might enter the purchasing application with values that you want to change. The PO Loader Defaults - Overrides and Options page enables you to override values on loaded purchase orders with the values that you specify. No matter what the ChartField value from the source is, the override value replaces it. You can also select options on this page that affect the status of the purchase orders and how the PO Calculations process (PO_POCALC) builds them.
PeopleSoft Maintenance Management can directly create purchase order staging data for the PO Calculations process to pick up and process. Use the system source Maintenance Management (WM), to define the business unit relationships. PO Loader defaults provide the mapping of a PeopleSoft Maintenance Management Business Unit to a PeopleSoft Purchasing Business Unit. PeopleSoft Maintenance Management does not use the overrides and defaults when creating the purchase order staging data.
PeopleSoft Order Management can directly create a purchase order from the Create/Update Order component. Use the system source OM Online Entry Panel (POM), to define the business unit relationships. PeopleSoft Order Management does not use the overrides and defaults when creating the purchase order.
Note. If you are loading staging tables from change requests, select PPO as the system source when you first enter the PO Loader Defaults component.
See Also
Page Name |
Object Name |
Navigation |
Usage |
PO_LOADER_DFL2 |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Purchasing, PO Loader Defaults |
Set default values for the PO Stage Load process. Default values populate empty purchase order fields when the process runs. |
|
PO_DFL_ASSET |
Click the Asset Information link on the PO Loader Defaults page. |
Enter asset information to appear by default in appropriate loaded transactions. Note. The Asset Information link is not available for a Maintenance Management (WM) system source. |
|
PO_LOADER_DFL1 |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Purchasing, PO Loader Defaults, Overrides and Options |
Define override options for the PO Stage Load process. These values replace existing purchase order field values when the process runs. |
Access the PO Loader Defaults - Overrides and Options page.
PO Loader Overrides
Use the PO Loader Overrides group box to set values that override the existing values provided by PeopleSoft Supply Planning, PeopleSoft Manufacturing, as well as values that are introduced to the system using purchase order change order process. These values are later staged by the PO Stage Load process (PO_POSTAGE).
Note. PeopleSoft Maintenance Management does use these overrides and options when creating purchase order staging data.
Buyer |
Select a buyer who overrides the buyer associated with an item. When the purchase order is created, the override buyer appears in the corresponding field, instead of the buyer associated with the item. |
Access the Asset Information page.
Note. This page is not available for a Maintenance Management (WM) system source.
When you consider the item on a distribution line to be an asset and plan to pass it on to the PeopleSoft Asset Management system through receiving, you must populate both the Business Unit (PeopleSoft Asset Management business unit) and Profile ID fields. When both fields contain values, the receiving business process treats the item as an asset and writes data to the PeopleSoft Asset Management staging tables. All fields entered here are passed to the PeopleSoft Asset Management system.
Business Unit |
Select a PeopleSoft Asset Management business unit. |
Cost Type |
Select the cost type that is incurred with the purchase of the item. Values are: C (cost), G (grant reimbursements), M (margin), R (revaluation), P (scrap on asset), and S (sales of assets). |
Capitalize |
Select this check box if the cost of this item is capitalized. You must enter an asset management business unit to select this check box. |
To define contract controls, use the Contract Control component (CNTRCT_CONTROL)
This section discusses how to set contract controls.
Page Name |
Object Name |
Navigation |
Usage |
CNTRCT_CONTROL |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Purchasing, Set Controls-Contracts, Set Controls - Contracts |
Set up the system to automatically assign ID numbers to each new contract and to define contract currency defaults. |
Access the Set Controls - Contracts page.
Contract
Select to have the system automatically assign sequential contract ID numbers. If you do not set up autonumbering, you are required to manually specify a unique ID whenever you create a new contract. |
|
Last Contract ID |
Displays the last contract number issued by the system. |
Default Currency
Currency Code |
Select the default currency code for contracts. The currency that you select is the default base currency for all contracts. |
Rate Type |
Enter a conversion rate type, which determines how the base currency is converted to other currencies. |
Master Contract
Use Autonumbering |
Select to have the system automatically assign sequential master contract ID numbers. If you do not set up autonumbering, you are required to manually specify a unique ID whenever you create a new master contract. |
Last Master Contract ID |
Displays the last master contract number issued by the system. |
Vendor Rebates
Last Rebate ID |
Displays the last rebate agreement number issued by the system. |
Last Claim ID |
Displays the last vendor rebate claim number issued by the system. |
Amount Tolerance Over and Amount Tolerance Under |
Enter the rebate agreement settlement tolerance amounts. These values will appear as defaults when defining a rebate agreement using the Rebate Agreement - Rebate Options page. |
Percentage Tolerance Over and Percentage Tolerance Under |
Enter the rebate agreement settlement tolerance percentages. These values will appear as defaults when defining a rebate agreement using the Rebate Agreement - Rebate Options page. |
To set up the tax vendor product codes cross reference, use the SUT Tax Vendor Product Xref component (SUT_PRODUCT_XREF).
This section discusses the page used to set up tax vendor product codes cross reference.
Page Name |
Object Name |
Navigation |
Usage |
SUT_PRODUCT_XREF |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Purchasing, Tax Vendor Product Code Xref, Tax Vendor Product Codes Cross Reference |
Establish the tax vendor product codes cross reference for Taxware and Vertex third-party tax applications. |
To set vendor control parameters, use the Set Controls - Vendor component (VENDOR_CONTROL).
This section discusses how to set vendor control parameters.
Each set of vendors that you define can be used for one or more PeopleSoft Payables business units, depending on the TableSet sharing setup. The parameters that you set at this level travel through the control hierarchy onto vouchers for any vendor belonging to this setID.
Page Name |
Object Name |
Navigation |
Usage |
VNDR_CNTRL |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Vendors, Set Controls-Vendor |
Set vendor control parameters, including autonumbering, withholding, duplicate vendor checking, and VAT applicability, for vendors belonging to the selected setID. |
Access the Vendor Set Control page.
Use Autonumbering |
Select to autonumber vendor IDs when you enter vendors for the selected setID. When you save a new vendor, the system automatically assigns the next vendor ID based on the last vendor ID assigned in either the PeopleSoft Payables or PeopleSoft Purchasing system. When you use autonumbering, the system enters Next in the search record Vendor ID field when you add a new vendor. |
Vendor Information Control
Display Withholding Option |
Select Global, 1099, or Global and 1099. This determines how the withholding link on the Vendor Information - Location page is labelled. |
Designate whether to enable VAT for vendors in this setID. |
|
Country |
Select a default country for the vendors in this setID. |
EFT Prenote Auto Confirmation
Wait Days |
Enter the number of days that the system waits to confirm a vendor prenote transaction after you send one to the bank for approval. A prenote transaction is a test transaction that enables a bank to verify that the routing information (transit number and bank account number) for an electronic funds transfer payment is valid. Typically, the bank notifies you within a certain number of days only if something is wrong with the prenote transaction. Set the number of wait days to be close to this time span. |
Duplicate Vendor Checking - Field Options
PeopleSoft Payables enables you to check for duplicate vendors in realtime, when users are entering new vendors in the Vendor Information component (VNDR_ID). Duplicate vendor checking options are set up by setID with the criteria specified here.
For each field option, select Do Not Check, Reject, or Warning. Duplicate vendor checking follows the following logic:
The vendor address fields are checked only against current effective-dated address records.
The Vendor Withholding TIN and Vendor Withholding Name fields are validated against all rows regardless of the effective date.
Reject criteria are validated first, and checking stops if a duplicate vendor is encountered.
Both rejects and warnings are checked only for vendors in the same setID.
ID Type |
To check for a duplicate identifier, select the identifier type, such as D&B Num (Dun & Bradstreet number). |
Select to check for duplicate VAT registration IDs. |
|
Vendor Name |
Select to check for duplicate vendor names. Vendor names must match exactly to come up as duplicates. |
Vendor Short Name |
Select to check for duplicate vendor short names. Short names must match exactly to come up as duplicates. |
(USA) Vendor Withholding TIN |
Select to check for duplicate withholding tax identification numbers. |
Withholding Name |
Select to check for duplicate withholding names. Withholding names must match exactly to come up as duplicates. |
Processing Options
Inactive Vendors |
Select one of these values: Do Not Include to exclude all inactive vendors when checking for an existing entry. Include/Reject to include inactive vendors and then reject the entry. Include/Warning to include inactive vendors and then warn that there is a duplicate vendor. |
Vendor CI Load(Vendor component interface load) |
Select one of these values: Do Not Check to exclude vendors loaded through the Vendor EIP. Check for Adds to check for new vendors loaded through the Vendor EIP. Check for Adds and Changes to check for adds and changes loaded through the Vendor EIP. Check for Changes to check for changes loaded through the Vendor EIP. |
Check for Duplicates at Save |
Select to check for duplicate vendors automatically when you save a vendor in the Vendor Information component. If you do not select this option, you can still check for duplicates by using the Check for Duplicates button on the Identifying Information page in the Vendor Information component. |
See Also
Importing Vendors Using the Vendor EIP
To define vendor pay group codes, use the Vendor Pay Group Codes component (PAY_GROUP_CD).
In this section, we discuss how to create vendor pay group codes.
You can assign each vendor in the system to a vendor pay group. Pay groups are optional selection criteria for pay cycles. When you set up the pay cycle selection criteria, you can elect to use vendor pay groups. You can then select payment group codes to include in the pay cycle, and the system creates payments to all vendors assigned to those groups.
See Also
Specifying Pay Group and Netting Criteria
Page Name |
Object Name |
Navigation |
Usage |
VNDR_PAY_GROUP_CD |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Vendors, Vendor Pay Group Codes |
Set up pay groups for vendors. |
To define vendor conversation keywords, use the Conversation Keywords component (KEYWORD_PNL).
In this section, we discuss how to define conversation keywords.
You can define keywords to categorize conversations that you have with vendors. Keywords might include price disputes, lead time inquiries, and so on. Conversation keywords enable you to record and track conversations that you have with the vendors.
The system uses the keywords to search the vendor conversation records when you try to resolve a particular problem. For example, on the Conversations page, you can record the key elements of a conversation regarding a price dispute. You could select the keywords Price and Dispute to use as search data. Later, you can search for all instances of those keywords to recall the record of the specific conversation.
See Also
Page Name |
Object Name |
Navigation |
Usage |
KEYWORD_VNDR |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Vendors, Conversation Keywords |
Define keywords to categorize conversations that you have with vendors. This page is optional. |
To enter vendor government certifications, use the Government Certifications component (GOV_CERTIFICATION).
In the U.S., various government sources provide vendors with classification certifications. For example, a vendor might be classified as Small Business - Hispanic Woman Owned.
Organizations must report information about the classification of vendors with whom they do business, and are sometimes also required to report similar information to their customers.
For example, ABC Organization reports vendor classification information to the Departments of Labor and Commerce and also reports similar information to the Edsel Motor Company, one of its major customers. It is necessary for ABC Organization to generate appropriate reporting to remain compliant with government customers. In addition, the automotive industry expects ABC Organization to have a reporting system that identifies various spending activities by different ethnic group categories.
To enter government certifications, you define the sources of government certifications and then define the government certification classifications. Once you define the sources and classifications, apply this information to the vendors in the Vendor Information component.
See Also
Entering Identifying Information
Page Name |
Object Name |
Navigation |
Usage |
GOV_CERTSRC_TBL |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Vendors, Government Certifications, Sources |
Define U.S. government sources from which you receive classifications of certification of vendors. |
|
GOV_CLASS_TBL |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Vendors, Government Certifications, Classifications |
Define types of classifications of certification from U.S. government sources. |
Matching is a flexible process that compares vouchers with purchase orders and receiving documents to ensure that you are paying for what you ordered and received. To run matching, you must have PeopleSoft Enterprise Payables and Purchasing installed on the same database.
To set up matching, use the following components:
Match Rule Type (AP_MTCH_RULETYPE).
Match Rules (AP_MTCH_RULES1 ).
Match Rule Control (AP_MTCH_RULE_CNTRL).
Document Association Group (AP_ASSTN_GRP).
Document Association Rule (AP_ASSOCIATION).
This section discusses how to:
View and update match rule types.
View and update match rule definitions.
View and update match rule workbench properties.
View and update match rule workflow parameters.
View and update match rule controls.
View and update the document association group.
View and update document association rules.
See Also
Managing Matches and Match Exceptions
Page Name |
Object Name |
Navigation |
Usage |
AP_MTCH_RULE_TYPE |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Vouchers, Match Rule Type, Match Rule Type |
View and create match rule types. Match rule types are matching categories, such as data entry, informational, merchandise quantity, merchandise unit price, merchandise amount, and system. All match rules are associated with a match rule type. |
|
AP_MTCH_RULES1 |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Vouchers, Match Rules, Rule Definition |
View, clone, create and update match rules. Match rules control the way that the Matching Application Engine process (AP_MATCH) compares the voucher, purchase order, receiver, and inspection information. |
|
AP_MTCH_RULES2 |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Vouchers, Match Rules, Workbench |
Select the label and fields to display on the Match Workbench. |
|
AP_MTCH_RULES3 |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Vouchers, Match Rules, Workflow |
Override the worklist and email notification parameters and user lists defined at the match rule type level. |
|
AP_MTCH_CNTRL_HDR |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Vouchers, Match Rule Control, Match Rule Control |
View and update the match rule controls. Match rule controls are sets of match rules applied against vouchers, purchase orders, and receivers during matching. |
|
AP_ASSTN_GRP |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Vouchers, Document Association Group, Document Association Group |
View the documents used in document association processing. You can include or exclude the delivered document associations. |
|
AP_ASSOCIATION |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Vouchers, Document Association Rules, Document Association Rules |
Define how the Matching Application Engine process (AP_MATCH) automatically associates receivers to vouchers and purchase orders. |
|
AP_ASCALG_CRIT_SEC |
Click the User Criteria link on the Document Association Rules page. |
Select the voucher fields, the condition operands, and the receiver fields for the criteria you are adding. |
Access the Match Rule Type page.
Match rule types are matching categories. Every match rule is associated with a match rule type. The match rule type controls the actions allowed after the application of the rule in the Matching process. They also provide default values for the workflow parameters defined on the rules. PeopleSoft delivers match rule types that include Data Entry, Merchandise - Amount, Merchandise - Quantity, Merchandise - Unit Price, Summary/Global Match Only, and System. To define additional match rule types, you must understand the complete matching process and the Matching Application Engine process (AP_MATCH).
Header
Workflow Flag |
Select to apply workflow to the rules that are associated to this match rule type. If you select the workflow flag, the Matching process generates worklist items for match exceptions. If you do not select the workflow flag, the system does not generate worklist items and the Send Email Notification field is not available. |
Send Email Notification |
Select to enable email notification. The Matching process notifies the defined users by email that there are match exceptions. This field is available if you select the Workflow Flag field. |
Notification Reminder Days |
Enter the number of days that the system waits before it sends another email notification for the match exceptions that have not been worked. This field is available if you select the Send Email Notification field. |
User List Source
This group box is available if you select the Workflow Flag field.
Note. You need to set up users to receive worklist items or email notifications or both on the User Profiles - Workflow page before you can route match exceptions to them.
Role |
Select to indicate that the list of users are based on roles. Enter the name in the Role Name field. All users with the specified role receives either a worklist item or an email notification or both, for match exceptions. |
SQL Definition (structure query language definition) |
Select to indicate that the list of users are based on a SQL definition. Enter the definition in the SQL Object Identifier field. The Matching process executes the SQL object to determine the user list. Note. PeopleSoft delivers four SQL objects for Buyer, Purchase Order, Receiver, and Voucher (AP_MTCH_WF_BUYER_SQL, AP_MTCH_WF_PO_SQL, AP_MTCH_WF_RECEIVER_SQL, and AP_MTCH_WF_VOUCHER_SQL, respectively). If you add new SQL definitions, you should use the two bind parameters, BUSINESS_UNIT and VOUCHER_ID. |
Query |
Select to indicate that the list of users are based on a query. Enter the name in the Query Name field. The Matching process executes the query to determine the user list. Note. To use a query, create a public query which selects the first column with a value equivalent to an operator ID (OPRID). If you want prompt values, use the fields available in the AP_VCHR_MTCH_VW. |
Note. You can override match rule type workflow parameters at the match rule level.
Allowed Match Action
Action |
Select a match action or actions to be taken after the rules associated with this type are applied. Valid action options for match rule controls include Debit Memo, Exception, and Match. Valid action options for the Match Workbench include Debit Memo and Override. Note. If you select Debit Memo, you must select a debit memo category on the Rule Definition page for each match rule associated with this match rule type. Note. The action or actions selected controls the actions allowed for the match rules associated with this match rule type. |
Allow on Rule Control |
Select to allow the match action on the Match Rule Control page for this match type. The Matching process automatically takes this action if the action is assigned to the rule. |
Allow on Workbench |
Select to allow the match action on the Match Exception Workbench Details page for the match rule that is associated to this match type. |
See Also
Understanding the Matching Engine
Viewing and Updating Match Rule Controls
Managing Matches and Match Exceptions
Access the Rule Definition page.
Match rules define how documents— vouchers, purchase orders, and receivers—are compared. PeopleSoft delivers the match rules that most organizations need. To define the additional valid match rules, you must understand the Matching process and its use of Model Record tables. It is also necessary to have an understanding of SQL.
Create Your Own Rule
The Create Your Own Rule group box only appears if you are adding a new match rule.
Copy From Match Rule Id and Copy |
Click the Copy button to copy an existing match rule SQL statement specified in the Copy From Match Rule Id field. |
Rule Properties
Match Rule Type |
Select the match rule type for the match rule. The match rule type determines which actions are allowed when the rule is used and the workflow defaults. Options include Data Entry, Merchandise - Amount, Merchandise - Quantity, Merchandise - Unit Price, Summary/Global Match Only, and System. |
Match Rule Level |
Select the level that the rule is applicable. Options are: Header Summary: The match rule is applied at the header level. The header summary record contains the voucher gross merchandise amount, total of purchase order schedule amounts, and total of receipt amounts that are associated to the specific purchase order schedule. Line Summary: The match rule is applied at the line summary level. The line summary record contains the voucher line merchandise amount, purchase order schedule merchandise amount, and total of receipt amounts that are associated to the specific purchase order schedule. |
Match Level Data Record |
Displays the data record associated with this match rule level. There is a data record for every match rule level. These records contain the values used in the rules SQL definition. Note. Use the values in the data record to create a custom match rule. You should first understand the values in the fields before creating the SQL where condition to ensure a valid match rule. |
Match Rule SQL Object (match rule structure query language object) |
Displays the SQL object associated with the match rule. The SQL object uses the fields contained in the match level data record. All delivered match rules are associated with a SQL object. |
Edit SQL |
Existing match rules only. Click the link to view the SQL statement that the system executes for this match rule on the Match Rule SQL Criteria page. Warning! Validate any changes made to the SQL statement to ensure proper syntax. This does not validate that the rule is going to perform as desired. Therefore, thoroughly test all match rules that you modify. |
Create SQL |
New match rules only. Click to add the SQL statement that the system executes for this match rule on the Match Rule SQL Criteria page. SQL statements must begin with and to be properly executed. The system automatically creates a SQL object associated with this rule when you update the new SQL statement. Warning! Validate any new SQL statements to ensure proper syntax. This does not validate that the rule is going to perform as desired. Therefore, thoroughly test all match rules that you create. |
Use Tolerance at Rule Control |
Select to include tolerance fields from the match rule control. Once you select this option, select either Amount or Percent to be used as a basis for the tolerance calculation. If you do not select this option, the Matching process will not use match rule control tolerances. See Matching Tolerances. |
Debit Memo Category |
This option is available if the Debit Memo action is chosen at the match rule type level. Select either Quantity or Unit Price. The system creates debit memo adjustment vouchers for merchandise - quantity and merchandise - unit price match rule types. Note. The system requires a debit memo category if you allow Debit Memo as an action at the match rule control level or on the Match Workbench on the Match Rule Type page. |
Message
Message Set Number and Message Number |
Select a valid set and message number for the exception message that appears if this rule is not met during matching. Match exception messages are stored in the message catalog by set and message number. |
View |
Click the link to view the message that appears in the exception log in the event that this match rule is not met during matching. |
Rule Applies To
The Rule Applies To group box only appears if the match rule level is Line Summary.
Association Name |
Select the document association name that is applicable to this match rule. During the Matching process, the system applies this match rule only to those document association names you defined. Options include VP (voucher and purchase order matching), VR (voucher and receiver matching), and VPR (voucher, purchase order, and receiver matching). |
See Also
Access the Match Rules - Workbench page.
Workbench Match Rule Label |
Displays the description of the rule that appears on the Matched Vouchers page, the Match Exception Workbench Details page, and the Match Overridden Workbench Details page. You can modify this field. |
Display this match rule on the workbench only if matching generates an exception for this rule |
Select to display the rule on the Match Exception Workbench Details page only if it is included in the exception record (AP_MTCH_EXCPTN). The system automatically selects this field for system match rules. |
Match Object |
Select the match objects associated with this match rule that appears as columns on the Matched Vouchers page, the Match Exception Workbench Details page, and the Match Overridden Workbench Details page. Match object options include PO, Receiver, and Voucher. |
Mapped To |
Select the field from the header summary record (AP_VCHR_HDR_SUM) or the line summary record (AP_VCHR_LN_SUM). |
Field Name |
Displays the field name based on the Match Object field and the Mapped To field values. |
Warning! The system uses the selected match objects and field names to display matching information on the Matched Vouchers page, the Match Exception Workbench Details page, and the Match Overridden Workbench Details page. If the mapping is incorrect, the matching information will not be accurate.
Access the Match Rules - Workflow page.
You can override email notification parameters and user lists defined at the match rule type level. The workflow fields on this page are similar to the workflow fields on the Match Rule Type page.
See Viewing and Updating Match Rule Types.
Access the Match Rule Control page.
When you copy individual source documents to a voucher, the voucher inherits the source document header, line, and distribution information. When you copy multiple purchase orders or multiple receipts to a voucher, the voucher inherits the first instance of the source document's header information. As an example, if you copy multiple lines from different purchase orders to a voucher, the first purchase order's header information will be copied to the voucher.
Note. The accounting template from the purchase order is copied to the voucher similar to other header fields.
Structure match rules to meet the business needs through match rule controls. Match rule controls are sets of rules that the system applies against vouchers, purchase orders, and receivers. You can define a single control ID with all of the applicable match rules or multiple match rule controls, each with a subset of applicable match rules. Match rule controls are defined by SetID. The Matching process uses the match control defined on the purchase order header to determine which match rules to apply.
Define amount or percent tolerances to override exceptions generated by the match rules. If a match exception exists, and the voucher is within the tolerances, the Matching process automatically overrides the exception.
PeopleSoft delivers match rule controls that include Standard Match rules Using Rules Tolerances, Standard Match Rules Using PO Tolerances, Standard,Debit Memo, and Basic.. To define additional match rule controls, you must understand the Matching process.
Header
Description |
Enter a short description for the match rule control. Use the long description box below the field to enter an expanded description of the match rule control. |
Currency Code |
Specify the currency code that is used to calculate the tolerance levels. |
Match Rule Configuration
Effective Date |
Enter the date that the match rules are valid. The Matching process applies these match rules to vouchers with a match due date of this date or later. |
Delete Rules |
Click to delete only the rules selected to be deleted on the Match Rules grid. |
Clear Rules |
Click to delete all match rules from the Match Rules grid. |
Populate Rules |
Click to populate the Match Rules grid with all the available match rules. This is required if you are adding a new match rule control so system match rules are automatically populated in the match rules table. You cannot delete or edit the system match rules. |
Match Rules - Rules Tab
Delete |
Select to mark the match rule for deletion. The match rule is deleted when you click the Delete button. |
|
Click to move the current row up or down by one row. This action changes the matching processing logic sequence. It also changes the display order of the match rules on the Matched Vouchers page, the Match Exception Workbench Details page, and the Match Overridden Workbench Details page. Note. The buttons are not available for system match rules. System match rules always appear first in the sequence. |
Match Rule ID (match rule identification) |
Displays the match rule associated with this match rule control. You can delete or add new match rules to the match rule control. |
If Rule is True Take Action |
Select the action to take during the Matching process when voucher lines are returned from executing the match rule SQL. The list of actions available for the match rule depends on its association to the match rule type and the match actions allowed. System match rules are display only. Possible actions include: Match: When this action is selected voucher lines returned are matched. Note. The system determines if there are any exceptions for the other voucher lines. If there is even a single exception for another voucher line, the system applies exception as the match action for the entire voucher. Debit Memo: When this action is selected voucher lines returned are marked as debit memo applicable. The system allows this option if there is a mismatch in quantity or unit price. The system waits until all match rules are executed and no exceptions exist before it creates the debit memo adjustment voucher. If you override the exceptions, the system creates the debit memo during the next Matching process if no other exceptions exist. Note. For the system to create debit memo adjustment vouchers for a vendor, you must first specify the debit memo options for vendor locations on the Debit Memo Options collapsible region on the Vendor Information - Payables Options page. Exception: When this action is selected voucher lines returned are marked as exceptions. Generally, this action is specified for match rules that check for inequality between the voucher and the purchase order and receiver. |
Continue to Next Rule |
Select the action to determine how the Matching process continues. System match rules are display only. Actions include: Always Continue: The Matching process applies the next match rule. Continue if False: The Matching process applies the next match rule for voucher lines not returned by executing the match rule SQL. Continue if True: The Matching process applies the next match rule for voucher lines if returned by executing the match rule SQL. |
Match Rules - Tolerances Tab
Under Amount |
Specify the tolerance amount to be used in the under tolerance calculation. This field is available if the Use Tolerance at Rule Control and Amount fields are selected on the Rule Definition page. |
Over Amount |
Specify the tolerance amount to be used in the over tolerance calculation. This field is available if the Use Tolerance at Rule Control and Amount fields are selected on the Rule Definition page. |
% Over Amount |
Specify the tolerance percent for the amount to be used in the over tolerance calculation. This field is available if the Use Tolerance at Rule Control and Percent fields are selected on the Rule Definition page. |
% Under Amount |
Specify the tolerance percent for the amount to be used in the under tolerance calculation. This field is available if the Use Tolerance at Rule Control and Percent fields are selected on the Rule Definition page. |
See Also
Access the Document Association Group page.
PeopleSoft delivers three document associations that include VP (voucher and purchase order matching), VR (voucher and receiver matching), and VPR (voucher, purchase order, and receiver matching). When the Matching process performs the match association, it assigns the voucher to one of the three match association records based on the match association SQL selection criteria. For example, the system assigns a voucher that has an associated PO ID with receipt required to VPR.
Specify the document association group to use in the Matching process on the Installation Options - Payables page.
Association Name |
Displays the document association group and the sequence for processing. Options include: VP: The system associates vouchers and purchase orders that do not require receipts. VR: The system associates vouchers and receivers (non purchase order receipts). VPR: The system associates vouchers, purchase orders, and receivers. You can include or exclude the delivered document associations that are not part of the business process. |
See Also
Understanding the Matching Engine
Setting Up Payables Installation Options
Access the Document Association Rules page.
As part of the Matching process, the document association process associates the appropriate purchase orders and receivers to the selected vouchers. The system associates the documents using the criteria specified on line 1. If no successful associations are found, the rules defined on line 2 apply, and so forth, until documents are associated.
|
Click to move the current row up or down by one row. This action changes the processing logic sequence for associating the documents. |
Rule |
Select a rule to apply when associating documents. Options include: Equal: The system selects the lines if the specified field on the source document (voucher) line matches exactly with the specified field on the association document (receiver). Only one association document line can be associated with the source document line. Equal Sum: The system selects the lines if the specified field on the source document line equals the sum of the specified field values on the associated document line or lines. One or more association document lines can be associated with the source document line. Select All: If any association document lines exist, the system selects the lines without comparing any rule fields. Select If One: If only one association document line exists, the system selects the line without comparing any rule fields. Sum Up To: If any association document lines exist, the system creates a running total of the specified field values and selects as many association document lines as necessary to equal the source document line field. The system concatenates the receiver BU, receiver ID, receiver line number, and the receiver ship sequence number and determines the minimum value and associates that receiver line to the voucher line. This process continues until the voucher line is completely associated or there are no more receipts. This may also result in a partial match of an associated document line. User Criteria: The system selects the lines based on the user criteria defined on the Document Association Criteria page. |
Voucher |
Select the voucher field to be used in document association processing. Options include Merch Amt (merchandise amount) and Quantity. You should only use Merch Amt for amount only purchase orders. |
Receiver |
Select the receiver field to be used in document association processing. Options include Merch Amt (merchandise amount), Qty Accept (quantity accepted), and Qty Recv (quantity received). You should only use Merch Amt for amount only purchase orders. |
Amount Only |
Select to apply the document association rule to amount only purchase orders, not regular purchase orders. Select Merch Amt (merchandise amount) for the Voucher and Receiver fields. |
User Criteria |
Click to access the Document Association Criteria page where you can enter a user-defined condition statement for the row. The Matching process uses the voucher and receiver values you define to select the receipts. This link is in bold if user criteria exists. |
See Also
Understanding the Matching Engine
To specify voucher build criteria, use the Voucher Build Criteria component (VCHR_BLD_DEFN).
This section provides an overview of how the Voucher Build Application Engine process (AP_VCHRBLD) uses voucher build criteria to build voucher records from purchase orders and receivers, and discusses how to define voucher build criteria.
See Also
When the Voucher Build process builds voucher records from purchase orders and receivers, it uses default processing logic to associate the voucher line information it has received with purchase orders and receivers. The process uses this association to help build the voucher from the receiver or purchase order data.
When you use the Quick Invoice Entry component (VCHR_QUICK_PNL) to enter basic voucher information for the Voucher Build process to build into voucher records, you can accept this default processing logic or specify a voucher build code that identifies special processing logic that you want the Voucher Build process to follow. These voucher build codes specify how the Voucher Build process finds matches between voucher line information and receivers or purchase orders. You define voucher build codes using the Voucher Build Criteria component.
See Also
Voucher Build Processing Logic for Associating Voucher Lines with Purchase Order and Receiver Lines
Page Name |
Object Name |
Navigation |
Usage |
VCHR_BLD_DEFN |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Vouchers, Voucher Build Criteria, Voucher Build Code Definition |
Define criteria that determine how the Voucher Build process creates voucher records from purchase orders and receivers. |
|
VCHR_PO_USER |
Select the User or View Only option in the User field for a purchase order criteria row on the Voucher Build Code Definition page, then click the User Criteria link in that row. |
Enter SQL statements for the user criteria you are adding. |
|
VCHR_PO_CLAUSE |
Click the Build Clause button in the purchase order criteria row on the Voucher Build Code Definition page. |
View the complete SQL statement for a purchase order criteria row on the Voucher Build Code Definition page. |
|
VCHR_RECV_USER |
Select the User or View Only option in the User field for a receiver criteria row on the Voucher Build Code Definition page, then click the User Criteria link in that row. |
Enter SQL statements for the user criteria you are adding. |
|
VCHR_RECV_CLAUSE |
Click the Build Clause button in the receiver criteria row on the Voucher Build Code Definition page. |
View the complete SQL statement for a receiver criteria row on the Voucher Build Code Definition page. |
Access the Voucher Build Code Definition page.
Note. The Voucher Build process first attempts to build the voucher using the receiver criteria you define. If the process does not find an association based upon the receiver information, then the logic proceeds to the purchase order criteria.
Note. The more specific the criteria you define, the better the system performs. If the voucher build criteria return multiple matches per voucher line, the Voucher Build process may select and build a voucher line record from the incorrect receiver or purchase order.
Purchase Order Criteria
The Voucher Build process uses the criteria that you define in this grid to find purchase orders for building voucher records. You can define multiple rows. The system looks for purchase orders using the criteria specified on the first line. If no purchase orders are found, the system uses the criteria defined on the second line, and so forth. You can use the up and down arrows in each row to change the line order.
A purchase order schedule can be associated with only one voucher line during a single Voucher Build process instance.
PO Line Opt (purchase order line option) |
Define the criteria the system uses for finding purchase orders. The available options are:
|
Item Option |
Define whether the system searches for purchase order schedules based on the item ID. The available options are: Item ID: The system uses the item setID and item ID on the voucher line. None: The system skips this field. |
Qty Option (quantity option) |
Define the criteria the system uses as a basis for finding purchase orders schedules. The available options are: None: The quantity is not used as a basis for finding purchase orders. PO Qty: The system uses the purchase order quantity and unit of measure. |
User |
To define a SQL statement for finding purchase orders, select User or View Only. The User Criteria link appears. Click this link to access the Voucher PO User page, where you can enter the SQL clause for the condition you are adding. Select None if you do not want to add a user-defined SQL clause. |
|
Click this button for any row to access the Override Session Default page, where you can view the complete SQL statement for that row, including any that you might have added. |
Receiver Criteria
The Voucher Build process uses the criteria that you define in this grid to find receivers for building voucher records. You can define multiple rows. The system looks for receivers using the criteria specified on the first line. If no receivers are found, the system uses the criteria defined on the second line, and so forth. You can use the up and down arrows in each row to change the line order.
Receiver Reference |
Define the criteria the system uses for finding receivers. The available options are: BOL (voucher bill of lading): The bill of lading on the receiver header equals the bill of lading on voucher header. Carrier ID: The carrier ID on the voucher header equals the carrier ID on receiver header. Invoice: The Voucher invoice number equals the receiver line Packing Slip ID. PackSlip: The voucher packing slip field equals the receiver line Packing Slip ID. None: The system defaults to receiver line option. |
PO Line Opt (purchase order line option) |
Define the criteria the system uses for finding purchase orders. The available options are: PO BU: The purchasing business unit on the voucher line equals the purchasing business unit on the receiver line. PO ID: The purchasing business unit and the PO ID on the voucher line equals the purchasing business unit and PO ID on the receiver line. PO Line: The purchasing business unit, PO ID, and the purchase order line number on the voucher line equals the purchasing business unit, PO ID, and the purchase order line number on the receiver line. PO Sched: The purchasing business unit, PO ID, purchase order line number, and the purchase order schedule on the voucher line equals the purchasing business unit, PO ID, purchase order line number and the purchase order schedule number on the receiver line. None:The system skips this field. |
Recv Line Opt (receiver line option) |
Define the criteria the system uses as a basis for finding receivers:
|
Item Option |
Define whether the system searches for receivers based on the item ID. The available options are: Item ID: The Item setID and the Item ID on the voucher line are used as a basis for finding receivers. None: The system skips the Item ID field. |
Qty Option (quantity option) |
Define how the system finds receivers based upon quantities. The available options are: Accepted: The accepted quantity on the receiver in the vendor's unit of measure. None: The system skips this field. Receipt: The quantity on the receiver in the vendor's unit of measure. |
User |
To define a SQL statement for finding receivers, select User or View Only. The User Criteria link appears. Click this link to access the Voucher Receiver User page, where you can enter the SQL clause for the condition you are adding. Select None if you do not want to add a user-defined SQL clause. |
|
Click the Build Criteria button for any row to access the Invoice Details page, where you can view the complete SQL statement for that row, including any that you might have added. |
To define document tolerances, use the Document Tolerance Definition component (DOC_TOL_DEFN).
This section provides an overview of document tolerance checking setup and discusses how to define document tolerances.
The Document Tolerance Checking Application Engine process (FS_DOC_TOL) enables you to edit tolerances between predecessor documents and successor documents—that is, between requisitions and purchase orders in PeopleSoft Purchasing and between purchase orders and vouchers in PeopleSoft Payables—before you run the PeopleSoft Commitment Control Budget Processor Application Engine process (FS_BP). The Document Tolerance Checking process validates that each distribution line amount on a document differs by no more than a predefined percentage (or fixed amount, depending on the setup) from the associated distribution line amount on its predecessor document.
To set up document tolerance checking:
Enable document tolerance checking by selecting the Enable Document Tolerance option on the Installation Options - Overall page and entering the ChartField whose values you use for setting up document tolerances.
The default ChartField is Fund Code.
(Optional) Require documents be approved before running the Document Tolerance Checking process on them by selecting the Document Approval Required option on the Installation Options - Overall page.
(Optional) Set up document tolerance exception override authorization for users on the Define User Preferences - Procurement - Document Tolerance Exceptions Override Authorizations page.
Define document tolerances by setID and ChartField value on the Document Tolerance Definition page.
Enable document tolerance checking for the general ledger business unit shared by the purchasing and accounts payables business units by selecting the Enable Document Tolerance option on the Procurement Controls - General Controls page.
See Also
Setting Installation Options for PeopleSoft Applications
Defining Document Tolerance Authorizations
Page Name |
Object Name |
Navigation |
Usage |
DOC_TOL_DEFN |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Document Tolerance Definition, Document Tolerance Definition |
Define document tolerances. |
Access the Document Tolerance Definition page.
Select a setID, ChartField, and ChartField value, and click the Get Tolerance Definition button to display the Tolerance Definition group box.
The tolerances to apply are:
When Encumbrance Exceeds Pre-encumbrance |
Enter the percentage and amount that the Document Tolerance Checking process uses to determine if a purchase order that exceeds a requisition fails document tolerance checking. |
When Expenditure Exceeds Encumbrance |
Enter the percentage and amount that the Document Tolerance Checking process uses to determine if a voucher that exceeds a purchase order fails document tolerance checking. |
Note. The system uses the lower value (either the percentage or amount) to calculate the tolerance. If you enter 0.00 in the Percent or Amount fields, the system calculates a zero tolerance, and the successor document must equal the predecessor document to pass document tolerance checking.