Prepare for your Next Interview
|
Welcome to the Geeks Talk forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us. |
This is a discussion on SetID and TableSet Sharing within the PeopleSoft forums, part of the Enterprise Solutions category; What is SetId,Business unit and table set sharing in people soft and how we can immpliment it??...
|
|||||||
| PeopleSoft PeopleSoft Knowledge Base, Learn and Share ERP Technology related articles, white papers, tutorials / study materials, example codes, FAQ's, Tips and Tricks. |
![]() |
| LinkBack | Thread Tools | Display Modes |
|
|||
|
SetID and TableSet Sharing
What is SetId,Business unit and table set sharing in people soft and how we can immpliment it??
|
| The Following User Says Thank You to vikasit1983 For This Useful Post: | ||
| Sponsored Links |
|
|||
|
Re: SetID and TableSet Sharing
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. |
![]() |
|
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Sharing QC Export Maps in Excel | PShow | Quality Center | 1 | 4 Weeks Ago 01:43 PM |
| Sharing NIC on a PC | pravina | Networking | 0 | 02-21-2008 05:26 AM |