Nov 25

Print this Post

Global Payroll — Rule and Non-Rule packages

Rule & Non-Rule Packages in a Global Payroll bundle
(Note: Some literal text and picture has been take from Peoplebooks)

In a Global Payroll bundle, there are country specific Rule and Non-Rule packages to be applied as per requirement. In any database where you are applying bundle, first you need to apply Rule package and then Non-Rule.

Before discussing any further details of Rule and Non-Rule packages, let us understand something about PIN in a Global Payroll System.

A PIN number is a numeric identifier for an element. Every element in Global Payroll has a unique PIN number, including the elements that you create and the elements PeopleSoft delivers. Global Payroll programs access and process an element by referring to its PIN number, rather than its name. A PIN is referred to as an element in Global Payroll. A PIN and an element are identical, and a PIN number is the same as an element number. We explain the term PIN here because it is referenced throughout the programs and table structure of the application. Think of PIN as the technical name that is used in the programming and table structure and element as the functional name that is used on all pages and discussions.

This is necessary because Global Payroll is designed for use by any organization in any country. Each organization will likely give the elements that form the basis for its payroll system different names, depending on its requirements. And organizations in different countries are going to name their elements using different languages. Also, the system elements delivered by PeopleSoft are often translated into many languages. If the name were the only way to identify an element, there could be problems.

PIN numbers also improve performance within batch processes. It is more efficient for the system to use numeric values than to use character values. This performance improvement is a result of being able to easily read the numeric values into the processing arrays and create a pointer to the correct place in the array. PINs are numbered sequentially.

Note. The system assigns a PIN number to each element that you create. The first number the system assigns is 100,001. PIN numbers prior to 100,001 are reserved for the elements that are delivered with Global Payroll.

Rule Package: In Global Payroll a rule is an element or combination of elements used to define a business rule. For example, an earning or deduction rule or a count or rounding rule. The primary key for rule-definition tables is PIN_NUM. A package comprises of more than one GP rule is known as Rule package.

Non-rule Package: In Global Payroll a Non-rule data includes processing results, payee data, setup definitions, and other data where PIN_NUM isn’t the primary key. A package comprises of more than one GP non-rule is known as Non-Rule package.

How to apply the rule and non-rule packages?

There are predefined steps to apply rule and non-rule packages. Sequence is first to apply Rule and then Non-rule package.

Apply Rule package:

There are Data Mover scripts delivered for Rule package within the bundle (per country extension), which follow this naming convention:

CX******_imp.dms (Rule Packager) where CX stands for two digit country extension and * is the bundle number.

Once you run the dms script through DataMover, you have to login into PIA of the same database and have to first compare and then upgrade the same Rule Package.

i) First step is to compare the package.

ii) Second is to upgrade the package.

iii) Proper attention and functional/business intervention is required while applying a Rule package as this will hit the core of Global Payroll engine: The Element. For example, if due to some business requirement some rule of the element has been changed by functional person and the same rule of that element has been changed by PeopleSoft in bundle, that will override the business specified rule and may leads to wrong results.

Apply Non-Rule package:

There are Data Mover scripts delivered for Non-Rule, which follow this naming convention:

CX******_elements.dms (Non-Rule Packager) and CX******_records.dms (Non-Rule Packager) where CX stands for two digit country extension and * is the bundle number.

Once you run the dms script through DataMover, you have to login into PIA of the same database and have to first compare and then upgrade the same Non-Rule Package.

i) Compare process:

ii) Upgrade process
Clean-up Script
Finally, do not forget to clean-up the database.

From the Data Mover, run the CLEANUP.DMS script. This script needs to be run only for Non Rule Packages. This script cleans up the unwanted PIN numbers which already got resolved during the course of applying Rule and Non-Rule packages, generally more than 50000000.

NOTE: In most of the bundles, clean up scripts is an automatic step which CA invoked by itself and need not to run outside a bundle.

Permanent link to this article: http://alokbhardwaj.com/oracle-peoplesoft/2008/11/25/global-payroll-rule-and-non-rule-packages/


  1. expsofter

    could you please check the photos uploaded? can’t see them.. would be great to see them..

    thanks for creating this blog! it’s very interesting!

  2. ShanatApps

    Is it that we have to run the gp_cleanup.dms script immediately after we run the non rule package compare and upgrade through PIA?

    Please suggest.


  3. Alok.Bhardwaj

    Hi Sharat,

    Yes, gp_cleanup.dms needs to be run to clean the unwanted elements from the system which get generates due to import of packages.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>