This page (revision-21) was last changed on 26-Nov-2021 10:22 by JMyers

This page was created on 26-Nov-2021 10:22 by JMyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
21 26-Nov-2021 10:22 4 KB JMyers to previous

Page References

Incoming links Outgoing links
IVPPYD
IVPPYD

Version management

Difference between version and

At line 1 changed 2 lines
!!!Alias: [IVPPYD]
(INF_CV_PAYMENTRULES)
[{TableOfContents }]
!!!PAYMENT RULES INTERFACE FILE
At line 4 changed one line
The INF_CV_PAYMENTRULES table is used to import the rules for disbursing an employee’s pay into the software data structures. Payment Rules are a date sensitive means of indicating the method(s) by which an employee elects to receive their pay. This may include payment by check, and/or an unlimited number of direct deposits.
The Payment Rules Interface File screen is used to import the rules for disbursing an employee’s pay into the software data structures. Payment Rules are a date sensitive means of indicating the method(s) by which an employee elects to receive their pay. This may include payment by check, and/or an unlimited number of direct deposits.
At line 6 changed 30 lines
Tables loaded:
*[P2K_PR_PAYMENT_RULES]
*[P2K_PR_PAYMENT_RULE_DETAILS]
!!Table Columns
\\
||Column name||Data Type / Size||Mand.||Notes
|[ID]|Number(10)| |Used internally to define a unique identification for the record. This field would not be loaded.
|[ENTITY_CODE]|Varchar2(16)|Y|Not moved to the software data structures, but used for validation of the employment record. Validation: The Entity Code provided must be defined on [P2K_CM_ENTITIES]
|[PERSON_CODE]|Varchar2(16)|Y|Used for validation of the employment record. Validation: Must be a valid [PERSON_CODE] already defined on the [P2K_HR_IDENTITIES] table.
|[EMPLOYMENT_TYPE]|Varchar2(30)| |Not moved to the software structures, but used for validation. Validation: The employee must have an active employment record for this employment type. Must be one of the fixed lexicon values from [X_EMPLOYMENT_TYPE]. Derivation: If you do not provide an employment type value, the conversion application will look for any [P2K_HR_EMPLOYMENTS] record that matches the other criteria. Suggestion: If you are loading employees, you can set this field to a fixed value of ‘01’.
|[HIRE_DATE]|Date()| |Not moved to the software structures, but used for validation of the employment record. Derivation: If you do not provide a hire date, the conversion application will look for any [P2K_HR_EMPLOYMENTS] record that matches the other criteria. Validation: Must be a valid date.
|[EFFECTIVE]|Date()|Y|Validation: Must be a valid date format. Suggestion: If you are not loading multiple date-effective records for the same entity code, then populate this field with a constant ‘01-Jan-0001’ which represents the beginning of time.
|[EXPIRY]|Date()|Y|Validation: Must be a valid date format, with a date after the effective date. Suggestion: If you are not loading multiple date-effective records for the same entity code, then populate this field with a constant ‘31-Dec-3999’ which represents the end of time.
|[CHANGE_CODE]|Varchar2(16)| |Validation: The Change Code provided must be defined on [P2K_CM_CHANGE_REASONS]
|[PAYMENT_RULE_TYPE]|Varchar2(30)|Y|Validation: Must be one of the fixed lexicon values from [X_PAYMENT_RULE_TYPE]
|[COUNTRY_CODE]|Varchar2(16)| |Not moved to the software structures, but used for validation of the bank transit code. Validation: Must be a valid country code on [P2K_CM_COUNTRIES]
|[BANK_TRANSIT_CODE]|Varchar2(16)| |Validation: Must be a valid bank location already defined on [P2K_PR_BANK_LOCATIONS]
|[BANK_ACCOUNT]|Varchar2(30)| |
|[BANK_ACCOUNT_TYPE]|Varchar2(30)| |Validation: Must be one of the fixed lexicon values from [X_BANK_ACCT_TYPE]
|[SPLIT_SEQUENCE]|Number(5)| |
|[AMOUNT]|Number(18)| |
|[NET_PAY_PERCENT]|Number(5)| |
|[PAY_REMAINING]|Varchar2(4)| |Validation: This field is a “toggle” field. The value will be translated as False if the value is left NULL, set to “N”, “NO” or “0”. All other values will translate to True
|[PAID_TO_ORDER_OF]|Varchar2(50)| |
|[DEPOSIT_START_DATE]|Date()| |Validation: Must be a valid date.
|[PRENOTE_REQUIRED]|Varchar2(4)| |Validation: This field is a “toggle” field. The value will be translated as False if the value is left NULL, set to “N”, “NO” or “0”. All other values will translate to True
|[PRENOTE_DATE]|Date()| |Validation: Must be a valid date.
|[BANK_TRANSIT_CODE_PAYBY]|Varchar2(16)| |Validation: Must be a valid bank location already defined on [P2K_PR_BANK_LOCATIONS]
|[BANK_ACCOUNT_PAYBY]|Varchar2(30)| |Validation: The payment rule must have been previously defined on [P2K_PR_PAYMENT_RULE_DETAILS].
|[PRIME_DEPOSIT]|Varchar2(4)| |
Payment Rules Interface File data is maintained on the [INF_CV_PAYMENTRULES] table.
At line 8 added 23 lines
;[ID|ID]:This field uniquely identifies the payment rule record within the data base.
;[Entity|ENTITY_CODE]:This field identifies the entity associated with the payment rule.
;[Employee #|PERSON_CODE]:This field identifies the person associated with the payment rule.
;[Employment Type|EMPLOYMENT_TYPE]:The person's employment type is displayed in this field.
;[Date of Hire|HIRE_DATE]:The employee's date of hire is displayed in this field.
;[Effective as of|EFFECTIVE]/[Expires On|EXPIRY]:If the employment is for a limited time, that time period is defined in these fields.
;[Change Reason|CHANGE_CODE]:This field displays the ‘Change Reason’ code, which provides the rationale as to why information has been created or changed as of an effective date.
;[Payment Rule Type|PAYMENT_RULE_TYPE]:This rule indicates whether the payment will be made by check or deposit.
;[Country Name|COUNTRY_CODE]:The entity's associated country is displayed in this field.
;[Bank Transit|BANK_TRANSIT_CODE]:The bank associated with the payment rule is displayed in this field.
;[Bank Account|BANK_ACCOUNT]:The bank account associated with the payment rule is displayed in this field.
;[Bank Account Type|BANK_ACCOUNT_TYPE]:The bank account type associated with the payment rule is displayed in this field.
;[Split Sequence|SPLIT_SEQUENCE]: This field defines the sequential order of a distribution mask when splitting a cost over multiple distributions.
;[Amount $|AMOUNT]:This field shows the amount calculated as a result of applying the PC Calc Method.
;[Net Pay Percent|NET_PAY_PERCENT]:This field holds the percentage of the net pay to be sent to this check or deposit account.
;[Pay Remaining|PAY_REMAINING]:Only ONE of the employee’s choices may be marked at one time as ‘Pay Remaining’. If more than one choice is selected, [UPCALC] will produce the following message: "PR#00029: Sequence (999) bypassed. Only one ‘Pay Remaining’ allowed." Pay the remaining balance of the net pay to this payment sequence. If this option is not used on a deposit account, the pay split calculation process pays any remaining net pay to a check.
;[Pay to the Order of|PAID_TO_ORDER_OF]:This field holds an alternative name that the check is made out to.
;[Deposit to Start as of|DEPOSIT_START_DATE]:This field is used only for U.S. installations to display the pay period start date where the deposit is to commence after the pre-note period is over.
;[Prenote Requirement|PRENOTE_REQUIRED]:This field is used only for U.S. installations to indicate if the deposit account will be pre-noted to the bank, and the required waiting period will be observed.
;[Date of Pre-notification|PRENOTE_DATE]:This field is used only for U.S. installations to indicate when the pre-notification was sent to the bank. The pay issue date becomes the pre-note date.
;[Bank Transit Code|BANK_ACCOUNT_PAYBY]:This field is used only for U.S. installations. During the pre-notification period, this account number, along with the previously identified transit code, identifies the payment rule that is to be used until the pre-notification period is finished.
;[Pay by Account|BANK_ACCOUNT_PAYBY]:This field is used only for U.S. installations. During the pre-notification period, this account number, along with the previously identified transit code, identifies the payment rule that is to be used until the pre-notification period is finished.
;[Prime Deposit|PRIME_DEPOSIT]:This field is used to indicate if this account is considered the prime deposit account
At line 38 removed one line
[{If var='loginstatus' contains 'authenticated'
At line 41 changed 4 lines
![Discussion|Edit:Internal.IVPPYD]
[{InsertPage page='Internal.IVPPYD' default='Click to create a new discussion page'}]
}]
![Notes|Edit:Internal.IVPPYD]
[{InsertPage page='Internal.IVPPYD' default='Click to create a new notes page'}]
This page (revision-21) was last changed on 26-Nov-2021 10:22 by JMyersTop