Set ID is the highest level key in Peoplesoft. Its very important to understand the concepts of SET ids and table set sharing for the purpose of centralisation and decentralisation of data. Control tables being Location Department Job Code Salary Plan Table..etc- there are about 8 HR control tables and a few more Finance table( I am not very sure of the number) Now these control tables with these setids control the Data that appears during a Transaction. Table set sharing is a place where all the control tables are listed. it is accessed by a business unit.
Peopletools>>Utilities>>administration>>Table set Sharing
Lets understand it with an example. There are two business units
lets say AZ and CA and Set ID for AZ is ab1 and setid for CA is XY1.
Now when you Navigate to table set sharing (Peopletools>utilities>table set sharing) and open it for Business unit AZ. You will see the SETID for all the Control Tables as ab1. The setid for this field is editable. Now suppose in the Job COde field of this Table set sharing if you change the setid to XY1 from ab1 then when you are hiring people into this business unit you will be able to access the jobcodes which were created with the setid XY1. So if you want the same set of jobcodes for both business units this is what you can do. So Control tables are the ones you create with Set IDs as the Key- eg Job Code Department Locations...which you create in the foundation structure. transaction tables are those which use business units as the key and are used for a transaction.
I could explain this better if i could show it you in the application
Lets understand it with an example. There are two business units
lets say AZ and CA and Set ID for AZ is ab1 and setid for CA is XY1.
Now when you Navigate to table set sharing (Peopletools>utilities>table set sharing) and open it for Business unit AZ. You will see the SETID for all the Control Tables as ab1. The setid for this field is editable. Now suppose in the Job COde field of this Table set sharing if you change the setid to XY1 from ab1 then when you are hiring people into this business unit you will be able to access the jobcodes which were created with the setid XY1. So if you want the same set of jobcodes for both business units this is what you can do. So Control tables are the ones you create with Set IDs as the Key- eg Job Code Department Locations...which you create in the foundation structure. transaction tables are those which use business units as the key and are used for a transaction.
I could explain this better if i could show it you in the application
No comments:
Post a Comment