Translate Tables: Tables which store static data like blood groups, days of the week, types of interviews etc. Data in translate tables do not change frequently.

Processing Tables: Tables which store default values which are pre-defined values that the system inserts into a field on a particular page. These default values are inserted on the basis of other information the user keys in.

Control Tables: Control tables store information which define company structure and processing rules. Values stored in this field are used to validate the transactions the users perform. Eg., Lists of vendors, customers, departments etc. Data in the control tables are shared by multiple components are updated when there is restructuring in the organization. Values are generally static.

Transaction Tables: Transaction tables store day to day transactions. Eg.: Personal data of employee. These tables are more frequently updated.

No. The web server that was delivered on the Tuxedo CD has absolutely nothing to do with WebLogic. WebLogic is a web application server that is designed for large-scale production websites. The HTTP server on the Tuxedo CD was only there to provide a mechanism for launching the graphical Tuxedo administration console if the Tuxedo administrator didn’t already have a web server in place. It was never intended for large-scale, production website use ? only for a system administrator or two.

Security by department tree defines which setid and deptid a permission list has access to. Security access types are different ways in which security can be driven for a security set. For example, department security can be driven by department tree or department setid. Both these are security access types which belong to security set department.

There are several scenarios that may exist when customers use the PeopleSoft Enterprise Portal with a mixture of 8.1x and 8.4 applications. Specific information on the use of the PeopleSoft Enterprise Portal in a blended environment will be available in a forthcoming white paper, which will be available on Customer Connection. In general, the recommendation is to use the PeopleSoft Enterprise Portal 8.4with 8.1x and 8.4 applications, rather than an older version.

Business units are logical structures used within an organization for reporting purposes. At least one business unit needs to be defined. Business units do not have any restrictions. The number of business units to be created depends entirely on the organization structure and business needs. For eg. A company’s reporting is done on the basis of geographical location. It has six business units namely- NAmerica, SAmerica, EMEA, APAC, Russia and AUS. On the other hand, another company’s reporting is done on the basis of cost centers and it has only one business unit – GLOBAL.

No. The PeopleSoft Mobile Agent architecture, which is used to support disconnected mobile applications, is only available in PeopleTools 8.4. The PeopleSoft Mobile Agent is dependent upon certain core technologies that were specifically developed for PeopleTools 8.4.

When a new functionality needs to be provided access for users, then roles and permissions are used. The functionality is associated to a menu—component—page. So the user needs to get access to the page in one of the various modes like: Add, update or view only. For this, the menu – component – page layer is tied to a permission list. This permission list is then attached to a role and the user is then provided this role through user profile. As a result user will be able to access the functionality.

In PeopleSoft, an establishment is an entity for regulatory purposes. It always has a physical address (location) and is associated with a company. It is an entity for which information is reported as a consolidated unit. For eg., an establishment can be defined as separate units of a company, based on location. In India, an establishment must be registered under the Factories Act or the Shops and Establishments act.

No. IBM WebSphere is certified on PeopleTools 8.4 only. Customer wishing to use IBM WebSphere with PeopleTools 8.1x may take advantage of an IBM WebSphere for early adopters program, created and managed by IBM. Further information about this program can be found in the whitepaper The IBM WebSphere 8.1x Early Adopter Program. Are there additional license requirements for IBM WebSphere

The voucher build process consists of two sub-processes voucher edit and pre-edit. The pre-edit sub-processes create skeleton voucher record sets from the partial information that you provided online using the components like Quick Invoice Entry (VCHR_QUICK_PNL) or the Summary Invoice Entry (VCHR_SUMM_PNL), or that it obtains from other sources. After the pre-edit sub-process creates voucher record sets successfully, it calls the voucher edit sub-process to complete the record sets.

Row level security is also known as Data Permission Security. It determines the access given to a user for all/specific set of rows through any PeopleSoft component which can be delivered or custom. For a row, access to all the fields is given. Row level security restricts user’s access to a subset of rows based on the value within a field in the record. That field could be department, job location, job company, job salary grade etc. There are certain PeopleSoft delivered security sets and access types which can be used as a basis of restriction. For e.g., restrict access for a user (using Job data component) to all the employees having a value of ‘SALES’ for the department field in the current effective dated job row.

The approver for self-service transactions is decided by Direct report setup in Setup HRMS -> Common Definitions -> Direct Reports for Managers -> Direct Report Setup. Here at a self-service transaction component level access for approval can be setup by using access type as: Group id, department manager id, department security tree, partial position management department manager id, partial position management supervisor, reports to position if full position management is used or by supervisor id in job.

No. Both products are certified with PIA as of version 8.4 and work equally well. By offering both BEA WebLogic and IBM WebSphere, we give our customers more choices and flexibility to run PeopleSoft in their preferred environment.

People soft integration broker provides SOA (service oriented architecture) technology, and enables the transferring of asynchronous and synchronous service operations. You can use the PeopleSoft integration broker to To execute synchronous and asynchronous messaging among internal as well as third party systems Delivers PeopleSoft business logic as web services to PeopleSoft and third party systems Invoke and consume web services from third party and PeopleSoft systems

The different security sets are: – Department, People with jobs, People without jobs, US federal people with jobs, Recruiting job openings and template based hire. For each security set, admin can enable or disable the access type. Based on this setup, the system will decide the type of security. For example, department security will be driven based on department tree, which is one access type or it can be driven by department setid which is another access type for the security set department. For POIs with no job rows, to define security, the security set People without jobs is used. The other options are access types like location, business unit or institution. So, the one which is enabled, will drive the security.

Apache JServ was a servlet engine that was supported in PeopleTools 8.1x. This support has been removed from PeopleTools 8.4 for several reasons: v JServ is no longer an active product and is in maintenance mode and there are no longer any new official releases. v Our customers have exhibited a desire to use commercial products for mission-critical enterprise web application servers rather than open source solutions. Therefore, moving to support Tomcat is not seen as a reasonable solution. v Apache can still be used as an HTTP server with BEA WebLogic.