This preface discusses:
JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne application fundamentals.
Common elements used in this implementation guide.
This Implementation Guide refers to the following JD Edwards EnterpriseOne product from Oracle: JD Edwards EnterpriseOne Payroll.
Additional, essential information describing the setup and design of the system appears in a companion volume of documentation called JD Edwards EnterpriseOne Human Capital Management Application Fundamentals 9.0 Implementation Guide.
Customers must conform to the supported platforms for the release as detailed in the JD Edwards EnterpriseOne minimum technical requirements. In addition, JD Edwards EnterpriseOne may integrate, interface, or work in conjunction with other Oracle products. Refer to the cross-reference material in the Program Documentation at http://oracle.com/contracts/index.html for Program prerequisites and version cross-reference documents to assure compatibility of various Oracle products.
See Also
JD Edwards EnterpriseOne HCM Fundamentals Preface
A companion Guide called About This Documentation contains general information, including:
Related documentation, common page elements, and typographical conventions for guides.
Information about using guides and managing the documentation library.
Information on the International Organization for Standardization (ISO) country and currency codes used within documentation.
A glossary of useful JD Edwards EnterpriseOne terms that are used in documentation.
See Also
About This Documentation Preface
Managing the Online Library and Implementation Guides
ISO Country and Currency Codes
Glossary of JD Edwards EnterpriseOne Terms
Auto Deposit Date |
Enter the date on which the funds are to be deposited into the employees' bank accounts. The system uses this date when creating the Auto Deposit Workfile. The default value for the Auto Deposit Date field is either the system date or the date that the system calculates from the payment offset. You can override the payment date by entering a value in this field. |
Check Date |
Enter the date that the payment will be issued. This date relates to a payroll check, an interim payment, a bank automatic-deposit advice slip, a payslip (cash), or a claim reimbursement. The default value for the Check Date field is either the system date or the date that the system calculates from the payment offset. You can override the payment date by entering a value in this field. This date must meet these criteria: The payment date must be greater than or equal to the ending date. Payment dates must be in ascending sequence throughout the year. If an ending date or check date for one period overlaps the ending date or check date for another pay period, the system displays an error message when you click OK. You can either change the information so that no dates overlap, or override the error. To override a conflicting date error, on some forms you can select the row that is in error, and then select Clear Date Edit from the Row menu. |
Date - Beginning Effective |
Enter the beginning date of the range of effective dates. |
Date - Ending Effective |
Enter the end date of the range of effective dates. |
Ending Date |
Enter the last day of a processing period (pay period, month, quarter or year). If an ending date or check date for one period overlaps the ending date or check date for another pay period, the system displays an error message when you click OK. You can either change the information so that no dates overlap, or override the error. To override a conflicting date error, select the row that is in error, and then select Clear Date Edit from the Row menu. |
From |
Enter the first date in a range of dates. |
Gross Pay |
Enter the actual gross pay amount for an employee. This amount is different from the distributed gross pay amount used for labour distribution. See data item DPAY. On Work Order Time Entry, use this field to record miscellaneous pay for an employee, such as piece rate bonus. |
Marital Status |
Enter the employee's federal marital status from the 668-W form. Marital Status will be automatically copied from the employee master if it is not entered. This code is used in the computation of all tax levy deductions. |
Payroll ID |
Enter the code that identifies a group of employees for whom you are processing payroll. Use this ID to process each step of the payroll cycle. This code is also used to identify the interim ID that you select when you enter interim payments. |
Report Version |
Enter the report version to run. This can be the version of the program that you are assigning to the specific payroll cycle step. You should use a consistent naming convention if you are processing multiple versions for more than one pay cycle step. For example, if you process three versions of each pay cycle step, you might name the three versions for each pay cycle step: MULTI1 MULTI2 MULTI3 |
T T (tax type) |
Enter the tax type code, which indicates the type of payroll tax being processed. This is a user-defined code (UDC) (07/TX). To set up state minimum wage amounts, you must enter MW in this field. To do so, you must first add MW to UDC 07/TX. However, you should not change the codes and definitions that are provided with the software. |
Tax Area , Work Tax Area , and Resident Tax Area |
Enter the code that identifies a geographical location and the tax authorities for an employee work site or the employee's residence, including employee and employer statutory requirements. This location is also used to identify the location and the tax authorities for U.S. unemployment or Canadian employment insurance rates. In the Vertex payroll tax calculation software, the tax area code is synonymous with GeoCode. To determine the valid codes for the location, refer to the documentation for the tax calculation software that you are using. |
Thru |
Enter the last date in a range of dates. |
Version |
Enter the version to use. The version is a user-defined set of specifications that control how applications and reports run. You use versions to group and save a set of user-defined processing option values and data selection and sequencing options. Interactive versions are associated with applications (usually as a menu selection). Batch versions are associated with batch jobs or reports. To run a batch process, you must select a version. |