This new troubleshooting document has tips to troubleshoot issues with configuration and deployment of JD Edwards EnterpriseOne 9.2 Trial Edition on Oracle Compute Cloud Service Instance. (Doc ID 2389858.1) http://ora.cl/GV5yW
Besides the traditional methods import/export JDE transactions to other applications and systems using Batch Processing, Interoperability tables or EDI, JD Edwards Enterprise One offers a lot of standard Business Services (BSSVs). They enable software applications that are written in various programming languages and are running on various platforms to exchange information. BSSVs are based on widely used open standards like XML, SOAP, and WSDL. Because they are based on open standards, the knowledge for creating BSSVs interfaces is widely available. Also there are numerous third party programs and APIs for running SOAP/WSDL calls.
The standard Business Service for Accounts Payable is the Accounts Payable Manager (JP040000) has two methods:
processVoucher – for importing Vouchers into JDE
getVoucher – for exporting Voucher details to third party systems
The JD Edwards Enterprise One component that runs BSSVs is the Business Services Server (BSSV Server).
Basically if one wants to import voucher details from JDE they have to compile an xml file with the SOAP request for the processVoucher method. The file will have all the needed details of the voucher plus SOAP formatting specifics. Then they need to submit the SOAP request to the JDE BSSV Server. The BSSV Server will reply with a SOAP response that will confirm the transaction or with an error message.
To export vouchers from JDE one will have compile an xml file with the SOAP request for the getVoucher method. The request will include all the details to locate the voucher. After submitting the SOAP request to the JDE BSSV Server they will receive a SOAP response with all the voucher details.
Details on how to use the Accounts Payable Manager or any other standard Business Service methods are available in the JD Edwards Technical Catalog.
During Rebate processing, the Sales Update (R42800) performs several updates on the F0911, F4079 and F4078 tables. This new document helps to explain why the Accrued Rebates in the F0911 may not be the same as the Rebate Amount paid to the customer. (Doc ID 2377902.1) http://ora.cl/ir6Ht
An ETO project P31P001 can be interfaced to Job Cost accounting and a Job Cost Chart of Account Structure, Job, Cost Type, Cost Code. The Project Attributes P31P011 header record, Project Information tab, provides the charge to Business unit. The Job Cost tab provides the Subsidiary (Cost Code) and the Project GL class code for the cost Type (object) lookup. The Upload Job Cost Budgets (R31P800) program is used to move amounts from the ETO project to the Job. This new KM document explains the process. (Doc ID 2390084.1). http://ora.cl/4E2Ja
Starting with tools release 184.108.40.206, Server Manager can be used for deploying ADF Applications. The instructions in this new KM document explain how to deploy a custom application to the ADF server using Server Manager. Doc ID 2382739.1. http://ora.cl/6g8SX
The JD Edwards EnterpriseOne Data Access Driver (DAD) is a type 4 jdbc driver whose sole purpose is to access JD Edwards database from an outside source. Applications such as Hyperion or BI Publisher can utilize the DAD to make such a connection.
NOTE: The DAD provides the third party tool access to EnterpriseOne data in read only mode.
What are the Requirements to Use the DAD?
The DAD can only be utilized with applications that support “read-only” jdbc type 4 drivers.
How Complex is the Setup?
The setup is fairly straight forward involving placement of the dad driver jar files into the location of third party applications class path directory (Usually this will be the product’s lib directory where that application’s jar files exists). Since JD Edwards EnterpriseOne is not a database in and of itself an environment is initialized which is then utilized to perform the queries on the JD Edwards data. This is done via a URL that specifies the environment name. To get this environment to work the jas.ini, jdbj.ini and jdelog.properties files should be created on the third party application’s machine. This has to be done via server manager by registering that third party application machine and then creating a managed instance for type Data Access Driver.
For additional resources regarding Data Access Driver please see the following KM documents:
E1: XMLP: Implementation Steps for Data Access Driver (DAD) with BI Publisher 11g and Above (Doc ID 1331667.1)
Invoices created by Sales Update (R42800) are created using the same business functions used to create invoices in programs such as Speed Invoice Entry (P03B11SI), Standard Invoice Entry (P03BB2002), Batch Invoice Processing (R03B11Z1A). When the post fails for an IB batch, a number of tools are available to identify the cause for the batch to fail. This new KM document helps with the troubleshooting process. (Doc ID 2379971.1). http://ora.cl/ZF4Dm
The purpose of this new KM document is to guide how to parse Customer Item Number or Supplier Item Number (F4101.CITM) into Company Item Number (F4101.LITM) using the business function VerifyAndGetItemMaster (X4101, F4101 Get Item Master Row). (Doc ID 2378787.1) http://ora.cl/6y3Eu
The purpose of this new document is to give a brief overview of the difference between R41500 (Automatic Inventory to GL Reconciliation) and R41543 (Item Ledger/Account Integrity) and provides troubleshooting information about how the validation routines differ between the two programs. (Doc ID 2377574.1) http://ora.cl/94mB8
The purpose of the report is to get the quantities in various locations to be in sync with what is specified on the work order details. The open work order commitments can be incorrectly stated when a work order is closed or cancelled with open quantities remaining. It is recommended to run the R3190 repost on a regular basis to clear out these remaining commitments.
What the Repost Open Quantities batch program will do:
The R3190 looks at the WASHTY field (Work Order Pick List Printed) in the Work Order Master File (F4801). If it is set to 1 (WO pick list printed), the program updates the Commitments field in F3111 to H (Hard Commit) for the components on the WO.
This program subtracts the Quantity - Work Order Commitments value (FUN1) from the total commitments value (PCOM) in the Location File (F41021).
The program then recalculates the commitments based on the parts list records that belong to work orders with a status below the status in the program's processing option.
It will populate the FUN1 field with this value and then add it to PCOM to give an accurate commitment quantity.
Perform a net change on all values for the quantity and quantity committed in the Item Location (F41021) table for the selected items and then recalculate the commitments.
The R3190 (Repost Open Quantity) will not change a hard commit to a soft commit based on changes to the Manufacturing Constants (P3009). When a parts list is attached to a work order and the material is hard committed, that commitment remains until the work order is fully issued or until a user goes into the parts list and changes the location either manually, through the multi-location screen or if need be, by SQL. This commitment can be cleared out by running the R3190 once the work order is at a status that is at or above the status of the processing option set in the R3190, but it cannot be changed from a hard to soft commitment.
On a side note, if the Manufacturing Constants are changed from soft to hard then the R3190 will change existing soft commitments from soft to hard. If Manufacturing Constants (P3009) are set up originally with hard commitments and then changed to the soft commitment method, the quantities that were already hard committed will still be hard committed. Running R3190 will retain the hard committed quantity.
For parent Item
Repost the quantity value in the Item Location table for the parent item. The system uses the information from the Work Order Master table (F4801) and the following calculation:
Repost the quantity committed value for components in the Item Location table for the location specified on the work order parts list for the item. Items selected based on values from work order parts lists are reposted for every location record in the Item Location File. The system uses the information from the Work Order Parts List (F3111) table and the following calculation:
Quantity required - quantity issued
How to use Repost Open Quantities batch program:
1. For the component:
If there is a mismatch in the calculation (erroneous calculation) in F41021 (Availability), the status in the PO should be bigger than (more than) the status of the existing WO’s that need to be processed for recalculation.
If there are WO’s at an intermediate status that need to be processed (they are not planned to be advanced to 99) and there are commitments created for them, the status in the PO should be smaller than (less then) the intermediate statuses. This will clear the commitments for the components and return the reserved quantities to the initial location.
2. For the parent:
If there is a mismatch in the calculation (erroneous calculation) in F41021 (Availability) for On Receipt and On WO quantities, the status in the PO should be bigger than (more than) the status of the existing WO’s that need to be used for recalculation.
If there are WO’s at an intermediate status that need to be processed (they are not planned to be advanced to 99) and there are On Receipt and On WO quantities created for them, the status in the PO should be smaller than (less then) the intermediate statuses. This will clear the On Receipt and On WO quantities for the parent.
It is recommended to use option B) with caution, as setting a small status (like ‘30’) in R3190 PO may cause all WO’s for that item to be affected (including the correct ones, which are not at ‘99’ yet). Workaround: temporarily have the WO’s that need to be excluded from the processing advanced to a status smaller than (less than) the one in the PO’s. Since there is no trouble with the corresponding quantities/commitments in F41021, after the processing of the target WO’s, the excluded WO’s status can be reverted back to what is was. Also using in the PO a status smaller than ‘10’ (default WO first status) can cause unwanted WO selection. Try this first in a non-production environment.
For more information on Work Order Repost R3190, please review the documents below:
R3190 Understanding Work Order Repost (Doc ID 1248874.1)
R3190 Work Order Repost Performance Checklist (Doc ID 661998.1)
R3190 Repost for Service and Equipment Maintenance Orders (Doc ID 953132.1)
What to Check When Troubleshooting Work Order Repost (R3190) Performance Issue (Doc ID 2300247.1)
Enhancement Request For R3190 Report to show all changes made by repost UBE (Doc ID 2356330.1)
To Add 2nd Item Number (LITM) In Data Selection Of Work Order Repost (R3190) (Doc ID 2287231.1)
Report Interconnect function in Report Design Aid (RDA) is used when a second report is called from a first report. This document lists some commonly encountered Report Interconnect issues. This document is created to assist customers in understanding and troubleshooting the different Report Interconnect issues.
Requisition Self Service(RSS) enables users to easily create requisitions for goods and services that they need. To provide users with greater flexibility during the requisition process, you can set up delegates who have the authority to enter,inquire on, reverse, and receive requisitions on behalf of other users. A new application Requisition Delegation (P43E280) (menu G43E41) was created to bring delegation to RSS (Requisition Self Service). Using the Requisition Delegation program (P43E280), users can search for, review, add, edit, copy, or delete delegation records. Delegation records are stored in the Delegation Master table (F43E280).
The Requisition Delegation program enables authorized users to enter delegation records for anyone in the organization. Oracle recommends that you use application security when implementing this program, and that you grant access to only those users who are authorized to set up delegation records for all members of the organization. Typically, authorized users of this program are in the purchasing and/or procurement departments of an organization, and all requests for delegation setup are sent to these authorized users.
The Requisition Delegation program enables you to:
Allow a delegated requestor to perform requisition entry task on behalf of the original requestor.
Allow approvals for the requisition order that is created by the delegated requestor to be routed to the original requestor's approval route.
Review previously active delegation records.
For more information please refer to 9.1 Enhancement - Requisition Self Service (RSS) Delegation (Doc ID 1495910.1).
Two large and comprehensive documents in the Software Updates area have been reformatted into the tabbed document type to make the information easier to consume and easier to find what you are looking for - including an overview table of contents. * E1: ESU: Understanding ESUs Installs - Software Updates (ESUs and ASUs) Under the Covers - Updated to EnterpriseOne 9.0, 9.1 and 9.2 (Doc ID 2388199.2) http://ora.cl/db1bC Software Updates is the process for applying Electronic Software Updates, or ESUs, and Cumulative Software Updates such as E1 9.1 Update 2, sometimes also referred to as Application Software Updates (ASUs). * E1: ESU: Information and Troubleshooting Spec Merge UBE R98700 PDF During an EnterpriseOne Software Update (ESU or ASU) Install (Doc ID 2387976.2) http://ora.cl/VU03l This knowledge document is designed to direct you through understanding JD Edwards EnterpriseOne Specification Merge UBE R98700 during a EnterpriseOne Software Update (ESU or ASU) Install and troubleshooting Known Issues while running Spec Merge R98700 job.
Two new documents have been created for the grower module.
* E1: 43C: Grower Contract Pricing Overview (Doc ID 2377434.1) http://ora.cl/O5i2C This document provides an overview of contract pricing and discusses how to set up the pricing adjustments/schedule.
* E1: 43C: Grower Contract Payment Schedule Overview (Doc ID 2378210.1) http://ora.cl/z4MA1 This document provides an overview of payment terms and discusses how to set up the payment terms in a Grower contract.
The 2017 Oregon Legislature passed House Bill (HB) 2017, which included the new statewide transit tax. Parts of HB 2017 related to the statewide transit tax were amended in the 2018 session. The amendment changed the definition of wages to match the definition of state income tax withholding rules. Starting July 1, 2018, employers must start withholding this tax in certain instances. See this new KM document for more information. (Doc ID 2388829.1) http://ora.cl/9pz7P
A collection is a coherent assortment of style items. It may be put together by a manufacturer or designer each season to showcase new trends for a particular market. You can find many collections in the apparel industry based on seasons, such as winter collections and summer collections, as well as other themed collections, such as leather collection or cotton collection.
Characteristics of Collections:
Are time-bound. Generally, a collection is designed and marketed for one season or year.
Have a multilevel structure. The collection structure consists of multiple levels such as themes, brands, and styles.
Groups related style items together.
Can contain the same style item that is present in other collections at the same time.
A collection template is a subset of style items from one or more collections. User can add style items from multiple collections to a collection template.
These templates are used during sales order entry, as well as purchase order entry, to simplify the process of entering orders. A collection template contains frequently ordered style items. A collection template applies to all customers.
For more information, please refer to Collections And Collection Templates in Apparel/Attribute Management (PCW06, PCW07, PCW54) (Doc ID 1622959.1)
Vertex has announced that they have released version 4.2.6. Changes were made in release 4.24 that caused incorrect wage accumulation in some cases when the customer chose JIT 3 (Accumulate wages only if tax is withheld). The issue could occur when an employee lives and works in two different states, and is marked state income tax exempt in one of the states. In the now-available release 4.2.6, the code changes made in release 4.2.4 were removed. Doc ID 2388887.1http://ora.cl/yO8nE
This new informational document "Personal Information Within JD Edwards EnterpriseOne" can be used as a reference to help identify where personally identifiable information, or sensitive personal information is managed and stored within JD Edwards EnterpriseOne. This document can be used to reference which applications, tables and data dictionary items manage and store customer, supplier and employee personal information. This document limits it analysis to master data applications and does not include an analysis of personal information within transactions. Doc ID 2388299.1http://ora.cl/J3TJ6
If you use taxed prices for sales orders, the system displays item prices that include taxes. You can either enter the taxed prices or allow the system to calculate the taxed prices, depending on the information that you enter and the type of sales order. This Enhancement was bought by Bug 11036125: E1 APPS - SOM TAXED UNIT PRICE from 9.0 Product Release.
To do so, below set up must be done for taxed prices:
Select the Sales Taxed Prices constant
In "Branch/Plant Constants program (P41001)" - select the "Enable Sales Taxed Prices" check box on the "System Constants" form. If you select this constant, then you must also select either the By Sold To or the By Ship To constant. Therefore, when you enter values in the Sold To and Ship To fields on a sales order, the system checks setting on the System Constants form to determine whether the system is set to use the Sold To or Ship To customer.
Specify that customers use taxed prices.
In the Customer Master program (P03013) select the Use Taxed Prices check box on the Billing Information form. The system displays the Use Taxed Prices check box on the Billing Information form only when you enable taxed prices for sales orders in the system.
For more information please see JD Edwards Enterprise One Taxed Prices for Sales Orders 9.0 (Doc ID 1234293.1)
To refresh any inventory commitments in Item Location File (F41021) where the item does not have any active sales orders associated with it, can use new report Refresh Inventory Commitments (R42990). The existing program Repost Active Sales Orders (R42995) refreshes the commitments for only those items that have an active sales order.
There may be a case where the sales orders are all completed for an item, but for some reason there is still an outstanding commitment recorded in F41021 that needs to be cleared out. R42995 will not update this item in F41021. One workaround involved creating a 'dummy' order for the specific item so that R42995 would correctly repost the order. The 'dummy' order would then need to be cancelled after running the Repost Active Sales Orders (R42995) program. Another workaround involved using a database utility program such as SQL to clear the commitment buckets in the Item Location (F41021) prior to running the Repost Active Sales Orders (R42995).
Run Refresh Inventory Commitment (R42990) at the same time as the existing R42995 is run. The UBE should be run outside business hours. Oracle strongly recommends that you run the R42995 program when no one is on the system. R42990 should also be run when no other sales activity is being performed.
With the installation of the ESU for Bug 25471557 - INVENTORY COMMITMENT REFRESH USING SALES REPOST, can make use of report R42990 (Refresh Inventory Commitments) from E1 9.2 release.
For more details, please review Refresh Inventory Commitments (R42990) (Doc ID 2230896.1).
JD Edwards EnterpriseOne 9.2 customers who installed Update 2 (UN2) or ESU JN14773 received new functionality for Address Book Translation Records. Users with a language specified in their user profile encountered errors in sales order entry, match voucher to open receipts, and voucher redistribution.
Development revised the Address Book translation functionality from automatic to manual processing and addressed error messaging. At this time, the fixes are delivered in two ESUs. An alert has been added to each ESU directing customers to apply both ESUs to ensure they receive the complete fix. Also, alerts have been added to UN2 and JN14773 pointing to document 2369906.1.
The revised functionality and related bugs are outlined in the KM document "E1: 01: Prevent Translation Table Updates and Correct Error Messages Associated with the Address Book Translation Records" (Doc ID 2369906.1). http://ora.cl/90XW4