Last updated on OCTOBER 05, 2016
Applies to:PeopleSoft Enterprise HRMS Global Payroll Core - Version 8.9 to 9.2 [Release 8.9 to 9]
Information in this document applies to any platform.
Enterprise, Global Payroll & Absence Management
1. How to apply Rule & Non Rule packages?
Rule Package :
a) Import the package
b) Compare package and ensure that the result is "Success"
c) Upgrade package
Â Non Rule Package
a) Import the Elements
b)Compare the package and ensure that the result is "Success"
c) Import records
d) Upgrade package.
*** Finally, do not forget to run cleanup script(CLEANUP.DMS). This script needs to be run only for Non Rule Packages.
2. What does cleanup.dms do?
This script will delete all 50,000,000+ pin numbers that exist in Element Definition tables.ÃÂ
This script should NOT be run in the MIDDLE of applying a Rule Package (unless you want to back out what you have just imported). Do NOT run this script and then try to run a Package Compare or Upgrade (as you have deleted the elements that the package is trying to compare/upgrade and this could also cause the original element definitions to be deleted).
3. Do we usually have to run cleanup.dms?
Normally there shouldn't be a need to run it. But it doesn't hurt if done before importing new packages. The cleanup.dms does not run by itself after compare/upgrade.However, the system tries to clean the system from 50 million rows after the upgrade process(Only for Rule Packager). So for example you could run the upgrade even though there were elements left in error (failure) after the compare was done.Â Since those elements cannot be upgraded 50 million pins would remain in the system.Â These are cleaned out automatically after the upgrade process has finished.
Hence, in theory there should not be a need to run the cleanup script after a successful upgrade.
For Non Rules Packagers, it is necessary to run the cleanup.dms
4. If some packager import/upgrade did not complete, is this OK?
It shouldn't be left unfinished. It is strongly recommended to resolve the conflicts generated after the compare process. Resolving the conflicts ensure a successful payrun.
5. Is it normal to run a payroll if a packager compare/upgrade did not complete?
No! This could result in an error if the payroll is using one of the elements included in the package. It is not normal and shouldn't be done without having either successfully completed the import/compare/upgrade procedure, or after the Cleanup script ran.
6. How does a customer identify the changes delivered in a Rule or a Non Rule Package?
Global Payroll 8.9 is delivered with a compare report utility to determine the changes delivered in a package.Unfortunately, this utility is not available in 8.3SP1 and 8.8SP1 releases. The only way to identify the changes is to import the rule or non rule package, then manually compare with exisiting config.
This document was previously published as Customer Connection Solution 200777492
The intent of this document is to describe solutions for problems or questions related to Global Payroll Pin Packager and Pins related Global Payroll issues.
This resolution applies to customers on PeopleSoft Global Payroll. This is a living document and will be updated as new solutions are created.
The customer is experiencing Member Element not found issue after performing Compare process for a Rules package delivered in bundle.
The customer ran the Payroll process successfully. However, the payroll results display the below
PIN XXXXXX () requested to be resolved as System PIN not in System Pin table.
The PIN (number) specified was not found when loading entries from the GP SYSTEM PIN table into SP ARRAY.
The customer is running the payroll process and getting the following error:
Element %1 (PIN %2) not loaded into UPINA. (Not applicable for country: %3)
The customer ran the Payroll process successfully. However, the Payee Messages display the below
Element xxxxxxxxx has an invalid PIN(xxxxxxxxx). Valid range is 1 thru 999999. PIN not loaded.
The customer is experiencing following error
Element XXXXXXXX(Pin XXXXXX) and data for the element - not loaded into the process.(N/A for country XXX).
Customer is trying to apply a Non Rule Package but the Compare button is inactive.
Customer has created few country extension rules and wish to migrate these new rules into other environments. However, the customer is unable to view/select these new rules in Create Rule Package component.
Customer is applying GP country extension bundles. They are experiencing issues with comparing and upgrading elements. The elements are upgraded correctly, but the date/time stamp is not updated and do not have anything written in audit trail for issues.
Customer installed demo database and can't find the country extension rules. The base table PS_GP_PIN does not contain country extension elements. What additional steps need to be performed in order to install Global Payroll country extension elements in the database ?
Customer is running payroll and experiencing the following error.
Invalid PIN number %1. Valid range is 1 thru %2. Expand GPCUPINT if needed.
Application Program Failed
In Pgm Section : GPPCDMGR
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms