This chapter provides an overview of PeopleSoft Pay/Bill Management table setup and discusses how to:
Set up related applications.
Define installation options.
Set up user preferences.
Set up security.
To implement Pay/Bill Management, you must first design and establish your system's business structure. Determine the best way to map your new system to your organization's business structures, practices, and procedures.
PeopleSoft applications rely on tables to store business transactions and the structure and processing rules that drive your system. Start by setting up the basic framework by using the pages in PeopleTools:
The PeopleSoft system builds these pages over core tables, which are delivered and shared among many PeopleSoft applications.
Set up these tables by using online pages.
If you use other PeopleSoft applications, such as those in Human Resources Management (PeopleSoft HRMS) or PeopleSoft Financials, the system administrator may have defined some of the framework already.
Work closely with administrators from these areas as you prepare to populate these tables.
Because of the relational design of PeopleSoft applications, the order in which you make important decisions about using the application is not always the order in which you use the online pages to set up the database tables.
Certain tables work as a group when you make processing or implementation decisions; therefore, you must establish data in some tables before others.
Pay/Bill Management integrates with many PeopleSoft applications. Set up tables in the following PeopleSoft applications before you set up tables that are specific to Pay/Bill-Management:
Time and Labor
Project Costing
Contracts
Billing
Payables
Payroll for North America
Global Payroll
Human Resources
Necessary table setup for each application, as well as integration, application messaging, and component interfaces, is discussed in other chapters in this PeopleBook.
See Also
Getting Started with PeopleSoft Enterprise Pay/Bill Management
Using Enterprise Integration Points
Integration with Other PeopleSoft Applications
When setting up Time and Labor, keep the following in mind:
To enter time in Pay/Bill Management, you can use only the PeopleSoft Time and Labor rapid time templates that contain the following fields: TRC (time reporting code), PC BU (Project Costing business unit), Project ID, Activity ID, Override Rate, and Billable Indicator.
Do not use task entity codes and do not use combination codes in your rapid time templates.
Defining time collection devices is optional.
Ensure that you defined the task template correctly for all elements for which you enter data.
Configure your HR departments so that they coincide in value with the corresponding General Ledger departments. That is a design assumption in Pay/Bill Management, especially if the Cost Sharing functionality in Project Costing is used.
When setting up Project Costing, make sure that you:
Enable the application messages for estimates and actuals on the Projects Options page.
Select the Time and Labor Actuals, Time and Labor Estimates, Time and Labor Contractor, and Time and Labor for Billing check boxes in the Time and Labor Interface group box on the Projects Options page.
Note. Ensure that you select the Project and Activity Team check box for each Project Costing business unit.
Enable Project Costing integration with Time and Labor on the Installation Options - Projects Integration page.
Select the Load Time Automatically check box in the Time and Labor Integration region of this page.
When configuring project types, make sure that the project types referred to in the Pay/Bill Management project profiles do not have default rate sets associated with them, otherwise, the system will not be able to automatically create contract custom rate sets for the temporary assignments.
For each Project Costing business unit, ensure that you configure the Program Management business unit options to have the Activity Date Cascade Calculations option set to Manual.
When setting up Contracts, and when configuring the product codes to be used by your contract profiles, ensure that temporary orders use rate-based products and career orders use amount-based products. The products should not be configurable as renewable or as third-party products. The products should not be configured to use templates for billing plans, billing plan details, revenue plans, or renewal plans.
In addition, when you select Products, Identify Product Details, Definition to configure products, ensure that you enter Contracts Only in the Product Use field. Then select the Contracts Options tab and enter a Price Type of Amount, and leave the four fields in the Templates group box blank.
With Billing, to find the billing interface parameter that you need to run the Billing Interface Application Engine, view the message log from the Contracts/Billing Interface process (CA_BI_INTFC).
When setting up Payables, remember that:
If you are entering contractor time through Time and Labor and using the Staffing Application Engine process (FO_TO_AP) to load time into voucher staging tables, the voucher profile must have an account mapped for every TRC for which you enter contract time.
If a vendor sends you an invoice for contractor time and you are entering it directly as a voucher into Payables, when you run the PC_TO_AP_PC process, you must select the Summary parameter in the Application Options group box on the run control page.
Warning! Do not select Detail.
When setting up Payroll for North America, remember that Time and Labor does not provide all the overtime rules to meet FLSA requirements, and Pay/Bill Management does not provide any rules. You must create your own.
Pay/Bill Management does not calculate overtime premium pay rates using FLSA regulations. However, it passes information to North American Payroll in a format that enables that application to compute the premium pay. Pay/Bill Management handles FLSA premium pay requirements as follows:
If the employee is non-exempt and belongs to a paygroup that is configured as FLSA required, the system does not use the overtime pay rate entered in the assignment, but rather it uses the regular time pay rate as the override rate for overtime pay.
The system then relies on North American Payroll to apply the earnings code multipliers on that override rate to compute premium pay. If the employee is exempt or belongs to a paygroup that is not configured as FLSA required, the system will use the overtime pay rate entered in the assignment as the override rate. In these situations, ensure that the earnings code associated with the overtime TRC does not have the multiplier factor, otherwise overtime premium may be compounded—once by the Pay/Bill Management assignment override rate, and again by the earnings code multiplier rate.
Compensation rate codes entered for staffing employees must have the Use FTE field value be set to No.
See Also
PeopleSoft Enterprise Time and Labor 8.9 PeopleBook, “Creating Rules in Time Administration”
When setting up Global Payroll, make sure that the TRCs for global salaried personnel map to an earnings code that does not add to gross or net amounts. This ensures that you do not pay an employee from employee record 1, 2, 3, and so forth, but instead that you pay from employee record 0.
See Also
Paying Salary and Hourly Employees With PeopleSoft Global Payroll
This section discusses how to set up installation options.
Note. The Installation Options - Staffing page is shared between Staffing Front Office and Pay/Bill Management. Some of the options on the page are specific to only one of the two applications, but some are options shared between the two.
See Also
Setting Up Your General Business Environment
Page Name |
Object Name |
Navigation |
Usage |
INSTALLATION_FO |
Set Up Financials/Supply Chain, Install, Installation Options, Staffing |
Set up installation options. |
User preferences enable you to set up default values that facilitate faster data entry into transaction tables. These default values can be overridden on the actual pages.
You set up user preferences using the pages described in the PeopleSoft Financials, Enterprise Service Automation, and Supply Chain Management Application Fundamentals 8.9 PeopleBook.
Note. You must set up overall preferences before you can set up default values.
See Defining Overall User Preferences.
See Defining Staffing General Preferences.
PeopleSoft applications use the capabilities and flexibility of multilevel security to provide an efficient, effective solution to security issues. Pay/Bill Management leverages the existing departmental security provided by the PeopleSoft Human Resources Management (HRMS) database for employees. Additionally, the Pay/Bill Management applicant and employee components in Financials also have departmental security.
Note. Other Financials applications, such as Expenses and Resource Management, also have their own employee components but those are not enabled for departmental security.
Based on the departmental security setup, users are granted or denied access to employee data based on the organizational hierarchy that you define in the security tree. Departmental security must be configured both in the HCM and Financials databases.
When you grant users access to a department ID on the security tree, you automatically grant them access to employee data in any department that reports (directly or indirectly) to that department ID, unless you restrict access to a specific department.
Using departmental security, grant and deny access to employee data by using row-level permission lists. Users are assigned a row-level permission list granting them access to data in certain departments.
Note. Department security only pertains to applicant and employee functionality.
Note. Other relevant information that is common to many applications is located in thePeopleSoft Enterprise HRMS Application Fundamentals PeopleBook.
See Also
PeopleSoft Enterprise HRMS 8.9 Application Fundamentals PeopleBook, “Setting Up and Administering HRMS Security”