Enter: the Setid. The Setid is the means by which sets of values are given an identifier. The Setid is generally the topmost key of any table in a PeopleSoft application that does not hold transactions. Setids are managed at the table level or, actually, at the group of table level. So, in the example of Virgin, you could see the following:.
One way to understand setids is to understand the entities in the application that use it i. These are:. The other main type of table in a PeopleSoft application is the transaction or document. These entities are keyed by a corollary field, called Business Unit. You could think of the business unit as a set of books in financials, or a discrete instance of a set of transactions that stand on their own for other applications.
Examples of business unit keyed tables are Journals, Ledgers which are just an aggregation of journals , vouchers, receivables, orders, returns, and cases. In the OLAP world, tables keyed by business unit are generally facts in the system. So, how to business units and setids relate to each other? Good question. Remember, that transaction tables are keyed by business unit. One could also think of a transaction as any business event that happens in an ERP application that needs to be captured or measured.
Therefore, the role of setids is to control either the set of values used for things captured in a given transaction, or the rules used for processing that transaction. This means that there is a relationship between a business unit, and the sets of values that are used for valid data, or for controlling processing which are stored in tables. This is done using the tableset controls which is accessed in the PeopleTools menu, under the administration sub-menu.
The mapping of setids to business units occur with the following levels:. Another good question. When you go into the journal page, the first thing it does is ask you what business unit the journal is for.
When you pick this value, you have identified what set of record group controls will be used for entering that journal. The first place you will se that is in prompting in the page. Pretty much any field, with the exception of the numeric fields, will use the setid indirection i. One example may be the following:. When you run any batch program, the first thing you need to supply in the run control is the business unit for the transactions to be processed.
This will identify the business rules to be used for that process such as balancing rules for posting journals. Another good question, especially for nVision.
PeopleSoft reporting tools definitely need to understand about setid indirection, so that the appropriate values are returned when the report joins transaction data to the attributes of the trasaction i. Oracle is a organization where oracle india pvt lts or oracle US llc would be registered companies. No Account? Sign up. By signing in, you agree to our Terms of Use and Privacy Policy.
Already have an account? Sign in. By signing up, you agree to our Terms of Use and Privacy Policy. Enter the email address associated with your account. We'll send a magic link to your inbox. Email Address. All Sign in options. Enter a Email Address.
Choose your interests Get the latest news, expert insights and market research, sent straight to your inbox. Newsletter Topics Select minimum 1 topic. Tags: PeopleTools.
Tony Huang September 30, 0 Comments. Thanks Somnath. You select the appropriate location from the prompt and save the component. After you completed this transaction, you realize that you also had to change the department of the employee along with the change in location. So you navigate back to Job data and try to change the department in the effective dated row that you created for the change in location transaction.
When you look up the department prompt in Job data, you again observe that the Setid field in the prompt is read only and has a pre-filled value of 'SHARE'. This is the second observation that I need you to question. Let us try to answer these questions first. How is the Setid value of certain fields like location, department, jobcode etc. The significance of Setid is that it helps to drive the security behind the display of key setup values in the application.
The customer requirement is that when they are hiring an employee in Australia, they should be able to look up all departments defined in the organization, but at the same time, they should be able to select only locations that are specific to Australia. As Department and Location setups are keyed by Setid, this key can be effectively used to drive this requirement.
So taking this simplistic example forward, you would have to create three setids in this case. For this customer, the Setid assigned to all departments should be the shared Setid, while the Setid assigned to Australian locations should be the Australian Setid and the New Zealand locations should have the New Zealand Setid.
With the Setid allocation while setting up key tables clarified, let us understand how the defaulting of Setid happens in Job data. The value of Business Unit selected in the Job data component controls the Setid that will be defaulted in the Department, Location, Jobcode and Salary Administration plan fields in the Job data component. Coming back to our example of the company with operations in Australia and New Zealand, let us assume that there are two business units that have been defined - one for Australia and another for New Zealand.
Prior to selecting the values for Department or Location, you will have to select the value for Business Unit in Job data a good corollary experiment is to try to look up the department and location prompts in job data without entering any value for Business Unit. You will see that no values will be returned for Departments or Locations in this case. Once a business unit is selected, the defaulted Setid values for Department, Location, Jobcode and Salary Administration plan is controlled by the value of the business unit field.
This goes on to say that if you selected business unit of Australia in Job data, the Setid defaulted for department prompt will be the shared Setid while the Setid defaulted for location prompt will be the Australian Setid. Similarly if you selected a New Zealand business unit in Job data, the Setid defaulted for department prompt will be the shared Setid, while the Setid defaulted for locations will be the New Zealand Setid.
This brings us to the obvious conclusion that there should be a link or mapping between the value of business unit and Setid for the various setup values. This means that there should be a mechanism where we can define that for Australia business unit, departments should have the shared Setid and locations should have the Australian Setid, while for New Zealand business unit, the Setid for locations should be New Zealand Setid.
0コメント