This page (revision-89) was last changed on 26-Nov-2021 10:22 by Karen Parrott

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

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
89 26-Nov-2021 10:22 43 KB Karen Parrott to previous
88 26-Nov-2021 10:22 42 KB mmcfarland to previous | to last
87 26-Nov-2021 10:22 42 KB kparrott to previous | to last
86 26-Nov-2021 10:22 42 KB kparrott to previous | to last
85 26-Nov-2021 10:22 42 KB kparrott to previous | to last
84 26-Nov-2021 10:22 41 KB jescott to previous | to last
83 26-Nov-2021 10:22 41 KB jescott to previous | to last
82 26-Nov-2021 10:22 41 KB jescott to previous | to last
81 26-Nov-2021 10:22 41 KB jescott to previous | to last

Page References

Incoming links Outgoing links
IPPH
IPPH

Version management

Difference between version and

At line 146 changed one line
;[Starting|START_DATE]:This field shows the start date of the pay line. Start_Date is a mandatory date field that will default as the pay period start date but may be overridden.
;[Starting|START_DATE]:This field shows the start date of the pay line. Start_Date will default as the pay period start date but may be overridden.
At line 148 changed one line
;[PC|PC_CODE]:A pay component code is a unique number code from 1 to 9,999 assigned to uniquely identify the [pay component|PAY COMPONENTS]. Only [pay components|PAY COMPONENTS] with the toggle ‘Enter Pay Lines’ turned on will be accessible. Data may only be entered in the fields that have had their toggle turned ON in the Pay Component form’s PC Rules tab. PC_Code from [P2K_PR_PAY_COMPONENTS] is a 4-digit numeric mandatory field that you must manually enter or use the LOV (F9).
;[PC|PC_CODE]:A pay component code is a unique number code from 1 to 9,999 assigned to uniquely identify the [pay component|PAY COMPONENTS]. Only [pay components|PAY COMPONENTS] with the toggle ‘Enter Pay Lines’ turned on will be accessible. Data may only be entered in the fields that have had their toggle turned ON in the Pay Component form’s PC Rules tab.
At line 150 changed one line
;[Abbreviation|PC_ABBREVIATION]:This field provides a short description of the [pay component|PAY COMPONENTS] which will be printed on check and deposit statements, lists and pay registers. PC_Abbreviation is a 16-character alphanumeric mandatory field that will default from the pay component chosen.
;[Abbreviation|PC_ABBREVIATION]:This field provides a short description of the [pay component|PAY COMPONENTS] which will be printed on check and deposit statements, lists and pay registers. PC_Abbreviation will default from the pay component chosen.
At line 152 changed one line
;[Value|TIME_ENTERED]:This field shows the amount or time entered for the [pay component|PAY COMPONENTS] indicated. Time_Entered is an 18 digit optional numeric field.
;[Value|TIME_ENTERED]:This field shows the amount or time entered for the [pay component|PAY COMPONENTS] indicated.
At line 168 changed one line
;:Time_Basis is an optional fixed lexicon ([X_TIME_BASIS]) that will default from the [pay component|PAY COMPONENTS] set up but may be overridden.
;:Time_Basis will default from the [pay component|PAY COMPONENTS] set up but may be overridden.
At line 190 changed one line
;[Audit Text|AUDIT_TEXT]:This field will display audit text generated for this line. Click on the right hand side of the text block to open the editor window. Audit_Text is an optional alphanumeric field that will be updated by the system.
;[Audit Text|AUDIT_TEXT]:This field will display audit text generated for this line. Click on the right hand side of the text block to open the editor window. Audit_Text will be updated by the system.
At line 194 changed one line
;[Reference|REFERENCE_INFO]:This field displays a user-defined reference or note determined by the [PC|PAY COMPONENTS] set up in the reference field in [IPPC] (either ‘Enter Description’ or ‘Enter Vendor Code’). This reference information may be either anecdotal or more structured (e.g. Union Code or Court Number). Reference_Info is a 50-character alphanumeric optional field.
;[Reference|REFERENCE_INFO]:This field displays a user-defined reference or note determined by the [PC|PAY COMPONENTS] set up in the reference field in [IPPC] (either ‘Enter Description’ or ‘Enter Vendor Code’). This reference information may be either anecdotal or more structured (e.g. Union Code or Court Number).
At line 196 changed one line
;[Department|DEPARTMENT_CODE]:This is the department defined from the pay line assignment. Department_Code is a 16-character alphanumeric mandatory field that will default from the assignment type indicated but you may manually enter or retrieve from the LOV(F9).
;[Department|DEPARTMENT_CODE]:This is the department defined from the pay line assignment. Department_Code will default from the assignment type indicated but you may manually enter or retrieve from the LOV(F9).
At line 198 changed one line
;[WCB Class|WCB_CLASS]:This field shows the Workers’ Compensation class from the assignment indicated for the pay line. WCB_Class is an optional user-defined lexicon ([X_WCB_CLASS]) that will default from the assignment type indicated and may be overridden.
;[WCB Class|WCB_CLASS]:This field shows the Workers’ Compensation class from the assignment indicated for the pay line. WCB_Class will default from the assignment type indicated and may be overridden.
At line 200 changed one line
;[Work Order|WORK_ORDER]:Work Order is used to define work orders attached to a specific pay line. The Work Order Validation is defined on the ‘Define G/L Company’ ([IDGC]) form. The work order on each pay line can be unedited (no validation) or validated from an external system that has been pre-programmed. Work_Order is a 50-character optional alphanumeric field.
;[Work Order|WORK_ORDER]:Work Order is used to define work orders attached to a specific pay line. The Work Order Validation is defined on the ‘Define G/L Company’ ([IDGC]) form. The work order on each pay line can be unedited (no validation) or validated from an external system that has been pre-programmed.
At line 202 changed one line
;[Cost Center|COST_CENTER_CODE]:Cost Center is used to define a short cut for cost center information attached to a specific pay line. Cost_Center from [P2K_CM_COST_CENTERS] is a 16-character alphanumeric optional field that you manually enter or use the LOV (F9).
;[Cost Center|COST_CENTER_CODE]:Cost Center is used to define a short cut for cost center information attached to a specific pay line.
At line 206 changed one line
;[Benefit Plan|PLAN_CODE]:If this pay line is for a benefit, then the benefit plan is indicated in this field. Benefit_Plan_Code for [P2K_BE_PLAN_DEFINITIONS] is a 16-character alphanumeric optional field you may complete with a value from the LOV (F9) provided.
;[Benefit Plan|PLAN_CODE]:If this pay line is for a benefit, then the benefit plan is indicated in this field.
At line 208 changed one line
;[Pay Point|PAY_POINT_TYPE]:This field indicates when this pay component needs to be picked up for processing during the pay calculation. Pay_Point_Type is a mandatory fixed lexicon ([X_PAY_POINT_TYPE]) that will default from the pay component chosen for this pay line.
;[Pay Point|PAY_POINT_TYPE]:This field indicates when this pay component needs to be picked up for processing during the pay calculation. Pay_Point_Type will default from the pay component chosen for this pay line.
At line 210 changed one line
;[Sequence|PAY_POINT_SEQUENCE]: This field shows the unique sequence number assigned to each item processed in a pay point and determines the order of processing within a ‘Pay Point Type’. Pay_Point_Sequence is an optional numeric field that will default from the pay component chosen for this pay line.
;[Sequence|PAY_POINT_SEQUENCE]: This field shows the unique sequence number assigned to each item processed in a pay point and determines the order of processing within a ‘Pay Point Type’. Pay_Point_Sequence will default from the pay component chosen for this pay line.
At line 212 changed one line
;[Task|PAY_POINT_TASK]:The pay point task identifies the kind of process within the pay point. Pay_Point_Task is a mandatory fixed lexicon ([X_PAY_POINT_TASK]) that you may use to look up the value.
;[Task|PAY_POINT_TASK]:The pay point task identifies the kind of process within the pay point.
At line 214 changed one line
;[Status|PAY_LINE_STATUS]:This field indicates if the pay lines is ‘Active’ or ‘To be deleted’. You have the option of deleting the line or marking it for deletion. When you delete a pay line through the ‘delete and commit record’ button in the horizontal toolbar, it is temporarily removed from the screen and will be physically removed by [UPAUDT]. If you choose to mark a pay line ‘to be deleted’ in the status field, it will be removed from immediate view but is still in the database; the line will then be physically removed from the database by the audit process ([UPAUDT]). Pay_Line_Status is a fixed lexicon ([X_PAY_LINE_STATUS]) that you may use to look up the value.
;[Status|PAY_LINE_STATUS]:This field indicates if the pay lines is ‘Active’ or ‘To be deleted’. You have the option of deleting the line or marking it for deletion. When you delete a pay line through the ‘delete and commit record’ button in the horizontal toolbar, it is temporarily removed from the screen and will be physically removed by [UPAUDT]. If you choose to mark a pay line ‘to be deleted’ in the status field, it will be removed from immediate view but is still in the database; the line will then be physically removed from the database by the audit process ([UPAUDT]).
At line 216 changed one line
;[Leave Type|LEAVE_TYPE_CODE]:If this is an attendance line then the leave type for that line is indicated in this field. Leave_Type_Code for [P2K_AT_LEAVE_POLICY_TYPES] is a 16-character alphanumeric optional field you may complete with a value from the LOV (F9) provided.
;[Leave Type|LEAVE_TYPE_CODE]:If this is an attendance line then the leave type for that line is indicated in this field.
At line 218 changed one line
;[End Date|END_DATE]:This field shows the end date of the pay line. End_Date is a mandatory date field that will initially default to the pay period end date but will change to the start date once the [pay component|PAY COMPONENTS] is entered. It can be overridden.
;[End Date|END_DATE]:This field shows the end date of the pay line. End_Date will initially default to the pay period end date but will change to the start date once the [pay component|PAY COMPONENTS] is entered. It can be overridden.
At line 220 changed one line
;[Audited|AUDITED]:If the Audited toggle is ON, the pay line has passed all the validation checks of the audit process ([UPAUDT]) and is ready to be processed through pay calculation. If the toggle is OFF, either the pay line has not yet been audited, or it has failed to pass the transaction audit. Audited is an optional toggle field that is system updated.
;[Audited|AUDITED]:If the Audited toggle is ON, the pay line has passed all the validation checks of the audit process ([UPAUDT]) and is ready to be processed through pay calculation. If the toggle is OFF, either the pay line has not yet been audited, or it has failed to pass the transaction audit. Audited is system updated.
At line 222 changed one line
;[Detail Generated|DETAIL_GENERATED]:If this toggle is ON, pay line detail has been generated for this pay line through ‘Save’, [UPTR] or [UPTL]. If this toggle is OFF, no pay line detail has been generated. Detail_Generated is an optional toggle field that is system updated.
;[Detail Generated|DETAIL_GENERATED]:If this toggle is ON, pay line detail has been generated for this pay line through ‘Save’, [UPTR] or [UPTL]. If this toggle is OFF, no pay line detail has been generated. Detail_Generated is system updated.
At line 224 changed one line
;[Posted Experience|POSTED_EXPERIENCE]:If the Posted Experience toggle is ON, the pay line has been updated to the experience application through the track experience process ([USEP]). If the toggle is OFF, the experience application has not been updated. Posted_Experience is an optional toggle field that is system updated.
;[Posted Experience|POSTED_EXPERIENCE]:If the Posted Experience toggle is ON, the pay line has been updated to the experience application through the track experience process ([USEP]). If the toggle is OFF, the experience application has not been updated. Posted_Experience is system updated.
At line 230 changed 3 lines
;[Work in Progress|WORK_IN_PROCESS]:If the Work in Progress toggle is ON, this pay line is considered a WIP transaction, which will be journalized to the Work in Progress account of the general ledger, instead of the GL accounts defined on the [IPPC] form. If the toggle is OFF, the pay line is a not journalized as work in progress. Work_In_Progress is an optional toggle field that is system updated but you may manually adjust.
;[Arrears Collected|ARREARS_COLLECTED]: This pay line is created by [UPAUDT] from the Sundry Arrears transaction and this toggle indicates this pay line is from Arrears and will be collected by [UPCALC]. If the Arrears Collected toggle is OFF, then this pay line is not an arrears. Arrears_Collected is an optional toggle field that is system updated but you may manually adjust.
;[Override Rate|RATE_OVERRIDDEN]:If the Override Rate toggle is ON, this pay line has had the defaulting rate altered. If the toggle is OFF, the pay line will display the original defaulting rate. Rate_Overridden is an optional toggle field that is system updated but you may manually adjust.
;[Work in Progress|WORK_IN_PROCESS]:If the Work in Progress toggle is ON, this pay line is considered a WIP transaction, which will be journalized to the Work in Progress account of the general ledger, instead of the GL accounts defined on the [IPPC] form. If the toggle is OFF, the pay line is a not journalized as work in progress. Work_In_Progress is system updated but you may manually adjust.
;[Arrears Collected|ARREARS_COLLECTED]: This pay line is created by [UPAUDT] from the Sundry Arrears transaction and this toggle indicates this pay line is from Arrears and will be collected by [UPCALC]. If the Arrears Collected toggle is OFF, then this pay line is not an arrears. Arrears_Collected is system updated but you may manually adjust.
;[Override Rate|RATE_OVERRIDDEN]:If the Override Rate toggle is ON, this pay line has had the defaulting rate altered. If the toggle is OFF, the pay line will display the original defaulting rate. Rate_Overridden is system updated but you may manually adjust.
At line 241 changed one line
;[PC|PC_CODE]:The details [pay component|PAY COMPONENTS] code(s) that default from the pay line [pay component|PAY COMPONENTS] code entered. For example, if a Time [pay component|PAY COMPONENTS] is entered on the pay line, then the Time and Earnings [pay component|PAY COMPONENTS] may be generated on the pay detail line. PC_Code from [P2K_PR_PAY_COMPONENTS] is a 4-digit numeric mandatory field that you must manually enter or use the LOV (F9).
;[PC|PC_CODE]:The details [pay component|PAY COMPONENTS] code(s) that default from the pay line [pay component|PAY COMPONENTS] code entered. For example, if a Time [pay component|PAY COMPONENTS] is entered on the pay line, then the Time and Earnings [pay component|PAY COMPONENTS] may be generated on the pay detail line.
At line 243 changed one line
;[Abbreviation|PC_ABBREVIATION]:This field provides a short description of the [pay component|PAY COMPONENTS] used for printing on check and deposit statements, lists and pay registers. PC_Abbreviation is a 16-character alphanumeric mandatory field that will default from the pay component chosen.
;[Abbreviation|PC_ABBREVIATION]:This field provides a short description of the [pay component|PAY COMPONENTS] used for printing on check and deposit statements, lists and pay registers. PC_Abbreviation will default from the pay component chosen.
At line 245 changed one line
;[Amount|AMOUNT_OVERRIDE]:This field shows the amount calculated as a result of applying the PC Calc Method. Amount_Override is an optional numeric field that will be populated by the system based on the pay component rules.
;[Amount|AMOUNT_OVERRIDE]:This field shows the amount calculated as a result of applying the PC Calc Method. Amount_Override will be populated by the system based on the pay component rules.
At line 247 changed one line
;[Rate|WAGE_RATE_OVERRIDE]:This field is the wage rate derived from the pay line rate and displayed in the basis of the [pay component|PAY COMPONENTS]. Wage_Rate_Override is an 18 digit optional numeric field that is system calculated based on the Time Basis indicated.
;[Rate|WAGE_RATE_OVERRIDE]:This field is the wage rate derived from the pay line rate and displayed in the basis of the [pay component|PAY COMPONENTS]. Wage_Rate_Override is system calculated based on the Time Basis indicated.
At line 262 changed one line
;:Rate_Basis_Override is an optional fixed lexicon ([X_RATE_BASIS]) that will be derived from the time basis indicated but may be overridden.
;:Rate_Basis_Override will be derived from the time basis indicated but may be overridden.
At line 264 changed 3 lines
;[Type|PC_DETAIL_TYPE]:'PC Detail Type' is used to determine the nature of the' Pay Line Details' that will eventually be created. The two main types are 'Entered Value', and 'Computed Value'. The other types are maximums and declining balance, which are not as common. The 'Entered Value' is populated (during save) with the value entered on the Pay Line. The ‘Computed Values’ are calculated based on the 'Calculation Method'. Only one ‘Computed Value’ is allowed per pay component detail. PC_Detail_Type is a fixed lexicon ([X_PC_DETAIL_TYPE]) that you may use to look up the value.
;[Calc. Method|PC_CALC_METHOD]:This field indicates the method by which an amount is calculated. PC_Calc_Method is an optional fixed lexicon ([X_PC_CALC_METHOD]) that will default from the pay component but may be overridden.
;[Description|DESCRIPTION]:This field provides detailed information on the Calc Method used. Description is a 50 character alphanumeric optional field that will default from the Calc Method.
;[Type|PC_DETAIL_TYPE]:'PC Detail Type' is used to determine the nature of the' Pay Line Details' that will eventually be created. The two main types are 'Entered Value', and 'Computed Value'. The other types are maximums and declining balance, which are not as common. The 'Entered Value' is populated (during save) with the value entered on the Pay Line. The ‘Computed Values’ are calculated based on the 'Calculation Method'. Only one ‘Computed Value’ is allowed per pay component detail.
;[Calc. Method|PC_CALC_METHOD]:This field indicates the method by which an amount is calculated. PC_Calc_Method will default from the pay component but may be overridden.
;[Description|DESCRIPTION]:This field provides detailed information on the Calc Method used. Description default from the Calc Method.
At line 276 changed one line
;:PC_Rate_Source is an optional fixed lexicon ([X_PC_RATE_SOURCE]) that will default from the pay component.
;:PC_Rate_Source will default from the pay component.
At line 278 changed one line
;[O/R User Variable|USER_VARIABLE_OVERRIDE]:You may wish to manually enter the user variable amount.For example, the user variable field may indicate a rate or 1.5 but for this particular transaction you may wish to enter 1.55. User_Variable_Override is an 18 digit optional numeric field that you may manually enter.
;[O/R User Variable|USER_VARIABLE_OVERRIDE]:You may wish to manually enter the user variable amount.For example, the user variable field may indicate a rate or 1.5 but for this particular transaction you may wish to enter 1.55.
At line 280 changed one line
;[User Variable|USER_VARIABLE_CODE]:This field shows the user variable that may be used according to the [pay component|PAY COMPONENTS] details set up. User_Variable_Code is a 16-character alphanumeric optional field that will default from the pay component but may be overridden.
;[User Variable|USER_VARIABLE_CODE]:This field shows the user variable that may be used according to the [pay component|PAY COMPONENTS] details set up. User_Variable_Code will default from the pay component but may be overridden.
At line 283 changed one line
up is shown in this field. Element_Code is an optional 16-character alphanumeric field that will default from the pay component but may be overridden.
up is shown in this field. Element_Code will default from the pay component but may be overridden.
At line 285 changed one line
;[Premium|PREMIUM_CODE]:If this pay line detail is a premium, it will contain the premium code. Premium_Code from [P2K_SA_PREMIUMS] is an optional 16-character field that you may complete with a value from the LOV (F9) provided.
;[Premium|PREMIUM_CODE]:If this pay line detail is a premium, it will contain the premium code. Premium_Code from
At line 287 changed one line
;[Audit Info|AUDIT_TEXT]:This fields will display the audit text generated for this line. This text is derived from the Audit Text field on the Pay Lines tab. Audit_Text is an optional alphanumeric field that will be updated by the system.
;[Audit Info|AUDIT_TEXT]:This fields will display the audit text generated for this line. This text is derived from the Audit Text field on the Pay Lines tab. Audit_Text will be updated by the system.
At line 289 changed one line
;[Pay Line Detail Status|PAY_LINE_DETAIL_STATUS]: This field indicates if the pay line is ’Active’ or ‘To be deleted’. You have the option of deleting the line or marking it for deletion. When you delete a pay line through the ‘delete and commit record’ button in the horizontal toolbar, it is temporarily removed from the screen and will be physically removed by [UPAUDT]. If you chooses to mark a pay line detail ‘to be deleted’ in the status field, it will be removed from your immediate view but is still in the database; the line will then be physically removed from the database by the audit process ([UPAUDT]). Pay_Line_Status is a fixed lexicon ([X_PAY_LINE_STATUS]) that you may use to look up the value.
;[Pay Line Detail Status|PAY_LINE_DETAIL_STATUS]: This field indicates if the pay line is ’Active’ or ‘To be deleted’. You have the option of deleting the line or marking it for deletion. When you delete a pay line through the ‘delete and commit record’ button in the horizontal toolbar, it is temporarily removed from the screen and will be physically removed by [UPAUDT]. If you chooses to mark a pay line detail ‘to be deleted’ in the status field, it will be removed from your immediate view but is still in the database; the line will then be physically removed from the database by the audit process ([UPAUDT]).
At line 291 changed one line
;[Action|PC_ACTION]:The PC Action determines whether a transaction item entered under this [pay component|PAY COMPONENTS] will be accumulated to the total value of the [pay component|PAY COMPONENTS], replace a prior transaction item, trigger a user calculation, or suppress a User calculation. PC_Action is a mandatory fixed lexicon ([X_PC_ACTION]) that will default from the pay component and may be overridden.
;[Action|PC_ACTION]:The PC Action determines whether a transaction item entered under this [pay component|PAY COMPONENTS] will be accumulated to the total value of the [pay component|PAY COMPONENTS], replace a prior transaction item, trigger a user calculation, or suppress a User calculation. PC_Action will default from the pay component and may be overridden.
At line 293 changed one line
;[Amount Processed|AMOUNT_PROCESSED]:This field shows the amount actually processed by the pay calculation process, after performing 'gross to net' assessment. The original transaction amount may be modified by the system based on the [pay component|PAY COMPONENTS] rules. For example, if there are insufficient earnings to take a deduction amount, the rule may indicate to take as much as possible with an arrears transaction being created to recover the balance at a later date. The amount processed would be the modified 'as much as possible' value. Amount_Processed is an optional numeric field that is system maintained.
;[Amount Processed|AMOUNT_PROCESSED]:This field shows the amount actually processed by the pay calculation process, after performing 'gross to net' assessment. The original transaction amount may be modified by the system based on the [pay component|PAY COMPONENTS] rules. For example, if there are insufficient earnings to take a deduction amount, the rule may indicate to take as much as possible with an arrears transaction being created to recover the balance at a later date. The amount processed would be the modified 'as much as possible' value. Amount_Processed is system maintained.
At line 295 changed one line
;[Distribution CR Mask|DISTRIBUTION_CR_MASK]:Distribution mask contains the distribution derived from the assignment, position, or job, overlaid by the distribution mask based on the credit GL code of the pay component. Distribution_CR_Mask is an optional 50-alphanumeric field that you manually enter or use the distribution editor to enter the value.
;[Distribution CR Mask|DISTRIBUTION_CR_MASK]:Distribution mask contains the distribution derived from the assignment, position, or job, overlaid by the distribution mask based on the credit GL code of the pay component.
At line 297 changed one line
;[Distribution DR Mask|DISTRIBUTION_DR_MASK]:Distribution mask contains the distribution derived from the assignment, position, or job, overlaid by the distribution mask based on the debit GL code of the pay component. Distribution_DR_Mask is an optional 50-alphanumeric field that you manually enter or use the distribution editor to enter the value.
;[Distribution DR Mask|DISTRIBUTION_DR_MASK]:Distribution mask contains the distribution derived from the assignment, position, or job, overlaid by the distribution mask based on the debit GL code of the pay component.
At line 307 changed one line
;[Premium|PREMIUM_CODE]:This field provides a user defined premium code that uniquely identifies this premium within the organization. Premium_Code is a 16-character alphanumeric mandatory field that you must manually enter.
;[Premium|PREMIUM_CODE]:This field provides a user defined premium code that uniquely identifies this premium within the organization.
At line 309 changed one line
;[Rate|PREMIUM_RATE]:This field shows the premium rate that is used in the premium calculation. Premium_Rate is an 18-digit numeric field.
;[Rate|PREMIUM_RATE]:This field shows the premium rate that is used in the premium calculation.
At line 311 changed one line
;[Basis|DRV_SPMD_RATE_BASIS]:The rate basis is the unit of measure that the associated rate is being stored or displayed in, for example, hourly, weekly, biweekly, semi-monthly, monthly, or annual. Rate_Basis is an optional fixed lexicon ([X_RATE_BASIS]) that you may use to look up the value.
;[Basis|DRV_SPMD_RATE_BASIS]:The rate basis is the unit of measure that the associated rate is being stored or displayed in, for example, hourly, weekly, biweekly, semi-monthly, monthly, or annual.
At line 313 changed one line
;[O/R Rate|PREMIUM_RATE]:This field holds the Premium Override rate you entered, which will be used in the premium calculation. Premium_Rate is an 18-digit numeric field.
;[O/R Rate|PREMIUM_RATE]:This field holds the Premium Override rate you entered, which will be used in the premium calculation.
At line 315 changed 2 lines
;[O/R Basis|RATE_BASIS]:The rate basis is the unit of measure that the associated rate is being stored or displayed in, for example, hourly, weekly, biweekly, semi-monthly, monthly, or annual. Rate_Basis is an optional fixed lexicon ([X_RATE_BASIS]) that you may use to look up the value.
;[O/R Basis|RATE_BASIS]:The rate basis is the unit of measure that the associated rate is being stored or displayed in, for example, hourly, weekly, biweekly, semi-monthly, monthly, or annual.
This page (revision-89) was last changed on 26-Nov-2021 10:22 by Karen ParrottTop