Understanding PeopleSoft HCM Common Components
This section lists common elements and discusses common component pages.
Field or Control |
Description |
|---|---|
Object Owner ID |
Identifies the application in which a common component is used. This is delivered functionality. |
Sub ID (sub application ID) |
Used to further partition component entries by function. For example, the Sub ID of M (Manager) allows component entries different from those of a Sub ID of E (Employee). |
PeopleSoft provides common pages to perform functionality across multiple Human Capital Management (HCM) applications. These pages are implemented as plug-in applications that you can easily configure and embed into an application via provided application program interface (APIs).
These applications are typically used to capture, store and present information for a particular generic function within the context of a calling application (for example, an application such as Talent Acquisition Manager, ePerformance or Benefits Administration).
Data Structures
Each common component manages its own data source. These common components have keys. All applications that embed the plug-in share the same data structure that uses a configurable key structure to accommodate the different requirements that each application has for organizing this data. Each application defines, or registers, the actual keys that are used when the plug-in runs within the context of the application that has embedded it. You register the keys by making an entry for the application in the plug-in's configuration page, which is keyed by the object owner ID of the embedding application.
User Interface
The use of plug-ins enables all applications that embed a plug-in to present the data consistently. For example, the same format is used to capture and present context-sensitive notes, whether the user is in Talent Acquisition Manager, ePerformance, Payroll for North America, or Benefits. To provide context-sensitive instructional text, labels, and so forth, each of the plug-in applications uses the text catalog to provide context sensitivity while maintaining a consistent style across all of HCM.
Configurable Behavior
Some embedding applications need the ability to enable, disable, or modify the plug-in functionality. Applications manipulate these configuration options inside the plug-in's configuration page—the same place it registers its keys.
HCM plug-ins, except for the text catalog, are embedded in an application by placing a graphic button on a page, and a simple API call on the button's FieldChange PeopleCode. The Text Catalog is generally invoked via an API in component-build, and/or PageActivate code.
Warning! Be careful when modifying configurations. PeopleSoft does not support some modifications, for example changing key values, that might cause other functionality in the application to not work as intended.