Skip navigation



With the Year End Processing season rounding up, many of us stack our notes and user guides back on the shelves to wait for the coming year. Once the dust is settled and everyday routine resumes, we tend to forget about the busy scramble of December, January and February.


In leaving that behind, we also sometimes forget that everything we do and process for Payroll throughout the rest of the calendar year is in one way or another in preparation for those few months.


We have the opportunity to take small steps as we go to help the Year End Process flow more smoothly when the deadlines approach:


  • Run your Payroll Tax History Integrity reports once a month, or more often to catch errors as they arise and be able to address them on the fly: Doc ID 645601.1 - Payroll Tax History Integrity Report.
  • Are there any (legislative) changes effective for the new payroll year? Keep an eye on Payroll Alerts and Announcements: Doc ID 1462428.2 - Information Center: JD Edwards World U.S. and Canadian Payroll Products.
  • Stay afloat with the latest Payroll and HR updates: Doc ID 657268.1 -  World HCM Current Software Downloads.

Get creative. Think outside the box!



There are times when there is no existing functionality in the World applications dedicated to meet your specific goals. In some cases, you can take advantage of what might appear to be unrelated functionality to accomplish a task in lieu of customizing the software. For example:


  • You need to restrict the shipment of items to certain addresses.
  • You have an item that can be transferred between warehouses but not sold to outside customers.
  • You need to recalculate the weight of items on an order just prior to shipping the items.


Sometimes a little creativity goes a long way:


1.  You can’t set up item restrictions by ship-to address, but you can set up the Next Status preference profile to default an invalid next status code to a sales order line based on the ship to address, thus prohibiting the creation of such order lines.


2.  There’s no flag to designate that an item cannot be sold to an outside customer; however, you can create a new line type for such items, for which you can either:

    • Refrain from setting up order activity rules (P40204) for the new line type, or
    • Set up activity rules for the document type specific to transfer orders only (if you use the Sales Transfer program P4242)

If a user then attempts to enter the item on a sales order, the order entry program will error stating that activity rules aren’t set up for the order type and line type being used.


3.  There is no program in the World applications dedicated to updating the weight on existing sales order lines. However, did you know the Shipment Confirmation program (P4205) will update the weight on a sales order line if the associated field (SDITWT) in the sales order detail file (F4211) is blank?

To update the weight on a few order lines, you can simply access each order via order entry, clear the weight and then ship confirm the order lines. To update numerous order lines, you can:

    • Use SQL to clear the weight field in the appropriate F4211 records, and
    • Run the Batch Shipment confirmation program (P42051 – available as of the 9.2 release), which calls P4205 in batch mode.  


If you need ideas about workarounds that may help you to meet your goals, don’t hesitate to open a service request or post a question on the MOS community forum.


Are you currently upgrading to JD Edwards World release A9.3?


Are you interested in talking to, and sharing with others, who are currently upgrading?  Join a group of your peers for informative networking sessions. This Customer consortium consists of regularly scheduled conference calls bringing together Oracle customers who are implementing release A9.3, with Oracle representatives and business partners.  Guest speakers will join to share information on a particular topic – examples include:

  • Tips and Techniques
  • Lessons Learned and Best Practices
  • Security Considerations
  • Upgrade Planning
  • Change Management


Several Oracle representatives attend the calls to get your feedback, answer questions and help resolve issues – from Oracle Consulting, Field Readiness, Global Customer Support, Product Strategy and Customer Programs.  All presentations are posted on the JD Edwards World Consortium webpage on the Quest website (

Who can attend?

Any JD Edwards World customer evaluating, planning or in the process of upgrading should attend.  Business Partners are also welcome.  Content is targeted to technical manager, IT directors, Project Managers and “super users”.


When is it?

Calls take place on the first Thursday of the month at:

8am Pacific  /  9am Mountain  / 10am Central / 11 am Eastern (USA and Canada time zones)

Visit and subscribe to this User Group at no cost. For more information on the World Upgrade Consortium or to view past recorded meetings, please review  JD Edwards World Upgrade Consortium (Doc ID 1286970.1).

Many companies are acquiring, merging or even consolidating, which means changes to their charts of accounts. 




There are many points to consider before you tackle this projects, such as:


  • What is the expected business value outcome?
    • Administrative - Will this be difficult to maintain?
    • Compliance - Consider local and international accounting standards.
    • Daily use - Will the accounting staff understand the changes?
    • Will the changes return measureable benefit in terms of expense control and more accurate reporting?


  • What is the time frame to implement the task?
    • Is this a long term or short term plan?
    • Implementation / testing time.
    • Internal documentation updated?
    • Staff training.


  • What additional man hours are needed to accomplish this effort in terms of planning, implementing, testing and training?



Once you have determined that the change is needed, here are a few things to consider as you embark on the project:

  • What changes are expected to the chart of accounts?
    • How many companies?
    • How many business units per company?
    • Do you need to track divisions?


  • Consider special reporting  requirements:
    • Account Structure - Does this remain the same for BU, OBJ and SUB?
    • Level of detail - Do you need additional layers for reporting?
    • 3rd account number - Are you importing data from an acquisition and want to track previous account numbers?
    • Is there a need to group business units or accounts using Category Codes?
    • Is there a need to track detail specifics that make use of subledgers and /or enhanced subledgers?
    • Is there a requirement to follow IFRS – International Financial Reporting Standards?


Tips for a smooth project:


  • Create a project plan.  This is a must!
  • Create a Master Data Spreadsheet.
  • Consider what tools are already provided in JD Edwards World.
  • Do you have custom programs?  
  • Create a test environment to test prior to go-live.
  • Set a realistic go-live date.



Finally, here are a few Knowledge Documents to review on My Oracle Support to assist:

  • How to Standardize the Chart of Accounts (Doc ID 984333.1)
  • Global Changes to Business Units, Object Accounts and Subsidiaries (Doc ID 627074.1)
  • Changing the Company Number on Business Units (Jobs) and Accounts (Doc ID 626863.1)
  • How to Transfer Amounts (Detail and Balances) to Another Account (Doc ID 15578184.1)
  • Overview of the International Financial Reporting Standards (IFRS) functionality within JDE World (Doc ID 1296548.1)
  • Release A9.3 Introduces Enhanced Subledger Accounting and Reporting (Doc ID 1451614.1)
  • FAQ: Account Master (F0901) and Chart of Accounts (F0909) (Doc ID 972513)



Remember, if you have questions unique to your chart of accounts needs, or any general question, post your questions on the JD Edwards World Community for a quick response from Oracle experts, or to  get input from other customers.

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.