This preface discusses:
JD Edwards EnterpriseOne products.
JD Edwards EnterpriseOne application fundamentals.
Common fields used in this implementation guide.
This implementation guide refers to these JD Edwards EnterpriseOne products from Oracle:
JD Edwards EnterpriseOne Accounts Payable
JD Edwards EnterpriseOne General Ledger
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 Financial 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 Financial Management Application 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
Address Number |
A number that identifies an entry in the JD Edwards EnterpriseOne Address Book system, such as employee, manager, or supplier. |
Effective Date |
The date when a transaction or policy rule becomes effective. If you leave this field blank, the system will use the current system date as the effective date for the policy rule. |
Employee ID |
The address book number of the employee for whom the expense report is submitted. The system completes this field with the address book number of the person who is signed on to the system. If you have authority to enter expense reports for other people, enter the address book number of the person for whom you are entering expenses. |
Expense Category |
A user-defined code (09E/EC) that categorizes expenses. Expense categories include airfare, meals, hotel, and car rental. |
Expense Location |
A user-defined code (09E/EL) that indicates where the expense was incurred. The system uses location information to determine the appropriate policy expense limits to which the expense applies. For transportation expenses, use the location where the ticket was purchased. |
Expense Report Type |
A user-defined code (09E/RT) that describes the expenses on the report. Examples of expense report types include travel and entertainment, relocation, and tuition reimbursement. The expense report type determines which expense categories from the policy are available for entering expense report detail information. |
Payment Method |
A user-defined code (09E/PM) that indicates how an employee paid an expense. For example, the employee might have used a credit card, cash, or personal check to pay the expense. |