This new KM document provides a matrix to demonstrate how different dates such as user defined dates, event dates and other date codes can affect Benefits Enrollment. Doc ID 2534743.1. http://ora.cl/zt2ug
This new KM document explains why the Pick Date might be overwritten with the Promised Date when clicking OK in the Transportation Sales Order Entry application (P4210). Doc ID 2534740.1. http://ora.cl/IE2td
The Single Euro Payments Area (SEPA) is a payment-integration initiative of the European Union for simplification of bank transfers denominated in Euro. SEPA is used in the European Union (EU) countries and in a few countries outside of EU that use Euro. SEPA’s goal was to reduce the costs of doing cross border transactions in the Euro currency. SEPA electronic payment formats were developed for both Accounts Payable (SEPA Credit Transfer) and for Accounts Receivable (SEPA Direct Debit. SEPA was based on subsets of ISO20022 standard.
JD Edwards implemented SEPA electronic payments for both Accounts Payable and Accounts Receivable. In order to obtain all the features one needs to apply the ESUs returned by the SEPA query for their release in the Change Assistant tool. For more info on how to install and use the Change Assistant tool please see Frequently Asked Questions For Change Assistant Tool - "How To" Questions (Doc ID 1057524.1).
These would be found in the navigation tree under: Search for Packages> JD Edwards > Electronic Software Updates > Localizations.
SEPA for Accounts Payable was implemented as a separate Payment Print Program in the existing Automatic Payments process. SEPA for Accounts Receivable was implemented as an automatic debit program in the existing Automatic Debits process. They both make use of Report Definitions.
The documentation for SEPA can be found in the localization manuals:
Past releases of the JD Edwards EnterpriseOne required that a customer establish licenses before running the product’s client software. The maximum expiration date of any JD Edwards license for client software is June 30, 2019. Past that date, releases of EnterpriseOne (prior to Tools Release 8.98) will be license locked for the JD Edwards EnterpriseOne Client. The whitepaper "JD Edwards EnterpriseOne Licensing Disabling Client Licensing for Various Tools Releases" explains what you need to do to avoid service disruption. It is attached to KM document Doc ID 2063072.1. http://ora.cl/J9fv4
This new KM document explains why ESUs and ASUs are shown with strikethroughs in the Software Updates application with a One-Click Provisioning EnterpriseOne installation. Doc ID 2533486.1. http://ora.cl/1nn2k
Learn about Continuous Delivery and Continuous Adoption for JD Edwards and hear how Skanska used this approach to ensure maximization of their ERP investments. Join this webinar on May 30 with Jeff Erickson of JD Edwards and CSS International. http://bit.ly/30pjO4e
What is your innovation strategy? Read this interview by Lyle Ekdahl, Senior Vice President, JD Edwards in #JDEdwards special issue of Oracle Profit magazine to know more about JD Edwards Continuous Innovation http://bit.ly/2HpuhFp