Example of Converting Sundry Lines#

Sundry Lines are payroll transactions for a specific employee that re-occur on a set frequency. Since they are payroll transactions, they can be deductions, earnings or any other type of transactions that can be entered through the payroll transaction screen IPSN. One requirement of Sundry Lines is that the pay component that is being loaded and converted must have the Enter Sundry toggle in the PC Rules section of the IPPC screen turned on.

Sundry Lines are stored in the database as a header/detail set of records. The tables that the converted records are converted into are actually P2K_PR_SUNDRY_LINES and P2K_PR_SUNDRY_LINE_DETAILS. The interface table where the records are loaded into combines these two records together in order to group them more easily. Since each Sundry Line can have several Sundry Line Details, it is best to build the interface records following this grouping. As a minimum, each Sundry Line needs one Sundry Line Detail.

The following table is a list of the columns in the INF_CV_SUNDRYLINES:

Name Null? Type Notes
ENTITY_CODE NOT NULL VARCHAR2(16) Used to derive link to EMPLOYMENT record
PERSON_CODE NOT NULL VARCHAR2(16) Used to derive link to EMPLOYMENT record
EMPLOYMENT_TYPE VARCHAR2(30) Used to derive link to EMPLOYMENT record
HIRE_DATEDATE Used to derive link to EMPLOYMENT record
FREQUENCY_CODE NOT NULL VARCHAR2(16) Must be a valid Pay Frequency on IPPF
SUNDRY_LINE_TYPE NOT NULL VARCHAR2(30) Must be valid lexicon entry. Typically 01 or Sundry
START_DATE NOT NULL DATE First day that Sundry records need to be processed by payroll
END_DATE NOT NULL DATE Last day Sundry record will be processed
PC_CODE_HEADER NOT NULL NUMBER(4) Must be a valid PC Code from the IPPC screen
UNIT_CODE VARCHAR2(16) A valid is only needed if this is not the employees prime assignment value
GROUP_CODE VARCHAR2(16) A valid is only needed if this is not the employees prime assignment value
POSITION_CODE VARCHAR2(16) A valid is only needed if this is not the employees prime assignment value
JOB_CODE VARCHAR2(16) A valid is only needed if this is not the employees prime assignment value
LEAVE_TYPE_CODE VARCHAR2(16) not used at this time
PLAN_CODE VARCHAR2(16) Not used at this time
USER_CALC_CODE VARCHAR2(16) Identifies the user calc to execute when sundry line is processed.
COUNTRY_CODE VARCHAR2(16) A valid is only needed if this is not the employees prime assignment value
STATE_PROVINCE_CODE VARCHAR2(16) A valid is only needed if this is not the employees prime assignment value
GEO_CODE VARCHAR2(16) A valid is only needed if this is not the employees prime assignment value
ASSIGNMENT_START_DATE DATE Used to derive link to ASSIGNMENT record
ASSIGNMENT_CODE NOT NULL VARCHAR2(16) Used to derive link to ASSIGNMENT record
TIMES_REMAINING NUMBER(5) The number of time the sundry line needs to be processed.
PAY_POINT_TYPE VARCHAR2(30)
PAY_POINT_TASK VARCHAR2(30)
PAY_POINT_SEQUENCE NUMBER(5)
TIME_ENTERED NUMBER(18,6) Value associated to the PC Code of this Sundry Line
TIME_BASIS VARCHAR2(30) Must be a valid lexicon entry. Typically 15 or $
WCB_CLASS VARCHAR2(30)
DISTRIBUTION_MASK VARCHAR2(50)
REFERENCE_INFO VARCHAR2(50)
PC_CODE_DETAILS NUMBER(4) Must be a valid PC Code from the IPPC screen
PC_ACTION NOT NULL VARCHAR2(30) Must be a valid lexicon entry. Typically A or Accumulate
PC_DETAIL_TYPE NOT NULL VARCHAR2(30) Must be a valid lexicon entry. Typically 20 or 'Entered Value'