When you want to review account activity over several fiscal periods, as well as statistics such as delinquent days sales outstanding (DSO), weighted average days late, average invoice amount, percent of invoices paid late, and so forth, you can run the Statistics History Update (R03B16A) program. In addition to providing statistical information about the performance of collections over a period, the system enables you to review multiple customer accounts simultaneously for comparison purposes.
More details on how this report works, common issues and troubleshooting tips could be found in:
How To Process and Purge Statistical History Refresh Data In JD Edwards EnterpriseOne Accounts Receivable (Doc ID 625834.1)
Frequently Asked Questions about AR Statistical History (Doc ID 664021.1)
How To Calculate Statistical History Update Fields (Doc ID 656325.1)
JD Edwards EnterpriseOne does not support the calculation of taxes on Landed Cost at the time of Voucher Match (P4314). When entering a landed cost voucher, the tax fields in the grid are locked and cannot be edited by the user.
In the past, clients have attempted to work around this problem by using Line Defaults to input the tax information and default in onto the grid row for the landed cost. This method was unreliable because it often resulted in an "Amount Does Not Balance To Gross" (0088) Error. In releases 9.0 and 9.1, the ability to use line defaults with landed cost was removed. In many countries Landed Costs are considered taxable, thus a method is needed to enter tax for landed costs. This new KM document provides a method that can be used. Doc ID 2361329.1. http://ora.cl/PS2C5
The Integrity Analysis program (R30601) generates a report that identifies any processes or Bill of Material (BOM) structures that must be corrected to properly generate production costs (R30812) and successfully obtain MRP output (R3482/R3483). If the report indicates errors, correct the processes or BOMs and run the Integrity Analysis program again. When the program does not find errors in the processes, it updates the low-level codes (IMLLX) in both the Item Master (F4101/LL CD column) and the Item Branch File (IBLLX- F4102). Low-level codes are commonly referred to as LLX, IMLLX, IBLLX, or lower level codes.
Purpose of BOM Integrity Report
To assign correct low-level codes, run the Bill of Material Structure Analysis program (R30601) with the processing option that is set to consider items in projects. Run the BOM Integrity (R30601) regularly to check for recursive BOMs, missing item branch records and to set low level codes. Correct any errors.
Troubleshooting Integrity Analysis Output and Errors (Doc ID 639397.1)
Set all low level codes (LLX) to 0. The file must be backed up, and the R30601 must be run after setting to zeros. This process is necessary as the Low Level Codes for an item (LLX) may have become misaligned between the F4101 and F4102. This process is documented in Low Level Code LLX is Different Between Branch Plants (Doc ID 828438.1).
Output from BOM Integrity Report
If all LLXs are correctly set between branches, there is no output from this SQL script. If the integrity of LLX is questioned, SQL F4102.IBLLX to '0' and then re-run R30601 followed by the SQL script again.
MRP (R3482 or R3483) and LLX
Low level codes provide MRP direction when exploding parent demand down to component demand, across all branch plants. Items which are at top level (Level 0 at BOM) across branches are planned first and each level is planned sequentially. When low level codes are not set up correctly, MRP will not create proper pegging records (P3412) or generate Detailed Messages (P3411).
The Low Level Code LLX should never be different between various Branch Plants in the same instance of EnterpriseOne, for details see Low Level Code LLX is Different Between Branch Plants (Doc ID 828438.1).
Not having correct low level codes will prevent parallel processing from completing correctly, for details see Parallel Processing for MRP R3482/R3483 (Doc ID 626115.1).
PRP and LLX
Project is for ETO, specifically when using Project Requirements Planning (PRP). PRP uses the low-level code to identify the lowest level at which an item resides in a bill of material structure. The low-level code is assigned to an item when the item is added to a manufacturing BOM. An item can reside on a manufacturing BOM, the project work breakdown structure, or both. Because the work breakdown structure is similar to a BOM structure but is not a BOM, the system requires a way to assign an item's low-level code when you use it on a given project.
Parallel Processing and LLX
Without parallel processing, MRP reads each record in the F4102 and processes them one by one, according to data selection and low-level code.
With parallel processing, multiple items can be processed at the same time. Items within the same low-level code(LLX) can be planned concurrently, since they do not depend on one another. The master UBE is called, which will in turn submit as many child UBEs as the number entered in the 'Number of Processors' processing option on the Parallel tab of R3482/R3483 minus one. The reason for 'minus one' is that the parent job counts as one of the jobs being Each UBE will submit an entry in the Job Control Status Master table (F986110).
When viewing submitted jobs, note the Parent + Child Subsystem UBEs. Each of these UBEs will write to, process and delete records from the Subsystem Job Master table (F986113).
You may frequently process Prepaid Cash or Check Sales Orders, as opposed to Credit Card Sales Orders. At the time of Sales Update (R42800) you can reflect the cash payment on the Customer Ledger (F03B11) record to show that the invoice was already paid and create the G/L Credit Journal Entry for the Accounts Receivable Trade Account to Offset the Debit created for the Sale. Refer to this new document for the setup and steps needed to create Preauthorized Drafts at the time of Sales Update to retire the Accounts Receivable obligation automatically. Doc ID 2361275.1. http://ora.cl/D5km4
Oracle EnterpriseOne software offers a variety of standard reports that provide useful information related to Case Management. The information contained in these reports allows an organization to analyze data in order to make decisions related to provider groups, case assignees, products and customers. Doc ID 2361256.1. http://ora.cl/EU0Tc
f you have an issue with restoring a BSSV par file that was saved from OMW, you can restore the BSSV objects manually by following the steps in this new KM Document. Doc ID 2358267.1. http://ora.cl/w4h2n
Normally the system will take the Tax Explanation Code from the 'Sold To' address, and the Tax Rate/Area from the 'Ship to' address on a sales order. By using “Date Sensitive Customer Sets” you can allow the 'Delivered To' or 'Ship To' address book number to be used to populate the Tax Rate/Area and Tax Explanation Code on a sales order. Line of Business must be active in AR constants and Customer Sets must be active in System constants.
For more information please see Date Sensitive Customer Sets (Doc ID 625649.1).
With the introduction of CafeOne in Tools Release 9.1.3, the Longitude and Latitude fields linked to the equipment number can be useful for managing physical asset locations. As maps can be part of CafeOne layouts, this data can be used to render the map location.
See how an organization and leverage this functionality in Equipment Master Setup and Processing (Doc ID 1392538.1) under the section Latitude and Longitude.
When you perform and action on an object through OMW or when package build creates a modification, OMW will create history records. You can export different versions of objects to restore and compare using ER Compare. You use the Work with Repository History (P98780H) application to manage the object history records. Doc ID 2357415.1. http://ora.cl/y9ck4
Warranty Claims/Supplier Recovery Claims is a feature within Service Warranty Management that tracks claims related to product failures. Claims can be between dealers and manufacturers or manufacturers and suppliers. Doc ID 2356820.1. http://ora.cl/CF2QZ
Sometimes, the PPD file used for paper tray selection after implementing the recommendation in "New Printer Paper Tray Selection Features on EnterpriseOne Tools Release 188.8.131.52 for PostScript Printers" (Doc ID 1333791.1), does not include the proper commands to be embedded into the postscript file created by JD Edwards EnterpriseOne and thus the paper tray selection is not working as expected. This new KM document provides instructions how to verify the information and correct it, if necessary. Doc ID 2353547.1. http://ora.cl/Yn0yY
This blog will help to download and apply the WLS Path for the issue mentioned in Unable To Access E1 Main Menu Screen After Clicking Login or Stuck on Login Page for JAS Instance Configured with WebLogic Server - 184.108.40.206.0 (Doc ID 2185160.1)
Note : This blog is created based on the below E1 Setup configuration, steps may vary depends upon your setup configuration ( OS and WLS version ..etc).
Download WLS Patch 26197278 from Patch and UpdatesWe can download weblogic patches from support portal --> patches and updates.Enter the Patch number as 26197278 then hit search buttonSelect the Patch then click on Download
Save the file in local drive then extract the zip file
Before trying to apply the WLS patch , make sure to complete the below tasksSet Environment variable : Add the opatch location K:\Oracle\Middleware\Oracle_Home\OPatch to PATH variable
Stop Admin Server , Managed Servers and Node manager
Follow the below steps to apply the WLS Patch:
Run CMD as administrator user
Type opatch version --> This should display the version as shown in the screenshot
Navigate to the Download location of the Patch ( C:\Users\Administrator\Downloads\p26197278_122120_Generic\26197278)
Now type opatch apply (enter y to continue the installation)
WLS Patch installed successfully! ( Now start the HTML Server and test the issue)
Starting with Tools Release 220.127.116.11 and Orchestrator Studio 5.0.0+/1.5.0+ ADF server Foundation IoT Orchestrator Studio components can be installed from Server Manager (see E1: IoT How to Install IoT Orchestration Components (Studio) And/Or ADF Application/Container from Server Manager (Doc ID 2310874.1)). Prior to this Tools Release and Studio/ADF Foundation release, you must import/deploy the components using the "ant deploy" command. This new HowTo KM document provides the necessary steps. Doc ID 2353230.1. http://ora.cl/QO09R
If you take credit cards, cash or check payments at the time of sales order entry, the sales order is prepaid and there is no need to collect a payment from the customer to retire their open accounts receivable invoice.
Normally Sales Update will automatically create an AR Ledger Record and a Debit to the AR Trade G/L Account even if the order has been prepaid.
If the Prepayment Tab processing options are set correctly the AR Batch Draft Creation (R03B671) will create Preauthorized Drafts at the time of Sales Update to retire the Accounts Receivable obligation automatically. When the AR Batch Draft Creation (R03B671) runs, it will record the payment against the AR Ledger invoice created by Sales Update and will also create a Credit Entry against AR Trade G/L Account leaving a net balance of $0 so that no money need be collected from the customer.
For details on how to setup this functionality, please refer to Case Study: How to Create Drafts at Sales Update for Prepaid Cash Sales Invoices (Doc ID 2361275.1). Although the example shown is for a Cash Sale, the functionality works equally well with Sales prepaid by Credit Card or Check.
Starting with BI Publisher 18.104.22.168 (delivered with Tools Release 9.1.x), there is a XSL-FO function for converting the HTML code from XML source into FO formatted text. This new KM document explains how to convert the HTML code so it can be included in BI Publisher reports. Doc ID 2352661.1. http://ora.cl/MP716
There are two new KM documents about FASB/IASB functionality for Real Estate Management: * "FASB/IASB Functionality for JD Edwards Real Estate Management (FASB ASC 842 / IASB IFRS 16 )" - this new document was created to provide updates, documentation links, and information about Advisor Webcasts and bugs related to Revenue Recognition, Straight Line Rent and Balance Sheet Lessee Accounting for the Real Estate Management product. Doc ID 2356624.1. http://ora.cl/tJ1jA * "Lease Management Enhancements to support FASB ASC 842 / IASB IFRS 16 Regulations" - this new document provides information about the lease management enhancement with links to the guides and an FAQ document. Doc 2356671.1. http://ora.cl/lt3n8