Skip navigation

NewFeature.pngThe JD Edwards EnterpriseOne 9.1.5 release delivered a set of exciting new features.


We are approaching the end of the year.  If your company’s date pattern is set up as calendar year, now is a good time to prepare for the Annual Close.


There are several tasks that need to be completed as part of the closing process; including closing the accounting period, changing the financial reporting date and closing the fiscal year.  Before closing the year, there are several other tasks that need to be performed before the annual close can take place:


  • Verify General Ledger Automatic Accounting Instructions (AAIs)
  • Set up Leger Type points to close to retained earnings
  • Enter period-end accruals
  • Review and post all batches
  • Verify data integrity
  • Reconcile General Ledger to bank accounts
  • Run monetary account valuation and financial reports


In addition to these tasks, organization should develop their own detailed closing tasks and include them in their internal documentation. 


For more information on the Annual Close process, please review Overview of Annual Close Report (R098201) (Doc ID 664688.1), Frequently Asked Questions on the Annual Close Report (R098201) (Doc ID 664687.1) and How To Close A Fiscal Year In JD Edwards EnterpriseOne Financial Management Webcast Knowledge Information (Doc ID 1620858.1).


You can also replay a recording for an Advisor Webcasts on closing a Fiscal Year by visiting Advisor Webcast JD Edwards EnterpriseOne Schedule and Archived (Doc ID 1450327.1), select tab Archived 2012 and locate the recording EnterpriseOne General Ledger GA Year-End and Annual Close, dated December 19, 2012.

As a new year approaches, ensure that Shop Floor Calendars are defined into 2015 and beyond.  When running planning reports (R3482/R3483), two common errors occur when running planning against specific calendars - "Date Generation Failed" and "Shop Floor Calendar Not Setup.” Both errors are referring to a missing, incomplete, or unavailable date in the future on one or more branch plants that Materials Requirements Planning (MRP) is utilizing.  The Shop Floor Calendar must be setup to get MRP

to plan as required. Additionally, capacity planning will be impacted without proper calendar setup.


Take time to review your Shop Floor Calendars before it’s too late!


For additional information, see Shop Floor Calendar Setup and Use (Doc ID 1129994.1).

NewFeature.png"To improve is to change; to be perfect is to change often."


While working with packages, at some point of time these questions would have cropped into your mind:

- Why is the Client package built first and then Server package?

- Why is the client package even built when I only want to build a server package?

- Why waste time building a client package when it is not required?


And so here we are with a considerable change to the package build functionality and the above questions are now all addressed with the streamlined Enterprise One package build process delivered with Tools 9.1.5.


This enhancement changes the order of the package is. Previously, the package built the client package first and then the enterprise server package. We have now eliminated the step of building a client package when it is not needed. Prior to 9.1.5, when building the client package, the specs were built into a package’s local database, C code was generated from Named Event Rules (NERs), business functions were compiled and the resulting directories were compressed. For the server package, the specs were retrieved from the package’s local database, which was built by the client, and inserted into the main database under the package name. The server-only business functions were moved from the deployment server to the enterprise server and compiled.  If compression was specified in the jde.ini, the directories were then compressed. This completed the package build.


Once the EnterpriseOne web server was introduced, many customers no longer needed to build the client package each time, so the need for client packages has decreased.  Because the client side was built before the server side, time was wasted building the client package even though it was not needed.


This change has switched the order of processing and moves both the process of building the server specs and the generation of NER onto the enterprise server.



To create this functionality there are numerous changes that are done both at Client side as well on the server side for Full and Client packages. Multiple new objects are added. Some noteworthy changes are:

- R9621S is a new UBE that runs first and initiates the server package build.

- R9622C is a new UBE that runs next and initiates the client package build. The client build only occurs if it was selected in the application.

- The client package’s local specs are no longer used to build the server spec tables in the database. Building the specs happens on the enterprise server; whereas before this enhancement, it happened on the build (client or deployment server) machine.

- The Package Definition application now has an option to compress the server package and/or the client package. The jde.ini setting is no longer valid.

- The system moves the server log, svrpkgbuild.log, from each server to the deployment server. Also, the files located under the text directory on the enterprise server are moved to the deployment server.

- There is no generation of NERs’ .c and .h files on the client.



Primary Server:

The primary server is the enterprise server to where all the business functions’ .c and .h files are moved, where the generation of NERs’ .c and .h files takes place, and where the spec tables are updated in the database.  If there is only one enterprise server selected, all of the package processing is performed on that one enterprise server.  If there are multiple enterprise servers, the user is asked to select a primary server during the package definition. This will be the server to which all the .c and .h files are transferred and upon which the generation of NERs takes place.


Server-Only or Server/Client Update Package Builds:

For server-only or server/client update packages, the specs for the server will build in the Central Objects data source like the full package does.  During a server/client update package, the specs are retrieved from the server spec tables (<tablename>_<packagename>, for example, F98710_DV910UP) during the server processing and are inserted into TAM files on the deployment server.

- New Directories on the Primary Enterprise Server:

“Include_checkin”, “source_checkin” ,  “res_checkin”,   “GenerateNER_Logs”, "<enterprise server machine type  and version>  (for example,   INTEL6.0)", “work”

- New Directories on the Deployment Server:

"serverLogs”, “serverLogs/GenerateNER_logs”, “serverLogs/<enterprise server name>”


Deprecated Directories:

"pack", "make" , "mobile", and "mobiledb".


For full details of this new functionality see Server Only Packages Functionality - From EnterpriseOne Tools Release 9.1.5 Onwards (Doc ID 1947622.1)


There is also a document that includes FAQ’s, Known Issues, and Troubleshooting for the new build process which is essential reading and one I would recommend you bookmark!  This document is FAQ, Known Issues, and Troubleshooting Server Only Packages Functionality - From EnterpriseOne Tools Release Onwards (Doc ID 1950295.1).


How to get this functionality?

1) Upgrade to Tools 9.1.5

2) Install the latest Planner ESU for EnterpriseOne 9.0 / 9.1 to get the updated package build objects.


For the full announcement of Tools 9.1.5 please see Oracle Announces JD Edwards EnterpriseOne Tools Release 9.1 Update 5 and Application Enhancements (Doc ID 1952442.1)

Hopefully by now you have taken the 2014 1099 ESU and are ready to start testing the 1099 method you plan to use in January to print your returns. See Important Yearly 1099 Year End Processing Bug/ESU Information For JD Edwards EnterpriseOne - 9.0 & 9.1 ESUs Are Now Available for Download!! (P04515) [Video] (Doc ID 657337.1) for more information on 1099 ESUs.


The two knowledge documents below provide all the important steps to follow after you have taken the ESU; complete all required address book clean up, then follow either of these documents. Note: To use both, truly you use the GL method fully and then only use the AP Adjustment program to adjust your GL totals, you are not able to use both fully.

  • How to Use the A/P Method for 1099 Year End Processing [Video] (Doc ID 661888.1)
  • How To Use the G/L Method for 1099 Year End Processing (Doc ID 663804.1)


You can use the My Oracle Support Community for EnterpriseOne Financials (Financial - JDE1 (MOSC) to post a new thread with any 1099 questions you have and the 1099 team will be glad to assist!

Announcement.pngThe JD Edwards code change required for Vertex Release 4.0 is available. 


What’s New:

  • School district information is being integrated into the GeoCoder to provide a more robust data access for states with complicated tax scenarios driven by school district.
  • New form values (CPP Tax and CPP Wages YTD) used to calculate QPP
  • Canadian Basic Exemption will now use the Canadian Basic exemption amount; not zero
  • Vertex form for Additional Medicare Wages


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

Keeping up and learning new technologies can be a tough job, and whether you have been enjoying the E1Page functionality since our initial release or are a new comer, we hope you find the redesigned E1Page document to be a great resource.  We have combined the following two documents:


  • Quick Start Guide, Troubleshooting, Sample, TOI Document, and Presentation for E1 Page (Doc ID 1394280.1)
  • Overview, Download, and Quick Start Guide for the E1 Page Generator [Video] (Doc ID 1401833.1)


into one cohesive knowledge document:


  • E1: E1PAGE: Overview of E1 Pages Including How to Develop, Edit and Manage E1 Pages and Build Pages with the E1 Page Generator (Doc ID 1674258.2).


We hope the tabs and headings allow for a more intuitive navigation and easier consumption of the many topics E1Pages and E1Page Generator can cover. 


If you are new to E1 Pages, EnterpriseOne (E1) Pages are the first screen end-users see when they log into EnterpriseOne. EnterpriseOne (E1) Pages are a mechanism for embedding HTML based content directly into E1. Content can include:


  • Business Navigation Process Flows
  • URL Links (e.g. )
  • Links to Internal sites such as Employee Self Service
  • Embedded links to BI Analytics Pages
  • Corporate Branding
  • Documentation
  • Any Rich HTML Content
  • Applications
  • Reports / OVR
  • Portlets
  • Watchlists


In short, they are a collection of HTML Pages which can be assigned to a user, role or *PUBLIC and effectively serve as a simpler version of a Portal Solution. Upon being published to a given user, these E1 Pages appear as a set of tabs to the user upon logging into E1  and can be customized to feature a specific process flow or create a custom dashboard for the user.  The following is a screen shot of our Health & Safety Incidents dashboard available from the Update Center by searching under OneView Reporting|E1Pages.



There are several improvements with the 9.1.5 tools release which will enable E1Page developers the ability to create a more personalized experience.  These new APIs are discussed in the Javascript APIS for Improved User Behavior.  Before creating pages with 9.1.5, be sure to download the new 5.0.x E1Page Generator as it includes a bug fix and usability improvements that go along with the interface changes in 9.1.5.


Speaking of interface changes, there is now a choice between the standard or the new simplified navigation (kiosk mode) with 9.1.5. With the simplified user interface, E1 Pages is the single portal for end users whether they are external or internal, as they only have access to the applications provided through the E1Page interface.  See How to Configure, Create and Manage the Simplified Navigation Feature and Form UI changes with 9.1.5 (Document 1952072.1) for complete details on this new functionality.

Announcement.pngNEW FUNCTIONALITY AVAILABLE - JD Edwards Real-Time Financial Reconciliation Applications


JD Edwards EnterpriseOne Financials is pleased to introduce new functionality to help you manage data integrity in the General Accounting module for Release 9.1 with Tools Release 9.1.5

This new enhancement provides interactive integrity checking programs that enable you to instantly identify potential financial integrity issues with real time financial reconciliation instead of waiting to evaluate results from batch processes. After reviewing any issues, you can quickly resolve the integrity issues within the integrity checking programs.  This enhancement provides many benefits, such as:

  • Close your books sooner by finding and resolving integrity issues without waiting for a report
  • Reduce time to resolve issues with the ability to view and resolve discrepancies interactively
  • Eliminate the need to work with PDF output to review issues
  • Supplement your internal balancing procedures
  • Eliminate the need to run corresponding batch programs


For more information, please see JD Edwards Real-Time Financial Reconciliation Applications Overview (Doc ID 1952920.1).

Do you purchase items from different countries? Or manufacture/assemble items in countries other than your 'home' country? Do you have regulatory requirements specifying that you indicate the country of origin on outbound documents or data transmissions? The Country of Origin enhancement , available beginning with EnterpriseOne 9.1 release, has the solution for you. 


We’ve added functionality to capture the country of origin on the lot master record.  We've modified our applications to allow you to utilize, and require if desired, a country of origin value when new lots are created.


The Country of Origin (COO) enhancement allows you to assign, monitor, report, and manage the country of origin on inventory records throughout the supply chain. A new field, Country of Origin (ORIG), is available in the lot master application to store the country of origin value. With COO, you have the ability to differentiate lots within stocked items by country of origin, providing visibility into current inventory across all item lots.


Existing customers using JD Edwards EnterpriseOne 9.1 and customers migrating to JD Edwards EnterpriseOne 9.1 may wish to begin using the Country of Origin functionality. Three global update UBEs are provided to assist customers updating data to begin using Country of Origin:


Country of Origin Update for Items (R41806) Activates the Country of Origin Required flag on the Item Master (F4101) and Item Branch (F4102) records and then sets the Country of Origin field in the Item Branch records, F4102. Country of Origin Update for Lots (R41807), updates the Country of Origin in the Lot Master (F4108) table. Country of Origin Update for Weigh Tag Master (R31B8505), updates the Country of Origin in the Weigh Tag Master (F31B85) table.


See Document 9.1 Enhancement – Country of Origin Global Updates (Doc ID 1499120.1)


For more information on Country of Origin, refer to the following documents:


  • 9.1 Enhancement - Inventory Transactions and Setup with Country of Origin (Doc ID 1499023.1)
  • 9.1 Enhancement - Country of Origin in Sales (Doc ID 1499709.1)
  • 9.1 Enhancement - Country of Origin in Procurement (Doc ID 1491732.1)
  • 9.1 Enhancement - Country of Origin in Interoperability (Doc ID 1495435.1)
  • 9.1 Enhancement - Country of Origin Apparel PCW46 (Doc ID 1495078.1)
  • JD Edwards EnterpriseOne 9.1 Bulk Stock Management Country of Origin Enhancement (Doc ID 1619713.1)
  • JD Edwards EnterpriseOne 9.1 Bulk Stock Management Lot Enhancement (Doc ID 1620165.1)
  • 9.1 Enhancement - General Overview of Country of Origin Field Use in Manufacturing (Doc ID 1495671.1)

ic-MobilePhone-red.pngJD Edwards EnterpriseOne Mobile Framework, in conjunction with Oracle Mobile Application Framework, addresses the challenge of simplifying mobile application development, enabling developers to securely create and deliver a more customer-specific mobile experience. JD Edwards EnterpriseOne customers can maximize IT investments and lower application development costs for enterprise mobility, using tools that enable organizations to easily build and securely extend mobile applications. Read More

To stay current on what is Oracle’s value proposition for midsize companies, read Oracle Information InDepth: Midsize Edition. The current edition includes an update on JD Edwards mobile application releases and other information relevant to your midsize customer.

Encourage your customers and prospects to subscribe to this informative resource. Find instructions on how to subscribe here.

JD Edwards EnterpriseOne's In-Memory Sales Advisor harvests the power of the extreme performance delivered by Oracle Engineer Systems to leverage massive sets of real-time transactional information.


Oracle Engineered Systems power  JD Edwards EnterpriseOne In-Memory Sales Advisor  to provide unprecedented speed to gather, aggregate and summarize real-time customer, product, and sales data. The JD Edwards EnterpriseOne In-Memory Sales Advisor brings real time visibility to revenue opportunities during order capture to drive sales, eliminate manual processes, and provide great customer service.


Allow your customer service representatives to suggest cross sell products that are typically purchased with the products on an order and drive additional sales for product bundles and discount opportunities.


With JD Edwards EnterpriseOne In-Memory Sales Advisor you can run "What If" scenarios to determine the impact of changing sales conditions on profit and revenue.


Check out all In-Memory Sales Advisor has to offer in Oracle Announces an update to Oracle’s JD Edwards EnterpriseOne In-Memory Sales Advisor Application (Doc ID 1593597.1).

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.