Skip navigation

Fixed Assets and Capital Asset Management are valuable modules that control and capture costs linked to asset records. However, upon obtaining this information, what tools exist that help a business organize and analyze these costs? The Equipment Cost Analysis module fulfills this requirement by extracting the cost data already captured by Fixed Assets and Capital Asset Management. Equipment Cost Analysis (Doc ID 1373970.1) details information that includes both set up and execution. Learn how this powerful tool can group equipment-related costs such that businesses can find the source of their costs in order to make more informed decisions about their assets.

NewFeature.pngUS Payroll - Tax Method H has been created for Non-Resident Aliens that are exempt from FICA (Social Security & Medicare) taxes but subject to FUTA (Federal Unemployment).

  • Tax Method = H
  • History Type = T

Refer to Tax Method For Non-Resident Alien Exempt From FICA But Subject To FUTA (Doc ID 2024726.1) for Electronic Software Update details.

Have you tried ending an employee’s benefit or change an amount/rate and received an end date that you were not expected?  Let’s examine how ending benefit plans work.


DBA History plays a big part in how DBA plans will end.


Enrollment w/Eligibility

If payroll history exists:

  • The system updates the employee’s deduction, benefit, accrual (DBA) instructions with an ending date for the associated DBA
  • Depending on how the enrollment ending date corresponds to the payroll cycle, the ending date for the DBA might differ from the enrollment ending date
  • Typically, the ending date for the DBA is the date on which the DBA was last recorded in the employee’s payroll history; that is, the last time that a deduction was made from the employee’s payroll
    • If the enrollment ending date is greater than the DBA history date, the date that the system assigns for the DBA ending date is the enrollment ending date
  • When you end an employee’s enrollment in one plan at the same time that you enroll the employee in another plan, the effective date of the DBA associated with the new plan is equal to the effective enrollment date for the new plan.


Enrollment Overrides

  • Requires manual entry
  • Eligibility requirement are waived
  • Enter the actual date on which you want to stop the benefit plan


If payroll history exists:

  • The system updates the employee’s DBA instructions with an ending date for the associated DBA
  • Depending on how the enrollment ending date corresponds to the payroll cycle, the ending date for the DBA might differ from the enrollment ending date
  • When the enrollment ending date is greater than the DBA history date, the date the system assigns for the DBA ending date is one day prior to the enrollment ending date.
  • When the enrollment end date precedes the date on which the DBA was last recorded in the employee’s payroll history, the DBA ending date is the payroll period end date that was last recorded in the DBA record


When you end an employee’s enrollment in one plan at the same time that you enroll the employee in another plan, the effective date of the DBA that is associated with the new plan is the same as the effective enrollment date for the new plan if the enrollment date is after the DBA history date. Otherwise, the new DBA begin date will be one day after the DBA payroll history date, which is different from the enrollment date. This situation generally occurs when you correct a mistaken enrollment after payroll has been processed.


NOTE: When no payroll history exists, the system will process the instruction regularly without end-dating it. While Batch Enrollment was not mentioned, the same applies.


Vertex Release 4.1

Posted by ShellyC-Oracle Jun 26, 2015

Announcement.pngAttention US and Canadian Payroll users, the JD Edwards EnterpriseOne code change required for Vertex Release 4.1 is available for download from the Update Center.


What's New in Release Vertex 4.1?


Federal Tax Recalculation

The following states have a new formula for calculating annual state taxable wages.

  • Alabama
  • Iowa
  • Missouri
  • Oregon

The formula for calculating annual state taxable wages includes a deduction for the employee’s annual federal withholding tax amount.  State tax withholding is calculated based on the annual state taxable wages. 


New Tax Method

JD Edwards is providing a new tax method, for Non-Resident Aliens who are exempt from FICA (social security and medicare) but subject FUTA.


Quantum for Payroll - Vertex Release 4.1 (Doc ID 2002367.1) provides a description of the new functionality and the associated bugs by release.


A/R Draft Payments

Posted by ChristyH-Oracle Jun 24, 2015

In various parts of the world it is common to pay your suppliers or receive money from your customers using a payment instrument called drafts. Drafts can go by different names. In the Asia Pacific region they are used for post-dated checks, whereas in the US they are used for credit card payments.


Drafts are essentially a promise to pay: your customer promises you, via a letter, by returning the slip at the bottom of an invoice or a statement, or via a credit card slip, that there will be enough money in their bank accounts to pay the invoice.


This payment instrument allows for direct communication between your bank and the bank of your supplier or customer.


Because of this and because they are initially only a promise to pay, using a draft to pay your obligations, or to receive money for obligations owed to you, the legal nature of the underlying liabilities is affected. This is the reason why you must classify, track, and report drafts separately from other types of payments and obligations. This is the reason why draft processing in JD Edwards EnterpriseOne goes through different statuses.


An Advisor Webcast on A/R Drafts is planned for later this year; the target date currently is in August. Please check Advisor Webcast JD Edwards EnterpriseOne Schedule and Archived Recordings’ (Doc ID 1450327.1) for details on the exact date and how to sign up for it.


In the meantime have a look at the following KM articles for more information:

  • How To Set Up and Process Drafts In EnterpriseOne Accounts Receivable (Doc ID 760933.1)
  • FAQ - Frequently Asked Questions on Accounts Receivable Draft Processing (Doc ID 965170.1)

Enhancement Bugs are written to request functionality that does not currently exist in the standard functionality of the system.  Clients are welcome to utilize Quest to assist with the disposition of and increase visibility for the requested enhancement. If you are a member of Quest User group please refer to Enhancement Requests via Quest User Groups (Doc ID 1192883.1) for increasing visibility of enhancement requests.


Legislative/Regulatory Bugs are also coded as Enhancement Bugs however, what sets them apart from a standard enhancement is the Desirability field located on the Bug template. All Legislative/Regulatory Bugs are coded with a Desirability of “0” which flags it as a Legislative/Regulatory Compliance Bug.


Note: Both Legislative/Regulatory and Enhancement Bugs go through a review process with the cross functional team which consist of Development and Product Strategy. Legislative/Regulatory Bugs however do not require Quest User Group visibility.

Announcement.pngCalling all Australia Payroll users!  The tax rates for financial year 2015-2016 are available.  Please access Australia Tax Information for July 1, 2015 through June 30, 2016 (Doc ID 1127623.1).


The information provided is based on Oracle's interpretation of the information published in the Australian Tax Office (ATO) guidelines.  If you plan to use the tax scales, you acknowledge and agree that the information contained in these updates is only intended to act as a guide. We recommend that you seek independent, professional advice regarding taxation obligation compliance.  Also visit the ATO website for tax scales, statement of formulas, etc.

Year-End Processing for Australia's 2014-2015 Financial year is just around the corner.  The ESU is available for download.  The bugs can be found in 2014-15 PAYG Year End Processing Update Information (Doc ID 743166.1).

Don't forget to access the Payroll Year-End Information Center (Doc ID 1377566.2).  This is your one stop shop for all things year end. When you access the information center, select the Use Tab, then Australia Payroll.  The information center is a compilation of important KM articles that will assist you with the process.

What's New In Your Year-End ESU?

  • The threshold for Lump E changed from $400-$1200 (effective 1 July 2015).
  • There's a new processing option in the Create Payment Summary Extract, R75A0140 that allows you to enter the threshold amount.  Note:  The threshold was previously hard coded, now it is controlled by the value in the processing option.


Year-End Processing Steps:

Step 1:  Data Preparation

  • Ensure that your summary history files are up to date.  Run the Payroll History Reconciliation, R75A7703
  • Run PDBA Rollover, R07390 to carry forward balances for deductions, benefits and accruals
  • Repost (if necessary), only consider if your detail and summary history tables are out of sync.

Step 2:  Setup

  • Company Address
  • Employee Names
  • Reporting Codes

Step 3:  Extract Payment Summary Information

Step 4:  Review Payment Summary Data

Step 5:  Revise Payment Summary Data (if necessary)

Step 6:  Add Fringe Benefit Taxable information

Step 7:  Print Payment Summaries

Step 8:  Create ATO Electronic File (EMPDUPE)


For more information on Australia Year-End processing for financial year 2014-15, please refer to the Advisor Webcast on the topic.  You will have access to the recording as well as the power point presentation.  Additionally, the E1 HCM Community has been updated with the Q&A from the advisor webcast.  You can continue discussions on the topic here as well.


The JD Edwards EnterpriseOne Applications Australia/New Zealand Payroll Implementation Guide will provide a wealth of information pertaining to and processing year-end.

Automatic Accounting Instructions (AAIs) are the backbone to the JD Edwards EnterpriseOne accounting system. You can think of AAIs as a set of rules where each one is associated to a specific account in the Account Master (F0901) and is used to determine what accounts should be used for specific transactions and postings. For example, there are AAIs that determine the Bank Account used on a voucher or an invoice during entry, or the Trade Account during posting of the transaction. Each AAI works as a different rule. EnterpriseOne has AAIs that for taxes, discounts, gain and loss, and much more.


Automatic Account Instructions are defined in application Work with Automatic Accounting Instructions (P0012) and there are specific AAIs hard coded to be used as different rules. For example, “PB” is used for determining the Accounts Payable Bank Account. The “PKL” AAI item is also used in Accounts Payable, but it is used to determine the posting account when a discount amount is lost during payment.


Depending on the AAI Item, you can also use GL offsets, Currency Codes, ranges of accounts and adjustment codes as suffixes to create a more flexible accounting system. Which AAI is used is determined based on a hierarchy and can vary depending on the AAI in question.


For more information on the AAIs in Accounts Payable, including a video, visit How To Set Up Automatic Accounting Instructions (AAIs) Within EnterpriseOne Accounts Payable (P0012) [Video](Doc ID 1991354.1).


If you are having issues with AAIs in Accounts Payable, please review our new Troubleshooting Automatic Accounting Instructions Within EnterpriseOne Accounts Payable (P0012)(Doc ID 1991402.1).


Need more information on Accounts Receivable AAIs? Review Overview and Set Up of Accounts Receivable Automatic Accounting Instructions (P0012) [Video](Doc ID 1982411.1). Or are you having an issue related to AAIs in AR? Review the new Troubleshooting Account Receivable Automatic Accounting Instruction AAI Errors (P0012, R09801)(Doc ID 1983922.1).

Watch this video to find out how JD Edwards EnterpriseOne Mobile Expense Management leverages the capabilities of smart phones and tablets to enable today's mobile workforce to simplify expense reporting, accelerate the approval process, and control adherence to company policies.

Welcome to the new world of the Industrial Internet of Things where machines, along with people and processes, are connected, enabling solutions which were previously not possible.

Watch this presentation to learn how the Internet of Things—also known IoT—helps you capitalize on your JD Edwards EnterpriseOne investment by increasing operating effectiveness and revenue while at the same time reducing costs.

Whether a seasoned veteran or a newbie, learning a new ERP system can be an uphill battle, regardless of the position one holds, which makes it nice when a software vendor can do something to help increase the upskilling of individuals learning the product.


One way JD Edwards completes this task is with its naming convention.  Really?  JD Edwards naming convention?  Are you serious!?  How can a codename actually help a user to better understand E1 vs a longer, more descriptive, name which may be more intuitive!?  Whoa there, I hear what you are saying, but there really has been a plan all along with this method, which has served JD Edwards well for many years and actually leads to a lower total cost of ownership.


No doubt you have heard words of wisdom all of your life, for instance:


"Time is really the only capital that any human being has, and the only thing he can’t afford to lose." —Thomas Edison


Our naming convention actually helps to fulfill your need to save time.  The real Business Reason behind a standard naming convention is that it promotes:

  • Understanding
  • Taking ownership
  • Governance
  • Reporting
  • Integration

Consider this fact about the potential complexity with tables.

In 2007 there was a posting stating SAP has over 125,000 standard tables,

The handy reference on this third party site,, lists EnterpriseOne 9.1 as having a total of 5112 tables. Although, I am not certain this is the exact amount, even if it were 10,000 tables, the less complicated JDE data model would be significantly easier to understand than SAP’s 125,000+.  This is low TCO (total cost of ownership) by design!!!


Ok, so there are fewer tables, which means less JD Edwards EnterpriseOne 9.1 Business Process Models (Doc ID 1642289.1), but what does this have to do with the naming conventions?


In JD Edwards, the naming convention for objects tells you the:

  • Object type
  • System code
  • Group type


For example,

  • F = File
  • Position 1-2: Is the System (09 General Accounting / 41 Inventory / 12 Fixed Asset / 09E Expenses, etc.)
  • Position 3-4: 01 (Master Table) 11 (Detail Table) 02 (Balance / Summary)

What is F0911?

  • File + General Accounting + Detail Table

And F0902?

  • File + General Accounting + Balances Table


Of course, these are simple examples but with this "basic" tip you can navigate most key important data models in JDE.  And the best part is this naming conversion doesn’t end with the tables.  Naming conventions are used for all object types.  See the following diagram taken from the JD Edwards EnterpriseOne Tools Development Guidelines for Application Design Guide under Chapter 3 Understanding JD Edwards EnterpriseOne Naming Conventions




Using this foundation, you can begin to learn the ins and outs of the product quicker, and if you are developing new content, simply use the same convention with system code 55-59 to identify custom objects and the transition is an easy one!  For more details on the naming convention for all of the object types, including new ones not shown in the graphic, see the JD Edwards EnterpriseOne Tools Development Guidelines for Application Design Guide under Chapter 3 Understanding JD Edwards EnterpriseOne Naming Conventions.

Filter Blog

By date: By tag:

Welcome to the My Oracle Support Community! We highly encourage you to personalize your community display name to make your activity more memorable. Please see for instructions.