Alias: IVPPYD#
(INF_CV_PAYMENTRULES)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.
Tables loaded:
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) | ||
| CREATE_DATE | Date() | This field used internally only to provide audit information for the creation/updating of records. This field would not be loaded. | |
| CREATE_USER | Varchar2(30) | This field used internally only to provide audit information for the creation/updating of records. This field would not be loaded. | |
| CHANGE_DATE | Date() | This field used internally only to provide audit information for the creation/updating of records. This field would not be loaded. | |
| CHANGE_USER | Varchar2(30) | This field used internally only to provide audit information for the creation/updating of records. This field would not be loaded. |
Notes #
Click to create a new notes pageScreen captures are meant to be indicative of the concept being presented and may not reflect the current screen design.
If you have any comments or questions please email the Wiki Editor
All content © High Line Corporation