Defining Element Relationships
To define element relationships, use the Define Element Relationships (GP_PIN_FLD_MAP1) component.
The Define Element Relationships utility builds an element map that shows how elements with PIN numbers are related. It defines the relationship between elements, and enables packager to determine if elements are used in non-rule data, which is important when deleting elements and packaging non-rule data.
Although the packager process rebuilds the map when you create a rule package, we recommend that you rebuild the map when you define new elements, change existing elements, or delete elements. It's also advisable to rebuild the map for the target database after completing an upgrade. This ensures that the map is current when displayed.
|
Page Name |
Definition Name |
Usage |
|---|---|---|
|
GP_PIN_FLD_MAP |
Start the GP_PINMAP process, which rebuilds element maps. View which records contain fields that store PIN numbers. You can add and delete records that you've created to the rule map. |
|
|
GP_PIN_FLD_MAP_ERR |
Review for errors after rebuilding the element map. |
Use the Define/Build page (GP_PIN_FLD_MAP) to start the GP_PINMAP process, which rebuilds element maps.
View which records contain fields that store PIN numbers. You can add and delete records that you've created to the rule map.
Navigation
Image: Define/Build page
This example illustrates the fields and controls on the Define/Build page.
This page only lists those records that contain elements (which store PIN numbers). PIN NUM is often the key to these records, though this is not always the case.
Note: You cannot edit or delete this page if it displays information for a PeopleSoft-delivered object.
See Adding Records to an Element Map.
|
Field or Control |
Definition |
|---|---|
| Record Type |
Select a record type, which is the type of record that contains elements. Values are: Element Definition: Records of this type define elements with a primary key of PIN_NUM. Examples: GP_ERN_DED (earnings and deductions), GP_ABS_TAKE (absence takes), GP_ARRAY arrays and GP_FORMULA (formulas). Note: The Element Definition record type is used only by PeopleSoft. Records that contain elements but don't define elements have one of the following record types: Set-up Definition: These are records you define when you implement Global Payroll. Examples: GP_ELIG_GRP_MBR (eligibility group member) and GP_RUN_TYPE_DTL (run type detail). Output Result Data: These records contain calculation results. Examples: GP_RSLT_ACUM (accumulator results) and GP_RSLT_PIN. Payee Data: These records contain payee-specific data. Examples: GP_ABS_EVENT (absence events) or GP_PYE_OVRD (payee overrides). |
| Record |
Displays the name of the record, containing one or more elements. |
| Export Record |
Displays the name of the record that the system uses when exporting this data to another database. |
| Effective Date Type |
Identifies whether the record is effective-dated. If this field is set incorrectly, the packager may fail. Effdt (effective date): This is the default value. Indicates that the record is effective-dated. Example: GP_BRACKET. Note: If you include in a package an element that has more than one effective-dated row, the system tries to match each row when comparing the source elements with the target database. If it finds a match, it replaces the row in the target database; if it doesn't find a match, it adds the row to the target database. And if a row in the target database has no match , the system leaves the row in the target database unchanged. No Effdt (not effective-dated): Indicates that the record doesn't have an effective date. Example: GP_ARRAY. Note: If you include in a package an element with no effective date, the system replaces all data for that element in the target database when you upgrade the package. Begin − End: Indicates that the record isn't effective-dated but contains begin and end dates. Example: GP_ACM_MBR. Note: If you include in a package an element with begin and end dates, the system replaces all data for that element in the target database when you upgrade the package. |
| Field Name |
Displays the name of the field in the record that contains other PIN number elements. For a record type of Element Definition, the system displays the name of the key field (PIN_NUM). |
Fields Referencing Other Elements
This group box displays all fields that store the PIN numbers of (member) elements that are used by the record/field combination at the top of the page.
The sample page displays information for GP_ERN_DED, the record that defines earning and deduction elements. This record can use up to 17 elements. PIN_AMT_NUM and PIN_BASE_NUM are some of the fields that store PIN numbers of member elements. For example, PIN_BASE_NUM identifies the element that returns the base amount. To resolve an earning or deduction element, the system must know the PIN numbers of elements that store the amount, base, generation control instructions, and so on.
|
Field or Control |
Definition |
|---|---|
| Field Name |
Displays the name of the field that stores a member element's PIN number. |
| Field Long Name |
Displays the long name of the field. |
| Field Status |
Displays the field's status. Values are: Valid: Indicates that the field in the record existed when the element map was last rebuilt. Invalid: Indicates that a field has been renamed or removed from the record, or that the record no longer exists. The system flags invalid fields when you rebuild the element map. |
Applicable Element Types
When the record type is Element Definition, this group box identifies the corresponding element types. For example, the element types that apply to GP_ERN_DED are Earnings and Deductions.
|
Field or Control |
Definition |
|---|---|
| Element Type |
Important when packaging elements. The element type that you select when creating a package gives the system information needed to select rows from the appropriate record. |
| Rebuild Effdt Element Map (rebuild effective-dated element map) |
Click to start the rebuild process. If the system cannot build the element map because of errors, this message appears on the page: "Effdt Element Map hasn't been built. Please check Validation page for errors." Note: If the rebuild process is unsuccessful, an error message also appears in the message log. |
Use the Validation page (GP_PIN_FLD_MAP_ERR) to review for errors after rebuilding the element map.
Navigation
Image: Validation page
This example illustrates the fields and controls on the Validation page.
Review this page for errors generated by the rebuild process.
|
Field or Control |
Definition |
|---|---|
| Status |
Displays Invalid if an error occurred. Usually means that a field has been renamed or removed from the record, or that the record no longer exists. If this is a PS Delivered/Maintained (PeopleSoft delivered/maintained) record, contact PeopleSoft support. If the error involves a record that you created, check the record to make sure all the fields are still valid. |
| Record (Table) Name |
Identifies the record that contained the invalid field. |
| PIN Nbr Fieldname (pay item name number field name) |
Displays the name of the field that appears in the Field Name field at the top of the Define/Build page. |
| Field Name |
Displays the field name that no longer exists in the record but appears on the Define/Build page. |
| Message |
Displays an error message pertaining to the specific field. |