This new tabbed document consolidates FAQs for all methods of voucher processing including: Standard Voucher Entry, Recurring Vouchers, Logged Vouchers, Prepayment Vouchers, Speed Status Change, and Voucher Journal Report. Doc ID 2431545.2. http://ora.cl/1HZ4M
As a best practice, you should always set up multiple tools release foundations, including a test environment for applying fixes to JD Edwards EnterpriseOne tools releases. This helps ensure that a stable environment exists before you promote fixes to your production environment. You can also use this same principle and procedure to set up multiple foundations of major tools releases, such as Tools Release 9.1 and Tools Release 9.2.
A Multiple Foundation configuration allows for longer and more thorough testing of a new service pack/Tools Release before it is introduced to the Production environment.
New changes and/or enhancements in a new TR/SP should be tested with your customizations. It allows for "tweaking" of your modified objects to make sure they will work with the new TR/SP.
Changes or enhancements introduced with a new service pack/TR may bring unexpected issues to your E1/OW configuration. Changes may include: kernel changes, new parameters, new features, etc. that should be thoroughly tested in an environment that is not the Production environment. MF can avoid unnecessary down time that may result from a TR/SP change introduced to your stable E1/OW configuration.
Test results and extended timeline can be used to develop detailed business cases on choosing whether or not to upgrade Tools Release/SP levels.
Multiple Foundation accounts directly for less risk.
Less risk equals saved money.
Multi Foundation Implementation Process - Overview:
Introduction: Introduction to Multiple Foundation for EnterpriseOne (Doc ID 626212.1) Unix/Linux: Multi-Foundation with Tools Release 8.97 and Above on a UNIX Enterprise Server (Doc ID 972436.1)
Windows: Multifoundation with Tools Release 8.97 and Above on Windows Enterprise Server (Doc ID 865621.1)
New enhancements for Joint Venture Management are now available to calculate overhead charges and billing for joint ventures:
Overhead is calculated once a month, and there can be only one overhead entry for the joint venture, business unit, rule, method, year, and month.
To calculate overhead, you use the Overhead Rules program (P09J50) to create an overhead rule that can contain different calculation methods. Each method has an effective start and end date for calculating the overhead amount. The system provides five overhead charging methods to use: Fixed Amount, Fixed Amount with Escalation, Fixed Percent, Fixed Percent with Sliding Scale, and Day Rate and User Defined Method.
B. Billing and Paying the Partners
The expenses incurred and revenue generated by a joint venture are shared among the joint venture partners. You record expenses and revenue for actual amounts, and then bill the distributed expenses or pay the distributed revenue to the partners based on ownership percentages maintained in the Division of Interest (DOI) tables (F09J20 and F09J21).
The new Joint Venture Management enhancements can be downloaded from the Update Center under the following bugs:
When creating a Watchlist Pane in UXOne, there are three options provided: All Watchlists, Empty Watchlist, and Dynamic Watchlist. This KM document explains these three available options. Doc ID 2452714.1. http://ora.cl/0BV6q
This new KM document provides the steps to create an Orchestration Report Service Request to dynamically pass data selection values to an EnterpriseOne report UBE. Doc ID 2449326.1. http://ora.cl/yY4ta
Starting November 1, 2018, JD Edwards EnterpriseOne will begin delivering ESUs (Electronic Software Updates) and Cumulative Updates in a way which requires Microsoft Visual Studio 2017 x86 (32-bit) Redistributable Libraries be installed on the Deployment Server. In preparation for this change we encourage you to install these redistributable libraries now to avoid the symptoms described in KM Doc ID 2459487.1. http://ora.cl/Zm0We
Viviana Tilita from the Oracle Support Tech team will be presenting at Open World this year "JD Edwards Support and Oracle Cloud Infrastructure: A Successful Path to Oracle Cloud" on Thursday October 25 at 1:00 PM in Park Central (floor 2) - Concordia. Learn about the latest Oracle’s JD Edwards cloud offerings including valuable tips and tricks for success based on real customer experiences. Viviana will cover key topics such as Oracle Cloud Infrastructure, one-click provisioning, and migration to the cloud. http://ora.cl/2aG86
Mini-briefings are targeted 15-minute briefings that provide tips and best practices related to maintaining, supporting and upgrading Oracle products. They will be held on Monday, Tuesday, Wednesday, and Thursday in Moscone West, on the 3rd floor located in the Stars Bar theater. This year at #OOW18, Viviana Tilita, from the JD Edwards Tech Support team, will be presenting mini-briefing session "Accelerate your Success on Oracle Cloud Infrastructure with Applications Unlimited Support". Join Viviana Wednesday October 24 at 10:30 AM to learn, ask questions, and enter to win a prize! http://ora.cl/r2Bp6
Join us for the My Oracle Support Monday Mix free customer appreciation event at Oracle Open World this year. CONNECT with Oracle Support executives, engineers and developers. ENGAGE on ideas, share experiences, and discover new opportunities. RE-ENERGIZE with hors d'oeuvres, drinks and inspiring conversation. Admission is open to all Oracle Support customers with an OpenWorld 2018 badge and a photo ID, but is subject to event capacity. Monday October 22 from 6:15 - 8:30 PM at Fang Restaurant, 660 Howard St. http://ora.cl/8r1C1
Come meet Oracle Support experts at the Stars Bar this year. The Stars Bar is a dedicated area where customers can come meet, connect and ask questions of the Support team. It will open at 10 AM Monday through Thursday in Moscone West on the 3rd floor. http://ora.cl/r2Bp6
This new KM document provides a table listing the new Automatic Accounting Instructions (AAIs) that are needed for Balance Sheet Lessee Accounting (P0012) in the Real Estate Management module. Doc ID 2447271.1. http://ora.cl/qv5IV
When reports are run from EnterpriseOne the jobs are created on the Linux server with ----rx--- permissions. This new KM document explains how to setup within JD Edwards to have all output reports created with 777 permissions. Doc ID 2443605.1. http://ora.cl/NE3Eq
This new KM documents shows how to have the beginning balance hours that were rolled at the end of the calendar year be reflected in the year-to-date (YTD) amount for the accrual. Doc ID 2441078.1. http://ora.cl/eq3g3
JD Edwards EnterpriseOne mobile enterprise applications offer users the ability to access and update important business data directly from a mobile tablet or smartphone device. Using Oracle's MAF (Mobile Application Framework) Mobile technology,
JD Edwards EnterpriseOne has developed a long list of mobile applications including:
Mobile Inventory Transfer Tablet (M41242)
Mobile Cycle Count Tablet (M41240)
The Mobile Inventory Transfer Tablet and Mobile Cycle Count Tablet applications allow organizations to increase the accuracy of their JD Edwards Inventory Management information. Providing material handlers with bar code enabled mobile applications removes delays and errors associated with paper based processes.
The Cycle Count mobile application enables you to count the inventory at the inventory location. The application allows you to perform scheduled cycle count and unscheduled cycle count. You use the Cycle Count mobile application to:
Achieve higher inventory accuracy
Reduce hours of operation
Increase operational efficiency
The Inventory Transfer mobile application enables you to transfer inventory from one location to another using barcode scanning or manual entry. The Inventory Transfer information includes item number, lot/serial number, location, unit of measure, transaction date, and quantity information. You can use Inventory Transfer mobile application for two types of inventory movement:
Movement between different locations in the same branch/plant.
Movement between different branch/plants.
This is the future of our mobile solution and many different applications have already been released. I would encourage you to take a look at the many different mobile product offerings in the links below on MOS:
JD Edwards EnterpriseOne Mobile Applications (Doc ID 1637232.2)
Mobile Solutions for EnterpriseOne Applications - What They Are and When to Use Them (Doc ID 2101624.2)
JD Edwards EnterpriseOne Applications Mobile Enterprise Applications Implementation Guide
EnterpriseOne security uses multiple table columns like FSVWYN (View), FSA (Add), FSCHNG (Change) and FSDLT (Delete) etc of F00950 table to define security types. This new KM document explains why the VWYN column may be blank for records in the F00950 table. Doc ID 2439031.1. http://ora.cl/vD4R9
Since the inventory turns report R41116 is based on amount (not quantity), should the transaction document type IB (Item Cost Change) be included in transaction family I (inventory transaction documents) in P43115 (Transaction Type Document Family Maintenance)? This new KM document addresses this question. Doc ID 2437857.1. http://ora.cl/VA4XU
This new KM document explains how the BurdeningPostCode (BUPC) and CommitmentReliefFlag (ALT7) fields are populated in the General Ledger table (F0911) for 3-way match vouchers. Doc ID 2434045.1. http://ora.cl/7qO2u
This KM document details the value options for "Lock Code" as seen in the Time Entry "Work with time Entry by Individual" application and stored in the Employee Transaction Detail File table (F06116). Doc ID 2433520.1. http://ora.cl/86Dv0
The work order mass update process enables selection of and modification to multiple work orders at the same time. The mass update process can be used for work orders that are assigned a work order type of 02 – 03 (manufacturing), 04 (equipment), 05 (service) and 10 (tenant) from the Order Type (48/OT) UDC table.
The Search for Work Orders (P48022) program can be used to search for and select the work orders that need to be modified, and then use the Work Order Mass Update program (P48714) to enter the new values that should be applied to the selected work orders. Alternatively, templates can be set up in the Work Order Mass Update Template program (P48710) to specify default values for the fields that need updating. After enter the new values, run the Work Order Mass Update batch program (R48714) in draft mode, verify the changes required, and then run the R48714 program in final mode to commit the changes to the database.
For more details, please review General Overview of Work Order Mass Update (Doc ID 1493492.1).
Oftentimes, it is necessary to test our EnterpriseOne inbound EDI transaction sets without having an EDI translator in place. This may be for a number of reasons, many of which relate to a new implementation where all processes have not yet been integrated. The good news is that you do not need to wait for an active EDI Translator to be in place before you can test the inbound transactions. As you may or may not know, each of our inbound EDI transactions comes with its own Status Inquiry/Revisions program. These programs can be utilized to populate the required fields in the inbound EDI interface tables, thus bypassing the need for an EDI translator. Below is a list of our inbound EDI transactions and the associated Status Inquiry/Revisions program.
Inbound 810: P47040
Inbound 824: P47191
Inbound 830: P47060
Inbound 840: P47090
Inbound 850: P47010
Inbound 852: P47120
Inbound 855: P47020
Inbound 856: P47030
Inbound 860: P47130
Inbound 861: P47070
Inbound 865: P47140
It should be noted that the info above was taken from EDI Quick Reference Guide (Doc ID 659847.1). This quick reference guide contains a lot of other information that can be helpful with regard to EDI implementations. Of special interest is all EDI white papers listed at the bottom of the document. The inbound papers contain the minimum required fields that need to be populated either via EDI translator or via the Status Inquiry/Revisions programs listed above.
There are no new JD Edwards code changes required for this new release 4.2.8 of Vertex's Quantum for Payroll, but you can find more information about what's new in this release in KM document "E1: 07/77: Quantum for Payroll - Vertex Release 4.2.8" (Doc ID 2450262.1). http://ora.cl/XI2Gm
Oracle previously announced the availability of upgrade improvements for JD Edwards EnterpriseOne customers on Oracle Technology Stack, enabling customers to accelerate the upgrade process and go live more quickly. Oracle is pleased to announce the support of these upgrade improvements for JD Edwards EnterpriseOne customers on the Microsoft Windows platform.
Find details and links to additional resources in KM document "Announcing Improvements to the Upgrade Process for JD Edwards Customers on Microsoft Windows" (Doc ID 2449646.1). http://ora.cl/t8SF5
A new enhancement has been delivered to allow customers to determine if a Bank Account Number is a required field when entering customer or supplier banking information. There are different types of bank accounts that do not require the Bank Account Number field. For example SEPA accounts do not require the Bank Account Number, instead the IBAN number is required and SWIFT numbers are optional. Find details in KM document "E1: 03B/04: New Enhancement - Configured Required Bank Account Numbers in Bank Accounts by Address (P0030A)" (Doc ID 2435342.1). http://ora.cl/m5lH1
In order for companies to remain competitive in the market place, more companies are joining together in joint partnerships. A Joint Venture is a partnership between multiple entities that share in the cost and revenue associated with the joint venture.
New enhancements for Joint Venture Management are now available to calculate overhead charges and billing for joint ventures: 1) Overhead Charges enable the joint venture to calculate and distribute indirect costs to the joint venture partners, 2) Joint Venture Invoicing provides the capability to invoice the joint venture partners for the costs that are incurred in the joint venture. More information about these two new enhancements can be found in KM document "E1: 09J: – Overhead Calculation and Invoicing Joint Venture Management EnterpriseOne 9.2" (Doc ID 2430912.1). http://ora.cl/G5Rd3