Skip navigation

Reader.pngSpec Merge Fails during installation of the Tools ESU for 9.2 (JN16206) and/or 9.1 (JM22219) on the following objects: P980051X, P980053X, P980060X, P98902X, and P98911X. A change was made that requires Tools Release 9.2.1 or greater for the above objects. This new KM document provides a workaround if you are unable to install Tools Release 9.2.1 along with the Tools Rollup ESU. "E1: ESU: Spec Merge Fails on Tools Rollup ESU" (Doc ID 2485840.1). http://ora.cl/ix4Wb

JD Edwards will only be implementing enhancements for the new IFRS 16/ FASB 842 requirements on EnterpriseOne 9.1 and 9.2 releases.  However, it is realized that there are customers that are not on these releases.

 

Lease Accounting Prior to 9.1 (Doc ID 2420929.1) is intended to outline our general product direction. Please note that is intended for informational purposes only.  The workarounds are only suggestions and may or may not be a solution for all customers.

 

This document will outline how JD Edwards’ customers might leverage JD Edwards Fixed Assets, General Accounting and Accounts Payable modules to meet the change in Lease Accounting Standards (for Finance and Operating Leases).

 

It is recommended that you seek professional advice to follow accounting entries through from a local certification, compliance and verification perspective before implementing.

news-announcement-293x240.jpgJD Edwards announces the general availability of JD Edwards EnterpriseOne Applications Release 9.2 Update 3.  Applications Release 9.2 Update 3 is a cumulative Update that contains all Application patches, certifications, localizations, regulatory and ERP enhancements that have been delivered since GA Release of Applications 9.2 in October 2015 up through enhancements released in October 2018.

 

* KM document "JD Edwards EnterpriseOne Applications Release 9.2 Update 3 Now Available" (Doc ID 2484501.1) provides the information you need to know about the new Update (UN3) now available. http://ora.cl/dF5xN

 

* KM document "EnterpriseOne Software Cumulative Updates Information" (Doc ID 741781.1) has been updated with the 9.2 Update 3 information including Special Instructions and a spreadsheet of the bugs and objects included in the Update. http://bit.ly/E1SoftwareCumulativeUpdates

 

* KM document "Available Baseline ESUs" (Doc ID 1053900.1) has also been updated with the 9.2 table of baselines to include those that are included in UN3. http://bit.ly/E1BaselineESUs

Reader.pngThis new KM document provides a list of the User Defined Objects (UDOs) used with 9.1 Lease Management features. It starts with information about the ESUs for the UDOs and then has a table of the UDOs component type, bug UDO ID, description, application, form ID, version and query. Doc ID 2466423.1. http://ora.cl/M1GD4

attention.jpgThis new KM document announces the removal of the JD Edwards EnterpriseOne Multi Tier images from the Oracle Cloud Marketplace and Oracle Software Delivery Cloud. Doc ID 2466416.1. http://ora.cl/k4iC6

Reader.pngThis new KM document looks at a scenario where two users are entering sales orders using the P4210 application for the same customer and item that could result in a negative allocation. Doc ID 2474709.1. http://ora.cl/3DE3t

JD Edwards EnterpriseOne Architecture Overview – Layered Architectural Style & MVC

Figure 1 represents a typical layer in the light ERP software. Java machine layer or representation layer represents the attribute of the individual application. This layer can access the database directly using JDBC or call the logic (business functions) in the application logic layer. Then these business functions call various standard APIs including the instruction on how to access database and represent it in the functions using ODBC middleware. Furthermore, this architecture leaves room for the additional interface for the future extension – Applications Interface Services (AIS) server which makes use of the code written in the Application logic layer.

layered.jpg

       Figure 1. Layered Architecture

 

Above figure contains both interactive and batch applications where interactive applications can be modeled using an MVC framework. MVC pattern comprises the Model (data), View (presentation), and Controller (logic) relationship as depicted in figure 2. This MVC architectural pattern follows a typical layered architectural style.

 

mvc.jpg

       Figure 2. MVC Pattern for Interactive Application

 

In MVC architecture pattern, a model is an instruction on how to manipulate data by calling a master business function. A view is the output of data either manipulated by the controller or returned value itself where traditional software represents data using a business view. And a controller defines the interface including how to call the model functions.

Reader.pngWith Tools Release 9.2.2.6 and above you may see AIS Proxy Caller [SEVERE] [RUNTIME] error messages in the jas logs when you're not using AIS. These can be corrected by a simple change to the jas.ini. See Doc ID 2473999.1. http://ora.cl/Xs8BU

Reader.pngThis new KM document illustrates how to call an external REST call that uses OAuth 2.0 from Orchestrator using Connector. http://ora.cl/nw0M1

Reader.pngThis new KM document describes the support policy around Oracle database features: materialized views, synonyms, data streams, high availability, and backup. Doc ID 2473478.1. http://ora.cl/f06Ia

Oracle JD Edwards EnterpriseOne previously published a Reference Architecture best practices white paper for implementing JD Edwards EnterpriseOne on Oracle Cloud Infrastructure with preconfigured security and high availability (HA). JD Edwards has automated this reference architecture to accelerate the deployment of JD Edwards EnterpriseOne Applications 9.2 including the latest enhancements and patches with Tools 9.2.3 on Oracle Cloud Infrastructure and reduce the total cost of implementation.

 

JD Edwards Reference Architecture Automation for OCI
Provisioning of JD Edwards reference architecture on OCI leverages Terraform automation for Infrastructure provisioning (Creating VCN, VMs, DBS, Storage, Load Balancer, and Security) and One-Click Provisioning automation to deploy JD Edwards EnterpriseOne components. The target environment provisioned using the Reference Architecture automation can be a new JD Edwards instance for new businesses or expanding to new geographies or can be further leveraged for:  

  • Lift & Shift to Oracle Cloud Infrastructure for customers on Application release 9.2.x
  • Move & Improve on Oracle Cloud Infrastructure (Upgrade to code current as part of Lift & Shift to OCI) for customers on JD Edwards Application releases 9.0.2 and 9.1.

 

Benefits of Reference Architecture

  • Optimized for Oracle Cloud Infrastructure
  • Preconfigured Security
  • High Availability
  • Validated by JD Edwards with each release cycle
  • Consistent implementation on OCI
  • Reduces risks (tested configuration) and streamlines support

      

Supported Environment

Release: JD Edwards EnterpriseOne Applications Release 9.2 (code current) and Tools 9.2.3

Platform: Linux with Oracle Database Cloud Service

 

Support for Multiple Databases with JD Edwards One-Click Provisioning

Oracle also announces support to provision and configure multiple database servers for different path codes on Oracle Database Cloud Service or Oracle database installed on OCI. Customers can leverage Terraform automation to provision multiple Oracle Database Cloud Service Instances and use One-Click Provisioning to deploy JD Edwards’s database schema. JD Edwards One-Click Provisioning supports up to five databases one per each pathcode (Shared, PD, DV, PY and PS)

 

Supported Environment

Release: JD Edwards Enterprise One Applications releases 9.2 and Tools 9.2.3

Platform: Linux with Oracle Database

 

For more information, see the following resources:

 

 

This announcement demonstrates Oracle’s continuing investment in JD Edwards products and our commitment to our customers to enable their journey to a digital enterprise.

Around this time of year we field many questions about the problems with the Received not Vouchered Account.  A few questions and answers follow:

 

Question 1:  We have open receipts where we paid the supplier using accounts payable or that we do not need to pay the supplier for. How can we clear the open RNV (Received Not Vouchered) from the receipts without reversing receipts?

Answer 1: In the case that receipts cannot or will not be reversed, the best way to clear the remaining RNV is to perform the following.

  1. Create a 3-way Voucher Match selecting the open receipt with Match Option 1.
  2. In the voucher add a second line (Match Option 4) for a negative amount. The account number used for the new line will be a business decision based on why the receipt is being closed. This negative line will offset with a Credit to the A/P trade account creating a zero-dollar voucher.
  3. Post the net zero-dollar voucher.

Note: Ensure that the added line is a negative lump sum amount (typically a J line type) with a valid Account Number. Also, set the P4314 processing options to NOT create a new line on the purchase order unless you want to wash the dollar amounts on the PO as well.

This information is also documented in Voucher Match FAQ (P0411 / P4314 ) (Doc ID 1305052.1).

 

Question 2: What tools are available to help analyze the Received not Vouchered Account?

Answer 2:  We have a set of programs that can be used to reconcile the Received Not Vouchered Account.  These are described in the following knowledge document:  Voucher Logging and Received Not Vouchered (RNV) Clearing Account Reconciliation (R09150)(Doc ID 986024.1)

 

In addition, there are some reports available:

  • R43450  Received not Vouchered Reconciliation Report

 

And if you have licensed One View, the following reports are available from  Program P43260 One View Purchase Order Receipts Inquiry:

  • Received not Vouchered by Company; Received Not Vouchered by Fiscal Period; Received Not Vouchered by Item; and Received Not Vouchered by Supplier

NewUpdate.jpgThe KM documents for 'Resolving Processing Errors Due to Year-End ESU Install' have been updated for the 2018 ESUs. One document focuses on the year-end ESU for 1099s, the other document focuses on the year-end ESU for US Payroll W2s and Canada Payroll T4s. Both documents take you through the steps for obtaining, installing and verifying the ESU installation as well as performing the necessary package build and Special Instructions.
* 1099s Doc ID 1596756.1 http://ora.cl/SVC
* W2s and T4s Doc ID 1919314.1 http://ora.cl/AE3YH

Reader.pngThis new KM document illustrates how to create and then test a connector using Service Request and Orchestration. Doc ID 2473399.1. http://ora.cl/pK7SI

Reader.pngThis new Demand Scheduling KM document provides workarounds if receiving "Error: Date Invalid" for Create Schedule (R40R010) for one-off or emergency orders. Doc ID 2473386.1. http://ora.cl/K5Y6Q

Reader.pngThis new KM document provides a method to automate starting and stopping the Scheduler Server in JD Edwards EnterpriseOne during the maintenance tasks by using a script. Doc ID 2470281.1. http://ora.cl/x7rV8

Reader.pngThis new KM document shows, with screen prints and step-by-step instructions, how to display a Google Map in a CafeOne layout. Doc ID 2469978.1. http://ora.cl/Mg7B3

Sometimes when creating an Equipment or Service work order for an asset the system gives the errors “There is an existing Work Order”, CAM error 1A69 or SWM Error ID 113T.  The hard errors stop user from simply entering an additional work order for the asset leaving users confused as to why and asking how to correct this issue. Don’t worry the information in the below document will answer that question for you.

 

Equipment Error ID 1A69 or 113T Work Order Already Exists (Doc ID 885798.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 https://community.oracle.com/docs/DOC-1022508 for instructions.