A new enhancement has been delivered to audit the activities performed on each batch of general ledger transaction; such as: who created the batch, when a batch was created , when the batch status was updated (approved, posted, reopened, reapproved, reposted, or deleted). An inquiry application (P00119 - G/L Batch Status History Inquiry) has been provided to review the batch status history. Refer to this new KM document for information about the ESU to install for implementing this new functionality. Doc ID 2648056.1. http://ora.cl/Wf0kJ
The Cash Basis error handling has been enhanced to improve user experience. When the report is processing a record and it runs into a failure, a detailed message will be written to the Work Center. The report will display the error message: Master Business Function Failure, see Work Center for details. Refer to this new KM document for information about the ESU to install for implementing the new functionality. Doc ID 2648034.1. http://ora.cl/FF2Uy
Starting with Tools Release 22.214.171.124, you can view the blob data as a string in Databrowser utility. This new KM document provides the steps and screen prints of what it will look like. Doc ID 2647652.1. http://ora.cl/x11WN
JD Edwards has been working on some requested functionality for Real Estate Management which include changes to facility set up, lease attachments, Sales Overage, global updates and subledgers for lease accounting.
Please see Enhancements for 9.2 Real Estate Management as of April 2020 (Doc ID 2663915.1) for the links to the ESUs to download and apply the new functionality.
This document provides the procedure that needs to be followed for JD Edwards EnterpriseOne LDAP authentication migration from one domain to another where the usernames are different than the first domain. Doc ID 2645803.1. http://ora.cl/bN3tb
In this webinar scheduled on May 4 hosted by @QuestUserGroup, learn how you can capture all the benefits of modern Oracle Cloud Infrastructure while still using #JDEdwards. Know more https://bit.ly/2XDo15w
This blog will help you to debug your Orchestration using Orchestrator Studio Debugger. From 126.96.36.199 Tools Release , we can debug the Orchestration Object from Orchestrator Studio.
The JD Edwards EnterpriseOne Orchestrator provides a way to debug your orchestrations. Debug Orchestrations is the tool that you can use to determine the state of your orchestration at any point during execution. Debug Orchestrations provides a view into an orchestration, enabling the designer to run an orchestration step-by-step and ensure that the data is correct at each step until the final orchestration output
As orchestrations become more complex, orchestration designers need a view of the data that is passed from one step to another to ensure that the orchestration is working as designed. Use the Debug Orchestrations to stop execution so that you can see the state of the orchestration at a specific point by reviewing the values of input parameters, output parameters, and variables. When the orchestration execution is stopped, you can review the output line by line to check for issues.
Orchestration debugger will be invoked when we click on the "Debug" button
Below features are available in Orchestrator Debugger
Run - Runs an orchestration until completion unless you set up breakpoints. If you set breakpoints, this option executes an orchestration till the breakpoint is reached or resumes a suspended orchestration.
Step Forward - Executes the orchestration one step at a time. When a step has been executed successfully, a green check mark appears on the step.
Stop Orchestration - Stops the execution of an orchestration.
Orchestration input - Shows or hides the dialog box to enter or edit the initial orchestration inputs.
Clear Break points - Removes all the breakpoints that you have set for the orchestration in the debug mode.
Close the debugger - Exits Debug Orchestrations.
For this demo purpose , we create the below simple orchestration to verify whether AB number is present in the system and notify via mail.
Follow the below steps to debug the Orchestration
Login into Orchestrator Studio
Select the Orchestration
Click Run Orchestration
We can set the break point by selecting the circle highlighted in the below screenshot
Breakpoints enable you to define where or when to halt the execution of an orchestration. You use breakpoints to run the orchestration until it reaches a certain step.
In the debug mode, a blue circle appears to the right of the step in the orchestration flow. You can set a breakpoint by clicking either the blue circle or the step in the orchestration flow. A blue dot appears next to the orchestration step indicating that the breakpoint has been set.
If you set a breakpoint and click the Run/Resume icon on the Debug Orchestrations panel, the orchestration runs until it encounters that step. To continue execution after the breakpoint, you can use the Run/Resume or Step Forward icons on the Debug Orchestrations panel.
Success condition debug flow
Failure condition debug flow
Data Section information - The Data tab displays all the available data that the orchestration consumes and generates, which includes the data that the orchestration consumes from a step. This tab displays the following information:
Step Variables. Displays all the variables created by the steps that have been executed. Variables from steps are added to the top of the list, so the most recent variables are shown at the top. Variables of single values like strings and numbers can be changed before resuming the orchestration. Variables containing arrays or JSON objects are read only.
Orchestration Inputs. Displays the values for inputs that were defined initially to start the orchestration.
System Values. Displays the values for the default inputs: User Address Book Number, User Name, System Date, and Orchestration Input. The values for these inputs represent the originator of the orchestration when executed at runtime. The system values are not editable as these are fixed for an orchestration.
History. Displays a record of the of the values for a variable that is overwritten. For each overwritten variable, click the History icon displayed in its row. The History dialog box lists the orchestration steps where the specific variable is used along with the values. Similarly, the Output tab displays the history of the overwritten output values.
Last Step section information - Displays the outputs generated from the previous step that was executed in the orchestration.
Output section information - Displays the accumulative output generated for all the steps in the orchestration until the breakpoint.
This new KM document explains with steps and screen prints how you can link to Google Maps using latitude and longitude into the Details tab of the Equipment Master Location Details (P17041 W17041A). Doc ID 2645490.1. http://ora.cl/OH7mF
Capabilities have been added to the Brazil solution that incorporates the requirements identified in the Nota Fiscal Technical Note (NT) nº 2/2016, version 1.60, which changes the layout of the fiscal document. This KM document provides information about the changes and the ESU required to get the changes for EnterpriseOne. Doc ID 2644971.1. http://ora.cl/eE5Qb
When the you create a progress payment voucher, it is created with a hold payment status. This new KM document explains what program to use to revise the pay status of the voucher to A (Approved) for payment processing. Doc ID 2644966.1. http://ora.cl/cC82E
Additional logging, such as debug logging, for Java Connector can be enabled using jdelog.properties file, which is present in the same location of jdeinterop.ini and the calling connector application. This new KM document provides the information to enable the settings. Doc ID 2644541.1. http://ora.cl/jC6ce
Still considering a move of your #JDEdwards instances to 64-bit? Get high level understanding of how #JDE supports 64-bit processing and read success stories on this LearnJDE page - https://bit.ly/2ReZhwx
Users can manually update the shipment weight in the Shipment Pieces form (W4915D), which cause a difference between the shipment weight and sales order weight. This new KM document explains the functionality and potential. Doc ID 2643959.1. http://ora.cl/3dx7U
Oracle announces an extension to our Premier Support policy for #JDEdwards EnterpriseOne 9.2. Oracle Premier Support provides comprehensive maintenance and software updates for your EnterpriseOne 9.2 release through AT LEAST 2031. https://bit.ly/3alobB1
Learn how to rapidly create and deploy your own #mobile apps using a combination of a browser-based development environment and JD Edwards EnterpriseOne orchestrations. The new “Build Your Own Mobile Application” learning path shows you how by leveraging #JDEdwards Orchestrator Studio and Oracle’s Visual Builder Cloud Service. Start now https://bit.ly/2UVQ4LI
Gain insights into modernizing your #JDEdwards platform with Jeff Erickson, Neil Pugh and a customer panel on April 20. Find out more about adopting technology updates to transform your business. Register today for this Quest Oracle Community webinar - https://bit.ly/3bS9s1M
This new Information Center is designed to consolidate product related information that may be valuable to you in dealing with business impacts from the Coronavirus (COVID-19). You'll find resources and KM documents, as they are created, related to COVID-19. There ar links to KM documents for JD Edwards support for the Families First Coronavirus Response Act for EnterpriseOne and World. Doc ID 2653439.2. http://ora.cl/8sJ7F
Discover how #JDEdwards EnterpriseOne 9.2 can help you transform your business into a digital leader. Join Robert Monahan and Gary Grieshaber from Oracle in this Roadmap session on April 20. Register now with Quest Oracle Community at https://bit.ly/2X7QIr0
Reimagine your business by rethinking how you use #JDEdwards applications and digital platform. Join Lyle Ekdahl, Oracle Senior Vice President for this Keynote session on April 20. Wear your favorite sports team jersey in support of the many sporting events we are missing. Register now with Quest Oracle Community at https://bit.ly/3bYEoNJ
Are you attending the #JDEdwards Keynote on April 20? Send us your applications or tools questions at AskJDEdwards_ww@oracle.com. We will answer during the keynote or roadmap sessions. Register with Quest Oracle Community at https://bit.ly/3bYEoNJ
In Sales Order Processing, sales order invoices may be generated several days prior to processing the orders through Sales Update. Historically, Invoice Print (R42565) and Sales Update (R42800) did not have the functionality to update the exchange rate based on the invoice date. Sales Order Batch Price / Cost Update (R42950) has been enhanced to provide the functionality to update the exchange rate based on the invoice date when calling from R42565 or R42800. Doc ID 2302364.1. http://ora.cl/w3yJ8
In Purchase Order Approvals (P43081) while using the e-mail link from the e-mail for approvals, the application has historically called the ZJDE0001 version. The functionality has been enhanced to add logic to pass a user identified P43081 version dynamically so that the hyperlink will be populated with the correct version. Doc ID 2643135.1. http://ora.cl/Pi2UR
This new KM document explains how to convert the date format when the Date format in the output is yyyyMMdd but a subsequent Form request expects the date to be MM/dd/yyyy. Doc ID 2641661.1. http://ora.cl/7W4pH
If you missed last week’s announcement of Tools Release 188.8.131.52, read it now to see how we are continuing our commitment to #JDEdwards EnterpriseOne with customer-driven enhancements, #ERP optimization, and #digitaltransformation. https://bit.ly/JDE924
Are you optimizing the control and usability of your Address Book? Learn about #JDEdwards Address Book improvements and see a demo. Join Karen Brown for this Oracle Benelux User Group webinar on April 16. Find it here - https://bit.ly/3cbLyyC
Continuing our commitment to #JDEdwards EnterpriseOne, we announce the availability of Tools Release 184.108.40.206 and customer-driven application enhancements. This release is focused on ERP optimization, digital process transformation, and simplifying & automating the maintenance of EnterpriseOne. Read more at http://bit.ly/JDE924
Sales Update (R42800) has been enhanced in the 9.2 release to create zero balance adjustment general ledger entries (F0911) for all cost methods. Prior to the enhancement, zero balance adjustments were written only for cost method 07, standard cost. Doc ID 2640788.1. http://ora.cl/9q1hu
This new KM document provides the steps to create an orchestration that will retrieve rows of records from a Data Request and for each record, call another service request. Doc ID 2640695.1. http://ora.cl/Gz7Jk
This new KM document provides a couple of possible solutions to create a hard error message when entering items into a Sales Order for customers not allow to order the particular items. Doc ID 2640287.1. http://ora.cl/OF1U3
Today we are announcing EnterpriseOne Tools Release 220.127.116.11, which includes Orchestrator enhancements to drive digital process transformation, significant improvements in user experience, features to simplify and automate the ongoing maintenance of JD Edwards, along with updated platform certifications.
Continuing our commitment to JD Edwards EnterpriseOne applications, we are also announcing the delivery of high value customer driven enhancements that can be easily implemented focusing on user productivity, extending business processes and support for new business processes in many applications across JD Edwards including Capital Asset Management, Financials, Grower Management, HCM, Inventory, Manufacturing, Order Management, Procurement, Project Costing, Quality Management, Real Estate, Service Management and Warehouse Management along with legislative, regulatory and localization updates. Doc ID 2654468.1. http://ora.cl/3Zd1C
Discover benefits of #JDEdwards EnterpriseOne 9.2 that will help you transform your business into a digital leader in this Roadmap session on April 20. Presented by Robert Monahan and Gary Grieshaber from Oracle. Register now with Quest Oracle Community at https://bit.ly/2X7QIr0
CORRECTION: Bob and Gary's session is on April 20, not April 21.
Explore how you can use #Digital platforms to transform and reimagine your business in this #JDEdwards Keynote session on April 20 presented by Lyle Ekdahl - Senior Vice President, Oracle. Register now with Quest Oracle Community at https://bit.ly/3bYEoNJ
We are closely monitoring reports and resources to support future changes to #JDEdwards Payroll. Tax calculations and other legislative requirements for the Families First Response Act can be found at: EnterpriseOne https://bit.ly/2XeJ2mX World https://bit.ly/2Rj750d
It is possible to update specific fields on a purchase order such as line number, quantity and promised delivery date from a spreadsheet sent in from a remote location where the users do not have access the EnterpriseOne software. This new KM document explains how you can use the EnterpriseOne Spreadsheet Import Assistant to update fields in a Purchase Order which are not locked. Doc ID 2639835.1. http://ora.cl/zR25f
During the installation of E1Local instance on a web development Client, the listener is configured to listen on the hostname or Fully Qualified Domain Name (FQDN). Everything works fine on Development Client, but it is required to secure the inbound communication on development Client and allow inbound connections only for localhost and exclude the communication using hostname or Fully Qualified Domain Name. This new KM document provides the required procedure to change the hostname the listener is listening on. Doc ID 2639492.1. http://ora.cl/xK2Co
This new KM document explains which Distribution AAI was used by Sales Update (R42800) to create the Journal Entries (F0911) for the Sales Amount and the Price Adjustment on an Order Type SA sales order (Samples) which is "sold" for an amount of zero because of a price adjustment that subtracts 100% of the price. Doc ID 2639225.1. http://ora.cl/vz2rz
Save the date. We’ll deliver a series of live #JDEdwards Keynote and Roadmap sessions digitally on April 20. Join Lyle Ekdahl, Bob Monahan, Gary Grieshaber and Jeff Erickson for updates on your JDE solutions.
Premier Support for applications release 9.1 ended on March 31, 2020. While you can remain on JD Edwards EnterpriseOne 9.1 and continue to acquire Sustaining Support for access to our Global Services team, as well as access to existing fixes for known 9.1 issues, we highly recommend you consider upgrading to JD Edwards EnterpriseOne 9.2. JD Edwards EnterpriseOne 9.2 is part of the Applications Unlimited commitment to continuous innovation. Oracle JD Edwards provides a commitment to offer Oracle Premier Support through at least 2030. For more information, see Doc ID 2627276.1. http://ora.cl/i4bQ7