Mark November 15th on your calendar. It’s #JDEdwards day during Quest Experience Week, when you can get digital education for #JDE users of all levels – for free! Sign up for updates. http://bit.ly/31voN42
Based on directions from Central Board of Indirect Taxes, Goods and Service Tax Network (GSTN) is working for building electronic infrastructure for uploading tax invoice information to GSTN portal on a real time basis and mandate tax payers to print the Invoice Reference Number generated by GSTN while printing the Tax invoices for B2B and B2G Taxable supplies. Oracle plans to provide required changes in existing solution to comply with GST requirements. Please review this article for updated information. The development, release and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. Doc ID 2567084.1. http://ora.cl/8yi1R
In 9.2, users who install the ESU for Enhancement Bug 29500686 (ORDER ACTIVITY RULES FOR MFG WO - TABLES AND DD ITEMS) will see work order activity rules functionality for manufacturing similar to what’s provided for equipment maintenance and sales and purchase order processing, to establish the allowable steps that an order can take from beginning to end. This new KM document explains the functionality of Work Order Activity Rules for manufacturing. Doc ID 2566426.1. http://ora.cl/Ps1X4
Bill of Material Change History P3011 is an enhancement that allows users to track all changes (add, update, delete) to Table F3011 BOM when Log Bill of Material flag is checked in P3009, Manufacturing Constants. To accomplish this, a new application was created - BOM Change History P3011. This makes the data viewable from the F3011. This is helpful for any user that wants to review changes made to the BOM parent or component. Doc ID 2564776.1. http://ora.cl/Tm7vh
Discover how the #JDEdwards EnterpriseOne 9.2 digital platform provides your path to the future with technologies like #Orchestrator, #UXOne, and process automation. Attend this Quest webinar on September 3rd presented by AJ Schifano - http://bit.ly/2zdUlOL
The approval process is often configured based on the business needs depending on the time period, changes of approvers as well as monetary constraints.
You can use the approval process for two types of approvers:
Approval route dictates the flow of the purchase approval process, therefore the purchase order will go to the approvers defined in the route if the purchase order total amount is higher than the user defined values entered in the ”From Amount” field. Although not recommended to have more than one person at an approval limit this scenario is often necessary in order to assure the process continues without interruption, which may consist in approvers being on vacations or just possible shifts in responsibilities.
The complexity of this option resides in the address book setup which will imply defining several layers of email contacts for the users defined in the route.
Hence, in a purchase order approval process with 3 approvers in the route code the business flow for a monetary hierarchy would be as follows:
After generating the purchase order mail should go to the first approver (from originator's id) for approval of order.
As soon as first approver approves the order then system should sends two emails, one is to originator and another one is to second approver.
As soon as second approver approves the order then system again should sends two emails, one is to originator and another one is to third approver.
As soon as third approver approves the order then system send mail to originator.
More information and examples can be found in the following KM documents:
JD Edwards EnterpriseOne deployments depend on a matrix of interdependent platform components from Oracle and third-party vendors. The product support lifecycle of these components is driven by their vendors, creating a continuous need to certify the latest versions of these products to give customers a complete technology stack that is functional, well-performing, and supported by the vendors. Starting with Tools Release 22.214.171.124, Oracle Database 19c is supported with 32-bit JD Edwards EnterpriseOne on Linux platform. The JD Edwards EnterpriseOne certifications for Oracle Database 19c on Linux platform are posted on the Certifications tab in My Oracle Support. Doc ID 2563489.1. http://ora.cl/uy7Ji
Learn how to personalize #JDEdwards #UXOne pages with the “Personalizing JD Edwards EnterpriseOne UX One Pages” learning path. Now available in Spanish, French, Japanese, and Simplified Chinese - http://bit.ly/2KMTWJO
Simplified Diagnostics Collector is a simple interface tool, built into Server Manager starting with Tools Release 126.96.36.199, to allow JD Edwards EnterpriseOne users to collect
diagnostic data and system information from EnterpriseOne servers.
Collection options: ESU install issue, OneWorld Client Install files, package build files, UBE output, Server Manager agent issue for Deployment Server
Collection options: Enterprise Server configuration and logs, UBE output, Server Manager agent issue for Enterprise Server
option to select from a drop-down list of Enterprise Servers
Collection options: HTML logs (includes Configuration files - JAS.INI, JDBJ.INI, tokengen.ini, etc. as well) , Server Manager agent issue for HTML Server
option to select from a drop-down list of HTML Servers
Server Manager Console
Collection options: system tables (CNC tables, ESU tables, OMW tables, Package tables), Server Manager console issue
option to select from a drop-down list of Server Manager console Servers
Simplified Diagnostics Collector Directories
The Collect and Generate button creates the following directories:
CaptureDiagnosticsEvery time you click the Collect and Generate button the directory is deleted and recreated.
CaptureDiagnosticsZipThis directory contains the generated .zip files and a temp directory. If it does not exist, it is created.
TempA sub-directory of CaptureDiagnosticsZip directory. This directory contains a copy of the most current .zip file for the Download Zip--<instance name> link. If the collected .zip file is over two gigabytes in size, it is recommended that you to manually copy the file. If you attempt to download the .zip file, the browser could time-out.
It is recommended that you periodically delete the .zip files in the following directories:
Deployment Server: <install path of Deployment Server instance>\CaptureDiagnosticZip
Enterprise Server: <install path of Enterprise Server instance>\CaptureDiagnosticZip
HTML Server: <install path of Server Manager Agent >\CaptureDiagnosticZip
Server Manager Console: <install path of Server manager Consolde>\CaptureDiagnosticZip
E1: SVM: Simplified Diagnostics Collector (Doc ID 2551889.1)
Advisor Webcast: JD Edwards EnterpriseOne Simplified Diagnostics Collector for 188.8.131.52 - presented on August 6, 2019 (Doc ID 2565402.1)
Simplified Diagnostics Collector is built into Server Manager with Tools Release 184.108.40.206 is installed to both the Server Manager console and the related servers. Some configuration needs to be verified in Server Manager.
For detailed Information about the configuration please check the "Required Configuration" tab of the KM document "JD Edwards: Simplified Diagnostics Collector" (Doc ID 2564285.2)
How does EnterpriseOne 9.2 help you create exceptional customer experiences and improve operational efficiency? Join #JDEdwards in an upcoming webinar on September 3 to know everything about the latest release of 9.2. Register with Quest User Community https://bit.ly/2P68lF6
Is your hardware outdated? Do you need to migrate to a different platform? Attend this session to learn about current platform trends, best practices to migrate to new hardware, and how other #JDEdwards customers have changed platforms - https://bit.ly/2Z1NDL9
Lease Management Create Amortization Schedule (R15170) is designed to use an R date pattern to calculate lease liability and right of use asset schedules.
If you are not on an R date pattern there are a couple of scenarios to view in Lease Accounting – Creating Amortization Schedules (R15170) If Not Using an ‘R’ Date Pattern (Doc ID 2542169.1) that may be of assistance to you.
The following Enhancement Bugs have been entered to address the issue:
Enhancement Bug 28328411 - Allow Create Amort Sched to Process for Company Date Pattern and Enhancement Bug 29548972 - Allow Date Pattern Other than R to be Used for Amortization Schedule Creation have been entered to requesting to allow the Amortization Schedule (R15170) to be created with a date pattern other than R.
If you are a member of Quest User group please refer to Enhancement Requests via Quest User Groups (Doc ID 1192883.1) for escalating enhancement requests.
Looking for a way to track bill of material history. New to 9.2 you can track BOM history base on parent items or parent items and specific components.
We will now be writing the Bill of Material Change (F3011) file for all changes and additions based on a manufacturing constants setting for logging bill of material changes under the BOM/Routing Options.
BOM Changes can be viewed from the following three places:
Directly from menu G3011 Daily PDM Discrete under BOM Change History (P3011)
Form exit from Bill of Material (P3002) (W3002H) for BOM History
After selecting the Bill of Material (W3002A) the user can access the BOM History again from the Form exit. Here the user also has the option under the Row exit to view the Bill of Material changes by parent/component for Component History.
With the installation of the ESU for Bug 29200369 users can make use of application P3011 (BOM Change History) from E1 9.2 release. For more details, please review 9.2 Enhancement Bill of Material Change History P3011/F3011 (Doc ID 2564776.1).
This new KM document has a short video of errors commonly seen in the Purchase Order Receipt application (P4312) and has a link listing of KM documents for P4312 errors. Doc ID 2096350.2. http://ora.cl/sq4BM
This new KM document has a short video of errors commonly seen in the Purchase Order Entry application (P4310) and has a link listing of KM documents for P4310 errors. Doc ID 1937160.2. http://ora.cl/dN7rU
This new KM document the reason for error "Invalid Basis Code" when using accruals with Basis Code 0 (% of New Base Price) in Price Adjustment Detail Revisions (P4072). Doc ID 2566369.1. http://ora.cl/C4dc4
The JD Edwards #Orchestrator has evolved since its release in 2016. Check this page on #LearnJDE that shows how #JDEdwards has added to the Orchestrator every quarter of every year since 2016! - http://bit.ly/31Ac2UO
This new KM document provides links to information about IBM's DB2 Design Advisor tool (db2advis) that can be used to identify which JDE indexes are not being accessed by E1 applications. Doc ID 2565949.1. http://ora.cl/a01YC
JD Edwards continuous innovation creates exceptional customer experiences and successes. Join Lyle Ekdahl at the #INFOCUS19 Keynote session on August 20 to directly hear from #JDEdwards - http://bit.ly/2LM12jE
This new KM document explains the process to import data into E1 tables using a CSV file via ftp. The example used shows how to use "Process Recorder" to save a Service Request to create an order using P4210 and create an orchestration to enter orders from a CSV file. Doc ID 2564800.1. http://ora.cl/iE5Xq
This new KM document explains potential causes for error "Asynchronous Business Function Error: There was a problem with the server running the business function F4314EndDoc" when attempting to voucher match a purchase order using the Voucher Match application P4314. Doc ID 2564655.1. http://ora.cl/08Ue4
JD Edwards content at your fingertips! Learn about product updates and build connections with your fellow #JDEdwards users at #OOW19 starting on September 16. To view the sessions catalog and register - http://bit.ly/2YmMJbX
This new KM document talks about resolving the error "Failed to fetch soft coding" when creating an FTP-connector via connections and promoting the orchestration and service request to another environment. Doc ID 2561000.1. http://ora.cl/ex8eo
While you're planning your visit for this year's INFOCUS conference, remember your friends from the JD Edwards Support organization will be there! Stop by our booth to say hello, provide feedback or ask questions. And, I'll be at as many of the SIG meetings as I can get to.
Consider adding these sessions by experts from Support to your training schedule:
* Hands on Lab: "Orchestrating Notifications" with Terry Pasqua and Terry Bowen #JDE-105750
Historically, there has been a difference in the Soft Rounding calculation between Sales Orders and Purchase Orders when using an Item Group (Purchasing Taxable) for Multiple Tax Rate configuration. In the Sales Order module, when Sales Update (R42800) creates Accounts Receivable records (F03B11/F0911), a Soft Rounding for Tax Calculation is done grouped by Tax Area and Item Group. In the Purchase Order module, when Match Voucher to Open Receipts (P4314) creates Accounts Payable records (F0411/F0911) a Soft Rounding for Tax Calculation is done grouped by Tax Area only. The Item Group (Purchasing Taxable) was ignored.
An enhancement is now available in releases 9.1 and 9.2 that allows users to choose to enable Voucher Match Tax Rounding by company for Accounts Payable.
For more information see Enhancement Available in Match Voucher Match to Open Receipts (P4314) to Allow Soft Rounding for Tax Calculation Grouped by Tax Area and Item Group (Doc ID 2475356.1).
Not sure what’s new with #JDEdwards Tools? Attend this #INFOCUS19 Roadmap session presented by Jeff Erickson on August 21 to know how #JDE continuous innovation can accelerate your transformation to a digital business - http://bit.ly/2ZeZhi0
Join #JDEdwards Manuel Neyra and Oscar Pinto da Luz Neto from MPL as they showcase how EnterpriseOne accelerates innovation and paves a path for businesses to redesign in a simple and efficient way. Sign up at https://lnkd.in/eYRJ72D