The below are the some of collection for common Peoplesoft Terminology.
Business Unit: A business unit is an organizational entity which maintains its own transaction data.
Transaction Tables: Transaction tables store data about day-to-day business activities. Transaction tables in PeopleSoft are keyed in by Business Unit.
Control Tables: Control tables store information that define the accounting structure and processing rules that are used when transactions are entered into your PeopleSoft applications. Control tables include master lists such as customers, vendors, products, items, and chart of accounts. Control tables are static; they change only when you perform specific maintenance, appropriate to changes in your business policies. Most PeopleSoft tables are keyed by Table Set Identifier, rather than by Business Unit. In addition, most are effective-dated.
Record Groups: The control tables used by each of the financial and distribution applications are grouped by function into record groups. A record group is a set of logically and functionally related control tables and views. All tables in the same record group will have the same key on each table.
Record Group Control: In the TableSet record group control panel, you specify which SetID you want a business unit to use for each record group. You can specify a single SetID for all Record Groups or a combination of any number of SetIDs.
SetID and TableSet Sharing
TableSet Id: Most data recorded in control tables is stored by Table Set ID (also called as SetID). Whenever your enter information in control table, you must enter the SetID to establish the ownership of that information. A grouping of data that is keyed by the same SetID is called a TableSet.
The accounting structure and processing rules for each PeopleSoft application that you use are defined in a series of control tables. A TableSet is a group of rows shared across control tables and identified by the same setID, on which you define the accounting structure for each business unit. For a business unit to process transactions, it must have an associated TableSet.
Several business units can share the control data in a TableSet; for example, vendors are defined by setID, and you can set up any number of business units to share the vendors in a setID.
Consider this relationship in simplified terms: the business unit contains all the actual data, and the TableSet contains the rules by which the data is processed. A setID identifies each TableSet. You can have as many setIDs as you like, but having numerous setIDs makes TableSet sharing more complex. Create at least one setID even if you do not take advantage of TableSet sharing. Some organizations need only one setID.
|how to send hyperlink with email in application engine program.||PeopleSoft Technical||06/13/2013 - 12:55am|
|Saving records||PeopleSoft Technical||06/04/2013 - 11:11am|
|can we alter a trigger in DB2 to add a new column||SQL & PL/SQL||05/29/2013 - 1:31am|
|Required Peoplesoft HRMS Functional Training||PeopleSoft Functional||05/07/2013 - 10:29pm|