Should be shared/controlled between different entities in the company. Setup (and terms!) is only to enable organisations define how setup data The appropriate setid for each record group. So tableset control is the link that maps the business unit values to Setid corresponding to the location record group to the Australian setidДЄnd set the shared setid as the setid for the Department record group. In this page, you will have to change the This will take you to the transaction page, where allДЄvailable record groups and the corresponding setid that will beДefaulted will be listed. Value of the Australian business unit in the search field called SetД¬ontrol value. You would have to navigate to the Tableset Control page and enter the So taking our previousД®xample, to define the setid defaults for the Australian business unit, Note that each setup value like Department,

Peopletools > Utilities > Administration > Tableset Control youД¬an define the setid that should default for each setup value for a Setid defaulted for locations will be the New Zealand setid. If you selected a New Zealand business unit in Job data, the setidДefaulted for department prompt will be the shared setid, while the That if you selected business unit of Australia in Job data, the setidДefaulted for department prompt will be the shared setid while the setidДefaulted for location prompt will be the Australian setid. Once a business unit is selected, the defaulted setid values forДeparment, Location, Jobcode and Salary Administration plan isД¬ontrolled by the value of the business unit field. No values will be returned for Departments or Locations in this case). Job data without entering any value for Business Unit. Select the value for Business Unit in Job data (a good corollaryД®xperiment is to try to look up the department and location prompts in To selecting the values for Department or Location, you will have to Have been defined - one for Australia and another for New Zealand. Jobcode and Salary Administration plan fields in the Job data component.Д¬oming back to our example of the company with operations in AustraliaДЄnd New Zealand, let us assume that there are two business units that

The value of Business Unit selected in the Job data component,Д¬ontrols the setid that will be defaulted in the Department, Location, With the setid allocation while setting up key tablesД¬larified, let us understand how the defaulting of setids happen in Job Setid, while the setid assigned to Australian locations should be theДЄustralian setid and the New Zealand locations should have the New For thisД¬ustomer, the setid assigned to all departments should be the shared One setid that is 'SHARED'Д«etween Australia and New Zealand, another setid that is specific toДЄustralia and the third setid specific to New Zealand. Have to create three setids in this case. So taking this simplistic example forward, you would Setups are keyed by Setid, this key can be effectively used to drive Locations that are specific to Australia. Organisation, but at the same time, they should be able to select only TheД¬ustomer requirement is that when they are hiring an employee inДЄustralia, they should be able to look up all departments defined in the PeopleSoft Workforce Administration for Australia and New Zealand. That it helps to drive the security behind the display of key setup Location, Jobcode, Salary Administration Plan, Employee Class etc. A number of setup components in PeopleSoft HCM like Department,

Peoplesoft report node definition