Setting Up Application-Specific Installation Options

This transaction type is used in recording the period-to-period changes in the carrying amount of the asset retirement obligation recorded as expense for income statement purposes. This field appears when you enable the Asset Retirement Obligations feature (Asset Retirement Obligations check box in the Features group box). See Accounting for Asset Retirement Obligations.

This transaction type is used when a lease payment is made in the current period for a prior period. The Prior Lease Payment (PLP) transaction type functions similarly to the Lease Payment (LPY) transaction type for accounting entry purposes. See Accounting Entry Template IDs Page

Select to enable joint venture options in Asset Management. This enables two or more business units to share ownership of an asset. The default for this feature is disabled.

Select to enable group asset processing features. The default for this feature is disabled.

Select to enable a feature that enables child component assets to inherit the remaining life of their parent asset. The default for this feature is disabled.

Select to use the Inflation Processing feature, which provides for monthly inflation adjustment transactions (transaction type INF) that adjust the asset balances (cost, period depreciation, year-to-date depreciation, and accumulated depreciation) for inflation. This is primarily used in countries other than the U.S. The default for this feature is disabled.

Select to use impairment processing, which provides for testing of assets that may meet impairment standards for your country.

Select to use revaluation processing, which provides for periodic asset cost adjustment to fair market value.

Select to create zero impairment or revaluation rows to the other books in order to maintain synchrony, even though those books do not process impairment or revaluation.

Select this option to enable functionality that converts transaction currency to base currency using the effective date that PeopleSoft Project Costing provides rather than using the asset's transaction date. This option is valid only for transactions originating in Project Costing.

Select this option to direct the accounting entries (AM_AMAEDIST) and depreciation close (AM_DPCLOSE) processes to utilize the primary book's base currency as the transaction currency. Deselect this option if you want the accounting entries and depreciation close processes to keep the original transaction currency balanced for each individual transaction. This option directly impacts PeopleSoft General Ledger journal entries.

Select this option to enable capitalization threshold processing at the system level. If this option is not enabled within installation options, any capitalization thresholds set at the business unit or profile levels are ignored. When implemented, the capitalization threshold feature enables PeopleSoft Asset Management to automatically assess the need to capitalize assets according to user-defined rules for different profiles of assets based on asset cost. The system uses the specified thresholds to determine whether to classify an asset as capital, noncapital or expense.

See PeopleSoft Asset Lifecycle Management Fundamentals, Setting Up Accounting Entry and Financial Processing for PeopleSoft Asset Management, "Defining Financial Processing for PeopleSoft Asset Management."

Select this option to enable asset retirement obligation processing. This functionality provides asset retirement obligation measurement and reporting in compliance with Financial Accounting Standards (FAS 143) for leased assets, group assets, and asset impairment.

See Accounting for Asset Retirement Obligations

Select a value to enable the interface of Project Costing (PC) detail ChartField values from the source systems into PeopleSoft Asset Management. When this check box is set properly, the ChartField values (Project, PC Business Unit, Activity, Source Type, Category, and Subcategory) are carried over to Asset Management pages and on through to General Ledger. The values are:

• Project ID Only - Retain only the Project ID

• Project ID through Activity ID - Retain Project Costing Business Unit, Project ID, and Activity ID

• Retain All – Retain all of the Project Costing ChartFields, i.e. Project Costing Business Unit, Activity ID, Resource Type, Resource Category, and Recourse Subcategory

The default value is ‘Project ID Only’, meaning that only the Project ID value from system sources will be carried over by the interface programs to Asset Management, and ultimately to General Ledger.

Primarily informational, assigned incrementally by the system. After you set this number, the next interface will be assigned a value one greater than the number you set.

Primarily informational, assigned incrementally by the system. After you set this number, the next pre-interface will be assigned a value one greater than the number you set.

This field appears when you enable the Asset Retirement Obligations feature (Asset Retirement Obligations check box in the Features group box). Select to specify the number of decimals to use for rounding in the Liability calculations.

Example: The formula for Liability is: (Expected Cash Flows Adjusted for Market Risk) * (1/(1+credit adjusted risk free rate) ^ estimated life).

This formula can produce a large number of decimal places and reporting precision requirements vary; therefore, the system uses the number as specified in this field to round the result.

Suppose that Precision for the ARO Calculation is 4. The Liability is calculated as follows:

A = Expected Cash Flows Adjusted for Market Risk

B = round((1+credit adjusted risk free rate) ^ estimated life, 4)

Liability = A * round(1/B,4)

For more information, see Accounting for Asset Retirement Obligations.

Select the default that you want to use. Account entry template IDs help speed up entry of the accounting templates by enabling you to associate more than one chart of accounts with an asset.

Specify the chunk size for the message, Get PIDATA, which is generated by Asset Management's Physical Inventory feature for usage by third party vendors. If the File Size for chunking (MB) is 8, and the total size of the message is 18 MB, the message is split into three chunks based upon the value provided in this field: the first and second chunks of 8 megabytes each and the third chunk of 2 MB. If this field is assigned a value of zero, the Tools Installation level variable (%MaxMessageSize) is used to determine the size of chunk.

This field appears when you enable the Asset Retirement Obligations feature (Asset Retirement Obligations check box in the Features group box). Enter the number of characters for the calculation of asset retirement obligations.

See Accounting for Asset Retirement Obligations

Select this option when adding assets with the Calculation Type of Remaining Value and the asset In Service date is earlier than the transaction date. If adding assets within the same fiscal year, the system calculates prior depreciation period (PDP) based on the In Service date as long as this option is selected. It is selected by default.

For example, if the fiscal year is 01/01/05 to 12/31/05, asset in service date is 03/01/05, transaction date is 05/01/05, accounting date is 05/01/05, calculation type is Remaining Value, and convention is Following Month, the system calculates PDP from 04/01/05.

Select this option when adding assets with the Calculation Type of Remaining Value and the asset In Service date is earlier than the transaction date. If adding assets within the same fiscal year, the system will calculate PDP based on the In Service date as long as this option is selected. It is selected by default.

For example, if the fiscal year is 01/01/05 to 12/31/05, asset in service date is 03/01/05, transaction date is 05/01/05, accounting date is 05/01/05, calculation type is Remaining Value, and convention is Following Month, the system calculates PDP from 04/01/05.

Select to stop the depreciation calculation when the net book value becomes less that its salvage value. This selection prevents the generation of negative depreciation.

Select this check box to enable real estate management space allocation options. The Property ID field in asset records is enabled.

Select this check box to enable IT Asset Management options.

Enter the time out threshold in seconds when interfacing with asset discovery tools.

Enter the maximum limit for rows processed in a batch.

Select to set the default for group creation to source device groups from the Asset Repository field (ARM) when creating new Software Device Groups within IT Asset Management. This default can be overridden at the time of group creation or edit.

Select this option to include Financial Impact Analysis during IT Asset Management processing for the Manage Exceptions and Assets not Reporting pagelets and detail. This option displays financial information (asset cost, net book value, and fair market value) that provides financial managers with immediate visibility of the financial impact of IT assets for proper disclosure in accordance with regulatory requirements.

Set the currency code to the base currency for Financial Impact values. This option is visible only when the Financial Impact check box is selected. The values for Financial Impact for Manage Exceptions and Assets not Reporting will be stored in the currency that is specified here. When the actual values display, they are converted to the currency that is specified within individual user preferences.

Set the rate type for Financial Impact values. This option is visible only when the Financial Impact check box is selected. The values for Financial Impact for Manage Exceptions and Assets not Reporting will be stored as specified here. When the actual values appear, they will be converted to the rate type that is specified within individual user preferences.

Assigns each temporary bill to a temporary bill invoice number identification. Define your temporary bill invoice number identification on the Invoice Number page.

If you define your Bill Entry Page Series options at a business-unit, bill-type, or bill-source level, the system uses this default ID if a page series ID is undefined for any business unit, bill type, or bill source.

Define the default number of maximum rows to limit the number of rows that appear within the scroll area at one time in bill entry or express bill entry, and define the maximum number of rows that appear in scroll areas in bill search or bill line search.

If you define search parameters that normally fetch 200 rows of billing data, for example, but you set the maximum number of rows to 40, you see 40 rows per chunk of the scroll. You can view the rest of the fetched data, 40 rows at a time, using the chunking arrows. You can also change the maximum number of rows displayed directly in bill entry, express bill entry, bill search, and bill line search.

The currency control code used for euro currency amounts throughout the Billing tables. Displays EUR by default, which is the euro currency code that the PeopleSoft system delivers in the Currency Code table. If you are not using the International Standards Organization (ISO) currency codes, change this default value to the euro currency code that you are using.

Stores the last interface ID used by external sources that pass billing transactions into the Bill Interface structure. External sources that use this ID are responsible for updating and maintaining its value every time they use a number from this field.

Enables manual invoice line numbering. The Billing invoice line numbering feature enables you to enter invoice line numbers during online bill entry. You can control invoice line numbers when you insert bill lines into a new or existing bill, delete existing bill lines, or update invoice line numbers for existing bill lines. Manual invoice line numbering only applies to bill lines entered online. It does not apply to bill lines imported through the Billing Interface.

Selecting this option activates a Manual Line Numbering flag on the Header - Info 2 page. Manual line numbering functions only if you enable the feature here and set the Manual Line Numbering flag on the bill header to ON.

Select this check box to enable online invoice rendering for the print pro forma job where the invoice form is in BI Publisher format. The invoice document will be rendered online in PDF format if the check box is selected.

Select this check box to change certain header fields on a Credit Invoice. If the check box is selected, the user can edit the fields and save them. However, a warning message that the changes are not recommended will be displayed to the user. If the check box is not selected, an error will be displayed when the user tries to change some of the fields on the Credit Invoice Header and the change will not be allowed.

The header fields that can be edited using this option are Currency, Customer, Type, Source, Cycle ID, Pay Terms, Billing Specialist and Sales person.

Select this check box to enable Process Feature Security.

Feature function security enables you to define user/role security down to the feature and field level to control access to entire features or individual fields within certain Order Management features.

In Billing, Feature Security will impact customers who use third-party taxes and use the option to Calculate Use Tax on Free Goods on the Billing Business Unit. It limits the entry and/or display of the Use tax basis and Use tax amount on Entry (Line Tax), Inquiry(Line Tax) and Interface pages.

See Defining Feature Function Security.

Determines whether links on the Bill Search pages navigate you to Standard Bill Entry, which is the default value, or Express Bill Entry.

The system populates the Lines to Add field on the Bill Entry Express - Line List page with this value.

Select a template from the list of templates available.

The express bill entry template allows you to configure the express bill entry page based on your requirement. Header sections and line tabs can be hidden. Within the line tabs, only the fields you select will be displayed. A single Accounting Distributions page is also configurable through the template.

Select to instruct the Finalization process to sequentially loop through business units when processing bills.

This option improves processing performance by looping through business units instead of processing transactions in a random order.

This option applies to the Finalization process for non-consolidated bills only. Consolidated bills can comprise of bills from multiple business units, thus eliminating the ability for the Finalization process to perform this task on consolidated bills.

Select to set the invoice date as the default date for Identifier Look Up. If the option is not selected, current date will be used for Identifier Look Up. This will allow the user to retain the functionality of using current date for all pricing.

Select to allow override of the Identifier Look Up Date. If this option is selected, the Identifier Look Up Date is displayed for each Bill Line in Bill Entry or Express Bill Entry. The field may be changed for each line.

Select this flag to update the latest identifier description on the newly created invoices. The description will be updated for the new invoices created through Copy Bill and Recurring Bill.

Define the level of detail that you pass to the system that generates your general ledger accounting entries.

If you select Business Unit or Bill Type, the GL Options page appears, where you can define the GL level options that default to all existing business units or bill types, respectively.

(Required) Define how the system passes accounting entries to your general ledger system.

If you select System in the GL Options group box, the GL Level field on this page becomes available for entry. Select one of the following values:

AR Creates GL Acct (accounting) Entries: Receivables creates accounting entries and passes them to your general ledger system. Select this value to indicate that Billing will not track accounting information, and to disable any validation requirements for values defined for each revenue line of a bill when you change the status to RDY.

BI Creates GL Acct Entries: Billing creates accounting entries and passes them to your general ledger system.

No GL Accounting Entries: You pass no accounting entries to your general ledger system.

Enables calculation and creation of accounting entries to be posted to your general ledger for future accounting periods. Use this to process bills that contain revenues to be realized in a future accounting period. This option is available for entry only if you selected BI Creates GL Acct Entries in the GL Level field.

Before you can generate deferred accounting entries, you must select this check box and define the future period accounting dates parameter at the same level that you set the GL options. For example, if you defined the GL options at the business unit level, select Enable Deferred Revenues and define the future period accounting dates parameter on the GL Options page to display by default all business units. On the Billing Definition - Business Unit 2 page, you can select values different from the defaults selected on the GL Options page. If you defined the GL options at the bill-type level, select Enable Deferred Revenues and define the future period accounting dates parameter on the GL Options page to display by default all bill types. On the Bill Type 2 page, you can select values different from the defaults selected on the GL options page.

Determines the accounting date that the system uses when you create future-dated accounting entries, and is available only when you select the Enable Deferred Revenues check box. Select First Day in Accounting Period to post deferred revenues to the proper realized income account on the first day of the realized accounting period; select Last Day in Accounting Period to post on the last day of the realized accounting period.

The calculation method used to divide and distribute deferred revenue across accounting periods. Click the Detail button to access the following valid proration method values:

(1) By Days Within Range: The system divides the number of revenue days in the period by the number of days in range.

(2) Evenly Using All Pds (periods): The system divides the total invoice line amount by the number of periods in the range. Revenue is recognized in equal portions for each accounting period, regardless of the number of days in each period.

(3) Evenly Using Mid-Period Rule: The system divides the total invoice line amount by the number of recognizable periods in the range. The number of recognizable periods is derived from applying rules to start/end days and mid-period day to determine whether the first and the last periods are recognizable or excluded entirely from the calculations.

(4) Evenly/Partial by Days: The system divides the total invoice line amount by the number of recognizable periods in the range. The number of recognizable periods is derived from applying rules to start/end days and mid-period day to determine whether the first and the last periods are recognizable or excluded entirely from the calculations.

(5) User Defined Proration Method: Available if you want to create your own proration method.

Enter the day in an accounting period that determines whether the accounting period is either fully recognizable or not recognizable at all. You can specify the mid-period day here, or allow the system to assign the date. The system defines the mid-period day by dividing the number of days in the accounting period by two and rounding to the nearest whole number. This field is available only when you select the proration method Evenly Using Mid-period Rule.

Select to enable the Online ChartField Combination Editing process for bill entry, which prevents you from passing invalid ChartField combinations to your general ledger.

Select to enable combination editing process to be done in batch for transactions that do not have ChartField inheritance turned on.

Select to enable combination editing process to be done for online transactions that do not have ChartField inheritance turned on.

Define the level of detail to pass to your accounts receivable and accounts payable system.

If you select in this group box Business Unit or Bill Type, the Default AR/AP Level page appears, where you can define the AR Level, AR distribution or AP Level option that displays by default all existing business units or bill types, respectively.

Define the level at which Billing passes open items to your receivables system. This field is available for entry only when you select System in the AR Options group box. Select from the following values:

Bill Line is AR Open Item: Billing passes each bill line as an open item in the receivables system.

Header is AR Open Item: Billing passes each bill as an open item in the receivables system.

No AR Open Items: Billing passes no open items to the receivables system.

Define the level of detail for passing AR account distribution to your accounts receivable system. This field is available for entry only when you select System in the AR Options group box. Select from the following values:

Use Header for Distribution: Send an AR account with each invoice/open item. Use this AR option only in conjunction with the AR level Header is AR Open Item or No AR Open Items.

Use Line for Distribution: Send an AR account for each line of the invoice. This is the only option available if you select the AR level Bill Line is AR Open Item.

Define the level at which PeopleSoft Billing populates the AP Voucher Staging records. Select from the following values:

Bill Line is AP Voucher: Billing generates an AP voucher for each bill line.

Header is AP Voucher: Billing generates an AP voucher for each bill header.

No AP Voucher: No voucher is created.

If this check box is selected, the contract number and bill plan as well as project information are required to be populated for the manually entered bill to interface with project costing. If the check box is deselected, only the project information is required for a manually entered bill to interface with project costing.

This option is available only if Bills Created Online option does not require contract information. This option determines if bills loaded through billing interface for system source of BBI or blank will require contract information in order to interface to project costing. This option has no impact on interface from other system sources.

Bill entry accounting templates enable you to define a selection of ChartFields that you want to work with while in the bill entry pages. If there are ChartFields that remain a constant value when you enter accounting information for your invoices, you may configure a template to exclude this ChartField. Defining an accounting template minimizes keystrokes in data entry, and keeps your page free of redundant information. Define accounting templates on the Bill Entry - Acctg Template page.

You can define your bill entry accounting template at the system, business-unit, bill-type, or bill-source level. If you select System, the Template field option becomes available for entry, where you can select a valid predefined bill entry accounting template ID to ensure that all billing activity uses the same bill entry accounting template.

If you define a bill entry accounting template at the business unit, bill type, or bill source level, enter a default template ID.

Select the date for the system to use for currency conversion by the Contracts billing process. Values include: Accounting Date and Transaction Date. This field is also used for as-incurred revenue processing (PSA_ACCTGGL) for currency conversion.

If you select Reduce by Retainage First and do not select Apply Retainage Upon Release, the system applies the reduced transaction to the limit and never applies the retainage to the limit.

If you select both Reduce by Retainage First and Apply Retainage Upon Release, the system backs the retainage out of the transaction; upon your releasing the retainage on the billing plan, the system applies the retainage to the limit.

Select to enable summary limits to be calculated when the Limits process (CA_LIMITS) runs. This option is used only for government contracts.

This option determines if certain fields and pages appear that are used with summary limits for government contracts. For example, if this option is selected, the PVN Generation Level field is shown on the Contracts Business Unit - Defaults page and the Contract Header - Billing Options page.

If this option is selected, the Limits process summarizes the excess amounts for each contract line when adding rows to PROJ_RESOURCE. The summarized rows are passed to PeopleSoft Billing with a billable (BIL) and revenue (REV) analysis type, and potentially to General Ledger and Receivables.

If this option is not selected, the Limits process does not summarize the incoming transactions when adding them to PROJ_RESOURCE. Instead, if the limit is exceeded, the process creates over the limit (OLT) and revenue over the limit (ROL) analysis type rows. In other words, if this option is not selected then the logic of the Limits process when it processes a government contract, is same as a standard contract. However, if this option is selected, for only government contracts, the Limits process summarizes incoming transactions.

For more information about the summary limits process:

See Understanding Summary Limits.

Select to enable OLT splits for contract lines with limits. When you select this option, the system splits a OLT row into one BIL line and one OLT line. This allows you to reach the limit amount exactly with the BIL line and the system places the remaining amount onto an OLT line.

If the Enable Summary Limits option is selected, this option applies only to regular contracts, not government contracts.

For contracts with a classification of Government, when the Limits process evaluates revenue transactions against revenue limits, the resulting revenue (REV) rows are either passed to the general ledger or marked as revenue over the limit (ROL) and passed to Project Costing. Select the Split to Match Limits Exactly check box to enable the system to split a REV (revenue) row into one REV line and one ROL (revenue over-the-limit) line when a revenue transaction breeches the limit defined for the contract line. This selection enables you to reach the limit amount exactly with the REV line, while passing the remaining transaction amount on to a ROL line.

Select a template that you want the system to use during the Limits Process to determine the sequence in which transactions are processed based on your business process. This list is based on the Processing Order Templates defined in the Process Order Template page.

See Setting Up a Processing Order Template.

Select if you have the Pay/Bill Management application installed on your system.

Select to defer processing from real time to batch. When you save contract lines to a contract, the system creates accounting distributions, and optionally, billing and revenue plans. In high volume cases, deferring processing of these attributes from real time to batch may speed up contract data entry. However, if you choose this selection, the contract attributes are not immediately available.

Select to enable reimbursable agreement functionality. By selecting this option, the Federal Reimbursable Agreement value appears in the drop-down list for the contract classification field when adding a new contract. While the value in the contract classification field defaults to Standard, you can select to specify the contract as a reimbursable agreement. Reimbursable agreements are subject to additional edits as described in the PeopleSoft Contracts. documentation.

Controls whether the amount field on the Contract General page is open and editable upon adding a contract or unavailable for entry. If you select this check box, the amount field on the Contract General page is unavailable for entry and the system populates the amount field.

This field appears on the page only if you select the Federal Reimbursable Agreement check box.

Select to define and apply different rates for billing and revenue calculations for rate-based contract lines associated with a fee type (cost-plus). This option is only applicable to contracts with a contract classification of Government.

Select a setID for your calendars.

Select a calendar with the lowest level of time periods for which you want to sum and display forecasted revenue.

Select a calendar with a higher level of time periods than the detail calendar, for which you want to sum and display forecasted revenue.

Select an accounting definition setID for the Journal Generator. The system uses the value in this field for streamlined revenue processing.

Select an accounting definition for fixed fee contract lines. The system uses the value in this field for streamlined revenue processing.

Select an accounting definition for rate-based contract lines. The system uses the value in this field for streamlined revenue processing.

Select an accounting definition for contract lines coming from the Transaction Billing Processor. The system uses the value in this field for streamlined revenue processing.

Displays DEPTID by default. If you have performed ChartField configuration or created another field that represents a department in your organizational structure, select the field name for your department ChartField.

Select to activate the travel services feature for the Expenses application. If the Use Travel Services check box is selected, then any time that an employee profile is added, modified, or deleted, the system sets a flag on the employee travel profile tables to indicate that a change was made.

When the Import or Export Travel Profile processes are run, the system passes employee travel profile data to the travel partner for travel profiles with the change flag (CHANGE_FLAG) on the Travel Profile table (TV_TRVL_PROF) set to Y (yes).

Activates combination editing, which prevents adding rows containing invalid combinations of ChartFields.

Links the expense system to PeopleSoft Workflow so that you can automate your expense-related business processes and send emails to employees regarding expense reports, approvals, cash advances, and so forth.

Select to enable Expenses to process amounts exceeding approved limits for expense types. When you set up an expense type, you can select a billing code parameter called Overage for that expense type.

Selecting this option activates the Overage column on the Expense Types 2 page, which allows employees to charge a different account for the amount they spend over their approved limits for the expense types. This option must be selected if you are enabling DCAA.

Select to enforce DCAA audit requirements for time reporting. When selected, Expenses enforces DCAA compliance and functionality, unless you disable DCAA processing for specific business units or employees.

See Expenses Definition - Business Unit 1 Page.

See Maintaining Employee Organizational Data.

Select to enable users to stage time reports and adjustments in Expenses and automatically call the PC_EX_TO_PC Application Engine to stage the data into the PeopleSoft Project Costing tables. If this option is disabled, the Expenses process only stages the transactions. You must then manually execute the PC_EX_TO_PC process from the Project Costing menu.

Select to prevent your expense system from using bar code scanning.

When you select this option, scanning a preprinted envelope from the Receipt Barcode Verification page populates the Receipt ID field with a value different from the Report ID field. Track receipts by placing them in an envelope printed with a bar code; track expense reports by using a bar code printed on the report itself.

If this option is not selected, the Receipt ID field on the Receipt Barcode Verification page is inactive.

When you select this option, selecting an expense report ID from the Receipt Barcode Verification page populates the Report ID field and the Receipt ID field. Therefore, you can track receipts using the same bar code as for the expense report.

Select Font to use a font stored on the client machine; select None for no bar coding.

Select an option that indicates how you want to store receipts.

Options include:

• Attachments Only – Select to indicate that you want to use the attachments feature with expense transactions.

• Both Imaging and Attachments – Select to indicate that you want to use the receipt imaging functionality and the attachment functionality with expense transactions.

• No Imaging/Attachments – Select to indicate that you are not using this feature.

• Receipt Imaging Only – Select to use the receipt imaging functionality without using the attachment functionality.

Select an option to indicate where attachments are allowed for expense transactions. Options include Header Level, Header and Line, Line Level, or No Attachments Allowed.

This field appears only when the Attachments Only or the Both Imaging and Attachments option is selected in the Option field.

Expenses uses automatic numbering to identify expense documents. This region displays the most recently used number for cash advances, expense reports, time reports, and travel authorizations.

If selected, the system searches for the designated project manager in the Project Costing system and routes the expense documents to that person.

If selected, the system searches the employee table to find the employee's manager who is the designated approver.

Select to require special or supplemental approvals following the Project Manager approval.

The system searches the employee table to find the employee's manager or supervisor who is the designated approver.

The system searches the approval tables to find the correct approver for the employee's business unit.

Select from where the employee expense reimbursements will come. This selection applies only to expense payments for employees. You still use your payables system for expense payments to other recipients, such as credit card vendors.

Select to enable email approvals for expense transactions when no risk template is defined in the system or no risk template is assigned to an approver. When a risk template is defined and assigned to an approver, the template overrides the email approval setting on the Installation Options - Expenses page.

See Setting Up Risk Templates for PeopleSoft Expenses.

Displays part of the bank table used to differentiate banks within the same country.

Select how expense payments will be made. Values are:

• Automated Clearing House: Send all expense payments to a central location for distribution to individual employee bank accounts.

• Electronic Funds Transfer: Reimbursement will occur using an electronic funds transfer or a direct deposit to the employee's bank account.

• Giro - EFT: Reimbursement will occur using an electronic fund transfer. This type of EFT is a form of payment that is supported only in Singapore.

• System Check: Reimbursement is in the form of a paper check. This is the default payment method.

Select the transaction code to use for interunit and intraunit processing of expense reports. The transaction code is associated with ChartField values for various accounting entry types.

Select the transaction code to use for interunit and intraunit processing of cash advances. The transaction code is associated with ChartField values for various accounting entry types.

Select to indicate that the account maintenance process should run during the Load External Data process. This applies to American Express, Visa, and MasterCard credit cards.

Deselect to indicate that only transaction data loads during the Load External Data process

Select to indicate that the Load External Data process automatically adds a new account to the employee profile if there are credit card numbers in the file that can be matched with an existing employee. This applies to American Express, Visa, and MasterCardV3 (xml file).

Deselect to indicate that all new credit card information is sent to the error table where the error message must be reviewed and corrected.

Click to access the Urgency (in Days) page.

Specify one of the following journal workflow approval methods for general ledger journal entries and standard budget journals:

• Approval Framework: Select this workflow methodology, which provides a configurable framework within the PeopleSoft Internet Architecture to simplify the approval process implementation. Also, select this option if you are enabling Mobile Approval Framework.

  See Understanding Configurable Workflow

  See also Understanding Mobile Approvals in General Ledger

• Virtual Approver: Select this journal approval workflow methodology, which requires the use of PeopleSoft Application Designer to define business processes, activities, business events, worklists, routings, and approval rule sets. This is the default value for the field.

  See Setting Up Journal Entry Approval in PeopleSoft Workflow

Select one of the following methods for handling journal deletion:

• Physical Delete: When using this option and you delete a journal from the Journal Entry - Lines page, the system deletes all the related journal data from all relevant journal tables. This is the default and historical method of deleting journals (same method in prior releases). With this method, the only remaining trace of the deleted journal is if audit logging was enabled for deleted journals.

• Logical Delete: When using this option and you delete a journal using the Journal Entry - Lines page, the system treats the following in the same way as the Physical Delete:

  • Removes Commitment Control data from the Commitment Control records.

  • Removes approval data, regardless of approval method (Virtual Approver or Approval Framework (AF, formerly AWE)).

  • Removes Suspense cross references.

  Unlike the Physical Delete method, the system retains the deleted journal data in the following records:

  • Journal Header (JRNL_HEADER)

  • Journal Header Attachments (JRNL_HEADER_ATT)

  • Journal Line (JRNL_LN)

  • Journal Balance (JRNL_CF_BAL_TBL)

  • Journal InterUnit Anchor (JRNL_IU_ANCHOR)

  • Journal VAT (JRNL_VAT)

  • Open Item (OPEN_ITEM_GL)

  • Journal Header Error (TSE_JHDR_FLD)

  • Journal Line Error (TSE_JLNE_FLD)

  You can view the logical deleted journal via the journal entry components (and journal inquiry components) in the same way as you would view a posted journal (Display Only mode) and the only action that you can perform is to copy the deleted journal. The system marks the logical deleted journal as follows:

  • Journal Header Status = D (Deleted).

  • Budget Header Status = N (Not Budget Checked).

  • Approval Status = N (None).

  Journal Entry - Lines Page

Enter a default process scheduler server name for the online journal edit process to use when journals are edited online. If this field is blank, the online journal edit process is scheduled without a process scheduler name. In this case, the process is typically picked up by the master scheduler and assigned to the next available process scheduler server.

Enter the time interval (in seconds) that the online PeopleCode sleeps between checking the journal edit process status. Once the journal edit process is complete, and after the system checks the status, it refreshes the component to show the edited journal. Supplying the right interval to meet your organization's needs can be an important factor in preventing a bottleneck or deadlock when multiple journal edit processes are continually submitted. The Online Journal Edit does not release the journal entry page until the previous edit process finishes. In prior releases, the interval in seconds that the PeopleCode would check the process scheduler server status was 10 seconds. This may be too long, particularly when using Commitment Control. Select the ideal number of seconds for your organization depending on your environment and your process scheduler server settings.

Select this option to receive an error when copying a journal with an inactive journal source.

Select the ChartFields to display along with the display order for journal Mobile Approvals. You can only display nine active ChartFIelds. There is no validation of these field values; be careful not to select the same ChartField to display more than once.

Select to indicate that projects are to be used as the source for calculating transaction balances on the summary, detail, and transaction pages. When Project is selected, the Reporting Analysis Group group box appears on this page. In addition, when Project is selected, you should run these processes to maintain transaction data in PROJ_RESOURCE:

• Purchasing to Project Costing process (PC_PO_TO_PC).

• Payables to Project Costing process (PC_AP_TO_PC).

• Requisitions to Project Costing process (PC_PO_TO_PC).

Select to indicate that commitment control is to be used as the source for calculating transaction balances on the summary, detail, and transaction pages. When Commitment Control is selected:

• The Third Party Cost Account field appears on this page.

• The budget ledger should include the Project Costing business unit, Project ID and, or the Activity ID, and Account.

• Budget checking must be line-by-line.

• Expense transactions come from the KK_ACTIVITY_LOG table and are stamped with an end of the month date.

If the Transaction Source is Project, select the ChartField that is defined in the PROJ_RESOURCE table. Only values with a PC transaction source are shown.

If the Transaction Source is Commitment Control, select the ChartField that is defined in the KK_TRANS_LOG table. Only values with a KK transaction source are shown.

Select the account to use to display transactions in the Third Party Cost section of the Expenditure Details Inquiry page. This is an optional field. If you leave this field blank and the transaction source is Commitment Control, the system does not separate third party costs.

Select a SetID to use for calculating actuals balances that appear on the Budget Status tab of the Award Detail and Project Detail pages.

Select the tree to use for calculating actuals balances that appear on the Budget Status tab of the Award Detail and Project Detail pages. Only account-based trees are available. If no reporting tree is selected, or if the account in the transaction data cannot be found in the reporting tree, then the transaction data is summed using UNKNOW as the budget category.

Select the analysis group for reporting sponsor expenditure balances. The Grants Sponsor Actual Costs (SPACT) analysis group appears as the default. The analysis group that is selected controls the analysis types that are included in the transaction balance calculations, which appear on the award and project summary and detail pages. The analysis types that are included in the SPACT analysis group are ACT, GLE, PAY, and SFA.

Select the analysis group for reporting sponsor encumbrance balances. The Grants Sponsor Encumbrances (SPENC) analysis group appears as the default. The analysis group that is selected controls the analysis types that are included in the transaction balance calculations, which appear on the award and project summary and detail pages. The analysis type that is included in the SPENC analysis group is COM.

Select the analysis group for reporting sponsor pre-encumbrance balances. The Grants Sponsor Requisitions (SPREQ) analysis group appears as the default. The analysis group that is selected controls the analysis types that are included in the transaction balance calculations, which appear on the award and project summary and detail pages. The analysis type that is included in the SPREQ analysis group is REQ.

Select the analysis group for reporting third-party expenditure balances. The analysis type and analysis group for third-party expenditures is user-defined. Therefore an analysis group does not appear by default.

Select the analysis group for reporting cost share expenditure balances. The Cost Sharing Analysis Group (CSTSH) analysis group appears as the default.

Select the analysis group for reporting cost share encumbrance balances. The Cost Sharing Commitment Balance (CSCOM) analysis group appears as the default.

Select the analysis group for reporting cost share pre-encumbrance balances. The Cost Sharing Requisition (CRQ) analysis group appears as the default.

Select to enable lease activation for a lease. If selected, the roles defined as an Internal Administrator and Internal Manager can activate leases. If deselected, only the roles defined as Internal Manager can activate leases.

See Defining Lease Administration Roles.

An API key needs to be generated and entered in this field to display the Google map on the Site page. The API key is generated from the following URL. http://code.google.com/apis/maps/signup.html.

Once the API key is generated and entered, the site map location will be based on the latitude and longitude for the site.

Select the value for the Manufacturing business unit that will receive changes from the PeopleSoft Product Lifecycle Management (PLM) system.

Define a value for all inbound items being added. This is useful if all inbound items will share the same UOM from the PLM system (such as EA).

Define the item life cycle status mapping for items with a status of:

• Active

• Discontinue

• Hold

This value is used when change orders are released to the PeopleSoft system. The PeopleSoft item status (SetID and business unit) is based on the affected item life cycle value for each item on a change order within the PDX XML. Therefore, any valid life cycle status that can be included on a change order sent to the PeopleSoft system must be mapped in this group box.

The LifeCycle Phase field on this page can contain commas to define a one-to-many mapping between the PeopleSoft system and the PLM system. For example, the screen shot shows how the life cycle status of Production and Preliminary are to be considered an Active item status for the PeopleSoft system item status.

Select from the following values:

Detail Offset Method: Balances each individual distribution line. Offsets to the distribution lines inherit the non-account ChartField values based on the established inheritance rules.

Summary Control: Balances the voucher rather than the individual lines.

Select to enable U.S. federal payment schedule generation for the installation. Schedule numbers must be unique, so these ranges cannot overlap. This option is for U.S. federal agencies only.

When you select this option, you must enter start and end schedule numbers for Transportation, Other, and Manual schedule types.

Define a schedule number range for various schedule payment types. Enter a beginning transportation, other, and manual number, and an end number for each to define the range for each payment schedule type.

For each payment schedule type, enter the last used payment schedule ID. The system automatically begins numbering subsequent payment schedules with the next higher number. The Pay Cycle Application Engine process (AP_APY2015) updates the last ID number.

Select to enable Prompt Payment Due Date calculation for the installation.

Select to enable CCR processing for the implementation.

Select to indicate that your Payables implementation already has updated SIC codes, and that the system should use these updated codes for CCR processing. When this check box is enabled, the system retrieves the updated SIC codes from existing vendor information. If you do not select this option, the system adds the correct, updated code information directly to the Central Contractor Registry ID Numbers page.

Select to indicate that your Payables implementation already has updated NAICS codes, and that the system should use these updated codes for CCR processing. This functionality is similar to that of the Use SIC Code Functionality field.

Select to enable late charge calculation at the installation level. If you do not select this option, all late charge information is hidden from users.

Select to have the system compare if it is more beneficial to take a discount by paying a discounted voucher early or by waiting for the due date, earning the interest income during that time.

You set up your discount evaluation parameters when you set up bank accounts and pay cycles.

Specify the document association group to use in the Matching process. The document association group defines the types of match associations and the sequence that the Matching process performs.

Select to indicate that PeopleSoft Project Portfolio Management is installed. When Project Portfolio Management is installed, project requests can begin only in Project Portfolio Management and not in Program Management.

Select to activate the project request workflow options on this page.

Select to require that project requests be approved by a funding department manager before projects can be created and assigned resources.

Select to indicate that an electronic notification is sent to the appropriate parties when a project request is created.

Select to indicate that an electronic notification is sent to the appropriate parties when a project request is updated.

Select to indicate that an electronic notification is sent to the appropriate parties when a detail plan is created for a project request.

Select to indicate that an electronic notification is sent to the appropriate parties when a project request is approved and the project can be created.

Select to indicate that an electronic notification is sent to the appropriate parties when a project request is rejected.

Select to enable program budgeting workflow.

Select to activate the Issue Management workflow options on this page.

Select to trigger workflow to the appropriate program, project, or activity owner when a user changes the issue summary on the Issue page.

Select to trigger workflow to the appropriate program, project, or activity owner when a user changes the issue priority on the Issue page.

Select to trigger workflow to the appropriate program, project, or activity owner when a user changes the issue resolution description on the Issue page.

Select to trigger workflow to the appropriate program, project, or activity owner when a user changes the issue notes on the Issue - Notes and Attachments page.

Select to trigger workflow to the appropriate program, project, or activity owner when a user changes the issue description on the Issue page.

Select to trigger workflow to the appropriate program, project, or activity owner when a user changes the issue status on the Issue page.

Select to trigger workflow to the appropriate program, project, or activity owner when a user changes the issue actual resolution date on the Issue page.

Select to trigger workflow to the appropriate program, project, or activity owner when a user adds issue attachments on the Issue - Notes and Attachments page.

Select to activate the Resource Name workflow option on this page.

Select to enable the ability for project managers to notify resources of new activity assignments from the Resources page.

Select to activate the Assigned To workflow option on this page.

Select to provide the project manager the option to trigger email notification to the resource for assigned deliverables.

Enter a setID that identifies the default control tables tableset.

Enter a file path and directory on the application server that are needed to import a third-party application and project tree into Project Costing. The Load Projects and Activities Application Engine process (PC_INTF_GEN), which is used to load projects and activities into Project Costing, stages the project tree as a flat file to this directory and invokes the Projects Tree Integration Application Engine process (PC_TREE_LOAD) to load it into Project Costing.

The default value is c:\temp\.

Enter a numeric value that specifies the last project ID issued.

Enter a numeric value that specifies the last transaction ID issued. The default value is 10000000.

Select to enable separate debit and credit entries for account processing. The default value is deselected.

Select to refresh the rows in the Project Transactions Reporting table (PC_RPO) based on the user's operator ID and the security defined for that user. If deselected, the system overwrites the Project Transactions Reporting table each time that the Report Summarization Application Engine process (PC_RPO) runs and is not subject to project-level security.

See Creating and Modifying Reports Using the Report Summarization Process.

Select to enable transorganizational accounting, which is the ability to charge transactions to an organizational entity that differs from that of the resource creating them.

Select to enable cost and revenue sharing between a resource's organization and the organization that owns the project or activity.

Select to activate Project Costing budgeting functionality including the creation of budgets through online pages or integration with Microsoft Project 2002.

When this option is selected and you create budget plans, the budgets are stored in the Project Budget Plan (PC_BUD_PLAN) and Project Budget Detail (PC_BUD_DETAIL) tables. Upon finalization of these budgets, transactions are sent to the Project Transaction table (PROJ_RESOURCE) and updated in the Summary Budget Data table (PC_BUD_SUMMARY). The Summary Budget Data table is used for delivered reporting analytics.

Deselect this option for the system to send transactions to the Project Transaction table only. The default value is deselected.

Select a default calendar to use for project budgeting. The default value is MN (monthly period calendar beginning January 1). This field is available only if you select the Enable Projects Budgeting option.

If you use Program Management, this field is used as the default budget period when you create budget detail lines by using the Program Budgeting feature. Each plan may use a different budget calendar.

Enter a default number of time periods to use in Project Costing budgeting. The default value is 12, and the field is a two–digit field. Therefore, you cannot exceed a value of 99. This field is available only if you select the Enable Projects Budgeting option.

Select to enable users to enter one or more general ledger (GL) business units, departments, and distribution percentages during the budgeting process for the system to use to distribute resource costs to budget detail rows. Deselect this option to distribute costs to budget detail rows based on the GL business unit and department from the budget items that are entered on the Resources by Activity page in Program Management.

When you select this option, the Distribute Activity Resource Amounts page appears when you click the Get Plan button on the Budget Plan page.

This field appears only if you use Program Management. The default value is option selected.

Select a default analysis group to use for cost budgets in Project Costing budgeting. The analysis group that you enter in this field appears as a default value for the Cost Budget analysis group on new projects. You can override the default value at the project level.

Select a default analysis group to use for revenue budgets in Project Costing budgeting. The analysis group that you enter in this field appears as a default value for the Revenue Budget analysis group on new projects. You can override the default value at the project level.

Select a default analysis group to use for actual cost transactions throughout the Project Costing system. The analysis group that you enter in this field appears as a default value for the Actual Cost analysis group on new projects. You can override the default value at the project level.

Select a default analysis group to use for revenue transactions throughout the Project Costing system. The analysis group that you enter in this field appears as a default value for the Actual Revenue analysis group on new projects. You can override the default value at the project level.

Select a default analysis group to use for billing transactions throughout the Project Costing system.

Select a default analysis group to represent the estimate at completion costs for a project. The analysis group that you enter in this field appears as a default value for the Forecast analysis group on new projects. You can override the default value at the project level.

Select a default analysis group that appears as the default forecast revenue analysis group on the Project Costing Definition page. The FREV analysis group is predefined and contains the same analysis types as the PSREV analysis group plus the ETB (billing estimate to complete) analysis type. Users can modify this value to any analysis group that is defined in the system.

See Analysis Groups.

Select an option that determines the calculation method that the system uses to reduce the balance of purchase requisitions as corresponding purchase orders are dispatched. Available values are:

COM Amount: Reduces purchase requisitions by the quantity and amount of corresponding purchase orders when they are dispatched.

REQ Rate: Reduces requisitions by using the committed quantity multiplied by the cost per unit on the purchase requisition. This is the default option.

REQ Total: Reverses the purchase requisition entirely when any corresponding purchase order is committed.

Select to automatically run the Purchasing Adjustment process (PC_POADJUST) when the Purchasing to Project Costing Application Engine process (PC_PO_TO_PC) runs. The Purchasing Adjustment process creates a requisition reversal row in the Project Transaction table.

Select an option that determines the calculation method that the system uses to reduce the balance of purchase requisitions as corresponding vouchers and material requests are processed. Available values are:

COM Rate: Reduces the purchase order based on the actual quantity from purchase order vouchers or material requests multiplied by the line cost per unit on the purchase order. This is the default option.

ACT Rate: Reduces the purchase order in the amount of the actual quantity and cost.

Select to automatically run the Purchasing Adjustment process when the Payables to Project Costing Application Engine process (PC_AP_TO_PC) runs. The Purchasing Adjustment process creates a purchase order reversal row in the Project Transaction table.

Select a location to store file attachments. Available values are:

File Server Select to store files on a file server. This option is a more efficient way to store files; however, it requires that you set up an FTP to the file server. This is the default option. If you select this option, you must enter an attachment directory in FTP Root field.

Database Select to store files in a database.

If you store attachments on a file server, enter the home directory where the attachment files are stored. This field appears only if you select the File Server option.

Select to enable open-period validation of newly created project transactions. The system validates the accounting date on project transactions against the Project Costing open periods or the GL open periods. If the accounting date does not fall within the open period, the system overrides the date with the closest, open-period date. The default value is deselected. Budget transactions are not validated.

Select the source against which the system validates the accounting date on project transactions. This field appears only if you select Enable Open Period Control. Available options are:

Projects Validates open periods based on a Project Costing business unit's calendar. This is the default option.

General Ledger Validates open periods based on a GL business unit calendar.

Select an analysis group that contains the analysis types that will be secured. Transaction rows of these analysis types appear as read-only rows on the Transaction List page. You can add or delete transactions that belong to secured analysis types only if you open the page in the Correct History mode.

Enter the default analysis type for revenue budget rows that are created when you run the Generate process in Proposal Management. The default value is ESB (Bill Estimate).

See Configuring Labor Defaults, Bill Options, and Security.

Enter the default analysis type for cost budget rows that are created when you run the Generate process in Proposal Management. The default value is ESC (Cost Estimate).

Enter the default analysis type to identify actual tools usage rows from Maintenance Management. The default value is TUG (Tools Usage).

See Maintenance Management Tools Usage Process.

Enter the default analysis type for importing deliverables progress log rows from PeopleSoft Services Procurement. The delivered default value is SPL.

Enter the analysis type that the system assigns to rows that are created when activity remaining work (estimated work − actual work) is multiplied by the activity cost rate. The default value is ETC. This field is available only if you use Program Management.

See Viewing and Loading Estimate to Complete Transactions.

Enter the analysis type that the system assigns to rows that are created when activity remaining work (estimated work − actual work) is multiplied by the activity bill rate. The default value is ETB. This field is available only if you use Program Management.

Select to enable status control functionality, which enables you to control transactions based on analysis types and effective dates. By using status control options, you can stop transactions from a feeder application if a project or activity status changes on the project Status page or activity Status page. The default value is deselected.

See Controlling Incoming Transactions.

Specify an analysis group that contains analysis types to use for journal entry.

Specify an analysis group that contains analysis types to use for integrating with receivables transactions.

See Understanding Transaction-Related Control Data and Setting Up Transaction-Related Information.

Specify an analysis group that contains analysis types to use for integrating with manual billing transactions.

See Understanding Transaction-Related Control Data and Setting Up Transaction-Related Information.

Select for PeopleSoft Time and Labor to publish time and labor actual PAY rows to the Project Transaction table (PROJ_RESOURCE) as soon as payroll is complete. If deselected, you must run the Time and Labor to Project Costing Application Engine process (PC_TL_TO_PC) manually to load the data into the Project Transaction table from a staging table. The default value is deselected.

See Reviewing and Loading Data to PeopleSoft Project Costing Tables.

Specify the type of date (accounting or transaction) to use for resolving rates for both pricing and funds distribution. The rates for both of these processes are effective-dated. The default value is accounting date.

Select to reprice a row that has been priced but not billed. The default value is deselected.

Select to require project transactions to be reviewed before they can be billed. You can override this option at the project type level and for individual projects. Conduct reviews by using the Project Manager Review component (PC_PM_REVIEW). The default value is deselected.

See Reviewing and Adjusting Project Cost Transactions.

Select to separate Period Of Performance exceptions on the Manager Transaction Review search page.

Select to enable the Funds Distribution feature. Use the Funds Distribution page to identify cost transactions that are eligible for distribution, and the Funds Distribution - Target Definition page to define target rows to distribute costs among funding sources.

Select to indicate that the Funds Distribution (PC_FND_DIST) process should automatically run when processing incoming transactions from the feeder systems that send transactions to Project Costing. This includes transactions created from the Add Transactions page and the Third Party Loader process. When this option is selected, the Funds Distribution process assumes that the Apply Burden Rates and the Run Pricing After Funds Distribution options are enabled on the Funds Distribution run control page.

This option is only enabled if the Enable Funds Distribution option is selected.

Select to allow a threshold amount to be modified on the Distribution Rules page after costs have been processed against the threshold. The threshold may not be lowered below the distributed amount.

Deselect to indicate that threshold amounts can not be changed once costs have been processed against the threshold.

This option is only enabled if the Enable Funds Distribution option is selected.

Select to indicate that the funding source rules can be grouped manually. Each target definition can be associated to a set of rules.

Deselect to indicate that each funding source rule will be associated with separate target definition.

This option can be overridden at the project costing business unit level

This option is only enabled if the Enable Funds Distribution option is selected.

Select to display a Reversals check box on the Funds Distribution - Target page. Reversal transactions are generated to send through budget checking and balance general ledger entries.

Deselect to hide a Reversals check box on the Funds Distribution - Target page.

This option is only enabled if the Enable Funds Distribution option is selected.

Select the analysis type that should have the Balancing check box automatically selected when defining Funds Distribution target rows.

Select to invoke the summarization process during the Expenses to Project Costing Integration process (PC_EX_TO_PC).

Select to invoke the summarization process during the General Ledger to Project Costing Integration process (PC_GL_TO_PC).

Select to invoke the summarization process during the Third Party Loader to Project Costing Integration processes.

Select to invoke the summarization process during the Pricing Engine process (PC_PRICING).

Select to indicate that the Variance Pricing process should use the Summarization engine to net target and history rows.

Deselect to indicate that the Variance Pricing process should net rows using a fixed set of fields. These fields are: Business Unit, Project, Activity, Resource ID From, Analysis Type, Resource Type, Category, Subcategory, Contract Number, Contract Line Number, Unit of Measure, General Ledger Business Unit, Account, Department ID, Operating Unit, Product, Fund Code, Class, Program, Budget Reference, Affiliate, Affiliate Intra1, Affiliate Intra2, ChartField1, ChartField2, ChartField3, Foreign Currency, Currency Code, and Currency Effective Date.

A Summarization Template for the Variance Pricing product code must also be set up. Otherwise, the fixed set of fields are used.

Select to invoke the summarization process during the Time and Labor to Project Costing Integration process (PC_TL_TO_PC).

Select to invoke the summarization process during the Accounts Payable to Project Costing Integration process (PC_AP_TO_PC), the Purchasing to Project Costing Integration process (PC_PO_TO_PC), and the Purchasing Adjustment Integration process (PC_POADJUST).

Select the date option that the system uses to process time reports that are created in Expenses and brought into Project Costing. Available options are:

Date Under Report: The dates entered on time reports when they are created in Expenses are the same dates that the system uses when the time reports are imported into Project Costing. This is the default value.

Period End Date: The time report end date determines the accounting period to which the system charges time in Project Costing. This setting is particularly important when the reporting period spans the end of one accounting period and the beginning another accounting period. For example, assume that you use monthly accounting periods and enter weekly time reports. If a month ends in the middle of a week, and therefore the reporting period spans the end and beginning of two accounting periods, the time is charged in Project Costing to the accounting period for which the reporting period ended—the latter of the two accounting periods.

See Setting Up Time and Expense ChartFields for PeopleSoft Project Costing.

Select to group and summarize the transactions to send to Asset Management by the cost types of the rows in the Project Transaction table instead of the cost type specified on the Define Assets page. The default value is deselected.

See Define Assets Page.

Select to group and summarize the transactions to send to Asset Management by the department ID of the rows in the Project Transaction table instead of the department specified on the Define Assets page. The default value is selected.

Select to require approval of asset capitalization transactions before they are sent to the Asset Management Loader tables. This option applies to assets that you create or adjust in Project Costing. It does not apply to asset retirement transactions.

Deselect the option to enable optional approval of assets. If approval is optional, assets with statuses of New and Approved are eligible to be sent to Asset Management. The default value is deselected.

See Reviewing and Approving Assets.

Select this option in a single currency environment if you have no need to send transaction currency detail to Asset Management when you capitalize assets. The capitalization processes ignore the five currency fields—Transaction Currency Code, Currency Effective Date, Rate Multiplier, Rate Divisor, and Rate Type—to achieve a greater level of summarization.

Deselect this option if you want to send currency transaction detail to Asset Management when you capitalize assets.

See Currency Summary Options.

Select the analysis group from which to assign an analysis type for budget rows that you import from Microsoft Project. The analysis type from this group is later selected during the Microsoft Project integration process.

See Understanding Integration of PeopleSoft Project Costing with Microsoft Project.

Select the analysis group by which all transaction rows with an analysis type belonging to the group will be sent from Project Costing to Microsoft Project. Only transactions with analysis types in the specified analysis group will be synchronized between Project Costing and Microsoft Project.

Select an analysis type to assign to work transactions (time entries) that are sent from Microsoft Project to the Project Transaction table. The default value is TLX.

Select the unit of measure for budget rows brought into Project Costing from Microsoft Project. The default setting is hours (MHR).

Displays the last used file number. The system automatically numbers the files with the next sequential number.

Displays the maximum quantity to be used for quantity break price calculations.

Select the checkbox to make the user defined fields available on the procurement transactions

Enter the maximum number of rows that you want returned when you search for purchase order-related information.

Enter the maximum number of rows that you want returned when you search for requisition-related information.

Enter the maximum number of rows that you want returned when you search for purchase order approval information.

Enter the maximum number of rows that you want returned when you search for requisition approval information.

Enter the maximum number of rows that you want returned when you search for requisitions that have been selected for purchase orders.

Enter the maximum number of rows that you want returned when you search for purchase orders that have been closed with a short amount.

Enter the maximum number of rows that you want returned when you search for contract information.

Select the method for the system to use when purchase order lines exceed the chunk size. Values include:

• Display Advanced Search Page: Select to have the system display the Advanced Search page when you select to open a purchase order with more lines than the maximum row limit. The system will not load any lines until you define search criteria for the purchase order lines.

• Load First Set of Lines: Select to have the system display purchase orders based on the chunking rule. The system loads the first chunk of purchase order lines and displays the Maintain Purchase Order page. This value is the default value for this field.

Select the method for the system to use when requisition lines exceed the chunk size. The values for purchase orders also apply to requisitions.

Displays the number of the last requisition loader request processed by the system. At initial setup, this is probably zero. As the Purchasing Requisition Loader Application Engine process (PO_REQLOAD) handles requests, it automatically numbers them beginning with the number that you enter here.

Enter the lowest number that you want to use to identify requisition loader requests.

Enter the highest number that you want to use to identify requisition loader requests. When the requisition loader reaches this number, it resets request numbering to the number that you enter in Min Loader ID.

Enter the maximum number of lines that can be loaded in a requisition loader process instance. Lines that exceed this number are ignored.

Enter the number of digits that appear for the procurement card.

Enter the maximum number of procurement card transactions that are created for a voucher.

Select this check box if you want to provide the ability to automatically create the bill to customer when defining a vendor using the Vendor Information - Identifying Information page. When you select this check box, the Create Bill-To Customer group box appears on the Vendor Information - Identifying Information page selected by default so that you can quickly create the bill to customer with default information.

Select this check box to use Oracle's XML Publisher (BI Publisher) to format and print purchase orders during the dispatch process. Oracle BI Publisher is a Java-based product within the Oracle Fusion Middleware family used for reporting. This check box impacts the dispatch processes within PeopleSoft Purchasing and PeopleSoft eProcurement. If this check box is not selected, then the system uses SQR to format and print purchase orders.

Select to have the process subtract all identified payments from the customer's outstanding balance.

Select to have the process subtract any express deposit, worksheet, or applied payment associated with a customer item from the outstanding balance.

Select to have the process subtract the balance due on items in dispute from the outstanding balance.

Select to establish a new action plan for a collection (COLL) condition when a customer that already has a collection action plan violates a collection rule with a higher priority.

Select if you want to monitor the collection (COLL), entry type/reason code (ETRC), key statistics exceeded (KSTE), and large amount coming due (LACD) conditions by business unit. The Condition Monitor treats each business unit and collection customer combination as a separate customer.

Business unit monitoring also affects the assignment of the action owner for these conditions. The Condition Monitor groups all open items for the business unit and collection customer combination together. If all these transactions have the same value in the action owner field, it uses that value for the assigned action owner. Otherwise, it assigns the owner based on the collection customer.

Here is an example:

Customer FRA01 has transactions in business unit FRA02 and FRA05. You assigned collector DKB to this customer. All of the transactions for this customer in the FRA02 business unit are assigned to collector JKB. All of the transactions in the FRA05 business unit are assigned to collector MLM. If the customer violates the collection criteria in both business units, the Condition Monitor creates two action plans: one for FRA02/FRA01 that it assigns to collector JKB and one for FRA05/FRA01 that it assigns to collector MLM. However, if some of the transactions in the FRA02 business unit are assigned to collector JKB and some are assigned to collector CCC, then the action plan for FRA02/FRA01 will be assigned to the collector for the customer, which is DKB.

Select the user ID for the individual in your organization who you want to be the action owner for action list items when the assigned action owner does not have a user ID. You must designate a default owner before you can define conditions for the Condition Monitor process.

Enter the maximum number of lines to be displayed on the sales order or quote before chunking is used.

Enter the maximum number of schedules per order line displayed before chunking is used.

Enter the maximum number of schedules to be priced online. If the sales order number of schedules exceeds the maximum, you are directed to the Order Repricing process (OM_REPRICE).

Enter the maximum number of rows that can be sources before chunking is used.

Select to enable PeopleSoft Search Framework to enhance searching capabilities for customers and products during sales order entry.

See PeopleTools: PeopleTools Global Technology, Translating Application Definitions

Select to process claimbacks.

Select to have the system prompt you to save a chunk. If deselected, the system automatically saves your order when you navigate from chunk to chunk.

Select to enable the system to use feature function security.

Enter the maximum number of lines to be displayed on the buying agreement before chunking is used.

Enter the maximum number of lines to be displayed on the Order Hold Workbench. The rows that display in the Order Hold Workbench depends on the search criteria for the type of rows (header, line, or schedule) that are selected and counted as the maximum.

Select the default priority, or importance, to appear on new service orders. Available values are from the Resource Management Priority table (RS_PRIORITY_TBL). Priority is used for information and reporting. It does not control any service order processing.

Enter the field name that represents the organizational unit, which categorizes all resources that are managed in Resource Management. The organizational unit field is used:

• When users select a service order owning organization.

• To define resource groups that are used to direct a search for resources to different parts of the organization.

• To define resource groups that appear on the Staffing Workbench - Manage Utilization page.

• To indicate which organizational unit to analyze on reports for scheduled utilization, unassigned resources, assignments ending, assignments listing, chart resource schedules, and average staffing time.

• To match resource organizational units with service order owning organizations for resources to be evaluated for service orders by the Resource Match engine and Resource Optimization feature.

Most organizations use departments to organize resources into logical groupings by functional area, in which case the organization field name value is DEPTID.

Enter the application record name that defines the organizational unit field.

If you use department as the organizational unit field, the organizational unit record is DEPT_TBL, which defines the Department (DEPTID) field.

Enter the name of the tree that contains the organizational unit arranged in a hierarchical business structure. The tree represents the organizational structure in the application. The organizational unit tree is available in Resource Management when users:

• Select an owning organization for individual service orders or service order templates, or as a service order default owning organization.

• Define resource groups.

• Indicate which organizational unit to analyze on reports.

The organizational unit tree must be one whose foundation is a tree structure built on the record specified in the Organizational Unit Record field.

Enter the name of the record that keeps track of the organizational unit to which each resource belongs.

If the organizational unit field is the Department field (DEPTID), you can use the Employee-Organization record RS_ORGEMPLBR_VW as delivered. The Employee-Organization record is a view of the Job record (JOB) that identifies the department for every employee. The Job record is the PeopleSoft HRMS record that identifies the department, location, job code, and a variety of other attributes for every employee in the organization.

This field is not used by Resource Management at this time. You can accept the default value, leave the field blank, or enter a value that can be used in the future if you create a configuration that uses a default billing rate.

Enter the currency code that is used by the Resource Optimization feature to convert all resource billing rates into one currency for comparison.

Select the rate type from the Market Rate Data Types table (RT_TYPE_TBL) that determines the default conversion rate for converting resource billing rates and currency codes.

This field is not used by Resource Management at this time. You can enter a value that can be used in the future if you create a configuration that uses a default billing rate unit of measure.

Select task categories and corresponding chart colors to appear on the Resource Schedule chart if you enter the chart from the:

• Assign Resource page.

• My Assignments Workbench - Assignments page.

• Staffing Workbench - Manage Utilization page, if you do not specify task categories and color options on the Utilization options page.

  See Specifying Staffing Workbench and Resource Utilization Options.

• Resources page in Program Management.

• Assignments Ending detail report.

Select the nonassignment (appointment) task categories that can be modified by managers with access to resource schedules. This selection applies to managers with access to the Monthly Schedule page.

Select the nonassignment task categories that can be modified by resources in their own resource schedules.

Select the nonassignment task categories that trigger a notification message to the resource and the resource manager if a manager with authority to modify resource schedules changes a task in the specified category in the resource schedule.

Select the nonassignment task categories that trigger a notification message to the resource manager if a resource changes a task in the specified category in the resource schedule.

Displays all nonassignment task category names and descriptions.

Select this check box to activate the Resource Management email notification workflow feature to notify the resource or resource manager of changes to selected task categories.

Select the Outlook desktop calendar application to synchronize with Resource Management resource schedules, or leave the field blank.

You must first separately implement Microsoft Exchange or Microsoft Outlook, and set up your PeopleSoft application to integrate with it, before any synchronization functions can occur.

Select this option to skip resource holidays that are on the resource's holiday schedule when you create assignments. An assignment is created for a specified date range; however, if you select this option, and there are holidays from the resource's holiday schedule within the date range of the assignment, the system will not schedule the assignment on those dates on the resource's calendar.

Deselect this option to schedule assignments on every working day within the assignment date range, including resource holidays.

This option appears only if Program Management is not installed. If Program Management is installed, the system always skips holidays when creating Resource Management assignments.

Select a task category that appears as the default category value on:

• Resource assignments that you create from the Express Search page in Resource Management.

• Service order resource requests that originate in Resource Management.

• The Resource Detail page in Program Management.

Users can change the default value on these pages.

Available values are based on task categories that have the Use for Assignment option selected on the Task Categories page in Resource Management.

Select to enable the integration between Resource Management and Services Procurement that allows user to initiate Services Procurement service requisitions from Resource Management to fulfill resource requests, and navigate to requisitions to make updates.

If you do not select this option, the Find External Resource icon does not appear on the Staffing Workbench - Fulfill Orders page.

Select this option for the project manager to be used as the requestor name for Services Procurement service requisitions that initiate in Resource Management. If you do not select this option, users are prompted to enter the name of the requestor when initiating a service requisition.

Select a business unit to serve as the default HR business unit for new non-employee data records (EMPLIDs) that are created for Services Procurement person IDs. This is a required field on the person's data record.

Select the default department. This is a required field on the person's data record.

Select a default value for each field. These are not required fields on the person's data record.

Enter a default value for standard hours per work day. Standard hours are used by the Resource Match engine to calculate Availability fit scores for each combination of eligible resource-and-open resource request.

Select the default standard work period. Standard work period is used by the Resource Match engine to calculate Availability fit scores for each combination of eligible resource-and-open resource request.

Select a default holiday schedule to populate resource schedules that are created for new non-employee data records (EMPLIDs).

Enter up to three characters to serve as the prefix for new resource employee IDs that are created for Services Procurement person IDs. When a user establishes a person ID as a non-employee resource, the employee ID default value is a concatenation of this prefix and the Last Emplid Used field value.

Enter a number, up to eight characters, to serve—along with the Employee ID Prefix field value—as the last system-generated employee ID that is created for a Services Procurement person ID.

For example, if the employee ID prefix is EXT and the last employee ID used is 500, the system assigns an employee ID of EXT00000501 to the next person ID that is converted to a resource in Resource Management.

Select this option to secure the resource's job code field

Select this option to secure the Address lines 1 through 4 for the resource.

Select this option to secure the city or town of the resource

Select this option to secure the post code/zip code of the resource

Select this option to secure the phone number when Phone Type = Home

Select this option to secure the passport numbers and Visa Numbers

Select this option to secure the entire Areas of Specialty section

Select this option to secure the entire Licenses and Certificates section

Select this option to secure the entire Test Results section

Select the check boxes that correspond to the resource profile sections that you want to appear on the Resource Profile review-only summary page. Sections that are not selected are hidden from the summary page, but remain visible in the profile to users with security permission to update profiles.

Select the unit of measure that determines whether the effort is in hours or days. If you select Hours, all of the capacity planning data appears with the primary display and update fields in hours.

Enter the default region setID that is used in Capacity Planning - Consolidated Scenario analysis.

Enter the default region code that is used in Capacity Planning - Consolidated Scenario analysis. This region is used for:

• Adding or removing supply in a Combined Scenario analysis.

  Note: You can add or remove capacity at a high level without specifying region. In that case, the default region code will be used.

• Calculating full-time resources in the demand forecast.

• Calculating full-time resources for demand in a Combined Scenario analysis.

Displays the number of hours that equal one full work day. The standard hours per work day are specified on the Resource Setup - Common Installation Options page.

See Setting Up Resources.

Enter the number of work days that equal one full month for the purpose of planning capacity.

Enter the number of days per month that equal one full-time resource for the purpose of planning capacity. Typically this value is the same as the standard work days per month.

Select this check box to populate the resource calendar whenever an assignment is created. This option is only used when Staffing Front Office is installed.

Select this check box to enable the system to change the ship to labels to worksite for ship-to addresses and ship-to customers within the Customer Information component.

Select this check box to enable the system to track resource request quantity changes.

Select this check box to enable the system to track assignment date changes.

Select to enable users with the appropriate permissions to reactivate previously closed assignments. If you select this option, you cannot select the Allow Additional Assignments option. Once you save the page, you cannot change this option.

Select to allow the creation of additional assignments. If you select this option, you cannot select the Allow Reactivate Closed Assign option. Once you save the page, you cannot change this option.

Select this check box to have the system automatically create an additional job for every new assignment for hourly employees. The system attempts to reuse job records unless you select this check box.

Select this check box to have the system automatically create an additional job for every new assignment for salaried employees. The system attempts to reuse job records unless you select this check box.

Enter an assignment event type. This event type provides additional functionality from the Candidate Summary page in the Recruiting Funnel. When you click the assignment event on this page, the system brings up the Assignment Header page.

See Candidate Summary Page

Enter a hire event type. This event type provides additional functionality from the Candidate Summary page in the Recruiting Funnel. When you click the hire event on this page, the system brings up the Applicant – Contact Information page. From here, you can hire the applicant as an employee or a non-employee.

See Candidate Summary Page

Enter the default department setID that is to be automatically associated with the candidates who use the Apply Online component. All applicants in the system must have a department. However, this information is not captured in the component used by candidates who use the Apply Online functionality.

Enter the default department ID that is to be automatically associated with the candidates who use the Apply Online component. All applicants in the system must have a department. However, this is not an available field for candidates using the Apply Online functionality.

Select the default attachment type that the system automatically associates with the resumes attached through the Apply Online component.

Select an option that determines whether candidates are required to register. Options include:

Optional Registration: Candidates are not required to register but are able to if they want to.

Registration Not Required: Candidates are not required to login to the system prior to applying.

Registration Required: Candidates must register prior to accessing the Apply Online component.

Select an option that the system uses to determine the applicant status after the candidates update their records. Options include: Applicant Active and Applicant Pending.

Select to indicate that your organization used a resume parsing provider.

Select the resume parsing provider. Suppliers must be setup through the Open Integration Framework before they can be selected here.

See PeopleSoft Staffing Front Officeproduct documentation. "Structuring PeopleSoft Staffing Front Office Processing Environment," Understanding Resume Parsing.

Select the language of the resumes being loaded.

Select this check box to indicate that you are using a job board distribution provider.

Select job board distributor. Distributors must be setup through the Open Integration Framework before they can be selected here.

Enter a valid URL for the Job Board Distributor.

Select to enable displaying award details to bidders. You can choose to:

• Display all bids

• Display bid scores

• Display bid's total bid price

• Display bid's bid factors

You can override the values set here on the Award Details page for each sourcing event.

Select to allow posting of events to third-party sites. When selected, you will be able to configure third party integration of events for a Sourcing Business Unit.

Select to enable the use of Supplier Contracts to create an RFx document.

Select if the bidder is allowed to edit the RFx document.

Entering information here enables event creator to chat with bidders using the MultiChannel Framework chat capabilities.

If selected, the system automatically creates users as MCF agents upon posting their first sourcing event. Bidders can then request to chat with the event creator from the bid response pages.

Complete the MultiChannel Framework default only if you have selected the Automatically create Agent profiles for Event Creators with these defaults check box.

A logical queue is an application-level queue that receives work requests (tasks) relating to an application area, such as chat requests regarding sales information, and routes them to agents capable of handling the work. For example, you might configure a logical queue called SOURCING for bidder issues.

The system randomly selects this queue so that the tasks in a logical queue are distributed by the framework among all available physical queues for scalability. For example, the SOURCING queue could be serviced by two MCF clusters across two physical queues: SOURCING1 and SOURCING2.

Specify the minimum agent skill required to handle this task.

The queue server assigns this task type to an available agent with the lowest skill level on that queue greater than or equal to the skill level required by the task.

The minimum value is 0, and there is no maximum value.

The value specified here can be overridden in the EnQueue() or InitChat() built-in function call.

Select the maximum load that this agent can be assigned before tasks are held or assigned to other agents. This is a required field.

The cost of each accepted task is added to the agent's current workload. A task is not assigned to an agent if its cost pushes the agent's current workload over the maximum.

Use to create default chat templates for each agent's profile. Chat templates are used to send responses to bidders. Values include: Abandon, Accept, Deny, End, Forward, and Other. For each response ID, you can add a response name, response description, and response text.

Use to define one or more default presence states for each agent's profile. Options include: Available and Unavailable. Add a presence description that appears when checking to see if an agent is available.

Enter the default navigational path to the server on which you create temporary server-side files. Use this application server directory, for example, when generating authored documents. The system generates the temporary document on the application server before transferring it to the FTP server. You might want to select a directory such as c:\temp, which exists on Windows application servers.

Select to enable the document administrator to run a server-side comparison of the current contract against a regenerated version or refreshed version of the contract. The comparison displays the differences and is for information purposes only.

Select to enable the generation of a document during the dispatch process. You select this check box in case a supplier does not use Microsoft Word 2003 and cannot read .xml version of the file.

Enter a path name for the default Windows server that will serve as a temporary location for document processing for server-side comparisons and document rendering of .XML. An example of a temporary location might be c:\temp.

Enter a default Windows server URL and a port number that define the location of the port where documents are processed on the Windows server. You must also have Microsoft Word 2003 installed on the Windows server for this function to work properly.

Enter the number of returned rows that you want to retrieve and display when you perform a search. If you do not enter a value, the system retrieves 20 rows at a time.

Select to indicate that you want to include syndication as part of the contract process. When you select this check box, the system includes the Syndication tab on the Contract Entry page.

If you use contract syndication and the Allow Contract Syndication check box is deselected later, the syndication features appear only for contracts that have already been syndicated. For contracts that have not been syndicated, the system hides the syndication features.

Select a default node to which contracts can be syndicated. The system cannot syndicate a contract until you define a subscriber node. This subscriber node is supplied as a default value on the supplier contract if Allow Contract Syndication has been selected.

If a node is not defined at the header level, the system generates a message during processing. If you run syndication as a batch process, only those contracts that have nodes defined can be selected for processing.

Select to include purchase order defaults as part of the syndicated contracts. The defaults include header and shipping information, and you click the PO Defaults link on the Contract page to view them.

Select to include miscellaneous charges in the syndicated contract. You can add miscellaneous charges to purchase orders in addition to sales and use taxes and value-added taxes.

Select to include milestone information in syndicated contracts. Milestones are points in a contract cycle, such as a specified period of time or a percentage of contract fulfillment, at which an approval or reevaluation is made by contract participants. Often, partial compensation is linked to a milestone. Supplier Contract Management verifies the release of milestone lines for merchandise amount changes.

Select to include syndicated shipping schedules in syndicated contract information. The system verifies that the line quantity on the shipping template is greater than the minimum line quantity.

Select to include syndicated distributions in syndicated contract information. During syndication, the system processes distribution percentages and amounts and verifies that the distribution amount does not exceed the contract line amount.

When you protect bind values, and the system generates authored documents, Microsoft Word 2003 places a protection tag around each transactional or wizard bind value in the document. This can be useful if you do not want bind values to be readily changed within an authored document, but want them primarily controlled by wizard or transactional changes within the PeopleSoft system. When Microsoft Word protection is in place, bind values cannot be easily changed. Controls for overriding protection exist within Microsoft Word.

Select to make Track Changes the default option when the system generates documents. If you do not select this check box, users can manually set the Track Changes feature in Microsoft Word.

Select the default method by which you want the system to log errors when it generates a contract document. The system provides the value as a default value to document configurators when you first create them. Two levels of logging are available. Select Details to indicate that the system should log full error details during the document generation process. Full logging can slow the generation process, but is useful for debugging and testing wizard paths when you create new configurators. Full logging also validates bind variables that the system uses within a configurator and validates the expansion of a configurator by checking rules that are evaluated during document generation.

Select Log Warnings and Wizard to log only warnings, such as missing bind values and the summary wizard history for a given document generation. You should use this setting after a configurator is made available for general use.

Select to indicate that approvals are required for clauses. When you select this check box, the system enables workflow approvals for clauses. If you do not select this check box, the person maintaining the clause can set the clause status to approved.

Select to indicate that approvals are required for documents. If you select this check box, the system requires the document administrator to submit documents for approval. If you do not select this check box, the document administrator can click the Approve button to approve the document for final dispatch to supplier for signature.

Select to indicate that if a document is edited after being approved, it must then be reapproved. Depending on organization internal controls for contract documents, this may or may not be required.

Select the method that the system should use to notify collaborators when they are listed as collaborators in the document collaboration process. Valid Values are:

Email: Select to use an email notice to alert collaborators that a collaboration is waiting for them.

Email and Worklist: Select to notify collaborators using both notification methods.

None: Select to indicate that a notification is not required.

User Preference: Select to use a combination of generic templates, which include user roles and PeopleCode application classes, to notify collaborators for clause and document approvals.

Worklist: Select to use an automated to-do list that routes work items. From the worklist, collaborators can directly access the pages that they need in order to perform the next action for a document, and then return to the worklist for another item.

Select the generic template that the system should use in routing documents for collaboration. This template controls the format of information for email notifications when the system routes a document for collaboration.

Predefined values are:

CS_ClsRteApproval: Route for Approval

CS_ClsRteReview: Route for Review

CS_ClsApprove: On Final Approve

CS_ClsDeny: On Final Deny

CS_ClsTimeout: On Timeout

Select the template that the system should use when collaboration has been completed for a document. The template controls the information that appears in the email to the administrator when collaboration is completed.

Enter the (EnterpriseOne) JD Edwards database from which the data is imported.

Enter the password required for logging in the (EnterpriseOne) JD Edwards database specified in the DBID field.

Enter the (EnterpriseOne) JD Edwards Integration Server.

Select this check box to enable a security measure that requires the user to reenter the password when dispatching payments from the Dispatch Payments page.

Enter the name of the server to run the Dispatch Payment Application Engine process (PMT_DISPATCH). Once entered, Process Scheduler only runs the Dispatch Payment Application Engine process on the selected server, rather than the next available server. This option is available to accommodate the transmission of security-sensitive payment files.

Enter the number of payments allowed in a PAYMENT_REQUEST application message passed from source systems, such as Payables, to Financial Gateway. Increasing the number of payments per message requires fewer messages to be sent, but it requires more memory to process—a system limitation that can affect performance. The default value is 1,500 payments per message.